From dhenrich at vmware.com  Tue Jun  1 19:03:48 2010
From: dhenrich at vmware.com (Dale Henrichs)
Date: Tue, 01 Jun 2010 10:03:48 -0700
Subject: [ANN] ConfigurationOfPier version 1.2.1.4 available
Message-ID: <4C053D74.4090609@vmware.com>

new version of ConfigurationOfPier available in
http://www.squeaksource.com/MetacelloRepository.

I've tested the configuration on Pharo 1.0, Squeak 4.1, and GLASS
1.0-beta.8.

On Squeak 4.1 there are 3 failures:

    MAExtensionsTest>>#testTimePrintOn:
    WABacktrackingTest>>#testDictionary
    WABacktrackingTest>>#testOrderedCollection

Dale


From pablogancharov at gmail.com  Tue Jun  1 23:28:42 2010
From: pablogancharov at gmail.com (Pablo Gancharov)
Date: Tue, 1 Jun 2010 18:28:42 -0300
Subject: "Add a Note" addon to pier
Message-ID: <AANLkTinUnPhlr4ZWyD12E0xPO4z22jcQRprzdLQvJr7I@mail.gmail.com>

Hello Lucas, The "User Contributed Notes" component that's shows on
http://book.seaside.st/book/ it's a pier component?
How can I add it to my pier site? Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20100601/097e10ce/attachment.html>

From renggli at gmail.com  Tue Jun  1 23:32:39 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Tue, 1 Jun 2010 23:32:39 +0200
Subject: "Add a Note" addon to pier
In-Reply-To: <AANLkTinUnPhlr4ZWyD12E0xPO4z22jcQRprzdLQvJr7I@mail.gmail.com>
References: <AANLkTinUnPhlr4ZWyD12E0xPO4z22jcQRprzdLQvJr7I@mail.gmail.com>
Message-ID: <AANLkTikGZxLo-ftFQOhZCHuJROovH9pOEYNxL-SwvKle@mail.gmail.com>

The class is called BONoteWidget.

Lukas

On 1 June 2010 23:28, Pablo Gancharov <pablogancharov at gmail.com> wrote:
> Hello Lucas, The "User Contributed Notes" component that's shows on
> http://book.seaside.st/book/ it's a pier component?
> How can I add it to my pier site? Thanks.
>
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>



-- 
Lukas Renggli
www.lukas-renggli.ch

From dhenrich at vmware.com  Wed Jun  2 00:05:11 2010
From: dhenrich at vmware.com (Dale Henrichs)
Date: Tue, 01 Jun 2010 15:05:11 -0700
Subject: [ANN] ConfigurationOfMagritte2 version 2.0.4 available
Message-ID: <4C058417.3060602@vmware.com>

new version of ConfigurationOfMagritte2 available in
http://www.squeaksource.com/MetacelloRepository.

I've tested the configuration on Pharo 1.0 and Squeak 4.1. Magritte2 is 
not yet avaialable on GLASS

On Squeak 4.1 there is 1 failures:

     MAExtensionsTest>>#testTimePrintOn:

Dale

From dhenrich at vmware.com  Wed Jun  2 00:24:49 2010
From: dhenrich at vmware.com (Dale Henrichs)
Date: Tue, 01 Jun 2010 15:24:49 -0700
Subject: [ANN] ConfiguurationOfPier2 version 2.0.55 available
Message-ID: <4C0588B1.8060203@vmware.com>

new version of ConfigurationOfPier2 available in
http://www.squeaksource.com/MetacelloRepository.

I've tested the configuration on Pharo 1.0 and Squeak 4.1. Tests run 
green on both platforms.

Pier2 is not yet avaialable on GLASS.

Dale

From dhenrich at vmware.com  Wed Jun  2 00:28:54 2010
From: dhenrich at vmware.com (Dale Henrichs)
Date: Tue, 01 Jun 2010 15:28:54 -0700
Subject: [ANN] ConfiguurationOfPier2 version 2.0.5 available
In-Reply-To: <4C0588B1.8060203@vmware.com>
References: <4C0588B1.8060203@vmware.com>
Message-ID: <4C0589A6.5030309@vmware.com>

Dale Henrichs wrote:
> new version of ConfigurationOfPier2 available in
> http://www.squeaksource.com/MetacelloRepository.
> 
> I've tested the configuration on Pharo 1.0 and Squeak 4.1. Tests run 
> green on both platforms.
> 
> Pier2 is not yet avaialable on GLASS.
> 
> Dale
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Seems I can't send an email without some sort of error ... that should 
be version 2.0.5...

Dale

From dhenrich at vmware.com  Wed Jun  2 00:47:38 2010
From: dhenrich at vmware.com (Dale Henrichs)
Date: Tue, 01 Jun 2010 15:47:38 -0700
Subject: [Ann] ConfigurationOfPierAddOns2 version 2.0.5 available
Message-ID: <4C058E0A.7030707@vmware.com>

new version of ConfigurationOfPierAddOns2 available in
http://www.squeaksource.com/MetacelloRepository.

Loaded the configuration on Pharo 1.0 and Squeak 4.1.

PierAddOns2 is not yet available on GLASS.

Dale

From dtrussardi at tiscali.it  Fri Jun  4 12:20:10 2010
From: dtrussardi at tiscali.it (dtrussardi at tiscali.it)
Date: Fri, 4 Jun 2010 12:20:10 +0200
Subject: Pier site export - import
Message-ID: <F2856F1C-ECB0-4516-B847-D5032F3691B3@tiscali.it>

Hi,

	i create a Pier site with the relative Gemstone implementation. 

	It's update to Pier 1.2.1.4 and work fine.


	Now i'm interested to port it to a new Gemstone environment.

	I can do  save of the Pier 'structures' relative to my site ?
	
	And after load it in a new environment ?

	
	Any pointers would be greatly appreciated !

	Thank,

		Dario
	

From marianopeck at gmail.com  Fri Jun  4 14:04:37 2010
From: marianopeck at gmail.com (Mariano Martinez Peck)
Date: Fri, 4 Jun 2010 14:04:37 +0200
Subject: Pier site export - import
In-Reply-To: <F2856F1C-ECB0-4516-B847-D5032F3691B3@tiscali.it>
References: <F2856F1C-ECB0-4516-B847-D5032F3691B3@tiscali.it>
Message-ID: <AANLkTinoZH-_OgTV8kCSFxc23qBD2JmKamOxEpzIDmwR@mail.gmail.com>

http://www.lukas-renggli.ch/blog/export-import

On Fri, Jun 4, 2010 at 12:20 PM, dtrussardi at tiscali.it <
dtrussardi at tiscali.it> wrote:

> Hi,
>
>        i create a Pier site with the relative Gemstone implementation.
>
>        It's update to Pier 1.2.1.4 and work fine.
>
>
>        Now i'm interested to port it to a new Gemstone environment.
>
>        I can do  save of the Pier 'structures' relative to my site ?
>
>        And after load it in a new environment ?
>
>
>        Any pointers would be greatly appreciated !
>
>        Thank,
>
>                Dario
>
> _______________________________________________
> 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/20100604/6963d261/attachment.html>

From dtrussardi at tiscali.it  Fri Jun  4 15:02:50 2010
From: dtrussardi at tiscali.it (dtrussardi at tiscali.it)
Date: Fri, 4 Jun 2010 15:02:50 +0200
Subject: Pier site export - import
Message-ID: <784D7482-23B7-43F4-B030-5E886D2378D5@tiscali.it>

Thank,

from:	

> http://www.lukas-renggli.ch/blog/export-import
> 

i read: 

Export the Site
Upgrade to the bleeding edge versions of Magritte and Pier. Also ensure that the package Pier-Squeak-Persistency is loaded and up-to-date.
Add the Import/Export component to one of your admin pages.
Read the instructions and click on Export to generate and download a complete snapshot of your site.


Now in gemstone  i don't  have load  the  Pier-Squeak-Persistency package.

And into	 http://seaside.gemstone.com/ss/pier		 i don't found any	 	Pier-Squeak-Persistency entry.

I do test for	 Pier-Squeak-Persistency	 entry  from		 http://source.lukas-renggli.ch/pier.

When i  load Pier-Squeak-Persistency-kph.24 i found the error: 

	'This package depends on the following classes:
	  ImageSegment
	You must resolve these dependencies before you will be able to load these definitions: 
 	 ImageSegment>>writeKernel:on:
	'

Any idea ?

	Thank,

		Dario

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20100604/600b47fa/attachment-0001.html>

From dhenrich at vmware.com  Fri Jun  4 18:24:28 2010
From: dhenrich at vmware.com (Dale Henrichs)
Date: Fri, 04 Jun 2010 09:24:28 -0700
Subject: Pier site export - import
In-Reply-To: <784D7482-23B7-43F4-B030-5E886D2378D5@tiscali.it>
References: <784D7482-23B7-43F4-B030-5E886D2378D5@tiscali.it>
Message-ID: <4C0928BC.6060105@vmware.com>

Dario,

I will have to get involved in this, since it is a GemStone-Specific 
issue. In the past I have used SIXX to move a Pier instance from Squeak 
to GemStone, but that was awhile back ...

To move from one GemStone version to another GemStone version, it isn't 
necessary to export your data and reimport like it is when changing 
versions of Pharo or any other client Smalltalk.

GemStone does provide an upgrade path that allows you to upgrade your 
installation to a new version...So you can upgrade from GemStone/S 64 
2.3 to GemStone/S 64 2.4.

