Hi Lukas (or anyone)
,
I have just tried out the PRMenuWidget, but I dont get what it is for.
Why cant you simply embed any page where you want a menu.
Keith
Hi,
We would like to fill the list of Pier installations from:
http://www.piercms.com/seaside/doc/examples
Thus, we kindly ask you to let us know if you have Pier installation
somewhere publicly so that we can link to it.
Thanks,
Doru
--
www.tudorgirba.com
"Problem solving should be concentrated on describing
the problem in a way that is relevant for the solution."
Hi,
I'm trying to align my tests a little bit more at
the moment. I'm using seaside testing for the tests
and magritte for most of the model objects.
Whenever a model asComponent is rendered every
individual MAElementComponent is rendered with an
automatically assigned name attribute. Is it hard
to resolve the description by this name value?
This way it would be possible to set values in a
form input fields. This is quite tedious at the
moment. The fields that use <label forId=""> it
is not too hard but not all of the input fields
have labels and not always are they the previous
sibling and so on... I know albatross has some
clever stuff to detect this but I like to do the
tests with seaside testing for the time being.
thanks,
Norbert
I accidentally added a seaside component that doesnt render to the pier
environment in a fresh 1.1.
I tried removing it from the document heirarchy but to no avail, any ideas?
Keith
I have a PRWidget that initializes a report based on whether self
context user isNil. I'm attempting to do unit tests on the widget using
SeasideTesting, but when setUp initializes the widget, it has no
context. Is there a simple way to create a test context?
I don't quite understand the pieces of a context ( kernel, structure,
command ) well enough to create one from scratch at this point.
Joel
While testing how hard it will be to bring my site
into pier I discovered some css class clashes. For
people it is quite normal to assign classes like
header, footer and the like.
In my opinion a cms like pier should try to step
out of the way of any usage conflict. Therefor I
would propose to namespace the css classes. A
pr_header, pr_footer will do I think.
Or do I missunderstand something completely? For me
it was not possible to reconstruct our layout without
haveing to remove all librares for the application. But
then it is tedious to work with pier as the edit boxes
and stuff are too small.
What is the best approach to bring in the own developed
design and having pier still functioning?
thanks,
Norbert
I am excited about trying Pier, but I have a bit of an investment in
code I have written in Visualworks 7.6 versus Squeak.
I tried loading the Pier bundle from the Cincom public repository, but
got lots of errors.
I found that if I pre-loaded Magritte, things went a little better, but
I am still getting errors.
Is the Visualworks version of Pier a dead end? Am I missing some
dependencies? Should I use an older version of Visualworks? Should I
just port my code over to Squeak?
If the Pier bundle on the Cincom public repository is good, then let me
know and I'll post my specific errors to try to work through it.
Thank-you.
I would like to have a static link that points directly to a login
page (i.e. http://mydomain.com/login). How can I make a url execute a
command (in this case PRLogin) directly?
Thanks,
David
----
1 Squeak/Seaside/Pier site deployed
My pier setup stabilizes a bit. I was able to reproduce
a few page layouts of our project and integrated some
components. At the moment I really love it as most of
the things I wanted worked out today.
One thing that I want to change is the title of a structure.
I don't want to have it as not all pages have titles and the
others deal differently with something like a title. So why
is the title mandatory for a structure? Is there an easy way
to get rid of it?
Navigating to a page, pressing edit and just integrate a
component by doing +...+ is really great! But I'm asking myself
what is the best way to acquire the data the component needs.
As an example I have a user and the user has a list of images.
I have a component that takes a list of images and displays them.
In my current approach these are connected via Announcements.
Whenever the user changes the image list component gets his model
set to the new list of images. What is the best way to decorate a
component with some functionality?
thanks in advance,
Norbert
