value link extendable?

Hi,

I try to figure out how to organize my environments in
pier. In one area of the site I need only to exchange
one single component per navigation level. I'm looking
for a way to only specify the environment on the top
most node.

The structure value link is one thing that might solve
this problem. Is there a way to add something to the
structure that the value link resolved? Then I could
specify something like this

+value:structure/neighbours+

to resolve a neighbours entry local to the seen page.
This way I can have a more heavy weight environment on
the top and would just specify neighbours entries on
each page.

Or is there another way to accomplish the same?

thanks,

Norbert

_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

> Or is there another way to accomplish the same?

Embed the component 'Document' into your environment. This enables
another editable area on every page. In the settings of the component
you can specify a default document and tell it to inherit the document
from the parent page, if you want.

HTH,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

On Sun, 2009-05-17 at 10:49 +0200, Lukas Renggli wrote:
> > Or is there another way to accomplish the same?
>
> Embed the component 'Document' into your environment. This enables
> another editable area on every page. In the settings of the component
> you can specify a default document and tell it to inherit the document
> from the parent page, if you want.
>
I can't find any 'Document" in my pier installation. I added

+document+

in my environment but the only thing I could select is a
PRDocumentWidget nothing else with document in it. And there
is no instance of PRComponent that is called 'Document'. Is
this something very new? I'm on gemstone so this should be
pier 1.1, right?

Norbert

_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Yes, the PRDocumentWidget is the right thing. I don't know its status
on GemStone, but it is already quite an old plugin.

Lukas

On Sunday, May 17, 2009, Norbert Hartl <[hidden email]> wrote:
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Hi Norbert,

Just embed the document in the environment and you will get an extra  
place to fill text in when you edit a page with that environment.

Cheers,
Doru

On 17 May 2009, at 11:17, Lukas Renggli wrote:

--
www.tudorgirba.com

"Yesterday is a fact.
  Tomorrow is a possibility.
  Today is a challenge."



_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

On Sun, 2009-05-17 at 11:17 +0200, Lukas Renggli wrote:
> Yes, the PRDocumentWidget is the right thing. I don't know its status
> on GemStone, but it is already quite an old plugin.
>
Well, it was broken but I fixed it. There were extra selectors called
parameterName: in some descriptions. Did they ever exist in magritte?
And there were some message

html rendererInstance ...

I exchanged them with

self context renderer

I think it is right.

Thanks for helping, now it works and it is _exactly_ what I was looking
for. But now I need to reset my kernel because I tried too much weird
stuff :)

thanks,

Norbert

_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

On Sun, 2009-05-17 at 11:20 +0200, Tudor Girba wrote:
> Hi Norbert,
>
> Just embed the document in the environment and you will get an extra  
> place to fill text in when you edit a page with that environment.
>
Thanks, but it is really hard to understand what you are writing.
For me as a user of pier "the document" has no meaning. For me it
would be "embed a PRDocumentWidget component into the environment".
And the phrase "when you edit a page" is right but for me there are
so many ways to edit things in pier I didn't figure out you mean
"_the_ Edit" :)
And while I didn't expect it on the same page where I edit the
contents of a page I overlooked the extra textinput field the first
time.

thanks again,

Norbert

_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Hi Norbert,

Thanks for the feedback.

Just to clarify the terms.

When we mention verbs related to Pier manipulation, we refer to  
commands. So, to edit a page means to invoke the Edit command on that  
page. When we refer to other types of edits we typically name them  
(e.g., Settings, Edit Design).

Related to Document/PRDocumentWidget, the first refers to the way a  
regular user sees the widget in the Pier UI (when choosing the  
component class), and the second refers to the name of the Smalltalk  
class.

I understood that you were taking a user point of view, so I am  
actually confused about how you see PRDocumentWidget in the drop down  
list when selecting the component class.

Cheers,
Doru


On 17 May 2009, at 13:11, Norbert Hartl wrote:

--
www.tudorgirba.com

"Every thing should have the right to be different."



_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

On Sun, 2009-05-17 at 13:48 +0200, Tudor Girba wrote:
I see only the class names in the drop down. Maybe this is something
gemstone dependent.

Norbert
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

On Sun, 2009-05-17 at 11:17 +0200, Lukas Renggli wrote:
> Yes, the PRDocumentWidget is the right thing. I don't know its status
> on GemStone, but it is already quite an old plugin.
>
I had anoter look and Pier-Documents in my gemstone is

Pier-Documents-lr.12

from

http://source.lukas-renggli.ch/pieraddons

That is strange. I upgrade to -lr.14 but it doesn't work.
Probably I would need a magritte update for parameterName: ?
And renderInstance? I saw in PRHaloRenderer but nowhere
else.

