I hope that you are going better. My mailbox just got the wonderfull
idea to get desync from pop so I just got 6000 mails duplicated :)
We will still have the following basic i-vars. These hold objects
need to be there in a valid object:
Structure: id, parent, properties
Resource: data, mimetype
I think properties should be optional and be inherited on the instance
side, e.g. if a component does not define a template or a storage the
one from the parent will be taken or the default one if nothing is
specified. In the current code the implementation of this behavior is
duplicated several times.
Another issue is the relation between the id and title. The id is
to the url from. Currently the title is generating a new id
automatically whenever it changes. This has got the advantage that the
url is always reflecting the page title, but there are also major
- changing the title breaks your bookmarks to the page
- titles have to be checked for validity (the id must be unique within
- special characters in titles make it hard to create links to that
pags, as they could be used in wiki *Title>Page*.
I did not really get it so you will explain us that.
I completely agree, the things that are needed to represent a page, a
chapter or a resource are still in i-vars. I don't think that every
component needs a title, so I would put this into the properties.
I'm not sure that title should not be a iv of page if page has to have
a title. There is a difference between an entity having a property and
all the entities.
Yes I think we could write some simple accessors for the most often
used properties like
and for the rest we would need to use
> But this means that we should have some way of creating method when
> you declare a new property and I do not like that. I prefer a static
If we don't want the static approach, my idea would be doing it highly
I would prefer to avoid that and do not mix meta stuff with the rest.
(aMessage args size = 0)
ifTrue: [ ^self propertyAt: aMessage selector ]
(aMessage args size = 1)
ifTrue: [ ^self propertyAt: aMessage selector put: aMessage args
> So could we discuss before you change everything in the point 3 above
> (move template, title, ivars to properties)?
I promised too much this morning: My headache has become worse and I
cannot work on the computer such a long time. So we will have some
more time to discuss and evaluate the possibilities :-)
Rest well. Computers can wait. I hope you will be ok to see ralph
Prof. Dr. Stéphane DUCASSE (ducasse(a)iam.unibe.ch)
"if you knew today was your last day on earth, what would you do
different? ... especially if, by doing something different, today
might not be your last day on earth" Calvin&Hobbes