Re: pgAdmin III commit: Database Designer (milestone 1 of GSoC 2011)

From: Luis Ochoa <ziul1979(at)gmail(dot)com>
To: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>, Dave Page <dpage(at)pgadmin(dot)org>, Guillaume Lelarge <guillaume(at)lelarge(dot)info>
Subject: Re: pgAdmin III commit: Database Designer (milestone 1 of GSoC 2011)
Date: 2011-06-29 18:55:58
Message-ID: BANLkTimxEpE=-BgmNaYpKzpdhEcoUCnurg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

On Wed, Jun 29, 2011 at 3:51 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:

> On Wed, Jun 29, 2011 at 3:16 AM, Luis Ochoa <ziul1979(at)gmail(dot)com> wrote:
> >
> > Well, I can change that class name, but when should I do that, now or
> > later?
> > which name can be used?
>
> Now would be better - I prefer not to leave the tree in a state where
> we know major restructuring is required for too long. Name-wise, I'd
> call the module "hotdraw", and prefix the class naes with "hd".
>

Well, I think "hotdraw" name standalone can be a problem because this is the
name of the original implementation, and that could lead to confuse
developers who work with source the code in the future, I suggest then
something hd only and the prefix will be hd too. What do you think about
this?

>
> >> Well, docs will be done at the end.
>
> End of what? If this is a milestone commit, then it presumably (I
> hope) encompasses some completed functionality - which really isn't
> complete until the docs are done. With the best will in the world,
> things left to the end of GSoC projects often don't get completed as
> planned, and I'd rather not see us end up with another cool, but
> undocumented feature.
>

Well I didn't write that sentence (following the thread) or anything about
writing docs at my project/proposal (or before), because I never got a
petition of doing that kind of things now or before, and they aren't
included at my schedule. But I can do that if someone tell me what Should I
do?.

>
>
>> I actually still hope we'll have
> >> another documentation system for next release, so docs will have to be
> >> reviewed completely.
>
> Yeah, I meant to ask you about that. I'd like to get that patch in
> early this cycle, as I want to spend some time on the docs myself.
> They're in dire need of an overhaul, and I'd rather not do it all in
> HTML. Yes, I am on a mission to sort out our crappy documentation.
>
>> And precomp.h, yeah, good catch. Forgot this one. Luis, can you update
> >> this file? Thanks.
> >>
> >
> > I'll do that and send you the patch.
>

Regards, Luis.

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2011-06-29 19:08:22 Re: pgAdmin III commit: Database Designer (milestone 1 of GSoC 2011)
Previous Message Guillaume Lelarge 2011-06-29 14:18:11 Re: configure "stuff"