Based on conversations in the GLASS list, I assume that you are 
interested in upgrading from 2.3 to 2.4 ... if that is the case, I will 
ask you to wait until I've announced a 2.4.x release that is ready for 
GLASS. There are additional upgrade steps that are involved when 
upgrading a GLASS instance that I have not validated, yet (which is why 
I haven't made 2.4.x generally available for GLASS users).

Dale

dtrussardi at tiscali.it wrote:
> Thank,
> 
> from:
> 
> http://www.lukas-renggli.ch/blog/export-import
> 
> 
> i read:
> 
> Export the Site
> 
>  1.  Upgrade<http://www.piercms.com/blog/how-to-upgrade-to-1.1> to the bleeding edge versions of Magritte and Pier. Also ensure that the package Pier-Squeak-Persistency is loaded and up-to-date.
>  2.  Add the Import/Export component to one of your admin pages.
>  3.  Read the instructions and click on Export to generate and download a complete snapshot of your site.
> 
> 
> Now in gemstone  i don't  have load  the  Pier-Squeak-Persistency package.
> 
> And into  http://seaside.gemstone.com/ss/pier  i don't found any   Pier-Squeak-Persistency entry.
> 
> I do test for Pier-Squeak-Persistency entry from http://source.lukas-renggli.ch/pier.
> 
> When i load Pier-Squeak-Persistency-kph.24 i found the error:
> 
> 'This package depends on the following classes: ImageSegment You must resolve these dependencies before you will be able to load these definitions: ImageSegment>>writeKernel:on: '
> 
> Any idea ?
> 
> Thank,
> 
> Dario
> 
> 
> 


From pablogancharov at gmail.com  Fri Jun  4 19:59:59 2010
From: pablogancharov at gmail.com (Pablo Gancharov)
Date: Fri, 4 Jun 2010 14:59:59 -0300
Subject: smallwiki Digest, Vol 53, Issue 2
In-Reply-To: <mailman.6393.1275656589.1939.smallwiki@iam.unibe.ch>
References: <mailman.6393.1275656589.1939.smallwiki@iam.unibe.ch>
Message-ID: <AANLkTil4lh3SAUf_kk71kVnJp8FrH5vpY1eQcbdu5irJ@mail.gmail.com>

> Message: 1
> Date: Tue, 1 Jun 2010 18:28:42 -0300
> From: Pablo Gancharov <pablogancharov at gmail.com>
> Subject: "Add a Note" addon to pier
> To: smallwiki at iam.unibe.ch
> Message-ID:
>        <AANLkTinUnPhlr4ZWyD12E0xPO4z22jcQRprzdLQvJr7I at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hello Lucas, The "User Contributed Notes" component that's shows on
> http://book.seaside.st/book/ it's a pier component?
> How can I add it to my pier site? Thanks.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20100601/097e10ce/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Tue, 1 Jun 2010 23:32:39 +0200
> From: Lukas Renggli <renggli at gmail.com>
> Subject: Re: "Add a Note" addon to pier
> To: "Magritte, Pier and Related Tools ..." <smallwiki at iam.unibe.ch>
> Message-ID:
>        <AANLkTikGZxLo-ftFQOhZCHuJROovH9pOEYNxL-SwvKle at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> The class is called BONoteWidget.
>
> Lukas
>
> On 1 June 2010 23:28, Pablo Gancharov <pablogancharov at gmail.com> wrote:
> > Hello Lucas, The "User Contributed Notes" component that's shows on
> > http://book.seaside.st/book/ it's a pier component?
> > How can I add it to my pier site? Thanks.
> >
> >
> > _______________________________________________
> > Magritte, Pier and Related Tools ...
> > https://www.iam.unibe.ch/mailman/listinfo/smallwiki
> >
>
>
>
> --
> Lukas Renggli
> www.lukas-renggli.ch
>


It is loaded on pier image by default or I have to do something else? I
can't find this component in the pier's list.

By the way I have other question: how is the right way that I should debug
my website that is hosted in sesidehosting.st?, because every time that I
get stucked (I.e. an primiteve has failed massage) I have to re-do all the
job again (I restart the image trough the seasidehosting panel)

Thanks !
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20100604/374807e8/attachment.html>

From marianopeck at gmail.com  Fri Jun  4 23:26:04 2010
From: marianopeck at gmail.com (Mariano Martinez Peck)
Date: Fri, 4 Jun 2010 23:26:04 +0200
Subject: Pier site export - import
In-Reply-To: <784D7482-23B7-43F4-B030-5E886D2378D5@tiscali.it>
References: <784D7482-23B7-43F4-B030-5E886D2378D5@tiscali.it>
Message-ID: <AANLkTimTsaaZ6ckwBTvtsq50uveTtszKlCxYPjsgwTL8@mail.gmail.com>

On Fri, Jun 4, 2010 at 3:02 PM, dtrussardi at tiscali.it <dtrussardi at tiscali.it
> wrote:

> Thank,
>
> from:
>
> http://www.lukas-renggli.ch/blog/export-import
>
>
> i read:
>
> Export the Site
>
>    1. Upgrade <http://www.piercms.com/blog/how-to-upgrade-to-1.1> to the
>    bleeding edge versions of Magritte and Pier. Also ensure that the package
>    Pier-Squeak-Persistency is loaded and up-to-date.
>    2. Add the *Import/Export* component to one of your admin pages.
>    3. Read the instructions and click on *Export* to generate and download
>    a complete snapshot of your site.
>
>
>
> Now in gemstone  i don't  have load  the  Pier-Squeak-Persistency package.
>
> And into  http://seaside.gemstone.com/ss/pier  i don't found any   Pier-Squeak-Persistency
> entry.
>
> I do test for Pier-Squeak-Persistency entry from
> http://source.lukas-renggli.ch/pier.
>
> When i load Pier-Squeak-Persistency-kph.24 i found the error:
>
> 'This package depends on the following classes: ImageSegment You must
> resolve these dependencies before you will be able to load these
> definitions: ImageSegment>>writeKernel:on: '
>


mmmm I though this component use ReferenceStream instead of ImageSegment. I
even have just put a halt in writeKernel:on:
and export my kernel and it didn't stop there...did you do an snapshot
instead of exporting?

can you export the whole stacktrace?



>
> Any idea ?
>
> Thank,
>
> Dario
>
>
> _______________________________________________
> 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/20100604/c05474b8/attachment.html>

From marianopeck at gmail.com  Fri Jun  4 23:26:46 2010
From: marianopeck at gmail.com (Mariano Martinez Peck)
Date: Fri, 4 Jun 2010 23:26:46 +0200
Subject: Pier site export - import
In-Reply-To: <4C0928BC.6060105@vmware.com>
References: <784D7482-23B7-43F4-B030-5E886D2378D5@tiscali.it>
	<4C0928BC.6060105@vmware.com>
Message-ID: <AANLkTikgUaXE0cd5jhucBDcY7QCuanR0gNvQeaNS9cx6@mail.gmail.com>

On Fri, Jun 4, 2010 at 6:24 PM, Dale Henrichs <dhenrich at vmware.com> wrote:

> Dario,
>
> I will have to get involved in this, since it is a GemStone-Specific issue.
> In the past I have used SIXX to move a Pier instance from Squeak to
> GemStone, but that was awhile back ...
>
>
Dale, is ReferenceStream or SmartReferenceStream working in Gemstone?

Cheers

Mariano


> To move from one GemStone version to another GemStone version, it isn't
> necessary to export your data and reimport like it is when changing versions
> of Pharo or any other client Smalltalk.
>
> GemStone does provide an upgrade path that allows you to upgrade your
> installation to a new version...So you can upgrade from GemStone/S 64 2.3 to
> GemStone/S 64 2.4.
>
> Based on conversations in the GLASS list, I assume that you are interested
> in upgrading from 2.3 to 2.4 ... if that is the case, I will ask you to wait
> until I've announced a 2.4.x release that is ready for GLASS. There are
> additional upgrade steps that are involved when upgrading a GLASS instance
> that I have not validated, yet (which is why I haven't made 2.4.x generally
> available for GLASS users).
>
> Dale
>
> dtrussardi at tiscali.it wrote:
>
>> Thank,
>>
>> from:
>>
>> http://www.lukas-renggli.ch/blog/export-import
>>
>>
>> i read:
>>
>> Export the Site
>>
>>  1.  Upgrade<http://www.piercms.com/blog/how-to-upgrade-to-1.1> to the
>> bleeding edge versions of Magritte and Pier. Also ensure that the package
>> Pier-Squeak-Persistency is loaded and up-to-date.
>>  2.  Add the Import/Export component to one of your admin pages.
>>  3.  Read the instructions and click on Export to generate and download a
>> complete snapshot of your site.
>>
>>
>>
>> Now in gemstone  i don't  have load  the  Pier-Squeak-Persistency package.
>>
>> And into  http://seaside.gemstone.com/ss/pier  i don't found any
>> Pier-Squeak-Persistency entry.
>>
>> I do test for Pier-Squeak-Persistency entry from
>> http://source.lukas-renggli.ch/pier.
>>
>> When i load Pier-Squeak-Persistency-kph.24 i found the error:
>>
>> 'This package depends on the following classes: ImageSegment You must
>> resolve these dependencies before you will be able to load these
>> definitions: ImageSegment>>writeKernel:on: '
>>
>> Any idea ?
>>
>> Thank,
>>
>> Dario
>>
>>
>>
>>
> _______________________________________________
> 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/20100604/771a8023/attachment-0001.html>

From dhenrich at vmware.com  Sat Jun  5 00:09:48 2010
From: dhenrich at vmware.com (Dale Henrichs)
Date: Fri, 04 Jun 2010 15:09:48 -0700
Subject: Pier site export - import
In-Reply-To: <AANLkTikgUaXE0cd5jhucBDcY7QCuanR0gNvQeaNS9cx6@mail.gmail.com>
References: <784D7482-23B7-43F4-B030-5E886D2378D5@tiscali.it>	<4C0928BC.6060105@vmware.com>
	<AANLkTikgUaXE0cd5jhucBDcY7QCuanR0gNvQeaNS9cx6@mail.gmail.com>
Message-ID: <4C0979AC.6020408@vmware.com>

I haven't ported either of those to GemStone, instead I ported SIXX, 
since it was designed for transferring object graphs between different 
Smalltalk implementations...

We have an upgrade path that allows one to upgrade versions without 
having to serialize the contents of the db (something that becomes 
unrealistic pretty quickly).

Dale

Mariano Martinez Peck wrote:
> 
> On Fri, Jun 4, 2010 at 6:24 PM, Dale Henrichs <dhenrich at vmware.com<mailto:dhenrich at vmware.com>> wrote:
> Dario,
> 
> I will have to get involved in this, since it is a GemStone-Specific issue. In the past I have used SIXX to move a Pier instance from Squeak to GemStone, but that was awhile back ...
> 
> 
> Dale, is ReferenceStream or SmartReferenceStream working in Gemstone?
> 
> Cheers
> 
> Mariano
> 
> To move from one GemStone version to another GemStone version, it isn't necessary to export your data and reimport like it is when changing versions of Pharo or any other client Smalltalk.
> 
> GemStone does provide an upgrade path that allows you to upgrade your installation to a new version...So you can upgrade from GemStone/S 64 2.3 to GemStone/S 64 2.4.
> 
> Based on conversations in the GLASS list, I assume that you are interested in upgrading from 2.3 to 2.4 ... if that is the case, I will ask you to wait until I've announced a 2.4.x release that is ready for GLASS. There are additional upgrade steps that are involved when upgrading a GLASS instance that I have not validated, yet (which is why I haven't made 2.4.x generally available for GLASS users).
> 
> Dale
> 
> dtrussardi at tiscali.it<mailto:dtrussardi at tiscali.it> wrote:
> Thank,
> 
> from:
> 
> http://www.lukas-renggli.ch/blog/export-import
> 
> 
> i read:
> 
> Export the Site
> 
>  1.  Upgrade<http://www.piercms.com/blog/how-to-upgrade-to-1.1> to the bleeding edge versions of Magritte and Pier. Also ensure that the package Pier-Squeak-Persistency is loaded and up-to-date.
>  2.  Add the Import/Export component to one of your admin pages.
>  3.  Read the instructions and click on Export to generate and download a complete snapshot of your site.
> 
> 
> 
> Now in gemstone  i don't  have load  the  Pier-Squeak-Persistency package.
> 
> And into  http://seaside.gemstone.com/ss/pier  i don't found any   Pier-Squeak-Persistency entry.
> 
> I do test for Pier-Squeak-Persistency entry from http://source.lukas-renggli.ch/pier.
> 
> When i load Pier-Squeak-Persistency-kph.24 i found the error:
> 
> 'This package depends on the following classes: ImageSegment You must resolve these dependencies before you will be able to load these definitions: ImageSegment>>writeKernel:on: '
> 
> Any idea ?
> 
> Thank,
> 
> Dario
> 
> 
> 
> 
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
> 
> 
> 

From dhenrich at vmware.com  Sat Jun  5 00:11:38 2010
From: dhenrich at vmware.com (Dale Henrichs)
Date: Fri, 04 Jun 2010 15:11:38 -0700
Subject: Pier site export - import
In-Reply-To: <AANLkTimTsaaZ6ckwBTvtsq50uveTtszKlCxYPjsgwTL8@mail.gmail.com>
References: <784D7482-23B7-43F4-B030-5E886D2378D5@tiscali.it>
	<AANLkTimTsaaZ6ckwBTvtsq50uveTtszKlCxYPjsgwTL8@mail.gmail.com>
Message-ID: <4C097A1A.3090800@vmware.com>

Since persistence is "built into GemStone" there has not been any need 
for the Persistency package ...

If I remember correctly Lukas based the import/export on SIXX, but I 
haven't had the time to look at those issues yet ...

