Please also have a look at the constantly updated Documentation for info on how to use the current jMP builds. This is by no means the final version of how things will be but its some hints for people who want to try around with the current builds.
On the news side, “Tomygun” offered to help out with the jMonkeyPlatform coding and he is working on a generic timeline editor and a cinematics editor for jMonkeyPlatform, here some eyecandy for you:
+1 for choosing the only Gnome theme that Ubuntu ships with which isn't absurdly unusable.
and… +2 for some nice work
Can you explain what prop means and what first and second means? I thought I knew but the way things were situated on the timeline assured me that I didn't understand XD
+1 for choosing the only Gnome theme that Ubuntu ships with which isn't absurdly unusable.
Lol right ;) I'm too lazy to search for something cooler so I ended up with that.
sbook said:
Can you explain what prop means and what first and second means? I thought I knew but the way things were situated on the timeline assured me that I didn't understand XD
The contents on the Tree are placeholder. The ones named "First" and "Second" should be each be a Spatial, Camera or something you will alter during time. Each holds a list of properties that are going to be affected, "Prop 1", "Prop 2", etc. In the timeline area you can drop KeyFrames (the red triangle pointing up), each of those holds a value for that property in that given time. By selecting the KeyFrame you can edit it's value, in an earlier screenshot a color picker is showing because that property was parametrized with a Color class type. Adding several KeyFrames with different values makes an animation. I still have to begin working on the Curves Editor, it will enable to define how the values are interpolated from keyframe to keyframe. Those familiar with the UDK, Unity or Maya surely know how a Curve editor works.
Currently each property track and it's keyframes are parametrized with a generic type, allowing the possibility of adding support to edit any kind of property and provide a custom Component to serve as it's value editor, default editors for the most common classes are already provided by Netbeans as the Color example shows. Given the design of Netbeans RCP it will be really simple to allow plugins to extend that functionality. Timelines basically wrap an object and it's properties, how those changes are shown will be in charge of each Timeline implementation making the whole "Sequence" editor (as I call it) extensible beyond just Spatials.
The fun part, when we begin linking the timelines to actual stuff, like a Spatial will take some time. But is definitely coming.
Momoko_Fan said:
Very cool. Soon the JMP will beat UDK at this rate!
Pffffffffff off course, I'm already planning the Particles Editor, Materials Editor and I have always been fascinated by language editors and compilers so who knows, perhaps we end up making games in BananaScript with the JMP.
sbook said: The contents on the Tree are placeholder. The ones named "First" and "Second" should be each be a Spatial, Camera or something you will alter during time. Each holds a list of properties that are going to be affected, "Prop 1", "Prop 2", etc. In the timeline area you can drop KeyFrames (the red triangle pointing up), each of those holds a value for that property in that given time. By selecting the KeyFrame you can edit it's value, in an earlier screenshot a color picker is showing because that property was parametrized with a Color class type. Adding several KeyFrames with different values makes an animation. I still have to begin working on the Curves Editor, it will enable to define how the values are interpolated from keyframe to keyframe. Those familiar with the UDK, Unity or Maya surely know how a Curve editor works.
I was thinking Props like one would have on a stage Properties makes much more sense, thanks for clearing that up!
The curves editor was perhaps the most enjoyable, and frustrating thing to use, when I used to spend lots of time doing animations in Maya. So much possibility for incredible movements that you spend all your time fussing towards perfection but never quite get there!
We haven't checked for potential copyright issues have we? I doubt there could be any, but you never know in this troubled decade...
Copyright issues about what? Clicking a button? Yeah, dont remember who has that patent, isnt it Apple or was that NEC? :D
Seriously, what do you mean? NetBeans, UDK..?
We haven't checked for potential copyright issues have we? I doubt there could be any, but you never know in this troubled decade...
Copyright issues about what? Clicking a button? Yeah, dont remember who has that patent, isnt it Apple or was that NEC? :D
Seriously, what do you mean? NetBeans, UDK..?
(as we talked about on GoogleTalk) I'm just paranoid with companies like Apple copyrighting "clench-to-zoom" and what-have-you every single day now in a great never-ending war to own all innovation... Worst case scenario and they sue we just make it better :P
Updated the jMP to work with the latest NiftyGUI updates and the SceneViewer works again on MacOS (no audio crash).
Just start up jMP, ignore errors and a non-starting SceneViewer, go to Tools->Plugins and update your jMP (make sure you have the nightly jMonkeyPlatform repository enabled in the Settings tab).
I am interested to create a log-on screen for the start of a game application.
I open the JmonkeyEngin3 by JMonkeyPlatform, whatever change I made to HelloNiftyGUI.java and the corresponding hellojme.xml, it always shows me the hello world screen.
So Is it possible to have a basic set up tutorial of NiftyGUI on Jmonkeyplatform? (Or if there are any, please give me a note where it is).
Another thing is:
Once I update the Jmonkeyplatform to yesterday's version, the BasicGame template is missing (adding a new project, click JME, I could see JmeTest and BasicGame previously).
Appreciate you can help me solve my Nifty setup problem on JMonkeyPlatform.
NifyGUI support is planned but not integrated yet. You can create nifty xml files and edit them by hand, just right-click a node in the assetmanager and select "add new…" then select NiftyGUI xml.
