since I at least hope that there will be some user-contributed plugins for jMP I thought it might be easier to collect them all in one update center so users can install them from one place. Also, external libraries etc. can be wrapped into plugins for easy installation and updating.
So I have created a googlecode project for such plugins which will be automatically compiled, version-labeled and added to the contributions update center like the core jMP plugins. The first plugin I added myself is Collada-Support for jMP via pgiâs great collada importer.
I was able to extract just the GLSL editor from http://kenai.com/projects/netbeans-opengl-pack and added it to the contrib update center. This means code highlighting, error checking and code completion for glsl frag/vert files in jMP!
and will there be quick manual for eclipse users ?
I dont think I will find the time to do the research on how to create NetBeans plugins in Eclipse soon, but in theory it should work by downloading a generic netbeans 6.9 install and importing the libraries etc.. Still, I think doing it in jMP or NetBeans makes way more sense as the support for the management of configuration files, creating new components, actions etc. is of course far better.
Cheers,
Normen
By the way, has anyone been able to install the GLSL editor plugin? It does not seem to like JMP alpha 2 or Netbeans 6.9 either (in 6.8 it works fine). There is something wrong with an Editor Library plugin version.
By the way, has anyone been able to install the GLSL editor plugin? It does not seem to like JMP alpha 2 or Netbeans 6.9 either (in 6.8 it works fine). There is something wrong with an Editor Library plugin version.
The one in the jMonkeyPlatform contributions update center works fine for me.
By the way, has anyone been able to install the GLSL editor plugin? It does not seem to like JMP alpha 2 or Netbeans 6.9 either (in 6.8 it works fine). There is something wrong with an Editor Library plugin version.
I had a similar problem, when i installed the alpha 2 the first time.
It was because i had the editor plugin installed on the alpha1.
I resolved the problem by deleting my previous settings (there is a check box in the installation to do it)
Maybe you should give it a try
I have done that and the problem has been solved. Thank you!
In the regular netbeans version happens the same. I upgraded recently from netbeans 6.8 to 6.9 (in this case for work) and there is the same issue with that plugin in 6.9 (in this case the kenai version).
Holger Dammertz, the author of NeoTextureEditor was very cooperative and I managed to make a jMP plugin out of his fantastic tool:
This is not all⌠Since the tool is also a library to generate textures on the fly I am working on a jME3 material loader that can load the NeoTexture .tgr files directly as a jME3 material, dynamically generating the textures! 8)
Available now through the jMP contributions update center.
If you update the plugin you will get a new library in jMP. Go to the projects properties and add the âNeoTexture-Librariesâ library.
To use it first create a new tgr file and edit it. In the properties field of any image node, enter the name of the texture as it would appear in a j3m file, like âm_ColorMapâ for SimpleTextured.j3md. Save the file.
Now open your Main.java file and the Palette (Window->Palette) and you will see two presets in the palette for adding the loader to the assetManager and for loading a material. Drag&Drop them both to the initialize() method of your Application, correct the MaterialDef and tgr file path names to your desire and youâre ready to load your procedural material
:!: Bitmap textures are not supported yet, only procedural ones!
There is also a TextureLoader for tgr files but its not fleshed out yet, it should be integrated so that tgr files can be used as texture names in j3m files or something similar.