From girba at iam.unibe.ch  Sat Dec  3 14:34:35 2005
From: girba at iam.unibe.ch (Tudor Girba)
Date: Sat, 3 Dec 2005 14:34:35 +0100
Subject: Fwd: [Fwd: SmallWiki]
References: <43919946.5070309@gmx.ch>
Message-ID: <2D132160-543A-4168-876F-D363A84A82CE@iam.unibe.ch>



Hi,

Does anyone know what is happening with the Smallwiki on kilana?

Doru

Begin forwarded message:

> From: Niklaus Haldimann <nhaldimann at gmx.ch>
> Date: December 3, 2005 2:10:30 PM GMT+01:00
> To: ESE Staff <ese-staff at iam.unibe.ch>
> Subject: [Fwd: SmallWiki]
> Reply-To: ese-staff at iam.unibe.ch
>
> SmallWiki has been down for quite some time, where should we complain?
>
> Nik
>
> -------- Original Message --------
> Subject: SmallWiki
> Date: Sat, 3 Dec 2005 13:40:38 +0100 (CET)
> From: Michael Pfeuti <m_pfeuti at yahoo.de>
> To: Nick Haldimann <nhaldimann at gmx.ch>
>
> nur zur information. das smallwiki vom ESE05
> funktioniert nicht mehr. es gibt immer einem timeout.
>
> mfg michael pfeuti
>
> *******************
> Michael Pfeuti
> Unteres Eichholz 22
> CH-3425 Koppigen
>
> +41344131860
> +41797068821
> *******************
>
>
> 	
>
> 	
> 		
> ___________________________________________________________
> Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier  
> anmelden: http://mail.yahoo.de
>
>

--
Tudor Adrian Girba                      Software Composition Group
(www.iam.unibe.ch/~girba)        University of Bern, Switzerland

"Beauty is where we see it."



From renggli at iam.unibe.ch  Sat Dec  3 17:25:42 2005
From: renggli at iam.unibe.ch (Lukas Renggli)
Date: Sat, 3 Dec 2005 17:25:42 +0100
Subject: [scg-all] Re: [Fwd: SmallWiki]
In-Reply-To: <2D132160-543A-4168-876F-D363A84A82CE@iam.unibe.ch>
References: <43919946.5070309@gmx.ch> <2D132160-543A-4168-876F-D363A84A82CE@iam.unibe.ch>
Message-ID: <222FCB39-FC5E-4C81-9B62-EEE54A1E2F43@iam.unibe.ch>



I fixed the problem.

The problem is that SmallWiki 1 doesn't properly work together with  
big resources. Data is simply kept in the image, thus the image gets  
bigger and less responsive more and more.

To solve the problem I removed some images that have been uploaded  
for the advanced design labs, they are available in source-code as  
well. Moreover I removed the permission for the anonymous-role to  
upload files, so people need to log in and only people that know the  
password will be able to upload anything (what was a security issue  
anyway).

Lukas

On 3 Dec 2005, at 14:34, Tudor Girba wrote:

> Hi,
>
> Does anyone know what is happening with the Smallwiki on kilana?
>
> Doru
>
> Begin forwarded message:
>
>> From: Niklaus Haldimann <nhaldimann at gmx.ch>
>> Date: December 3, 2005 2:10:30 PM GMT+01:00
>> To: ESE Staff <ese-staff at iam.unibe.ch>
>> Subject: [Fwd: SmallWiki]
>> Reply-To: ese-staff at iam.unibe.ch
>>
>> SmallWiki has been down for quite some time, where should we  
>> complain?
>>
>> Nik
>>
>> -------- Original Message --------
>> Subject: SmallWiki
>> Date: Sat, 3 Dec 2005 13:40:38 +0100 (CET)
>> From: Michael Pfeuti <m_pfeuti at yahoo.de>
>> To: Nick Haldimann <nhaldimann at gmx.ch>
>>
>> nur zur information. das smallwiki vom ESE05
>> funktioniert nicht mehr. es gibt immer einem timeout.
>>
>> mfg michael pfeuti
>>
>> *******************
>> Michael Pfeuti
>> Unteres Eichholz 22
>> CH-3425 Koppigen
>>
>> +41344131860
>> +41797068821
>> *******************
>>
>>
>> 	
>>
>> 	
>> 		
>> ___________________________________________________________
>> Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier  
>> anmelden: http://mail.yahoo.de
>>
>>
>
> --
> Tudor Adrian Girba                      Software Composition Group
> (www.iam.unibe.ch/~girba)        University of Bern, Switzerland
>
> "Beauty is where we see it."
>

-- 
Lukas Renggli
http://www.lukas-renggli.ch



From renggli at iam.unibe.ch  Sat Dec  3 17:25:42 2005
From: renggli at iam.unibe.ch (Lukas Renggli)
Date: Sat, 3 Dec 2005 17:25:42 +0100
Subject: [Fwd: SmallWiki]
In-Reply-To: <2D132160-543A-4168-876F-D363A84A82CE@iam.unibe.ch>
References: <43919946.5070309@gmx.ch> <2D132160-543A-4168-876F-D363A84A82CE@iam.unibe.ch>
Message-ID: <222FCB39-FC5E-4C81-9B62-EEE54A1E2F43@iam.unibe.ch>



I fixed the problem.

The problem is that SmallWiki 1 doesn't properly work together with  
big resources. Data is simply kept in the image, thus the image gets  
bigger and less responsive more and more.

To solve the problem I removed some images that have been uploaded  
for the advanced design labs, they are available in source-code as  
well. Moreover I removed the permission for the anonymous-role to  
upload files, so people need to log in and only people that know the  
password will be able to upload anything (what was a security issue  
anyway).

Lukas

On 3 Dec 2005, at 14:34, Tudor Girba wrote:

