On Dec 6, 2007 2:33 PM, <
smalltalk@...> wrote:
>
> I have explored this strategy before for output. The thing is I really
> need to produce the RDF/XML/FOAF/RSS/ATOM or whatever else is required
> given a particular use case on demand relevant to the context. Many
> situations, Seaside won't play much of a part if any, however Magritte
> and my back-end (eventually Gemstone) will. There are many channels
> already to the application, so I want to define how to provide data in
> each format once regardless of the channel.
I don't think I expressed myself clearly. Magritte is (as I
understand it) a way to provide extra meta "descriptions" of how your
objects might be presented. Other components can take these
components and turn them into some representation. For example, the
Seaside Magritte renderer takes these descriptions and makes HTML.
You could create e.g. a PDF renderer that reads these descriptions and
generates a PDF item from them. I know that would be a lot of work,
but once it's done one time we all have it.
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
