Re: [Gimp-developer] GIMP Developer Meeting #3 - March 28, 2011

2011-03-29 Thread gespert...@gmail.com
> On 2011-03-29 14:09, LightningIsMyName wrote: >> ** Default JPEG Quality (quickie, not a real topic) ** >> Change to 95 2x1, and add a hack to save defaults (using something >> like the PNG plugin does, or something more elegant). Note that a >> decent system to save plugin defaults, along with o

Re: [Gimp-developer] GIMP Developer Meeting #3 - March 28, 2011

2011-03-29 Thread Alexandre Prokoudine
On 3/29/11, Michael Natterer wrote: > On 03/29/2011 06:54 PM, Alexandre Prokoudine wrote: >> On 3/29/11, Michael Natterer wrote: >> >>> As I said before, let's please work on our public interface >> >> Let's try to outline what exactly needs doing, eh? :) > > - Website updates I think I could add

Re: [Gimp-developer] GIMP Developer Meeting #3 - March 28, 2011

2011-03-29 Thread Michael Natterer
On 03/29/2011 06:54 PM, Alexandre Prokoudine wrote: > On 3/29/11, Michael Natterer wrote: > >> As I said before, let's please work on our public interface > > Let's try to outline what exactly needs doing, eh? :) - Website updates - News - Wiki - Blogs - Maybe we should have a GIMP blog aggregator

Re: [Gimp-developer] GIMP Developer Meeting #3 - March 28, 2011

2011-03-29 Thread Alexandre Prokoudine
On 3/29/11, Michael Natterer wrote: > As I said before, let's please work on our public interface Let's try to outline what exactly needs doing, eh? :) The new website is stuck in the middle mostly because AFAIK Jimmac was busy all the time with GNOME 3 which is finally soon to be out, so maybe

Re: [Gimp-developer] GIMP Developer Meeting #3 - March 28, 2011

2011-03-29 Thread Michael Natterer
On 03/29/2011 02:45 PM, Martin Nordholts wrote: > 2011/3/29 LightningIsMyName: >> ** Re-Discussing GIMP's programming language ** >> For core (non-UI), continue using GObject, use code generators (such >> as turbine) and do copy/paste/replace for existing GObject classes >> (for the rare case where

Re: [Gimp-developer] GIMP Developer Meeting #3 - March 28, 2011

2011-03-29 Thread Ville Pätsi
On 2011-03-29 14:09, LightningIsMyName wrote: > ** Default JPEG Quality (quickie, not a real topic) ** > Change to 95 2x1, and add a hack to save defaults (using something > like the PNG plugin does, or something more elegant). Note that a > decent system to save plugin defaults, along with other a

Re: [Gimp-developer] GIMP Developer Meeting #3 - March 28, 2011

2011-03-29 Thread Martin Nordholts
2011/3/29 LightningIsMyName : > ** Re-Discussing GIMP's programming language ** > For core (non-UI), continue using GObject, use code generators (such > as turbine) and do copy/paste/replace for existing GObject classes > (for the rare case where the generator won't be enough). Hi, Unfortunately

Re: [Gimp-developer] GIMP Developer Meeting #3 - March 28, 2011

2011-03-29 Thread LightningIsMyName
Hello, no organized meeting log this time, for various reasons, however I'm attaching below the list of decided actions in the meeting, along with some other off-topic points that were discussed: ** GSoC Student Applications ** Core developers sign up as mentors (for GSoC) schumaml: Write mail a

Re: [Gimp-developer] GIMP Developer Meeting #3 - March 28, 2011

2011-03-28 Thread LightningIsMyName
Hello On Mon, Mar 28, 2011 at 6:27 PM, Kevin Cozens wrote: > > It's a good thing I asked that we clarify the problem as I was thinking it > was something else entirely. Pointers to a couple of files that show the > issue of a lot of boilerplate code would be good so we can all see the > extent of

Re: [Gimp-developer] GIMP Developer Meeting #3 - March 28, 2011

2011-03-28 Thread Kevin Cozens
Alexandre Prokoudine wrote: > It has *something* to do with too much gobject boilerplate code. It's a good thing I asked that we clarify the problem as I was thinking it was something else entirely. Pointers to a couple of files that show the issue of a lot of boilerplate code would be good so we

Re: [Gimp-developer] GIMP Developer Meeting #3 - March 28, 2011