> Hi,
>
> Does anyone know what is happening with the Smallwiki on kilana?
>
> Doru
>
> Begin forwarded message:
>
>> From: Niklaus Haldimann <nhaldimann at gmx.ch>
>> Date: December 3, 2005 2:10:30 PM GMT+01:00
>> To: ESE Staff <ese-staff at iam.unibe.ch>
>> Subject: [Fwd: SmallWiki]
>> Reply-To: ese-staff at iam.unibe.ch
>>
>> SmallWiki has been down for quite some time, where should we  
>> complain?
>>
>> Nik
>>
>> -------- Original Message --------
>> Subject: SmallWiki
>> Date: Sat, 3 Dec 2005 13:40:38 +0100 (CET)
>> From: Michael Pfeuti <m_pfeuti at yahoo.de>
>> To: Nick Haldimann <nhaldimann at gmx.ch>
>>
>> nur zur information. das smallwiki vom ESE05
>> funktioniert nicht mehr. es gibt immer einem timeout.
>>
>> mfg michael pfeuti
>>
>> *******************
>> Michael Pfeuti
>> Unteres Eichholz 22
>> CH-3425 Koppigen
>>
>> +41344131860
>> +41797068821
>> *******************
>>
>>
>> 	
>>
>> 	
>> 		
>> ___________________________________________________________
>> Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier  
>> anmelden: http://mail.yahoo.de
>>
>>
>
> --
> Tudor Adrian Girba                      Software Composition Group
> (www.iam.unibe.ch/~girba)        University of Bern, Switzerland
>
> "Beauty is where we see it."
>

-- 
Lukas Renggli
http://www.lukas-renggli.ch



From jacaetevha at gmail.com  Sat Dec  3 19:21:56 2005
From: jacaetevha at gmail.com (Jason Rogers)
Date: Sat, 3 Dec 2005 13:21:56 -0500
Subject: [Webteam] Stable SW1 version on squeaksource
In-Reply-To: <87ek4vhy7c.fsf@info.unicaen.fr>
References: <87ek4vhy7c.fsf@info.unicaen.fr>
Message-ID: <72412f1f0512031021qf42723tb9346c68dae3a68e@mail.gmail.com>



Thanks a lot Samir!! This is really helpful.

On 12/2/05, Samir Saidani <saidani at squeakfr.org> wrote:
> Hi,
>
> I put a stable version of smallwiki1 on squeaksource
> (http://www.squeaksource.com/smallwiki1 , SmallWiki-Kernel-stable and
> SmallWiki-Parser-stable). This version is currently used for
> squeak.org, and www.seaside.st, and seems stable as a rock ! The
> current version, available in squeakmap, will be renamed unstable. So
> for little and/or trivial features, just put them into the stable
> version on squeaksource (read/write access for everyone), and for big
> and important features, requiring some deep modification of the
> smallwiki1 kernel, probably shoud we work with the unstable branch
> (read/write access for everyone too).
>
> Let's share our contributions !
>
> Regards,
> Samir
> _______________________________________________
> Webteam mailing list
> Webteam at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/webteam
>


--
Jason Rogers

"I am crucified with Christ: nevertheless I live; yet not I,
but Christ liveth in me: and the life which I now live in
the flesh I live by the faith of the Son of God, who loved
me, and gave himself for me."
    Galatians 2:20



From ducasse at iam.unibe.ch  Sun Dec  4 09:34:24 2005
From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=)
Date: Sun, 4 Dec 2005 09:34:24 +0100
Subject: Stable SW1 version on squeaksource
In-Reply-To: <87ek4vhy7c.fsf@info.unicaen.fr>
References: <87ek4vhy7c.fsf@info.unicaen.fr>
Message-ID: <7E17CDAD-A476-484F-8F19-A5E019396DA7@iam.unibe.ch>



Hi samir

I think that this is important that people willing to continue to  
work on SmallWiki 1 takes control of it.
So this is good that you invest and shared.

Stef

> Hi,
>
> I put a stable version of smallwiki1 on squeaksource
> (http://www.squeaksource.com/smallwiki1 , SmallWiki-Kernel-stable and
> SmallWiki-Parser-stable). This version is currently used for
> squeak.org, and www.seaside.st, and seems stable as a rock ! The
> current version, available in squeakmap, will be renamed unstable. So
> for little and/or trivial features, just put them into the stable
> version on squeaksource (read/write access for everyone), and for big
> and important features, requiring some deep modification of the
> smallwiki1 kernel, probably shoud we work with the unstable branch
> (read/write access for everyone too).
>
> Let's share our contributions !
>
> Regards,
> Samir



From rleon at insario.com  Mon Dec  5 21:14:03 2005
From: rleon at insario.com (Ramon Leon)
Date: Mon, 5 Dec 2005 13:14:03 -0700
Subject: Autofocus
References: <24C40DFA333DC44882F9FB0115F33D8F32B6A8@ARGON.insario.local> <E1CABC32-74B6-4B68-B44F-0F0C882CD0C5@iam.unibe.ch>
Message-ID: <24C40DFA333DC44882F9FB0115F33D8F1653D6@ARGON.insario.local>

Anyone know what happened to autofocus on magritte descriptions?  With this gone, how are you currently putting the cursor in the first field when an edit form appears?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 2702 bytes
Desc: not available
Url : http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20051205/1e6cac0c/attachment.bin

From renggli at iam.unibe.ch  Tue Dec  6 10:42:28 2005
From: renggli at iam.unibe.ch (Lukas Renggli)
Date: Tue, 6 Dec 2005 10:42:28 +0100
Subject: Autofocus
In-Reply-To: <24C40DFA333DC44882F9FB0115F33D8F1653D6@ARGON.insario.local>
References: <24C40DFA333DC44882F9FB0115F33D8F32B6A8@ARGON.insario.local> <E1CABC32-74B6-4B68-B44F-0F0C882CD0C5@iam.unibe.ch> <24C40DFA333DC44882F9FB0115F33D8F1653D6@ARGON.insario.local>
Message-ID: <013A7AFD-E135-4F47-B3AC-DC21D61A27F7@iam.unibe.ch>



> Anyone know what happened to autofocus on magritte descriptions?   
> With this gone, how are you currently putting the cursor in the  
> first field when an edit form appears?

I removed it.

The problem was basically because there is no good place to put this  
property and the following problems:

- you could have multiple descriptions within the same form where  
auto-focus was set to true, especially when composing descriptions at  
runtime from several different sources.

- #autofocus: did not work with some more complex form-elements like  
one-to-one, one-to-many, multiple-selection, ...

- when changing from WAHtmlRenderer to WACanvasRenderer there was no  
replacement for the method #autofocus:, however this could be easily  
added again.

- I felt that is unnecessary to have #autofocus: in the description  
itself, if you really need to automatically focus an element you  
probably do a sophisticated manual rendering anyway.

- proper separation of view and meta-model, something St?phane  
Ducasse and I just recently discussed: a problem in the current  
version of Magritte is that I mix meta-stuff and Seaside/Morphic  
configuration, such as #componentClass:, #attributes, #morphicClass,  
#autofocus: ... this should be the responsibility of a different  
object, not the description itself. It leads to some hard to tackle  
problems with extension-methods, if you want to use descriptions with/ 
without different view-implementations, however it is not easy to  
solve. Maybe something for Magritte 1.1 ;-)

Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch




From cdrick at free.fr  Tue Dec  6 11:34:13 2005
From: cdrick at free.fr (Cdrick)
Date: Tue, 06 Dec 2005 11:34:13 +0100
Subject: Layout component 
Message-ID: <43956925.1090504@free.fr>



Just an email to make some remarks... maybe useless, so if I say 
something stupid  tell it ;)

First, I found the name of Pier really good. It really reflects that it 
is more than a wiki (for me the wiki is just a component among 
others...). Pier is a framework where you can attach and organize 
seaside application (component)...

so I was wandering Lukas if you plan to make a specific component to 
organize the application Layout. It is done now in the environnement 
edit... so with a wiki syntax...  and maybe it's possible to create a 
specific component for it that could be organized dynamically with ajax 
like in the google personnalized main page 
(http://cdrick.free.fr/googlePersonalized.png   /I was moving the "RSS 
component" Musiciens.biz during the capture/)...
Do you think it is possible, interesting ? I wish I could create such a 
component but I actually have some doubt  :d

Anyway Thanks for all this great work (especially magritte for me ;) )

See you

C?drick


From damien.cassou at laposte.net  Tue Dec  6 12:02:45 2005
From: damien.cassou at laposte.net (Damien Cassou)
Date: Tue, 06 Dec 2005 12:02:45 +0100
Subject: Layout component
In-Reply-To: <43956925.1090504@free.fr>
References: <43956925.1090504@free.fr>
Message-ID: <43956FD5.1070003@laposte.net>




> First, I found the name of Pier really good. It really reflects that 
> it is more than a wiki (for me the wiki is just a component among 
> others...). 

Lukas, do you want to go furter in removing the wiki part ? Why not 
creating a package Pier-Wiki which should have all the classes related 
to wiki (PRPage for example). Then, the Pier package will be smaller. It 
is interesting because it shows that Pier is very very pluggable.

Bye


From rleon at insario.com  Tue Dec  6 17:55:28 2005
From: rleon at insario.com (Ramon Leon)
Date: Tue, 6 Dec 2005 09:55:28 -0700
Subject: Autofocus
Message-ID: <24C40DFA333DC44882F9FB0115F33D8F32B711@ARGON.insario.local>



Good enough, appreciate the explanation.  

> -----Original Message-----
> From: owner-smallwiki at iam.unibe.ch 
> [mailto:owner-smallwiki at iam.unibe.ch] On Behalf Of Lukas Renggli
> Sent: Tuesday, December 06, 2005 2:42 AM
> To: smallwiki at iam.unibe.ch
> Subject: Re: Autofocus
> 
> > Anyone know what happened to autofocus on magritte descriptions?   
> > With this gone, how are you currently putting the cursor in 
> the first 
> > field when an edit form appears?
> 
> I removed it.
> 
> The problem was basically because there is no good place to 
> put this property and the following problems:
> 
> - you could have multiple descriptions within the same form 
> where auto-focus was set to true, especially when composing 
> descriptions at runtime from several different sources.
> 
> - #autofocus: did not work with some more complex 
> form-elements like one-to-one, one-to-many, multiple-selection, ...
> 
> - when changing from WAHtmlRenderer to WACanvasRenderer there 
> was no replacement for the method #autofocus:, however this 
> could be easily added again.
> 
> - I felt that is unnecessary to have #autofocus: in the 
> description itself, if you really need to automatically focus 
> an element you probably do a sophisticated manual rendering anyway.
> 
> - proper separation of view and meta-model, something 
> St?phane Ducasse and I just recently discussed: a problem in 
> the current version of Magritte is that I mix meta-stuff and 
> Seaside/Morphic configuration, such as #componentClass:, 
> #attributes, #morphicClass,
> #autofocus: ... this should be the responsibility of a 
> different object, not the description itself. It leads to 
> some hard to tackle problems with extension-methods, if you 
> want to use descriptions with/ without different 
> view-implementations, however it is not easy to solve. Maybe 
> something for Magritte 1.1 ;-)
> 
> Lukas
> 
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
> 
> 
> 



From damien.cassou at laposte.net  Thu Dec  8 06:27:06 2005
From: damien.cassou at laposte.net (Damien Cassou)
Date: Thu, 08 Dec 2005 06:27:06 +0100
Subject: [PIER] MAOneToManyComponent>>add without duplicates
Message-ID: <4397C42A.6040703@laposte.net>



Hi all,

I modified the MAOneToManyComponent>>add method not to accept the 
duplicated :

MAOneToManyComponent>>add
    [...]
    (result notNil and: [(self value includes: result) not])
        ifTrue: [ self value: (self value copyWith: result); refresh ].

Bye


From cdrick at free.fr  Fri Dec  9 10:09:29 2005
From: cdrick at free.fr (Cdrick)
Date: Fri, 09 Dec 2005 10:09:29 +0100
Subject: questions about descriptions
Message-ID: <439949C9.4010101@free.fr>



I think I will be interested in specific descriptions and before trying 
to code them or whatever else, here are what I need... Mostly here to 
discuss on solutions to do that without "breaking" Magritte ;)

