13 Apr
2005
13 Apr
'05
1:10 p.m.
Hello Lukas,
hm, yes, but I think this might be a feature of general interest, because
the possibility to adapt the components when defining the description could
be important for many forms that will be created with Magritte in the
future. Otherwise, all the form elements are bound to have the same look
(width, height, alignment, etc.), and for forms that are a bit more complex,
e.g., with different text areas for different types of content, it might be
useful to adapt the look of the different form elements according to what
they represent.
I have developed a similar framework (in PHP, don't laugh ;) in the past,
and there the ability to customize the different form elements freely is
really crucial because we have to create many different and complex forms
with it.
Or how do you see the future of Magritte? I think it has a great potential
and the possibility to customize the components easily without subclassing
might come in quite handy.
Another issue currently is the customization of a description if it depends
on the instance of the structure. For instance, one would like to have
elements in a select list that are dependent on the instance of a structure
and that cannot be determined statically. As far as I understand the only
possibility to achieve that is to override #description on the
instance-side and to add the desired instance-dependent elements there. Or
am I mistaken here?
David
well what do you do with your all your div, span,
heading and anchor-tags?
There are blocks that are rendered all over the place :-)
yep, sorry, my bad, I have made a mess. ;)
Please submit a patch to SmallWiki2-Seaside, I just
didn't bothered to put
all those style-sheets and images into a style library class yet, it was
simply easier for me to edit the file in a css-editor.
yes, I see. I can add the styles to a library, no problem.
Similar problem as above: I suggest that you submit a
patch to the latest
SmallWiki2 package that fits your needs so that it can be merged into the
core code and everybody can profit.
ok, I can try.
It would be
great to have a method MAElementDescription >>
attributeAt:put:
to specify new attributes for the component of a description. Currently,
one
has to use #attributes which is not convenient.
Margritte is not a Seaside framework, generally speaking.
As far as I know there is just one use of #attributes: in SmallWiki itself
and as I don't write code that I don't need, I didn't felt the need for
such methods yet. However feel free to add them for your convenience,
that's the reason why there are class extensions ;-)