9 Dec
2005
9 Dec
'05
10:09 a.m.
I think I will be interested in specific descriptions and before trying
to code them or whatever else, here are what I need... Mostly here to
discuss on solutions to do that without "breaking" Magritte ;)
- will it be good to have something like a nested descriptions
(MANestedContainer ??). I have to represent event and according to the
type of event (human or natural), the option list is different. How to
you do that ? using a nesting container (that doesn't exist yet) or
using two descriptions with maybe a MADynamic object for the second
description linked to the first one...
- second point, I will probably need to represent a "physical"
measurement (with a unit or an intensity). Units or descriptions of
intensity can be different according to what is measured. So here, what
would you do ? using nested description ? What about creating a
MAMeasurementDescription but if so, will it be a subclass of
MAElementDescription and then MAMagnitudeDescription or will it be a
subclass of MAContainer or even of MADescription ?
Thanks
Cédrick
9 Dec
9 Dec
10:53 a.m.
Hi Cédrick,
- will it be good to have something like a nested
descriptions
(MANestedContainer ??). I have to represent event and according to
the type of event (human or natural), the option list is different.
How to you do that ? using a nesting container (that doesn't exist
yet) or using two descriptions with maybe a MADynamic object for
the second description linked to the first one...
we have built a nested list at netstyle.ch using Magritte: the model
is basically a tree where you have to select one of the leaves. The
GUI looks like the column-view of the finder in OS X. Is that what
you want? Else maybe the OneToOneRelationshipDescription with
different classes could be a possibility?
- second point, I will probably need to represent a
"physical"
measurement (with a unit or an intensity). Units or descriptions of
intensity can be different according to what is measured. So here,
what would you do ? using nested description ? What about creating
a MAMeasurementDescription but if so, will it be a subclass of
MAElementDescription and then MAMagnitudeDescription or will it be
a subclass of MAContainer or even of MADescription ?
The first thing you need is probably the model, what is presumably a
subclass of Magnitude. Then you can code (like MANumberDescription) a
new description for your model. I once did something similar at
netstyle.ch for currencies.
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
1:47 p.m.
New subject: questions about descriptions AND MANumberDescription
Hi Lukas :)
we have built a nested list at netstyle.ch using
Magritte: the model
is basically a tree where you have to select one of the leaves. The
GUI looks like the column-view of the finder in OS X. Is that what
you want? Else maybe the OneToOneRelationshipDescription with
different classes could be a possibility?
I'll try to do that way... thanks ;)
The first thing you need is probably the model, what is presumably a
subclass of Magnitude. Then you can code (like MANumberDescription) a
new description for your model. I once did something similar at
netstyle.ch for currencies.
Ok I see... still the model ;) I'll try this week-end and I'll give
feedback when done...(or not :))
So just another question as we are talking of MANumberDescription and as
I'm playing with it :d
What I'm triing to do is providing instead of a text input component a
List choice where there is a collection of number between min and max
according to a given step... (10 20 30 40...). What would be the better
? creating a MANumberListComponent that display the list... or adding
functionality in MANumberComponent...?
Also, I see that the default component for MANumberComponent are
MAInputText and MARangeComponent but I cant really get how the
MARangeComponent is used (called when defining the MANumberDescription).
is it: (MANumberDescription auto: ... label: ... priority..)
componentClass: MANumberDescription
defaultComponentClasses second; (is it how we acces it ??)
yourself.
I actually don't really understand how MARangeComponent works, is it for
a javascript check ?
2:34 p.m.
New subject: questions about descriptions AND MANumberDescription
So just another question as we are talking of
MANumberDescription
and as I'm playing with it :d What I'm triing to do is providing
instead of a text input component a List choice where there is a
collection of number between min and max according to a given
step... (10 20 30 40...). What would be the better ? creating a
MANumberListComponent that display the list... or adding
functionality in MANumberComponent...?
Yeah, create a new view such as MANumberComponent/MARangeComponent.
Also, I see that the default component for
MANumberComponent are
MAInputText and MARangeComponent but I cant really get how the
MARangeComponent is used (called when defining the
MANumberDescription).
is it: (MANumberDescription auto: ... label: ... priority..)
componentClass: MANumberDescription
defaultComponentClasses second; (is it how we acces it ??)
yourself.
I usually code directly the component class:
(MANumberDescription auto: ...)
componentClass: MARangeComponent;
yourself.
However, as I already mentioned in a previous mail, this imposes a
strong coupling between the description and the view (e.g., if you
have a model package with some descriptions and different view
packages that all want to specify their own view-components). I don't
know how we could solve that problem right now, so do it as you
suggested ;-)
I actually don't really understand how
MARangeComponent works, is
it for a javascript check ?
Yeah, that is a control displaying a slider. It is currently only
working in Safari and probably KHTML, because it builds on top of
proposal to extend HTML that is not in the standard yet. It should
however safely degenerate to a normal text-input if your browser
doesn't support it.
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
7015
days inactive
7015
days old
3 comments
2 participants
participants (2)
-
Cdrick -
Lukas Renggli