I'm getting real close, but I'm not there yet:)

Dale

Mariano Martinez Peck wrote:
> 
> On Fri, Jun 4, 2010 at 3:02 PM, dtrussardi at tiscali.it<mailto:dtrussardi at tiscali.it> <dtrussardi at tiscali.it<mailto:dtrussardi at tiscali.it>> wrote:
> Thank,
> 
> from:
> 
> http://www.lukas-renggli.ch/blog/export-import
> 
> 
> i read:
> 
> Export the Site
> 
>  1.  Upgrade<http://www.piercms.com/blog/how-to-upgrade-to-1.1> to the bleeding edge versions of Magritte and Pier. Also ensure that the package Pier-Squeak-Persistency is loaded and up-to-date.
>  2.  Add the Import/Export component to one of your admin pages.
>  3.  Read the instructions and click on Export to generate and download a complete snapshot of your site.
> 
> 
> Now in gemstone  i don't  have load  the  Pier-Squeak-Persistency package.
> 
> And into  http://seaside.gemstone.com/ss/pier  i don't found any   Pier-Squeak-Persistency entry.
> 
> I do test for Pier-Squeak-Persistency entry from http://source.lukas-renggli.ch/pier.
> 
> When i load Pier-Squeak-Persistency-kph.24 i found the error:
> 
> 'This package depends on the following classes: ImageSegment You must resolve these dependencies before you will be able to load these definitions: ImageSegment>>writeKernel:on: '
> 
> 
> mmmm I though this component use ReferenceStream instead of ImageSegment. I even have just put a halt in writeKernel:on:
> and export my kernel and it didn't stop there...did you do an snapshot instead of exporting?
> 
> can you export the whole stacktrace?
> 
> 
> 
> Any idea ?
> 
> Thank,
> 
> Dario
> 
> 
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
> 
> 
> 


From sergiolist at village-buzz.com  Sat Jun  5 18:28:16 2010
From: sergiolist at village-buzz.com (sergio_101)
Date: Sat, 5 Jun 2010 12:28:16 -0400
Subject: Comment: Input is conflicting with concurrent modification
Message-ID: <AANLkTikDr7MVHe2OeqW7LodNXUbyFzjF_xcx_gfFFNew@mail.gmail.com>

for some reason, no one can add comments to my site.. they are getting
the above error.

i tried it, and i am getting the same thing..

is there any way to clear this?


-- 
----
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 sergiolist at village-buzz.com  Mon Jun  7 17:38:21 2010
From: sergiolist at village-buzz.com (sergio_101)
Date: Mon, 7 Jun 2010 11:38:21 -0400
Subject: email on comment
Message-ID: <AANLkTiniuA1WRc4PAAdF_rkGRGb1KnYsGkya2FoRAIyE@mail.gmail.com>

is there anything already set up that has the system email the admin
when a new comment is added to the blog?

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 lefraternite at googlemail.com  Tue Jun  8 16:08:24 2010
From: lefraternite at googlemail.com (Sloan)
Date: Tue, 8 Jun 2010 16:08:24 +0200
Subject: adding css id in magritte forms
Message-ID: <AANLkTikPwc__4zF3EnQCg7yudsbEEXrw_bWdFvm5smah@mail.gmail.com>

Hello,

I'd like to add an id tag to a magritte generated form (like so <form
id="something" ...). Is there a chance to do this? I already know I can
assign a css id to a container around the form, but that's not what I want.
The seaside testing framework requires an id in the form.
Also, I am using the MACssRenderer in one of my models. However, if I subset
the descriptions to create a form magritte will use the table renderer
instead.

Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20100608/565af3bc/attachment.html>

From renggli at gmail.com  Tue Jun  8 17:54:03 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Tue, 8 Jun 2010 17:54:03 +0200
Subject: email on comment
In-Reply-To: <AANLkTiniuA1WRc4PAAdF_rkGRGb1KnYsGkya2FoRAIyE@mail.gmail.com>
References: <AANLkTiniuA1WRc4PAAdF_rkGRGb1KnYsGkya2FoRAIyE@mail.gmail.com>
Message-ID: <AANLkTinfvNHKuwjyapaEUomEiJJuoLQLxap-MDyvhwW5@mail.gmail.com>

Not that I know, but if you subscribe to the comments feed you should
get notified about comments too.

Lukas

On 7 June 2010 17:38, sergio_101 <sergiolist at village-buzz.com> wrote:
> is there anything already set up that has the system email the admin
> when a new comment is added to the blog?
>
> 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  Wed Jun  9 07:01:14 2010
From: sergiolist at village-buzz.com (sergio_101)
Date: Wed, 9 Jun 2010 01:01:14 -0400
Subject: email on comment
In-Reply-To: <AANLkTinfvNHKuwjyapaEUomEiJJuoLQLxap-MDyvhwW5@mail.gmail.com>
References: <AANLkTiniuA1WRc4PAAdF_rkGRGb1KnYsGkya2FoRAIyE@mail.gmail.com>
	<AANLkTinfvNHKuwjyapaEUomEiJJuoLQLxap-MDyvhwW5@mail.gmail.com>
Message-ID: <AANLkTil2sbIw85O2BygXdy7vQWHCfCAn4Z-71Ay3fRdH@mail.gmail.com>

On Tue, Jun 8, 2010 at 11:54 AM, Lukas Renggli <renggli at gmail.com> wrote:
> Not that I know, but if you subscribe to the comments feed you should
> get notified about comments too.
>
oooh.. good idea..

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  Wed Jun  9 12:20:31 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Wed, 9 Jun 2010 12:20:31 +0200
Subject: adding css id in magritte forms
In-Reply-To: <AANLkTikPwc__4zF3EnQCg7yudsbEEXrw_bWdFvm5smah@mail.gmail.com>
References: <AANLkTikPwc__4zF3EnQCg7yudsbEEXrw_bWdFvm5smah@mail.gmail.com>
Message-ID: <AANLkTikObLJd1-Nc9LvqLFw3rW6zU6AMDTfhNLElydQG@mail.gmail.com>

It is not supported because some Magritte rendered use automatically
generated IDs. Use (unique) CSS classes.

Lukas

On 8 June 2010 16:08, Sloan <lefraternite at googlemail.com> wrote:
> Hello,
>
> I'd like to add an id tag to a magritte generated form (like so <form
> id="something" ...). Is there a chance to do this? I already know I can
> assign a css id to a container around the form, but that's not what I want.
> The seaside testing framework requires an id in the form.
> Also, I am using the MACssRenderer in one of my models. However, if I subset
> the descriptions to create a form magritte will use the table renderer
> instead.
>
> Regards
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>



-- 
Lukas Renggli
www.lukas-renggli.ch

From lefraternite at googlemail.com  Wed Jun  9 14:22:18 2010
From: lefraternite at googlemail.com (SLoan)
Date: Wed, 09 Jun 2010 14:22:18 +0200
Subject: adding css id in magritte forms
In-Reply-To: <AANLkTikObLJd1-Nc9LvqLFw3rW6zU6AMDTfhNLElydQG@mail.gmail.com>
References: <AANLkTikPwc__4zF3EnQCg7yudsbEEXrw_bWdFvm5smah@mail.gmail.com>
	<AANLkTikObLJd1-Nc9LvqLFw3rW6zU6AMDTfhNLElydQG@mail.gmail.com>
Message-ID: <4C0F877A.7070808@gmail.com>

Okay thanks. My second issue was that if I subset the descriptions it 
will only use the MATableRenderer by default.

((self descriptionSomething,
    ....) asComponentOn: aModel) addValidatedForm;
returns a table layout. Is it possible to specify a CssRenderer?

Regards,
Sloan

Am 09.06.2010 12:20, schrieb Lukas Renggli:
> It is not supported because some Magritte rendered use automatically
> generated IDs. Use (unique) CSS classes.
>
> Lukas
>
> On 8 June 2010 16:08, Sloan<lefraternite at googlemail.com>  wrote:
>    
>> Hello,
>>
>> I'd like to add an id tag to a magritte generated form (like so<form
>> id="something" ...). Is there a chance to do this? I already know I can
>> assign a css id to a container around the form, but that's not what I want.
>> The seaside testing framework requires an id in the form.
>> Also, I am using the MACssRenderer in one of my models. However, if I subset
>> the descriptions to create a form magritte will use the table renderer
>> instead.
>>
>> Regards
>>
>> _______________________________________________
>> Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>
>>      
>
>
>    

From luc.fabresse at gmail.com  Thu Jun 10 11:21:59 2010
From: luc.fabresse at gmail.com (Luc Fabresse)
Date: Thu, 10 Jun 2010 11:21:59 +0200
Subject: [ANN] ESUG Awards 2010
Message-ID: <AANLkTincZZifEG6xcgQvuLcw1lpvmL_BgMCwpqDNn8e2@mail.gmail.com>

Dear Smalltalkers,

You are invited to submit your nice Smalltalk based software to the 7th ESUG
Innovation Technology Awards. The top 3 teams with the most innovative
software will receive, respectively, 500 Euros, 300 Euros and 200 Euros
during an awards ceremony at the 18th International Smalltalk Joint
Conference 2009 in Brest, France.
No constraints are put on the software except that it should be
Smalltalk-based or Smalltalk-related and all flavours of Smalltalk are
accepted.

More details on the web:
http://www.esug.org/Conferences/2010/Innovation+Technology+Awards
Results of the 2009 edition:
http://www.esug.org/Conferences/2009/Innovation+Technology+Awards/Winners+and+Nominations

Luc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20100610/0b1b152b/attachment.html>

From nick.ager at gmail.com  Fri Jun 11 21:26:40 2010
From: nick.ager at gmail.com (Nick Ager)
Date: Fri, 11 Jun 2010 20:26:40 +0100
Subject: changing a magritte description dynamically
Message-ID: <AANLkTikVaVnVEiVueBP7LBjxmknhBv8lMhWQD3Sk8Sfw@mail.gmail.com>

Hi,

I have a form that's using generated via Magritte descriptions. I'd like to
be able to change the label on one of the fields dynamically. I thought I'd
found the solution by overriding #description on the instance-side and
editing the field's description as in:

