Guys, let me introduce Chris Huf to you, our latest SDR developer and the 3rd Chris in the club. He did an awesome job in creating this Standalone Editor. Download it right now, and drool over the opportunities. I really believe, this piece will put our little project on the map, its the missing puzzle piece for using SDR in a production environment.

Welcome and the editor looks very good and clean. Havenīt had time to try it more yet though.

But one suggestion from an interface designers point of view: I know dark interfaces are "en vogue" currently, but actually itīs the most horrible thing you can do. Itīs the worst thing for users eyes. So Iīd really like to see a way to at least change the interface color.

We also should think about using chris'browser as kind of keyapplication of all plugins:When a loaderscript/plugin of any 3d app try to load an sdr, it could open first the browser and inside the browser we let the user select the sdr and "send" the sdr and all the maps to the 3d app.On every 3D app you have then the same browser to select an sdr. We then have to script the I/O part or at least a kind of workaround like a global "send to" folder.

I'm talking about workarounds because I don't know any way to receive variables from an application with (3ds)maxscript, but i could write a callback handler which traces a defined folder for new content and then load the new content to the 3d app as new SDR.

btw, when i open sdr's with a wrong Syntax for the bitmapname (missing quotes)it gives me an error. I want to suggest a kind of autocorrection, which simply corrects the syntax and let it open in the browser.

Sorry, but I have to strongly oppose. All of us have a working browser already, and they actually do look similarto each other. Personally, I do not want to start an external app just for browsing, I prefer a browser that has the UI look and feel of the host application. The SDR-Editor is kind of special in doing the authoring job. Our Importer Plugins should concentrate on the actual setup, and be otherwise dumb.

But I can see where you are coming from.You like the extra functionality of Chris's Browser. So do I. But I would rather have simple commandline utilities, that allow me to access these functionalities right out of my plugin. Let's say, calling Code:

SDREdit -l"folder/mysdr.sdr"

in a commandline would open up the Editor with that SDR loaded, then I could put that on a button. Another commandline option could be: Code:

We also should think about using chris'browser as kind of keyapplication of all plugins:

Disagree because:- You would sacrifice a certain cross platform compatibility you've created by doing it with scripts- Startup time slowdown... (plus the fact sdrEdit isn't very memory friendly)

Quote:

btw, when i open sdr's with a wrong Syntax for the bitmapname (missing quotes)it gives me an error. I want to suggest a kind of autocorrection, which simply corrects the syntax and let it open in the browser.