29 Nov
2005
29 Nov
'05
11:36 p.m.
It is definitely not a conversion method, the
resulting
description is completely independent from the receiver of
the message: it can be recomposed, reused with or without any
other model instance. What is more, have you ever seen an
#asClass conversion method to ask your instance for its
meta-representation (#class)?
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
Hmm.. that's a good point. My inclination is to toss the word meta in
there somewhere, it is after all metadata, but you already said you were
avoiding that. It's not that big a deal I guess, I just wanted to raise
the issue since it was a problem for me. I still think description is
far to useful an accessor in "any" problem domain to use it as an
extension on Object, I'd at least call it descriptor, but I'm not
complaining. I love the framework man, keep up the great work, I check
for updates daily and have learned quite a bit about Smalltalk style
from reading your code.
30 Nov
30 Nov
12:28 a.m.
New subject: Magritte Validation Error
It's not that big a deal I guess, I just wanted to
raise
the issue since it was a problem for me. I still think description is
far to useful an accessor in "any" problem domain to use it as an
extension on Object, I'd at least call it descriptor, but I'm not
complaining.
Sure, I am open for discussion on any part of the framework. I see
that we should try to reduce conflicts as much as possible and having
extensions in Object naturally lead to such troubles (unless we have
something like class-boxes).
I think #descriptor would be a nice name as well, but I am not sure
if it is worth the troubles of a rename: there is already a lot of
existing code built on top of Magritte (at netstyle.ch we are using
Magritte in productive systems since april 2005) and I know software
(have a look at OmniBrowser), that would conflict with #descriptor
but does not with #description ... ;-)
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
5 Dec
5 Dec
9:14 p.m.
New subject: Autofocus
Anyone know what happened to autofocus on magritte descriptions? With this gone, how are
you currently putting the cursor in the first field when an edit form appears?
6 Dec
6 Dec
10:42 a.m.
New subject: Autofocus
Anyone know what happened to autofocus on magritte
descriptions?
With this gone, how are you currently putting the cursor in the
first field when an edit form appears?
I removed it.
The problem was basically because there is no good place to put this
property and the following problems:
- you could have multiple descriptions within the same form where
auto-focus was set to true, especially when composing descriptions at
runtime from several different sources.
- #autofocus: did not work with some more complex form-elements like
one-to-one, one-to-many, multiple-selection, ...
- when changing from WAHtmlRenderer to WACanvasRenderer there was no
replacement for the method #autofocus:, however this could be easily
added again.
- I felt that is unnecessary to have #autofocus: in the description
itself, if you really need to automatically focus an element you
probably do a sophisticated manual rendering anyway.
- proper separation of view and meta-model, something Stéphane
Ducasse and I just recently discussed: a problem in the current
version of Magritte is that I mix meta-stuff and Seaside/Morphic
configuration, such as #componentClass:, #attributes, #morphicClass,
#autofocus: ... this should be the responsibility of a different
object, not the description itself. It leads to some hard to tackle
problems with extension-methods, if you want to use descriptions with/
without different view-implementations, however it is not easy to
solve. Maybe something for Magritte 1.1 ;-)
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
6955
days inactive
6962
days old
3 comments
2 participants
participants (2)
-
Lukas Renggli -
Ramon Leon