2011-03-28 Thread Simon Budig
Martin Nordholts (ense...@gmail.com) wrote: > 2011/3/27 Michael Natterer : > > And this is *exactly* the problem. We would end up with programmers > > that quickly learnt vala, having no clue about GObject. That's > > absolutely horrible. > > How is it a problem that our code becomes so easy that

Re: [Gimp-developer] GIMP Developer Meeting #3 - March 28, 2011

2011-03-28 Thread Alexia Death
On Mon, Mar 28, 2011 at 10:26 AM, Martin Nordholts wrote: > How is it a problem that our code becomes so easy that even "dumb" > programmers can understand and improve it when we are not forced to > include patches from such "dumb" programmers? This not how I understood mitch... I understood it as

Re: [Gimp-developer] GIMP Developer Meeting #3 - March 28, 2011

2011-03-28 Thread Martin Nordholts
2011/3/27 Michael Natterer : > On 03/27/2011 04:45 PM, Martin Nordholts wrote: >> >> On 03/27/2011 02:12 PM, Michael Natterer wrote: >>> >>> As to the actual iussue of introducing whatever *additional* >>> language in GIMP, I strongly doubt that it would help us in >>> any way. It would increase th

Re: [Gimp-developer] GIMP Developer Meeting #3 - March 28, 2011

2011-03-27 Thread Michael Natterer
On 03/27/2011 04:45 PM, Martin Nordholts wrote: > On 03/27/2011 02:12 PM, Michael Natterer wrote: >> >> As to the actual iussue of introducing whatever *additional* >> language in GIMP, I strongly doubt that it would help us in >> any way. It would increase the complexity of both building and >> pr

Re: [Gimp-developer] GIMP Developer Meeting #3 - March 28, 2011

2011-03-27 Thread Aurimas Juška
Hi, On Sun, Mar 27, 2011 at 3:12 PM, Michael Natterer wrote: > So when you write code, how much time do you spend writing the > boilerplate? 10%? I would say it's much much less, because writing > the code is a small fraction of the time actually spent on the code, > the rest is debugging, refact

Re: [Gimp-developer] GIMP Developer Meeting #3 - March 28, 2011

2011-03-27 Thread Martin Nordholts
On 03/27/2011 02:12 PM, Michael Natterer wrote: > > So when you write code, how much time do you spend writing the > boilerplate? 10%? I would say it's much much less, because writing > the code is a small fraction of the time actually spent on the code, > the rest is debugging, refactoring, readin

Re: [Gimp-developer] GIMP Developer Meeting #3 - March 28, 2011

2011-03-27 Thread Michael Natterer
On 03/27/2011 11:36 AM, Martin Nordholts wrote: > 2011/3/27 Kevin Cozens: >> LightningIsMyName wrote: >>> *** Optional topic: Re-Discussing GIMP's programming language *** >>> Some developers that weren't present in the last meeting, highly >>> disagree on the attempt to introduce vala into gimp, c

Re: [Gimp-developer] GIMP Developer Meeting #3 - March 28, 2011

2011-03-27 Thread Martin Nordholts
2011/3/27 Kevin Cozens : > LightningIsMyName wrote: >> *** Optional topic: Re-Discussing GIMP's programming language *** >> Some developers that weren't present in the last meeting, highly >> disagree on the attempt to introduce vala into gimp, claiming that it >> will scare off developers (more th

Re: [Gimp-developer] GIMP Developer Meeting #3 - March 28, 2011

2011-03-26 Thread Alexandre Prokoudine
On 3/27/11, Kevin Cozens wrote: > Before talking about which new programming language is needed(?) in GIMP we > should make sure the problem is clearly defined as to *why* we need > something new. What problem is the new language going to solve? > > IIRC, it had something to do with creation of GU

Re: [Gimp-developer] GIMP Developer Meeting #3 - March 28, 2011

2011-03-26 Thread Kevin Cozens
LightningIsMyName wrote: > *** Optional topic: Re-Discussing GIMP's programming language *** > Some developers that weren't present in the last meeting, highly > disagree on the attempt to introduce vala into gimp, claiming that it > will scare off developers (more than the "simple" C GObject code)

Re: [Gimp-developer] GIMP Developer Meeting #3 - March 28, 2011

2011-03-25 Thread Martin Nordholts
On 03/25/2011 02:31 PM, LightningIsMyName wrote: > *** Other topics *** > Any other suggestions should be suggested by replying to this email, > or adding it directly to the wiki (if you have permissions to edit the > wiki). Hi, What's the status of making wiki.gimp.org resolve to gimp-wiki.who.e