description
| description pricePerUnitDescription |
self halt.
description := super description.
pricePerUnitDescription := description detect: [:each| each accessor
readSelector == #pricePerUnit].
self addCurrencyToDescriptionLabel: pricePerUnitDescription.

^ description

However it seems that the description is cached so this method is rarely
called.

Any thoughts on how to dynamically change the label in a magritte field
greatly received.

Thanks

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

From renggli at gmail.com  Sat Jun 12 01:03:49 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Sat, 12 Jun 2010 01:03:49 +0200
Subject: changing a magritte description dynamically
In-Reply-To: <AANLkTikVaVnVEiVueBP7LBjxmknhBv8lMhWQD3Sk8Sfw@mail.gmail.com>
References: <AANLkTikVaVnVEiVueBP7LBjxmknhBv8lMhWQD3Sk8Sfw@mail.gmail.com>
Message-ID: <AANLkTikZ0Apjwfkr0mfIwIhmERisJSrJdi--M-2jWEGl@mail.gmail.com>

On 11 June 2010 21:26, Nick Ager <nick.ager at gmail.com> wrote:
> Hi,
> I have a form that's using generated via Magritte descriptions. I'd like to
> be able to change the label on one of the fields dynamically. I thought I'd
> found the solution by overriding #description on the instance-side and
> editing the field's description as in:
> description
> | description pricePerUnitDescription |
> self halt.
> description := super description.
> pricePerUnitDescription := description detect: [:each| each accessor
> readSelector == #pricePerUnit].
> self addCurrencyToDescriptionLabel: pricePerUnitDescription.
> ^ description
> However it seems that the description is cached so this method is rarely
> called.
> Any thoughts on how to?dynamically change the label in a magritte field
> greatly received.

Only the description on the class-side is cached, the #description
method one the instance-side is called whenever a form, report, query,
... is made.

Lukas



> 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  Sat Jun 12 14:03:26 2010
From: nick.ager at gmail.com (Nick Ager)
Date: Sat, 12 Jun 2010 13:03:26 +0100
Subject: changing a magritte description dynamically
In-Reply-To: <AANLkTikZ0Apjwfkr0mfIwIhmERisJSrJdi--M-2jWEGl@mail.gmail.com>
References: <AANLkTikVaVnVEiVueBP7LBjxmknhBv8lMhWQD3Sk8Sfw@mail.gmail.com>
	<AANLkTikZ0Apjwfkr0mfIwIhmERisJSrJdi--M-2jWEGl@mail.gmail.com>
Message-ID: <AANLkTikT1HvFBxvm9VQIyBmiPceA-sLMnwch-C3lFMhM@mail.gmail.com>

>
>
> Only the description on the class-side is cached, the #description
> method one the instance-side is called whenever a form, report, query,
> ... is made.
>
> Lukas


Thanks Lukas. I fixed the problem by changing my code:

quotationsTable := MAReport rows: quotations description: IZQuotation
description

to:

quotationsTable := MAReport rows: quotations description: quotations first
description

That is I'm now calling #description from the instance side rather than the
class side. Made sense once I'd thought about it

Thanks

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

From nick.ager at gmail.com  Sun Jun 13 15:22:37 2010
From: nick.ager at gmail.com (Nick Ager)
Date: Sun, 13 Jun 2010 14:22:37 +0100
Subject: WAResponseGenerator>>expiredKey
Message-ID: <AANLkTikFPzSBMcIclMt4iHffPynn1OSZLksu-_ph9iEq@mail.gmail.com>

Hi,

Selecting a different look using Pier's PRDesignChooserWidget causes
an WAUnregisteredHandlerError exception to be raised. This occurs on the
latest builds: http://hudson.lukas-renggli.ch/job/Pier%202/lastBuild/

The PRDesignChooserWidget registers 'pier' with the new structure in place
then sends an #expiredKey response as:

    self requestContext responseGenerator
        expiredKey;
        respond

The problem appears to be in a change to WAResponseGenerator>>expiredKey,
which was introduced:

---
Name: Seaside-Core-YM.639
Author: YM
Time: 22 May 2010, 7:39:33 pm
UUID: e24bae83-3671-4679-ac8d-9f21154c304e
Ancestors: Seaside-Core-pmm.638

http://code.google.com/p/seaside/issues/detail?id=552

- Corrected WAResponseGenerator>>#expiredKey to always use the correct URL
- Implemented WAPathConsumer>>#upToEnd
----

The exception is thrown in the line:
url := self requestContext handler url.

#handler returns a WASession which I presume wasn't expected when the code
was written.

Changing the code to:

url := self requestContext request url

stops the exception from being thrown, but doesn't result in a URL free from
keys; not the desired effect. I found a handy Pier extension method
WAUrl>>purgeSeasideFields.The rewritten WAResponseGenerator>>expiredKey then
becomes:

expiredKey
"The session key has expired, redirect the request to the home directory
preserving the path as well as possible."

| url |
self request isXmlHttpRequest
ifTrue: [ ^ self forbidden ].
url := self requestContext request url.
url addAllToPath: self requestContext consumer upToEnd.
self request isGet ifTrue: [
url purgeSeasideFields].
self response redirectTo: url

With the requirement that the WAUrl>>purgeSeasideFields is moved from
Pier-Seaside-Mapping into Seaside-Core-HTTP.

Thoughts?

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

From nick.ager at gmail.com  Mon Jun 14 00:47:34 2010
From: nick.ager at gmail.com (Nick Ager)
Date: Sun, 13 Jun 2010 23:47:34 +0100
Subject: WAResponseGenerator>>expiredKey
In-Reply-To: <AANLkTikFPzSBMcIclMt4iHffPynn1OSZLksu-_ph9iEq@mail.gmail.com>
References: <AANLkTikFPzSBMcIclMt4iHffPynn1OSZLksu-_ph9iEq@mail.gmail.com>
Message-ID: <AANLkTinzSEF-JwNF2HI2WhPQPjJWFv0mpp3a4K7R_6lG@mail.gmail.com>

Under Julian's guidance we fixed this issue, with both a fix to
Seaside WAResponseGenerator>> expiredRegistryKey and some fixes to
PRDesignChooserWidget>>renderContentOn:


Name: Seaside-Core-Nick.644
Author: Nick
Time: 13 June 2010, 5:57:22 pm
UUID: 967def9d-0131-4ec8-bd40-b27d13987f57
Ancestors: Seaside-Core-pmm.643

Fix #expiredKey to use the registry URL instead of the session URL when
redirecting. Then rename it to #expiredRegistryKey in order to be explicit.

----

Name: Pier-Setup-Nick.84
Author: Nick
Time: 13 June 2010, 5:53:32 pm
UUID: 450e1618-0911-4061-91e6-ede14bdfcb58
Ancestors: Pier-Setup-lr.83

redirecting back to Pier after a new application is registered didn't work
on latest Seaside. New implementation more specific about what we're trying
to achieve.  Consider reviewing code in PRDistribution>>register

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

From renggli at gmail.com  Mon Jun 14 07:18:29 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Mon, 14 Jun 2010 07:18:29 +0200
Subject: [Seaside-dev] Re: WAResponseGenerator>>expiredKey
In-Reply-To: <AANLkTinzSEF-JwNF2HI2WhPQPjJWFv0mpp3a4K7R_6lG@mail.gmail.com>
References: <AANLkTikFPzSBMcIclMt4iHffPynn1OSZLksu-_ph9iEq@mail.gmail.com> 
	<AANLkTinzSEF-JwNF2HI2WhPQPjJWFv0mpp3a4K7R_6lG@mail.gmail.com>
Message-ID: <AANLkTilJYPISj7ZMG-_OPbfkEnH9Ot-TTv6uXXManBCj@mail.gmail.com>

It is great that this issue could be fixed so quickly :-)

Lukas

On 14 June 2010 00:47, Nick Ager <nick.ager at gmail.com> wrote:
> Under Julian's guidance we fixed this issue, with both a fix to
> Seaside?WAResponseGenerator>>?expiredRegistryKey and some fixes to
> PRDesignChooserWidget>>renderContentOn:
>
> Name: Seaside-Core-Nick.644
> Author: Nick
> Time: 13 June 2010, 5:57:22 pm
> UUID: 967def9d-0131-4ec8-bd40-b27d13987f57
> Ancestors: Seaside-Core-pmm.643
> Fix #expiredKey to use the registry URL instead of the session URL when
> redirecting. Then rename it to #expiredRegistryKey in order to be explicit.
> ----
> Name: Pier-Setup-Nick.84
> Author: Nick
> Time: 13 June 2010, 5:53:32 pm
> UUID: 450e1618-0911-4061-91e6-ede14bdfcb58
> Ancestors: Pier-Setup-lr.83
> redirecting back to Pier after a new application is registered didn't work
> on latest Seaside. New implementation more specific about what we're trying
> to achieve. ?Consider reviewing code in PRDistribution>>register
> --
>
> _______________________________________________
> 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 lenglish5 at cox.net  Mon Jun 14 07:44:45 2010
From: lenglish5 at cox.net (Lawson English)
Date: Sun, 13 Jun 2010 22:44:45 -0700
Subject: Auto login page for pier...
Message-ID: <4C15C1CD.9080509@cox.net>

Is there an option for a page similar to this for Pier?

https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Suggestions on how to make my own, if there isn't?

Thanks.

Lawson

From renggli at gmail.com  Mon Jun 14 07:47:22 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Mon, 14 Jun 2010 07:47:22 +0200
Subject: Auto login page for pier...
In-Reply-To: <4C15C1CD.9080509@cox.net>
References: <4C15C1CD.9080509@cox.net>
Message-ID: <AANLkTimycx1xUNxYCVicVt926VYgovju_aTz_LavxXNj@mail.gmail.com>

I don't understand what exactly you are trying to do, can you explain?

Lukas

On 14 June 2010 07:44, Lawson English <lenglish5 at cox.net> wrote:
> Is there an option for a page similar to this for Pier?
>
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>
> Suggestions on how to make my own, if there isn't?
>
> 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  Mon Jun 14 08:30:35 2010
From: lenglish5 at cox.net (Lawson English)
Date: Sun, 13 Jun 2010 23:30:35 -0700
Subject: Auto login page for pier...
In-Reply-To: <AANLkTimycx1xUNxYCVicVt926VYgovju_aTz_LavxXNj@mail.gmail.com>
References: <4C15C1CD.9080509@cox.net>
	<AANLkTimycx1xUNxYCVicVt926VYgovju_aTz_LavxXNj@mail.gmail.com>
Message-ID: <4C15CC8B.7080604@cox.net>

On 6/13/10 10:47 PM, Lukas Renggli wrote:

> I don't understand what exactly you are trying to do, can you explain?
>
>    


Well, it would be ok for people to register  automatically without 
administrator interaction: just enter a name and password and they're set.



Lawson

From dhenrich at vmware.com  Wed Jun 16 21:23:55 2010
From: dhenrich at vmware.com (Dale Henrichs)
Date: Wed, 16 Jun 2010 12:23:55 -0700
Subject: MAReportComponent>>renderTableCaptionOn: sends #caption ... #caption
	not implemented
Message-ID: <4C1924CB.7070109@vmware.com>

Not sure where to report Magritte bugs....

This is in Magritte-Seaside-lr.335 ... #caption is sent to a 
description, but I haven't found any implementors ... is this a bug 
waiting to happen or is magic involved:)

Dale

From dhenrich at vmware.com  Wed Jun 16 21:37:20 2010
From: dhenrich at vmware.com (Dale Henrichs)
Date: Wed, 16 Jun 2010 12:37:20 -0700
Subject: several uses of #ifNotNil: in PierSecurity  (Pier2)
Message-ID: <4C1927F0.8040208@vmware.com>

I'm porting to Pier2  to GemStone and ran into several places where 
#ifNotNil: is being used ... what is the accepted replacement for 
#ifNotNil: ... I can clean these up as part of my port.

Dale

From renggli at gmail.com  Wed Jun 16 23:01:30 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Wed, 16 Jun 2010 23:01:30 +0200
Subject: MAReportComponent>>renderTableCaptionOn: sends #caption ... 
	#caption not implemented
In-Reply-To: <4C1924CB.7070109@vmware.com>
References: <4C1924CB.7070109@vmware.com>
Message-ID: <AANLkTimrARIsrXJxVRuoyQCtHJ6zvnMJ1SBQ_MqzBI1R@mail.gmail.com>

Actually I don't know where MAReportComponent is coming from?

Seems to be a long obsolete class, it should be removed. I don't see
how it can work. Use MAReport.

Lukas

-- 
Lukas Renggli
www.lukas-renggli.ch

From renggli at gmail.com  Wed Jun 16 23:02:54 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Wed, 16 Jun 2010 23:02:54 +0200
Subject: MAReportComponent>>renderTableCaptionOn: sends #caption ... 
	#caption not implemented
In-Reply-To: <4C1924CB.7070109@vmware.com>
References: <4C1924CB.7070109@vmware.com>
Message-ID: <AANLkTilCwtvH9YBYIDhbrP2vvvcuGx3S1X2xnFWaXOou@mail.gmail.com>

> Not sure where to report Magritte bugs....

There is a bug tracker:

http://code.google.com/p/magritte-metamodel/

Lukas

>
> This is in Magritte-Seaside-lr.335 ... #caption is sent to a description,
> but I haven't found any implementors ... is this a bug waiting to happen or
> is magic involved:)
>
> Dale
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>



-- 
Lukas Renggli
www.lukas-renggli.ch

From dhenrich at vmware.com  Wed Jun 16 23:06:25 2010
From: dhenrich at vmware.com (Dale Henrichs)
Date: Wed, 16 Jun 2010 14:06:25 -0700
Subject: MAReportComponent>>renderTableCaptionOn: sends #caption ... 
	#caption not implemented
In-Reply-To: <AANLkTilCwtvH9YBYIDhbrP2vvvcuGx3S1X2xnFWaXOou@mail.gmail.com>
References: <4C1924CB.7070109@vmware.com>
	<AANLkTilCwtvH9YBYIDhbrP2vvvcuGx3S1X2xnFWaXOou@mail.gmail.com>
Message-ID: <4C193CD1.3000407@vmware.com>

Lukas Renggli wrote:
>> Not sure where to report Magritte bugs....
> 
> There is a bug tracker:
> 
> http://code.google.com/p/magritte-metamodel/
> 
> Lukas
> 
>> This is in Magritte-Seaside-lr.335 ... #caption is sent to a description,
>> but I haven't found any implementors ... is this a bug waiting to happen or
>> is magic involved:)
>>
>> Dale
>> _______________________________________________
>> Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>
> 
> 
> 
Ah, the "Report Issue" link on your Magritte page points to:

 
http://bugs.squeak.org/set_project.php?project_id=9&make_default=no&ref=bug_report_page.php

I'll report a bug and then remove that class:)

Thanks,

Dale

From renggli at gmail.com  Wed Jun 16 23:06:26 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Wed, 16 Jun 2010 23:06:26 +0200
Subject: several uses of #ifNotNil: in PierSecurity (Pier2)
In-Reply-To: <4C1927F0.8040208@vmware.com>
References: <4C1927F0.8040208@vmware.com>
Message-ID: <AANLkTilkZZxdK3Vxm_6k20xR7z509xJgYJwt5_wfSWNz@mail.gmail.com>

I don't see any senders in my image.

Actually #ifNotNil: is accepted by Slime, the rewrite rules we follow are these:

	self rewriteRule
		replace: '``@boolean ifNotNilDo: ``@block'
			with: '``@boolean ifNotNil: ``@block';
		replace: '``@boolean ifNotNilDo: ``@block1 ifNil: ``@block2'
			with: '``@boolean ifNotNil: ``@block1 ifNil: ``@block2';
		replace: '``@boolean ifNil: ``@block1 ifNotNilDo: ``@block2'
			with: '``@boolean ifNil: ``@block1 ifNotNil: ``@block2';
		replace: '``@boolean ifNotNil: [ | `@temps | ``@.body ]'
			with: '``@boolean ifNotNil: [ :arg | | `@temps | ``@.body ]';
		replace: '``@boolean ifNotNil: [ | `@temps | ``@.body ] ifNil: ``@block '
			with: '``@boolean ifNotNil: [ :arg | | `@temps | ``@.body ] ifNil: ``@block';
		replace: '``@boolean ifNil: ``@block ifNotNil: [ | `@temps | ``@.body ]'
			with: '``@boolean ifNil: ``@block ifNotNil: [ :arg | | `@temps | ``@.body ]'

Personally I only use #ifNil: for lazy accessors, otherwise I don't
like these constructs.

Lukas

On 16 June 2010 21:37, Dale Henrichs <dhenrich at vmware.com> wrote:
> I'm porting to Pier2 ?to GemStone and ran into several places where
> #ifNotNil: is being used ... what is the accepted replacement for #ifNotNil:
> ... I can clean these up as part of my port.
>
> Dale
> _______________________________________________
> 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 Jun 16 23:08:44 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Wed, 16 Jun 2010 23:08:44 +0200
Subject: MAReportComponent>>renderTableCaptionOn: sends #caption ... 
	#caption not implemented
In-Reply-To: <4C193CD1.3000407@vmware.com>
References: <4C1924CB.7070109@vmware.com>
	<AANLkTilCwtvH9YBYIDhbrP2vvvcuGx3S1X2xnFWaXOou@mail.gmail.com> 
	<4C193CD1.3000407@vmware.com>
Message-ID: <AANLkTimSp4jtNjk_mE-8AsL9k6R7batBLzvNNj2Z-zaT@mail.gmail.com>

Ahh, that is outdated for a long time. Thanks for pointing out, it is fixed now.

Lukas

On 16 June 2010 23:06, Dale Henrichs <dhenrich at vmware.com> wrote:
> Lukas Renggli wrote:
>>>
>>> Not sure where to report Magritte bugs....
>>
>> There is a bug tracker:
>>
>> http://code.google.com/p/magritte-metamodel/
>>
>> Lukas
>>
>>> This is in Magritte-Seaside-lr.335 ... #caption is sent to a description,
>>> but I haven't found any implementors ... is this a bug waiting to happen
>>> or
>>> is magic involved:)
>>>
>>> Dale
>>> _______________________________________________
>>> Magritte, Pier and Related Tools ...
>>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>>
>>
>>
>>
> Ah, the "Report Issue" link on your Magritte page points to:
>
>
> http://bugs.squeak.org/set_project.php?project_id=9&make_default=no&ref=bug_report_page.php
>
> I'll report a bug and then remove that class:)
>
> Thanks,
>
> Dale
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>



-- 
Lukas Renggli
www.lukas-renggli.ch

From dhenrich at vmware.com  Wed Jun 16 23:17:34 2010
From: dhenrich at vmware.com (Dale Henrichs)
Date: Wed, 16 Jun 2010 14:17:34 -0700
Subject: several uses of #ifNotNil: in PierSecurity (Pier2)
In-Reply-To: <AANLkTilkZZxdK3Vxm_6k20xR7z509xJgYJwt5_wfSWNz@mail.gmail.com>
References: <4C1927F0.8040208@vmware.com>
	<AANLkTilkZZxdK3Vxm_6k20xR7z509xJgYJwt5_wfSWNz@mail.gmail.com>
Message-ID: <4C193F6E.7010500@vmware.com>

Lukas,

The senders (using the non-portable variant with unary block arg) are 
all in Pier-Security-lr.165.

Dale

Lukas Renggli wrote:
> I don't see any senders in my image.
> 
> Actually #ifNotNil: is accepted by Slime, the rewrite rules we follow are these:
> 
> 	self rewriteRule
> 		replace: '``@boolean ifNotNilDo: ``@block'
> 			with: '``@boolean ifNotNil: ``@block';
> 		replace: '``@boolean ifNotNilDo: ``@block1 ifNil: ``@block2'
> 			with: '``@boolean ifNotNil: ``@block1 ifNil: ``@block2';
> 		replace: '``@boolean ifNil: ``@block1 ifNotNilDo: ``@block2'
> 			with: '``@boolean ifNil: ``@block1 ifNotNil: ``@block2';
> 		replace: '``@boolean ifNotNil: [ | `@temps | ``@.body ]'
> 			with: '``@boolean ifNotNil: [ :arg | | `@temps | ``@.body ]';
> 		replace: '``@boolean ifNotNil: [ | `@temps | ``@.body ] ifNil: ``@block '
> 			with: '``@boolean ifNotNil: [ :arg | | `@temps | ``@.body ] ifNil: ``@block';
> 		replace: '``@boolean ifNil: ``@block ifNotNil: [ | `@temps | ``@.body ]'
> 			with: '``@boolean ifNil: ``@block ifNotNil: [ :arg | | `@temps | ``@.body ]'
> 
> Personally I only use #ifNil: for lazy accessors, otherwise I don't
> like these constructs.
> 
> Lukas
> 
> On 16 June 2010 21:37, Dale Henrichs <dhenrich at vmware.com> wrote:
>> I'm porting to Pier2  to GemStone and ran into several places where
>> #ifNotNil: is being used ... what is the accepted replacement for #ifNotNil:
>> ... I can clean these up as part of my port.
>>
>> Dale
>> _______________________________________________
>> Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>
> 
> 
> 


From dhenrich at vmware.com  Wed Jun 16 23:23:15 2010
From: dhenrich at vmware.com (Dale Henrichs)
Date: Wed, 16 Jun 2010 14:23:15 -0700
Subject: several uses of #ifNotNil: in PierSecurity (Pier2)
In-Reply-To: <4C193F6E.7010500@vmware.com>
References: <4C1927F0.8040208@vmware.com>	<AANLkTilkZZxdK3Vxm_6k20xR7z509xJgYJwt5_wfSWNz@mail.gmail.com>
	<4C193F6E.7010500@vmware.com>
Message-ID: <4C1940C3.6080904@vmware.com>

I did a #senders in Pharo 1.0 with Pier installed  and the offenders 
don't show up, but if you look at the following methods you'll see them:

   PRStructure>>group:
   PRStructure>>owner:
   PUSecurity class>>onStructureAdded:

other senders (using the zero arg form) are:

   MAComponentRenderer>>hasError:
   MAFileUploadComponent>>remove
   PRCase>>document:

Seems that there is a bug in senders...

Dale

Dale Henrichs wrote:
> Lukas,
> 
> The senders (using the non-portable variant with unary block arg) are 
> all in Pier-Security-lr.165.
> 
> Dale
> 
> Lukas Renggli wrote:
>> I don't see any senders in my image.
>>
>> Actually #ifNotNil: is accepted by Slime, the rewrite rules we follow are these:
>>
>> 	self rewriteRule
>> 		replace: '``@boolean ifNotNilDo: ``@block'
>> 			with: '``@boolean ifNotNil: ``@block';
>> 		replace: '``@boolean ifNotNilDo: ``@block1 ifNil: ``@block2'
>> 			with: '``@boolean ifNotNil: ``@block1 ifNil: ``@block2';
>> 		replace: '``@boolean ifNil: ``@block1 ifNotNilDo: ``@block2'
>> 			with: '``@boolean ifNil: ``@block1 ifNotNil: ``@block2';
>> 		replace: '``@boolean ifNotNil: [ | `@temps | ``@.body ]'
>> 			with: '``@boolean ifNotNil: [ :arg | | `@temps | ``@.body ]';
>> 		replace: '``@boolean ifNotNil: [ | `@temps | ``@.body ] ifNil: ``@block '
>> 			with: '``@boolean ifNotNil: [ :arg | | `@temps | ``@.body ] ifNil: ``@block';
>> 		replace: '``@boolean ifNil: ``@block ifNotNil: [ | `@temps | ``@.body ]'
>> 			with: '``@boolean ifNil: ``@block ifNotNil: [ :arg | | `@temps | ``@.body ]'
>>
>> Personally I only use #ifNil: for lazy accessors, otherwise I don't
>> like these constructs.
>>
>> Lukas
>>
>> On 16 June 2010 21:37, Dale Henrichs <dhenrich at vmware.com> wrote:
>>> I'm porting to Pier2  to GemStone and ran into several places where
>>> #ifNotNil: is being used ... what is the accepted replacement for #ifNotNil:
>>> ... I can clean these up as part of my port.
>>>
>>> Dale
>>> _______________________________________________
>>> 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


