-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Future of skript-parser #25
Comments
It is good to have a central place for progress. I think the road map is fairly detailed and pretty realistic. I have a few remarks:
Beside that, I don’t want to go too in-depth into the end goals of the road map, but I think making a JVM parser will be hard, especially with all the events etc. It’s definitely possible but I don’t know if this should be a priority. About the application parts, I always was thinking about making an IDE for skript-parser, that automatically installs the main plugin and registered addons. I do not know how to make one, but maybe this could be a thing on the road map? Because that sounds a lot more useful and practical than making an Android application. We can be ambitious, but our dreams need to be realistic. We have no budget whatsoever and we all do this because we like this project. |
Of course. The addon developers api of this project will not be available before
Maybe it could be interesting to share with the main project what you did. Like create a pull request for functions, one for dates etc...
I'm not sure to make it right now. Like you see in the roadmap, modules system (so addons which are non-related to Minecraft) will start to work only for the
We already think about it. It takes time, and we didn't chose any name yet. Let's see in the future.
It already exists since a while. We call it
It's the same thing of BDiscord. While the api for addons dev is not stable (and so api for modules), we can't make it. |
If Syst3ms wants to go this way, I think I’ll just abandon it and transfer everything here. The main reason I made my own project is that Syst3ms initially wanted to keep this library, welp, a library, with little function to have a bare foundation.
You can currently make a perfectly fine addon for this parser using the tools provided. It is actually pretty straightforward, yet given that there is no documentation for it yet.
I currently think this is a priority. We can’t go from a library to a full functional program without going to this relatively simply process.
I think we should make a separate one only for this project if we want to take it this far. You’re ambitious, and I want to be too, but this’ll only work if we can get more people on track. This should go together with finding a name.
Agreed. I took another look at the road map and it’s on the right spot. I currently am just waiting for @Syst3ms to reply. If he wants to go this way, I’ll transfer Buzzle onto this after a new name is chosen. |
Hey @Mwexim
It was what Syst3ms saying me in a vocal discussion |
See @WeeskyBDW post above
Literally not. Find a new name is not the priority at all. Change the project name takes 5 minutes, but working on the projects take months.
Let see with @Syst3ms & Skript contributors |
I agree for separeted discord server, it permit to not be loosed whith many channels (1 by skript addon in skript-chat server) and then a better activity/responce time from other contributors. Also, it permit to people who just interrest by skript-parser to have a special discord server for that For finish, it permit to make public discussions about skript-parser and more opinions |
Why wouldn't this be possible to be done on the Skript Chat Discord server? I just think it would be much more convenient to create a specific category on Skript Chat. |
I already knew this. I’m just putting my arguments here because I do feel I am engaged with it. Although I am not a Skript contributor, I do have had regular conversations with Syst3ms since may. I don’t know how long each of you guys contributed to this project in particular (I mean skript-parser), but suddenly (since a month or so) there are a lot more contributions from several people like @Olyno and @Romitou . So sorry if I am not taken as an active contributor to this project, I did not want to force my opinion onto anyone here. I just think it’s weird after all this time suddenly there are plans. Was this planned with the contributors of Skript itself? |
Peak contributions are due to several factors. On my side, it's mainly because I have time and I like to contribute to Skript at my scale. |
If you want to contribute to an implementation of the parser using what you've written yourself, you are more than welcome to do so. Nonetheless, I am somewhat reluctant to begin implementation right away, because my mentality is "logic & API first, implementation later". I am very much open to any suggestions or propositions for a better API. The core logic and library aspect of the project will always be kept to some extent. I'm mixed about creating a dedicated discord or something of the sort. Right now I don't feel like the project is quite active enough to warrant one. A good start for the documentation would be to generate the javadoc of the project, which might need some changes to do because the syntaxes Javadoc follows Skript's custom documentation format right now. A wiki is still welcome. |
Future of skript-parser
Overview
The skript-parser project was created to improve the current Skript parser.
Here is a simple roadmap to guide current and future contributors throughout the project
Based on the big spots of the initial Skript project (SkriptLang/Skript#121):
With regard to this project directly:
Roadmap
Here is the proposed roadmap:
Implement all existing Skript syntax that does not require Minecraft (example: amount of %objects%)
Add a testing system like the current Skript project
Create a CLI in order to execute scripts in an efficient way
Fix parser & CLI issues
Rework the system of variables to make it much more efficient
Fix potential variables issues
Having a high-performance module system to extend the skript-parser
Fix potential modules system issues
Full documentation
Skript-to-JVM compiler
Fix potential issues with JVM compiler
Total duration: planned on 26 months, September 2022
To note: All these dates are only approximate and may change depending on the speed of the project and its contributors. Please do not take them for granted, but only as a guide.
skript-parser projects
If we have projects created with the new parser, it will be easier to see our progress. Here are some interesting projects to do:
To note: These are only project ideas. The goal is not to push them to the maximum but only to see the skills that skript-parser possesses.
The text was updated successfully, but these errors were encountered: