I really like your simple world editor. I have a few suggestions that I think might be helpful.
Documentation:
The “simple” aspect of your editor is quickly becoming “not-so-simple” as you add more functionality. To this end, I would suggest writing a document to explain how to use it. I know that English is not your first language, so I will volunteer to proof read your document for you, if you would like. I am a native English speaker and have been teaching English in Brazil for almost twenty years. I look at the jME forums almost everyday, so if you want my email for contact, just let me know.
GUI:
I think your GUI is fine and the color scheme is very cool. You say that you want to make the GUI cooler. I don’t think that is necessary. The GUI is very cool as it is. It will need the obvious adjustment as the app grows, as is to be expected. I like your choice of Nifty, as it shows what results can be achieved with the Nifty library. There are some very small English mistakes that should be rectified, but nothing too serious. Your ENTITIES tab should probably be called ASSETS, since this is what you are dealing with.
Integration with JMP:
I like to use blender full screen with JMP open. It is quite easy to Alt-Tab between applications. And now we can execute blender from within JMP once a .blend file is selected, which is really nice. I think your app could be executed in a similar fashion, having a button to open it in JMP. It would probably be better if it could default to full screen when it first opens too. And it would be good to have an appropriate icon to appear in the task bar (I’m running Win 8.1) rather than the default java tea cup.
Well, those are my comments. I hope they have given you something to think about.
Até mais!
PS. I’m also really hoping that the Nifty Editor goes ahead. That is another cool project too.
I really like your simple world editor. I have a few suggestions that I think might be helpful.
Documentation:
…
GUI:
…
Integration with JMP:
…
Well, those are my comments. I hope they have given you something to think about.
Até mais!
PS. I’m also really hoping that the Nifty Editor goes ahead. That is another cool project too.
Hey! Thank you for such suggestions!
I still have not so much time: job+freelance+wife take the time.
And the SWE is still one-man-project. But i want it to become the community project. I hope this will be changed when i add some cool features (lights positioning, physics etc…).
Looking good! I think SWE could be a really good starting point for developers who want to make their game moddable by novice users, since it’s at that place in between the SDK and a game with just a scriptable console.
Have you put it through its paces yet, doing a little project from beginning to end with it?
@erlend_sh said:
Looking good! I think SWE could be a really good starting point for developers who want to make their game moddable by novice users, since it's at that place in between the SDK and a game with just a scriptable console.
Have you put it through its paces yet, doing a little project from beginning to end with it?
Thanks!
I need to make some improvements and refactoring still to make it fully usable. But it will happen soon.
Then i will make some tutorials.
first time I came across this and it is looking pretty neat.
Not sure if I might use it in the near future but I’ll keep this one in mind - you never know
Just wondering… What functionality does the JSON provide that node properties and BinaryExporter wouldn’t? Also I’ve added lighting functionality. PM if you’d like it (or do it yourself, look into LightNode’s).
It’s just because I’ve also removed all JSON saving and loading, and everything seems to be working fine (LayerGroup settings are stored in an ‘editor’ node as node properties), but I’m wondering if I’ve missed anything out.
Edit: It’s also probably worth noting that you should use link nodes instead of directly adding the asset. If you use JSON saving then it’s fine, but for J3O it packages everything except textures into the 1 j3o file. Just a suggestion.
Do you have Skype? As I’d be interested in joining this project.
@fabsterpal said:
Just wondering.. What functionality does the JSON provide that node properties and BinaryExporter wouldn't? Also I've added lighting functionality. PM if you'd like it (or do it yourself, look into LightNode's).
It's just because I've also removed all JSON saving and loading, and everything seems to be working fine (LayerGroup settings are stored in an 'editor' node as node properties), but I'm wondering if I've missed anything out.
Edit: It's also probably worth noting that you should use link nodes instead of directly adding the asset. If you use JSON saving then it's fine, but for J3O it packages everything except textures into the 1 j3o file. Just a suggestion.
Do you have Skype? As I’d be interested in joining this project.
