I understand (about the good architecture). It should be designed carefully to support all the sources (I was aware only of the plug-ins). Does this object model you use for C allows inheritance? About the preview calculations. I was thinking that it might be faster to pre-calculate all the plug-ins/core/GEGL on 2-3 fixed sample images [300x300] (ex. an apple, a person, a building and a sunset) and store them on the user's machine. Each time he opens this feature browser, if there is a new feature without a sample image, it'll be calculating it and storing it on hard disk. It should still happen in a separate thread of course but I think it would speed up things. What do you think about it? Avgoustinos On Sat, Apr 10, 2010 at 11:00 AM, Martin Nordholts <enselic@xxxxxxxxx> wrote: > On 04/10/2010 11:26 AM, Avgoustinos Kadis wrote: >> Hello, >> >> I'm an applicant for GSoC 2010. I got inspired by the "menu search" >> idea and proposed the "user friendly plug-in browser" that would allow >> users to find the plug-in they want by seeing the effect on an example >> image. The whole thing is to browse through images rather than through >> text. The reason is that the names of plug-ins say nothing to many of >> the users (including me) and they hesitate to try them. But by seeing >> the effect of the plug-in they will be more willing to use it. >> >> Could you please give me some feedback on my proposal? I would like to >> know if this idea is feasible. Are there any aspects I didn't think >> of? > > The idea makes complete sense and has been discussed every now and then. > There are a couple of requirements that a design would have to fulfil: > > * The preview calculations needs to support different sources, most > notably GIMP legacy core, plug-ins, and GEGL, so a good architecture is > necessary > > * Preview calculations needs to be done in a lazy on-demand manner to > make the UI responsive. That is, preview calculations needs to happen > outside of the UI thread so one can browse around freely without being > forced to wait for previews to finish rendering > > / Martin > > > > -- > > My GIMP Blog: > http://www.chromecode.com/ > "GIMP 2.8 development still under control" > _______________________________________________ > Gimp-developer mailing list > Gimp-developer@xxxxxxxxxxxxxxxxxxxxxx > https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer > _______________________________________________ Gimp-developer mailing list Gimp-developer@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
