Re: [Gimp-developer] easy questions
The second is, I haven't looked at the code at all, but is the GIMP multithreaded and/or does it absolutely require a multitasking OS? You won't be able to use any plugin without a multitasking OS... I think what the OP really meant to ask whether GIMP requires a *pre-emptively* multitasking OS. I.e. one that can interrupt a running process that has exceeded its timeslice, even if it doesn't do any system calls (or similar) that gives the kernel a chance to let another process have the CPU. (For instance, Windows 3.1 wasn't able to do that.) As far as I can guess, sure, GIMP might work on such a system... as long as it has other functionality that GIMP and GTK needs. That's the main problem, not having pre-emptive multitasking would to me indicate there's a good chance that the OS is very lacking in other respects, too. --tml ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] easy questions
Hi, Tor Lillqvist [EMAIL PROTECTED] writes: I think what the OP really meant to ask whether GIMP requires a *pre-emptively* multitasking OS. I.e. one that can interrupt a running process that has exceeded its timeslice, even if it doesn't do any system calls (or similar) that gives the kernel a chance to let another process have the CPU. (For instance, Windows 3.1 wasn't able to do that.) As far as I can guess, sure, GIMP might work on such a system... I don't think GIMP plug-ins would work w/o proper multitasking and using GIMP w/o plug-ins doesn't make too much sense. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] easy questions
On 9 Jul 2004, Sven Neumann wrote: Hi, Tor Lillqvist [EMAIL PROTECTED] writes: I think what the OP really meant to ask whether GIMP requires a *pre-emptively* multitasking OS. I.e. one that can interrupt a running process that has exceeded its timeslice, even if it doesn't do any system calls (or similar) that gives the kernel a chance to let another process have the CPU. (For instance, Windows 3.1 wasn't able to do that.) As far as I can guess, sure, GIMP might work on such a system... I don't think GIMP plug-ins would work w/o proper multitasking and using GIMP w/o plug-ins doesn't make too much sense. Hmm, I'm confident you could get it to work on a cooperative multitasking system. You might need to add a yield() into the glib loop, but no big deal. Of course, it wouldn't work *well*, but then again cooperative multitasking never does. Rockwalrus ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] easy questions
Hi Zack, Quoting Zack [EMAIL PROTECTED]: The first is, how intimately is the GIMP tied to GTK+? Very. Although the GUI code has been separated out from the internals, the GIMP depends on GTK+ to a huge extent. It is inextricably linked to glib and gobject too. The second is, I haven't looked at the code at all, but is the GIMP multithreaded and/or does it absolutely require a multitasking OS? I wouldn't say so. I don't believe there is threading code in the GIMP, but I am not sure. Cheers, Dave. -- Dave Neary Lyon, France ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] easy questions
On Wed, Jul 07, 2004 at 10:06:58AM +0200, David Neary wrote: Hi Zack, Quoting Zack [EMAIL PROTECTED]: The first is, how intimately is the GIMP tied to GTK+? Very. Although the GUI code has been separated out from the internals, the GIMP depends on GTK+ to a huge extent. It is inextricably linked to glib and gobject too. The second is, I haven't looked at the code at all, but is the GIMP multithreaded and/or does it absolutely require a multitasking OS? I wouldn't say so. I don't believe there is threading code in the GIMP, but I am not sure. You won't be able to use any plugin without a multitasking OS... Regards, DindinX -- [EMAIL PROTECTED] Celibacy is not hereditary ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] easy questions
Hi, Quoting David Odin [EMAIL PROTECTED]: The second is, I haven't looked at the code at all, but is the GIMP multithreaded and/or does it absolutely require a multitasking OS? You won't be able to use any plugin without a multitasking OS... Won't the plug-in just become modular over the main app? Oh, no - we use shared memory, so the two apps need to be running at the same time... Dave. -- Dave Neary Lyon, France ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] easy questions
Hi, Zack [EMAIL PROTECTED] writes: I have a couple basic questions for the people who know the GIMP code well. The first is, how intimately is the GIMP tied to GTK+? Most of the core code (but none of the plug-ins) has a clean separation of the GUI from the core functionality. However since a good deal of code is GUI code I'd say it is quite intimate with GTK+. The second is, I haven't looked at the code at all, but is the GIMP multithreaded and/or does it absolutely require a multitasking OS? Thank you... It makes use of multi-threading if compiled with the --enable-mp flag and however it is compiled, it absolutely needs a multitasking OS. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
