[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNUe-dev] GCD samples
From: |
chafar |
Subject: |
Re: [GNUe-dev] GCD samples |
Date: |
Sun, 13 Jun 2004 01:50:28 +0200 |
User-agent: |
Mutt/1.3.28i |
Hello.
El sáb, jun 12, a las 11:59:38 Jason Cater escribía:
> I have two questions/concerns with the GCD format.
>
> <property name="code" type="string(3)" ...>
>
> Why have type= be a composite attribute, instead of having two separate
> attributes: type="string" size="3" ?
>
> The only reason I ask is this would really complicate creating any design
> tools (a GNUe Designer module, etc), as then you can't just have simple
> controls, like a Combo Box with (string|number|...) and an edit field for the
> sizes.
You'll be able to do so, because there is another attribute, @length,
that works as you want.
>
> Also,
>
> <property name="upd" type="UPDATE_Update" />
>
> Seems to me that you're only asking for trouble later on by having the
> type=".." serve two functions, one being a static list of data types and the
> other being a referenced field. It might make more sense to have "type=" be a
> limited, controlled list (like type="string|number|reference") and adding
> another attribute for the referenced properties; i.e., the example above
> would be:
>
> <property name="upd" type="reference" reference="UPDATE_Update" />
>
> Maybe "reference" isn't the ideal keyword to use, but I having dug deep into
> the appserver terminology yet.
I like the way it's done. From SQL point of view, your suggestion is
clean, but from an oo pespective, it's right as is.
For the purpose of designer tool, if a way to build a list of available
classes were found, you could add them to the list of 'native' types for
the dropdown list on @type, but this leads yout into other problems.
Still, I think that we are talking about geas *classes* and, so, the oo
orientation should be preserved.
>
> These are my only two concerns wrt being able to do a GNUe Designer module,
> and to be able to take better advantage of existing integrity tools.
>
> -- Jason
>
On my own, what I don't understand is the meaning of a class/@module
attribute, because class element is inside a module element: what is
this other module?
And, though it is nearly irrelevant, may be @comment should be named
@description, following gnue-schema's @description attr names.
>
>
> On Wednesday 09 June 2004 05:53 pm, kilo wrote:
> > Hi
> >
> > I have created some new sample GCD files based on gnue-packages and
> > Hungarian "common logic".
> >
> > They can be viewed at http://www.gnuenterprise.org/~kilo/newGCD where
> > you will find GCD files (with extension '.txt', that should be cut off
> > in production) and corresponding Dia and PNG files.
> >
> > Please check and review them, I would be glad to hear your opinion.
> >
> > kilo
> > Gabor Kmetyko
> >
> >
greetings
--
José Esteban
Granada - Spain
http://alcances.net