- will it be good to have something like a nested descriptions 
(MANestedContainer ??). I have to represent event and according to the 
type of event (human or natural), the option list is different. How to 
you do that ? using a nesting container (that doesn't exist yet) or 
using two descriptions with maybe a MADynamic object for the second 
description linked to the first one...

- second point, I will probably need to represent a "physical" 
measurement (with a unit or an intensity). Units or descriptions of 
intensity can be different according to what is measured. So here, what 
would you do ? using nested description ? What about creating a 
MAMeasurementDescription but if so, will it be a subclass of 
MAElementDescription and then MAMagnitudeDescription or will it be a 
subclass of MAContainer or even of MADescription ?

Thanks
C?drick


From renggli at iam.unibe.ch  Fri Dec  9 10:44:35 2005
From: renggli at iam.unibe.ch (Lukas Renggli)
Date: Fri, 9 Dec 2005 10:44:35 +0100
Subject: Layout component
In-Reply-To: <43956FD5.1070003@laposte.net>
References: <43956925.1090504@free.fr> <43956FD5.1070003@laposte.net>
Message-ID: <4DFF2499-7031-4945-9E1B-B92A3539A62C@iam.unibe.ch>



>> First, I found the name of Pier really good. It really reflects  
>> that it is more than a wiki (for me the wiki is just a component  
>> among others...).
>
> Lukas, do you want to go furter in removing the wiki part ? Why not  
> creating a package Pier-Wiki which should have all the classes  
> related to wiki (PRPage for example). Then, the Pier package will  
> be smaller. It is interesting because it shows that Pier is very  
> very pluggable.

Yeah, the wiki part (at least the parser and visitor) could be easily  
removed, but since the wiki is an integral part, e.g. to build the  
environment by providing an abstraction over xhtml, I don't see much  
sense removing it.

Moreover Pier should be something that is runnable out of the box, so  
that people can start to add content right after the installation.  
Removing the wiki part from pier would prevent this simplicity and  
give the well known Zope effect where you have to start coding weird  
xml/html/dhtml/zpt/... templates.

Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch



From renggli at iam.unibe.ch  Fri Dec  9 10:53:32 2005
From: renggli at iam.unibe.ch (Lukas Renggli)
Date: Fri, 9 Dec 2005 10:53:32 +0100
Subject: questions about descriptions
In-Reply-To: <439949C9.4010101@free.fr>
References: <439949C9.4010101@free.fr>
Message-ID: <EA8FFC47-2B4A-4928-8B02-5D8C8C968751@iam.unibe.ch>



Hi C?drick,

> - will it be good to have something like a nested descriptions  
> (MANestedContainer ??). I have to represent event and according to  
> the type of event (human or natural), the option list is different.  
> How to you do that ? using a nesting container (that doesn't exist  
> yet) or using two descriptions with maybe a MADynamic object for  
> the second description linked to the first one...

we have built a nested list at netstyle.ch using Magritte: the model  
is basically a tree where you have to select one of the leaves. The  
GUI looks like the column-view of the finder in OS X. Is that what  
you want? Else maybe the OneToOneRelationshipDescription with  
different classes could be a possibility?

> - second point, I will probably need to represent a "physical"  
> measurement (with a unit or an intensity). Units or descriptions of  
> intensity can be different according to what is measured. So here,  
> what would you do ? using nested description ? What about creating  
> a MAMeasurementDescription but if so, will it be a subclass of  
> MAElementDescription and then MAMagnitudeDescription or will it be  
> a subclass of MAContainer or even of MADescription ?

The first thing you need is probably the model, what is presumably a  
subclass of Magnitude. Then you can code (like MANumberDescription) a  
new description for your model. I once did something similar at  
netstyle.ch for currencies.

Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch




From cdrick at free.fr  Fri Dec  9 13:47:52 2005
From: cdrick at free.fr (Cdrick)
Date: Fri, 09 Dec 2005 13:47:52 +0100
Subject: questions about descriptions AND MANumberDescription
In-Reply-To: <EA8FFC47-2B4A-4928-8B02-5D8C8C968751@iam.unibe.ch>
References: <439949C9.4010101@free.fr> <EA8FFC47-2B4A-4928-8B02-5D8C8C968751@iam.unibe.ch>
Message-ID: <43997CF8.9080602@free.fr>



Hi Lukas :)

> we have built a nested list at netstyle.ch using Magritte: the model  
> is basically a tree where you have to select one of the leaves. The  
> GUI looks like the column-view of the finder in OS X. Is that what  
> you want? Else maybe the OneToOneRelationshipDescription with  
> different classes could be a possibility?
>
 I'll try to do that way... thanks ;)

>
> The first thing you need is probably the model, what is presumably a  
> subclass of Magnitude. Then you can code (like MANumberDescription) a  
> new description for your model. I once did something similar at  
> netstyle.ch for currencies.
>
Ok I see...  still the model ;)   I'll try this week-end and I'll give 
feedback when done...(or not :))


So just another question as we are talking of MANumberDescription and as 
I'm playing with it :d  
What I'm triing to do is providing instead of a text input component a 
List choice where there is a collection of number between min and max 
according to a given step...  (10 20 30 40...). What would be the better 
? creating a MANumberListComponent that display the list... or adding 
functionality in MANumberComponent...?

Also, I see that the default component for MANumberComponent are 
MAInputText and MARangeComponent but I cant really get how the 
MARangeComponent is used (called when defining the MANumberDescription).

is it:   (MANumberDescription auto: ... label: ... priority..)
                componentClass: MANumberDescription 
defaultComponentClasses second;    (is it how we acces it ??)
                yourself.

I actually don't really understand how MARangeComponent works, is it for 
a javascript check ?



From renggli at iam.unibe.ch  Fri Dec  9 14:34:29 2005
From: renggli at iam.unibe.ch (Lukas Renggli)
Date: Fri, 9 Dec 2005 14:34:29 +0100
Subject: questions about descriptions AND MANumberDescription
In-Reply-To: <43997CF8.9080602@free.fr>
References: <439949C9.4010101@free.fr> <EA8FFC47-2B4A-4928-8B02-5D8C8C968751@iam.unibe.ch> <43997CF8.9080602@free.fr>
Message-ID: <98414371-8C5B-4B3B-A015-9F20E8655C2D@iam.unibe.ch>



> So just another question as we are talking of MANumberDescription  
> and as I'm playing with it :d  What I'm triing to do is providing  
> instead of a text input component a List choice where there is a  
> collection of number between min and max according to a given  
> step...  (10 20 30 40...). What would be the better ? creating a  
> MANumberListComponent that display the list... or adding  
> functionality in MANumberComponent...?

Yeah, create a new view such as MANumberComponent/MARangeComponent.

> Also, I see that the default component for MANumberComponent are  
> MAInputText and MARangeComponent but I cant really get how the  
> MARangeComponent is used (called when defining the  
> MANumberDescription).
>
> is it:   (MANumberDescription auto: ... label: ... priority..)
>                componentClass: MANumberDescription  
> defaultComponentClasses second;    (is it how we acces it ??)
>                yourself.

I usually code directly the component class:

(MANumberDescription auto: ...)
	componentClass: MARangeComponent;
	yourself.

However, as I already mentioned in a previous mail, this imposes a  
strong coupling between the description and the view (e.g., if you  
have a model package with some descriptions and different view  
packages that all want to specify their own view-components). I don't  
know how we could solve that problem right now, so do it as you  
suggested ;-)

> I actually don't really understand how MARangeComponent works, is  
> it for a javascript check ?

Yeah, that is a control displaying a slider. It is currently only  
working in Safari and probably KHTML, because it builds on top of  
proposal to extend HTML that is not in the standard yet. It should  
however safely degenerate to a normal text-input if your browser  
doesn't support it.

Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch



From renggli at iam.unibe.ch  Fri Dec  9 14:43:37 2005
From: renggli at iam.unibe.ch (Lukas Renggli)
Date: Fri, 9 Dec 2005 14:43:37 +0100
Subject: [ANN] Central Magritte/Pier Code Repository
Message-ID: <136374CB-9E09-42DD-B659-FC9342104409@iam.unibe.ch>



Hi,

due to the increasing demand to have a central Magritte and Pier code  
repository, I migrated all my existing version to a new squeak-source  
repository at http://mc.lukas-renggli.ch. All the development will  
now go trough this interface.

URLs to load the latest version of Magritte and Pier should still be  
working, however if you had a password to commit code into those  
directories it won't work anymore. Please register an account and I  
will add you to the appropriate projects.

	http://mc.lukas-renggli.ch/magritte
	http://mc.lukas-renggli.ch/pier

I also created two projects for add-ons to Magritte and Pier, that  
are ment as places to put small-extensions you want to put into  
public, such as a new description type for Magritte or a new widget  
for Pier. Those two repositories have got public write rights.

	http://mc.lukas-renggli.ch/magritteaddons
	http://mc.lukas-renggli.ch/pieraddons

If you have your own projects that you would like to share, feel free  
to register your own project.

Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch


From philippe.marschall at gmail.com  Fri Dec  9 16:15:39 2005
From: philippe.marschall at gmail.com (Philippe Marschall)
Date: Fri, 9 Dec 2005 16:15:39 +0100
Subject: [ANN] Central Magritte/Pier Code Repository
In-Reply-To: <136374CB-9E09-42DD-B659-FC9342104409@iam.unibe.ch>
References: <136374CB-9E09-42DD-B659-FC9342104409@iam.unibe.ch>
Message-ID: <66666f210512090715v2cf132e9y@mail.gmail.com>



Yes finally a place to put all the addons and a new home for Spielverderber!
*moving my stuff*


2005/12/9, Lukas Renggli <renggli at iam.unibe.ch>:
> Hi,
>
> due to the increasing demand to have a central Magritte and Pier code
> repository, I migrated all my existing version to a new squeak-source
> repository at http://mc.lukas-renggli.ch. All the development will
> now go trough this interface.
>
> URLs to load the latest version of Magritte and Pier should still be
> working, however if you had a password to commit code into those
> directories it won't work anymore. Please register an account and I
> will add you to the appropriate projects.
>
>         http://mc.lukas-renggli.ch/magritte
>         http://mc.lukas-renggli.ch/pier
>
> I also created two projects for add-ons to Magritte and Pier, that
> are ment as places to put small-extensions you want to put into
> public, such as a new description type for Magritte or a new widget
> for Pier. Those two repositories have got public write rights.
>
>         http://mc.lukas-renggli.ch/magritteaddons
>         http://mc.lukas-renggli.ch/pieraddons
>
> If you have your own projects that you would like to share, feel free
> to register your own project.
>
> Lukas
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
>



From renggli at iam.unibe.ch  Fri Dec  9 17:06:31 2005
From: renggli at iam.unibe.ch (Lukas Renggli)
Date: Fri, 9 Dec 2005 17:06:31 +0100
Subject: [ANN] Central Magritte/Pier Code Repository
In-Reply-To: <66666f210512090715v2cf132e9y@mail.gmail.com>
References: <136374CB-9E09-42DD-B659-FC9342104409@iam.unibe.ch> <66666f210512090715v2cf132e9y@mail.gmail.com>
Message-ID: <3A3B71E4-20C2-4E9C-A596-9095F7FAD5B4@iam.unibe.ch>



And by the way, the RSS to register to for the latest news about  
Magritte/Pier related commits:

	http://mc.lukas-renggli.ch/feed.rss

-- 
Lukas Renggli
http://www.lukas-renggli.ch



From damien.cassou at laposte.net  Fri Dec  9 19:01:53 2005
From: damien.cassou at laposte.net (Damien Cassou)
Date: Fri, 09 Dec 2005 19:01:53 +0100
Subject: [ANN] Central Magritte/Pier Code Repository
In-Reply-To: <136374CB-9E09-42DD-B659-FC9342104409@iam.unibe.ch>
References: <136374CB-9E09-42DD-B659-FC9342104409@iam.unibe.ch>
Message-ID: <4399C691.9040308@laposte.net>




> due to the increasing demand to have a central Magritte and Pier code  
> repository, I migrated all my existing version to a new squeak-source  
> repository at http://mc.lukas-renggli.ch. All the development will  
> now go trough this interface.
>
> URLs to load the latest version of Magritte and Pier should still be  
> working, however if you had a password to commit code into those  
> directories it won't work anymore. Please register an account and I  
> will add you to the appropriate projects.
>
>     http://mc.lukas-renggli.ch/magritte
>     http://mc.lukas-renggli.ch/pier
>
> I also created two projects for add-ons to Magritte and Pier, that  
> are ment as places to put small-extensions you want to put into  
> public, such as a new description type for Magritte or a new widget  
> for Pier. Those two repositories have got public write rights.
>
>     http://mc.lukas-renggli.ch/magritteaddons
>     http://mc.lukas-renggli.ch/pieraddons
>
> If you have your own projects that you would like to share, feel free  
> to register your own project.

Hi,

it is a very good news. Unfortunately, I can't connect to any of this 
URLs. It seems mc.lukas-renggli.ch is down.


From renggli at iam.unibe.ch  Sat Dec 10 11:30:02 2005
From: renggli at iam.unibe.ch (Lukas Renggli)
Date: Sat, 10 Dec 2005 11:30:02 +0100
Subject: [ANN] Central Magritte/Pier Code Repository
In-Reply-To: <4399C691.9040308@laposte.net>
References: <136374CB-9E09-42DD-B659-FC9342104409@iam.unibe.ch> <4399C691.9040308@laposte.net>
Message-ID: <A42091F9-E882-4E1F-892A-28E84AD7E002@iam.unibe.ch>



> it is a very good news. Unfortunately, I can't connect to any of  
> this URLs. It seems mc.lukas-renggli.ch is down.

Strange, this is just the ready-made SqueakSource image that I ran on  
the existing repository data. The CPU was at 99% and no debugger  
showed up. I restarted it, let's see if it works better now ...

Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch



From damien.cassou at laposte.net  Tue Dec 27 16:48:51 2005
From: damien.cassou at laposte.net (Damien Cassou)
Date: Tue, 27 Dec 2005 16:48:51 +0100
Subject: [Magritte] Remove on OneToManyComponent does not remove
Message-ID: <43B16263.2060204@laposte.net>



When you click the remove link in a report for OneToManyComponent, the 
element is removed from the report but is still in the memory. Here are 
steps to reproduce :

