I agree with the idea of modularizing the UI components. However, what are your plans for addressing the GUI issues surrounding plugins?
I understand that all the Script-Fu stuff seems to use a generic dialog mechanism which shouldn't be a problem. The plugins which I'm concerned about are those which fall into the Filters category;
CML Explorer
Dynamic Text
Flame
Fractal Explorer
Gfig
Mosaic
... (there's a bunch more in this category)
Any thoughts on how this problem might be solved? Do we need a new SDK so that these types of plugins don't need to be written against a specific GUI toolkit?
For the record, the PRIMARY reason we were working on GeTK (a port of GTK+ for BeOS) was to allow us to port the GIMP for BeOS...
At the time it was started, I was under the impression that no one else was working on a port of the GIMP to BeOS. Our approach was to get a working version of GTK+ on BeOS so that we could leverage the ongoing development of the GIMP and it's plug-ins with minimal effort. Additionally, we planned to add extensions into the GeTK framework to allow for better integration into the BeOS application/desktop environment, thus minimizing the impact of using a non-native toolkit. We also planned to use themes to make the GIMP look more like the rest of the apps on the BeOS desktop...
EventLoop is taking an entirely different approach to porting the GIMP to BeOS. The only redundant effort was the fact that we were both trying to port the GIMP...
Slashdot Mirror
I agree with the idea of modularizing the UI components. However, what are your plans for addressing the GUI issues surrounding plugins?
I understand that all the Script-Fu stuff seems to use a generic dialog mechanism which shouldn't be a problem. The plugins which I'm concerned about are those which fall into the Filters category;
Any thoughts on how this problem might be solved? Do we need a new SDK so that these types of plugins don't need to be written against a specific GUI toolkit?
For the record, the PRIMARY reason we were working on GeTK (a port of GTK+ for BeOS) was to allow us to port the GIMP for BeOS...
At the time it was started, I was under the impression that no one else was working on a port of the GIMP to BeOS. Our approach was to get a working version of GTK+ on BeOS so that we could leverage the ongoing development of the GIMP and it's plug-ins with minimal effort. Additionally, we planned to add extensions into the GeTK framework to allow for better integration into the BeOS application/desktop environment, thus minimizing the impact of using a non-native toolkit. We also planned to use themes to make the GIMP look more like the rest of the apps on the BeOS desktop...
EventLoop is taking an entirely different approach to porting the GIMP to BeOS. The only redundant effort was the fact that we were both trying to port the GIMP...
:-l