From dhenrich at vmware.com  Wed Jun 16 23:31:50 2010
From: dhenrich at vmware.com (Dale Henrichs)
Date: Wed, 16 Jun 2010 14:31:50 -0700
Subject: several uses of #ifNotNil: in PierSecurity (Pier2)
In-Reply-To: <AANLkTilkZZxdK3Vxm_6k20xR7z509xJgYJwt5_wfSWNz@mail.gmail.com>
References: <4C1927F0.8040208@vmware.com>
	<AANLkTilkZZxdK3Vxm_6k20xR7z509xJgYJwt5_wfSWNz@mail.gmail.com>
Message-ID: <4C1942C6.1070803@vmware.com>

Lukas,

Unless I misunderstand the rewrite rules, doesn't the following rule end 
up as a noop (ifNotNil: isn't really converted):

   replace: '``@boolean ifNotNil: [ | `@temps | ``@.body ]'
      with: '``@boolean ifNotNil: [ :arg | | `@temps | ``@.body ]';

and worse yet the `ifNotNil: [:arg|]` form isn't supported by GemStone...

Dale


Lukas Renggli wrote:
> I don't see any senders in my image.
> 
> Actually #ifNotNil: is accepted by Slime, the rewrite rules we follow are these:
> 
> 	self rewriteRule
> 		replace: '``@boolean ifNotNilDo: ``@block'
> 			with: '``@boolean ifNotNil: ``@block';
> 		replace: '``@boolean ifNotNilDo: ``@block1 ifNil: ``@block2'
> 			with: '``@boolean ifNotNil: ``@block1 ifNil: ``@block2';
> 		replace: '``@boolean ifNil: ``@block1 ifNotNilDo: ``@block2'
> 			with: '``@boolean ifNil: ``@block1 ifNotNil: ``@block2';
> 		replace: '``@boolean ifNotNil: [ | `@temps | ``@.body ]'
> 			with: '``@boolean ifNotNil: [ :arg | | `@temps | ``@.body ]';
> 		replace: '``@boolean ifNotNil: [ | `@temps | ``@.body ] ifNil: ``@block '
> 			with: '``@boolean ifNotNil: [ :arg | | `@temps | ``@.body ] ifNil: ``@block';
> 		replace: '``@boolean ifNil: ``@block ifNotNil: [ | `@temps | ``@.body ]'
> 			with: '``@boolean ifNil: ``@block ifNotNil: [ :arg | | `@temps | ``@.body ]'
> 
> Personally I only use #ifNil: for lazy accessors, otherwise I don't
> like these constructs.
> 
> Lukas
> 
> On 16 June 2010 21:37, Dale Henrichs <dhenrich at vmware.com> wrote:
>> I'm porting to Pier2  to GemStone and ran into several places where
>> #ifNotNil: is being used ... what is the accepted replacement for #ifNotNil:
>> ... I can clean these up as part of my port.
>>
>> Dale
>> _______________________________________________
>> Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>
> 
> 
> 


From renggli at gmail.com  Thu Jun 17 09:17:46 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Thu, 17 Jun 2010 09:17:46 +0200
Subject: several uses of #ifNotNil: in PierSecurity (Pier2)
In-Reply-To: <4C1942C6.1070803@vmware.com>
References: <4C1927F0.8040208@vmware.com>
	<AANLkTilkZZxdK3Vxm_6k20xR7z509xJgYJwt5_wfSWNz@mail.gmail.com> 
	<4C1942C6.1070803@vmware.com>
Message-ID: <AANLkTinBcfD9uz_T8Ljd37zaAlwPwW6AKnmxb0TLXBfi@mail.gmail.com>

Ahh, we weren't aware of that. We have to check the code-base.

The rewrite was ment to make the code work in Squeak 3.9 and earlier.

Lukas

On 16 June 2010 23:31, Dale Henrichs <dhenrich at vmware.com> wrote:
> Lukas,
>
> Unless I misunderstand the rewrite rules, doesn't the following rule end up
> as a noop (ifNotNil: isn't really converted):
>
> ?replace: '``@boolean ifNotNil: [ | `@temps | ``@.body ]'
> ? ? with: '``@boolean ifNotNil: [ :arg | | `@temps | ``@.body ]';
>
> and worse yet the `ifNotNil: [:arg|]` form isn't supported by GemStone...
>
> Dale
>
>
> Lukas Renggli wrote:
>>
>> I don't see any senders in my image.
>>
>> Actually #ifNotNil: is accepted by Slime, the rewrite rules we follow are
>> these:
>>
>> ? ? ? ?self rewriteRule
>> ? ? ? ? ? ? ? ?replace: '``@boolean ifNotNilDo: ``@block'
>> ? ? ? ? ? ? ? ? ? ? ? ?with: '``@boolean ifNotNil: ``@block';
>> ? ? ? ? ? ? ? ?replace: '``@boolean ifNotNilDo: ``@block1 ifNil:
>> ``@block2'
>> ? ? ? ? ? ? ? ? ? ? ? ?with: '``@boolean ifNotNil: ``@block1 ifNil:
>> ``@block2';
>> ? ? ? ? ? ? ? ?replace: '``@boolean ifNil: ``@block1 ifNotNilDo:
>> ``@block2'
>> ? ? ? ? ? ? ? ? ? ? ? ?with: '``@boolean ifNil: ``@block1 ifNotNil:
>> ``@block2';
>> ? ? ? ? ? ? ? ?replace: '``@boolean ifNotNil: [ | `@temps | ``@.body ]'
>> ? ? ? ? ? ? ? ? ? ? ? ?with: '``@boolean ifNotNil: [ :arg | | `@temps |
>> ``@.body ]';
>> ? ? ? ? ? ? ? ?replace: '``@boolean ifNotNil: [ | `@temps | ``@.body ]
>> ifNil: ``@block '
>> ? ? ? ? ? ? ? ? ? ? ? ?with: '``@boolean ifNotNil: [ :arg | | `@temps |
>> ``@.body ] ifNil: ``@block';
>> ? ? ? ? ? ? ? ?replace: '``@boolean ifNil: ``@block ifNotNil: [ | `@temps
>> | ``@.body ]'
>> ? ? ? ? ? ? ? ? ? ? ? ?with: '``@boolean ifNil: ``@block ifNotNil: [ :arg
>> | | `@temps | ``@.body ]'
>>
>> Personally I only use #ifNil: for lazy accessors, otherwise I don't
>> like these constructs.
>>
>> Lukas
>>
>> On 16 June 2010 21:37, Dale Henrichs <dhenrich at vmware.com> wrote:
>>>
>>> I'm porting to Pier2 ?to GemStone and ran into several places where
>>> #ifNotNil: is being used ... what is the accepted replacement for
>>> #ifNotNil:
>>> ... I can clean these up as part of my port.
>>>
>>> Dale
>>> _______________________________________________
>>> 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 renggli at gmail.com  Thu Jun 17 09:25:51 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Thu, 17 Jun 2010 09:25:51 +0200
Subject: several uses of #ifNotNil: in PierSecurity (Pier2)
In-Reply-To: <4C1940C3.6080904@vmware.com>
References: <4C1927F0.8040208@vmware.com>
	<AANLkTilkZZxdK3Vxm_6k20xR7z509xJgYJwt5_wfSWNz@mail.gmail.com> 
	<4C193F6E.7010500@vmware.com> <4C1940C3.6080904@vmware.com>
Message-ID: <AANLkTimhFQZa7ZdskZqqf6ZVTcwV3BgFPOYKZC5z9Uoo@mail.gmail.com>

> I did a #senders in Pharo 1.0 with Pier installed ?and the offenders don't
> show up, but if you look at the following methods you'll see them:
>
> ?PRStructure>>group:
> ?PRStructure>>owner:
> ?PUSecurity class>>onStructureAdded:
>
> other senders (using the zero arg form) are:
>
> ?MAComponentRenderer>>hasError:
> ?MAFileUploadComponent>>remove
> ?PRCase>>document:
>
> Seems that there is a bug in senders...

I reported it here: http://code.google.com/p/pharo/issues/detail?id=2559

I want to update the rewrite rule. So GemStone only has #ifNil: with
zero arguments?

Lukas


>
> Dale
>
> Dale Henrichs wrote:
>>
>> Lukas,
>>
>> The senders (using the non-portable variant with unary block arg) are all
>> in Pier-Security-lr.165.
>>
>> Dale
>>
>> Lukas Renggli wrote:
>>>
>>> I don't see any senders in my image.
>>>
>>> Actually #ifNotNil: is accepted by Slime, the rewrite rules we follow are
>>> these:
>>>
>>> ? ? ? ?self rewriteRule
>>> ? ? ? ? ? ? ? ?replace: '``@boolean ifNotNilDo: ``@block'
>>> ? ? ? ? ? ? ? ? ? ? ? ?with: '``@boolean ifNotNil: ``@block';
>>> ? ? ? ? ? ? ? ?replace: '``@boolean ifNotNilDo: ``@block1 ifNil:
>>> ``@block2'
>>> ? ? ? ? ? ? ? ? ? ? ? ?with: '``@boolean ifNotNil: ``@block1 ifNil:
>>> ``@block2';
>>> ? ? ? ? ? ? ? ?replace: '``@boolean ifNil: ``@block1 ifNotNilDo:
>>> ``@block2'
>>> ? ? ? ? ? ? ? ? ? ? ? ?with: '``@boolean ifNil: ``@block1 ifNotNil:
>>> ``@block2';
>>> ? ? ? ? ? ? ? ?replace: '``@boolean ifNotNil: [ | `@temps | ``@.body ]'
>>> ? ? ? ? ? ? ? ? ? ? ? ?with: '``@boolean ifNotNil: [ :arg | | `@temps |
>>> ``@.body ]';
>>> ? ? ? ? ? ? ? ?replace: '``@boolean ifNotNil: [ | `@temps | ``@.body ]
>>> ifNil: ``@block '
>>> ? ? ? ? ? ? ? ? ? ? ? ?with: '``@boolean ifNotNil: [ :arg | | `@temps |
>>> ``@.body ] ifNil: ``@block';
>>> ? ? ? ? ? ? ? ?replace: '``@boolean ifNil: ``@block ifNotNil: [ | `@temps
>>> | ``@.body ]'
>>> ? ? ? ? ? ? ? ? ? ? ? ?with: '``@boolean ifNil: ``@block ifNotNil: [ :arg
>>> | | `@temps | ``@.body ]'
>>>
>>> Personally I only use #ifNil: for lazy accessors, otherwise I don't
>>> like these constructs.
>>>
>>> Lukas
>>>
>>> On 16 June 2010 21:37, Dale Henrichs <dhenrich at vmware.com> wrote:
>>>>
>>>> I'm porting to Pier2 ?to GemStone and ran into several places where
>>>> #ifNotNil: is being used ... what is the accepted replacement for
>>>> #ifNotNil:
>>>> ... I can clean these up as part of my port.
>>>>
>>>> Dale
>>>> _______________________________________________
>>>> Magritte, Pier and Related Tools ...
>>>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>>>
>>>
>>>
>>
>> _______________________________________________
>> Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>



-- 
Lukas Renggli
www.lukas-renggli.ch


From dhenrich at vmware.com  Thu Jun 17 18:34:09 2010
From: dhenrich at vmware.com (Dale Henrichs)
Date: Thu, 17 Jun 2010 09:34:09 -0700
Subject: several uses of #ifNotNil: in PierSecurity (Pier2)
In-Reply-To: <AANLkTimhFQZa7ZdskZqqf6ZVTcwV3BgFPOYKZC5z9Uoo@mail.gmail.com>
References: <4C1927F0.8040208@vmware.com>	<AANLkTilkZZxdK3Vxm_6k20xR7z509xJgYJwt5_wfSWNz@mail.gmail.com>
	<4C193F6E.7010500@vmware.com> <4C1940C3.6080904@vmware.com>
	<AANLkTimhFQZa7ZdskZqqf6ZVTcwV3BgFPOYKZC5z9Uoo@mail.gmail.com>
Message-ID: <4C1A4E81.3000707@vmware.com>

That's true right now .... I haven't made a big issue out #ifNotNil: 
because the Seaside coding convention says not to use #ifNotNil:.

#ifNotNil: isn't implemented in our base system, so I _could_ change the 
implementation to match the "standard" if there is one...

Dale

Lukas Renggli wrote:
>> I did a #senders in Pharo 1.0 with Pier installed  and the offenders don't
>> show up, but if you look at the following methods you'll see them:
>>
>>  PRStructure>>group:
>>  PRStructure>>owner:
>>  PUSecurity class>>onStructureAdded:
>>
>> other senders (using the zero arg form) are:
>>
>>  MAComponentRenderer>>hasError:
>>  MAFileUploadComponent>>remove
>>  PRCase>>document:
>>
>> Seems that there is a bug in senders...
> 
> I reported it here: http://code.google.com/p/pharo/issues/detail?id=2559
> 
> I want to update the rewrite rule. So GemStone only has #ifNil: with
> zero arguments?
> 
> Lukas

From renggli at gmail.com  Thu Jun 17 18:41:03 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Thu, 17 Jun 2010 18:41:03 +0200
Subject: several uses of #ifNotNil: in PierSecurity (Pier2)
In-Reply-To: <4C1A4E81.3000707@vmware.com>
References: <4C1927F0.8040208@vmware.com>
	<AANLkTilkZZxdK3Vxm_6k20xR7z509xJgYJwt5_wfSWNz@mail.gmail.com> 
	<4C193F6E.7010500@vmware.com> <4C1940C3.6080904@vmware.com> 
	<AANLkTimhFQZa7ZdskZqqf6ZVTcwV3BgFPOYKZC5z9Uoo@mail.gmail.com> 
	<4C1A4E81.3000707@vmware.com>
Message-ID: <AANLkTimTTZma6lUZNoKTTEkCqG95x5dBp4jIp1MFlguy@mail.gmail.com>

> That's true right now .... I haven't made a big issue out #ifNotNil: because
> the Seaside coding convention says not to use #ifNotNil:.

I've fixed all senders now. I think this is written there because
older versions of Squeak had a problem with that.

> #ifNotNil: isn't implemented in our base system, so I _could_ change the
> implementation to match the "standard" if there is one...

Yeah, I think that should be changed. Most Smalltalks accept zero or
one argument blocks in #ifNotNil:.

Lukas

>
> Dale
>
> Lukas Renggli wrote:
>>>
>>> I did a #senders in Pharo 1.0 with Pier installed ?and the offenders
>>> don't
>>> show up, but if you look at the following methods you'll see them:
>>>
>>> ?PRStructure>>group:
>>> ?PRStructure>>owner:
>>> ?PUSecurity class>>onStructureAdded:
>>>
>>> other senders (using the zero arg form) are:
>>>
>>> ?MAComponentRenderer>>hasError:
>>> ?MAFileUploadComponent>>remove
>>> ?PRCase>>document:
>>>
>>> Seems that there is a bug in senders...
>>
>> I reported it here: http://code.google.com/p/pharo/issues/detail?id=2559
>>
>> I want to update the rewrite rule. So GemStone only has #ifNil: with
>> zero arguments?
>>
>> Lukas
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>



-- 
Lukas Renggli
www.lukas-renggli.ch


From dhenrich at vmware.com  Thu Jun 17 19:11:43 2010
From: dhenrich at vmware.com (Dale Henrichs)
Date: Thu, 17 Jun 2010 10:11:43 -0700
Subject: Pier-Twitter (for Pier2) should use Grease utf8 decode: instead of
	TextConverter?
Message-ID: <4C1A574F.7020504@vmware.com>

I'm porting Pier2 and friends to GemStone and Pier-Twitter is using 
TextConverter for decoding UTF8...since Grease is a prereq anyway, 
shouldn't Pier-Twitter (for Pier2) use GRcodec?

Dale

From renggli at gmail.com  Thu Jun 17 19:52:52 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Thu, 17 Jun 2010 19:52:52 +0200
Subject: Pier-Twitter (for Pier2) should use Grease utf8 decode: instead 
	of TextConverter?
In-Reply-To: <4C1A574F.7020504@vmware.com>
References: <4C1A574F.7020504@vmware.com>
Message-ID: <AANLkTim1B5dLxfGctyqWIEjKh9iu-JILiwNrTY9OoDPr@mail.gmail.com>

Definitely, I guess this wasn't ported to Seaside 3 yet.

Lukas

On 17 June 2010 19:11, Dale Henrichs <dhenrich at vmware.com> wrote:
> I'm porting Pier2 and friends to GemStone and Pier-Twitter is using
> TextConverter for decoding UTF8...since Grease is a prereq anyway, shouldn't
> Pier-Twitter (for Pier2) use GRcodec?
>
> Dale
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>



-- 
Lukas Renggli
www.lukas-renggli.ch

From dhenrich at vmware.com  Thu Jun 17 20:40:10 2010
From: dhenrich at vmware.com (Dale Henrichs)
Date: Thu, 17 Jun 2010 11:40:10 -0700
Subject: JQFormExampleTest>>testExampleClass fails
Message-ID: <4C1A6C0A.7010600@vmware.com>

I am porting/testing the Pier-JQuery addOn (from the Pier2 addons) to 
GemStone and it requires JQueryWidgetBox, which I have also loaded into 
GemStone which is how I have discovered that the 
JQFormExampleTest>>testExampleClass test fails...

The expected javascript is:

   $(this).example("Example Text",{className:"fancy"})

but the following is being output:

   $(this).example("Example Text",{"className":"fancy"})

I'm not familiar enough with javascript to know whether the expected 
javascript is correct or whether the actual output is correct...

The test is using JQueryInstance to generate the javascript and it looks 
like the JQueryInstance is testing a similar pattern of javascript so I 
_assume_ that the expected javascript is wrong, but I wanted to double 
check before changing the test...

Dale

From nick.ager at gmail.com  Thu Jun 17 22:27:04 2010
From: nick.ager at gmail.com (Nick Ager)
Date: Thu, 17 Jun 2010 21:27:04 +0100
Subject: JQFormExampleTest>>testExampleClass fails
In-Reply-To: <4C1A6C0A.7010600@vmware.com>
References: <4C1A6C0A.7010600@vmware.com>
Message-ID: <AANLkTimEgiZ1SSOg3VilWkjy8jfrnEH0RNZYLhWl8vbD@mail.gmail.com>

Hi Dale,

I am porting/testing the Pier-JQuery addOn (from the Pier2 addons) to
> GemStone and it requires JQueryWidgetBox, which I have also loaded into
> GemStone which is how I have discovered that the
> JQFormExampleTest>>testExampleClass test fails...
>

I'm partly responsible for this, having committed PRJQuerySeachWidget into
the Pier-JQuery repository.


> The expected javascript is:
>
>  $(this).example("Example Text",{className:"fancy"})
>
> but the following is being output:
>
>  $(this).example("Example Text",{"className":"fancy"})
>

The test is failing after a fix to the way keys are encoded in Dictionaries.
I've changed the test in JQFormExampleTest.

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

From cappadonza at hotmail.com  Fri Jun 18 05:40:12 2010
From: cappadonza at hotmail.com (isaiah perumalla)
Date: Fri, 18 Jun 2010 03:40:12 +0000
Subject: Hey,
Message-ID: <SNT113-W62445DEA3CE5059CB41CE1D2C00@phx.gbl>


Hi,
How are you?
I have good news for you. Last week, I order one Lenovo Apple iPad Tablet (64GB, Wifi + 3G) from this website: www.Mrcmall.com. I've received the item today. It's amazing! The item is original, brand new and has high quality, but it's much cheaper. I'm pleased to share this good news with you! I believe you will find what you want there and have an good experience on shopping from them. 
Best regards!
 		 	   		  
_________________________________________________________________
Need a new place to live? Find it on Domain.com.au
http://clk.atdmt.com/NMN/go/157631292/direct/01/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20100618/07a37fe0/attachment-0001.html>

From luc.fabresse at gmail.com  Wed Jun 23 10:29:25 2010
From: luc.fabresse at gmail.com (Luc Fabresse)
Date: Wed, 23 Jun 2010 10:29:25 +0200
Subject: [ANN] ESUG Awards 2010
Message-ID: <AANLkTilrBeK6uF_Gi7FxofryWEm0fqXzy8iZ6mubmPOK@mail.gmail.com>

Dear Smalltalkers,

You are invited to submit your nice Smalltalk based software to the 7th ESUG
Innovation Technology Awards. The top 3 teams with the most innovative
software will receive, respectively, 500 Euros, 300 Euros and 200 Euros
during an awards ceremony at the 18th International Smalltalk Joint
Conference 2010 in Barcelona, Spain.
No constraints are put on the software except that it should be
Smalltalk-based or Smalltalk-related and all flavours of Smalltalk are
accepted.

More details on the web (submission process, ...):
http://www.esug.org/Conferences/2010/Innovation+Technology+Awards
Results of the 2009 edition:
http://www.esug.org/Conferences/2009/Innovation+Technology+Awards/Winners+and+Nominations
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20100623/f23f9bc3/attachment.html>

From dhenrich at vmware.com  Sun Jun 27 19:54:34 2010
From: dhenrich at vmware.com (Dale Henrichs)
Date: Sun, 27 Jun 2010 10:54:34 -0700
Subject: New structure for Seaside30, Magritte2,
	and Pier2 Metacello configurations
Message-ID: <4C27905A.7000509@vmware.com>

I am looking for a little feedback on the changes that I have made to 
the latest configurations of Seaside30, Magritte2, and Pier2. I have new 
versions for each of these configurations queued up for release 
(#development blessing), but before releasing them I'd like to hear if 
the changes I've made will cause trouble for folks using Magritte2 
and/or Pier2 in their applications.

In the past, when you referenced Seaside30 from a configuration, the 
entire Seaside3.0 release would be loaded, including development tools, 
examples, both adaptors (on Squeak/Pharo and GemStone)...basically the 
whole kitchen sink.

With the 3.0.0-alpha5.15 release I've defined several groups for 
Seaside3.0 (with feedback from the Seaside devs:): Base, Base Tests, 
Development and Development Tests. I will also add a One-click group to 
shdow the one-click release. Without going into too much detail, the 
Base group defines the set of packages that are needed for a production 
release, while the Development group defines the set of packages that 
are useful in development (on top of the Base).

To see how these new groups work out, I have created new versions of the 
configurations for Magritte2 and Pier2 that reference the Base group 
(plus any other packages that were needed) instead of bringing in the 
entire Seaside3.0 release...This is the big change. After loading the 
Magritte2 or Pier2 configuration you will need to load from the 
Seaside30 configuration any and all packages that you may need for your 
own application.

I haven't released the changes yet, but if you are curious or concerned 
you can try out the releases ahead of time ... depending upon feedback I 
may go with a different scheme.

In a fresh image, you can see what will be loaded for production by 
executing one or more of the following expressions (note you need to get 
the latest version of each of the configs from the SqueakSource 
MetacelloRepository...oh and for best results use Metacello 1.0-beta.27.1):

   (ConfigurationOfMagritte2 project version: '2.0.5') load.
   (ConfigurationOfPier2 project version: '2.0.6') load.
   (ConfigurationOfPierAddOns2 project version: '2.0.6') load.

Once you've loaded one of these configs, there will be no development 
tools nor any adaptors so at a minimum you'll need to load one of the 
following depending upon which adaptor you want to use:

   "All platforms"
   (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15')
     load: #('Seaside-Adaptors-Swazoo').
   "Squeak and Pharo"
   (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15')
     load: #('Seaside-Adaptors-Comanche').
   "GemStone"
   (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15')
     load: #('Seaside-Adaptors-FastCGI').

If you want to load in the Seaside development environment then you 
would evaluate the following expression:

   (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15')
     load: #('Development').

So at this point you can see the direction I'm going with this ... the 
Magritte2 and Pier2 configurations are currently aimed at loading the 
bare minimum needed for functionality from Seaside3.0 for Magritte2 and 
Pier2 with the idea that you'd load the additional functionality that 
you want by dealing directly with Seaside30 configuration (like loading 
adaptors and development)...

Pier2 already depends upon the following javascript packages:

    'Javascript-Core' 'Prototype-Core' 'Scriptaculous-Core' 'JQuery-UI'

but if you're currently using Magritte2 and javascript, then you'll need 
to explicitly load the javascript package(s) that you are using.

There are other ways that the configs could be structured. This approach 
minimizes the coupling between the Seaside3.0 and Magritte2/Pier2 
configurations, which I think is a good thing.

I've taken the bare minimum step: loading what is required... it would 
be reasonable to add 'Dev' groups to both Magritte2 and Pier2 that would 
bring in Seaside30 dev support on the other hand, I don't think it is 
reasonable to add support for loading the various Adaptors to Magritte2 
and Pier2, so if you're going to have to deal with the Seaside30 config 
directly anyway why bother with adding dev groups ...

Anyway this is what _I_ think and I am interested in what you folks think...

For GemStone folks ... the answer is yes, Magritte2 and Pier2 have been 
ported to GemStone/S 64 2.4 finally:). If you've been working with 
Seaside3.0 already, you can load the Magritte2/Pier2/PierAddOns2 configs 
into a fresh 1.0-beta.8....otherwise I'll ask you to wait until I 
announcement.

Dale

From jfitzell at gmail.com  Sun Jun 27 22:14:09 2010
From: jfitzell at gmail.com (Julian Fitzell)
Date: Sun, 27 Jun 2010 21:14:09 +0100
Subject: non-specific dependencies
Message-ID: <AANLkTikqFPolfQDXky0jQrIdAvIi1nCxRUrI0cwvVfYN@mail.gmail.com>

On Sun, Jun 27, 2010 at 6:54 PM, Dale Henrichs <dhenrich at vmware.com> wrote:
> Once you've loaded one of these configs, there will be no development tools
> nor any adaptors so at a minimum you'll need to load one of the following
> depending upon which adaptor you want to use:
>
> ?"All platforms"
> ?(ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15')
> ? ?load: #('Seaside-Adaptors-Swazoo').
> ?"Squeak and Pharo"
> ?(ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15')
> ? ?load: #('Seaside-Adaptors-Comanche').
> ?"GemStone"
> ?(ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15')
> ? ?load: #('Seaside-Adaptors-FastCGI').

This, of course, is why package management systems like RPM and Deb
end up having "provides". This would allow Seaside-Base to require
"http-adaptor" or something and each of those packages to provide
"http-adaptor". The package manager can then look for possibilities
and prompt if it finds more than one.

Not saying you need to go that route, but it's probably the
"traditional" solution.

Julian


From dhenrich at vmware.com  Sun Jun 27 23:55:53 2010
From: dhenrich at vmware.com (Dale Henrichs)
Date: Sun, 27 Jun 2010 14:55:53 -0700
Subject: [Seaside] non-specific dependencies
In-Reply-To: <AANLkTikqFPolfQDXky0jQrIdAvIi1nCxRUrI0cwvVfYN@mail.gmail.com>
References: <AANLkTikqFPolfQDXky0jQrIdAvIi1nCxRUrI0cwvVfYN@mail.gmail.com>
Message-ID: <4C27C8E9.3020208@vmware.com>

Thanks Julian ... I wasn't fishing for Metacello features, but this 
sounds like something I will certainly look into adding to Metacello in 
the future.

Dale

Julian Fitzell wrote:
> On Sun, Jun 27, 2010 at 6:54 PM, Dale Henrichs <dhenrich at vmware.com> wrote:
>> Once you've loaded one of these configs, there will be no development tools
>> nor any adaptors so at a minimum you'll need to load one of the following
>> depending upon which adaptor you want to use:
>>
>>  "All platforms"
>>  (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15')
>>    load: #('Seaside-Adaptors-Swazoo').
>>  "Squeak and Pharo"
>>  (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15')
>>    load: #('Seaside-Adaptors-Comanche').
>>  "GemStone"
>>  (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15')
>>    load: #('Seaside-Adaptors-FastCGI').
> 
> This, of course, is why package management systems like RPM and Deb
> end up having "provides". This would allow Seaside-Base to require
> "http-adaptor" or something and each of those packages to provide
> "http-adaptor". The package manager can then look for possibilities
> and prompt if it finds more than one.
> 
> Not saying you need to go that route, but it's probably the
> "traditional" solution.
> 
> Julian
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

From emaringolo at gmail.com  Tue Jun 29 19:46:16 2010
From: emaringolo at gmail.com (Esteban A. Maringolo)
Date: Tue, 29 Jun 2010 10:46:16 -0700 (PDT)
Subject: Magritte2
In-Reply-To: <1277833375602-2272515.post@n4.nabble.com>
References: <1277833375602-2272515.post@n4.nabble.com>
Message-ID: <1277833576251-2272519.post@n4.nabble.com>


I just installed Magritte2, is there any reference about the differences
between versions 1 and 2? 

I think I wanted to install Magritte 1, and by mistake installed 2 thinking
it was the last stable "mainstream" version. 

Regards!
-- 
View this message in context: http://forum.world.st/Magritte2-tp2272515p2272519.html
Sent from the Magritte, Pier and Related Tools mailing list archive at Nabble.com.

From renggli at gmail.com  Tue Jun 29 19:52:17 2010
From: renggli at gmail.com (Lukas Renggli)
Date: Tue, 29 Jun 2010 19:52:17 +0200
Subject: Magritte2
In-Reply-To: <1277833576251-2272519.post@n4.nabble.com>
References: <1277833375602-2272515.post@n4.nabble.com>
	<1277833576251-2272519.post@n4.nabble.com>
Message-ID: <AANLkTimZVhRuQmwKEJ1HVCoovzh2JhfxBUd4UHZI3VC-@mail.gmail.com>

There is no difference.

Lukas

On 29 June 2010 19:46, Esteban A. Maringolo <emaringolo at gmail.com> wrote:
>
> I just installed Magritte2, is there any reference about the differences
> between versions 1 and 2?
>
> I think I wanted to install Magritte 1, and by mistake installed 2 thinking
> it was the last stable "mainstream" version.
>
> Regards!
> --
> View this message in context: http://forum.world.st/Magritte2-tp2272515p2272519.html
> Sent from the Magritte, Pier and Related Tools mailing list archive at Nabble.com.
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>



-- 
Lukas Renggli
www.lukas-renggli.ch

From jfitzell at gmail.com  Tue Jun 29 23:10:59 2010
From: jfitzell at gmail.com (Julian Fitzell)
Date: Tue, 29 Jun 2010 22:10:59 +0100
Subject: Magritte2
In-Reply-To: <AANLkTimZVhRuQmwKEJ1HVCoovzh2JhfxBUd4UHZI3VC-@mail.gmail.com>
References: <1277833375602-2272515.post@n4.nabble.com>
	<1277833576251-2272519.post@n4.nabble.com> 
	<AANLkTimZVhRuQmwKEJ1HVCoovzh2JhfxBUd4UHZI3VC-@mail.gmail.com>
Message-ID: <AANLkTimoRuyX4-jPzvO0ao_10bbrk41BE0_f-vgsFxTg@mail.gmail.com>

More accurately, Magritte 2 runs on top of Grease and has been ported
to VA Smalltalk. Other than that there's not much difference.

Julian

On Tue, Jun 29, 2010 at 6:52 PM, Lukas Renggli <renggli at gmail.com> wrote:
> There is no difference.
>
> Lukas
>
> On 29 June 2010 19:46, Esteban A. Maringolo <emaringolo at gmail.com> wrote:
>>
>> I just installed Magritte2, is there any reference about the differences
>> between versions 1 and 2?
>>
>> I think I wanted to install Magritte 1, and by mistake installed 2 thinking
>> it was the last stable "mainstream" version.
>>
>> Regards!
>> --
>> View this message in context: http://forum.world.st/Magritte2-tp2272515p2272519.html
>> Sent from the Magritte, Pier and Related Tools mailing list archive at Nabble.com.
>> _______________________________________________
>> 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 davorin.rusevljan at gmail.com  Wed Jun 30 11:20:04 2010
From: davorin.rusevljan at gmail.com (Davorin Rusevljan)
Date: Wed, 30 Jun 2010 11:20:04 +0200
Subject: Magritte2
In-Reply-To: <AANLkTimoRuyX4-jPzvO0ao_10bbrk41BE0_f-vgsFxTg@mail.gmail.com>
References: <1277833375602-2272515.post@n4.nabble.com>
	<1277833576251-2272519.post@n4.nabble.com>
	<AANLkTimZVhRuQmwKEJ1HVCoovzh2JhfxBUd4UHZI3VC-@mail.gmail.com>
	<AANLkTimoRuyX4-jPzvO0ao_10bbrk41BE0_f-vgsFxTg@mail.gmail.com>
Message-ID: <AANLkTika8W88GO5mdH1Dv7zz64TZTkUP1JkJrS1BmRNP@mail.gmail.com>

On Tue, Jun 29, 2010 at 11:10 PM, Julian Fitzell <jfitzell at gmail.com> wrote:

> More accurately, Magritte 2 runs on top of Grease and has been ported
> to VA Smalltalk. Other than that there's not much difference.
>
>
Was there also a move to make it compatible with 3.0?

davorin rusevljan
http://www.cloud208.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20100630/6ae11156/attachment.html>

From emaringolo at gmail.com  Wed Jun 30 14:22:04 2010
From: emaringolo at gmail.com (Esteban A. Maringolo)
Date: Wed, 30 Jun 2010 09:22:04 -0300
Subject: Magritte2
In-Reply-To: <AANLkTika8W88GO5mdH1Dv7zz64TZTkUP1JkJrS1BmRNP@mail.gmail.com>
References: <1277833375602-2272515.post@n4.nabble.com>
	<1277833576251-2272519.post@n4.nabble.com> 
	<AANLkTimZVhRuQmwKEJ1HVCoovzh2JhfxBUd4UHZI3VC-@mail.gmail.com> 
	<AANLkTimoRuyX4-jPzvO0ao_10bbrk41BE0_f-vgsFxTg@mail.gmail.com> 
	<AANLkTika8W88GO5mdH1Dv7zz64TZTkUP1JkJrS1BmRNP@mail.gmail.com>
Message-ID: <AANLkTikwmiuFSv9CiDe3Qy2ferZzcgcK9RsQzxhd0-zn@mail.gmail.com>

2010/6/30 Davorin Rusevljan <davorin.rusevljan at gmail.com>:
> On Tue, Jun 29, 2010 at 11:10 PM, Julian Fitzell <jfitzell at gmail.com> wrote:
>>
>> More accurately, Magritte 2 runs on top of Grease and has been ported
>> to VA Smalltalk. Other than that there's not much difference.
>>
>
> Was there also a move to make it compatible with 3.0?

Maybe the issues I found have to do with this, how naive I am!

I'll try with Seaside 2.9

Regards!


Esteban A. Maringolo