From: Stefan S. <ss...@ge...> - 2012-02-13 21:04:50
|
Hei Benjamin, I was actually not talking about the internal plugins but all the Extensions that we have in the plugin section listed... and I guess a couple of people also developed their own... like SkyJUMP & AdbToolbox ones. Is Cinema4D browser-based? couldn't find anything on that when I shortly browsed. Because I think if we do something new, then it should go towards a web browser-based application... anyway.. no resources there for now ;) stefan On 13/02/2012 2:44 AM, Benjamin Gudehus wrote: > 2012/2/13 Stefan Steiniger <ss...@ge... <mailto:ss...@ge...>> > > btw. Not saying that shouldn't break backward compatibility. > However, that would be then OJ 2.0 if we are going to clean up > everything and really seperate GUI from api etc more strict. > Though.. we > have sooo many plugins... > > > If we go through all plugins that make use of MultiInputDialog (I > count 63 plugins) and > prepare them systematically by writing unit tests and list all dialog > fields as class fields, > then I think it's the matter of one single commit to convert them all > for a new api. > > A dream of mine would be to come up then with a complete new > browser-based & HTML 5 based GUI (on Firefox?). But that's a > dream, and > would need a year of development I guess... So I rather concentrate on > writing documentation for now. > > > HTML5 guis are a bit overrated. First we would need to build a second > API between > the JTS and OpenJUMP API (Feature, Layer, LayerManager) and the HTML5 web > application. With second API I mean a RESTful web service. > > I personally think the next gen OpenJUMP "desktop" gui could look like > this: > http://www.maxon.net/uploads/pics/CINEMA_4D_Screenshot4_04.jpg > > (Instead of Perpective => LayerViewPanel, Objects tab => Layers tab, > Structure tab => Selection tab, Attributes tag => Feature attributes tab, > Materials view => Layer styles view.) > > And we need to split the toolbar into two toolbars (main toolbar and > cursor tools toolbar)! > > There could be a classic view mode, too. With the simple > LayerNamePanel on the > left side and LayerViewPanel on the right side. > > |