Added properties for SunAndStars.
Finished working on integration with SkyControl.
@sgold
Also, I’m waiting for review of the PR:
Started to work on updating terrain editing and adding “spawning tools”, to spawn some models on a scene using a brush
I have read everything in the thread but didn’t see anything about a GUI Builder using Lemur, if @pspeed gave his blessing that is? Like how when you add a new swing gui form, the palette opens up with all your options like buttons, layouts, properties?
Or is that something that should still be handled by code?
It’s open source, BSD license… blessing not required. Go forth and make cool stuff.
Does Lemur support declarative style of scene structure like FXML in javaFX?
What do you mean by “declarative style”?
That’s not the same as “does it have a mark-up/definition language?”… to which the answer is “No, because no one has implemented that yet”.
I just use groovy when I want that.
Something like this:
I just think about what can be a result from “scene builder” in the case with Lemur…
I attempted to do something like this, rolling out my own widgets on top of Lemur, with a XML layout.
The XML looks like this
So, maybe I will make something like ‘scene builder’ in future But now I’m working on other features
ver. 1.6.0
-Updated jME libraries.
-Implemented multi-terrain editing.
-Extended Plugin API
-Added the plugin to integrate SkyControl
-Extracted supporting tonegod.emitter to a separated plugin.
-Updated Settings dialog.
-Bugfixing.
IMHO xml is still a waaaay better way to make UIs than all that .setXY() spaghetti code.
Well that’s your opinion, but my point was more, if you are going to use some kind of markup langage, there are so many choices that cross my mind before XML…
I shouldn’t have troll, or hijack the discussion, don’t mind me.
These are not the only two options.
(sentence)(conjunction)but(/conjunction)(conditional)if(/conditional)(pronoun)you(/pronoun)(verb)like(/verb)(pronoun)that(/pronoun)…
then more power to you.
Personally, I think DSLs are best for UIs. XML is abysmal.
I agree that XML is not ideal (if I were to redo it now I’d choose JSON instead).
However: the whole point of an XML or JSON layout is to build tools on top of it (like Google did with the Android XML layout files). Tools that are intended to be used by designers, not coders. The whole point of having an editor.
This is why I’m a bit skeptical with Groovy: it is powerful mostly for programmers.
Ops! Sorry for keeping up the hijiacking
Groovy != DSL. Groovy is the tool you could use to make the DSL.
Even JSON is a little verbose when you just want something like:
container {
label(“My Label”)
button(“Exit”)
}