Rickard Edén

I think this is related to #561

Not sure. I may have gotten the idea from the material or shader editor. Properties in general aren't manipulated that much except for spatials and filters.

This is the particular widget that is used: [FloatPanel](https://github.com/jMonkeyEngine/sdk/blob/cd2fb05b8c2a227c2617d96a61440bab63376d3d/jme3-materialeditor/src/com/jme3/gde/materials/multiview/widgets/FloatPanel.java#L19) There's also a smaller one I made for the Shader editor: [FloatPanelSmall](https://github.com/jMonkeyEngine/sdk/blob/cd2fb05b8c2a227c2617d96a61440bab63376d3d/jme3-materialeditor/src/com/jme3/gde/materials/multiview/widgets/FloatPanelSmall.java)

Although there is no reference to it in the stacktrace, I guess it's related to ExternalChangeScanner? Are there other instances listening for asset changes? I made some changes to it...

I've written this for my own project. Maybe it could be leveraged.

Here's what I could find. It's been a while, so I'm not sure if everything is is used. It doesn't download jre's by itself. Those I downloaded manually. There are...

Its actually using launch4j. I believe I opted for not bundling the jre in the exe though

Some further usage revealed there is the function in the scenecomposer window to create a (i assume) MeshCollisionShape. It'll work for most use cases, I guess. I'll leave this open...

I think it might be this one: https://github.com/emilianbold/maven.search.remote

Sadly not, it seems. The message "No sources for xx:x available" is displayed, but nothing happens.