From jborden23 at mac.com  Wed Mar  2 04:56:36 2011
From: jborden23 at mac.com (John Borden)
Date: Tue, 01 Mar 2011 21:56:36 -0600
Subject: Pier 1.2 to 2.0 conversion
Message-ID: <176012DD-07BA-4B3D-B862-D84F1F154EC0@mac.com>

Pier Experts - What all are the changes between older version and Pier 2.0?  I've noticed that HTML needs to be contained within triple curly brackets ({{{<b>like this</b>}}}) - is there anything written that will convert existing Pier 1.2 pages to this?  I've got a wiki with over 5000 pages.
Thanks,
John


From renggli at gmail.com  Wed Mar  2 08:38:30 2011
From: renggli at gmail.com (Lukas Renggli)
Date: Wed, 2 Mar 2011 08:38:30 +0100
Subject: Pier 1.2 to 2.0 conversion
In-Reply-To: <176012DD-07BA-4B3D-B862-D84F1F154EC0@mac.com>
References: <176012DD-07BA-4B3D-B862-D84F1F154EC0@mac.com>
Message-ID: <AANLkTi=T7UdyswsUTt6KHJ88W7FtGMinDBEqdm5HA6pD@mail.gmail.com>

It should be possible to export an old Pier and import it into a Pier
2.0. The differendes are minimal, you just need to make sure that you
have loaded all the same plugins. For the HTML changes it depends on
your use of HTML in normal pages: Typically HTML is only used in the
environment/templates, so it should be easy to fix manually.

Lukas

On Wednesday, 2 March 2011, John Borden <jborden23 at mac.com> wrote:
> Pier Experts - What all are the changes between older version and Pier 2.0? ?I've noticed that HTML needs to be contained within triple curly brackets ({{{<b>like this</b>}}}) - is there anything written that will convert existing Pier 1.2 pages to this? ?I've got a wiki with over 5000 pages.
> Thanks,
> John
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

-- 
Lukas Renggli
www.lukas-renggli.ch


From norbert at hartl.name  Wed Mar  2 10:11:13 2011
From: norbert at hartl.name (Norbert Hartl)
Date: Wed, 2 Mar 2011 10:11:13 +0100
Subject: Pier 1.2 to 2.0 conversion
In-Reply-To: <AANLkTi=T7UdyswsUTt6KHJ88W7FtGMinDBEqdm5HA6pD@mail.gmail.com>
References: <176012DD-07BA-4B3D-B862-D84F1F154EC0@mac.com>
	<AANLkTi=T7UdyswsUTt6KHJ88W7FtGMinDBEqdm5HA6pD@mail.gmail.com>
Message-ID: <A0D91702-CC1F-4FAA-867B-9AE29375F740@hartl.name>


On 02.03.2011, at 08:38, Lukas Renggli wrote:

> It should be possible to export an old Pier and import it into a Pier
> 2.0. The differendes are minimal, you just need to make sure that you
> have loaded all the same plugins. For the HTML changes it depends on
> your use of HTML in normal pages: Typically HTML is only used in the
> environment/templates, so it should be easy to fix manually.
> 
> 
And check that you change the occurrences of "+value:children+" to "*value:children*"

Norbert

> On Wednesday, 2 March 2011, John Borden <jborden23 at mac.com> wrote:
>> Pier Experts - What all are the changes between older version and Pier 2.0?  I've noticed that HTML needs to be contained within triple curly brackets ({{{<b>like this</b>}}}) - is there anything written that will convert existing Pier 1.2 pages to this?  I've got a wiki with over 5000 pages.
>> Thanks,
>> John
>> 
>> _______________________________________________
>> Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>> 
> 
> -- 
> Lukas Renggli
> www.lukas-renggli.ch
> 
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki



From damien.pollet at gmail.com  Thu Mar  3 04:05:56 2011
From: damien.pollet at gmail.com (Damien Pollet)
Date: Thu, 3 Mar 2011 04:05:56 +0100
Subject: Magritte description for e-mail
In-Reply-To: <4225409E-3D6F-4001-8256-1167DDC480AC@tiscali.it>
References: <4225409E-3D6F-4001-8256-1167DDC480AC@tiscali.it>
Message-ID: <AANLkTikUZBbYvkyE5-xm87snCfTt=ZL_BPKyTkZUorgN@mail.gmail.com>

Bumping this one?

Is there a MAEmailDescription somewhere?
I'm thinking something very much like MAStringDescription, but with a
nice validator to ensure that the string complies with the RFCs on
email addresses?



On Tue, Jul 13, 2010 at 20:26, dtrussardi at tiscali.it
<dtrussardi at tiscali.it> wrote:
> Hi,
>
> ? ? ? ?i have some descriptions and one based on MAStringDescription for manage the e-mail reference.
>
> ? ? ? ?Now i'm interested to create a MAReport with fields for management email.
>
> ? ? ? ?Where for management ?i think a link to open new email directly from report ?:
>
> ? ? ? ? ? ? ? ? ? ? ? ?html anchor attributeAt: 'href' put: 'mailto:', anObject emailBase.
>
>
> ? ? ? ?How i can do it ?
>
> ? ? ? ?Anyone create a specific MADescription for define e management ?email reference ?
>
>
> ? ? ? ?Thank,
>
> ? ? ? ? ? ? ? ?Dario
>
>
>
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>



-- 
Damien Pollet
type less, do more [ | ] http://people.untyped.org/damien.pollet


From renggli at gmail.com  Thu Mar  3 11:14:49 2011
From: renggli at gmail.com (Lukas Renggli)
Date: Thu, 3 Mar 2011 11:14:49 +0100
Subject: Magritte description for e-mail
In-Reply-To: <AANLkTikUZBbYvkyE5-xm87snCfTt=ZL_BPKyTkZUorgN@mail.gmail.com>
References: <4225409E-3D6F-4001-8256-1167DDC480AC@tiscali.it>
	<AANLkTikUZBbYvkyE5-xm87snCfTt=ZL_BPKyTkZUorgN@mail.gmail.com>
Message-ID: <AANLkTi=90EGcg3QW7tdtx8OtvAsu9jS3mnTybqDSoz+d@mail.gmail.com>

I think very early versions of Magritte had an MAEmailDescription, but
later I found it was easier just to use a MAStringDescription with an
appropriate validation associated.

As for the report you can configure #reportColumnClass: on any
description to change how it is displayed int he report (I might be
wrong on the exact name of this message, as I don't have an image at
hand right now).

Lukas

On 3 March 2011 04:05, Damien Pollet <damien.pollet at gmail.com> wrote:
> Bumping this one?
>
> Is there a MAEmailDescription somewhere?
> I'm thinking something very much like MAStringDescription, but with a
> nice validator to ensure that the string complies with the RFCs on
> email addresses?
>
>
>
> On Tue, Jul 13, 2010 at 20:26, dtrussardi at tiscali.it
> <dtrussardi at tiscali.it> wrote:
>> Hi,
>>
>> ? ? ? ?i have some descriptions and one based on MAStringDescription for manage the e-mail reference.
>>
>> ? ? ? ?Now i'm interested to create a MAReport with fields for management email.
>>
>> ? ? ? ?Where for management ?i think a link to open new email directly from report ?:
>>
>> ? ? ? ? ? ? ? ? ? ? ? ?html anchor attributeAt: 'href' put: 'mailto:', anObject emailBase.
>>
>>
>> ? ? ? ?How i can do it ?
>>
>> ? ? ? ?Anyone create a specific MADescription for define e management ?email reference ?
>>
>>
>> ? ? ? ?Thank,
>>
>> ? ? ? ? ? ? ? ?Dario
>>
>>
>>
>>
>> _______________________________________________
>> Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>
>
>
>
> --
> Damien Pollet
> type less, do more [ | ] http://people.untyped.org/damien.pollet
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki



-- 
Lukas Renggli
www.lukas-renggli.ch


From renggli at gmail.com  Mon Mar  7 18:29:13 2011
From: renggli at gmail.com (Lukas Renggli)
Date: Mon, 7 Mar 2011 18:29:13 +0100
Subject: Enabling cookies causes callback links to incorrectly redirect in
	Firefox
In-Reply-To: <AANLkTinUXjKCu6PsuCh5gi31sHk+aGH-nY2CDf6S4-Q3@mail.gmail.com>
References: <AANLkTinsXW2sXEwjr3sJUYg6H8ftNS0yd4F=HqJuEcqd@mail.gmail.com>
	<AANLkTinUXjKCu6PsuCh5gi31sHk+aGH-nY2CDf6S4-Q3@mail.gmail.com>
Message-ID: <AANLkTikxnnRHdui78NnesnPaWn7aU2GOT3TaK7SGXvGC@mail.gmail.com>

Thanks for preparing the image and sorry for not looking into it
earlier. I will try to look into this problem tonight.

Lukas

On 27 February 2011 14:16, Nick Ager <nick.ager at gmail.com> wrote:
> I've uploaded an image which demonstration the issue:
> http://getitmade.com/static/Pier-2.zip
>
> Download and browse to http://localhost:8080/pier/call
> Click on the "++" or "--" links of the WACounter instance twice in Firefox.
> Notice that only in Firefox the second click of the callback take you
> to http://localhost:8080/pier/dates rather than incrementing the
> counter.
>
> On 26 February 2011 15:50, Nick Ager <nick.ager at gmail.com> wrote:
>> I've logged a bug: http://code.google.com/p/pier/issues/detail?id=132
>>
>> The text of the bug is:
>>
>>
>> Steps to recreate the bug:
>> 1) Download the recent build of Pier 2 -
>> http://hudson.lukas-renggli.ch/job/Pier%202/ - this bug is not present
>> in Pier with Seaside 2.8
>> 2) In a workspace execute the following:
>>
>> PREventDistribution register.
>> WAAdmin defaultDispatcher defaultHandler preferenceAt: #useCookies put: true.
>> (PRPathLookup start: (PRKernel instances anyOne) root path: '/call')
>> contents: 'In Firefox, try clicking on the counter
>>
>> +counter+'.
>> (PRPathLookup start: (PRKernel instances anyOne) root path: '/call') addChild: (
>> (PRComponent named: 'counter') componentClass: WACounter; yourself)
>>
>> 3) Within Firefox (I'm using 3.16.13) browse to
>> http://localhost:8080/pier/call - you should be on the "Call for
>> Contributions" page into which the above script embeds the standard
>> Seaside counter component in the page.
>> 4) Try clicking on the "++" or "--" links a couple of times and you'll
>> find yourself taken to http://localhost:8080/pier/dates and rather
>> than modifying the counter value.
>>
>> Here's my understanding of the bug:
>>
>> 1) Amongst other metadata Pier adds the following to the header: <link
>> href="/pier/dates" rel="next">
>> 2) In Firefox when cookies are enabled, the <link rel="next"> causes
>> firefox to issue at least two requests for each page; the first
>> request for the url specified, the second for the url specified in the
>> href of the <link rel="next">. Note this second request is not visible
>> in firebug (I added request logging to WAComancheRequestConverter). In
>> Safari or Chrome, I haven't seen any additional requests and so the
>> problem does not appear.
>> 3) The second request confuses the callback hander
>>
>> Unfortunately my understanding of how the callback handler should work
>> is limiting my ability to fix the bug. Any thoughts?
>>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>



-- 
Lukas Renggli
www.lukas-renggli.ch

From nick.ager at gmail.com  Mon Mar  7 19:00:03 2011
From: nick.ager at gmail.com (Nick Ager)
Date: Mon, 7 Mar 2011 18:00:03 +0000
Subject: Enabling cookies causes callback links to incorrectly redirect in
	Firefox
In-Reply-To: <AANLkTikxnnRHdui78NnesnPaWn7aU2GOT3TaK7SGXvGC@mail.gmail.com>
References: <AANLkTinsXW2sXEwjr3sJUYg6H8ftNS0yd4F=HqJuEcqd@mail.gmail.com>
	<AANLkTinUXjKCu6PsuCh5gi31sHk+aGH-nY2CDf6S4-Q3@mail.gmail.com>
	<AANLkTikxnnRHdui78NnesnPaWn7aU2GOT3TaK7SGXvGC@mail.gmail.com>
Message-ID: <AANLkTinyancc89aKT5a6tBGbErh9gmXKAhJtcXREwxDk@mail.gmail.com>

No problem - The simplest illustration of the problem is probably to
execute the following on a Pier 2 image (no need to download the image
I've prepared):

createSimplestPierIllustratingCallbackProblemInFirefox
	| app rootPage |

	rootPage := (PRPage named: 'rootPage')  contents: '*counter*
*shouldntgohere*'; yourself.
	rootPage localEnvironment: ((PRComponent named: 'contents')
componentClass: PRContentsWidget; yourself).
	rootPage addChild: ((PRComponent named: 'counter') componentClass:
WACounter; yourself).
	rootPage addChild: ((PRPage named: 'shouldntgohere') contents:
'shouldn''t be here'; yourself).
	
	PRKernel reset.
	app := PRPierFrame registerAsApplication: 'pier' kernel: (PRKernel
named: 'testKernel' root: rootPage).
	app preferenceAt: #useCookies put: true.



On 7 March 2011 17:29, Lukas Renggli <renggli at gmail.com> wrote:
> Thanks for preparing the image and sorry for not looking into it
> earlier. I will try to look into this problem tonight.
>
> Lukas
>
> On 27 February 2011 14:16, Nick Ager <nick.ager at gmail.com> wrote:
>> I've uploaded an image which demonstration the issue:
>> http://getitmade.com/static/Pier-2.zip
>>
>> Download and browse to http://localhost:8080/pier/call
>> Click on the "++" or "--" links of the WACounter instance twice in Firefox.
>> Notice that only in Firefox the second click of the callback take you
>> to http://localhost:8080/pier/dates rather than incrementing the
>> counter.
>>
>> On 26 February 2011 15:50, Nick Ager <nick.ager at gmail.com> wrote:
>>> I've logged a bug: http://code.google.com/p/pier/issues/detail?id=132
>>>
>>> The text of the bug is:
>>>
>>>
>>> Steps to recreate the bug:
>>> 1) Download the recent build of Pier 2 -
>>> http://hudson.lukas-renggli.ch/job/Pier%202/ - this bug is not present
>>> in Pier with Seaside 2.8
>>> 2) In a workspace execute the following:
>>>
>>> PREventDistribution register.
>>> WAAdmin defaultDispatcher defaultHandler preferenceAt: #useCookies put: true.
>>> (PRPathLookup start: (PRKernel instances anyOne) root path: '/call')
>>> contents: 'In Firefox, try clicking on the counter
>>>
>>> +counter+'.
>>> (PRPathLookup start: (PRKernel instances anyOne) root path: '/call') addChild: (
>>> (PRComponent named: 'counter') componentClass: WACounter; yourself)
>>>
>>> 3) Within Firefox (I'm using 3.16.13) browse to
>>> http://localhost:8080/pier/call - you should be on the "Call for
>>> Contributions" page into which the above script embeds the standard
>>> Seaside counter component in the page.
>>> 4) Try clicking on the "++" or "--" links a couple of times and you'll
>>> find yourself taken to http://localhost:8080/pier/dates and rather
>>> than modifying the counter value.
>>>
>>> Here's my understanding of the bug:
>>>
>>> 1) Amongst other metadata Pier adds the following to the header: <link
>>> href="/pier/dates" rel="next">
>>> 2) In Firefox when cookies are enabled, the <link rel="next"> causes
>>> firefox to issue at least two requests for each page; the first
>>> request for the url specified, the second for the url specified in the
>>> href of the <link rel="next">. Note this second request is not visible
>>> in firebug (I added request logging to WAComancheRequestConverter). In
>>> Safari or Chrome, I haven't seen any additional requests and so the
>>> problem does not appear.
>>> 3) The second request confuses the callback hander
>>>
>>> Unfortunately my understanding of how the callback handler should work
>>> is limiting my ability to fix the bug. Any thoughts?
>>>
>> _______________________________________________
>> Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>
>
>
>
> --
> Lukas Renggli
> www.lukas-renggli.ch
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

From renggli at gmail.com  Mon Mar  7 19:00:57 2011
From: renggli at gmail.com (Lukas Renggli)
Date: Mon, 7 Mar 2011 19:00:57 +0100
Subject: Enabling cookies causes callback links to incorrectly redirect in
	Firefox
In-Reply-To: <AANLkTikxnnRHdui78NnesnPaWn7aU2GOT3TaK7SGXvGC@mail.gmail.com>
References: <AANLkTinsXW2sXEwjr3sJUYg6H8ftNS0yd4F=HqJuEcqd@mail.gmail.com>
	<AANLkTinUXjKCu6PsuCh5gi31sHk+aGH-nY2CDf6S4-Q3@mail.gmail.com>
	<AANLkTikxnnRHdui78NnesnPaWn7aU2GOT3TaK7SGXvGC@mail.gmail.com>
Message-ID: <AANLkTi=mSXgoOV5jKR3TfSOxOTpUQET3nRSOS3jwjQ4b@mail.gmail.com>

That was a tricky one:

Unfortunately the Mozilla engine does prefetching of some "random"
links on websites
(https://developer.mozilla.org/en/Link_prefetching_FAQ). This
aggressive prefixing is a highly controversial topic even in the
FireFox community itself, because of all kinds of issues.

Now obviously this prefetching is generally something we don't want to
happen with Seaside applications as callbacks could unwillingly be
triggered. I changed the Seaside code to deny all prefetch requests in
WAApplication. This should solve the problem:

  Name: Seaside-Core-lr.711
  Author: lr
  Time: 7 March 2011, 6:52:15 pm
  UUID: 57d701cc-b90b-458d-9f7a-cf9a493a9997
  Ancestors: Seaside-Core-dkh.710

  - added a tester for prefetch requests

  Name: Seaside-Session-lr.135
  Author: lr
  Time: 7 March 2011, 6:53:50 pm
  UUID: 07b0af88-64b7-4bcb-8778-d14e448dddd9
  Ancestors: Seaside-Session-pmm.134

Lukas

-- 
Lukas Renggli
www.lukas-renggli.ch

From jfitzell at gmail.com  Wed Mar  9 09:15:46 2011
From: jfitzell at gmail.com (Julian Fitzell)
Date: Wed, 9 Mar 2011 08:15:46 +0000
Subject: [Seaside-dev] Re: Enabling cookies causes callback links to
	incorrectly redirect in Firefox
In-Reply-To: <AANLkTi=mSXgoOV5jKR3TfSOxOTpUQET3nRSOS3jwjQ4b@mail.gmail.com>
References: <AANLkTinsXW2sXEwjr3sJUYg6H8ftNS0yd4F=HqJuEcqd@mail.gmail.com>
	<AANLkTinUXjKCu6PsuCh5gi31sHk+aGH-nY2CDf6S4-Q3@mail.gmail.com>
	<AANLkTikxnnRHdui78NnesnPaWn7aU2GOT3TaK7SGXvGC@mail.gmail.com>
	<AANLkTi=mSXgoOV5jKR3TfSOxOTpUQET3nRSOS3jwjQ4b@mail.gmail.com>
Message-ID: <AANLkTikZHvXoVG3pa9f=UttmNv_Pxtgn9NN673toNmzt@mail.gmail.com>

This is, of course, part of the problem with using GET requests for
callbacks... shame you can't specify POST in an href anchor... :)

Julian

On Mon, Mar 7, 2011 at 6:00 PM, Lukas Renggli <renggli at gmail.com> wrote:
> That was a tricky one:
>
> Unfortunately the Mozilla engine does prefetching of some "random"
> links on websites
> (https://developer.mozilla.org/en/Link_prefetching_FAQ). This
> aggressive prefixing is a highly controversial topic even in the
> FireFox community itself, because of all kinds of issues.
>
> Now obviously this prefetching is generally something we don't want to
> happen with Seaside applications as callbacks could unwillingly be
> triggered. I changed the Seaside code to deny all prefetch requests in
> WAApplication. This should solve the problem:
>
> ?Name: Seaside-Core-lr.711
> ?Author: lr
> ?Time: 7 March 2011, 6:52:15 pm
> ?UUID: 57d701cc-b90b-458d-9f7a-cf9a493a9997
> ?Ancestors: Seaside-Core-dkh.710
>
> ?- added a tester for prefetch requests
>
> ?Name: Seaside-Session-lr.135
> ?Author: lr
> ?Time: 7 March 2011, 6:53:50 pm
> ?UUID: 07b0af88-64b7-4bcb-8778-d14e448dddd9
> ?Ancestors: Seaside-Session-pmm.134
>
> Lukas
>
> --
> Lukas Renggli
> www.lukas-renggli.ch
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>


From renggli at gmail.com  Wed Mar  9 17:28:16 2011
From: renggli at gmail.com (Lukas Renggli)
Date: Wed, 9 Mar 2011 17:28:16 +0100
Subject: Enabling cookies causes callback links to incorrectly redirect in
	Firefox
In-Reply-To: <AANLkTikZHvXoVG3pa9f=UttmNv_Pxtgn9NN673toNmzt@mail.gmail.com>
References: <AANLkTinsXW2sXEwjr3sJUYg6H8ftNS0yd4F=HqJuEcqd@mail.gmail.com>
	<AANLkTinUXjKCu6PsuCh5gi31sHk+aGH-nY2CDf6S4-Q3@mail.gmail.com>
	<AANLkTikxnnRHdui78NnesnPaWn7aU2GOT3TaK7SGXvGC@mail.gmail.com>
	<AANLkTi=mSXgoOV5jKR3TfSOxOTpUQET3nRSOS3jwjQ4b@mail.gmail.com>
	<AANLkTikZHvXoVG3pa9f=UttmNv_Pxtgn9NN673toNmzt@mail.gmail.com>
Message-ID: <AANLkTimAR=nFcAnUykAaMwBYV-02LpfG=m85X7hsiHdC@mail.gmail.com>

Somehow similar (and not adressed by my fix) is that Chrome is doing
"random" GET requests when you type an URL to provide auto-completion.
I assume that this is less likely to hit a Seaside callback, but we
should still pay attention.

Lukas

On Wednesday, 9 March 2011, Julian Fitzell <jfitzell at gmail.com> wrote:
> This is, of course, part of the problem with using GET requests for
> callbacks... shame you can't specify POST in an href anchor... :)
>
> Julian
>
> On Mon, Mar 7, 2011 at 6:00 PM, Lukas Renggli <renggli at gmail.com> wrote:
>> That was a tricky one:
>>
>> Unfortunately the Mozilla engine does prefetching of some "random"
>> links on websites
>> (https://developer.mozilla.org/en/Link_prefetching_FAQ). This
>> aggressive prefixing is a highly controversial topic even in the
>> FireFox community itself, because of all kinds of issues.
>>
>> Now obviously this prefetching is generally something we don't want to
>> happen with Seaside applications as callbacks could unwillingly be
>> triggered. I changed the Seaside code to deny all prefetch requests in
>> WAApplication. This should solve the problem:
>>
>> ?Name: Seaside-Core-lr.711
>> ?Author: lr
>> ?Time: 7 March 2011, 6:52:15 pm
>> ?UUID: 57d701cc-b90b-458d-9f7a-cf9a493a9997
>> ?Ancestors: Seaside-Core-dkh.710
>>
>> ?- added a tester for prefetch requests
>>
>> ?Name: Seaside-Session-lr.135
>> ?Author: lr
>> ?Time: 7 March 2011, 6:53:50 pm
>> ?UUID: 07b0af88-64b7-4bcb-8778-d14e448dddd9
>> ?Ancestors: Seaside-Session-pmm.134
>>
>> Lukas
>>
>> --
>> Lukas Renggli
>> www.lukas-renggli.ch
>> _______________________________________________
>> seaside-dev mailing list
>> seaside-dev at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>>
>

-- 
Lukas Renggli
www.lukas-renggli.ch


From nick.ager at gmail.com  Thu Mar 10 17:55:49 2011
From: nick.ager at gmail.com (Nick Ager)
Date: Thu, 10 Mar 2011 16:55:49 +0000
Subject: Halo view for Pier
Message-ID: <AANLkTik=haEOBobMz8oTh92UbS+TvAmRdaPS1SmEzMxa@mail.gmail.com>

Hi,

I remember seeing a demo of a halo view for editing Pier components
that I think Lukas and Tudor worked on. Can anyone point me at a
repository containing the code?

I'm interested in building UIs where the user can edit in-place rather
than editing in a form which then flips to the resulting screen.  I'm
considering using something like JQWidgetBox-JEditable-* in
http://www.squeaksource.com/JQueryWidgetBox. Anyone with experience of
doing this kind of thing?

Cheers

Nick

From renggli at gmail.com  Thu Mar 10 20:20:56 2011
From: renggli at gmail.com (Lukas Renggli)
Date: Thu, 10 Mar 2011 20:20:56 +0100
Subject: Halo view for Pier
In-Reply-To: <AANLkTik=haEOBobMz8oTh92UbS+TvAmRdaPS1SmEzMxa@mail.gmail.com>
References: <AANLkTik=haEOBobMz8oTh92UbS+TvAmRdaPS1SmEzMxa@mail.gmail.com>
Message-ID: <AANLkTimVNTfWL5nQPDgFHObX3pDBsp7O9Hq=fzL5kykJ@mail.gmail.com>

> I remember seeing a demo of a halo view for editing Pier components
> that I think Lukas and Tudor worked on. Can anyone point me at a
> repository containing the code?

The code is in 'Pier-EditorEnh', not sure if it has been ported to Pier 2.0 yet.

Lukas

-- 
Lukas Renggli
www.lukas-renggli.ch

From p3anoman at gmail.com  Fri Mar 11 02:02:30 2011
From: p3anoman at gmail.com (John McKeon)
Date: Thu, 10 Mar 2011 20:02:30 -0500
Subject: Halo view for Pier
In-Reply-To: <AANLkTik=haEOBobMz8oTh92UbS+TvAmRdaPS1SmEzMxa@mail.gmail.com>
References: <AANLkTik=haEOBobMz8oTh92UbS+TvAmRdaPS1SmEzMxa@mail.gmail.com>
Message-ID: <AANLkTi=31MCfyuneLzARKLL8c54VmbSAWorOLyK_4o+R@mail.gmail.com>

Hello Nick,
I have put a few jQuery widgets to use with Magritte. Most notably a
datepicker, a timepicker and an autocompleter for one-to-one relation
lookups. I am stuck on forms right now and avoiding the "flipping" back
effect.
The code is in the
Magritte2-Addons<http://source.lukas-renggli.ch/magritte2addons>repository
if you want to take a look.

John

On Thu, Mar 10, 2011 at 11:55 AM, Nick Ager <nick.ager at gmail.com> wrote:

> Hi,
>
> I remember seeing a demo of a halo view for editing Pier components
> that I think Lukas and Tudor worked on. Can anyone point me at a
> repository containing the code?
>
> I'm interested in building UIs where the user can edit in-place rather
> than editing in a form which then flips to the resulting screen.  I'm
> considering using something like JQWidgetBox-JEditable-* in
> http://www.squeaksource.com/JQueryWidgetBox. Anyone with experience of
> doing this kind of thing?
>
> Cheers
>
> Nick
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>



-- 
http://john-mckeon.us
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20110310/09429095/attachment.html>

From chaetal at gmail.com  Sun Mar 20 19:34:12 2011
From: chaetal at gmail.com (Dennis Schetinin)
Date: Sun, 20 Mar 2011 21:34:12 +0300
Subject: Import/export Pier widget in Pharo 1.1.1
Message-ID: <AANLkTikXP3j1bMDc9ZtW5AO=MWKjb3_oK=FRKwhL4afz@mail.gmail.com>

I load Seaside, Pier and addons with the script below. Most things (at least
those I've tried) works, but Import/Export widget. It simply ignores all
clicks on Import and Export buttons. What's wrong (how is it possible?!) and
how can I resolve this issue? BTW: Grease, Seaside, Magritte, Pier tests are
green.

TIA

Gofer new
    squeaksource: 'MetacelloRepository';
    package: 'ConfigurationOfSeaside30';
    load.
(Smalltalk at: #ConfigurationOfSeaside30) load.

Gofer new
    squeaksource: 'MetacelloRepository';
    package: 'ConfigurationOfPier2';
    load.
(Smalltalk at: #ConfigurationOfPier2) load.

project := ConfigurationOfPier2 project.
(project version: '2.0.7') load.

(Smalltalk at: #ConfigurationOfPier2)  project latestVersion load:
'Pier-Tests-Model'.

(Smalltalk at: #ConfigurationOfSeaside30) project latestVersion
    load: #('Magritte2 Tests' 'Pier2 Tests').


Gofer new
    squeaksource: 'MetacelloRepository';
    package: 'ConfigurationOfPierAddOns2';
    load.
(Smalltalk at: #ConfigurationOfPierAddOns2) project latestVersion load:
'ALL'.

PRDistribution register.

-- 
Dennis Schetinin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20110320/cd1750d0/attachment-0001.html>

From chaetal at gmail.com  Sun Mar 20 21:18:38 2011
From: chaetal at gmail.com (Dennis Schetinin)
Date: Sun, 20 Mar 2011 23:18:38 +0300
Subject: Import/export Pier widget in Pharo 1.1.1
In-Reply-To: <AANLkTikXP3j1bMDc9ZtW5AO=MWKjb3_oK=FRKwhL4afz@mail.gmail.com>
References: <AANLkTikXP3j1bMDc9ZtW5AO=MWKjb3_oK=FRKwhL4afz@mail.gmail.com>
Message-ID: <AANLkTi=0-u=teR83xSjaBSHpYN8-4P_V1Q6Sw9k78=gj@mail.gmail.com>

? I've found there's no form around Import and Export dialogs. Adding a form
around Export helps, but Import still does not as file selection callback is
still not invoked.

2011/3/20 Dennis Schetinin <chaetal at gmail.com>

> I load Seaside, Pier and addons with the script below. Most things (at
> least those I've tried) works, but Import/Export widget. It simply ignores
> all clicks on Import and Export buttons. What's wrong (how is it possible?!)
> and how can I resolve this issue? BTW: Grease, Seaside, Magritte, Pier tests
> are green.
>
> TIA
>
> Gofer new
>     squeaksource: 'MetacelloRepository';
>     package: 'ConfigurationOfSeaside30';
>     load.
> (Smalltalk at: #ConfigurationOfSeaside30) load.
>
> Gofer new
>     squeaksource: 'MetacelloRepository';
>     package: 'ConfigurationOfPier2';
>     load.
> (Smalltalk at: #ConfigurationOfPier2) load.
>
> project := ConfigurationOfPier2 project.
> (project version: '2.0.7') load.
>
> (Smalltalk at: #ConfigurationOfPier2)  project latestVersion load:
> 'Pier-Tests-Model'.
>
> (Smalltalk at: #ConfigurationOfSeaside30) project latestVersion
>     load: #('Magritte2 Tests' 'Pier2 Tests').
>
>
> Gofer new
>     squeaksource: 'MetacelloRepository';
>     package: 'ConfigurationOfPierAddOns2';
>     load.
> (Smalltalk at: #ConfigurationOfPierAddOns2) project latestVersion load:
> 'ALL'.
>
> PRDistribution register.
>
> --
> Dennis Schetinin
>



-- 
Dennis Schetinin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20110320/6d494748/attachment.html>

From chaetal at gmail.com  Tue Mar 22 06:10:10 2011
From: chaetal at gmail.com (Dennis Schetinin)
Date: Tue, 22 Mar 2011 08:10:10 +0300
Subject: Import old Pier site into Pier 2
Message-ID: <AANLkTi=SsFbQ_TxfgQ0U4Zi3zHUZjkHMrpHaXDTfc71q@mail.gmail.com>

How can I do that? Out-of-the-box it says: Unable to import: 'Global
"Sitemap" not found'.
-- 
Dennis Schetinin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20110322/b548d00c/attachment.html>

From renggli at gmail.com  Tue Mar 22 07:31:23 2011
From: renggli at gmail.com (Lukas Renggli)
Date: Tue, 22 Mar 2011 07:31:23 +0100
Subject: Import old Pier site into Pier 2
In-Reply-To: <AANLkTi=SsFbQ_TxfgQ0U4Zi3zHUZjkHMrpHaXDTfc71q@mail.gmail.com>
References: <AANLkTi=SsFbQ_TxfgQ0U4Zi3zHUZjkHMrpHaXDTfc71q@mail.gmail.com>
Message-ID: <AANLkTimPvKMWRNc_DtLmZgejPEyLY5GxzNuOf9cG4PDv@mail.gmail.com>

Sounds like you use the Sitemap plugin in your exported model, but the
plugin is not loaded in the image you import it to.

Lukas

On 22 March 2011 06:10, Dennis Schetinin <chaetal at gmail.com> wrote:
> How can I do that? Out-of-the-box it says: Unable to import: 'Global
> "Sitemap" not found'.
> --
> Dennis Schetinin
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>



-- 
Lukas Renggli
www.lukas-renggli.ch

From xekoukou at gmail.com  Thu Mar 24 20:53:28 2011
From: xekoukou at gmail.com (Apostolis Xekoukoulotakis)
Date: Thu, 24 Mar 2011 21:53:28 +0200
Subject: New Pier User
Message-ID: <AANLkTim9fkPb6UQ4XMEBRty9HZfuEUV8DivtcJDs4iBd@mail.gmail.com>

Hello fellows,

I would like to ask you if there is any documentation on creating new addons
for the pier systems, apart from the code.
Also if there is documentation for the already existant addons, for all the
addons.
Is the list http://source.lukas-renggli.ch/pieraddons/ complete or are there
more?

If there is no documentation what are the differences in creating components
for pier than for a general seaside web site.
Do i have to learn magritte?

-- 

This message and any attachments (the "message") are confidential,
intended solely for the addressee(s), and may contain legally
privileged information.
Any unauthorised use or dissemination is prohibited. E-mails are
susceptible to alteration.
I shall not be liable for the message if altered, changed or
falsified.


Sincerely yours,

     Apostolis Xekoukoulotakis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20110324/542aa0d7/attachment.html>

From renggli at gmail.com  Thu Mar 24 21:19:10 2011
From: renggli at gmail.com (Lukas Renggli)
Date: Thu, 24 Mar 2011 21:19:10 +0100
Subject: New Pier User
In-Reply-To: <AANLkTim9fkPb6UQ4XMEBRty9HZfuEUV8DivtcJDs4iBd@mail.gmail.com>
References: <AANLkTim9fkPb6UQ4XMEBRty9HZfuEUV8DivtcJDs4iBd@mail.gmail.com>
Message-ID: <AANLkTi=vXRmk9oA7dHP2C4mrX+canW-hbO91_LOtaO0x@mail.gmail.com>

Welcome!

> I would like to ask you if there is any documentation on creating new addons
> for the pier systems, apart from the code.

Not much. Most documentation is linked from the website
<http://www.piercms.com/>. Also some people (including myself) wrote
blog posts on extending Pier.

> Also if there is documentation for the already existant addons, for all the
> addons.
> Is the list?http://source.lukas-renggli.ch/pieraddons/?complete or are there
> more?

This is a code repository, there are many other extensions if you
search on www.squeaksource.com.

> If there is no documentation what are the differences in creating components
> for pier than for a general seaside web site.

Any Seaside component is a Pier component and can be directly plugged
into a Pier site. However, if you want your Seaside component be able
to interact and reflect on Pier it needs to know about Pier, for
example by subclassing PRWidget which is a subclass of WAComponent
with some added functionality. This is the only difference.

> Do i have to learn magritte?

Not necessarily, but it will make your life much simpler.

Lukas

-- 
Lukas Renggli
www.lukas-renggli.ch


From xekoukou at gmail.com  Fri Mar 25 07:09:54 2011
From: xekoukou at gmail.com (Apostolis Xekoukoulotakis)
Date: Fri, 25 Mar 2011 08:09:54 +0200
Subject: newbie help...
Message-ID: <AANLkTinec6Btn7+98+0CFr7BV_oDp5hMsU9tcYDw-2kK@mail.gmail.com>

I would like someone to verify this..

I want to create a plugin that would be part of the enviroment of a number
of pages.
the plugin wants to know the user that is logged in, the owner of the page
that is viewing and the absolute path of the page.

So  to get this i ll put in my component these lines right?

PRContext user
PRContext structure owner
PRContext structure absolutePath

I guess that the absolute path is the only way to identfy a page.

Another problem i have is with persistency..
I googled and found that lots of people have already talked about it.
For me and i think every new programmer, it is the biggest obstacle for
using Pier...
Pier is very powerfull , easy to use and programm due to its smalltalk
foundation. The code is so easily understood and the reusability of the code
is phenomenal.

So If this persistency problem is solved with the new programmer in mind,
the one that just wants its objects to save, no questions asked, Pier would
rock.

So to use Pier, the only option for me is to go for a non-free DB like
gemstoneS. All i have to do is tell Pier to save objects and gemstone will
do it automatically without me changing any of the code, right?
Unfortunately at the time of writing i have access to a 32bit CPU so i cant
check for myself..

I know there are other options like magma, but from what i understand you
have to understand the underlying structure and i dont want to.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20110325/d2c8fd99/attachment-0001.html>

From nick.ager at gmail.com  Fri Mar 25 10:00:28 2011
From: nick.ager at gmail.com (Nick Ager)
Date: Fri, 25 Mar 2011 09:00:28 +0000
Subject: newbie help...
In-Reply-To: <AANLkTinec6Btn7+98+0CFr7BV_oDp5hMsU9tcYDw-2kK@mail.gmail.com>
References: <AANLkTinec6Btn7+98+0CFr7BV_oDp5hMsU9tcYDw-2kK@mail.gmail.com>
Message-ID: <AANLkTinGn=1=FPX7ueB1zJrXa=jJqW4bvsht-8Hf_JNA@mail.gmail.com>

Hi Apostolis,

I want to create a plugin that would be part of the enviroment of a number
> of pages.
> the plugin wants to know the user that is logged in, the owner of the page
> that is viewing and the absolute path of the page.
>
> So  to get this i ll put in my component these lines right?
>
> PRContext user
> PRContext structure owner
> PRContext structure absolutePath
>

If you derive your component from PRWidget rather than WAComponent you have
access to #context, see for example PUSecurityWidget


> I guess that the absolute path is the only way to identfy a page.
>
> Another problem i have is with persistency..
> I googled and found that lots of people have already talked about it.
> For me and i think every new programmer, it is the biggest obstacle for
> using Pier...
> Pier is very powerfull , easy to use and programm due to its smalltalk
> foundation. The code is so easily understood and the reusability of the code
> is phenomenal.
>
> So If this persistency problem is solved with the new programmer in mind,
> the one that just wants its objects to save, no questions asked, Pier would
> rock.
>
> So to use Pier, the only option for me is to go for a non-free DB like
> gemstoneS. All i have to do is tell Pier to save objects and gemstone will
> do it automatically without me changing any of the code, right?
> Unfortunately at the time of writing i have access to a 32bit CPU so i cant
> check for myself..
>
> I know there are other options like magma, but from what i understand you
> have to understand the underlying structure and i dont want to.
>

If you go the Gemstone route, for deployment you can use a free Amazon EC2
micro instance. See:
http://nickager.com/blog/Screencast-creating-a-new-instance-based-on-pre-configured-AMI/and
http://nickager.com/blog/Create-a-free-Gemstone-server-in-the-cloud-in-10-minutes/

Hope this helps

Nick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20110325/1fdaa9f5/attachment.html>

From dhenrich at vmware.com  Fri Mar 25 17:05:52 2011
From: dhenrich at vmware.com (Dale Henrichs)
Date: Fri, 25 Mar 2011 09:05:52 -0700
Subject: newbie help...
In-Reply-To: <AANLkTinec6Btn7+98+0CFr7BV_oDp5hMsU9tcYDw-2kK@mail.gmail.com>
References: <AANLkTinec6Btn7+98+0CFr7BV_oDp5hMsU9tcYDw-2kK@mail.gmail.com>
Message-ID: <DE3F9404-A13B-41AD-A384-35BFD57EAF31@vmware.com>


On Mar 24, 2011, at 11:09 PM, Apostolis Xekoukoulotakis wrote:

> I would like someone to verify this..
> 
> I want to create a plugin that would be part of the enviroment of a number of pages.
> the plugin wants to know the user that is logged in, the owner of the page that is viewing and the absolute path of the page.
> 
> So  to get this i ll put in my component these lines right?
> 
> PRContext user
> PRContext structure owner
> PRContext structure absolutePath
> 
> I guess that the absolute path is the only way to identfy a page.
> 
> Another problem i have is with persistency..
> I googled and found that lots of people have already talked about it.
> For me and i think every new programmer, it is the biggest obstacle for using Pier...
> Pier is very powerfull , easy to use and programm due to its smalltalk foundation. The code is so easily understood and the reusability of the code is phenomenal.
> 
> So If this persistency problem is solved with the new programmer in mind, the one that just wants its objects to save, no questions asked, Pier would rock.
> 
> So to use Pier, the only option for me is to go for a non-free DB like gemstoneS. All i have to do is tell Pier to save objects and gemstone will do it automatically without me changing any of the code, right?
> Unfortunately at the time of writing i have access to a 32bit CPU so i cant check for myself..

GemStone has a very generous free for commercial use license...The majority of folks using GemStone develop their applications in Pharo and deploy them in GemStone, so you can do your initial development in Pharo on your 32bit machine ... GemStone's persistence model is based on the same concept as image persistence, instead of saving your image, you do a commit and in the case of Pier the GemStone transactions are handled in the Seaside framework, so you don't have to add any special code to your Pier application to take advantage of GemStone persistence.

> 
> I know there are other options like magma, but from what i understand you have to understand the underlying structure and i dont want to.
> 
> 
> 
> <ATT00001..txt>



From sergiolist at village-buzz.com  Fri Mar 25 21:31:23 2011
From: sergiolist at village-buzz.com (sergio_101)
Date: Fri, 25 Mar 2011 16:31:23 -0400
Subject: comments turned off?
Message-ID: <AANLkTimoc2EGRCXwh6pHBqREL8jB9Z8fNPOqFBOqKcvh@mail.gmail.com>

i was just about to install disqus on my site, and as i went to turn
off the comments on my site, i realized that they were not turned on!
this is fine, as i won't have to figure how to turn them off, but i
was just wondering how they got turned off / disabled to begin with..

very strange! any ideas?

thanks!

-- 
----
peace,
sergio
photographer, journalist, visionary

http://www.CodingForHire.com
http://www.coffee-black.com
http://www.painlessfrugality.com
http://www.twitter.com/sergio_101
http://www.facebook.com/sergio101

From renggli at gmail.com  Sat Mar 26 07:23:39 2011
From: renggli at gmail.com (Lukas Renggli)
Date: Sat, 26 Mar 2011 07:23:39 +0100
Subject: comments turned off?
In-Reply-To: <AANLkTimoc2EGRCXwh6pHBqREL8jB9Z8fNPOqFBOqKcvh@mail.gmail.com>
References: <AANLkTimoc2EGRCXwh6pHBqREL8jB9Z8fNPOqFBOqKcvh@mail.gmail.com>
Message-ID: <AANLkTinvZqz=VOzxqnkB5tWR3TPAufEdWscfwsvZ82BX@mail.gmail.com>

If you edit the blog you can configure for how long after the post
comments are allowed. If set to 0 comments are disabled.

Cheers,
Lukas

On Friday, 25 March 2011, sergio_101 <sergiolist at village-buzz.com> wrote:
> i was just about to install disqus on my site, and as i went to turn
> off the comments on my site, i realized that they were not turned on!
> this is fine, as i won't have to figure how to turn them off, but i
> was just wondering how they got turned off / disabled to begin with..
>
> very strange! any ideas?
>
> thanks!
>
> --
> ----
> peace,
> sergio
> photographer, journalist, visionary
>
> http://www.CodingForHire.com
> http://www.coffee-black.com
> http://www.painlessfrugality.com
> http://www.twitter.com/sergio_101
> http://www.facebook.com/sergio101
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

-- 
Lukas Renggli
www.lukas-renggli.ch

From sergiolist at village-buzz.com  Mon Mar 28 00:36:19 2011
From: sergiolist at village-buzz.com (sergio_101)
Date: Sun, 27 Mar 2011 18:36:19 -0400
Subject: comments turned off?
In-Reply-To: <AANLkTinvZqz=VOzxqnkB5tWR3TPAufEdWscfwsvZ82BX@mail.gmail.com>
References: <AANLkTimoc2EGRCXwh6pHBqREL8jB9Z8fNPOqFBOqKcvh@mail.gmail.com>
	<AANLkTinvZqz=VOzxqnkB5tWR3TPAufEdWscfwsvZ82BX@mail.gmail.com>
Message-ID: <AANLkTim=oKkzve7s72Kis2RQj+yK0Sbfy5wWOCnUKDjd@mail.gmail.com>

On Sat, Mar 26, 2011 at 2:23 AM, Lukas Renggli <renggli at gmail.com> wrote:
> If you edit the blog you can configure for how long after the post
> comments are allowed. If set to 0 comments are disabled.
>

ah! found it!

what units is that in?

thanks!


-- 
----
peace,
sergio
photographer, journalist, visionary

http://www.CodingForHire.com
http://www.coffee-black.com
http://www.painlessfrugality.com
http://www.twitter.com/sergio_101
http://www.facebook.com/sergio101

From estebanlm at gmail.com  Thu Mar 31 17:07:16 2011
From: estebanlm at gmail.com (Esteban Lorenzano)
Date: Thu, 31 Mar 2011 12:07:16 -0300
Subject: adding style with images to pier
Message-ID: <DC97DB65-CA56-4458-BC37-164B7A9C23CD@gmail.com>

Hi,
I wonder how can I add a css who references an image to a page in Pier.

For example, I have this style: 

.aclass {
	background-image: url(background.png);
}

so... I upload the style to /system/components/css/style.css, and I change my page to use that css. 

So... how can I add the image file? I tried by creating a /system/components/css/background.png file, but it does not works :(

Also... I would like to add some meta information (a couple of <link> rels), and no idea how to do it... any idea?

Thanks,
Esteban