Open : http://localhost:8080/seaside/examplebrowser
Click Edit
In 'Phone numbers' click Add
Put values inside fields and Save
Give a first name and a last name
Save the form
Remove the phone number
Click Edit
In 'Phone numbers' click Add
Put values inside fields and Save

The two phone numbers are displayed even if we removed one.


From renggli at iam.unibe.ch  Wed Dec 28 10:07:29 2005
From: renggli at iam.unibe.ch (Lukas Renggli)
Date: Wed, 28 Dec 2005 10:07:29 +0100
Subject: [Magritte] Remove on OneToManyComponent does not remove
In-Reply-To: <43B16263.2060204@laposte.net>
References: <43B16263.2060204@laposte.net>
Message-ID: <17EF451C-D087-4DAC-8DB1-28878FFDC7B0@iam.unibe.ch>



> Open : http://localhost:8080/seaside/examplebrowser
> Click Edit
> In 'Phone numbers' click Add
> Put values inside fields and Save
> Give a first name and a last name
> Save the form

This goes to a read-only view ...

> Remove the phone number

... and the remove-link should be hidden. The problem is that the  
reporting component is still very limited, but I am working on it as  
I need several of them in Pier now.

> Click Edit
> In 'Phone numbers' click Add
> Put values inside fields and Save

The remove doesn't work here, because in the read-only view the  
values are (obviously) never committed.

Thanks for reporting the problem.

Cheers,
Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch



From damien.cassou at laposte.net  Wed Dec 28 21:20:11 2005
From: damien.cassou at laposte.net (Damien Cassou)
Date: Wed, 28 Dec 2005 21:20:11 +0100
Subject: MessageNotUnderstood: WAAnchorTag>>context
Message-ID: <43B2F37B.90803@laposte.net>



Hi,

I've installed Seaside2.6a2-pmm79, Magritte-All-lr.109 and 
Pier-All-lr.31 on a fresh
Squeak3.8-6665.
The examplebrowser is not accessible anymore. It seems there is a problem
in WAAnchorTag>>url which refers to a non existant #context.

