Photo gallery?
by Damien Cassou
Hi,
is there any photo gallery available for Pier? I mean a widget where I
could upload pictures and they are rendered in a nice way. I started
one 4 years ago but I abandoned it.
Bye
--
Damien Cassou
http://damiencassou.seasidehosting.st
5 years, 4 months
installing Pier in Pharo2
by Peter H. Meadows
I want to learn/play with Pier.
Starting with Pharo 20500 image, I loaded seaside30 and pier3 from the
configurations browser. (ignored some warnings).
Then I do:
PRPierFrame registerAsApplication: 'emptyPier' kernel: PRPierFrame
exampleEmpty .
but I get WARequestContextNotFound error.
How can I make it work? Should I be using seaside2.8? What is the
difference between pier2 and pier3?
thx.
9 years, 12 months
iCal port to Magritte3
by Yanni Chiu
I just started to look at ical on squeaksource, and am happy to find
it's actively being worked on.
Is anyone working on porting iCalMagritte to Magritte3?
Should I do it, and call it iCalMagritte3? Then we'd have two dev
streams to maintain.
There are some minor problems with the code.
- ICalChronos-PaulDeBruicker.5 is not in the repository (maybe lost to a
squeaksource restart)
- the test class StafferDateAndTime is not defined anywhere (maybe it's
in the missing package)
10 years, 4 months
Pier file upload problems: MessageNotUnderstood: PRViewCommand>>fields
by Martin Krebs
I have tried Pier2 and the new PierAdmin but I keep getting an error when I
try to upload an image file (I have also had the error when I try to edit
the footer layout). I am running on MAC OSX snow Leapard, But have also
happens on an Ubuntu installation in VirtualBox on my Mac, and on a separate
PC with Ubuntu installed. has anybody seen this error before? (please see
debug print below) - I hope somebody can help?
Many thanks.
Seaside Walkback
MessageNotUnderstood: PRViewCommand>>fields
Debug Proceed Full Stack
Possible Causes
you sent a message this type of object doesn't understand
Stack Trace
thisContext
PRViewCommand(Object)>>doesNotUnderstand: #fields
self
a PRViewCommand[270270464]
thisContext
PRDocumentWidget>>text:
self
a PRDocumentWidget
thisContext
[:value | self text: value] in PRDocumentWidget>>renderEditOn:
self
a PRDocumentWidget
thisContext
BlockClosure>>valueWithPossibleArguments:
self
[:value | self text: value]
thisContext
WAValueCallback>>evaluateWithArgument:
self
a WAValueCallback
New Session Configure Halos Profile Memory XHTML 4/10 ms
--
View this message in context: http://forum.world.st/Pier-file-upload-problems-MessageNotUnderstood-PRVi...
Sent from the Magritte, Pier and Related Tools mailing list archive at Nabble.com.
10 years, 4 months
Pier site change from hacker
by dtrussardi＠tiscali.it
Hi,
i have a development site based on Pier3 run on Gemstone environment ( 3.1.0.2 ).
The server is based on Ubuntu server 10.04 LTS.
Now i do some performance test and the site answer at public web request.
Yesterday and today i have found some page change from ??? one hacker ???
One attached page changes report:
Structure Command Date Time User
/missione Edit 01/10/2013 6:40:55 open
/missione Edit 01/09/2013 21:8:20 open
where i note the user is not set.
The pier is created from PRDistribution subclass where the creation instance do:
self rootPage enumerator
with;
all;
do: [ :each |
each outgoingReferences
do: [ :link | (link isKindOf: PRInternalLink) ifTrue: [ link target: nil ] ].
each securityDecoration owner: self kernel users anyOne.
each securityDecoration group: self kernel groups anyOne ].
The Pier user name and password are change by default.
The Gemstone DataCurator password is change.
Someone considerations about it?
Thanks,
Dario
10 years, 4 months
Re: Pier component state when redisplay the page
by Reza Razavi
Hi Dario,
On January 3, 2013 at 12:32 PM "dtrussardi(a)tiscali.it"
<dtrussardi(a)tiscali.it> wrote:
> But within the same session when change the menu, i expect that the
system does not lose the references and don't create new instance.
As far as I can remember, this behavior is implemented by Pier Widgets.
> No one has a concrete example of how to solve the problem?
Any subclass of PRWidget should provide an example of how to solve that
problem.
Cheers,
Reza
10 years, 5 months
Re: Pier component state when redisplay the page
by Reza Razavi
Hi Yanni,
I would suggest looking at the references to PRCurrentContextHolder,
specifically PRPierFrame>>withContextDo:.
Cheers,
Reza
On January 4, 2013 at 6:05 PM Yanni Chiu <yanni(a)rogers.com> wrote:
> On 04/01/13 2:21 AM, Reza Razavi wrote:
> > On January 4, 2013 at 4:29 AM Yanni Chiu <yanni(a)rogers.com> wrote:
> >> It seems that the menu is nothing more than a page with a list of
> >> structure links, and is displayed through a PRDefaultView.
> >
> > Yes. The page (menu) itself is displayed as a PRDefaultView, which then
> > searches for each of its outgoing links/Components in the current
> > Context. So, the problem may also be related to the Context too.
> > Replacing your Component with a Widget may provide a solution, since
> > PRWidgets keep a pointer to their Context.
>
> Okay, the saved context in PRWidget seems to be the crucial difference.
> Without using PRWidget, the context used to generate url's would be:
> "PRCurrentContext value". I don't understand how a PRContext gets
> associated with a Seaside session though.
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
10 years, 5 months
Re: Pier component state when redisplay the page
by Reza Razavi
On January 4, 2013 at 4:29 AM Yanni Chiu <yanni(a)rogers.com> wrote:
> It seems that the menu is nothing more than a page with a list of
> structure links, and is displayed through a PRDefaultView.
Yes. The page (menu) itself is displayed as a PRDefaultView, which then
searches for each of its outgoing links/Components in the current
Context. So, the problem may also be related to the Context too.
Replacing your Component with a Widget may provide a solution, since
PRWidgets keep a pointer to their Context.
Cheers,
Reza
10 years, 5 months
