3 Jan
2013
3 Jan
'13
1:29 p.m.
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
3 Jan
3 Jan
4:54 p.m.
New subject: Pier component state when redisplay the page
Hi, Reza
thank,
i do some test and i think to found a my hold problem with Pier.
> Ciao,
>
> i have do some test with the PRDistribution register
>
> It create a default pier entry Welcome to Pier!
>
>
> It in appearance work fine but under where is the problem that i describe in these
e-mails.
>
>
> The first time ( and when open a new session ) the anchor relative to the menu
report right href with the _s and _k parameter
>
> for example the Home anchor report :
>
>
> <a class=" active internal page" title="Welcome to Pier!"
href="/pier?_s=9K76T_OM34OI-n_d&_k=mZPHc-oUOnpyR1IQ&_n&1">Home</a>
>
>
>
> For each next sequence display the menu anchor don't report any _s _k
value.
>
> Apparently it works fine, but in reality the system loses information and create a
new instance of the page at any click.
>
> In my case, i lose the state of the component ( counter ) in the page and the error
is apparent.
>
>
> Perhaps the problem is relative to the cookies where the system manage some
information.
>
>
> If in the pier dispatcher entry point i disable the cookies the _s _k href value
aren't manage even when the system create new session.
>
>
> Someone has some suggestions indication on how to solve the problem?
>
> For the pier entry is necessary - obligatory enabled the cookies ?
Thank for any considerations,
Dario
4 Jan
4 Jan
4:29 a.m.
New subject: Pier component state when redisplay the page
On 03/01/13 10:54 AM, dtrussardi(a)tiscali.it wrote:
>> The first time ( and when open a new session ) the anchor relative to the menu
report right href with the _s and _k parameter
>> for example the Home anchor report :
>>
>> <a class=" active internal page" title="Welcome to
Pier!"
href="/pier?_s=9K76T_OM34OI-n_d&_k=mZPHc-oUOnpyR1IQ&_n&1">Home</a>
>>
>> For each next sequence display the menu anchor don't report any _s _k
value.
>>
>> Someone has some suggestions indication on how to solve the problem?
This behaviour has always disturbed me, and thanks to your question,
I've finally looked into it.
It seems that the menu is nothing more than a page with a list of
structure links, and is displayed through a PRDefaultView. If you look
at PRDefaultView>>isRestful, it returns true. Try an *experiment*, and
change it to return false. Does the change cause the generated anchor
links to have the "lost" _s and _k parameters?
The problem is that if your menu item points at a structure that is not
restful (and your counter state is not restful), then the menu item will
appear to misbehave. I think the fix is to create your own menu widget.
Maybe look at PRViewsWidget or PRCommandsWidget to see what code is needed.
3:03 p.m.
New subject: Pier component state when redisplay the page
Ciao,
thanks for any consideration.
On 03/01/13 10:54 AM, dtrussardi(a)tiscali.it wrote:
I change the PRDefaultView>>isRestful to ^false and with it the menu anchor
manage the _k parameter.
With the _k parameters the request work fine and don't create a new instance of the
page at any click.
I don't understund because the menu anchor don't manage the _s parameter but the
_k is enough for my question.
>> The first time ( and when open a new session ) the anchor relative to the menu
report right href with the _s and _k parameter
>> for example the Home anchor report :
>>
>> <a class=" active internal page" title="Welcome to
Pier!"
href="/pier?_s=9K76T_OM34OI-n_d&_k=mZPHc-oUOnpyR1IQ&_n&1">Home</a>
>>
>> For each next sequence display the menu anchor don't report any _s _k
value.
>>
>> Someone has some suggestions indication on how to solve the problem?
This behaviour has always disturbed me, and thanks to your question, I've finally
looked into it.
It seems that the menu is nothing more than a page with a list of structure links, and is
displayed through a PRDefaultView. If you look at PRDefaultView>>isRestful, it
returns true. Try an *experiment*, and change it to return false. Does the change cause
the generated anchor links to have the "lost" _s and _k parameters?
The problem is that if your menu item points at a structure that is not restful (and your
counter state is not restful), then the menu item will appear to misbehave. I think the
fix is to create your own menu widget. Maybe look at PRViewsWidget or PRCommandsWidget to
see what code is needed.
In my image i have a deprecated PRMenuWidget it can use for solve this problematic ?
I look at PRViewsWidget and i think to define a new PRNewMenuWidget
and define a menuPage with
menuPage
^ menuWidget ifNil:
[ menuWidget := (PRPage named: 'menu')
addChild: ((PRComponent named: 'widgetmenu')
prototypeInstance: PRNewMenuWidget new;
yourself);
contents: '+widgetmenu+'
]
Now i don't understand where i define the menu structure:
'- *Home>/*
- *Chi siamo>/chisiamo*
- *Missione>/missione*
- *Catalogo>/catalogo*
- *Offerte>/offerte*
- *Ordini>/menuonline*
- *Blog>/blog*
- *Riferimenti>/riferimenti*';
and how redefine the method PRNewMenuWidget renderItem: aClass on: html
Thanks,
Dario
P.S. i'm interested to understund the pier environment. Where i can found some
documentation?
5:53 p.m.
New subject: Pier component state when redisplay the page
On 04/01/13 9:03 AM, dtrussardi(a)tiscali.it wrote:
In my image i have a deprecated PRMenuWidget it can use for solve this problematic ?
I didn't know PRMenuWidget was still included. Try using PRMenuWidget
instead of what I said about looking at PRViewsWidget for code inspiration.
Have a look at PRMenuWidget class>>defaultDocument
I think the code you need is something like:
menuPage
| document widget |
document := PRDocumentParser parse:
'- *Home>/*
- *Chi siamo>/chisiamo*
- *Missione>/missione*
- *Catalogo>/catalogo*
- *Offerte>/offerte*
- *Ordini>/menuonline*
- *Blog>/blog*
- *Riferimenti>/riferimenti*'.
widget = PRMenuWidget new.
widget write: document using: widget descriptionDocument.
^ menuWidget ifNil:
[ menuWidget := (PRPage named: 'menu')
addChild: ((PRComponent named: 'widgetmenu')
prototypeInstance: widget;
yourself);
contents: '+widgetmenu+'
]
P.S. i'm interested to understund the pier environment. Where i can found some
documentation?
Other than http://piercms.com, this mailing list is it, AFAIK.
5 Jan
5 Jan
5:40 p.m.
New subject: Pier component state when redisplay the page
Ciao,
thanks Yanni.
On 04/01/13 9:03 AM, dtrussardi(a)tiscali.it wrote:
I followed your indications and the statements work.
The PRMenuWidget define :
renderContentOn: html
| visitor |
visitor := PRMostSpecificInternalLinkVisitor new
visit: self document.
PRMenuRenderer new
target: visitor target;
continue: self document
in: self on: html
But the menu anchor don't manage the _k parameter.
I don't understund how the widgets works but in this my case
the PRContext
urlOn: aRenderer
"Answer a Seaside URL to get into the receiving context."
| url |
^ aRenderer callbacks isNil
ifTrue: [ self url ]
ifFalse: [
url := aRenderer context actionUrl copy.
url purgeOtherFields; adaptToContext: self.
**** (self command isRestful and: [ self application hasCookieInContext: self
requestContext ])
ifTrue: [ url purgeSeasideFields ]
ifFalse: [
url queryFields
at: '_n' put: nil;
at: (aRenderer callbacks store: self activationCallback) put: nil ].
url ]
reference in any case the command ( see *** )
Now the PRViewCommand
isRestful
^ self viewComponentClass isRestful
and it answer the PRDefaultView isRestful -> ^true
So the problem remains.
I wonder if in any case the widget is managed as a PRViewCommand
or if they exist precisely to avoid such management.
Some considerations about it and my menu management problem?
Ciao, thanks,
Dario
In my image i have a deprecated PRMenuWidget it can use for solve this problematic ?
I didn't know PRMenuWidget was still included. Try using PRMenuWidget instead of what
I said about looking at PRViewsWidget for code inspiration.
Have a look at PRMenuWidget class>>defaultDocument
I think the code you need is something like:
menuPage
| document widget |
document := PRDocumentParser parse:
'- *Home>/*
- *Chi siamo>/chisiamo*
- *Missione>/missione*
- *Catalogo>/catalogo*
- *Offerte>/offerte*
- *Ordini>/menuonline*
- *Blog>/blog*
- *Riferimenti>/riferimenti*'.
widget = PRMenuWidget new.
widget write: document using: widget descriptionDocument.
^ menuWidget ifNil:
[ menuWidget := (PRPage named: 'menu')
addChild: ((PRComponent named: 'widgetmenu')
prototypeInstance: widget;
yourself);
contents: '+widgetmenu+'
]
9:21 p.m.
New subject: Pier component state when redisplay the page
On 05/01/13 11:40 AM, dtrussardi(a)tiscali.it wrote:
So the problem remains.
I wonder if in any case the widget is managed as a PRViewCommand
or if they exist precisely to avoid such management.
Some considerations about it and my menu management problem?
Does anyone else have any suggestions?
Do you have to use a WACounter? Or, is that just for discussion
purposes. Can you create something like PRCounterWidget that subclasses
from PRWidget - that might work, but I've not tried it myself.
4135
days inactive
4137
days old
6 comments
3 participants
participants (3)
-
dtrussardi＠tiscali.it -
Reza Razavi -
Yanni Chiu