Pier2 - Look and seaside components
renggli at gmail.com
Sat Feb 6 23:19:46 MET 2010
>> I cannot reproduce that problem. I get a list with all the Pier
>> Widgets and all the Seaside Components (see components.png).
> I also saw this complete list, but my own components (inherited from
> WAComponent are not
> displayed unless I code the #canBeRoot method as Julian suggested).
> This is the expected behaviour? Sorry If I'm missing things about
> Seaside 3.0, but I can see on
> the config app any class inherited from WAComponent, without having
> #canBeRoot method.
Strange, in my Seaside 3.0 image I have more than 200 subclasses of
WAComponent, but only those 20 that return true from #canBeRoot are
displayed in the configuration interface. That exact same behavior was
already part of Seaside 2.8, and probably earlier versions too.
>>> And about the look and feel of the old Pier I can't find explanation
>>> on the lists and so... :(
>> I do not understand this question.
> I means that the Pier version I was using, show an orange look and
> feel that may be changed
> on the main page with another that have a grey bar and orange buttons
> (named Events or so).
> On the new version (Pier 2) I'm not seeing that looks, that is ok?
> Some doc about how to add an own look and feel to Pier?
I think that orange look comes from Pier-Setup package. Evaluate
PRDistribution new register to get a default setup.
More information about the smallwiki