25 Feb
2008
25 Feb
'08
1:02 a.m.
Sorry to reshash the subject but part of the problem has to do with
the multiple versions (thumbnaills, etc) of a file that I mentioned
briefly in the Seaside list.
i went to subclass MAFileModel but realized that because I was using a
memory representation in development to make things easier to test and
an external representation in development, I'd have to choose to
subclass only one and use it always.
Maybe I should not be bothered so much but I wondered if it wouldn't
be more interesting to keep the memory and external representations
similar.
But I was thinking about it after I sent the e-mail and maybe it would
be more interesting to write a new type of description to handle that.
I don't know, however, how that would play with the rest of the
system. I believe Magritte makes it easy to design new descriptions,
right?
Anyway, I'm new to Magritte so maybe my models are not as well
designed as they should be. Any ideas wil be appreciated.
Cheers,
Ronaldo
On 2/24/08, Lukas Renggli <renggli(a)iam.unibe.ch> wrote:
--
Ronaldo Ferraz
http://log.reflectivesurface.com
Altough adding
descriptions would not make sense to the core, would it
make sense to change MAFileModel into a MAObject? That would make it
easier to build extensions on top of it.
The idea of MAFileModel is that you can easily subclass it to provide
your own strategy to store and retrieve the file. MAFileDescription
takes the #kind: as an argument, so you can tell it what class to
instantiate.
Maybe you can give an example, why you need to add new values to the
existing MAFileModel subclasses?
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki