From lenglish5 at cox.net  Wed Aug  4 01:36:31 2010
From: lenglish5 at cox.net (Lawson English)
Date: Tue, 03 Aug 2010 16:36:31 -0700
Subject: discussion forum based on seaside/pier?
Message-ID: <4C58A7FF.3010109@cox.net>

Does such a beastie exist?


Lawson

From renggli at gmail.com  Thu Aug  5 18:52:39 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Thu, 5 Aug 2010 18:52:39 +0200
Subject: [Seaside] discussion forum based on seaside/pier?
In-Reply-To: <4C58A7FF.3010109@cox.net>
References: <4C58A7FF.3010109@cox.net>
Message-ID: <AANLkTimJAzkYXxUdEFoaEJQkep3DRSx4oAtxz6s_=HH=@mail.gmail.com>

There is <http://scg.unibe.ch/archive/projects/Roth04a.pdf>, but I
don't know if it is still maintained and/or if it works with the
latest Seaside/Magritte/Pier?

Lukas

On 4 August 2010 01:36, Lawson English <lenglish5 at cox.net> wrote:
> Does such a beastie exist?
>
>
> Lawson
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>



-- 
Lukas Renggli
www.lukas-renggli.ch

From renggli at gmail.com  Thu Aug  5 20:55:52 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Thu, 5 Aug 2010 20:55:52 +0200
Subject: Magritte2
In-Reply-To: <AANLkTinzTgrP=J6p93jSTW4jFvgWvMGSpcDpuW5pXa93@mail.gmail.com>
References: <AANLkTinzTgrP=J6p93jSTW4jFvgWvMGSpcDpuW5pXa93@mail.gmail.com>
Message-ID: <AANLkTinW1Ne4WBDE9Wgno0K_j6vFnuh2bm3rWhkvy6qk@mail.gmail.com>

Hi Elliot,

I reply to the Magritte list, because other people might be interested
or provide other answers too:

> I'm wanting to do something like http://www.nakedobjects.net but with
> Pharo/Magma/Magritte2 (and later seaside for web view). ?I've looked at the
> Magritte tutorial that is dated Feb 5, 2007 but it seems to be a little
> outdated and geared specifically towards seaside. ?Is there a later tutorial
> for Magritte or other material that I can reference to learn it? ?I've
> loaded the Magritte2 package from squeaksource and it looks a little
> daunting!

The tutorial is not outdated, Magritte was relatively stable in the
past few years. I've been repeatedly using the tutorial in the past
few years in various training sessions.

The Seaside book has a chapter on Magritte:
<http://book.seaside.st/book/advanced/magritte>; and of course the
other links from <http://www.lukas-renggli.ch/smalltalk/magritte>.

The package Magritte-Core can be used without Seaside, in fact there
is nothing that depends on Seaside. However, most people (including
myself) have been using Magritte in the context of Seaside, that's why
the support there is the most sophisticated. There is Magritte-Morphic
that creates basic Morphic interfaces.

> Is Pharo/Magma/Magritte2 the right stack for this type of project in your
> opinion?http://www.lukas-renggli.ch/smalltalk/magritte

Sure, I almost use it in any project.

Lukas

> Thanks in advance for any information you can provide.
> Elliot
>



-- 
Lukas Renggli
www.lukas-renggli.ch


From razavi at acm.org  Fri Aug  6 11:26:56 2010
From: razavi at acm.org (Reza Razavi)
Date: Fri, 06 Aug 2010 11:26:56 +0200
Subject: Embedding JQuery examples using Pier Components  
Message-ID: <89dhun$2mkl9t@smtp.pt.lu>

Hi,

Starting with the latest one-click Seaside image, I registered a Pier 
application following [1], then successfully embedded on-line many of 
JQuery examples using Pier Components. It's impressive to observe how 
smoothly it works! I only had a minor issue that is reported in [2].

Regards,
Reza

[1] Procedure for registering a Pier application for the needs of the 
above tests:
    A) Add the following libraries to PRPierFrame class >> 
configureApplication: JQDeploymentLibrary, JQUiDeploymentLibrary, and 
JQUiLightnessTheme
    B) Execute PRDistribution new register

[2] When embedding the JQWidgetBoxJQToolsTabsExample, the following 
sequence raises MessageNotUnderstood
    A) JQWidgetBoxJQToolsTabsExample >> updateRoot:
    B) In the #removeAllSuchThat: loop, the message #attributes is 
sent to a WAOpeningConditionalComment


From renggli at gmail.com  Mon Aug  9 08:42:09 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Mon, 9 Aug 2010 08:42:09 +0200
Subject: Fw: small Pier question? 8-Aug
In-Reply-To: <523486.53542.qm@web52303.mail.re2.yahoo.com>
References: <523486.53542.qm@web52303.mail.re2.yahoo.com>
Message-ID: <AANLkTinm4Jnc7Ub-rkrGK0RmSEvsb9MCH=FkOC0mqO69@mail.gmail.com>

Welcome. What is your question?

Lukas

On Monday, August 9, 2010, c parks <crparks_24 at yahoo.com> wrote:
> Another attempt....
>
> Thanks!
>
> --- On Sun, 8/8/10, smallwiki-owner at iam.unibe.ch <smallwiki-owner at iam.unibe.ch> wrote:
>
> From: smallwiki-owner at iam.unibe.ch <smallwiki-owner at iam.unibe.ch>
> Subject: small Pier question?  8-Aug
> To: crparks_24 at yahoo.com
> Date: Sunday, August 8, 2010, 10:52 PM
>
> You are not allowed to post to this mailing list, and your message has
> been automatically rejected.? If you think that your messages are
> being rejected in error, contact the mailing list owner at
> smallwiki-owner at iam.unibe.ch?<http://mc/compose?to=smallwiki-owner at iam.unibe.ch>.
>
>
>

-- 
Lukas Renggli
www.lukas-renggli.ch


From lenglish5 at cox.net  Mon Aug  9 10:49:43 2010
From: lenglish5 at cox.net (Lawson English)
Date: Mon, 09 Aug 2010 01:49:43 -0700
Subject: [Seaside] discussion forum based on seaside/pier?
In-Reply-To: <AANLkTimJAzkYXxUdEFoaEJQkep3DRSx4oAtxz6s_=HH=@mail.gmail.com>
References: <4C58A7FF.3010109@cox.net>
	<AANLkTimJAzkYXxUdEFoaEJQkep3DRSx4oAtxz6s_=HH=@mail.gmail.com>
Message-ID: <4C5FC127.80305@cox.net>

Thanks. Reading now.

L.

On 8/5/10 9:52 AM, Lukas Renggli wrote:
> There is<http://scg.unibe.ch/archive/projects/Roth04a.pdf>, but I
> don't know if it is still maintained and/or if it works with the
> latest Seaside/Magritte/Pier?
>
> Lukas
>
> On 4 August 2010 01:36, Lawson English<lenglish5 at cox.net>  wrote:
>    
>> Does such a beastie exist?
>>
>>
>> Lawson
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>>      
>
>
>    


From stephan at stack.nl  Tue Aug 10 16:52:55 2010
From: stephan at stack.nl (Stephan Eggermont)
Date: Tue, 10 Aug 2010 16:52:55 +0200
Subject: Magritte2
In-Reply-To: <AANLkTinW1Ne4WBDE9Wgno0K_j6vFnuh2bm3rWhkvy6qk@mail.gmail.com>
References: <AANLkTinzTgrP=J6p93jSTW4jFvgWvMGSpcDpuW5pXa93@mail.gmail.com>
	<AANLkTinW1Ne4WBDE9Wgno0K_j6vFnuh2bm3rWhkvy6qk@mail.gmail.com>
Message-ID: <0A0C51C5-9181-4B95-9A6D-5063A53C811E@stack.nl>


On 5 aug 2010, at 20:55, Lukas Renggli wrote:

> Hi Elliot,
> 
> I reply to the Magritte list, because other people might be interested
> or provide other answers too:
> 
>> I'm wanting to do something like http://www.nakedobjects.net but with
>> Pharo/Magma/Magritte2 (and later seaside for web view).

If you're interested in a naked objects style interface, you might
be interested in maui, jmatter and glamour. In the early days of NakedObjects
I was a contributor (and to Sanssouci). 

They work fairly well for simple domain models, but are weak when you use 
type objects/knowledge level. 

You'll probably want to make some changes in describing relationships
in Magritte, and add ActionDescriptions.

Stephan

From razavi at acm.org  Tue Aug 10 23:41:59 2010
From: razavi at acm.org (Reza Razavi)
Date: Tue, 10 Aug 2010 23:41:59 +0200
Subject: Optimizing #isRestful
Message-ID: <89dhun$2o7rm5@smtp.pt.lu>

Hi Lukas, all,

#isRestful is called by PRContext >> urlOn:, typically via the 
PRMenuRenderer (so, upon every page refresh), which delegates to the 
current Command, which, in the case of PRViewCommand, delegates in 
turn to its 'viewComponent'.

To avoid creating an instance of the #viewComponentClass just to 
check if its #isRestful, would it make sense to:
1) Move to the class side the four occurrences of #isRestful 
implementation in the PRViewComponent hierarchy, and then
2) Change the code in PRViewCommand to delegate to #viewComponentClass?

Regards,
Reza


From lenglish5 at cox.net  Sat Aug 14 00:51:01 2010
From: lenglish5 at cox.net (Lawson English)
Date: Fri, 13 Aug 2010 15:51:01 -0700
Subject: Step by step on how to create pier-based blog?
Message-ID: <4C65CC55.40204@cox.net>

http://www.lukas-renggli.ch/blog/installation

The video doesn't load in either safari, firefox or chrome on my Mac.


Are there more resources I should be looking at for this?



Lawson

From lenglish5 at cox.net  Sat Aug 14 01:24:59 2010
From: lenglish5 at cox.net (Lawson English)
Date: Fri, 13 Aug 2010 16:24:59 -0700
Subject: starting pier from one-click image?
Message-ID: <4C65D44B.2060307@cox.net>

so using the oneclick squeak 4.1 image, there's no default entry point 
for pier, nor any explanation of how to set one up.


Lawson

From lenglish5 at cox.net  Sat Aug 14 07:16:45 2010
From: lenglish5 at cox.net (Lawson English)
Date: Fri, 13 Aug 2010 22:16:45 -0700
Subject: Step by step on how to create pier-based blog?
In-Reply-To: <4C65CC55.40204@cox.net>
References: <4C65CC55.40204@cox.net>
Message-ID: <4C6626BD.9080407@cox.net>

On 8/13/10 3:51 PM, Lawson English wrote:
> http://www.lukas-renggli.ch/blog/installation
>
> The video doesn't load in either safari, firefox or chrome on my Mac.
>
>
> Are there more resources I should be looking at for this?
>

OK, so managed to get Pier installed into the squeak 4.1 one-click 
distribution and clicked on blog. I can leave a comment but I get stuck 
in a loop where I can't cancel the comment request.  Has pier, 
especially the blog component, been tested with the 4.1 one click 
distribution?


Lawson

From nick.ager at gmail.com  Sat Aug 14 07:52:52 2010
From: nick.ager at gmail.com (Nick Ager)
Date: Sat, 14 Aug 2010 06:52:52 +0100
Subject: Step by step on how to create pier-based blog?
In-Reply-To: <4C6626BD.9080407@cox.net>
References: <4C65CC55.40204@cox.net>
	<4C6626BD.9080407@cox.net>
Message-ID: <AANLkTincdCvo27qhedNvSp-8f54u0ZH0NtsNxAEnh5Z2@mail.gmail.com>

Hi Lawson,



>>
> OK, so managed to get Pier installed into the squeak 4.1 one-click
> distribution and clicked on blog. I can leave a comment but I get stuck in a
> loop where I can't cancel the comment request.  Has pier, especially the
> blog component, been tested with the 4.1 one click distribution?
>
>
>
Some ways of registering Pier:

1) PRPierFrame registerAsApplication: 'pier' kernel:  PRDistribution new
kernel.
2) PRPierFrame registerAsApplication: 'pier' kernel: (PRKernel named:
'aSimpleKernel').
3) PRPierFrame registerAsApplication: 'pier' kernel: (PRKernel new root:
(PRPage new title: 'test title'; contents: 'Pier on Seaside 3.0'; name:
'testPage'); name: 'aVerySimpleKernel').

AFAIK all Pier development takes place on Pharo - might be worth trying the
Pharo Seaside30rc and seeing if you have the same problem there.

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

From renggli at gmail.com  Sat Aug 14 08:01:44 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Sat, 14 Aug 2010 08:01:44 +0200
Subject: [Seaside] starting pier from one-click image?
In-Reply-To: <4C65D44B.2060307@cox.net>
References: <4C65D44B.2060307@cox.net>
Message-ID: <AANLkTikiWoejdaq61YsAvWN-YFFCaM5DkioPqvu8DhGi@mail.gmail.com>

There is no one-click image for Squeak 4.1 AFAIK. Please try the
official image from piercms.com, or a daily build from
hudson.lukas-renggli.ch.

Lukas

On Saturday, August 14, 2010, Lawson English <lenglish5 at cox.net> wrote:
> so using the oneclick squeak 4.1 image, there's no default entry point for pier, nor any explanation of how to set one up.
>
>
> Lawson
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

-- 
Lukas Renggli
www.lukas-renggli.ch

From lenglish5 at cox.net  Sat Aug 14 08:35:06 2010
From: lenglish5 at cox.net (Lawson English)
Date: Fri, 13 Aug 2010 23:35:06 -0700
Subject: [Seaside] starting pier from one-click image?
In-Reply-To: <AANLkTikiWoejdaq61YsAvWN-YFFCaM5DkioPqvu8DhGi@mail.gmail.com>
References: <4C65D44B.2060307@cox.net>
	<AANLkTikiWoejdaq61YsAvWN-YFFCaM5DkioPqvu8DhGi@mail.gmail.com>
Message-ID: <4C66391A.5080703@cox.net>

On 8/13/10 11:01 PM, Lukas Renggli wrote:
> There is no one-click image for Squeak 4.1 AFAIK. Please try the
> official image from piercms.com, or a daily build from
> hudson.lukas-renggli.ch.
>    

That you don't know about it could explain why pier has no set entry 
point in it and why the pier blog component has problems with it.


http://www.squeak.org/Documentation/Installation/#h-5

The homepage for the Seaside web framework is here.



Download Seaside 3.0:

Easy Install (recommended for new users)
Expert Install (just the image and changes)

From nick.ager at gmail.com  Sat Aug 14 09:07:58 2010
From: nick.ager at gmail.com (Nick Ager)
Date: Sat, 14 Aug 2010 08:07:58 +0100
Subject: Step by step on how to create pier-based blog?
In-Reply-To: <AANLkTincdCvo27qhedNvSp-8f54u0ZH0NtsNxAEnh5Z2@mail.gmail.com>
References: <4C65CC55.40204@cox.net> <4C6626BD.9080407@cox.net>
	<AANLkTincdCvo27qhedNvSp-8f54u0ZH0NtsNxAEnh5Z2@mail.gmail.com>
Message-ID: <AANLkTi=qx+-B3vHq62Qo=YHoh0Ce1md94LL+8ipwjNnD@mail.gmail.com>

>
> Some ways of registering Pier:
>
> 1) PRPierFrame registerAsApplication: 'pier' kernel:  PRDistribution new
> kernel.
> 2) PRPierFrame registerAsApplication: 'pier' kernel: (PRKernel named:
> 'aSimpleKernel').
> 3) PRPierFrame registerAsApplication: 'pier' kernel: (PRKernel new root:
> (PRPage new title: 'test title'; contents: 'Pier on Seaside 3.0'; name:
> 'testPage'); name: 'aVerySimpleKernel').
>
> AFAIK all Pier development takes place on Pharo - might be worth trying the
> Pharo Seaside30rc and seeing if you have the same problem there.
>
>
> On 14 August 2010 07:35, Lawson English <lenglish5 at cox.net> wrote:

> On 8/13/10 11:01 PM, Lukas Renggli wrote:
>
>> There is no one-click image for Squeak 4.1 AFAIK. Please try the
>> official image from piercms.com, or a daily build from
>> hudson.lukas-renggli.ch.
>>
>>
>
> That you don't know about it could explain why pier has no set entry point
> in it and why the pier blog component has problems with it.
>
>
How about downloading one of Lucas' daily builds or use Seaside30rc on Pharo
and register Pier with:
   PRPierFrame registerAsApplication: 'pier' kernel:  PRDistribution new
kernel

If you can reproduce the problem on Pharo then send an error report to the
Pier mailing list. If your error is only present on the Squeak build, then
report the problem on the squeak mailing list.

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

From renggli at gmail.com  Sat Aug 14 09:42:17 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Sat, 14 Aug 2010 09:42:17 +0200
Subject: [Seaside] starting pier from one-click image?
In-Reply-To: <4C66391A.5080703@cox.net>
References: <4C65D44B.2060307@cox.net>
	<AANLkTikiWoejdaq61YsAvWN-YFFCaM5DkioPqvu8DhGi@mail.gmail.com>
	<4C66391A.5080703@cox.net>
Message-ID: <AANLkTim6FDEPRn20+zjbceuJjSy+_E_prO+J8YR4VtdB@mail.gmail.com>

>> There is no one-click image for Squeak 4.1 AFAIK. Please try the
>> official image from piercms.com, or a daily build from
>> hudson.lukas-renggli.ch.
>
> That you don't know about it could explain why pier has no set entry point
> in it and why the pier blog component has problems with it.

I am not aware of somebody using/supporting/testing Pier on Squeak.

Let me know if we need to change something to make
Pier/Magritte/Seaside/Grease more portable.

> http://www.squeak.org/Documentation/Installation/#h-5
>
> The homepage for the Seaside web framework is here.

You could try the scripts I use on my build-server:

   http://github.com/renggli/builder/tree/master/scripts/

Lukas

-- 
Lukas Renggli
www.lukas-renggli.ch

From razavi at acm.org  Sat Aug 14 09:48:57 2010
From: razavi at acm.org (Reza Razavi)
Date: Sat, 14 Aug 2010 09:48:57 +0200
Subject: Step by step on how to create pier-based blog?
In-Reply-To: <AANLkTi=qx+-B3vHq62Qo=YHoh0Ce1md94LL+8ipwjNnD@mail.gmail.c
 om>
References: <4C65CC55.40204@cox.net> <4C6626BD.9080407@cox.net>
	<AANLkTincdCvo27qhedNvSp-8f54u0ZH0NtsNxAEnh5Z2@mail.gmail.com>
	<AANLkTi=qx+-B3vHq62Qo=YHoh0Ce1md94LL+8ipwjNnD@mail.gmail.com>
Message-ID: <89dhun$2pb696@smtp.pt.lu>

At 09:07 14/08/2010, Nick Ager wrote:
>How about downloading one of Lucas' daily builds or use Seaside30rc on Pharo

Hi Lawson, Nick, all,

I actually downloaded and tried both. I didn't 
notice the following issue you mentioned in a previous email.

>I can leave a comment but I get stuck in a loop 
>where I can't cancel the comment request.

My understanding is that you refer a 
functionality that is not an endless loop, but 
actually part of the blog's design. The "leave a 
comment" dialog appears systematically, even if 
you cancel it, as far as the post still accepts comments (there is a timeout).

This being said, I observed better development 
performances with the Hudson download. It seems 
that the Seaside30rc on Pharo package comes with 
some development packages pre-loaded that 
sometimes make you wait a while before accepting 
a method, or rendering a text typed in a 
workspace, etc. (I'm still under Vista and not OSX, sorry for that).

With the Husdon image, Build #200 (13 ao?t 2010 
10:40:23), I only had a small issue with the 
settings dialog. MCConfiguration >> 
updateFromImage seems missing. From a comparison 
of the packages for MonticelloConfigurations 
between Seaside30rc on Pharo and Hudson images in 
http://www.squeaksource.com/Pharo, it appears 
that the version of Hudson is outdated. I loaded 
the latest one 
(MonticelloConfigurations-StephaneDucasse.61) and 
it seems working just fine now.

Hoping this helps,
Regards,
Reza






From andreas.raab at gmx.de  Sat Aug 14 17:19:27 2010
From: andreas.raab at gmx.de (Andreas Raab)
Date: Sat, 14 Aug 2010 08:19:27 -0700
Subject: Squeak 4.1 / Seaside / "One-Click" images
In-Reply-To: <AANLkTikiWoejdaq61YsAvWN-YFFCaM5DkioPqvu8DhGi@mail.gmail.com>
References: <4C65D44B.2060307@cox.net>
	<AANLkTikiWoejdaq61YsAvWN-YFFCaM5DkioPqvu8DhGi@mail.gmail.com>
Message-ID: <4C66B3FF.2030509@gmx.de>

On 8/13/2010 11:01 PM, Lukas Renggli wrote:
> There is no one-click image for Squeak 4.1 AFAIK.

Oh sure there is. Right here:
http://www.seaside.st/download/squeak
http://www.squeak.org/Documentation/Installation/#h-5
http://ftp.squeak.org/various_images/seaside/Squeak4.1/

These were further referenced in several blog posts:
http://news.squeak.org/2010/07/23/seaside-3-0rc-one-click-image/
http://squeakingalong.wordpress.com/2010/07/24/new-squeak-4-1-seaside-images/
http://squeakingalong.wordpress.com/2010/08/07/using-squeakssl-with-seaside/

Cheers,
   - Andreas

From renggli at gmail.com  Wed Aug 18 08:53:03 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Wed, 18 Aug 2010 08:53:03 +0200
Subject: Optimizing #isRestful
In-Reply-To: <89dhun$2o7rm5@smtp.pt.lu>
References: <89dhun$2o7rm5@smtp.pt.lu>
Message-ID: <AANLkTikYNjV8z7L6vKUbh-RGcPnPf1OKLxo-b9grKRyr@mail.gmail.com>

Sorry for not replying earlier. That sounds like a good idea. I don't
see anybody depending on the instance-side implementation.

Lukas

On 10 August 2010 23:41, Reza Razavi <razavi at acm.org> wrote:
> Hi Lukas, all,
>
> #isRestful is called by PRContext >> urlOn:, typically via the
> PRMenuRenderer (so, upon every page refresh), which delegates to the current
> Command, which, in the case of PRViewCommand, delegates in turn to its
> 'viewComponent'.
>
> To avoid creating an instance of the #viewComponentClass just to check if
> its #isRestful, would it make sense to:
> 1) Move to the class side the four occurrences of #isRestful implementation
> in the PRViewComponent hierarchy, and then
> 2) Change the code in PRViewCommand to delegate to #viewComponentClass?
>
> Regards,
> Reza
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>



-- 
Lukas Renggli
www.lukas-renggli.ch

From razavi at acm.org  Wed Aug 18 09:28:02 2010
From: razavi at acm.org (Reza Razavi)
Date: Wed, 18 Aug 2010 09:28:02 +0200
Subject: Optimizing #isRestful
In-Reply-To: <AANLkTikYNjV8z7L6vKUbh-RGcPnPf1OKLxo-b9grKRyr@mail.gmail.c
 om>
References: <89dhun$2o7rm5@smtp.pt.lu>
	<AANLkTikYNjV8z7L6vKUbh-RGcPnPf1OKLxo-b9grKRyr@mail.gmail.com>
Message-ID: <8bbtuf$312en7@smtp.pt.lu>

At 08:53 18/08/2010, Lukas Renggli wrote:
>I don't see anybody depending on the instance-side implementation.

Thanks for your response Lukas.
I'll propose a patch asap.

Regards,
Reza 


From renggli at gmail.com  Wed Aug 18 09:29:31 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Wed, 18 Aug 2010 09:29:31 +0200
Subject: Optimizing #isRestful
In-Reply-To: <8bbtuf$312en7@smtp.pt.lu>
References: <89dhun$2o7rm5@smtp.pt.lu>
	<AANLkTikYNjV8z7L6vKUbh-RGcPnPf1OKLxo-b9grKRyr@mail.gmail.com>
	<8bbtuf$312en7@smtp.pt.lu>
Message-ID: <AANLkTim_L9_KmgXD0ErOGSN_BBS--g2+ZytuVQgLZYiW@mail.gmail.com>

I already committed  a patch :-)

On 18 August 2010 09:28, Reza Razavi <razavi at acm.org> wrote:
> At 08:53 18/08/2010, Lukas Renggli wrote:
>>
>> I don't see anybody depending on the instance-side implementation.
>
> Thanks for your response Lukas.
> I'll propose a patch asap.
>
> Regards,
> Reza
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>



-- 
Lukas Renggli
www.lukas-renggli.ch

From renggli at gmail.com  Wed Aug 18 09:30:59 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Wed, 18 Aug 2010 09:30:59 +0200
Subject: Optimizing #isRestful
In-Reply-To: <AANLkTim_L9_KmgXD0ErOGSN_BBS--g2+ZytuVQgLZYiW@mail.gmail.com>
References: <89dhun$2o7rm5@smtp.pt.lu>
	<AANLkTikYNjV8z7L6vKUbh-RGcPnPf1OKLxo-b9grKRyr@mail.gmail.com>
	<8bbtuf$312en7@smtp.pt.lu>
	<AANLkTim_L9_KmgXD0ErOGSN_BBS--g2+ZytuVQgLZYiW@mail.gmail.com>
Message-ID: <AANLkTi=eovW3TesT9n8ZLZMThSRCTp3p8dMtJc1E+c=G@mail.gmail.com>

Name: Pier-Seaside-lr.489
Author: lr
Time: 18 August 2010, 9:20:02 am
UUID: 4b4b1ed3-369e-4a1b-93cd-bc3dc0374ddd
Ancestors: Pier-Seaside-lr.488

- moved #isRestful to class-side

Also Seaside needs a patch to work with the latest Pier:

Name: Seaside-Core-lr.656
Author: lr
Time: 18 August 2010, 9:19:12 am
UUID: 8571f819-9d9b-4fbd-bf2f-0e612da035cf
Ancestors: Seaside-Core-pmm.655

- re-added #hasCookieInContext:, it is required by other software

On 18 August 2010 09:29, Lukas Renggli <renggli at gmail.com> wrote:
> I already committed ?a patch :-)
>
> On 18 August 2010 09:28, Reza Razavi <razavi at acm.org> wrote:
>> At 08:53 18/08/2010, Lukas Renggli wrote:
>>>
>>> I don't see anybody depending on the instance-side implementation.
>>
>> Thanks for your response Lukas.
>> I'll propose a patch asap.
>>
>> Regards,
>> Reza
>> _______________________________________________
>> Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>
>
>
>
> --
> Lukas Renggli
> www.lukas-renggli.ch
>



-- 
Lukas Renggli
www.lukas-renggli.ch


From razavi at acm.org  Wed Aug 18 10:24:57 2010
From: razavi at acm.org (Reza Razavi)
Date: Wed, 18 Aug 2010 10:24:57 +0200
Subject: Optimizing PRViewCommand >> label
In-Reply-To: <AANLkTim_L9_KmgXD0ErOGSN_BBS--g2+ZytuVQgLZYiW@mail.gmail.c
 om>
References: <89dhun$2o7rm5@smtp.pt.lu>
	<AANLkTikYNjV8z7L6vKUbh-RGcPnPf1OKLxo-b9grKRyr@mail.gmail.com>
	<8bbtuf$312en7@smtp.pt.lu>
	<AANLkTim_L9_KmgXD0ErOGSN_BBS--g2+ZytuVQgLZYiW@mail.gmail.com>
Message-ID: <89dhun$2qee52@smtp.pt.lu>

At 09:29 18/08/2010, Lukas Renggli wrote:
>I already committed  a patch :-)

Impressive; thanks!

Just in case you would still have some time to devote, a similar case 
is "PRViewCommand >> label", which is in particular often called by 
"WAAnchorTag >> goto:"

An alternative would be:
PRViewCommand >> label
         ^ self viewComponentClass labelIn: self context

Which would imply for example:
PRDefaultView class >> labelIn: aContext
         ^ aContext structure title

And eventually:
PRDefaultView >> label
         ^ self class labelIn: sel context

In the "worth" case, the class would instantiate itself to compute its label.

That could though break the plug-ins that depend on the current behavior.

Regards,
Reza 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20100818/6c6e6e5c/attachment.html>

From lenglish5 at cox.net  Wed Aug 18 19:38:05 2010
From: lenglish5 at cox.net (Lawson English)
Date: Wed, 18 Aug 2010 10:38:05 -0700
Subject: Inline http or html page?
Message-ID: <4C6C1A7D.3090809@cox.net>

  How do I embed raw http in a pier page, or embed an external page?

+http://www.google.com+   doesn't work.



Lawson

From lenglish5 at cox.net  Wed Aug 18 20:09:13 2010
From: lenglish5 at cox.net (Lawson English)
Date: Wed, 18 Aug 2010 11:09:13 -0700
Subject: Inline http or html page?
In-Reply-To: <4C6C1A7D.3090809@cox.net>
References: <4C6C1A7D.3090809@cox.net>
Message-ID: <4C6C21C9.2070608@cox.net>

  OK, so I see that you can use an HTML widget to add html to a 
structure, but I'm confused as to how to control the display of the 
markup combined with the html.



On 8/18/10 10:38 AM, Lawson English wrote:
>  How do I embed raw http in a pier page, or embed an external page?
>
> +http://www.google.com+   doesn't work.
>
>
>
> Lawson
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>


From renggli at gmail.com  Wed Aug 18 20:35:51 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Wed, 18 Aug 2010 20:35:51 +0200
Subject: Inline http or html page?
In-Reply-To: <4C6C21C9.2070608@cox.net>
References: <4C6C1A7D.3090809@cox.net> <4C6C21C9.2070608@cox.net>
Message-ID: <AANLkTims3TPGMs9zzFiXR5itpw0goA3YYArCy-m9GsUX@mail.gmail.com>

{{{verbatim html}}} in Pier 2

Lukas

On 18 August 2010 20:09, Lawson English <lenglish5 at cox.net> wrote:
> ?OK, so I see that you can use an HTML widget to add html to a structure,
> but I'm confused as to how to control the display of the markup combined
> with the html.
>
>
>
> On 8/18/10 10:38 AM, Lawson English wrote:
>>
>> ?How do I embed raw http in a pier page, or embed an external page?
>>
>> +http://www.google.com+ ? doesn't work.{{>>
>>
>>
>> Lawson
>> _______________________________________________
>> 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
www.lukas-renggli.ch