Norbert

_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

> I see only the class names in the drop down. Maybe this is something
> gemstone dependent.

Definitely. Pier normally does not display Smalltalk related concepts in the UI.

Yes. This requires you to update to the very latest versions of
Magritte-Core, Magritte-Seaside, Pier-Core and Pier-Seaside.

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Norbert,

I've submitted a GemStone bug on this, so you should look forward to fix in the next week or so...

Dale
----- "Norbert Hartl" <[hidden email]> wrote:

| On Sun, 2009-05-17 at 13:48 +0200, Tudor Girba wrote:
| > Hi Norbert,
| >
| > Thanks for the feedback.
| >
| > Just to clarify the terms.
| >
| > When we mention verbs related to Pier manipulation, we refer to  
| > commands. So, to edit a page means to invoke the Edit command on
| that  
| > page. When we refer to other types of edits we typically name them
|
| > (e.g., Settings, Edit Design).
| >
| > Related to Document/PRDocumentWidget, the first refers to the way a
|
| > regular user sees the widget in the Pier UI (when choosing the  
| > component class), and the second refers to the name of the Smalltalk
|  
| > class.
| >
| > I understood that you were taking a user point of view, so I am  
| > actually confused about how you see PRDocumentWidget in the drop
| down  
| > list when selecting the component class.
|
| I see only the class names in the drop down. Maybe this is something
| gemstone dependent.
|
| Norbert
| > Cheers,
| > Doru
| >
| >
| > On 17 May 2009, at 13:11, Norbert Hartl wrote:
| >
| > > On Sun, 2009-05-17 at 11:20 +0200, Tudor Girba wrote:
| > >> Hi Norbert,
| > >>
| > >> Just embed the document in the environment and you will get an
| extra
| > >> place to fill text in when you edit a page with that
| environment.
| > >>
| > > Thanks, but it is really hard to understand what you are writing.
| > > For me as a user of pier "the document" has no meaning. For me it
| > > would be "embed a PRDocumentWidget component into the
| environment".
| > > And the phrase "when you edit a page" is right but for me there
| are
| > > so many ways to edit things in pier I didn't figure out you mean
| > > "_the_ Edit" :)
| > > And while I didn't expect it on the same page where I edit the
| > > contents of a page I overlooked the extra textinput field the
| first
| > > time.
| > >
| > > thanks again,
| > >
| > > Norbert
| > >
| > >> Cheers,
| > >> Doru
| > >>
| > >> On 17 May 2009, at 11:17, Lukas Renggli wrote:
| > >>
| > >>> Yes, the PRDocumentWidget is the right thing. I don't know its
|
| > >>> status
| > >>> on GemStone, but it is already quite an old plugin.
| > >>>
| > >>> Lukas
| > >>>
| > >>> On Sunday, May 17, 2009, Norbert Hartl <[hidden email]>
| wrote:
| > >>>> On Sun, 2009-05-17 at 10:49 +0200, Lukas Renggli wrote:
| > >>>>>> Or is there another way to accomplish the same?
| > >>>>>
| > >>>>> Embed the component 'Document' into your environment. This
| enables
| > >>>>> another editable area on every page. In the settings of the
| > >>>>> component
| > >>>>> you can specify a default document and tell it to inherit the
| > >>>>> document
| > >>>>> from the parent page, if you want.
| > >>>>>
| > >>>> I can't find any 'Document" in my pier installation. I added
| > >>>>
| > >>>> +document+
| > >>>>
| > >>>> in my environment but the only thing I could select is a
| > >>>> PRDocumentWidget nothing else with document in it. And there
| > >>>> is no instance of PRComponent that is called 'Document'. Is
| > >>>> this something very new? I'm on gemstone so this should be
| > >>>> pier 1.1, right?
| > >>>>
| > >>>> Norbert
| > >>>>
| > >>>> _______________________________________________
| > >>>> Magritte, Pier and Related Tools ...
| > >>>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
| > >>>>
| > >>>
| > >>> --
| > >>> Lukas Renggli
| > >>> http://www.lukas-renggli.ch
| > >>> _______________________________________________
| > >>> Magritte, Pier and Related Tools ...
| > >>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
| > >>
| > >> --
| > >> www.tudorgirba.com
| > >>
| > >> "Yesterday is a fact.
| > >> Tomorrow is a possibility.
| > >> Today is a challenge."
| > >>
| > >>
| > >>
| > >> _______________________________________________
| > >> Magritte, Pier and Related Tools ...
| > >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
| > >
| > > _______________________________________________
| > > Magritte, Pier and Related Tools ...
| > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki
| >
| > --
| > www.tudorgirba.com
| >
| > "Every thing should have the right to be different."
| >
| >
| >
| > _______________________________________________
| > Magritte, Pier and Related Tools ...
| > https://www.iam.unibe.ch/mailman/listinfo/smallwiki
|
| _______________________________________________
| Magritte, Pier and Related Tools ...
| https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