Image: Squeak3.8 [latest update: #6665]

SecurityManager state:
Restricted: false
FileAccess: true
SocketAccess: true
Working Dir /tmp/squeak
Trusted Dir /tmp/squeak/secure
Untrusted Dir /tmp/squeak/My Squeak

WAAnchorTag(Object)>>doesNotUnderstand: #context
    Receiver: a WAAnchorTag
    Arguments and temporary variables:
        aMessage:     context
    Receiver's instance variables:
        parent:     a WATableDataTag
        canvas:     a WARenderCanvas
        isClosed:     nil
        attributes:     a WAHtmlAttributes
        url:     nil
        callbackKey:     '16'
        promptString:     nil

WAAnchorTag>>url
    Receiver: a WAAnchorTag
    Arguments and temporary variables:

    Receiver's instance variables:
        parent:     a WATableDataTag
        canvas:     a WARenderCanvas
        isClosed:     nil
        attributes:     a WAHtmlAttributes
        url:     nil
        callbackKey:     '16'
        promptString:     nil

WAAnchorTag>>href
    Receiver: a WAAnchorTag
    Arguments and temporary variables:

    Receiver's instance variables:
        parent:     a WATableDataTag
        canvas:     a WARenderCanvas
        isClosed:     nil
        attributes:     a WAHtmlAttributes
        url:     nil
        callbackKey:     '16'
        promptString:     nil

[] in WAAnchorTag>>with: {[self href asString]}
    Arguments and temporary variables:
        aBlock:     [] in MADescribedColumn(MAColumn)>>renderHeadCellOn: 
{[self renderHeadC...etc...


--- The full stack ---
WAAnchorTag(Object)>>doesNotUnderstand: #context
WAAnchorTag>>url
WAAnchorTag>>href
[] in WAAnchorTag>>with: {[self href asString]}
 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[] in WAHtmlAttributes>>at:ifAbsentPut: {[self attributes add: keyString 
-> errBlock value]}
Array(Collection)>>detect:ifNone:
WAHtmlAttributes>>at:ifAbsent:
WAHtmlAttributes>>at:ifAbsentPut:
WAAnchorTag>>with:
[] in MADescribedColumn(MAColumn)>>renderHeadCellOn: {[self isSortable   
ifTrue: [html anchor     callback: [self report sort: sel...]}
BlockContext>>renderOn:
WATableDataTag(WATagBrush)>>within:
[] in WATableDataTag(WATagBrush)>>with: {[self within: aBlock]}
BlockContext>>renderOn:
WARenderCanvas(WACanvas)>>nest:
WATableDataTag(WABrush)>>with:
WATableDataTag(WATagBrush)>>with:
MADescribedColumn(MAColumn)>>renderHeadCellOn:
[] in MAReport>>renderTableHeadOn: {[:each | each renderHeadCellOn: html]}
Array(SequenceableCollection)>>do:
[] in MAReport>>renderTableHeadOn: {[self columns   do: [:each | each 
renderHeadCellOn: html]]}
BlockContext>>renderOn:
WAGenericTag(WATagBrush)>>within:
[] in WAGenericTag(WATagBrush)>>with: {[self within: aBlock]}
BlockContext>>renderOn:
WARenderCanvas(WACanvas)>>nest:
WAGenericTag(WABrush)>>with:
WAGenericTag(WATagBrush)>>with:
MAReport>>renderTableHeadOn:
[] in MAReport>>renderTableOn: {[self showHeader   ifTrue: [self 
renderTableHeadOn: html]]}
BlockContext>>renderOn:
WAGenericTag(WATagBrush)>>within:
[] in WAGenericTag(WATagBrush)>>with: {[self within: aBlock]}
BlockContext>>renderOn:
WARenderCanvas(WACanvas)>>nest:
WAGenericTag(WABrush)>>with:
WAGenericTag(WATagBrush)>>with:
MAReport>>renderTableOn:
[] in MAReport>>renderContentOn: {[self renderTableOn: html]}
BlockContext>>renderOn:
WATableTag(WATagBrush)>>within:
[] in WATableTag(WATagBrush)>>with: {[self within: aBlock]}
BlockContext>>renderOn:
WARenderCanvas(WACanvas)>>nest:
WATableTag(WABrush)>>with:
WATableTag(WATagBrush)>>with:
MAReport>>renderContentOn:
MAReport(WAPresenter)>>renderWithContext:
[] in MAReport(WAComponent)>>renderOn: {[:each | each renderWithContext: 
aRenderer context]}
MAReport(WAComponent)>>decorationChainDo:
MAReport(WAComponent)>>renderOn:
WARenderCanvas>>render:
MAOneToManyComponent>>renderViewerOn:
MAOneToManyComponent(MAElementComponent)>>renderContentOn:
MAOneToManyComponent(WAPresenter)>>renderWithContext:
[] in MAOneToManyComponent(WAComponent)>>renderOn: {[:each | each 
renderWithContext: aRenderer context]}
MAOneToManyComponent(WAComponent)>>decorationChainDo:
MAOneToManyComponent(WAComponent)>>renderOn:
WARenderCanvas>>render:
MATableRenderer(MAComponentRenderer)>>renderControl:
[] in MATableRenderer>>renderControl: {[super renderControl: aDescription]}


From matasar at gmail.com  Wed Dec 28 22:48:37 2005
From: matasar at gmail.com (Ben Matasar)
Date: Wed, 28 Dec 2005 13:48:37 -0800
Subject: [Seaside] MessageNotUnderstood: WAAnchorTag>>context
In-Reply-To: <43B2F37B.90803@laposte.net>
References: <43B2F37B.90803@laposte.net>
Message-ID: <3347ff740512281348i6ec1b28ao745a7af390badac0@mail.gmail.com>

I also have this problem, but with SUExample.

WACounter works fine, which I assume is because it doesn't use the Canvas.

Ben

On 12/28/05, Damien Cassou <damien.cassou at laposte.net> wrote:
>
> Hi,
>
> I've installed Seaside2.6a2-pmm79, Magritte-All-lr.109 and
> Pier-All-lr.31 on a fresh
> Squeak3.8-6665.
> The examplebrowser is not accessible anymore. It seems there is a problem
> in WAAnchorTag>>url which refers to a non existant #context.
>
> Image: Squeak3.8 [latest update: #6665]
>
> SecurityManager state:
> Restricted: false
> FileAccess: true
> SocketAccess: true
> Working Dir /tmp/squeak
> Trusted Dir /tmp/squeak/secure
> Untrusted Dir /tmp/squeak/My Squeak
>
> WAAnchorTag(Object)>>doesNotUnderstand: #context
>     Receiver: a WAAnchorTag
>     Arguments and temporary variables:
>         aMessage:     context
>     Receiver's instance variables:
>         parent:     a WATableDataTag
>         canvas:     a WARenderCanvas
>         isClosed:     nil
>         attributes:     a WAHtmlAttributes
>         url:     nil
>         callbackKey:     '16'
>         promptString:     nil
>
> WAAnchorTag>>url
>     Receiver: a WAAnchorTag
>     Arguments and temporary variables:
>
>     Receiver's instance variables:
>         parent:     a WATableDataTag
>         canvas:     a WARenderCanvas
>         isClosed:     nil
>         attributes:     a WAHtmlAttributes
>         url:     nil
>         callbackKey:     '16'
>         promptString:     nil
>
> WAAnchorTag>>href
>     Receiver: a WAAnchorTag
>     Arguments and temporary variables:
>
>     Receiver's instance variables:
>         parent:     a WATableDataTag
>         canvas:     a WARenderCanvas
>         isClosed:     nil
>         attributes:     a WAHtmlAttributes
>         url:     nil
>         callbackKey:     '16'
>         promptString:     nil
>
> [] in WAAnchorTag>>with: {[self href asString]}
>     Arguments and temporary variables:
>         aBlock:     [] in MADescribedColumn(MAColumn)>>renderHeadCellOn:
> {[self renderHeadC...etc...
>
>
> --- The full stack ---
> WAAnchorTag(Object)>>doesNotUnderstand: #context
> WAAnchorTag>>url
> WAAnchorTag>>href
> [] in WAAnchorTag>>with: {[self href asString]}
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> [] in WAHtmlAttributes>>at:ifAbsentPut: {[self attributes add: keyString
> -> errBlock value]}
> Array(Collection)>>detect:ifNone:
> WAHtmlAttributes>>at:ifAbsent:
> WAHtmlAttributes>>at:ifAbsentPut:
> WAAnchorTag>>with:
> [] in MADescribedColumn(MAColumn)>>renderHeadCellOn: {[self isSortable
> ifTrue: [html anchor     callback: [self report sort: sel...]}
> BlockContext>>renderOn:
> WATableDataTag(WATagBrush)>>within:
> [] in WATableDataTag(WATagBrush)>>with: {[self within: aBlock]}
> BlockContext>>renderOn:
> WARenderCanvas(WACanvas)>>nest:
> WATableDataTag(WABrush)>>with:
> WATableDataTag(WATagBrush)>>with:
> MADescribedColumn(MAColumn)>>renderHeadCellOn:
> [] in MAReport>>renderTableHeadOn: {[:each | each renderHeadCellOn: html]}
> Array(SequenceableCollection)>>do:
> [] in MAReport>>renderTableHeadOn: {[self columns   do: [:each | each
> renderHeadCellOn: html]]}
> BlockContext>>renderOn:
> WAGenericTag(WATagBrush)>>within:
> [] in WAGenericTag(WATagBrush)>>with: {[self within: aBlock]}
> BlockContext>>renderOn:
> WARenderCanvas(WACanvas)>>nest:
> WAGenericTag(WABrush)>>with:
> WAGenericTag(WATagBrush)>>with:
> MAReport>>renderTableHeadOn:
> [] in MAReport>>renderTableOn: {[self showHeader   ifTrue: [self
> renderTableHeadOn: html]]}
> BlockContext>>renderOn:
> WAGenericTag(WATagBrush)>>within:
> [] in WAGenericTag(WATagBrush)>>with: {[self within: aBlock]}
> BlockContext>>renderOn:
> WARenderCanvas(WACanvas)>>nest:
> WAGenericTag(WABrush)>>with:
> WAGenericTag(WATagBrush)>>with:
> MAReport>>renderTableOn:
> [] in MAReport>>renderContentOn: {[self renderTableOn: html]}
> BlockContext>>renderOn:
> WATableTag(WATagBrush)>>within:
> [] in WATableTag(WATagBrush)>>with: {[self within: aBlock]}
> BlockContext>>renderOn:
> WARenderCanvas(WACanvas)>>nest:
> WATableTag(WABrush)>>with:
> WATableTag(WATagBrush)>>with:
> MAReport>>renderContentOn:
> MAReport(WAPresenter)>>renderWithContext:
> [] in MAReport(WAComponent)>>renderOn: {[:each | each renderWithContext:
> aRenderer context]}
> MAReport(WAComponent)>>decorationChainDo:
> MAReport(WAComponent)>>renderOn:
> WARenderCanvas>>render:
> MAOneToManyComponent>>renderViewerOn:
> MAOneToManyComponent(MAElementComponent)>>renderContentOn:
> MAOneToManyComponent(WAPresenter)>>renderWithContext:
> [] in MAOneToManyComponent(WAComponent)>>renderOn: {[:each | each
> renderWithContext: aRenderer context]}
> MAOneToManyComponent(WAComponent)>>decorationChainDo:
> MAOneToManyComponent(WAComponent)>>renderOn:
> WARenderCanvas>>render:
> MATableRenderer(MAComponentRenderer)>>renderControl:
> [] in MATableRenderer>>renderControl: {[super renderControl:
> aDescription]}
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20051228/0913cebc/attachment.htm

From avi.bryant at gmail.com  Thu Dec 29 02:06:39 2005
From: avi.bryant at gmail.com (Avi Bryant)
Date: Wed, 28 Dec 2005 17:06:39 -0800
Subject: [Seaside] MessageNotUnderstood: WAAnchorTag>>context
In-Reply-To: <3347ff740512281348i6ec1b28ao745a7af390badac0@mail.gmail.com>
References: <43B2F37B.90803@laposte.net> <3347ff740512281348i6ec1b28ao745a7af390badac0@mail.gmail.com>
Message-ID: <ad69ab690512281706q19fea3c3j4580c661e06c4587@mail.gmail.com>



On 12/28/05, Ben Matasar <matasar at gmail.com> wrote:
> I also have this problem, but with SUExample.
>
> WACounter works fine, which I assume is because it doesn't use the Canvas.

There was some work I started to get WAAnchorTag using real WAUrl
instances instead of strings as URLs, but it never got finished (IIRC
I was waiting for Lukas to finish it off for me :).  FWIW, the version
I'm currently using (which definitely works) is Seaside2.6a2-ac.76.

Avi



From renggli at iam.unibe.ch  Thu Dec 29 09:59:38 2005
From: renggli at iam.unibe.ch (Lukas Renggli)
Date: Thu, 29 Dec 2005 09:59:38 +0100
Subject: [Seaside] MessageNotUnderstood: WAAnchorTag>>context
In-Reply-To: <ad69ab690512281706q19fea3c3j4580c661e06c4587@mail.gmail.com>
References: <43B2F37B.90803@laposte.net> <3347ff740512281348i6ec1b28ao745a7af390badac0@mail.gmail.com> <ad69ab690512281706q19fea3c3j4580c661e06c4587@mail.gmail.com>
Message-ID: <457A8D71-FB33-45BB-8F99-C10A17323A95@iam.unibe.ch>



>> I also have this problem, but with SUExample.
>>
>> WACounter works fine, which I assume is because it doesn't use the  
>> Canvas.
>
> There was some work I started to get WAAnchorTag using real WAUrl
> instances instead of strings as URLs, but it never got finished (IIRC
> I was waiting for Lukas to finish it off for me :).  FWIW, the version
> I'm currently using (which definitely works) is Seaside2.6a2-ac.76.

I tried to finish (Seaside2.6a2-lr.74), however supporting string  
URLs (String) and object URLs (WAUrl) is not that easy because it  
requires some conversion between the two. Especially parsing a string  
is difficult and requires a lot of ugly logic, as you can see in  
WAUrl>>fromString: in Seaside2.6a2-lr.74. I vote to only support URLs  
as objects, but that would break existing code and probably would be  
less efficient.

Another thing that stopped me from finishing, was that the default  
URL returned by WAAnchor wasn't the base-path of the application but  
the current URL, that led to problems when I wanted to link to a  
parent (within the directory tree of Pier). So there is even more  
logic required: most applications that do not modify the URL probably  
want to keep the current URL, but those that modify it want to start  
from the base-path.

I guess there is some abstraction missing here, however I wasn't able  
to fix that in a straight forward way, so I stopped for now. If  
nobody else is proposing a solution I will certainly work on it again  
as soon as it becomes inevitable for Pier.

Cheers,
Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch


From damien.cassou at laposte.net  Thu Dec 29 12:31:41 2005
From: damien.cassou at laposte.net (Damien Cassou)
Date: Thu, 29 Dec 2005 12:31:41 +0100
Subject: [GestionImmo]
Message-ID: <43B3C91D.8000201@laposte.net>

Hi,

Mathieu Hopmann and me developed an application based on
magritte, pier and mysql. This application stores data in a mysql
database.

It allows the user to manage lease in flats with owners, town,
building...

You can just read the source code or configure everything to run it.

If you just want to read the code, load 'Mysql Driver' from SqueakMap
and GestionImmo from SqueakSource
(http://www.squeaksource.com/GestionImmo).

To make this application run, configure those things :

1) Install 'Mysql Driver' from SqueakMap
2) Install GestionImmo from SqueakSource
   http://www.squeaksource.com/GestionImmo
3) Create a new mysql database and load the two attached files
4) Because of a problem with Mysql Driver, if your mysql server
    is greater or equal to 4.1you should read
    http://dev.mysql.com/doc/refman/5.0/en/old-client.html
5) Define this new globals with your information :
    GIUser := 'username'.
    GIPasswd := 'password'.
    GIHost := 'localhost'.
    GIDataBase := 'databaseName'.
    GIPort := 3306.
6) Execute this : GISeasideInit initializePages.
7) Open your browser on :
    http://localhost:8080/seaside/pier/GestionImmo

If you have any problem send me as many mails as you feel necessary.


-- 
Damien
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: creation.sql
Url: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20051229/a349730d/creation.bat
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: insertion.sql
Url: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20051229/a349730d/insertion.bat

From stephane.ducasse at free.fr  Thu Dec 29 21:32:30 2005
From: stephane.ducasse at free.fr (stephane ducasse)
Date: Thu, 29 Dec 2005 21:32:30 +0100
Subject: MessageNotUnderstood: WAAnchorTag>>context
In-Reply-To: <43B2F37B.90803@laposte.net>
References: <43B2F37B.90803@laposte.net>
Message-ID: <C87D5E71-DA0E-4685-9A71-5281F76D2BC2@free.fr>



By the way, I'm showing seaside to all the students of my new  
Smalltalk lectures and I can tell you that:
	- David tutorial is cool and it is really important to have such a  
kind of tutorial.
	- the tests and allTests and exampleBrowser are really important to  
get some examples of seaside
	usage.
	
Stef