5 Feb
2010
5 Feb
'10
10:57 p.m.
Hi:
I installed (using the Metacello configuration) the Seaside 3.0 and
migrated one of my applications.
Now, playing with the new Pier 2:
1. Reading this list I managed how to configure and setup, but I can't
make it show the look of the
older version nor the possibility of change to the old Events look.
These features are not availables?
2. I want to add an own seaside component on a Pier page, but the
combo to select only show the
examples and so.....how I can add to this list my own seaside components?
Thanks.
--
=================================================
Germán S. Arduino <gsa @ arsol.net> Twitter: garduino
Arduino Software & Web Hosting http://www.arduinosoftware.com
PasswordsPro http://www.passwordspro.com
=================================================
5 Feb
5 Feb
11:46 p.m.
On Fri, Feb 5, 2010 at 1:57 PM, Germán Arduino <garduino(a)gmail.com> wrote:
2. I want to add an own seaside component on a Pier
page, but the
combo to select only show the
examples and so.....how I can add to this list my own seaside components?
Have you defined #canBeRoot on the class-side of your component to
return true? I'm assuming Pier uses that mechanism just like the
Seaside config app does... (but I could be wrong).
Julian
6 Feb
6 Feb
4:11 p.m.
Yes, I didn't code the #canBeRoot but I understood that not needed
anymore on Seaside 3.0, else
how may be that any WAComponent based class is shown on the config application?
And about the look and feel of the old Pier I can't find explanation
on the lists and so... :(
Cheers.
Germán.
2010/2/5 Julian Fitzell <jfitzell(a)gmail.com>om>:
On Fri, Feb 5, 2010 at 1:57 PM, Germán Arduino
<garduino(a)gmail.com> wrote:
2. I want to add an own seaside component on a
Pier page, but the
combo to select only show the
examples and so.....how I can add to this list my own seaside components?
Have you defined #canBeRoot on the class-side of your component to
return true? I'm assuming Pier uses that mechanism just like the
Seaside config app does... (but I could be wrong).
Julian
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
4:34 p.m.
Yes, I didn't code the #canBeRoot but I understood
that not needed
anymore on Seaside 3.0, else
how may be that any WAComponent based class is shown on the config application?
I cannot reproduce that problem. I get a list with all the Pier
Widgets and all the Seaside Components (see components.png).
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.
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
11:02 p.m.
Hi Lukas:
Lets me explain better:
2010/2/6 Lukas Renggli <renggli(a)gmail.com>om>:
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.
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?
Thanks.
Germán.
Yes, I
didn't code the #canBeRoot but I understood that not needed
anymore on Seaside 3.0, else
how may be that any WAComponent based class is shown on the config application?
I cannot reproduce that problem. I get a list with all the Pier
Widgets and all the Seaside Components (see components.png).
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.
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
11:19 p.m.
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. 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.
11:43 p.m.
Hi Lukas:
2010/2/6 Lukas Renggli <renggli(a)gmail.com>om>:
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.
I get the behaviour you comment only on the combo of Pier (when adding
a component) but on the Seaside config app any class inherited of WAComponent
is displayed....(have or not the #canBeRoot method). I'm using Pharo RC2.
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.
Tried this now I can change the look, but never I get the colors and buttons
of the previous versions. May be the .css are missing...?
Also, selecting the Book look I get:
MessageNotUnderstood: receiver of "named:" is nil
Your request could not be completed. An exception occurred.
Thanks by the help.
Germán.
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. 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. Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
--
=================================================
Germán S. Arduino <gsa @ arsol.net> Twitter: garduino
Arduino Software & Web Hosting http://www.arduinosoftware.com
PasswordsPro http://www.passwordspro.com
=================================================
7 Feb
7 Feb
12:34 a.m.
2010/2/6 Germán Arduino <garduino(a)gmail.com>om>:
I think that orange look comes from Pier-Setup package. Evaluate
PRDistribution new register to get a default setup.
Tried this now I can change the look, but never I get the colors and buttons
of the previous versions. May be the .css are missing...?
Also, selecting the Book look I get:
MessageNotUnderstood: receiver of "named:" is nil
Your request could not be completed. An exception occurred.
Thanks by the help.
Germán.
This is only the pending question then.
Cheers.
Germán.
Hi Lukas:
2010/2/6 Lukas Renggli <renggli(a)gmail.com>om>:
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.
I get the behaviour you comment only on the combo of Pier (when adding
a component) but on the Seaside config app any class inherited of WAComponent
is displayed....(have or not the #canBeRoot method). I'm using Pharo RC2.
Not, sorry, sorry, I was using a subclassification of Magritte Reports and one
of the ancestors have a registration at class level... :(
My big fault, not saw all the inherited tree.
Sorry again.
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. > 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?
5432
days inactive
5433
days old
7 comments
3 participants
participants (3)
-
Germán Arduino -
Julian Fitzell -
Lukas Renggli