----- "Lukas Renggli" <[hidden email]> wrote:

| > I had anoter look and Pier-Documents in my gemstone is
| >
| > Pier-Documents-lr.12
| >
| > from
| >
| > http://source.lukas-renggli.ch/pieraddons
| >
| > That is strange. I upgrade to -lr.14 but it doesn't work.
| > Probably I would need a magritte update for parameterName: ?
| > And renderInstance? I saw in PRHaloRenderer but nowhere
| > else.
|
| Yes. This requires you to update to the very latest versions of
| Magritte-Core, Magritte-Seaside, Pier-Core and Pier-Seaside.
|

Lukas,

Are these updates part of Pier 1.1.1 (which is what I moved to with GLASS.230-dkh.209)? At the time I moved to 1.1.1 I used the 1.1.1 image that was distributed - at the time there were later versions of some of the packages, but I was reluctant to load packages that may be meant to be part of the release...

Is there a later version of Pier available (later than 1.1.1)?

I ask, because I have had to make GemStone-specific changes to some of the packages, so it's not quite as easy as just loading the newer versions of the packages...

Dale
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

> Is there a later version of Pier available (later than 1.1.1)?

Not yet, many people seem to just use the latest version though.

I am not entirely happy with the value links and file handling (both
issues were recently discussed here on the list). If these issues are
resolved a new version like 1.2 will be necessary ...

> I ask, because I have had to make GemStone-specific changes to some of the packages, so it's not quite as easy as just loading the newer versions of the packages...

What are these issues? If possible I would like to make this easier.
Especially if Pier moves towards Seaside 2.9, I would like to package
all platform dependent code separately.

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

On Sun, 2009-05-17 at 12:19 -0700, Dale Henrichs wrote:
> Norbert,
>
> I've submitted a GemStone bug on this, so you should look forward to fix in the next week or so...
>
Great! I could send you my findings but it seems it just happens
because of the version mismatch.

Norbert
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Norbert,

If you've got some more detail, I'd appreciate it, especially if the fix is just use the correct set of package versions.

Dale

----- "Norbert Hartl" <[hidden email]> wrote:

