@normen said: To add to the fragmentation of jME libraries? Why do you think people will find it easier to add to a maven repo than creating a plugin library with a wizard? And if they do, why should SDK users be left in the rain?
I really don’t want to start an IDE flamewar here, but its a fact that there are at least 3 big players and lots of smaller alternative program environments out there. Now, i would say that most of the programmers already working with java don’t want to install a separate IDE. Even users who already use netbeans probably don’t want to resetup theire whole programming environment.
This leads to 2 issues, firstly i think there are not sooo many people out there that use the sdk how it is ment to be used, missing/broken functionallity or for whatever reason.
As a follow up all that people have no interest at all writing fixes, or plugins for a editor system they actually cant/dont use in their production…
Don’t get me wrong, i kind of like the idea to have a central toolbox/editor environment. (As you call it, the jmeExperience)
But from my point of view the ultimate goal should be to write the whole thing against jme and not against netbeans, so that every programmer out there could make use of it. Even the hardliner writing a project in vim could start a editor within jme. It could actually be only a jme plugin at all.
[java]statemanager.attach(new Jme3Editor()[/java]
could be all needed to integrate it in your own project.
Once it would work, we could even start the editor while playing our game. While running around you see that the terrain textures are not matching, a simple click on “CTRL+T” opens the ingame terrain editor, and you correct the issue.
If you like it to be integrated into your ide, all needed would be writing a minimal plugin opening a tab showing jme. What i am proposing is to bring the whole idea of the sdk to any production environment out there…
*The pluginsystem could then actually fully depend on gradle, if you want a clickable gui as you have currently in the sdk, no problem i would say. After all the new plugin-plugin would only have to add/remove a single line in the grade file.
**Consider this as an option for 3.2 i would say.