Re: pgScript patch

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Mickael Deloison <mdeloison(at)gmail(dot)com>, pgadmin-hackers(at)postgresql(dot)org
Subject: Re: pgScript patch
Date: 2008-08-12 18:00:16
Message-ID: 48A1CFB0.4030206@lelarge.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Dave Page a écrit :
> On Tue, Aug 12, 2008 at 3:39 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>
>> Ok, bad example. But I think you misunderstood the part about
>> "isolation", if that's what you mean with the part about separate.
>>
>> I mean, the vast majority of pgscript will not overlap with th vast
>> majority of pgadmin code. Thus, someone who's "just working on the
>> object tree" for example, will not be affected at all by integrating
>> pgscript.
>>
>> Whereas we should of course integrate them at all points where it's
>> reasonable, because that is likely to give a much better user experience.
>
> What you advocate there sounds to me like it should be integrated in
> the sense that it's part of our codebase, but isolated in it's own
> project and built as a DLL to be used by pgAdmin. Which in some ways
> gives us the best of both worlds, as Mickael could continue to
> maintain the code outside of the pgAdmin cycle, either directly on
> branches of the pgAdmin code, or by working on a copy from which we
> update the pgAdmin tree periodically.
>
> I actually kinda like that idea...
>

I also prefer the DLL idea. Not sure I understand the interest of
pgscript in pgAdmin, though...

--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message svn 2008-08-13 08:07:12 SVN Commit by dpage: r7401 - trunk/www/development
Previous Message Magnus Hagander 2008-08-12 17:46:50 Re: pgScript patch