@erlend_sh said:
Awesome work. Let us know if you run into any problems with the AssetPack creation. We'd love for more contributors to get into the habit of making Plugins and AssetPacks as a means to more effectively share their work with all jME3 users.
So I have some assets like shaders, materials, matdefs, textures and also some code. Now I wonder if should create an assetpack or a plugin...
Seemingly assetpacks can only place stuff into the Projects Assets folder, and not the Source Packages folder, is this correct? So using an assetpack would mean I place the code into Misc and require users to cut&paste that into their source folder.
An additional issue is that right now I'm working on a filter, and hence want to add a AbstractNewFilterAction. This means I need to create a plugin, doesn't it?
I also can't get asset preview working for my materials, it only works for models I presume? Also my attempt to add a dummy model using my materials with the electricity shaders in order to get a preview did not work out, for some reason it scrapped everything but the model, which then appeared invisible due to the missing stuff.
And while I'm at it: http://i.imgur.com/c5fMX.png
Another thing: How can I remove assets from the asset browser?
Now for plugins: I see that there's the Core-Data which has assets placed in it, as well as the jme3-test-data library mentioned in the Hello Assets tutorial, however adding that library to an project did not make textures and stuff appear in the sdk, so I wonder if there is a pain-free way for users to access assets in plugins like they can access stuff in assetpacks...?
Right now it seems the best way would be to split this contribution up into an assetpack containing the assets and a plugin containing the code and require users to download both to get them working, with no preview whatsoever besides the applets I released here. Is this the appropriate way?
For the dummy model to work the shaders would have to be accessible in the assetpack project under the right path as well. Also they would have to be copied along with the model then.
Yes, the AssetPack project support is pretty alpha still
Data cannot be accessed from other plugins, only classes. You can however access the ProjectAssetManager of both the AssetPack projects and the normal ones.
Yes, there would be no preview but people can add your assetpack items to their projects at least Another way would be to create a j2se library, so basically a jar library like the “jme3” one thats referenced for every BasicGame project. This way you could also update the shader in the plugin and peoples project would update as well as they only reference the jar with the shader…
maybe we could add custom filter support, like we have for custom controls. So there would be no need to create plugins for new Filters as long as they follow the bean standard, so you can list and edit its properties through reflection.
@nehon said:
1) maybe we could add custom filter support, like we have for custom controls. So there would be no need to create plugins for new Filters as long as they follow the bean standard, so you can list and edit its properties through reflection.
Probably yeah.. Question is how to get the instances.. Similar to the Controls I guess, by scanning the code..
I’m sorry to keep you waiting, but things didn’t exactly work out as I planned them and right now I’m learning for exams, once they are over I will continue tinkering with jme.
I just want to ask if you can release some of your ready shaders to public? We now have shaderBlow plugin in the JME and we can put your shaders to the ShaderBlow plugin where all users can use it directly.
What happened to Electricity5Material.java? The point of the 5th shader was to use layers, which was enabled through that class.
General explanations of the ideas behind the shaders:
Create lines. Modify those lines randomly.
Shader: Creates lines around the model using fresnel term.
Shader: Creates lines horizontally using vertex positions.
Shader: Creates lines using texture coordinates.
Shader: Creates lines by extracting value regions from blurred noise.
Shader: Creates lines like fur/grass shaders do using layers.
http://i.imgur.com/c5fMX.png
Another way would be to create a j2se library, so basically a jar library like the “jme3” one thats referenced for every BasicGame project. This way you could also update the shader in the plugin and peoples project would update as well as they only reference the jar with the shader…