| On Sun, 2009-05-17 at 12:19 -0700, Dale Henrichs wrote:
| > Norbert,
| >
| > I've submitted a GemStone bug on this, so you should look forward to
| fix in the next week or so...
| >
| Great! I could send you my findings but it seems it just happens
| because of the version mismatch.
|
| Norbert
| > Dale
| > ----- "Norbert Hartl" <[hidden email]> wrote:
| >
| > | On Sun, 2009-05-17 at 13:48 +0200, Tudor Girba wrote:
| > | > Hi Norbert,
| > | >
| > | > Thanks for the feedback.
| > | >
| > | > Just to clarify the terms.
| > | >
| > | > When we mention verbs related to Pier manipulation, we refer to
|
| > | > commands. So, to edit a page means to invoke the Edit command
| on
| > | that  
| > | > page. When we refer to other types of edits we typically name
| them
| > |
| > | > (e.g., Settings, Edit Design).
| > | >
| > | > Related to Document/PRDocumentWidget, the first refers to the
| way a
| > |
| > | > regular user sees the widget in the Pier UI (when choosing the
|
| > | > component class), and the second refers to the name of the
| Smalltalk
| > |  
| > | > class.
| > | >
| > | > I understood that you were taking a user point of view, so I am
|
| > | > actually confused about how you see PRDocumentWidget in the
| drop
| > | down  
| > | > list when selecting the component class.
| > |
| > | I see only the class names in the drop down. Maybe this is
| something
| > | gemstone dependent.
| > |
| > | Norbert
| > | > Cheers,
| > | > Doru
| > | >
| > | >
| > | > On 17 May 2009, at 13:11, Norbert Hartl wrote:
| > | >
| > | > > On Sun, 2009-05-17 at 11:20 +0200, Tudor Girba wrote:
| > | > >> Hi Norbert,
| > | > >>
| > | > >> Just embed the document in the environment and you will get
| an
| > | extra
| > | > >> place to fill text in when you edit a page with that
| > | environment.
| > | > >>
| > | > > Thanks, but it is really hard to understand what you are
| writing.
| > | > > For me as a user of pier "the document" has no meaning. For me
| it
| > | > > would be "embed a PRDocumentWidget component into the
| > | environment".
| > | > > And the phrase "when you edit a page" is right but for me
| there
| > | are
| > | > > so many ways to edit things in pier I didn't figure out you
| mean
| > | > > "_the_ Edit" :)
| > | > > And while I didn't expect it on the same page where I edit
| the
| > | > > contents of a page I overlooked the extra textinput field the
| > | first
| > | > > time.
| > | > >
| > | > > thanks again,
| > | > >
| > | > > Norbert
| > | > >
| > | > >> Cheers,
| > | > >> Doru
| > | > >>
| > | > >> On 17 May 2009, at 11:17, Lukas Renggli wrote:
| > | > >>
| > | > >>> Yes, the PRDocumentWidget is the right thing. I don't know
| its
| > |
| > | > >>> status
| > | > >>> on GemStone, but it is already quite an old plugin.
| > | > >>>
| > | > >>> Lukas
| > | > >>>
| > | > >>> On Sunday, May 17, 2009, Norbert Hartl <[hidden email]>
| > | wrote:
| > | > >>>> On Sun, 2009-05-17 at 10:49 +0200, Lukas Renggli wrote:
| > | > >>>>>> Or is there another way to accomplish the same?
| > | > >>>>>
| > | > >>>>> Embed the component 'Document' into your environment.
| This
| > | enables
| > | > >>>>> another editable area on every page. In the settings of
| the
| > | > >>>>> component
| > | > >>>>> you can specify a default document and tell it to inherit
| the
| > | > >>>>> document
| > | > >>>>> from the parent page, if you want.
| > | > >>>>>
| > | > >>>> I can't find any 'Document" in my pier installation. I
| added
| > | > >>>>
| > | > >>>> +document+
| > | > >>>>
| > | > >>>> in my environment but the only thing I could select is a
| > | > >>>> PRDocumentWidget nothing else with document in it. And
| there
| > | > >>>> is no instance of PRComponent that is called 'Document'.
| Is
| > | > >>>> this something very new? I'm on gemstone so this should be
| > | > >>>> pier 1.1, right?
| > | > >>>>
| > | > >>>> Norbert
| > | > >>>>
| > | > >>>> _______________________________________________
| > | > >>>> Magritte, Pier and Related Tools ...
| > | > >>>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
| > | > >>>>
| > | > >>>
| > | > >>> --
| > | > >>> Lukas Renggli
| > | > >>> http://www.lukas-renggli.ch
| > | > >>> _______________________________________________
| > | > >>> Magritte, Pier and Related Tools ...
| > | > >>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
| > | > >>
| > | > >> --
| > | > >> www.tudorgirba.com
| > | > >>
| > | > >> "Yesterday is a fact.
| > | > >> Tomorrow is a possibility.
| > | > >> Today is a challenge."
| > | > >>
| > | > >>
| > | > >>
| > | > >> _______________________________________________
| > | > >> Magritte, Pier and Related Tools ...
| > | > >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
| > | > >
| > | > > _______________________________________________
| > | > > Magritte, Pier and Related Tools ...
| > | > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki
| > | >
| > | > --
| > | > www.tudorgirba.com
| > | >
| > | > "Every thing should have the right to be different."
| > | >
| > | >
| > | >
| > | > _______________________________________________
| > | > Magritte, Pier and Related Tools ...
| > | > https://www.iam.unibe.ch/mailman/listinfo/smallwiki
| > |
| > | _______________________________________________
| > | Magritte, Pier and Related Tools ...
| > | https://www.iam.unibe.ch/mailman/listinfo/smallwiki
| > _______________________________________________
| > Magritte, Pier and Related Tools ...
| > https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

----- "Lukas Renggli" <[hidden email]> wrote:
|
| > I ask, because I have had to make GemStone-specific changes to some
| of the packages, so it's not quite as easy as just loading the newer
| versions of the packages...
|
| What are these issues? If possible I would like to make this easier.
| Especially if Pier moves towards Seaside 2.9, I would like to package
| all platform dependent code separately.

The list isn't real big (i'd have to do a diff to get the little changes), but the main change that I'm thinking/worried about is actually a Magritte issue that overflows into Pier.

GemStone can't migrate an object that is on the stack (as a receiver), this means that the normal Magritte mechanism for creating variables doesn't work in GemStone...callers of readUsing: ... the solution for GemStone is to flip the logic:

if an 'object readUsing: aDescription' fails with an ErrCantBecomeSelfOnStack error, because object is a receiver on the stack, I retry doing 'aDescription accessor read: object'...object isn't on the stack so the migrate succeeds ... unfortunately there are a number of places where I have to insert GemStone-specific code ... in Magritte and Pier ... doing anything else would have been even more intrusive and probably broken a ton of code to boot...

Offhand there are probably only 20 methods affected but they are sprinkled around the system...

Dale
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki