Using Magritte objects in pier

[Norbert Hartl]

On Wed, 2009-02-25 at 10:07 +0100, Lukas Renggli wrote:
> > - How do I embedded any magritte object on a page? In my
> >  code I just do anObject asComponent. Is there an easy
> >  way to just integrate objects on a page. It needs some
> >  tricks in order not to display all the time the same
> >  object. I think yo know what I mean
> 
> You can embed any Seaside component into Pier. In the case of a
> Magritte component you might need to wrap it into a normal Seaside
> component that returns true for #canBeRoot and that sets-up the
> Magritte component.
> 
> Simply create an embedded link in the page like so: +magritte-form+.
> Click on the link to add a component and select your component from
> the list.
> 
Ok, thanks, I expected that. It is not big of a problem. With an
additional component I can set up the announcements as well. It just
makes the following approach a little more complicated.

> > - If there is a good solution for the above is there a
> >  solution for displaying individual slots of an object?
> >  I mean to have access to an individual component class
> >  for an instance variable. The most difficult thing
> >  (while developing the project) was to layout the
> >  magritte forms. I would like to see something like
> >  +mySuperObject/@title+
> >  +mySuperObject/@text+
> >  to display the component classes of the object and
> >  dealing with the rest of the html the pier way.
> 
> Mhh ... links support parameters, but that use-case is currently not
> implemented. Maybe you want to give a try and implement that yourself?
> 
Yes, I'll give it a try. I need to know pier anyway if I want to use
it. It is just that I had a very hard time to resolve even simple
things in pier. I can accept the "structure is everything" thingy but
most of this is than "the structure in your brain" and that is hard to
follow. I scan again the papers I collected about magritte and pier over
the years. At the moment it is an infinite learning curve (the structure
seems to be a graph :) ).

thanks so far,

Norbert