From lenglish5 at cox.net  Wed Aug 18 22:53:41 2010
From: lenglish5 at cox.net (Lawson English)
Date: Wed, 18 Aug 2010 13:53:41 -0700
Subject: Inline http or html page?
In-Reply-To: <AANLkTims3TPGMs9zzFiXR5itpw0goA3YYArCy-m9GsUX@mail.gmail.com>
References: <4C6C1A7D.3090809@cox.net> <4C6C21C9.2070608@cox.net>
	<AANLkTims3TPGMs9zzFiXR5itpw0goA3YYArCy-m9GsUX@mail.gmail.com>
Message-ID: <4C6C4855.7000007@cox.net>

  On 8/18/10 11:35 AM, Lukas Renggli wrote:
> {{{verbatim html}}}
Thanks so much. Life saver and all that :-)


Lawson

From lenglish5 at cox.net  Fri Aug 20 00:34:47 2010
From: lenglish5 at cox.net (Lawson English)
Date: Thu, 19 Aug 2010 15:34:47 -0700
Subject: environment copy strangeness in pier on seaside 3.0rc one-click
	install
Message-ID: <4C6DB187.7030103@cox.net>

  I was trying to make a copy of my enviornment template in Pier using 
the seaside 3.0rc oneclick available from squeak.org


The steps I took:

login.
click on +system
click on _environment

select the copy command and name it environmentcopy
save

create a new page.

click settings.
Point the environment to /system/templates/environmentcopy

(have to manually enter that since "choose" doesn't work as I expected)

save


start editing /system/templates/environmentcopy.

it saves the changes in the original environment page.


Is this normal behavior? I thought copy meant copy contents, not just 
create a new link to the same file.



Lawson

From lenglish5 at cox.net  Fri Aug 20 00:58:20 2010
From: lenglish5 at cox.net (Lawson English)
Date: Thu, 19 Aug 2010 15:58:20 -0700
Subject: environment copy strangeness in pier on seaside 3.0rc one-click
	install
In-Reply-To: <4C6DB187.7030103@cox.net>
References: <4C6DB187.7030103@cox.net>
Message-ID: <4C6DB70C.4000900@cox.net>

  OK, so I see partly where my error is. I originally changed the Menu 
component which is referred to in both the environment file and the 
environmentcopy file.

I created a menucopy file and changed THAT, but can't figure out how to 
make environmentcopy refer to it instead of the original menu component. 
IOW, I want enviornmentcopy to use menucopy instead of menu...

Thanks in advance.


Lawson

On 8/19/10 3:34 PM, Lawson English wrote:
>  I was trying to make a copy of my enviornment template in Pier using 
> the seaside 3.0rc oneclick available from squeak.org
>
>
> The steps I took:
>
> login.
> click on +system
> click on _environment
>
> select the copy command and name it environmentcopy
> save
>
> create a new page.
>
> click settings.
> Point the environment to /system/templates/environmentcopy
>
> (have to manually enter that since "choose" doesn't work as I expected)
>
> save
>
>
> start editing /system/templates/environmentcopy.
>
> it saves the changes in the original environment page.
>
>
> Is this normal behavior? I thought copy meant copy contents, not just 
> create a new link to the same file.
>
>
>
> Lawson
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>


From lenglish5 at cox.net  Fri Aug 20 21:28:23 2010
From: lenglish5 at cox.net (Lawson English)
Date: Fri, 20 Aug 2010 12:28:23 -0700
Subject: can't load Gallery addon because I can't load Rio
Message-ID: <4C6ED757.8040100@cox.net>

  The Gallery addon for pier first requires that Rio be installed.

http://www.squeaksource.com/@7zePIlRlfoA0dT1I/VwzOlsoy


However, rio won't install due to errors:

FileMacOSXExectuive class as yet unclassified getenv:

getenv: varString
     " self getenv: 'HOME' "
     " self getenv: 'ZYZZYX' "

<> expected ->cdecl:  char* 'getenv' ( char* ) module: 'libc.dylib'>
     ^self externalCallFailed


Not sure how to fix this...

Using the Seaside-3.0rc  one-click for Pharo-Seaside


Lawson

From lenglish5 at cox.net  Mon Aug 23 20:02:34 2010
From: lenglish5 at cox.net (Lawson English)
Date: Mon, 23 Aug 2010 11:02:34 -0700
Subject: test message
Message-ID: <4C72B7BA.7060906@cox.net>

  this hist has been quiet lately. So just checking to see if the server 
is working.


Lawson

From nick.ager at gmail.com  Wed Aug 25 11:02:35 2010
From: nick.ager at gmail.com (Nick Ager)
Date: Wed, 25 Aug 2010 10:02:35 +0100
Subject: PRContentsWidget swallowing errors
Message-ID: <AANLkTinh0CVB5d=DeryAEC2W5oLxO3ZMp5=hTy63nVK5@mail.gmail.com>

Hi,

I've noticed that non-validation errors are trapped by the code in
PRContentsWidget>>#onAnswerCommand: aCommand

Can anyone anticipate any problems catching MAError rather than Error, so
that non-validation errors are propagated as normal and validation errors
are displayed. Currently the code reads:

onAnswerCommand: aCommand
aCommand isNil
ifTrue: [ ^ self context: (self context structure: self context structure)
].
[ aCommand execute ]
on: Error
do: [ :err | ^ self component errors add: err ].
self context: aCommand answer


I'd like to change Error to MAError

Have I missed anything?

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

From renggli at gmail.com  Wed Aug 25 12:00:22 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Wed, 25 Aug 2010 12:00:22 +0200
Subject: PRContentsWidget swallowing errors
In-Reply-To: <AANLkTinh0CVB5d=DeryAEC2W5oLxO3ZMp5=hTy63nVK5@mail.gmail.com>
References: <AANLkTinh0CVB5d=DeryAEC2W5oLxO3ZMp5=hTy63nVK5@mail.gmail.com>
Message-ID: <AANLkTimP1wcYwLDgo-7GODvczBEVaY9Z=cVohMMM1qXQ@mail.gmail.com>

Please give it a try and we will see if there are any bad side-effects.

Lukas

On 25 August 2010 11:02, Nick Ager <nick.ager at gmail.com> wrote:
> Hi,
> I've noticed that non-validation errors are trapped by the code in
> PRContentsWidget>>#onAnswerCommand: aCommand
> Can anyone anticipate any problems catching MAError rather than Error, so
> that non-validation errors are?propagated?as normal and validation errors
> are displayed. Currently the code reads:
> onAnswerCommand: aCommand
> aCommand isNil
> ifTrue: [ ^ self context: (self context structure: self context structure)
> ].
> [ aCommand execute ]
> on: Error
> do: [ :err | ^ self component errors add: err ].
> self context: aCommand answer
>
> I'd like to change Error to MAError
> Have I missed anything?
> Nick
> _______________________________________________
> 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  Wed Aug 25 12:05:50 2010
From: nick.ager at gmail.com (Nick Ager)
Date: Wed, 25 Aug 2010 11:05:50 +0100
Subject: PRContentsWidget swallowing errors
In-Reply-To: <AANLkTimP1wcYwLDgo-7GODvczBEVaY9Z=cVohMMM1qXQ@mail.gmail.com>
References: <AANLkTinh0CVB5d=DeryAEC2W5oLxO3ZMp5=hTy63nVK5@mail.gmail.com>
	<AANLkTimP1wcYwLDgo-7GODvczBEVaY9Z=cVohMMM1qXQ@mail.gmail.com>
Message-ID: <AANLkTi=8cGy6=fct85VDVu-h2URsDqs7ffxFZnzMFUN0@mail.gmail.com>

Hi Lukas,

Please give it a try and we will see if there are any bad side-effects.


It appears to be working as I'd hoped in *my* Pier application. I'll
continue testing and assuming nothing unanticipated occurs I'll check-in the
change

Thanks

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

From nick.ager at gmail.com  Thu Aug 26 00:50:10 2010
From: nick.ager at gmail.com (Nick Ager)
Date: Wed, 25 Aug 2010 23:50:10 +0100
Subject: PRContentsWidget swallowing errors
In-Reply-To: <AANLkTi=8cGy6=fct85VDVu-h2URsDqs7ffxFZnzMFUN0@mail.gmail.com>
References: <AANLkTinh0CVB5d=DeryAEC2W5oLxO3ZMp5=hTy63nVK5@mail.gmail.com>
	<AANLkTimP1wcYwLDgo-7GODvczBEVaY9Z=cVohMMM1qXQ@mail.gmail.com>
	<AANLkTi=8cGy6=fct85VDVu-h2URsDqs7ffxFZnzMFUN0@mail.gmail.com>
Message-ID: <AANLkTi=RkJZ0W-hDcfWjEkJCtss6esrYcsii8gHm8J4m@mail.gmail.com>

Hi,

I tried to check this change in but the check-in failed with a 401
unauthorized

I've attached the mcz version

Nick

On 25 August 2010 11:05, Nick Ager <nick.ager at gmail.com> wrote:

> Hi Lukas,
>
> Please give it a try and we will see if there are any bad side-effects.
>
>
> It appears to be working as I'd hoped in *my* Pier application. I'll
> continue testing and assuming nothing unanticipated occurs I'll check-in the
> change
>
> Thanks
>
> Nick
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20100825/dfc42101/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Pier-Seaside-NickAger.490.mcz
Type: application/octet-stream
Size: 128310 bytes
Desc: not available
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20100825/dfc42101/attachment-0001.obj>

From renggli at gmail.com  Thu Aug 26 08:06:43 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Thu, 26 Aug 2010 08:06:43 +0200
Subject: PRContentsWidget swallowing errors
In-Reply-To: <AANLkTi=RkJZ0W-hDcfWjEkJCtss6esrYcsii8gHm8J4m@mail.gmail.com>
References: <AANLkTinh0CVB5d=DeryAEC2W5oLxO3ZMp5=hTy63nVK5@mail.gmail.com>
	<AANLkTimP1wcYwLDgo-7GODvczBEVaY9Z=cVohMMM1qXQ@mail.gmail.com>
	<AANLkTi=8cGy6=fct85VDVu-h2URsDqs7ffxFZnzMFUN0@mail.gmail.com>
	<AANLkTi=RkJZ0W-hDcfWjEkJCtss6esrYcsii8gHm8J4m@mail.gmail.com>
Message-ID: <AANLkTi=JSETgP22XriMknr5pRaWR5sNcfMpFHjbu0S=z@mail.gmail.com>

This is strange, are you sure that you use the right initials and
password? You are member with full write access in the groups of
Magritte and Pier.

Lukas

On 26 August 2010 00:50, Nick Ager <nick.ager at gmail.com> wrote:
> Hi,
> I tried to check this change in but the check-in failed with a 401
> unauthorized
> I've attached the mcz version
> Nick
>
> On 25 August 2010 11:05, Nick Ager <nick.ager at gmail.com> wrote:
>>
>> Hi Lukas,
>>
>>> Please give it a try and we will see if there are any bad side-effects.
>>
>> It appears to be working as I'd hoped in *my* Pier application. I'll
>> continue testing and assuming nothing?unanticipated occurs?I'll check-in the
>> change
>> Thanks
>> Nick
>
> _______________________________________________
> 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  Thu Aug 26 09:13:45 2010
From: nick.ager at gmail.com (Nick Ager)
Date: Thu, 26 Aug 2010 08:13:45 +0100
Subject: PRContentsWidget swallowing errors
In-Reply-To: <AANLkTi=JSETgP22XriMknr5pRaWR5sNcfMpFHjbu0S=z@mail.gmail.com>
References: <AANLkTinh0CVB5d=DeryAEC2W5oLxO3ZMp5=hTy63nVK5@mail.gmail.com>
	<AANLkTimP1wcYwLDgo-7GODvczBEVaY9Z=cVohMMM1qXQ@mail.gmail.com>
	<AANLkTi=8cGy6=fct85VDVu-h2URsDqs7ffxFZnzMFUN0@mail.gmail.com>
	<AANLkTi=RkJZ0W-hDcfWjEkJCtss6esrYcsii8gHm8J4m@mail.gmail.com>
	<AANLkTi=JSETgP22XriMknr5pRaWR5sNcfMpFHjbu0S=z@mail.gmail.com>
Message-ID: <AANLkTi=UPEEyRYZDFr2OAbGpEQgh5SvD-FD=ydU3CF5Z@mail.gmail.com>

Sorry Lukas my mistake - I was using the wrong password. I've now checked-in
my changes.

On 26 August 2010 07:06, Lukas Renggli <renggli at gmail.com> wrote:

> This is strange, are you sure that you use the right initials and
> password? You are member with full write access in the groups of
> Magritte and Pier.
>
> Lukas
>
> On 26 August 2010 00:50, Nick Ager <nick.ager at gmail.com> wrote:
> > Hi,
> > I tried to check this change in but the check-in failed with a 401
> > unauthorized
> > I've attached the mcz version
> > Nick
> >
> > On 25 August 2010 11:05, Nick Ager <nick.ager at gmail.com> wrote:
> >>
> >> Hi Lukas,
> >>
> >>> Please give it a try and we will see if there are any bad side-effects.
> >>
> >> It appears to be working as I'd hoped in *my* Pier application. I'll
> >> continue testing and assuming nothing unanticipated occurs I'll check-in
> the
> >> change
> >> Thanks
> >> Nick
> >
> > _______________________________________________
> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20100826/e1b63a06/attachment.html>

From razavi at acm.org  Thu Aug 26 09:16:12 2010
From: razavi at acm.org (Reza Razavi)
Date: Thu, 26 Aug 2010 09:16:12 +0200
Subject: PRContentsWidget swallowing errors
In-Reply-To: <AANLkTinh0CVB5d=DeryAEC2W5oLxO3ZMp5=hTy63nVK5@mail.gmail.c
 om>
References: <AANLkTinh0CVB5d=DeryAEC2W5oLxO3ZMp5=hTy63nVK5@mail.gmail.com>
Message-ID: <8bbtuf$33nth1@smtp.pt.lu>

At 11:02 25/08/2010, Nick Ager wrote:
>I've noticed that non-validation errors are trapped by the code in 
>PRContentsWidget>>#onAnswerCommand: aCommand

Hi Nick,

You have certainly also noticed that this is a key method in the 
Pier's request handling process. In my experience, and just from a 
practical point of view, I found it useful for "production" images to 
have here Error instead of MAError, since even in case of an 
unexpected error, Pier keeps handling requests gracefully, while 
rendering the error message on the client side. For development 
images, it would be sufficient to add a 'halt' inside the exception 
handling block.

I should add that, in practice, I've encountered rarely such cases, 
and, as far as I remember, those cases have always been related to my 
own add-ons. Nevertheless, it seems hard to definitely assess that 
during the execution of ALL commands, in ALL end-user use cases, the 
exceptional situations will strictly be limited to validation errors. 
If this makes sense, then Error would be a better choice.

Regards,
Reza  


From renggli at gmail.com  Thu Aug 26 09:19:20 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Thu, 26 Aug 2010 09:19:20 +0200
Subject: PRContentsWidget swallowing errors
In-Reply-To: <AANLkTi=UPEEyRYZDFr2OAbGpEQgh5SvD-FD=ydU3CF5Z@mail.gmail.com>
References: <AANLkTinh0CVB5d=DeryAEC2W5oLxO3ZMp5=hTy63nVK5@mail.gmail.com>
	<AANLkTimP1wcYwLDgo-7GODvczBEVaY9Z=cVohMMM1qXQ@mail.gmail.com>
	<AANLkTi=8cGy6=fct85VDVu-h2URsDqs7ffxFZnzMFUN0@mail.gmail.com>
	<AANLkTi=RkJZ0W-hDcfWjEkJCtss6esrYcsii8gHm8J4m@mail.gmail.com>
	<AANLkTi=JSETgP22XriMknr5pRaWR5sNcfMpFHjbu0S=z@mail.gmail.com>
	<AANLkTi=UPEEyRYZDFr2OAbGpEQgh5SvD-FD=ydU3CF5Z@mail.gmail.com>
Message-ID: <AANLkTin9Hyg6M6G6+cU5UbOFXLgwewkAsxErLzQ1i_4p@mail.gmail.com>

Excellent, thank you.

Lukas

On Thursday, August 26, 2010, Nick Ager <nick.ager at gmail.com> wrote:
> Sorry Lukas my mistake - I was using the wrong password. I've now checked-in my changes.
>
> On 26 August 2010 07:06, Lukas Renggli <renggli at gmail.com> wrote:
> This is strange, are you sure that you use the right initials and
> password? You are member with full write access in the groups of
> Magritte and Pier.
>
> Lukas
>
> On 26 August 2010 00:50, Nick Ager <nick.ager at gmail.com> wrote:
>> Hi,
>> I tried to check this change in but the check-in failed with a 401
>> unauthorized
>> I've attached the mcz version
>> Nick
>>
>> On 25 August 2010 11:05, Nick Ager <nick.ager at gmail.com> wrote:
>>>
>>> Hi Lukas,
>>>
>>>> Please give it a try and we will see if there are any bad side-effects.
>>>
>>> It appears to be working as I'd hoped in *my* Pier application. I'll
>>> continue testing and assuming nothing?unanticipated occurs?I'll check-in the
>>> change
>>> Thanks
>>> Nick
>>
>> _______________________________________________
>> 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
>
>

-- 
Lukas Renggli
www.lukas-renggli.ch


From nick.ager at gmail.com  Thu Aug 26 09:36:37 2010
From: nick.ager at gmail.com (Nick Ager)
Date: Thu, 26 Aug 2010 08:36:37 +0100
Subject: PRContentsWidget swallowing errors
In-Reply-To: <8bbtuf$33nth1@smtp.pt.lu>
References: <AANLkTinh0CVB5d=DeryAEC2W5oLxO3ZMp5=hTy63nVK5@mail.gmail.com>
	<8bbtuf$33nth1@smtp.pt.lu>
Message-ID: <AANLkTimk8YrNbSgrKtM4j9YKm2Zuba96abO+jt7RkH0z@mail.gmail.com>

Hi Reza,


> In my experience, and just from a practical point of view, I found it
> useful for "production" images to have here Error instead of MAError, since
> even in case of an unexpected error, Pier keeps handling requests
> gracefully, while rendering the error message on the client side. For
> development images, it would be sufficient to add a 'halt' inside the
> exception handling block.
>

I see your point. My understanding for the intent of the code was as a
mechanism to display form validation errors, rather than general programming
errors. I had a couple of bugs when I ported to Gemstone that were silently
consumed (the errors weren't displayed) by PRContentsWidget's error handling
and felt that this wasn't the intention of the original code. It seemed to
me that programming error exceptions should be propagated and handled in a
more general exception handler.

In the case you mention, where 'Pier keeps handling requests gracefully'
would the errors make any sense to the user and could they take remedial
action to correct the error?

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

From razavi at acm.org  Thu Aug 26 10:19:58 2010
From: razavi at acm.org (Reza Razavi)
Date: Thu, 26 Aug 2010 10:19:58 +0200
Subject: PRContentsWidget swallowing errors
In-Reply-To: <AANLkTimk8YrNbSgrKtM4j9YKm2Zuba96abO+jt7RkH0z@mail.gmail.c
 om>
References: <AANLkTinh0CVB5d=DeryAEC2W5oLxO3ZMp5=hTy63nVK5@mail.gmail.com>
	<8bbtuf$33nth1@smtp.pt.lu>
	<AANLkTimk8YrNbSgrKtM4j9YKm2Zuba96abO+jt7RkH0z@mail.gmail.com>
Message-ID: <8bbtuf$33ooi2@smtp.pt.lu>

At 09:36 26/08/2010, Nick Ager wrote:
>were silently consumed (the errors weren't displayed) by 
>PRContentsWidget's error handling and felt that this wasn't the 
>intention of the original code.

To me, the intention of the original code has for sure not been to 
hide errors, but to provide a handy solution to capture unexpected 
errors. This method is the "heart" of the Pier's request interpreter 
("eval"), and in that sense it seems well situated for processing 
those exceptions. Of course, there is room for fine tuning, but my 
understanding is that Pier has invested in avoiding such programming 
errors. Still, Pier is an extendable system and in that sense 
responsible for handling eventual errors in plug-ins. Error instead 
of MAError may be also explained in this way.

>In the case you mention, where 'Pier keeps handling requests 
>gracefully' would the errors make any sense to the user and could 
>they take remedial action to correct the error?

No, programming errors don't, in general, make sense to end-users. 
Remedial measures could be taken if the error is related to end-user 
actions. For example, feeding unexpected content (not only by Pier, 
but also by its plug-ins). But in all cases, for end-users it seems 
better to have an application that keeps responsive, eventually with 
meaningful error messages, instead of a *wall back* window.

Regards,
Reza         


From nick.ager at gmail.com  Thu Aug 26 10:33:14 2010
From: nick.ager at gmail.com (Nick Ager)
Date: Thu, 26 Aug 2010 09:33:14 +0100
Subject: PRContentsWidget swallowing errors
In-Reply-To: <8bbtuf$33ooi2@smtp.pt.lu>
References: <AANLkTinh0CVB5d=DeryAEC2W5oLxO3ZMp5=hTy63nVK5@mail.gmail.com>
	<8bbtuf$33nth1@smtp.pt.lu>
	<AANLkTimk8YrNbSgrKtM4j9YKm2Zuba96abO+jt7RkH0z@mail.gmail.com>
	<8bbtuf$33ooi2@smtp.pt.lu>
Message-ID: <AANLkTikofJ7BjtdU_9HrFkeU1m+0ZfO7bM30q9shoahV@mail.gmail.com>

Hi Raza,

No, programming errors don't, in general, make sense to end-users. Remedial
> measures could be taken if the error is related to end-user actions. For
> example, feeding unexpected content (not only by Pier, but also by its
> plug-ins). But in all cases, for end-users it seems better to have an
> application that keeps responsive, eventually with meaningful error
> messages, instead of a *wall back* window.
>
>
I agree that you don't want to display walk-back errors to end users though
is there a problem changing WAWalkbackErrorHandler to something that makes
more sense to the end user?

Nick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20100826/2d0deff3/attachment-0001.html>

From razavi at acm.org  Thu Aug 26 10:48:48 2010
From: razavi at acm.org (Reza Razavi)
Date: Thu, 26 Aug 2010 10:48:48 +0200
Subject: PRContentsWidget swallowing errors
In-Reply-To: <AANLkTikofJ7BjtdU_9HrFkeU1m+0ZfO7bM30q9shoahV@mail.gmail.c
 om>
References: <AANLkTinh0CVB5d=DeryAEC2W5oLxO3ZMp5=hTy63nVK5@mail.gmail.com>
	<8bbtuf$33nth1@smtp.pt.lu>
	<AANLkTimk8YrNbSgrKtM4j9YKm2Zuba96abO+jt7RkH0z@mail.gmail.com>
	<8bbtuf$33ooi2@smtp.pt.lu>
	<AANLkTikofJ7BjtdU_9HrFkeU1m+0ZfO7bM30q9shoahV@mail.gmail.com>
Message-ID: <89dhun$2t03e0@smtp.pt.lu>

At 10:33 26/08/2010, Nick Ager wrote:
>is there a problem changing WAWalkbackErrorHandler to something that 
>makes more sense to the end user?

Seaside provides general mechanisms. More specific solutions depend 
on the end-user community that one targets. In my experience, I had 
happy end-users with a simple dialog box asking their agreement to 
communicate their execution stack, knowing that that context may 
contain proprietary information.

Regards,
Reza 


From nick.ager at gmail.com  Thu Aug 26 10:58:03 2010
From: nick.ager at gmail.com (Nick Ager)
Date: Thu, 26 Aug 2010 09:58:03 +0100
Subject: PRContentsWidget swallowing errors
In-Reply-To: <89dhun$2t03e0@smtp.pt.lu>
References: <AANLkTinh0CVB5d=DeryAEC2W5oLxO3ZMp5=hTy63nVK5@mail.gmail.com>
	<8bbtuf$33nth1@smtp.pt.lu>
	<AANLkTimk8YrNbSgrKtM4j9YKm2Zuba96abO+jt7RkH0z@mail.gmail.com>
	<8bbtuf$33ooi2@smtp.pt.lu>
	<AANLkTikofJ7BjtdU_9HrFkeU1m+0ZfO7bM30q9shoahV@mail.gmail.com>
	<89dhun$2t03e0@smtp.pt.lu>
Message-ID: <AANLkTinWFvL0iv8YrDBS5pASYRdDXhJVe9eF0FvdpNbi@mail.gmail.com>

So what to do? Should I back out the change?

On 26 August 2010 09:48, Reza Razavi <razavi at acm.org> wrote:

> At 10:33 26/08/2010, Nick Ager wrote:
>
>> is there a problem changing WAWalkbackErrorHandler to something that makes
>> more sense to the end user?
>>
>
> Seaside provides general mechanisms. More specific solutions depend on the
> end-user community that one targets. In my experience, I had happy end-users
> with a simple dialog box asking their agreement to communicate their
> execution stack, knowing that that context may contain proprietary
> information.
>
>
> Regards,
> Reza
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20100826/9299e951/attachment.html>

From razavi at acm.org  Thu Aug 26 11:17:31 2010
From: razavi at acm.org (Reza Razavi)
Date: Thu, 26 Aug 2010 11:17:31 +0200
Subject: PRContentsWidget swallowing errors
In-Reply-To: <AANLkTinWFvL0iv8YrDBS5pASYRdDXhJVe9eF0FvdpNbi@mail.gmail.c
 om>
References: <AANLkTinh0CVB5d=DeryAEC2W5oLxO3ZMp5=hTy63nVK5@mail.gmail.com>
	<8bbtuf$33nth1@smtp.pt.lu>
	<AANLkTimk8YrNbSgrKtM4j9YKm2Zuba96abO+jt7RkH0z@mail.gmail.com>
	<8bbtuf$33ooi2@smtp.pt.lu>
	<AANLkTikofJ7BjtdU_9HrFkeU1m+0ZfO7bM30q9shoahV@mail.gmail.com>
	<89dhun$2t03e0@smtp.pt.lu>
	<AANLkTinWFvL0iv8YrDBS5pASYRdDXhJVe9eF0FvdpNbi@mail.gmail.com>
Message-ID: <8bbtuf$33pkar@smtp.pt.lu>

At 10:58 26/08/2010, Nick Ager wrote:
>So what to do? Should I back out the change?

As Lukas suggested, it would be useful to give it a try, if possible 
in real test conditions involving end-users, to gain a better idea of 
the real risks, at least in your own app's config.

Regards,
Reza 


From nick.ager at gmail.com  Thu Aug 26 11:51:21 2010
From: nick.ager at gmail.com (Nick Ager)
Date: Thu, 26 Aug 2010 10:51:21 +0100
Subject: PRContentsWidget swallowing errors
In-Reply-To: <8bbtuf$33pkar@smtp.pt.lu>
References: <AANLkTinh0CVB5d=DeryAEC2W5oLxO3ZMp5=hTy63nVK5@mail.gmail.com>
	<8bbtuf$33nth1@smtp.pt.lu>
	<AANLkTimk8YrNbSgrKtM4j9YKm2Zuba96abO+jt7RkH0z@mail.gmail.com>
	<8bbtuf$33ooi2@smtp.pt.lu>
	<AANLkTikofJ7BjtdU_9HrFkeU1m+0ZfO7bM30q9shoahV@mail.gmail.com>
	<89dhun$2t03e0@smtp.pt.lu>
	<AANLkTinWFvL0iv8YrDBS5pASYRdDXhJVe9eF0FvdpNbi@mail.gmail.com>
	<8bbtuf$33pkar@smtp.pt.lu>
Message-ID: <AANLkTi=z6pmqZgexS+rJXJ+r9VEvxJqdrwASA8SGqf=Y@mail.gmail.com>

OK - it works for me. Let me know if you have problem in your app.

On 26 August 2010 10:17, Reza Razavi <razavi at acm.org> wrote:

> At 10:58 26/08/2010, Nick Ager wrote:
>
>> So what to do? Should I back out the change?
>>
>
> As Lukas suggested, it would be useful to give it a try, if possible in
> real test conditions involving end-users, to gain a better idea of the real
> risks, at least in your own app's config.
>
>
> Regards,
> Reza
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20100826/fcf15655/attachment.html>

From razavi at acm.org  Thu Aug 26 12:24:00 2010
From: razavi at acm.org (Reza Razavi)
Date: Thu, 26 Aug 2010 12:24:00 +0200
Subject: PRContentsWidget swallowing errors
In-Reply-To: <AANLkTi=z6pmqZgexS+rJXJ+r9VEvxJqdrwASA8SGqf=Y@mail.gmail.c
 om>
References: <AANLkTinh0CVB5d=DeryAEC2W5oLxO3ZMp5=hTy63nVK5@mail.gmail.com>
	<8bbtuf$33nth1@smtp.pt.lu>
	<AANLkTimk8YrNbSgrKtM4j9YKm2Zuba96abO+jt7RkH0z@mail.gmail.com>
	<8bbtuf$33ooi2@smtp.pt.lu>
	<AANLkTikofJ7BjtdU_9HrFkeU1m+0ZfO7bM30q9shoahV@mail.gmail.com>
	<89dhun$2t03e0@smtp.pt.lu>
	<AANLkTinWFvL0iv8YrDBS5pASYRdDXhJVe9eF0FvdpNbi@mail.gmail.com>
	<8bbtuf$33pkar@smtp.pt.lu>
	<AANLkTi=z6pmqZgexS+rJXJ+r9VEvxJqdrwASA8SGqf=Y@mail.gmail.com>
Message-ID: <89dhun$2t1ehu@smtp.pt.lu>

At 11:51 26/08/2010, Nick Ager wrote:
>Let me know if you have problem in your app.

Sure.
Cheers,
Reza 


From lenglish5 at cox.net  Sat Aug 28 17:23:31 2010
From: lenglish5 at cox.net (Lawson English)
Date: Sat, 28 Aug 2010 08:23:31 -0700
Subject: Pier Blog has uneven behavior
Message-ID: <4C7929F3.40700@cox.net>

  Hey, helping a friend with his blog at: http://www.morphle.com:8204   
and he's noticed that sometimes, when he goes to a specific blog entry, 
he enters the page at the top and sometimes at the bottom. Is this a 
random behavior or based on some cookie that is set or...?


Thanks,

Lawson




From renggli at gmail.com  Sat Aug 28 17:37:01 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Sat, 28 Aug 2010 17:37:01 +0200
Subject: Pier Blog has uneven behavior
In-Reply-To: <4C7929F3.40700@cox.net>
References: <4C7929F3.40700@cox.net>
Message-ID: <AANLkTimyTqQ_9XgKs08pWhENFXvUv_=85cnORq9XKd9i@mail.gmail.com>

The default script that Pier includes sets the focus to the first
Magritte form field. That's convenient for many setups but doesn't
work for all designs. I suspect that you better remove the script from
the seaside config of the pier app.

Lukas

On Saturday, August 28, 2010, Lawson English <lenglish5 at cox.net> wrote:
> ?Hey, helping a friend with his blog at: http://www.morphle.com:8204 ? and he's noticed that sometimes, when he goes to a specific blog entry, he enters the page at the top and sometimes at the bottom. Is this a random behavior or based on some cookie that is set or...?
>
>
> Thanks,
>
> Lawson
>
>
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

-- 
Lukas Renggli
www.lukas-renggli.ch


From lenglish5 at cox.net  Sat Aug 28 17:41:30 2010
From: lenglish5 at cox.net (Lawson English)
Date: Sat, 28 Aug 2010 08:41:30 -0700
Subject: Pier Blog has uneven behavior
In-Reply-To: <AANLkTimyTqQ_9XgKs08pWhENFXvUv_=85cnORq9XKd9i@mail.gmail.com>
References: <4C7929F3.40700@cox.net>
	<AANLkTimyTqQ_9XgKs08pWhENFXvUv_=85cnORq9XKd9i@mail.gmail.com>
Message-ID: <4C792E2A.8030802@cox.net>

  On 8/28/10 8:37 AM, Lukas Renggli wrote:
> The default script that Pier includes sets the focus to the first
> Magritte form field. That's convenient for many setups but doesn't
> work for all designs. I suspect that you better remove the script from
> the seaside config of the pier app.
Thanks Lukas.


lawson

From lenglish5 at cox.net  Sat Aug 28 22:37:25 2010
From: lenglish5 at cox.net (Lawson English)
Date: Sat, 28 Aug 2010 13:37:25 -0700
Subject: Pier Blog has uneven behavior
In-Reply-To: <AANLkTimyTqQ_9XgKs08pWhENFXvUv_=85cnORq9XKd9i@mail.gmail.com>
References: <4C7929F3.40700@cox.net>
	<AANLkTimyTqQ_9XgKs08pWhENFXvUv_=85cnORq9XKd9i@mail.gmail.com>
Message-ID: <4C797385.8040507@cox.net>

  To be honest, someone else was working on the blog-specific stuff but 
they had a vacation scheduled starting a few days ago. Unfortunately, 
the horror festival is Monday, and I'm clueless about Pier at this point.

What do you mean by "remove the script from the seaside config of the 
pier app?" I've looked at the config/pier page and not sure what I am 
supposed to remove.

Sheepishly, Lawson

On 8/28/10 8:37 AM, Lukas Renggli wrote:
> The default script that Pier includes sets the focus to the first
> Magritte form field. That's convenient for many setups but doesn't
> work for all designs. I suspect that you better remove the script from
> the seaside config of the pier app.
>
> Lukas
>
> On Saturday, August 28, 2010, Lawson English<lenglish5 at cox.net>  wrote:
>>   Hey, helping a friend with his blog at: http://www.morphle.com:8204   and he's noticed that sometimes, when he goes to a specific blog entry, he enters the page at the top and sometimes at the bottom. Is this a random behavior or based on some cookie that is set or...?
>>
>>
>> Thanks,
>>
>> Lawson
>>
>>
>>
>> _______________________________________________
>> Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>


From renggli at gmail.com  Sat Aug 28 23:33:43 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Sat, 28 Aug 2010 23:33:43 +0200
Subject: Pier Blog has uneven behavior
In-Reply-To: <4C797385.8040507@cox.net>
References: <4C7929F3.40700@cox.net>
	<AANLkTimyTqQ_9XgKs08pWhENFXvUv_=85cnORq9XKd9i@mail.gmail.com>
	<4C797385.8040507@cox.net>
Message-ID: <AANLkTinD+VNrmHZL94W9DV2H2qjOnjAdMoKaMeLFJdue@mail.gmail.com>

I don't have an image at hand to check, but I think it must be the
(only) libray class starting with the prefix PR*.

Lukas

On Saturday, August 28, 2010, Lawson English <lenglish5 at cox.net> wrote:
> ?To be honest, someone else was working on the blog-specific stuff but they had a vacation scheduled starting a few days ago. Unfortunately, the horror festival is Monday, and I'm clueless about Pier at this point.
>
> What do you mean by "remove the script from the seaside config of the pier app?" I've looked at the config/pier page and not sure what I am supposed to remove.
>
> Sheepishly, Lawson
>
> On 8/28/10 8:37 AM, Lukas Renggli wrote:
>
> The default script that Pier includes sets the focus to the first
> Magritte form field. That's convenient for many setups but doesn't
> work for all designs. I suspect that you better remove the script from
> the seaside config of the pier app.
>
> Lukas
>
> On Saturday, August 28, 2010, Lawson English<lenglish5 at cox.net> ?wrote:
>
>  ?Hey, helping a friend with his blog at: http://www.morphle.com:8204 ? and he's noticed that sometimes, when he goes to a specific blog entry, he enters the page at the top and sometimes at the bottom. Is this a random behavior or based on some cookie that is set or...?
>
>
> Thanks,
>
> Lawson
>
>
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>
>
>
>

-- 
Lukas Renggli
www.lukas-renggli.ch


From p3anoman at gmail.com  Sun Aug 29 00:23:43 2010
From: p3anoman at gmail.com (John McKeon)
Date: Sat, 28 Aug 2010 18:23:43 -0400
Subject: Pier Blog has uneven behavior
In-Reply-To: <AANLkTinD+VNrmHZL94W9DV2H2qjOnjAdMoKaMeLFJdue@mail.gmail.com>
References: <4C7929F3.40700@cox.net>
	<AANLkTimyTqQ_9XgKs08pWhENFXvUv_=85cnORq9XKd9i@mail.gmail.com>
	<4C797385.8040507@cox.net>
	<AANLkTinD+VNrmHZL94W9DV2H2qjOnjAdMoKaMeLFJdue@mail.gmail.com>
Message-ID: <AANLkTikvRO+e-Km7T1bzdusnpE_FPk_mJ7vgccwZrk-v@mail.gmail.com>

I think you want to remove PRJavascriptSupport.
On the *Seaside* config page for the Pier app, about halfway down, under
General heading, you should see the libraries listed. Click the configure
button to remove the above.

HTH
John

On Sat, Aug 28, 2010 at 5:33 PM, Lukas Renggli <renggli at gmail.com> wrote:

> I don't have an image at hand to check, but I think it must be the
> (only) libray class starting with the prefix PR*.
>
> Lukas
>
> On Saturday, August 28, 2010, Lawson English <lenglish5 at cox.net> wrote:
> >  To be honest, someone else was working on the blog-specific stuff but
> they had a vacation scheduled starting a few days ago. Unfortunately, the
> horror festival is Monday, and I'm clueless about Pier at this point.
> >
> > What do you mean by "remove the script from the seaside config of the
> pier app?" I've looked at the config/pier page and not sure what I am
> supposed to remove.
> >
> > Sheepishly, Lawson
> >
> > On 8/28/10 8:37 AM, Lukas Renggli wrote:
> >
> > The default script that Pier includes sets the focus to the first
> > Magritte form field. That's convenient for many setups but doesn't
> > work for all designs. I suspect that you better remove the script from
> > the seaside config of the pier app.
> >
> > Lukas
> >
> > On Saturday, August 28, 2010, Lawson English<lenglish5 at cox.net>  wrote:
> >
> >   Hey, helping a friend with his blog at: http://www.morphle.com:8204
> and he's noticed that sometimes, when he goes to a specific blog entry, he
> enters the page at the top and sometimes at the bottom. Is this a random
> behavior or based on some cookie that is set or...?
> >
> >
> > Thanks,
> >
> > Lawson
> >
> >
> >
> > _______________________________________________
> > 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
>



-- 
http://john-mckeon.us/pier
http://john-mckeon.us/f <http://john-mckeon.us/timesheets>ootballpool
 (login: guest/football)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20100828/38aecc78/attachment.html>

From lenglish5 at cox.net  Sun Aug 29 09:35:55 2010
From: lenglish5 at cox.net (Lawson English)
Date: Sun, 29 Aug 2010 00:35:55 -0700
Subject: Minor audio link issue in markup language?
Message-ID: <4C7A0DDB.4080107@cox.net>

  When I use +audio+ to refer to an audio file int he library, it 
displays a QuickTime control widget. When I refer to the audio using a 
url, +http://www.myserver.com/audio.mp3+,   it just shows the link, 
which opens a new window when I click on it.

Is there any way to get an inline auido control widget for an external file?

Thanks,


Lawson



From lenglish5 at cox.net  Sun Aug 29 19:24:44 2010
From: lenglish5 at cox.net (Lawson English)
Date: Sun, 29 Aug 2010 10:24:44 -0700
Subject: Pier Blog has uneven behavior
In-Reply-To: <AANLkTikvRO+e-Km7T1bzdusnpE_FPk_mJ7vgccwZrk-v@mail.gmail.com>
References: <4C7929F3.40700@cox.net>	<AANLkTimyTqQ_9XgKs08pWhENFXvUv_=85cnORq9XKd9i@mail.gmail.com>	<4C797385.8040507@cox.net>	<AANLkTinD+VNrmHZL94W9DV2H2qjOnjAdMoKaMeLFJdue@mail.gmail.com>
	<AANLkTikvRO+e-Km7T1bzdusnpE_FPk_mJ7vgccwZrk-v@mail.gmail.com>
Message-ID: <4C7A97DC.1010807@cox.net>

  On 8/28/10 3:23 PM, John McKeon wrote:
> I think you want to remove PRJavascriptSupport.
> On the *Seaside* config page for the Pier app, about halfway down, 
> under General heading, you should see the libraries listed. Click the 
> configure button to remove the above.
>
>

That did the trick, thanks!


Lawson


From razavi at acm.org  Tue Aug 31 14:23:02 2010
From: razavi at acm.org (Reza Razavi)
Date: Tue, 31 Aug 2010 14:23:02 +0200
Subject: Removing children 
Message-ID: <8bbtuf$35h790@smtp.pt.lu>

Hi all,

It seems that PRRemoveCommand >> doExecute does not remove the 
children of the current structure. Am I missing something, or should 
the following be added just before *self structure remove*:

self structure enumerator contents do: [:aChild | aChild remove ]

Thank you in advance for our response,
Regards,
Reza





From renggli at gmail.com  Tue Aug 31 14:53:54 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Tue, 31 Aug 2010 14:53:54 +0200
Subject: Removing children
In-Reply-To: <8bbtuf$35h790@smtp.pt.lu>
References: <8bbtuf$35h790@smtp.pt.lu>
Message-ID: <AANLkTi=+5xpXs_VDEbEjJqqi9DxCJy6YL1JsMX6vN=MW@mail.gmail.com>

Why do you think this is a problem?

Lukas

On 31 August 2010 14:23, Reza Razavi <razavi at acm.org> wrote:
> Hi all,
>
> It seems that PRRemoveCommand >> doExecute does not remove the children of
> the current structure. Am I missing something, or should the following be
> added just before *self structure remove*:
>
> self structure enumerator contents do: [:aChild | aChild remove ]
>
> Thank you in advance for our response,
> Regards,
> Reza
>
>
>
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>



-- 
Lukas Renggli
www.lukas-renggli.ch

From razavi at acm.org  Tue Aug 31 16:08:34 2010
From: razavi at acm.org (Reza Razavi)
Date: Tue, 31 Aug 2010 16:08:34 +0200
Subject: Removing children
In-Reply-To: <AANLkTi=+5xpXs_VDEbEjJqqi9DxCJy6YL1JsMX6vN=MW@mail.gmail.c
 om>
References: <8bbtuf$35h790@smtp.pt.lu>
	<AANLkTi=+5xpXs_VDEbEjJqqi9DxCJy6YL1JsMX6vN=MW@mail.gmail.com>
Message-ID: <8bbtuf$35ijfu@smtp.pt.lu>

At 14:53 31/08/2010, Lukas Renggli wrote:
>Why do you think this is a problem?

Hi Lukas,

It seems that the children keep pointing to their parent, which is 
the removed structure. I'd expect the children to be removed too, 
actually starting from the leaf nodes. So something like (not tested):

PRRemoveCommand >> removeWithChildren: aStructure

         aStructure hasChildren ifTrue:
                 [ aStructure enumerator contents do: [:aChild | self 
removeWithChildren: aChild ]].
         aStructure remove

PRRemoveCommand >> doExeccute
         [...]
         self removeWithChildren: self structure
         [...]

Does this makes sense?

Regards,
Reza




From renggli at gmail.com  Tue Aug 31 18:13:35 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Tue, 31 Aug 2010 18:13:35 +0200
Subject: Removing children
In-Reply-To: <8bbtuf$35ijfu@smtp.pt.lu>
References: <8bbtuf$35h790@smtp.pt.lu>
	<AANLkTi=+5xpXs_VDEbEjJqqi9DxCJy6YL1JsMX6vN=MW@mail.gmail.com>
	<8bbtuf$35ijfu@smtp.pt.lu>
Message-ID: <AANLkTin=dwhSuqPTSBseVSJVHBpAKWF4+pW5gDdpVKpC@mail.gmail.com>

>> Why do you think this is a problem?
>
> Hi Lukas,
>
> It seems that the children keep pointing to their parent, which is the
> removed structure. I'd expect the children to be removed too, actually
> starting from the leaf nodes. So something like (not tested):

Keeping the relationship is intentional to be able to remove and
reinstall the tree somewhere else. I think the parent link is also
required to be able to restore a deleted page.

So why do you think the parent should be nilled?

Lukas

-- 
Lukas Renggli
www.lukas-renggli.ch

From razavi at acm.org  Tue Aug 31 18:57:24 2010
From: razavi at acm.org (Reza Razavi)
Date: Tue, 31 Aug 2010 18:57:24 +0200
Subject: Removing children
In-Reply-To: <AANLkTin=dwhSuqPTSBseVSJVHBpAKWF4+pW5gDdpVKpC@mail.gmail.c
 om>
References: <8bbtuf$35h790@smtp.pt.lu>
	<AANLkTi=+5xpXs_VDEbEjJqqi9DxCJy6YL1JsMX6vN=MW@mail.gmail.com>
	<8bbtuf$35ijfu@smtp.pt.lu>
	<AANLkTin=dwhSuqPTSBseVSJVHBpAKWF4+pW5gDdpVKpC@mail.gmail.com>
Message-ID: <89dhun$2umsvd@smtp.pt.lu>

At 18:13 31/08/2010, Lukas Renggli wrote:
>Keeping the relationship is intentional to be able to remove and
>reinstall the tree somewhere else. I think the parent link is also
>required to be able to restore a deleted page.

Well noted; thanks for the precisions!

>So why do you think the parent should be nilled?

It seems that the memory space is never released, because even when 
later the *max history* is reached in PRHistoryPersistency, #do: just 
removes from its history collection the context that points to the 
"removed" (hidden?) structure. So, if I understand well, the 
structure will not be garbage collected due to the circular 
relationship between the parent and its children?

Regards,
Reza 


From renggli at gmail.com  Tue Aug 31 19:05:58 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Tue, 31 Aug 2010 19:05:58 +0200
Subject: Removing children
In-Reply-To: <89dhun$2umsvd@smtp.pt.lu>
References: <8bbtuf$35h790@smtp.pt.lu>
	<AANLkTi=+5xpXs_VDEbEjJqqi9DxCJy6YL1JsMX6vN=MW@mail.gmail.com>
	<8bbtuf$35ijfu@smtp.pt.lu>
	<AANLkTin=dwhSuqPTSBseVSJVHBpAKWF4+pW5gDdpVKpC@mail.gmail.com>
	<89dhun$2umsvd@smtp.pt.lu>
Message-ID: <AANLkTikKayO1FG09W1owHeFJoJajPFMk2KHWG8VCBiFY@mail.gmail.com>

On 31 August 2010 18:57, Reza Razavi <razavi at acm.org> wrote:
> At 18:13 31/08/2010, Lukas Renggli wrote:
>>
>> Keeping the relationship is intentional to be able to remove and
>> reinstall the tree somewhere else. I think the parent link is also
>> required to be able to restore a deleted page.
>
> Well noted; thanks for the precisions!
>
>> So why do you think the parent should be nilled?
>
> It seems that the memory space is never released, because even when later
> the *max history* is reached in PRHistoryPersistency, #do: just removes from
> its history collection the context that points to the "removed" (hidden?)
> structure. So, if I understand well, the structure will not be garbage
> collected due to the circular relationship between the parent and its
> children?

If you flush the PRHistoryPersistency the references should go. Unless
they are still referenced somewhere else (e.g. sessions).

I don't think that there are any Smalltalk VMs left that do not
collect circular references.

Lukas

-- 
Lukas Renggli
www.lukas-renggli.ch

From steven at stevenrbaker.com  Tue Aug 31 19:07:11 2010
From: steven at stevenrbaker.com (Steven R. Baker)
Date: Tue, 31 Aug 2010 10:07:11 -0700
Subject: Persisisting Data
Message-ID: <BA22C5C5-13B1-4160-A606-1CAC2BBCE572@stevenrbaker.com>

Hello,

I've deployed Pier to my web server, and started entering data. I accidentally hit Ctrl-C in the wrong window, taking down the squeak VM and losing all of my edits.

My Pier instance is running headless on my server, so I have a few questions. Does the Pier OneClick image have VNC running by default, so I can get in? How do I tell Pier to write its changes to disk immediately from the web interface? Where do I see the interval at which it does this automatically?

Also, has anyone done Disqus integration, or is that something I get to do? :)

Thanks,

-Steven



From renggli at gmail.com  Tue Aug 31 19:17:28 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Tue, 31 Aug 2010 19:17:28 +0200
Subject: Persisisting Data
In-Reply-To: <BA22C5C5-13B1-4160-A606-1CAC2BBCE572@stevenrbaker.com>
References: <BA22C5C5-13B1-4160-A606-1CAC2BBCE572@stevenrbaker.com>
Message-ID: <AANLkTi=KQyGa=v8dgjaghDdafaN78d4dCMVa_U++Q6zB@mail.gmail.com>

> My Pier instance is running headless on my server, so I have a few questions. Does the Pier OneClick image have VNC running by default, so I can get in?

No, you have to install and start it yourself:
http://book.seaside.st/book/advanced/deployment/maintaining/vnc

> How do I tell Pier to write its changes to disk immediately from the web interface? Where do I see the interval at which it does this automatically?

http://localhost:8080/seaside/pier/systemmanagement/persistency

Make sure to set it to 'Image Persistency' before deployment.

There are some settings to choose, as well as you can trigger a
snapshot immediately.

> Also, has anyone done Disqus integration, or is that something I get to do? :)

Not that I know.

Lukas

-- 
Lukas Renggli
www.lukas-renggli.ch

From razavi at acm.org  Tue Aug 31 19:38:47 2010
From: razavi at acm.org (Reza Razavi)
Date: Tue, 31 Aug 2010 19:38:47 +0200
Subject: Removing children
In-Reply-To: <AANLkTikKayO1FG09W1owHeFJoJajPFMk2KHWG8VCBiFY@mail.gmail.c
 om>
References: <8bbtuf$35h790@smtp.pt.lu>
	<AANLkTi=+5xpXs_VDEbEjJqqi9DxCJy6YL1JsMX6vN=MW@mail.gmail.com>
	<8bbtuf$35ijfu@smtp.pt.lu>
	<AANLkTin=dwhSuqPTSBseVSJVHBpAKWF4+pW5gDdpVKpC@mail.gmail.com>
	<89dhun$2umsvd@smtp.pt.lu>
	<AANLkTikKayO1FG09W1owHeFJoJajPFMk2KHWG8VCBiFY@mail.gmail.com>
Message-ID: <89dhun$2un8f5@smtp.pt.lu>

At 19:05 31/08/2010, Lukas Renggli wrote:
>If you flush the PRHistoryPersistency the references should go. Unless
>they are still referenced somewhere else (e.g. sessions).

Well noted, many thanks Lukas!
I'll do more systematic tests regarding this, and also the circular 
references later.

Regards,
Reza