Error: "/seaside/mmiki/seaside/files/WAStandardFiles/externalAnchors.js" not found.

<45F70AD0.10904@sonaural.com> <72174665-0BA4-4976-BC74-3E216E9B4D5D@iam.unibe.ch> <45F71F90.9020005@sonaural.com> Message-ID: >>> Ideas where to look? >> >> FireBug is the only answer I know to any problem related to >> JavaScript: >> >> http://www.getfirebug.com/ > > Man, that's handy! In the Script tab it says: > >

Error: > "/seaside/mmiki/seaside/files/WAStandardFiles/externalAnchors.js" not > found.

> > I don't quite know what this means. Why would it be looking in this > path? (mmiki is the name of the pier kernel) That's odd. Are you using Apache? Rewrite rules? Proxies? Obviously it cannot find the JavaScript files. Locally they should be reachable at http://localhost:8080/seaside/files/WAStandardFiles/ externalAnchors.js. Does that work? Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From brad at sonaural.com Tue Mar 13 23:29:16 2007 From: brad at sonaural.com (Brad Fuller) Date: Tue, 13 Mar 2007 15:29:16 -0700 Subject: Javascript in pier page In-Reply-To: References: <45F7035D.6010206@sonaural.com> <45F70AD0.10904@sonaural.com> <72174665-0BA4-4976-BC74-3E216E9B4D5D@iam.unibe.ch> <45F71F90.9020005@sonaural.com> Message-ID: <45F725BC.1070304@sonaural.com> Lukas Renggli wrote: >>>> Ideas where to look? >>> FireBug is the only answer I know to any problem related to >>> JavaScript: >>> >>> http://www.getfirebug.com/ >> Man, that's handy! In the Script tab it says: >> >>

Error: >> "/seaside/mmiki/seaside/files/WAStandardFiles/externalAnchors.js" not >> found.

>> >> I don't quite know what this means. Why would it be looking in this >> path? (mmiki is the name of the pier kernel) > > That's odd. Are you using Apache? Rewrite rules? Proxies? > > Obviously it cannot find the JavaScript files. Locally they should be > reachable at http://localhost:8080/seaside/files/WAStandardFiles/ > externalAnchors.js. Does that work? Yep, it works locally - well not locally but direct and not thru apache (I had to clear '/' in Server Path in config to be able to navigate locally. Also, if I bypass apache and have '/' in the Server Path, icons don't show up.). I don't think my rewrite rules are anything special. This is my test setup but I just checked on the other site and it operates the same with the exact same error. Here are my rewrite rules: ProxyPreserveHost On RewriteEngine ON RewriteCond /home/web/mmiki/%{REQUEST_FILENAME} !-f RewriteRule ^/(.*)$ http://localhost:9999/seaside/mmiki/$1 [proxy,last] I think this is the same problem that I have when seaside times out. I the path duplicated like: /seaside/miki/seaside/mmiki Obviously, I've done something wrong with the image (unless you see something wrong in the rewrite rules) From koubo2006 at yengawa.jpn.org Wed Mar 14 02:20:48 2007 From: koubo2006 at yengawa.jpn.org (Koji Yokokawa) Date: Wed, 14 Mar 2007 10:20:48 +0900 Subject: Breadcrumbs List Message-ID: <20070314100702.FDD5.KOUBO2006@yengawa.jpn.org> Hi all, I made a breadcrumbs list for Pier. It displays the trail of the user in the Pier site. Detailes: http://yengawa-wiki.webhop.org/YengawaWiki/55 Demo site: http://yengawapier.webhop.org/ Have fun! -- ! Koji Yokokawa http://www.yengawa.com/ ^self new! From brad at sonaural.com Wed Mar 14 03:58:05 2007 From: brad at sonaural.com (Brad Fuller) Date: Tue, 13 Mar 2007 19:58:05 -0700 Subject: Javascript in pier page In-Reply-To: <45F725BC.1070304@sonaural.com> References: <45F7035D.6010206@sonaural.com> <45F70AD0.10904@sonaural.com> <72174665-0BA4-4976-BC74-3E216E9B4D5D@iam.unibe.ch> <45F71F90.9020005@sonaural.com> <45F725BC.1070304@sonaural.com> Message-ID: <45F764BD.3090100@sonaural.com> Brad Fuller wrote: > Lukas Renggli wrote: >>>>> Ideas where to look? >>>> FireBug is the only answer I know to any problem related to >>>> JavaScript: >>>> >>>> http://www.getfirebug.com/ >>> Man, that's handy! In the Script tab it says: >>> >>>

Error: >>> "/seaside/mmiki/seaside/files/WAStandardFiles/externalAnchors.js" not >>> found.

>>> >>> I don't quite know what this means. Why would it be looking in this >>> path? (mmiki is the name of the pier kernel) >> That's odd. Are you using Apache? Rewrite rules? Proxies? >> >> Obviously it cannot find the JavaScript files. Locally they should be >> reachable at http://localhost:8080/seaside/files/WAStandardFiles/ >> externalAnchors.js. Does that work? > > Yep, it works locally - well not locally but direct and not thru apache > (I had to clear '/' in Server Path in config to be able to navigate > locally. Also, if I bypass apache and have '/' in the Server Path, icons > don't show up.). > > I don't think my rewrite rules are anything special. This is my test > setup but I just checked on the other site and it operates the same with > the exact same error. > > Here are my rewrite rules: > > ProxyPreserveHost On > RewriteEngine ON > RewriteCond /home/web/mmiki/%{REQUEST_FILENAME} !-f > RewriteRule ^/(.*)$ http://localhost:9999/seaside/mmiki/$1 [proxy,last] > > I think this is the same problem that I have when seaside times out. I > the path duplicated like: /seaside/miki/seaside/mmiki > > Obviously, I've done something wrong with the image (unless you see > something wrong in the rewrite rules) I think the rewrite rules are ok. I'm seeing this in the apache access log: "GET /seaside/files/SULibrary/prototype.js HTTP/1.1" 404 82 I don't know why SULibrary is looking externally for the files. I didn't tell it to do so. Is this the default? From brad at sonaural.com Wed Mar 14 04:13:39 2007 From: brad at sonaural.com (Brad Fuller) Date: Tue, 13 Mar 2007 20:13:39 -0700 Subject: Javascript in pier page In-Reply-To: <66666f210703131323j3d3e4b3ai1c382d6588b8d04b@mail.gmail.com> References: <45F7035D.6010206@sonaural.com> <66666f210703131323j3d3e4b3ai1c382d6588b8d04b@mail.gmail.com> Message-ID: <45F76863.4080609@sonaural.com> Philippe Marschall wrote: > Have a look at: > http://spielverderber.seasidehosting.st/spielwiese > that embeds several JavaScripts components into a page simply cool... I gotta figure out how to create javascript modules! From ducasse at iam.unibe.ch Wed Mar 14 18:44:42 2007 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Wed, 14 Mar 2007 18:44:42 +0100 Subject: Problem with Pier Blog In-Reply-To: <52CCC8B9-4A98-4D70-8165-81433B1B8EA6@iam.unibe.ch> References: <45F6D535.6080604@zyoconsulting.com> <52CCC8B9-4A98-4D70-8165-81433B1B8EA6@iam.unibe.ch> Message-ID: so maybe you should have an installer. I have the impression that as soon as a package get a public usage it should have an installer. or we will be killed by dependencies. Stef On 13 mars 07, at 17:51, Lukas Renggli wrote: >> I get the next error: >> >> >> MessageNotUnderstood: WARenderedHtmlRoot>>rss > > The Pier blog requires the package RSRSS from http:// > www.squeaksource.com/rsrss as a prerequisite. > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From brad at sonaural.com Thu Mar 15 04:13:27 2007 From: brad at sonaural.com (Brad Fuller) Date: Wed, 14 Mar 2007 20:13:27 -0700 Subject: Javascript in pier page In-Reply-To: <45F764BD.3090100@sonaural.com> References: <45F7035D.6010206@sonaural.com> <45F70AD0.10904@sonaural.com> <72174665-0BA4-4976-BC74-3E216E9B4D5D@iam.unibe.ch> <45F71F90.9020005@sonaural.com> <45F725BC.1070304@sonaural.com> <45F764BD.3090100@sonaural.com> Message-ID: <45F8B9D7.50106@sonaural.com> Brad Fuller wrote: > Brad Fuller wrote: >> Lukas Renggli wrote: >>>>>> Ideas where to look? >>>>> FireBug is the only answer I know to any problem related to >>>>> JavaScript: >>>>> >>>>> http://www.getfirebug.com/ >>>> Man, that's handy! In the Script tab it says: >>>> >>>>

Error: >>>> "/seaside/mmiki/seaside/files/WAStandardFiles/externalAnchors.js" not >>>> found.

>>>> >>>> I don't quite know what this means. Why would it be looking in this >>>> path? (mmiki is the name of the pier kernel) >>> That's odd. Are you using Apache? Rewrite rules? Proxies? >>> >>> Obviously it cannot find the JavaScript files. Locally they should be >>> reachable at http://localhost:8080/seaside/files/WAStandardFiles/ >>> externalAnchors.js. Does that work? >> Yep, it works locally - well not locally but direct and not thru apache >> (I had to clear '/' in Server Path in config to be able to navigate >> locally. Also, if I bypass apache and have '/' in the Server Path, icons >> don't show up.). >> >> I don't think my rewrite rules are anything special. This is my test >> setup but I just checked on the other site and it operates the same with >> the exact same error. >> >> Here are my rewrite rules: >> >> ProxyPreserveHost On >> RewriteEngine ON >> RewriteCond /home/web/mmiki/%{REQUEST_FILENAME} !-f >> RewriteRule ^/(.*)$ http://localhost:9999/seaside/mmiki/$1 [proxy,last] >> >> I think this is the same problem that I have when seaside times out. I >> the path duplicated like: /seaside/miki/seaside/mmiki >> >> Obviously, I've done something wrong with the image (unless you see >> something wrong in the rewrite rules) > > I think the rewrite rules are ok. I'm seeing this in the apache access log: > "GET /seaside/files/SULibrary/prototype.js HTTP/1.1" 404 82 > > I don't know why SULibrary is looking externally for the files. I didn't > tell it to do so. Is this the default? Ok, so I don't get it. Why would apache look for these files? These javascripts are in the image. In fact, all I have is css in my own library. Is this something about the back and forth of rewrite rules that I don't understand? Someone know? -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From renggli at iam.unibe.ch Thu Mar 15 08:03:29 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Thu, 15 Mar 2007 08:03:29 +0100 Subject: Javascript in pier page In-Reply-To: <45F8B9D7.50106@sonaural.com> References: <45F7035D.6010206@sonaural.com> <45F70AD0.10904@sonaural.com> <72174665-0BA4-4976-BC74-3E216E9B4D5D@iam.unibe.ch> <45F71F90.9020005@sonaural.com> <45F725BC.1070304@sonaural.com> <45F764BD.3090100@sonaural.com> <45F8B9D7.50106@sonaural.com> Message-ID: >>> >>> Here are my rewrite rules: >>> >>> ProxyPreserveHost On >>> RewriteEngine ON >>> RewriteCond /home/web/mmiki/%{REQUEST_FILENAME} !-f >>> RewriteRule ^/(.*)$ http://localhost:9999/seaside/mmiki/$1 >>> [proxy,last] >>> >>> I think this is the same problem that I have when seaside times >>> out. I >>> the path duplicated like: /seaside/miki/seaside/mmiki >>> >>> Obviously, I've done something wrong with the image (unless you see >>> something wrong in the rewrite rules) >> >> I think the rewrite rules are ok. I'm seeing this in the apache >> access log: >> "GET /seaside/files/SULibrary/prototype.js HTTP/1.1" 404 82 >> >> I don't know why SULibrary is looking externally for the files. I >> didn't >> tell it to do so. Is this the default? > > Ok, so I don't get it. Why would apache look for these files? These > javascripts are in the image. In fact, all I have is css in my own > library. Is this something about the back and forth of rewrite rules > that I don't understand? > > Someone know? Yes it looks to me as if the files do not get rewritten correctly. Try adding the following line to your rewrite rules: RewriteRule ^/seaside/files/(.*)$ http://localhost:9999/seaside/ files/$1 [proxy,last] Make sure it is the first rule to be applied, so that it looks somehow like: ProxyPreserveHost On RewriteEngine On RewriteRule ^/seaside/files/(.*)$ http://localhost:9999/seaside/ files/$1 [proxy,last] RewriteCond /home/web/mmiki/%{REQUEST_FILENAME} !-f RewriteRule ^/(.*)$ http://localhost:9999/seaside/mmiki/$1 [proxy,last] Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Thu Mar 15 08:07:53 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Thu, 15 Mar 2007 08:07:53 +0100 Subject: Problem with Pier Blog In-Reply-To: References: <45F6D535.6080604@zyoconsulting.com> <52CCC8B9-4A98-4D70-8165-81433B1B8EA6@iam.unibe.ch> Message-ID: > so maybe you should have an installer. > I have the impression that as soon as a package get a public usage it > should have an installer. > or we will be killed by dependencies. It starts to be complicated. I already have sort of a simple installer framework. Magritte -> loads seaside, kom, magritte Pier -> loads magritte, pier Pier Unix Security -> loads pier, unix security But then Pier Blog -> loads pier, rsrss, pier blog What about the package 'Pier Unix Security'? Should that be loaded as well? No, because there are other security frameworks around that might be used instead. The dependenceis of 'Pier Unix Security' and 'Pier Blog' could depend on different versions of Pier. What a mess. Lukas > > Stef > > On 13 mars 07, at 17:51, Lukas Renggli wrote: > >>> I get the next error: >>> >>> >>> MessageNotUnderstood: WARenderedHtmlRoot>>rss >> >> The Pier blog requires the package RSRSS from http:// >> www.squeaksource.com/rsrss as a prerequisite. >> >> Cheers, >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> >> >> _______________________________________________ >> SmallWiki, Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- Lukas Renggli http://www.lukas-renggli.ch From azreal1977 at hotmail.com Thu Mar 15 13:32:33 2007 From: azreal1977 at hotmail.com (J J) Date: Thu, 15 Mar 2007 12:32:33 +0000 Subject: Problem with Pier Blog In-Reply-To: Message-ID: Better (imo) would be some kind of package (e.g. universe). I don't think installer scripts in squeak map are a good long term solution. >From: st�phane ducasse >Reply-To: "Magritte, Pier and Related Tools ..." >To: "Magritte, Pier and Related Tools ..." >Subject: Re: Problem with Pier Blog >Date: Wed, 14 Mar 2007 18:44:42 +0100 > >so maybe you should have an installer. >I have the impression that as soon as a package get a public usage it >should have an installer. >or we will be killed by dependencies. > >Stef > >On 13 mars 07, at 17:51, Lukas Renggli wrote: > > >> I get the next error: > >> > >> > >> MessageNotUnderstood: WARenderedHtmlRoot>>rss > > > > The Pier blog requires the package RSRSS from http:// > > www.squeaksource.com/rsrss as a prerequisite. > > > > Cheers, > > Lukas > > > > -- > > Lukas Renggli > > http://www.lukas-renggli.ch > > > > > > > > _______________________________________________ > > SmallWiki, Magritte, Pier and Related Tools ... > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > >_______________________________________________ >SmallWiki, Magritte, Pier and Related Tools ... >https://www.iam.unibe.ch/mailman/listinfo/smallwiki _________________________________________________________________ With tax season right around the corner, make sure to follow these few simple tips. http://articles.moneycentral.msn.com/Taxes/PreparationTips/PreparationTips.aspx?icid=HMFebtagline From diegof79 at gmail.com Thu Mar 15 16:11:45 2007 From: diegof79 at gmail.com (Diego Fernandez) Date: Thu, 15 Mar 2007 12:11:45 -0300 Subject: Newbie question about Pier Message-ID: <8328b1510703150811l4bfded47t71ec74c883e79fd3@mail.gmail.com> Hi! I want to use Pier as a wiki at work, so I'm evaluating if it meets my needs. (side note: It's very complicated to get information about Pier from the main Squeak site, the Pier wiki or the Seaside site. I don't known how the Ruby guys get the resources to make their web sites... but we -I mean the squeak community- need to learn a lot from them in this area) After running the image provided by Keith, I've tried to use Magma and I got the same error about "objects" file mentioned early in the list :(. So before digging more into the problem, I have a couple of questions: - What is the recommended mechanism for persistence: plain files, Magma, image? - If I want to change the persistence method, how hard is to do the migration? (I think that I should execute a script that loads all the wiki in the image using the source persistence method, then write all those objects using the target persistence method... there is an easy way to do that?) - How can I make Pier components? (I'm new to Seaside too) - It's possible to use LDAP for Pier authentication? If not, how hard is to use another authentication method? (I have experience developing LDAP authentication libraries for gemstone... so I can help in this area) - I want to change the stylesheet how I can do that? - I want to change the view component, so certain options like editing or configuring the environment are invisible if the user is not logged in... any clue on how to start? - It's possible so show or hide a component according to the user role? I want to show the tree component only if the user is the administrator of the wiki That are a lot of questions for a single mail! So many thanks in advance! Diego.- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20070315/cec09033/attachment.html From ducasse at iam.unibe.ch Thu Mar 15 16:38:40 2007 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Thu, 15 Mar 2007 16:38:40 +0100 Subject: Problem with Pier Blog In-Reply-To: References: <45F6D535.6080604@zyoconsulting.com> <52CCC8B9-4A98-4D70-8165-81433B1B8EA6@iam.unibe.ch>

Message-ID: True This is an excellent example that could be used to propose a good solution to deal with dependencies. On 15 mars 07, at 08:07, Lukas Renggli wrote: >> so maybe you should have an installer. >> I have the impression that as soon as a package get a public usage it >> should have an installer. >> or we will be killed by dependencies. > > It starts to be complicated. I already have sort of a simple > installer framework. > > Magritte -> loads seaside, kom, magritte > Pier -> loads magritte, pier > Pier Unix Security -> loads pier, unix security > > But then > > Pier Blog -> loads pier, rsrss, pier blog > > What about the package 'Pier Unix Security'? Should that be loaded as > well? No, because there are other security frameworks around that > might be used instead. The dependenceis of 'Pier Unix Security' and > 'Pier Blog' could depend on different versions of Pier. What a mess. > > Lukas > > > > > >> >> Stef >> >> On 13 mars 07, at 17:51, Lukas Renggli wrote: >> >>>> I get the next error: >>>> >>>> >>>> MessageNotUnderstood: WARenderedHtmlRoot>>rss >>> >>> The Pier blog requires the package RSRSS from http:// >>> www.squeaksource.com/rsrss as a prerequisite. >>> >>> Cheers, >>> Lukas >>> >>> -- >>> Lukas Renggli >>> http://www.lukas-renggli.ch >>> >>> >>> >>> _______________________________________________ >>> SmallWiki, Magritte, Pier and Related Tools ... >>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> >> >> _______________________________________________ >> SmallWiki, Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From brad at sonaural.com Thu Mar 15 16:52:56 2007 From: brad at sonaural.com (Brad Fuller) Date: Thu, 15 Mar 2007 08:52:56 -0700 Subject: Javascript in pier page In-Reply-To: References: <45F7035D.6010206@sonaural.com> <45F70AD0.10904@sonaural.com> <72174665-0BA4-4976-BC74-3E216E9B4D5D@iam.unibe.ch> <45F71F90.9020005@sonaural.com> <45F725BC.1070304@sonaural.com> <45F764BD.3090100@sonaural.com> <45F8B9D7.50106@sonaural.com> Message-ID: <45F96BD8.5040002@sonaural.com> Lukas Renggli wrote: >>>> Here are my rewrite rules: >>>> >>>> ProxyPreserveHost On >>>> RewriteEngine ON >>>> RewriteCond /home/web/mmiki/%{REQUEST_FILENAME} !-f >>>> RewriteRule ^/(.*)$ http://localhost:9999/seaside/mmiki/$1 >>>> [proxy,last] >>>> >>>> I think this is the same problem that I have when seaside times >>>> out. I >>>> the path duplicated like: /seaside/miki/seaside/mmiki >>>> >>>> Obviously, I've done something wrong with the image (unless you see >>>> something wrong in the rewrite rules) >>> I think the rewrite rules are ok. I'm seeing this in the apache >>> access log: >>> "GET /seaside/files/SULibrary/prototype.js HTTP/1.1" 404 82 >>> >>> I don't know why SULibrary is looking externally for the files. I >>> didn't >>> tell it to do so. Is this the default? >> Ok, so I don't get it. Why would apache look for these files? These >> javascripts are in the image. In fact, all I have is css in my own >> library. Is this something about the back and forth of rewrite rules >> that I don't understand? >> >> Someone know? > > Yes it looks to me as if the files do not get rewritten correctly. > Try adding the following line to your rewrite rules: > > RewriteRule ^/seaside/files/(.*)$ http://localhost:9999/seaside/ > files/$1 [proxy,last] > > Make sure it is the first rule to be applied, so that it looks > somehow like: > > ProxyPreserveHost On > RewriteEngine On > RewriteRule ^/seaside/files/(.*)$ http://localhost:9999/seaside/ > files/$1 [proxy,last] > RewriteCond /home/web/mmiki/%{REQUEST_FILENAME} !-f > RewriteRule ^/(.*)$ http://localhost:9999/seaside/mmiki/$1 > [proxy,last] Thanks Lukas. I'm learning more about rewrite rules than I ever wanted to! That almost works. It now doesn't accommodate css files served from apache. Why it worked before, I don't know, but I'll find out. I'm investigating it now and I'll post my results. Hopefully, others might find it useful. -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From philippe.marschall at gmail.com Thu Mar 15 18:24:16 2007 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Thu, 15 Mar 2007 18:24:16 +0100 Subject: Newbie question about Pier In-Reply-To: <8328b1510703150811l4bfded47t71ec74c883e79fd3@mail.gmail.com> References: <8328b1510703150811l4bfded47t71ec74c883e79fd3@mail.gmail.com> Message-ID: <66666f210703151024s337b0539lcd51df0177491a50@mail.gmail.com> 2007/3/15, Diego Fernandez : > Hi! > I want to use Pier as a wiki at work, so I'm evaluating if it meets my > needs. > > (side note: It's very complicated to get information about Pier from the > main Squeak site, the Pier wiki or the Seaside site. I don't known how the > Ruby guys get the resources to make their web sites... but we -I mean the > squeak community- need to learn a lot from them in this area) > > After running the image provided by Keith, I've tried to use Magma and I got > the same error about "objects" file mentioned early in the list :(. So > before digging more into the problem, I have a couple of questions: > - What is the recommended mechanism for persistence: plain files, Magma, > image? I would say this depends on your requirements. > - If I want to change the persistence method, how hard is to do the > migration? (I think that I should execute a script that loads all the wiki > in the image using the source persistence method, then write all those > objects using the target persistence method... there is an easy way to do > that?) > - How can I make Pier components? (I'm new to Seaside too) There are two options: - any kind of Seaside component (subclass of WAComponent or WATask) will do - make subclasses of PRStructure that are described with Margitte and implement the related commands have a look at: http://mc.lukas-renggli.ch/pieraddons.html or the blog plugin to get some ideas > - It's possible to use LDAP for Pier authentication? It's not implemented. > If not, how hard is to > use another authentication method? (I have experience developing LDAP > authentication libraries for gemstone... so I can help in this area) Once you have a Squeak LDAP client running, it should be fairly easy. > - I want to change the stylesheet how I can do that? remove PRPierLibrary from the pier application (via the Seaside config application) and add your own > - I want to change the view component, so certain options like editing or > configuring the environment are invisible if the user is not logged in... > any clue on how to start? To always display the environment remove the PRHider decoration (the simplest way is with the object explorer). Then you can set the view permission on the environment. > - It's possible so show or hide a component according to the user role? I > want to show the tree component only if the user is the administrator of the > wiki Change the view permission of the component. Cheers Philippe > That are a lot of questions for a single mail! > So many thanks in advance! > Diego.- > > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > From renggli at iam.unibe.ch Thu Mar 15 21:42:31 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Thu, 15 Mar 2007 21:42:31 +0100 Subject: Newbie question about Pier In-Reply-To: <66666f210703151024s337b0539lcd51df0177491a50@mail.gmail.com> References: <8328b1510703150811l4bfded47t71ec74c883e79fd3@mail.gmail.com> <66666f210703151024s337b0539lcd51df0177491a50@mail.gmail.com> Message-ID: Hi Diego, nice to hear from you. >> (side note: It's very complicated to get information about Pier >> from the >> main Squeak site, the Pier wiki or the Seaside site. I don't known >> how the >> Ruby guys get the resources to make their web sites... but we -I >> mean the >> squeak community- need to learn a lot from them in this area) The source where all the documentation is linked from here: http://www.lukas-renggli.ch/smalltalk/pier >> After running the image provided by Keith, I've tried to use Magma >> and I got >> the same error about "objects" file mentioned early in the list : >> (. So >> before digging more into the problem, I have a couple of questions: >> - What is the recommended mechanism for persistence: plain files, >> Magma, >> image? > > I would say this depends on your requirements. I just save the image. Works fine for me. Image segments created in a forked copy of the image would be a nice and quick solution as well, I just didn't had the time to implement that yet. >> - If I want to change the persistence method, how hard is to do the >> migration? (I think that I should execute a script that loads all >> the wiki >> in the image using the source persistence method, then write all >> those >> objects using the target persistence method... there is an easy >> way to do >> that?) I just heard from a guy that never really touched Squeak before (he is an experiences Smalltalker though) that he easily migrated the whole object graph of a Pier Site from one image to another one using SIXX. >> - How can I make Pier components? (I'm new to Seaside too) > > There are two options: > - any kind of Seaside component (subclass of WAComponent or WATask) > will do Yes. Any component that could be its own application (e.g. #canBeRoot returns true) can be added and used within Pier. If you want to have a bit more of convenience have a look at PRWidget and subclasses. These are basically all the components used to get the default look and feel. > - make subclasses of PRStructure that are described with Margitte and > implement the related commands That's something else. PRStructure and its subclasses form the pages of the Pier CMS. It can declare though what view to use (yet another Seaside component, a subclass of PRView in fact). >> - It's possible to use LDAP for Pier authentication? > > It's not implemented. > >> If not, how hard is to >> use another authentication method? (I have experience developing LDAP >> authentication libraries for gemstone... so I can help in this area) > > Once you have a Squeak LDAP client running, it should be fairly easy. Should be easy to do though. You could take one of the existing security frameworks and create the users/groups dynamically from an LDAP query. >> - I want to change the view component, so certain options like >> editing or >> configuring the environment are invisible if the user is not >> logged in... >> any clue on how to start? You need to load a security plugin. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From brad at sonaural.com Fri Mar 16 04:42:24 2007 From: brad at sonaural.com (Brad Fuller) Date: Thu, 15 Mar 2007 20:42:24 -0700 Subject: Javascript in pier page In-Reply-To: <45F96BD8.5040002@sonaural.com> References: <45F7035D.6010206@sonaural.com> <45F70AD0.10904@sonaural.com> <72174665-0BA4-4976-BC74-3E216E9B4D5D@iam.unibe.ch> <45F71F90.9020005@sonaural.com> <45F725BC.1070304@sonaural.com> <45F764BD.3090100@sonaural.com> <45F8B9D7.50106@sonaural.com> <45F96BD8.5040002@sonaural.com> Message-ID: <45FA1220.3040905@sonaural.com> Brad Fuller wrote: >> Yes it looks to me as if the files do not get rewritten correctly. >> Try adding the following line to your rewrite rules: >> >> RewriteRule ^/seaside/files/(.*)$ http://localhost:9999/seaside/ >> files/$1 [proxy,last] >> >> Make sure it is the first rule to be applied, so that it looks >> somehow like: >> >> ProxyPreserveHost On >> RewriteEngine On >> RewriteRule ^/seaside/files/(.*)$ http://localhost:9999/seaside/ >> files/$1 [proxy,last] >> RewriteCond /home/web/mmiki/%{REQUEST_FILENAME} !-f >> RewriteRule ^/(.*)$ http://localhost:9999/seaside/mmiki/$1 >> [proxy,last] > > Thanks Lukas. I'm learning more about rewrite rules than I ever wanted > to! That almost works. It now doesn't accommodate css files served from > apache. Why it worked before, I don't know, but I'll find out. I'm > investigating it now and I'll post my results. Hopefully, others might > find it useful. Believe it or not, I worked on this all day. The rewrite rules you have are correct and work for me... at the end of the day. I do not know why they didn't work right off the bat. When I tried them and they didn't work, I tried various other tricks and studied the rewrite rules and conditions on the apache page and elsewhere. Nothing really worked well. Then, the seaside image started hanging by the end of the day (don't know why, I didn't touch it much) and I finally had to just kill it. At that point I was actually back to where I started but I didn't know I had re-written the rules back to Lukas's original suggestion! After I restarted seaside, it just worked. Go figur.... What a day. (hey, I know more about rewrite rules...) Now... my next problem is the timeout problem. When the page time's out, I get an error. At least I think that's the reason. I'll create another thread for that discussion. Everyone, thanks for your help! brad From brad at sonaural.com Fri Mar 16 04:43:49 2007 From: brad at sonaural.com (Brad Fuller) Date: Thu, 15 Mar 2007 20:43:49 -0700 Subject: path error on link-click after a while in Pier Message-ID: <45FA1275.2000603@sonaural.com> I get error's like this sometimes when I click a link in pier: Error: "/seaside/mmiki/seaside/mmiki/A-Page" not found. Notice the path is duplicated. I figure that this is an error that occurs after the page time's out. yes? How can I fix this? Why does this happen? Lukas mentioned a thread to search for but I can't find that message (sorry!) and I haven't found a good explanation. Can anyone point me in the right direction? thanks, brad -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From renggli at iam.unibe.ch Fri Mar 16 07:52:25 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 16 Mar 2007 07:52:25 +0100 Subject: path error on link-click after a while in Pier In-Reply-To: <45FA1275.2000603@sonaural.com> References: <45FA1275.2000603@sonaural.com> Message-ID: <35FDB0D8-E7F0-43FC-9997-C0928F25C105@iam.unibe.ch> > I get error's like this sometimes when I click a link in pier: > > Error: "/seaside/mmiki/seaside/mmiki/A-Page" not found. > > Notice the path is duplicated. I figure that this is an error that > occurs after the page time's out. yes? > > How can I fix this? Why does this happen? Lukas mentioned a thread to > search for but I can't find that message (sorry!) and I haven't > found a > good explanation. > > Can anyone point me in the right direction? Again this can be solved with a RewrtieRule that you put before RewriteCond in your Apache config: RewriteRule $/seaside/mmiki/(.*)^ http://localhost:9999/$1 [proxy,last] The reason you need this is a problem of Seaside redirecting to the wrong URL when a session has a timeout. Unfortunately this is not that easy to fix. I did several attempts during the development of 2.7, but could not figure out a way that did not break a lot of other applications altogether. Anyway, for now the above RewriteRule does the trick. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From brad at sonaural.com Fri Mar 16 15:35:25 2007 From: brad at sonaural.com (Brad Fuller) Date: Fri, 16 Mar 2007 07:35:25 -0700 Subject: path error on link-click after a while in Pier In-Reply-To: <35FDB0D8-E7F0-43FC-9997-C0928F25C105@iam.unibe.ch> References: <45FA1275.2000603@sonaural.com> <35FDB0D8-E7F0-43FC-9997-C0928F25C105@iam.unibe.ch> Message-ID: <45FAAB2D.5090507@sonaural.com> Lukas Renggli wrote: >> I get error's like this sometimes when I click a link in pier: >> >> Error: "/seaside/mmiki/seaside/mmiki/A-Page" not found. >> >> Notice the path is duplicated. I figure that this is an error that >> occurs after the page time's out. yes? >> >> How can I fix this? Why does this happen? Lukas mentioned a thread to >> search for but I can't find that message (sorry!) and I haven't >> found a >> good explanation. >> >> Can anyone point me in the right direction? > > Again this can be solved with a RewrtieRule that you put before > RewriteCond in your Apache config: > > RewriteRule $/seaside/mmiki/(.*)^ http://localhost:9999/$1 > [proxy,last] > > The reason you need this is a problem of Seaside redirecting to the > wrong URL when a session has a timeout. Unfortunately this is not > that easy to fix. I did several attempts during the development of > 2.7, but could not figure out a way that did not break a lot of other > applications altogether. Anyway, for now the above RewriteRule does > the trick. Bummer... I thought that there was something in the image so I wouldn't have to write another rule, but now I remember you saying you investigated this. BTW: just to be clear the rule above has the "^" and "$" flipped around. Shouldn't it be: RewriteRule ^/seaside/mmiki/(.*)$ http://localhost:9999/$1 [proxy,last] -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From renggli at iam.unibe.ch Fri Mar 16 15:41:35 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 16 Mar 2007 15:41:35 +0100 Subject: path error on link-click after a while in Pier In-Reply-To: <45FAAB2D.5090507@sonaural.com> References: <45FA1275.2000603@sonaural.com> <35FDB0D8-E7F0-43FC-9997-C0928F25C105@iam.unibe.ch> <45FAAB2D.5090507@sonaural.com> Message-ID: <02CF7CEE-AA1C-4837-A780-2BC367525FF9@iam.unibe.ch> > BTW: just to be clear the rule above has the "^" and "$" flipped > around. > Shouldn't it be: > > RewriteRule ^/seaside/mmiki/(.*)$ http://localhost:9999/$1 > [proxy,last] Yes, exactly. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From diegof79 at gmail.com Sat Mar 17 19:33:51 2007 From: diegof79 at gmail.com (Diego Fernandez) Date: Sat, 17 Mar 2007 15:33:51 -0300 Subject: Newbie question about Pier In-Reply-To: References: <8328b1510703150811l4bfded47t71ec74c883e79fd3@mail.gmail.com> <66666f210703151024s337b0539lcd51df0177491a50@mail.gmail.com> Message-ID: <8328b1510703171133p6423ae8fo4878a977defbe55d@mail.gmail.com> Many thanks to everyone for the answers :) I need to setup a wiki fast.. so I'm going to start with the old ComSwiki until I learn more about Seaside and Pier... so you will hear more questions from me about Pier :) (BTW Lukas your work on Pier is amassing, thanks!) On 3/15/07, Lukas Renggli wrote: > > Hi Diego, > > nice to hear from you. > > >> (side note: It's very complicated to get information about Pier > >> from the > >> main Squeak site, the Pier wiki or the Seaside site. I don't known > >> how the > >> Ruby guys get the resources to make their web sites... but we -I > >> mean the > >> squeak community- need to learn a lot from them in this area) > > The source where all the documentation is linked from here: > > http://www.lukas-renggli.ch/smalltalk/pier > > >> After running the image provided by Keith, I've tried to use Magma > >> and I got > >> the same error about "objects" file mentioned early in the list : > >> (. So > >> before digging more into the problem, I have a couple of questions: > >> - What is the recommended mechanism for persistence: plain files, > >> Magma, > >> image? > > > > I would say this depends on your requirements. > > I just save the image. Works fine for me. Image segments created in a > forked copy of the image would be a nice and quick solution as well, > I just didn't had the time to implement that yet. > > >> - If I want to change the persistence method, how hard is to do the > >> migration? (I think that I should execute a script that loads all > >> the wiki > >> in the image using the source persistence method, then write all > >> those > >> objects using the target persistence method... there is an easy > >> way to do > >> that?) > > I just heard from a guy that never really touched Squeak before (he > is an experiences Smalltalker though) that he easily migrated the > whole object graph of a Pier Site from one image to another one using > SIXX. > > >> - How can I make Pier components? (I'm new to Seaside too) > > > > There are two options: > > - any kind of Seaside component (subclass of WAComponent or WATask) > > will do > > Yes. Any component that could be its own application (e.g. #canBeRoot > returns true) can be added and used within Pier. If you want to have > a bit more of convenience have a look at PRWidget and subclasses. > These are basically all the components used to get the default look > and feel. > > > - make subclasses of PRStructure that are described with Margitte and > > implement the related commands > > That's something else. PRStructure and its subclasses form the pages > of the Pier CMS. It can declare though what view to use (yet another > Seaside component, a subclass of PRView in fact). > > >> - It's possible to use LDAP for Pier authentication? > > > > It's not implemented. > > > >> If not, how hard is to > >> use another authentication method? (I have experience developing LDAP > >> authentication libraries for gemstone... so I can help in this area) > > > > Once you have a Squeak LDAP client running, it should be fairly easy. > > Should be easy to do though. You could take one of the existing > security frameworks and create the users/groups dynamically from an > LDAP query. > > >> - I want to change the view component, so certain options like > >> editing or > >> configuring the environment are invisible if the user is not > >> logged in... > >> any clue on how to start? > > You need to load a security plugin. > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > > _______________________________________________ > SmallWiki, 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/20070317/23c70901/attachment.html From ssastre at seaswork.com Mon Mar 19 15:16:49 2007 From: ssastre at seaswork.com (Sebastian Sastre) Date: Mon, 19 Mar 2007 11:16:49 -0300 Subject: User's role based observation of the model Message-ID: Hi there, I was reading the Lukas thesis about Magritte. By the way... congratulations for that nice document Lukas. I have questions about Magritte beign useful for generating views of the model. Note I said views and not view of the model because I think is interesting to generate more than one unique view for it. I have several examples in wich this feature is desirable. Most are user based. With user based I mean the user's role should determinate the observation. An organization's anOperator should see something of aDocumentModel but aManager should see diferent and probably more details of the same aDocumentModel and aDirector should see just metrics about that (aDocumentModel). I see that one could manipulate the design to "force" aDocumentModel to be of different species for each observer but the cost is undesirable complication, reality-virtuality mismatch and identity mess (made worst with and RDBMS mapping in the middle). I don't like the dark side. I think is possible a better approach but until now I was unable to see a clear way on how Magritte could help with multiple description request. The descriptions for the objects are deducted from class side #descriptionXX of the objects wich collaborates with MADescriptionBuilder but it's cache seems to be designed to store only one description per object. Do you think that to extend Magritte to support several descriptions per object should be the best approach to this problem? thanks, Sebastian Sastre -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20070319/6043210c/attachment.html From renggli at iam.unibe.ch Mon Mar 19 15:32:23 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 19 Mar 2007 15:32:23 +0100 Subject: User's role based observation of the model In-Reply-To: References: Message-ID: <0D07232D-3A33-4B2D-ACF3-AF178C245AF1@iam.unibe.ch> > I think is possible a better approach but until now I was > unable to see a clear way on how Magritte could help with multiple > description request. The descriptions for the objects are deducted > from class side #descriptionXX of the objects wich collaborates > with MADescriptionBuilder but it's cache seems to be designed to > store only one description per object. That's the default and what is required most of the time. However there is nothing that prevents you from having multiple descriptions for a single object (or class). Descriptions are just objects that can be composed and stored in instance-variables like anything else. I know of quite a lot of projects that have been doing exactly that. > Do you think that to extend Magritte to support several > descriptions per object should be the best approach to this problem? For example you could dispatch the request for a description trough your user model: SomeModel>>descriptionFor: aUser ^ aUser descriptionOf: self UserModel>>descriptionOf: anObject ^ MACachedBuilderWithUser for: anObject class user: self Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From ssastre at seaswork.com Mon Mar 19 17:31:32 2007 From: ssastre at seaswork.com (Sebastian Sastre) Date: Mon, 19 Mar 2007 13:31:32 -0300 Subject: User's role based observation of the model In-Reply-To: <0D07232D-3A33-4B2D-ACF3-AF178C245AF1@iam.unibe.ch> Message-ID: Very good! I think Magritte won a new friend ;) cheers, Sebastian Sastre > -----Mensaje original----- > De: smallwiki-bounces at iam.unibe.ch > [mailto:smallwiki-bounces at iam.unibe.ch] En nombre de Lukas Renggli > Enviado el: Lunes, 19 de Marzo de 2007 11:32 > Para: Magritte, Pier and Related Tools ... > Asunto: Re: User's role based observation of the model > > > I think is possible a better approach but until now I > was unable > > to see a clear way on how Magritte could help with multiple > > description request. The descriptions for the objects are deducted > > from class side #descriptionXX of the objects wich > collaborates with > > MADescriptionBuilder but it's cache seems to be designed to > store only > > one description per object. > > That's the default and what is required most of the time. > However there is nothing that prevents you from having > multiple descriptions for a single object (or class). > Descriptions are just objects that can be composed and stored > in instance-variables like anything else. > I know of quite a lot of projects that have been doing exactly that. > > > Do you think that to extend Magritte to support several > > descriptions per object should be the best approach to this problem? > > For example you could dispatch the request for a description > trough your user model: > > SomeModel>>descriptionFor: aUser > ^ aUser descriptionOf: self > > UserModel>>descriptionOf: anObject > ^ MACachedBuilderWithUser for: anObject class user: self > > > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From sebjulliand at gmail.com Mon Mar 19 19:21:51 2007 From: sebjulliand at gmail.com (=?ISO-8859-1?Q?S=E9bastien_Julliand?=) Date: Mon, 19 Mar 2007 19:21:51 +0100 Subject: Commands on multiple structures / Timestamps Message-ID: <4f6c865a0703191121k3b63323eyad91fe9dab74f6da@mail.gmail.com> According to how commands work in Pier, is it possible to apply a command on more than a single structure? Another question: is there something in Pier to retrieve the date and time of creation/modification of each page (or do I need to add some descriptions to PRStructure?) Cheers, -- S?bastien JULLIAND -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20070319/eea97029/attachment-0001.html From renggli at iam.unibe.ch Mon Mar 19 21:02:21 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 19 Mar 2007 21:02:21 +0100 Subject: Commands on multiple structures / Timestamps In-Reply-To: <4f6c865a0703191121k3b63323eyad91fe9dab74f6da@mail.gmail.com> References: <4f6c865a0703191121k3b63323eyad91fe9dab74f6da@mail.gmail.com> Message-ID: > According to how commands work in Pier, is it possible to apply a > command on more than a single structure? Yes, however this is not the way they have been designed to be used. It is better to create a copy for every execution. To make a command to a different structure you need a new context anyway as contexts are immutable. > Another question: is there something in Pier to retrieve the date > and time of creation/modification of each page (or do I need to add > some descriptions to PRStructure?) Retrieving creating/modification time only works with a persistency scheme attached logs all the command executions. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From ducasse at iam.unibe.ch Mon Mar 19 21:15:02 2007 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Mon, 19 Mar 2007 21:15:02 +0100 Subject: Commands on multiple structures / Timestamps In-Reply-To: <4f6c865a0703191121k3b63323eyad91fe9dab74f6da@mail.gmail.com> References: <4f6c865a0703191121k3b63323eyad91fe9dab74f6da@mail.gmail.com> Message-ID: On 19 mars 07, at 19:21, S?bastien Julliand wrote: > According to how commands work in Pier, is it possible to apply a > command on more than a single structure? seb and me want to know whether we could apply a command to all the elements of a list of page for example. > Another question: is there something in Pier to retrieve the date > and time of creation/modification of each page (or do I need to add > some descriptions to PRStructure?) > > Cheers, > -- > S?bastien JULLIAND > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From renggli at iam.unibe.ch Mon Mar 19 21:21:30 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 19 Mar 2007 21:21:30 +0100 Subject: Commands on multiple structures / Timestamps In-Reply-To: References: <4f6c865a0703191121k3b63323eyad91fe9dab74f6da@mail.gmail.com> Message-ID: <86572145-D1CB-495A-A957-ED7E28989A41@iam.unibe.ch> >> According to how commands work in Pier, is it possible to apply a >> command on more than a single structure? > > seb and me want to know whether we could apply a command to all the > elements of a list of page for example. Sure that's possible. Something like that should work: self root enumerator with all hidden do: [ :structure | (self context structure: each command: aCommand copy) command execute ] Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From brad at sonaural.com Mon Mar 19 21:47:40 2007 From: brad at sonaural.com (Brad Fuller) Date: Mon, 19 Mar 2007 13:47:40 -0700 Subject: path error on link-click after a while in Pier In-Reply-To: <35FDB0D8-E7F0-43FC-9997-C0928F25C105@iam.unibe.ch> References: <45FA1275.2000603@sonaural.com> <35FDB0D8-E7F0-43FC-9997-C0928F25C105@iam.unibe.ch> Message-ID: <45FEF6EC.4020500@sonaural.com> Lukas Renggli wrote: >> I get error's like this sometimes when I click a link in pier: >> >> Error: "/seaside/mmiki/seaside/mmiki/A-Page" not found. >> >> Notice the path is duplicated. I figure that this is an error that >> occurs after the page time's out. yes? >> >> How can I fix this? Why does this happen? Lukas mentioned a thread to >> search for but I can't find that message (sorry!) and I haven't >> found a >> good explanation. >> >> Can anyone point me in the right direction? >> > > Again this can be solved with a RewrtieRule that you put before > RewriteCond in your Apache config: > > RewriteRule $/seaside/mmiki/(.*)^ http://localhost:9999/$1 > [proxy,last] > > The reason you need this is a problem of Seaside redirecting to the > wrong URL when a session has a timeout. Unfortunately this is not > that easy to fix. I did several attempts during the development of > 2.7, but could not figure out a way that did not break a lot of other > applications altogether. Anyway, for now the above RewriteRule does > the trick. > OK, I admit this is a bit OT, but it does have something to do with getting Seaside and Apache working together. Others might benefit too... and I'm surprised that others don't see this problem. Actually, one would think that the solution above would work, but in my case it does not. In fact, sometimes I get the path repeated 3 times! What I did was bypass apache, set the Pier app default timeout low and go at it to see if I could find something useful. In every case of a timeout, Pier worked fine when bypassing apache. After timeouts, seaside went to the next page just fine. So, I think my issue is something to do with apache. I thought maybe there is a cache problem on the server side, so I made sure that no cache module is loaded. Why would the path get duplicated so many times and KOM/Seaside work just fine? brad From renggli at iam.unibe.ch Mon Mar 19 22:00:13 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 19 Mar 2007 22:00:13 +0100 Subject: path error on link-click after a while in Pier In-Reply-To: <45FEF6EC.4020500@sonaural.com> References: <45FA1275.2000603@sonaural.com> <35FDB0D8-E7F0-43FC-9997-C0928F25C105@iam.unibe.ch> <45FEF6EC.4020500@sonaural.com> Message-ID: <5E3278E9-AAC3-4C01-9100-3D699D074962@iam.unibe.ch> > Actually, one would think that the solution above would work, but > in my > case it does not. In fact, sometimes I get the path repeated 3 times! That's strange this never occurred to me. Did you check the Apache logs (access.log, error.log, rewrite.log)? > What I did was bypass apache, set the Pier app default timeout low and > go at it to see if I could find something useful. You could also evaluate WARegistry clearAllHandlers to expire all existing session at once ;) Lukas -- Lukas Renggli http://www.lukas-renggli.ch From brad at sonaural.com Mon Mar 19 22:11:12 2007 From: brad at sonaural.com (Brad Fuller) Date: Mon, 19 Mar 2007 14:11:12 -0700 Subject: path error on link-click after a while in Pier In-Reply-To: <5E3278E9-AAC3-4C01-9100-3D699D074962@iam.unibe.ch> References: <45FA1275.2000603@sonaural.com> <35FDB0D8-E7F0-43FC-9997-C0928F25C105@iam.unibe.ch> <45FEF6EC.4020500@sonaural.com> <5E3278E9-AAC3-4C01-9100-3D699D074962@iam.unibe.ch> Message-ID: <45FEFC70.7060208@sonaural.com> Lukas Renggli wrote: >> Actually, one would think that the solution above would work, but >> in my >> case it does not. In fact, sometimes I get the path repeated 3 times! >> > > That's strange this never occurred to me. Did you check the Apache > logs (access.log, error.log, rewrite.log)? > Absolutely, that's what I've been looking at so long... ;-( > >> What I did was bypass apache, set the Pier app default timeout low and >> go at it to see if I could find something useful. >> > > You could also evaluate > > WARegistry clearAllHandlers > Yeah, I'll add that to my ritual. Thanks! > to expire all existing session at once ;) > > Lukas > > -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From renggli at iam.unibe.ch Mon Mar 19 23:30:38 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 19 Mar 2007 23:30:38 +0100 Subject: No free space in set In-Reply-To: <44F04FDD.10003@laposte.net> References: <448ECA08.9090307@yahoo.co.uk> <44F04F16.7050502@laposte.net> <44F04FDD.10003@laposte.net> Message-ID: <7C1E980B-B9B9-449E-8EEF-ACA6C24F0A79@iam.unibe.ch> It took at lot of time, but I just fixed the reported problem. It was a long standing Seaside bug related to the backtracking of Set's and all its subclasses. This problem should be fixed in my latest commit: Name: Seaside2.8a1-lr.219 Author: lr Time: 19 March 2007, 11:19:55 pm UUID: 20950b51-ebc2-464c-943c-d8feaf856e37 Ancestors: Seaside2.8a1-lr.218 - fixed a bug that caused sets and dictionaries to get corrupted when being backtracked (a long standing bug) - minor performance improvement when restoring backtracked state by using the squeak primitive Cheers, Lukas On 26 Aug 2006, at 15:42, Damien Cassou wrote: > VM: unix - a SmalltalkImage > Image: Squeak3.9gamma [latest update: #7051] > > SecurityManager state: > Restricted: false > FileAccess: true > SocketAccess: true > Working Dir /home/cassou/Documents/squeak/image/victaid > Trusted Dir /home/cassou/Documents/squeak/image/victaid/secure > Untrusted Dir /home/cassou/Documents/squeak/image/victaid/My Squeak > > Set(Object)>>error: > Receiver: a Set(a PRPage name: 'syntax' a PRPage name: 'pier') > Arguments and temporary variables: > aString: 'There is no free space in this set!' > Receiver's instance variables: > tally: 2 > array: an Array(a PRPage name: 'syntax' a PRPage name: 'pier') > > Set>>findElementOrNil: > Receiver: a Set(a PRPage name: 'syntax' a PRPage name: 'pier') > Arguments and temporary variables: > anObject: a PRPage name: 'information' > index: 0 > Receiver's instance variables: > tally: 2 > array: an Array(a PRPage name: 'syntax' a PRPage name: 'pier') > > Set>>noCheckAdd: > Receiver: a Set(a PRPage name: 'syntax' a PRPage name: 'pier') > Arguments and temporary variables: > anObject: a PRPage name: 'information' > Receiver's instance variables: > tally: 2 > array: an Array(a PRPage name: 'syntax' a PRPage name: 'pier') > > [] in Set>>rehash {[:each | newSelf noCheckAdd: each]} > Arguments and temporary variables: > newSelf: a Set(a PRPage name: 'syntax' a PRPage name: 'pier') > each: a PRPage name: 'information' > > > --- The full stack --- > Set(Object)>>error: > Set>>findElementOrNil: > Set>>noCheckAdd: > [] in Set>>rehash {[:each | newSelf noCheckAdd: each]} > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > Set>>do: > Set>>rehash > Set(Object)>>veryDeepCopyWith: > WeakKeyAssociation(Object)>>veryDeepCopyWith: > Array(Object)>>veryDeepCopyWith: > WeakIdentityKeyDictionary(Object)>>veryDeepCopyWith: > ValueHolder(Object)>>veryDeepCopyWith: > Array(Object)>>veryDeepCopyWith: > ResponseContinuation(Object)>>veryDeepCopyWith: > Association(Object)>>veryDeepCopyWith: > Array(Object)>>veryDeepCopyWith: > Dictionary(Object)>>veryDeepCopyWith: > WALRUCache(Object)>>veryDeepCopyWith: > WASession(Object)>>veryDeepCopyWith: > Association(Object)>>veryDeepCopyWith: > Array(Object)>>veryDeepCopyWith: > Dictionary(Object)>>veryDeepCopyWith: > WAApplication(Object)>>veryDeepCopyWith: > Association(Object)>>veryDeepCopyWith: > Array(Object)>>veryDeepCopyWith: > Dictionary(Object)>>veryDeepCopyWith: > WADispatcher(Object)>>veryDeepCopyWith: > WAKom(Object)>>veryDeepCopyWith: > MethodContext(Object)>>veryDeepCopyWith: > MethodContext(Object)>>veryDeepCopyWith: > MethodContext(Object)>>veryDeepCopyWith: > MethodContext(Object)>>veryDeepCopyWith: > MethodContext(Object)>>veryDeepCopyWith: > MethodContext(Object)>>veryDeepCopyWith: > BlockContext(Object)>>veryDeepCopyWith: > MethodContext(Object)>>veryDeepCopyWith: > BlockContext(Object)>>veryDeepCopyWith: > Process(Object)>>veryDeepCopyWith: > Semaphore(Object)>>veryDeepCopyWith: > WAProcessMonitor(Object)>>veryDeepCopyWith: > MethodContext(Object)>>veryDeepCopyWith: > BlockContext(Object)>>veryDeepCopyWith: > MethodContext(Object)>>veryDeepCopyWith: > BlockContext(Object)>>veryDeepCopyWith: > MethodContext(Object)>>veryDeepCopyWith: > BlockContext(Object)>>veryDeepCopyWith: > MethodContext(Object)>>veryDeepCopyWith: > BlockContext(Object)>>veryDeepCopyWith: > MethodContext(Object)>>veryDeepCopyWith: > MessageNotUnderstood(Object)>>veryDeepCopyWith: > WAWalkback(Object)>>veryDeepCopyWith: > BlockContext(Object)>>veryDeepCopyWith: > WAAnswerHandler(Object)>>veryDeepCopyWith: > WAStateHolder(Object)>>veryDeepCopyWith: > WeakKeyAssociation(Object)>>veryDeepCopyWith: > Array(Object)>>veryDeepCopyWith: > WeakIdentityKeyDictionary(Object)>>veryDeepCopyWith: > WAStateRegistry(Object)>>veryDeepCopyWith: > WASession(Object)>>veryDeepCopyWith: > Association(Object)>>veryDeepCopyWith: > Array(Object)>>veryDeepCopyWith: > Dictionary(Object)>>veryDeepCopyWith: > -- and more not shown -- > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- Lukas Renggli http://www.lukas-renggli.ch From brad at sonaural.com Tue Mar 20 00:57:08 2007 From: brad at sonaural.com (Brad Fuller) Date: Mon, 19 Mar 2007 16:57:08 -0700 Subject: path error on link-click after a while in Pier In-Reply-To: <5E3278E9-AAC3-4C01-9100-3D699D074962@iam.unibe.ch> References: <45FA1275.2000603@sonaural.com> <35FDB0D8-E7F0-43FC-9997-C0928F25C105@iam.unibe.ch> <45FEF6EC.4020500@sonaural.com> <5E3278E9-AAC3-4C01-9100-3D699D074962@iam.unibe.ch> Message-ID: <45FF2354.6010007@sonaural.com> Lukas Renggli wrote: >> Actually, one would think that the solution above would work, but >> in my >> case it does not. In fact, sometimes I get the path repeated 3 times! >> > > That's strange this never occurred to me. It would help to find this problem if I understood more of what Seaside is suppose to do when there is a page time-out. Can anyone explain the logic at page-time out for seaside? ======================= For those interested (I suppose it's only me), Here are traces from the rewrite log with different rewrite rules. Modules loaded: rewrite_module proxy_module proxy_http_module No cache modules loaded *No* other "proxy" directives used except below *===TRACE 1===== *ProxyPreserveHost On RewriteEngine ON RewriteRule ^/seaside/files/(.*)$ http://localhost:9999/seaside/files/$1 [proxy,last] RewriteCond /home/web/mmiki/%{REQUEST_FILENAME} !-f RewriteRule ^/(.*)$ http://localhost:9999/seaside/mmiki/$1 [proxy,last] Result: at page timeout, it appears that seaside writes the path to the Pier app, resulting in a duplicated path [Start rewrite engine on request] (2) init rewrite engine with requested uri /DonsTestPage [is there a match with first rule?] (3) applying pattern '^/seaside/files/(.*)$' to uri '/DonsTestPage' [nope, check next rule] (3) applying pattern '^/(.*)$' to uri '/DonsTestPage' [yep, look at the condition before this] (4) RewriteCond: input='/home/web/mmiki//DonsTestPage' pattern='!-f' => matched [nope, this isn't a local file, so rewrite it] (2) rewrite /DonsTestPage -> http://localhost:9999/seaside/mmiki/DonsTestPage [and send it to seaside with the proper path] (2) forcing proxy-throughput with http://localhost:9999/seaside/mmiki/DonsTestPage (1) go-ahead with proxy request proxy:http://localhost:9999/seaside/mmiki/DonsTestPage [OK] [but, then it continues - THIS MUST BE THE TIME OUT] [Start rewrite engine on request] (2) init rewrite engine with requested uri /seaside/mmiki/DonsTestPage [is there a match with first rule?] (3) applying pattern '^/seaside/files/(.*)$' to uri '/seaside/mmiki/DonsTestPage' [nope, check next rule] (3) applying pattern '^/(.*)$' to uri '/seaside/mmiki/DonsTestPage' [yep, look at the condition before this] (4) RewriteCond: input='/home/web/mmiki//seaside/mmiki/DonsTestPage' pattern='!-f' => matched [nope, this isn't a file, so rewrite it] (2) rewrite /seaside/mmiki/DonsTestPage -> http://localhost:9999/seaside/mmiki/seaside/mmiki/DonsTestPage [and send it on it's way] (2) forcing proxy-throughput with http://localhost:9999/seaside/mmiki/seaside/mmiki/DonsTestPage (1) go-ahead with proxy request proxy:http://localhost:9999/seaside/mmiki/seaside/mmiki/DonsTestPage [OK] *===TRACE 2=============* If a rewrite rule is added to eliminate the path at the time out: ================ ProxyPreserveHost On RewriteEngine ON RewriteRule ^/seaside/files/(.*)$ http://localhost:9999/seaside/files/$1 [proxy,last] RewriteRule ^/seaside/mmiki/(.*)$ http://localhost:9999/$1 [proxy,last] RewriteCond /home/web/mmiki/%{REQUEST_FILENAME} !-f RewriteRule ^/(.*)$ http://localhost:9999/seaside/mmiki/$1 [proxy,last] Result: 2nd rewrite rule catches path but seaside really needs the path to the Pier app. (2) init rewrite engine with requested uri /DonsTestPage (3) applying pattern '^/seaside/files/(.*)$' to uri '/DonsTestPage' (3) applying pattern '^/seaside/mmiki/(.*)$' to uri '/DonsTestPage' (3) applying pattern '^/(.*)$' to uri '/DonsTestPage' (4) RewriteCond: input='/home/web/mmiki//DonsTestPage' pattern='!-f' => matched (2) rewrite /DonsTestPage -> http://localhost:9999/seaside/mmiki/DonsTestPage (2) forcing proxy-throughput with http://localhost:9999/seaside/mmiki/DonsTestPage (1) go-ahead with proxy request proxy:http://localhost:9999/seaside/mmiki/DonsTestPage [OK] (2) init rewrite engine with requested uri /seaside/mmiki/DonsTestPage (3) applying pattern '^/seaside/files/(.*)$' to uri '/seaside/mmiki/DonsTestPage' (3) applying pattern '^/seaside/mmiki/(.*)$' to uri '/seaside/mmiki/DonsTestPage' (2) rewrite /seaside/mmiki/DonsTestPage -> http://localhost:9999/DonsTestPage (2) forcing proxy-throughput with http://localhost:9999/DonsTestPage (1) go-ahead with proxy request proxy:http://localhost:9999/DonsTestPage [OK] *===TRACE 3===========* But,of course seaside needs the path to the app. If the rewrite rule is written to add the path for the timeout It works fine. Except the URL in the browser adds the path =============== ProxyPreserveHost On RewriteEngine ON RewriteRule ^/seaside/files/(.*)$ http://localhost:9999/seaside/files/$1 [proxy,last] RewriteRule ^/seaside/mmiki/(.*)$ http://localhost:9999/seaside/mmiki/$1 [proxy,last] RewriteCond /home/web/mmiki/%{REQUEST_FILENAME} !-f RewriteRule ^/(.*)$ http://localhost:9999/seaside/mmiki/$1 [proxy,last] Result: 2nd RewriteRule adds the correct path, but the URL the client receives includes the path. Not pretty. (2) init rewrite engine with requested uri /DonsTestPage (3) applying pattern '^/seaside/files/(.*)$' to uri '/DonsTestPage' (3) applying pattern '^/seaside/mmiki/(.*)$' to uri '/DonsTestPage' (3) applying pattern '^/(.*)$' to uri '/DonsTestPage' (4) RewriteCond: input='/home/web/mmiki//DonsTestPage' pattern='!-f' => matched (2) rewrite /DonsTestPage -> http://localhost:9999/seaside/mmiki/DonsTestPage (2) forcing proxy-throughput with http://localhost:9999/seaside/mmiki/DonsTestPage (1) go-ahead with proxy request proxy:http://localhost:9999/seaside/mmiki/DonsTestPage [OK] (2) init rewrite engine with requested uri /seaside/mmiki/DonsTestPage (3) applying pattern '^/seaside/files/(.*)$' to uri '/seaside/mmiki/DonsTestPage' (3) applying pattern '^/seaside/mmiki/(.*)$' to uri '/seaside/mmiki/DonsTestPage' (2) rewrite /seaside/mmiki/DonsTestPage -> http://localhost:9999/seaside/mmiki/DonsTestPage (2) forcing proxy-throughput with http://localhost:9999/seaside/mmiki/DonsTestPage (1) go-ahead with proxy request proxy:http://localhost:9999/seaside/mmiki/DonsTestPage [OK] This is the desired path, but the URL in the client browser is incorrect: It is: http://igor:8080/seaside/mmiki/DonsTestPage?command=PRViewCommand&view=PRDefaultView It should not have the "/seaside/mmiki" path, And, actually, this doesn't work when you want to go back to the top in Pier after timeout. From keith_hodges at yahoo.co.uk Tue Mar 20 06:12:44 2007 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Tue, 20 Mar 2007 05:12:44 +0000 Subject: No free space in set In-Reply-To: <7C1E980B-B9B9-449E-8EEF-ACA6C24F0A79@iam.unibe.ch> References: <448ECA08.9090307@yahoo.co.uk> <44F04F16.7050502@laposte.net> <44F04FDD.10003@laposte.net> <7C1E980B-B9B9-449E-8EEF-ACA6C24F0A79@iam.unibe.ch> Message-ID: <45FF6D4C.8050905@yahoo.co.uk> Lukas Renggli wrote: > It took at lot of time, but I just fixed the reported problem. It was > a long standing Seaside bug related to the backtracking of Set's and > all its subclasses. This problem should be fixed in my latest commit Good catch :-) Thanks for all of your investment of effort into this one. Keith ___________________________________________________________ All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of use." - PC Magazine http://uk.docs.yahoo.com/nowyoucan.html From brad at sonaural.com Tue Mar 20 06:39:10 2007 From: brad at sonaural.com (Brad Fuller) Date: Mon, 19 Mar 2007 22:39:10 -0700 Subject: path error on link-click after a while in Pier In-Reply-To: <45FA1275.2000603@sonaural.com> References: <45FA1275.2000603@sonaural.com> Message-ID: <45FF737E.3080502@sonaural.com> http://cmsbox.netstyle.ch/ seems to exhibit a problem too when it times out. Although, it looks more like it uses ProxyPass instead of Rewrite rules. From sebjulliand at gmail.com Tue Mar 20 13:35:54 2007 From: sebjulliand at gmail.com (=?ISO-8859-1?Q?S=E9bastien_Julliand?=) Date: Tue, 20 Mar 2007 13:35:54 +0100 Subject: Commands on multiple structures / Timestamps In-Reply-To: References: <4f6c865a0703191121k3b63323eyad91fe9dab74f6da@mail.gmail.com> Message-ID: <4f6c865a0703200535i6ec62758n3de9a93c9e118b3d@mail.gmail.com> 2007/3/19, Lukas Renggli : > > > According to how commands work in Pier, is it possible to apply a > > command on more than a single structure? > > Yes, however this is not the way they have been designed to be used. > It is better to create a copy for every execution. To make a command > to a different structure you need a new context anyway as contexts > are immutable. > > > Another question: is there something in Pier to retrieve the date > > and time of creation/modification of each page (or do I need to add > > some descriptions to PRStructure?) > > Retrieving creating/modification time only works with a persistency > scheme attached logs all the command executions. > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > Ok Lukas. Does this persitency scheme adds some descriptions to the structures? (like Unix Security adds owner/user/group description for example) -- S?bastien JULLIAND -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20070320/0731c0d9/attachment.html From ssastre at seaswork.com Tue Mar 20 14:06:20 2007 From: ssastre at seaswork.com (Sebastian Sastre) Date: Tue, 20 Mar 2007 10:06:20 -0300 Subject: Adaptative (to user's role) edition of objects with many "properties" Message-ID: Hi there, for applications sometimes the user want to edit an object that has many instvars to edit or it's composed. I guess that this could lead to forms too large to be practical for the end user's daily use. One solution to this is could be the partition of the form into smaller forms with tabs. The problem is that one should describe once and let the description prepared to be capable of build several composed forms to each model. This could be archieved by different form building policies. A concrete form build's policy should define the look of the component. To give a simple example of this policy: if the component to build is no bigger than 6 "fields" it should be like "the normal ones" (actual default) but if it has more than 6 "fields", put the first 6 in a tab and the next 6 in another tab (or more, until the total ammount of fields are reached). The policies should be extensible but generic enough to maintain economy in the design. Is also desirable collaboration with user's role to gain additional customization of the observation. A smarter policy could take advantage of grouping info set in the descriptions. As an example some fields could belong to the #'admin.indetification' or #'operator.identification' group/role to keep grouped the right fields of the editor's form for the object/model. I'd like to hear opinions about this or to know about better approachs to solve this problem. cheers, Sebastian Sastre PD: as a side note I'm evaluating to use Magritte with Glorp mapping (like Ramon Leon suggest) so, if I'm undesrtanding this right, the descriptions to map the persistance of the model objects should be "like" another role observating them but describing the persistance wanted. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20070320/e258c96b/attachment.html From renggli at iam.unibe.ch Tue Mar 20 14:57:03 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 20 Mar 2007 14:57:03 +0100 Subject: Commands on multiple structures / Timestamps In-Reply-To: <4f6c865a0703200535i6ec62758n3de9a93c9e118b3d@mail.gmail.com> References: <4f6c865a0703191121k3b63323eyad91fe9dab74f6da@mail.gmail.com> <4f6c865a0703200535i6ec62758n3de9a93c9e118b3d@mail.gmail.com> Message-ID: <3387DD21-0E74-496A-8F35-22B348F3B205@iam.unibe.ch> > Ok Lukas. > Does this persitency scheme adds some descriptions to the > structures? (like Unix Security adds owner/user/group description > for example) Yes, most extension packages use descriptions to extend existing classes with new functionality. The information is basically already there (see #creationTimestamp and #modificationTimestamp), I probably just missed to add the description. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Tue Mar 20 15:23:40 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 20 Mar 2007 15:23:40 +0100 Subject: Adaptative (to user's role) edition of objects with many "properties" In-Reply-To: References: Message-ID: <87581635-A9BD-4FCC-A7E2-D6386C0EF39F@iam.unibe.ch> > for applications sometimes the user want to edit an object that > has many instvars to edit or it's composed. I guess that this could > lead to forms too large to be practical for the end user's daily use. Certainly. > This could be archieved by different form building policies. A > concrete form build's policy should define the look of the > component. To give a simple example of this policy: if the > component to build is no bigger than 6 "fields" it should be like > "the normal ones" (actual default) but if it has more than 6 > "fields", put the first 6 in a tab and the next 6 in another tab > (or more, until the total ammount of fields are reached). A subclass (or a replacement) of MAContainerComponent is your friend. There are other ways to define custom rendering strategies as you can see on the slides 48 to 54 at: http://www.lukas-renggli.ch/smalltalk/magritte/tutorial.pdf > The policies should be extensible but generic enough to > maintain economy in the design. Is also desirable collaboration > with user's role to gain additional customization of the observation. When developing an application I basically find myself describing objects (1), writing new or custom interpreters of these descriptions (2) and adding some glue code (3). As you observed the interpreters included with Magritte are very basic and usually require some customization when being used in a real world applications. However the requirements for different applications are usually so different that (in my opinion) it makes no sense to try to make something that works for everybody. For example, have a look at http://www.juniorwebaward.ch and click on 'Anmelden' (or 'S'annoncer' if you are in the french version). What you have there is a flow of automatically generated Magritte forms. You have something very similar at http://www.seasidehosting.st, however there are some distinct differences. It is very easy to iterate over a set of descriptions and build your own custom interface and integrate it with different validation strategies. > A smarter policy could take advantage of grouping info set in > the descriptions. As an example some fields could belong to the > #'admin.indetification' or #'operator.identification' group/role to > keep grouped the right fields of the editor's form for the object/ > model. For the project I am currently working on I added a group property to MADescription that does exactly that. The interpreter looks like this: renderContentOn: html group := nil. html heading level: 1; with: 'Preferences'. html form multipart; with: [ self editor description do: [ :each | each group = group ifFalse: [ html heading level: 2; with: (self labelForSelector: each group). group := each group ]. html heading level: 3; with: each label. html render: (self editor childAt: each); break ]. html submitButton text: 'Save'; callback: [ self editor commit ] ] > PD: as a side note I'm evaluating to use Magritte with Glorp > mapping (like Ramon Leon suggest) so, if I'm undesrtanding this > right, the descriptions to map the persistance of the model objects > should be "like" another role observating them but describing the > persistance wanted. I am using properties for that, e.g. something like #bePersistent to tell the description to be considered for persistency or #beSearchable to tell the description to build indexes and to be considered for searches, etc. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From ducasse at iam.unibe.ch Tue Mar 20 21:28:16 2007 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Tue, 20 Mar 2007 21:28:16 +0100 Subject: Commands on multiple structures / Timestamps In-Reply-To: <3387DD21-0E74-496A-8F35-22B348F3B205@iam.unibe.ch> References: <4f6c865a0703191121k3b63323eyad91fe9dab74f6da@mail.gmail.com> <4f6c865a0703200535i6ec62758n3de9a93c9e118b3d@mail.gmail.com> <3387DD21-0E74-496A-8F35-22B348F3B205@iam.unibe.ch> Message-ID: <77D3F0FB-BE6B-4B5E-8E03-2C3B1AC169EF@iam.unibe.ch> On 20 mars 07, at 14:57, Lukas Renggli wrote: >> Ok Lukas. >> Does this persitency scheme adds some descriptions to the >> structures? (like Unix Security adds owner/user/group description >> for example) > > Yes, most extension packages use descriptions to extend existing > classes with new functionality. The information is basically already > there (see #creationTimestamp and #modificationTimestamp), I probably > just missed to add the description. which would make a lot of sense since they represent some really key information for querying. So seb please add them. Stef > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From ssastre at seaswork.com Tue Mar 20 21:29:52 2007 From: ssastre at seaswork.com (Sebastian Sastre) Date: Tue, 20 Mar 2007 17:29:52 -0300 Subject: Adaptative (to user's role) edition of objects with many"properties" In-Reply-To: <87581635-A9BD-4FCC-A7E2-D6386C0EF39F@iam.unibe.ch> Message-ID: This is so interesting.. I didn't use Glorp before. Can you tell me more about how I can take advantage of your #beSearchable group proposal using Glorp? Some reference to start with would help. thanks, Sebastian Sastre > -----Mensaje original----- > De: smallwiki-bounces at iam.unibe.ch > [mailto:smallwiki-bounces at iam.unibe.ch] En nombre de Lukas Renggli > Enviado el: Martes, 20 de Marzo de 2007 11:24 > Para: Magritte, Pier and Related Tools ... > Asunto: Re: Adaptative (to user's role) edition of objects > with many"properties" > > > for applications sometimes the user want to edit an object that > > has many instvars to edit or it's composed. I guess that this could > > lead to forms too large to be practical for the end user's > daily use. > > Certainly. > > > This could be archieved by different form building policies. A > > concrete form build's policy should define the look of the > component. > > To give a simple example of this policy: if the component > to build is > > no bigger than 6 "fields" it should be like "the normal > ones" (actual > > default) but if it has more than 6 "fields", put the first > 6 in a tab > > and the next 6 in another tab (or more, until the total ammount of > > fields are reached). > > A subclass (or a replacement) of MAContainerComponent is your > friend. > There are other ways to define custom rendering strategies as > you can see on the slides 48 to 54 at: > > http://www.lukas-renggli.ch/smalltalk/magritte/tutorial.pdf > > > The policies should be extensible but generic enough to > maintain > > economy in the design. Is also desirable collaboration with user's > > role to gain additional customization of the observation. > > When developing an application I basically find myself > describing objects (1), writing new or custom interpreters of > these descriptions > (2) and adding some glue code (3). > > As you observed the interpreters included with Magritte are > very basic and usually require some customization when being > used in a real world applications. However the requirements > for different applications are usually so different that (in > my opinion) it makes no sense to try to make something that > works for everybody. For example, have a look at > http://www.juniorwebaward.ch and click on 'Anmelden' (or > 'S'annoncer' if you are in the french version). What you have > there is a flow of automatically generated Magritte forms. > You have something very similar at > http://www.seasidehosting.st, however there are some distinct > differences. It is very easy to iterate over a set of > descriptions and build your own custom interface and > integrate it with different validation strategies. > > > A smarter policy could take advantage of grouping info > set in the > > descriptions. As an example some fields could belong to the > > #'admin.indetification' or #'operator.identification' group/role to > > keep grouped the right fields of the editor's form for the object/ > > model. > > For the project I am currently working on I added a group > property to MADescription that does exactly that. The > interpreter looks like this: > > renderContentOn: html > group := nil. > html heading level: 1; with: 'Preferences'. > html form multipart; with: [ > self editor description do: [ :each | > each group = group ifFalse: [ > html heading level: 2; with: > (self labelForSelector: each group). > group := each group ]. > html heading level: 3; with: each label. > html render: (self editor childAt: > each); break ]. > html submitButton > text: 'Save'; > callback: [ self editor commit ] ] > > > PD: as a side note I'm evaluating to use Magritte with > Glorp mapping > > (like Ramon Leon suggest) so, if I'm undesrtanding this right, the > > descriptions to map the persistance of the model objects should be > > "like" another role observating them but describing the persistance > > wanted. > > I am using properties for that, e.g. something like > #bePersistent to tell the description to be considered for > persistency or #beSearchable to tell the description to build > indexes and to be considered for searches, etc. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From sebjulliand at gmail.com Wed Mar 21 00:01:21 2007 From: sebjulliand at gmail.com (=?ISO-8859-1?Q?S=E9bastien_Julliand?=) Date: Wed, 21 Mar 2007 00:01:21 +0100 Subject: Commands on multiple structures / Timestamps In-Reply-To: <77D3F0FB-BE6B-4B5E-8E03-2C3B1AC169EF@iam.unibe.ch> References: <4f6c865a0703191121k3b63323eyad91fe9dab74f6da@mail.gmail.com> <4f6c865a0703200535i6ec62758n3de9a93c9e118b3d@mail.gmail.com> <3387DD21-0E74-496A-8F35-22B348F3B205@iam.unibe.ch> <77D3F0FB-BE6B-4B5E-8E03-2C3B1AC169EF@iam.unibe.ch> Message-ID: <4f6c865a0703201601s64393fb2jb2c1ae9ec0266ebf@mail.gmail.com> 2007/3/20, st?phane ducasse : > > > On 20 mars 07, at 14:57, Lukas Renggli wrote: > > >> Ok Lukas. > >> Does this persitency scheme adds some descriptions to the > >> structures? (like Unix Security adds owner/user/group description > >> for example) > > > > Yes, most extension packages use descriptions to extend existing > > classes with new functionality. The information is basically already > > there (see #creationTimestamp and #modificationTimestamp), I probably > > just missed to add the description. > > which would make a lot of sense since they represent some really key > information for querying. > So seb please add them. > > Stef > > > > > > Lukas > > > > -- > > Lukas Renggli > > http://www.lukas-renggli.ch > > > > > > > > _______________________________________________ > > SmallWiki, Magritte, Pier and Related Tools ... > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > Ok, done. I just added two timestamp descriptions to PRStructure (creation & modification). Creation is initialized with "Timestamp now" in #doExecute of PRAddCommand. Modification is initialized/modified in #doExecute of PREditCommand. They can be retrieved by their respectives selectors and by #creationTimestamp and #modificationTimestamp if no persistency scheme is plugged. It seems to work (and it looks nice in the report ^^). Did I forget something? Anyway Lukas, we were talking with stef about adding "comparison description" to the meta-descriptions of Magritte. For example: I have a report that lists every pages of Pier. It's a MAReport, so it uses pages descriptions and it's very nice. Now, I want that report to show me only pages that match a specific query (say Creation timeStamp = Today). Something in the Macintosh finder's style ;). It could be great, to build this query, if I could choose a description in a dropdown menu and then, this description tells me "you can compare me this way, using these methods". Then I show another dropdown menu with these methods. And so everything could be done dynamically. If you decide to add a new description to PRStructure, then my report will still work, and so on... Do you see what I mean and do you have an ideas on that? :p Cheers, -- S?bastien JULLIAND -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20070321/dfc35eca/attachment.html From renggli at iam.unibe.ch Wed Mar 21 00:02:41 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Wed, 21 Mar 2007 00:02:41 +0100 Subject: Adaptative (to user's role) edition of objects with many"properties" In-Reply-To: References: Message-ID: > This is so interesting.. > I didn't use Glorp before. Can you tell me more about how I can take > advantage of your #beSearchable group proposal using Glorp? Some > reference > to start with would help. I am sure the maintainer of the Magritte Glorp package can help you here. This is something that I did in other applications. To see an open-source example have a look at #beEditable and #bePersistent in Pier. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Wed Mar 21 00:12:18 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Wed, 21 Mar 2007 00:12:18 +0100 Subject: Commands on multiple structures / Timestamps In-Reply-To: <4f6c865a0703201601s64393fb2jb2c1ae9ec0266ebf@mail.gmail.com> References: <4f6c865a0703191121k3b63323eyad91fe9dab74f6da@mail.gmail.com> <4f6c865a0703200535i6ec62758n3de9a93c9e118b3d@mail.gmail.com> <3387DD21-0E74-496A-8F35-22B348F3B205@iam.unibe.ch> <77D3F0FB-BE6B-4B5E-8E03-2C3B1AC169EF@iam.unibe.ch> <4f6c865a0703201601s64393fb2jb2c1ae9ec0266ebf@mail.gmail.com> Message-ID: <01E764CD-2617-417A-8D76-7D57F7643D98@iam.unibe.ch> > Do you see what I mean and do you have an ideas on that? :p Yes, I see. This is certainly feasible. Take your ideas from Apple Mail, iTunes and Finder smart groups. Also check out the attached screenshot, it shows a user interface to specify condition in a similar way. This commercial application (therefor I cannot give you the source code) based on Magritte has been written a couple of years ago. -------------- next part -------------- A non-text attachment was scrubbed... Name: pastedGraphic.tiff Type: image/tiff Size: 36580 bytes Desc: not available Url : http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20070321/151a18eb/pastedGraphic-0001.tiff -------------- next part -------------- Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From ducasse at iam.unibe.ch Wed Mar 21 10:05:05 2007 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Wed, 21 Mar 2007 10:05:05 +0100 Subject: Commands on multiple structures / Timestamps In-Reply-To: <01E764CD-2617-417A-8D76-7D57F7643D98@iam.unibe.ch> References: <4f6c865a0703191121k3b63323eyad91fe9dab74f6da@mail.gmail.com> <4f6c865a0703200535i6ec62758n3de9a93c9e118b3d@mail.gmail.com> <3387DD21-0E74-496A-8F35-22B348F3B205@iam.unibe.ch> <77D3F0FB-BE6B-4B5E-8E03-2C3B1AC169EF@iam.unibe.ch> <4f6c865a0703201601s64393fb2jb2c1ae9ec0266ebf@mail.gmail.com> <01E764CD-2617-417A-8D76-7D57F7643D98@iam.unibe.ch> Message-ID: <4063BBF0-E4BB-46C8-BA94-ED292B1FEF9D@iam.unibe.ch> lukas I thought that we could enrich the metadescription themselves to let us know what are the selectors we can use and the other object we can use (such as today lastMonth....) Stef On 21 mars 07, at 00:12, Lukas Renggli wrote: >> Do you see what I mean and do you have an ideas on that? :p > > Yes, I see. This is certainly feasible. Take your ideas from Apple > Mail, iTunes and Finder smart groups. > > Also check out the attached screenshot, it shows a user interface > to specify condition in a similar way. This commercial application > (therefor I cannot give you the source code) based on Magritte has > been written a couple of years ago. > > > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From renggli at iam.unibe.ch Wed Mar 21 10:47:35 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Wed, 21 Mar 2007 10:47:35 +0100 Subject: Commands on multiple structures / Timestamps In-Reply-To: <4063BBF0-E4BB-46C8-BA94-ED292B1FEF9D@iam.unibe.ch> References: <4f6c865a0703191121k3b63323eyad91fe9dab74f6da@mail.gmail.com> <4f6c865a0703200535i6ec62758n3de9a93c9e118b3d@mail.gmail.com> <3387DD21-0E74-496A-8F35-22B348F3B205@iam.unibe.ch> <77D3F0FB-BE6B-4B5E-8E03-2C3B1AC169EF@iam.unibe.ch> <4f6c865a0703201601s64393fb2jb2c1ae9ec0266ebf@mail.gmail.com> <01E764CD-2617-417A-8D76-7D57F7643D98@iam.unibe.ch> <4063BBF0-E4BB-46C8-BA94-ED292B1FEF9D@iam.unibe.ch> Message-ID: > lukas I thought that we could enrich the metadescription themselves to > let us know what are the selectors we can use and the other object we > can use (such as today lastMonth....) Exactly, Magritte does not provide this information right now. In fact trough the history of Magritte there were some attempts in providing something like that as part of the core framework, but it hasn't happened yet as it turned out to be a bit difficult to make it useful in different contexts. What I did in this project I sent the screenshot was to create a comparator object that represented a sentences like: creation date is earlier than yesterday tags contains seaside number of visits between 1000 and 2000 etc. As you can observe this is basically a Smalltalk message to a receiver with some arguments. How to build these messages? I extended descriptions to return comparators they support: this is basically a collection of selectors associated with a collection of descriptions for each of their arguments. Then I build a UI that (1) lets users choose the description they want to query, (2) displays a drop down with the selectors (or better a readable label) that let users choose an operation and then (3) display editors for the arguments based on the descriptions. That's the basic strategy. We can do some pair programming next week and try to come up with something that is useable as part of the core, if you like? Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From sebjulliand at gmail.com Wed Mar 21 15:46:20 2007 From: sebjulliand at gmail.com (=?ISO-8859-1?Q?S=E9bastien_Julliand?=) Date: Wed, 21 Mar 2007 15:46:20 +0100 Subject: Commands on multiple structures / Timestamps In-Reply-To: References: <4f6c865a0703191121k3b63323eyad91fe9dab74f6da@mail.gmail.com> <4f6c865a0703200535i6ec62758n3de9a93c9e118b3d@mail.gmail.com> <3387DD21-0E74-496A-8F35-22B348F3B205@iam.unibe.ch> <77D3F0FB-BE6B-4B5E-8E03-2C3B1AC169EF@iam.unibe.ch> <4f6c865a0703201601s64393fb2jb2c1ae9ec0266ebf@mail.gmail.com> <01E764CD-2617-417A-8D76-7D57F7643D98@iam.unibe.ch> <4063BBF0-E4BB-46C8-BA94-ED292B1FEF9D@iam.unibe.ch> Message-ID: <4f6c865a0703210746g23fc5faj4cec51d60d2e9e8c@mail.gmail.com> 2007/3/21, Lukas Renggli : > > > lukas I thought that we could enrich the metadescription themselves to > > let us know what are the selectors we can use and the other object we > > can use (such as today lastMonth....) > > Exactly, Magritte does not provide this information right now. In > fact trough the history of Magritte there were some attempts in > providing something like that as part of the core framework, but it > hasn't happened yet as it turned out to be a bit difficult to make it > useful in different contexts. > > What I did in this project I sent the screenshot was to create a > comparator object that represented a sentences like: > > creation date is earlier than yesterday > tags contains seaside > number of visits between 1000 and 2000 > etc. > > As you can observe this is basically a Smalltalk message to a > receiver with some arguments. How to build these messages? I extended > descriptions to return comparators they support: this is basically a > collection of selectors associated with a collection of descriptions > for each of their arguments. Then I build a UI that (1) lets users > choose the description they want to query, (2) displays a drop down > with the selectors (or better a readable label) that let users choose > an operation and then (3) display editors for the arguments based on > the descriptions. Yay! What you describe here is exactly what's in our mind. That's the basic strategy. We can do some pair programming next week > and try to come up with something that is useable as part of the > core, if you like? Yes, Stef told me you are around here next week. Indeed, it would be great if we could come up with something. I'll have a lot of time for this project next week, so I'll be ready when you are :). -- S?bastien JULLIAND -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20070321/c3b61d7e/attachment.html From renggli at iam.unibe.ch Sat Mar 24 08:14:23 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sat, 24 Mar 2007 08:14:23 +0100 Subject: path error on link-click after a while in Pier In-Reply-To: <45FF737E.3080502@sonaural.com> References: <45FA1275.2000603@sonaural.com> <45FF737E.3080502@sonaural.com> Message-ID: <629B7D92-8A62-468D-BE4A-2B694CB6FE67@iam.unibe.ch> > http://cmsbox.netstyle.ch/ seems to exhibit a problem too when it > times out. Although, it looks more like it uses ProxyPass instead > of Rewrite rules. Thanks, this is fixed now. No, it uses RewriteRules. It is basically the same setup everywhere. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From matthias.berth at googlemail.com Sat Mar 24 21:12:15 2007 From: matthias.berth at googlemail.com (Matthias Berth) Date: Sat, 24 Mar 2007 21:12:15 +0100 Subject: Linking to a command in a Pier wiki page? Message-ID: <9aa6ae270703241312o200171a8y8d82c05fae03be45@mail.gmail.com> Hello, is it possible to link to a Pier command from a Pier page? Example wiki text: !Welcome Please *log in>command:PULogin*, or *read more*. Cheers Matthias From renggli at iam.unibe.ch Sat Mar 24 21:58:46 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sat, 24 Mar 2007 21:58:46 +0100 Subject: Linking to a command in a Pier wiki page? In-Reply-To: <9aa6ae270703241312o200171a8y8d82c05fae03be45@mail.gmail.com> References: <9aa6ae270703241312o200171a8y8d82c05fae03be45@mail.gmail.com> Message-ID: > is it possible to link to a Pier command from a Pier page? > > Example wiki text: > > !Welcome > Please *log in>command:PULogin*, or *read more*. This is currently not possible, but would be a nice thing to add. For now (as a workaround) you can create try the following markup using an external URL, however note that this will create a new session: !Welcome Please *log in>http://www.lukas-renggli.ch/?command=PULogin*, or *read more*. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Sat Mar 24 21:59:43 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sat, 24 Mar 2007 21:59:43 +0100 Subject: [ANN] Bug Tracking on Mantis Message-ID: Bugs of Magritte and Pier are now tracked on Mantis. To report chose the project 'Squeak Packages' and an appropriate category, e.g. 'Magritte' or 'Pier'. Of course, and this is still the preferred way, all the Monticello repositories are open for your contribution. Therefor if you have found and fixed a bug you can directly commit your changes there. They will eventually be merged into the mainstream. That's simple and generally more efficient. For all other cases there is Mantis now. Cheers, Lukas PS: There is also a category for Seaside on Mantis, in case that's the source of problems. -- Lukas Renggli http://www.lukas-renggli.ch From brad at sonaural.com Sat Mar 24 23:20:51 2007 From: brad at sonaural.com (Brad Fuller) Date: Sat, 24 Mar 2007 15:20:51 -0700 Subject: path error on link-click after a while in Pier In-Reply-To: <629B7D92-8A62-468D-BE4A-2B694CB6FE67@iam.unibe.ch> References: <45FA1275.2000603@sonaural.com> <45FF737E.3080502@sonaural.com> <629B7D92-8A62-468D-BE4A-2B694CB6FE67@iam.unibe.ch> Message-ID: <4605A443.1060800@sonaural.com> Lukas Renggli wrote: >> http://cmsbox.netstyle.ch/ seems to exhibit a problem too when it >> times out. Although, it looks more like it uses ProxyPass instead >> of Rewrite rules. >> > > Thanks, this is fixed now. > > No, it uses RewriteRules. It is basically the same setup everywhere. > Can you tell me how you fixed it. I STILL have the same problems as before. I cannot figure i out. -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From renggli at iam.unibe.ch Mon Mar 26 09:16:04 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 26 Mar 2007 09:16:04 +0200 Subject: path error on link-click after a while in Pier In-Reply-To: <4605A443.1060800@sonaural.com> References: <45FA1275.2000603@sonaural.com> <45FF737E.3080502@sonaural.com> <629B7D92-8A62-468D-BE4A-2B694CB6FE67@iam.unibe.ch> <4605A443.1060800@sonaural.com> Message-ID: <615E900F-4678-49B3-B6AA-A6CED11FBA74@iam.unibe.ch> >>> http://cmsbox.netstyle.ch/ seems to exhibit a problem too when it >>> times out. Although, it looks more like it uses ProxyPass instead >>> of Rewrite rules. >>> >> >> Thanks, this is fixed now. >> >> No, it uses RewriteRules. It is basically the same setup everywhere. > > Can you tell me how you fixed it. I STILL have the same problems as > before. I cannot figure i out. I applied this rewrite rule as the first one: RewriteRule ^/seaside/pier(.*)$ http://www.lukas-renggli.ch$1 [R,L] It redirects to the root if Seaside generates an invalid request URL. Unfortunately this is not easy to fix in Seaside, as this would break a lot of other applications that are not served from the root. I will see for Seaside 2.8 if we can do something about it. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From charles at datasof.com Mon Mar 26 17:12:50 2007 From: charles at datasof.com (Charles A. Monteiro) Date: Mon, 26 Mar 2007 10:12:50 -0500 Subject: [ANN] Bug Tracking on Mantis In-Reply-To: References: Message-ID: So you all bumped into Mantis :), I did as well about a year ago, not a bad bug tracker at all, it has its couple quirks but overall at least to me smoother to use than something like RequestTracker. On Sat, 24 Mar 2007 15:59:43 -0500, Lukas Renggli wrote: > Bugs of Magritte and Pier are now tracked on Mantis. To report chose > the project 'Squeak Packages' and an appropriate category, e.g. > 'Magritte' or 'Pier'. > > Of course, and this is still the preferred way, all the Monticello > repositories are open for your contribution. Therefor if you have > found and fixed a bug you can directly commit your changes there. > They will eventually be merged into the mainstream. That's simple and > generally more efficient. For all other cases there is Mantis now. > > Cheers, > Lukas > > PS: There is also a category for Seaside on Mantis, in case that's > the source of problems. > -- Charles A. Monteiro http://wiki.nycsmalltalk.org http://www.monteirosfusion.com http://monteirofusion.blogspot.com From renggli at iam.unibe.ch Mon Mar 26 16:24:25 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 26 Mar 2007 16:24:25 +0200 Subject: [ANN] Bug Tracking on Mantis In-Reply-To: References: Message-ID: <1B087BAF-7F69-4C21-B358-B7365843B11D@iam.unibe.ch> > So you all bumped into Mantis :), I did as well about a year ago, > not a > bad bug tracker at all, it has its couple quirks but overall at > least to > me smoother to use than something like RequestTracker. Mhh, I noticed that I forgot to mention the URL. Less useful if nobody knows where to find it, but I think most people correctly guessed that we use the official Squeak bug tracker: http://bugs.squeak.org/set_project.php? project_id=9&make_default=no&ref=bug_report_page.php Lukas -- Lukas Renggli http://www.lukas-renggli.ch From damien.cassou at gmail.com Tue Mar 27 18:23:29 2007 From: damien.cassou at gmail.com (Damien Cassou) Date: Tue, 27 Mar 2007 18:23:29 +0200 Subject: Problem with Pier Blog In-Reply-To: References: <45F6D535.6080604@zyoconsulting.com> <52CCC8B9-4A98-4D70-8165-81433B1B8EA6@iam.unibe.ch>

Message-ID: <6ac749c10703270923w467e4b3ambb3dd5e3b9b650aa@mail.gmail.com> Pier-Blog is on Universe. 2007/3/15, st?phane ducasse : > True > This is an excellent example that could be used to propose a good > solution to deal with dependencies. > > On 15 mars 07, at 08:07, Lukas Renggli wrote: > > >> so maybe you should have an installer. > >> I have the impression that as soon as a package get a public usage it > >> should have an installer. > >> or we will be killed by dependencies. > > > > It starts to be complicated. I already have sort of a simple > > installer framework. > > > > Magritte -> loads seaside, kom, magritte > > Pier -> loads magritte, pier > > Pier Unix Security -> loads pier, unix security > > > > But then > > > > Pier Blog -> loads pier, rsrss, pier blog > > > > What about the package 'Pier Unix Security'? Should that be loaded as > > well? No, because there are other security frameworks around that > > might be used instead. The dependenceis of 'Pier Unix Security' and > > 'Pier Blog' could depend on different versions of Pier. What a mess. > > > > Lukas > > > > > > > > > > > >> > >> Stef > >> > >> On 13 mars 07, at 17:51, Lukas Renggli wrote: > >> > >>>> I get the next error: > >>>> > >>>> > >>>> MessageNotUnderstood: WARenderedHtmlRoot>>rss > >>> > >>> The Pier blog requires the package RSRSS from http:// > >>> www.squeaksource.com/rsrss as a prerequisite. > >>> > >>> Cheers, > >>> Lukas > >>> > >>> -- > >>> Lukas Renggli > >>> http://www.lukas-renggli.ch > >>> > >>> > >>> > >>> _______________________________________________ > >>> SmallWiki, Magritte, Pier and Related Tools ... > >>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > >> > >> > >> _______________________________________________ > >> SmallWiki, Magritte, Pier and Related Tools ... > >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > > -- > > Lukas Renggli > > http://www.lukas-renggli.ch > > > > > > > > _______________________________________________ > > SmallWiki, Magritte, Pier and Related Tools ... > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Damien Cassou From matthias.berth at googlemail.com Tue Mar 27 19:57:55 2007 From: matthias.berth at googlemail.com (Matthias Berth) Date: Tue, 27 Mar 2007 19:57:55 +0200 Subject: Design of Pier Blog Message-ID: <9aa6ae270703271057y4d0f5445l8394fe1794c5be44@mail.gmail.com> Hello, I am trying to figure out the design of the classes in Pier Blog. I am wondering why PBBlog is a subclass of PRCase, and not a direct subclass of PRStructure: PRStructure #('parent' 'name' 'title' 'tags') PRCase #('document') PBBlog #('managingEditor' 'webMaster' 'copyright' 'language' 'itemCount' 'feedTitle' 'commentTimeout') PBEntry #('uuid' 'author' 'publication') PBComment #() PBPost #('sourceUrl' 'sourceTitle' 'enclosure') PRPage #() PRComponent #('componentClass' 'settings') PRFile #('file') PRForm #('model' 'metamodel') PRCase's class comment says:"I am an abstract class holding onto a document definition representing the contents of the receiver. Most of my subclasses will allow user to edit myself using the Wiki syntax." I guess my question is: for an application that is similar to a blog (managing a list of homogeneous entries, maybe nested), is it a good idea to make it a direct subclass of PRStructure? Matthias From renggli at iam.unibe.ch Tue Mar 27 21:06:23 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 27 Mar 2007 21:06:23 +0200 Subject: Design of Pier Blog In-Reply-To: <9aa6ae270703271057y4d0f5445l8394fe1794c5be44@mail.gmail.com> References: <9aa6ae270703271057y4d0f5445l8394fe1794c5be44@mail.gmail.com> Message-ID: <10F264FE-0280-416A-86CA-79736629473F@iam.unibe.ch> > I am trying to figure out the design of the classes in Pier Blog. I am > wondering why PBBlog is a subclass of PRCase, and not a direct > subclass of PRStructure: I wanted to be able to put a longer description of the Blog. PRStructure and all other subclasses except PRCase don't have an attached document. > I guess my question is: for an application that is similar to a blog > (managing a list of homogeneous entries, maybe nested), is it a good > idea to make it a direct subclass of PRStructure? The decision if a PRStructure can be nested or not is orthogonal to the functionality the class provides. The nesting is solely with the PRChildren decoration that can be added and removed on demand, in fact this happens behind the curtain. In SmallWiki this was different and caused a lot of problems. By overriding #canBeChildOf: and #canBeParentOf: you can control what can be nested into what else. So the question to subclass PRStructure or PRCase is solely a question if you need the parser, formatter and editor for the wiki syntax. aBoolean ifTrue: [ PRCase ] ifFalse: [ PRStructure ] Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From matthias.berth at googlemail.com Tue Mar 27 23:15:06 2007 From: matthias.berth at googlemail.com (Matthias Berth) Date: Tue, 27 Mar 2007 23:15:06 +0200 Subject: Design of Pier Blog In-Reply-To: <10F264FE-0280-416A-86CA-79736629473F@iam.unibe.ch> References: <9aa6ae270703271057y4d0f5445l8394fe1794c5be44@mail.gmail.com> <10F264FE-0280-416A-86CA-79736629473F@iam.unibe.ch> Message-ID: <9aa6ae270703271415x31c122dao2fd19db0465d1935@mail.gmail.com> Lukas, > I wanted to be able to put a longer description of the Blog. > PRStructure and all other subclasses except PRCase don't have an > attached document. yeah, that's what I found out after writing the email :-) > The decision if a PRStructure can be nested or not is orthogonal to > the functionality the class provides. The nesting is solely with the > PRChildren decoration that can be added and removed on demand, in > fact this happens behind the curtain. In SmallWiki this was different > and caused a lot of problems. By overriding #canBeChildOf: and > #canBeParentOf: you can control what can be nested into what else. > > So the question to subclass PRStructure or PRCase is solely a > question if you need the parser, formatter and editor for the wiki > syntax. That makes sense, thanks a lot! Matthias From brad at sonaural.com Wed Mar 28 00:48:54 2007 From: brad at sonaural.com (Brad Fuller) Date: Tue, 27 Mar 2007 15:48:54 -0700 Subject: path error on link-click after a while in Pier In-Reply-To: <615E900F-4678-49B3-B6AA-A6CED11FBA74@iam.unibe.ch> References: <45FA1275.2000603@sonaural.com> <45FF737E.3080502@sonaural.com> <629B7D92-8A62-468D-BE4A-2B694CB6FE67@iam.unibe.ch> <4605A443.1060800@sonaural.com> <615E900F-4678-49B3-B6AA-A6CED11FBA74@iam.unibe.ch> Message-ID: <46099F56.1010100@sonaural.com> Lukas Renggli wrote: >>>> http://cmsbox.netstyle.ch/ seems to exhibit a problem too when it >>>> times out. Although, it looks more like it uses ProxyPass instead >>>> of Rewrite rules. >>>> >>>> >>> Thanks, this is fixed now. >>> >>> No, it uses RewriteRules. It is basically the same setup everywhere. >>> >> Can you tell me how you fixed it. I STILL have the same problems as >> before. I cannot figure i out. >> > > I applied this rewrite rule as the first one: > > RewriteRule ^/seaside/pier(.*)$ http://www.lukas-renggli.ch$1 [R,L] > Thanks Lukas, that seems to work. The difference is the [R] from before to redirecting it back to the domain name once again. Again, thanks! What a headache that was! brad -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From yjgalla at gmx.net Wed Mar 28 14:03:22 2007 From: yjgalla at gmx.net (Elfi Heck) Date: Wed, 28 Mar 2007 14:03:22 +0200 Subject: wikimatrix.org Message-ID: <460A598A.4030105@gmx.net> Just found http://www.wikimatrix.org. I'm wondering why Pier is not listed there. Is there some other reason apart from "no one registered it yet"? Cheers, Elfi From yjgalla at gmx.net Wed Mar 28 14:10:55 2007 From: yjgalla at gmx.net (Elfi Heck) Date: Wed, 28 Mar 2007 14:10:55 +0200 Subject: gmane Message-ID: <460A5B4F.5000901@gmx.net> This list used to be readable via gmane. That stopped in September 2006. Did the list move or something like that? Would it be possible to update the gmane information? Elfi (again) From renggli at iam.unibe.ch Wed Mar 28 14:25:17 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Wed, 28 Mar 2007 14:25:17 +0200 Subject: wikimatrix.org In-Reply-To: <460A598A.4030105@gmx.net> References: <460A598A.4030105@gmx.net> Message-ID: > Just found http://www.wikimatrix.org. I'm wondering why Pier is not > listed there. Is there some other reason apart from "no one registered > it yet"? Because it is more than a Wiki, more like a CMS with full pluggability for Seaside applications ;-) Well, I think it could make sense to add. Do you volunteer? Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Wed Mar 28 14:26:08 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Wed, 28 Mar 2007 14:26:08 +0200 Subject: gmane In-Reply-To: <460A5B4F.5000901@gmx.net> References: <460A5B4F.5000901@gmx.net> Message-ID: <6BF0396A-8235-4F04-BF5A-DBD2C0D3E512@iam.unibe.ch> > This list used to be readable via gmane. That stopped in September > 2006. > Did the list move or something like that? Would it be possible to > update > the gmane information? I don't know. Could it be because we moved the archive somewhere else? How does gmane work? Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From yjgalla at gmx.net Wed Mar 28 15:02:59 2007 From: yjgalla at gmx.net (Elfi Heck) Date: Wed, 28 Mar 2007 15:02:59 +0200 Subject: wikimatrix.org In-Reply-To: References: <460A598A.4030105@gmx.net> Message-ID: <460A6783.5050602@gmx.net> > Because it is more than a Wiki, more like a CMS with full > pluggability for Seaside applications ;-) > I knew that, of course :-) > Well, I think it could make sense to add. Do you volunteer? > I'd say yes, but I'm not sure I really know all features. I am able to answer questions like: "What programming language is it implemented in?", so if you you want me to, I could try to at least enter the basic information there. Elfi From norbert at hartl.name Wed Mar 28 15:08:09 2007 From: norbert at hartl.name (Norbert Hartl) Date: Wed, 28 Mar 2007 15:08:09 +0200 Subject: Empty Magritte Modules Message-ID: <1175087289.32515.26.camel@localhost> All the latest versions of magritte in the Monticello repository seem to be empty. For expample, I downloaded the latest Magritte-Seaside (219) with my web browser from mc.lukas-renggli.ch. The mcz file is 16205 bytes in size. source.st is just 279 bytes. This doesn't seem to be a full release. Norbert From yjgalla at gmx.net Wed Mar 28 15:14:07 2007 From: yjgalla at gmx.net (Elfi Heck) Date: Wed, 28 Mar 2007 15:14:07 +0200 Subject: gmane In-Reply-To: <6BF0396A-8235-4F04-BF5A-DBD2C0D3E512@iam.unibe.ch> References: <460A5B4F.5000901@gmx.net> <6BF0396A-8235-4F04-BF5A-DBD2C0D3E512@iam.unibe.ch> Message-ID: <460A6A1F.3050708@gmx.net> > I don't know. Could it be because we moved the archive somewhere > else? How does gmane work? > I don't know. I'll try to find out. I saw that they have an "edit" link. I'll try if they let anyone update the information, if you have no objections. Elfi From cbeler at enit.fr Wed Mar 28 16:21:48 2007 From: cbeler at enit.fr (=?ISO-8859-1?Q?C=E9drick_B=E9ler?=) Date: Wed, 28 Mar 2007 16:21:48 +0200 Subject: gmane In-Reply-To: <6BF0396A-8235-4F04-BF5A-DBD2C0D3E512@iam.unibe.ch> References: <460A5B4F.5000901@gmx.net> <6BF0396A-8235-4F04-BF5A-DBD2C0D3E512@iam.unibe.ch> Message-ID: <460A79FC.1000107@enit.fr> strange, gmane is working for me... My uni dns wasn't well configured for all squeak related site and lists :( !!! so I used gmane until yesterday and it seems ok... there are today's messages... http://news.gmane.org/gmane.comp.lang.smalltalk.squeak.seaside C?drick Lukas Renggli a ?crit : >> This list used to be readable via gmane. That stopped in September >> 2006. >> Did the list move or something like that? Would it be possible to >> update >> the gmane information? >> > > I don't know. Could it be because we moved the archive somewhere > else? How does gmane work? > > Cheers, > Lukas > > -- */C?drick/**/ B?ler/* */DOCTORANT/* * * *L*aboratoire *G*?nie de *P*roduction - Equipe Production Automatis?e Ecole Nationale d'Ing?nieurs de Tarbes - http://www.enit.fr 47, Avenue d'Azereix - BP 1629 F-65016 TARBES Cedex - FRANCE _Phone:_ (+33) (0)5 62 44 27 00 (poste 28 37) _Fax:_ (+33) (0)5 62 44 27 08 _Mobile:_ (+33) (0)6 81 33 02 04 E-mail: cbeler at enit.fr From yjgalla at gmx.net Wed Mar 28 15:57:56 2007 From: yjgalla at gmx.net (Elfi Heck) Date: Wed, 28 Mar 2007 15:57:56 +0200 Subject: gmane In-Reply-To: <460A79FC.1000107@enit.fr> References: <460A5B4F.5000901@gmx.net> <6BF0396A-8235-4F04-BF5A-DBD2C0D3E512@iam.unibe.ch> <460A79FC.1000107@enit.fr> Message-ID: <460A7464.7010407@gmx.net> > http://news.gmane.org/gmane.comp.lang.smalltalk.squeak.seaside > I don't see any problems with the *seaside* list, either. http://dir.gmane.org/gmane.comp.lang.smalltalk.smallwiki has one message Jan, 26 one message Nov, 11 all other messages are Sep, 17 and before. Elfi From renggli at iam.unibe.ch Wed Mar 28 15:57:32 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Wed, 28 Mar 2007 15:57:32 +0200 Subject: wikimatrix.org In-Reply-To: <460A6783.5050602@gmx.net> References: <460A598A.4030105@gmx.net> <460A6783.5050602@gmx.net> Message-ID: >> Well, I think it could make sense to add. Do you volunteer? > > I'd say yes, but I'm not sure I really know all features. I am able to > answer questions like: "What programming language is it implemented > in?", so if you you want me to, I could try to at least enter the > basic > information there. Ok, enter the basic information and copy the rest into the mailing list so that we can collect all the remaining information together. That's simpler, and more important I don't have to register on that web site ;-) Thanks for your upcoming contribution! Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Wed Mar 28 16:09:48 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Wed, 28 Mar 2007 16:09:48 +0200 Subject: gmane In-Reply-To: <460A6A1F.3050708@gmx.net> References: <460A5B4F.5000901@gmx.net> <6BF0396A-8235-4F04-BF5A-DBD2C0D3E512@iam.unibe.ch> <460A6A1F.3050708@gmx.net> Message-ID: >> I don't know. Could it be because we moved the archive somewhere >> else? How does gmane work? > > I don't know. I'll try to find out. I saw that they have an "edit" > link. > I'll try if they let anyone update the information, if you have no > objections. Sure, please do so. I don't have any idea who installed it in the first place. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Wed Mar 28 16:26:16 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Wed, 28 Mar 2007 16:26:16 +0200 Subject: Empty Magritte Modules In-Reply-To: <1175087289.32515.26.camel@localhost> References: <1175087289.32515.26.camel@localhost> Message-ID: > All the latest versions of magritte in the > Monticello repository seem to be empty. For expample, > I downloaded the latest Magritte-Seaside (219) with my > web browser from mc.lukas-renggli.ch. The mcz file is > 16205 bytes in size. source.st is just 279 bytes. This > doesn't seem to be a full release. Yes, these were some faulty commits that used a different commit strategy in Monticello (diff-commits). These are somehow broken and show up as empty packages, probably a bug in Monticello for Squeak 3.9. I removed them now from the repository. Please clear your cache and try again to load the latest version. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From norbert at hartl.name Wed Mar 28 17:41:55 2007 From: norbert at hartl.name (Norbert Hartl) Date: Wed, 28 Mar 2007 17:41:55 +0200 Subject: Empty Magritte Modules In-Reply-To: References: <1175087289.32515.26.camel@localhost> Message-ID: <1175096515.32515.34.camel@localhost> On Wed, 2007-03-28 at 16:26 +0200, Lukas Renggli wrote: > > All the latest versions of magritte in the > > Monticello repository seem to be empty. For expample, > > I downloaded the latest Magritte-Seaside (219) with my > > web browser from mc.lukas-renggli.ch. The mcz file is > > 16205 bytes in size. source.st is just 279 bytes. This > > doesn't seem to be a full release. > > Yes, these were some faulty commits that used a different commit > strategy in Monticello (diff-commits). These are somehow broken and > show up as empty packages, probably a bug in Monticello for Squeak > 3.9. I removed them now from the repository. Please clear your cache > and try again to load the latest version. > I don't had luck. Magritte-seaside-219 Magritte-Tests-lr.11 Magritte-Model-lr.253 Magritte-Model-lr.254 Magritte-Model-lr.255 are all empty. For now I loaded Maritte-All-lr.204 and this seems to work. Norbert From yjgalla at gmx.net Thu Mar 29 15:09:33 2007 From: yjgalla at gmx.net (Elfi Heck) Date: Thu, 29 Mar 2007 15:09:33 +0200 Subject: wikimatrix.org In-Reply-To: References: <460A598A.4030105@gmx.net> <460A6783.5050602@gmx.net> Message-ID: <460BBA8D.2060201@gmx.net> > Ok, enter the basic information and copy the rest into the mailing > list so that we can collect all the remaining information together. > Pier is now visible on http://www.wikimatrix.org/show/Pier. I've entered some information I gleaned from SqueakMap browser (version/license information), the project page (overview text), the seaside mailing list (webservers) and other sources. If something is wrong, it would be good to tell me ASAP, so I can correct it. Please tell me also about all the missing information. Cheers, Elfi From alexandre.buisson at etu.univ-savoie.fr Fri Mar 30 09:58:16 2007 From: alexandre.buisson at etu.univ-savoie.fr (Alexandre Buisson) Date: Fri, 30 Mar 2007 09:58:16 +0200 Subject: VisualWorks image with Magritte Message-ID: <460CC318.1080801@etu.univ-savoie.fr> Hello, I look for a visualWorks image with Magritte, where can I find one ? thanks for your response.. From philippe.marschall at gmail.com Fri Mar 30 18:38:14 2007 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Fri, 30 Mar 2007 18:38:14 +0200 Subject: wikimatrix.org In-Reply-To: <460BBA8D.2060201@gmx.net> References: <460A598A.4030105@gmx.net> <460A6783.5050602@gmx.net> <460BBA8D.2060201@gmx.net> Message-ID: <66666f210703300938qf5b072t93224ba9db270545@mail.gmail.com> 2007/3/29, Elfi Heck : > > > Ok, enter the basic information and copy the rest into the mailing > > list so that we can collect all the remaining information together. > > > Pier is now visible on http://www.wikimatrix.org/show/Pier. I've entered > some information I gleaned from SqueakMap browser (version/license > information), the project page (overview text), the seaside mailing list > (webservers) and other sources. > If something is wrong, it would be good to tell me ASAP, so I can > correct it. Please tell me also about all the missing information. License Cost/ Fee: free Webserver: (has webserver included, but can be run behind Apache/lighty/whatever) ACL: yes, with Windows Security Host Blocking: yes, with Windows Security Commercial Support: I'm pretty sure netstyle.ch will provide commercial support if asked Issue Tracker: http://bugs.squeak.org/ (I think) Unicode Support: yes Interface Languages: english only InterWiki: yes (I think) Other (data storage): xml, oodb, smalltalk image Themes & Skins: yes (I think) Embedded Video: yes (I think, probably needs testing) Images (syntax): +image+ > Cheers, Elfi > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > From philippe.marschall at gmail.com Fri Mar 30 18:58:09 2007 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Fri, 30 Mar 2007 18:58:09 +0200 Subject: wikimatrix.org In-Reply-To: <460BBA8D.2060201@gmx.net> References: <460A598A.4030105@gmx.net> <460A6783.5050602@gmx.net> <460BBA8D.2060201@gmx.net> Message-ID: <66666f210703300958w4884bd6cm593f8a0fdea94e29@mail.gmail.com> 2007/3/29, Elfi Heck : > > > Ok, enter the basic information and copy the rest into the mailing > > list so that we can collect all the remaining information together. > > > Pier is now visible on http://www.wikimatrix.org/show/Pier. I've entered > some information I gleaned from SqueakMap browser (version/license > information), the project page (overview text), the seaside mailing list > (webservers) and other sources. > If something is wrong, it would be good to tell me ASAP, so I can > correct it. Please tell me also about all the missing information. I just found out that no is an answer too, so Operating System: Windows, MacOS, Linux (maybe Solaris, *BSD and RiscOS, but I don't know about the VM status on these machines) License Cost/ Fee: free Webserver: none needed Datastorage: Text Files: no MySQL: no PostgreSQL: theoricially, probably no is better Oracle: no SQLite: no BerkeleyDB: no RCS: no Other: XML, Magman, Smalltalk image, ReferenceStream, SmartRefernceStream (ImageSegment) ACL: yes, with Windows Security Authentication Backends: no (if I understood correctly) Preconfigured Hosting: no Support Forum: no IRC Channel: no Preview: no Right-to-Left Support: Optional (if I understood correctly) Email notification: no Comments: no Page Redirection: no Conflict Handling: no Namespaces: yes (I think) Math formulas: no Tables: yes (!) CREOLE support: no Markdown Support: no Textile Support: no BBCode Support: no Emoticon Images: no (was in old versions) Syntax Highlighting: no Footnotes: no Section Editing: no Double-Click Edit: no Toolbar: no WYSIWYG Editing: no Access Keys: yes (I think) Auto Signature: no (I think) Raw Export: yes (!) > Cheers, Elfi > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > From renggli at iam.unibe.ch Fri Mar 30 19:31:39 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 30 Mar 2007 19:31:39 +0200 Subject: wikimatrix.org In-Reply-To: <66666f210703300958w4884bd6cm593f8a0fdea94e29@mail.gmail.com> References: <460A598A.4030105@gmx.net> <460A6783.5050602@gmx.net> <460BBA8D.2060201@gmx.net> <66666f210703300958w4884bd6cm593f8a0fdea94e29@mail.gmail.com> Message-ID: Some more comments and a few additions: > Page Redirection: no Yes, you can do this by adding something like into the body of your page: > Conflict Handling: no Yes, Magritte does this. > Namespaces: yes (I think) Yes, definitely. > Section Editing: no > Double-Click Edit: no That was also possible some time ago. Should be easy to add if somebody wants this. > Access Keys: yes (I think) Yes. > CREOLE support: no I think it would be cool if somebody implemented that. It is sort of a standard nowadays. > Issue Tracker: http://bugs.squeak.org/ (I think) Yes. > InterWiki: yes (I think) I don't think so. > Themes & Skins: yes (I think) Yes, but unfortunately there are no other choices available. It would be cool if different skins could be included with the distribution. I would also like to have to ugly header table to be removed (I don't use it in my personal website) ;-) > Embedded Video: yes (I think, probably needs testing) Yes, it works. > Images (syntax): +image+ Monospace Format: = Monospace Text 1 = Monospace Text 2 or via html



Strikethrough Format: via html 

Superscript Format: via html ^{Subscript Format: via html _{Aligning Text: via html 

Text Indentation: via html 

Definition Lists: via html 


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



From yjgalla at gmx.net  Fri Mar 30 19:50:50 2007
From: yjgalla at gmx.net (Elfi Heck)
Date: Fri, 30 Mar 2007 19:50:50 +0200
Subject: wikimatrix.org
In-Reply-To: <66666f210703300958w4884bd6cm593f8a0fdea94e29@mail.gmail.com>
References: <460A598A.4030105@gmx.net>		<460A6783.5050602@gmx.net>		<460BBA8D.2060201@gmx.net>
	<66666f210703300958w4884bd6cm593f8a0fdea94e29@mail.gmail.com>
Message-ID: <460D4DFA.6060501@gmx.net>

OK, I've entered your information with the following changes:
> I just found out that no is an answer too, so
>   
The possible answers for many of the fields are No, Yes, Optional, 
Plugin, Patch
> Operating System: Windows, MacOS, Linux (maybe Solaris, *BSD and
> RiscOS, but I don't know about the VM status on these machines)
>   
I put "anything Squeak runs on" in because the comparison views will 
look awful when the text is too long
> Webserver: none needed
>   
I've kept my entry, because that's what "standalone" means, and you have 
yet to convince me that it doesn't run with the other two :-)
> PostgreSQL: theoricially, probably no is better
>   
I put in "no"
> ACL: yes, with Windows Security
>   
There's only Yes, No, Unknown available, so I chose "Yes"
> Authentication Backends: no (if I understood correctly)
>   
> ...
> Support Forum: no
> IRC Channel: no
>   
These are free text fields so I'm simply leaving them empty
> Conflict Handling: no
>   
I've kept Unknown for now because Lukas says "Yes", but the available 
options are None, Conflict Detection, Page Locking, Conflict Resolution
> Namespaces: yes (I think)
>   
"Yes", it is then
> Tables: yes (!)
>   
The choices are simple, complex, simple + complex. I put simple because 
I don't know what their meaning of complex is .
> Double-Click Edit: no
>   
After reading Lukas' mail I put in "Patch"

The information icons to the right of each field point to a wiki page 
where it's possible to give some details. I'll try to add additional 
information given here to these pages.

I hope I didn't miss anything,
Elfi



From yjgalla at gmx.net  Fri Mar 30 20:00:07 2007
From: yjgalla at gmx.net (Elfi Heck)
Date: Fri, 30 Mar 2007 20:00:07 +0200
Subject: wikimatrix.org
In-Reply-To: 
References: <460A598A.4030105@gmx.net>		<460A6783.5050602@gmx.net>		<460BBA8D.2060201@gmx.net>	<66666f210703300958w4884bd6cm593f8a0fdea94e29@mail.gmail.com>
	
Message-ID: <460D5027.6000100@gmx.net>


> Yes, you can do this by adding something like into the body of your  
> page:
>
> 
>   
I thought this would be something to add to the information page, so 
there it is now.
>> Conflict Handling: no
>>     
>
> Yes, Magritte does this.
>   
See my answer to Philippe. "Yes" is not an available choice (they are 
Conflict detection, Page locking, Conflict resolution)
>> CREOLE support: no
>>     
>
> I think it would be cool if somebody implemented that. It is sort of  
> a standard nowadays.
>   
I also put this in an information page.

Cheers, Elfi

From yjgalla at gmx.net  Fri Mar 30 20:19:02 2007
From: yjgalla at gmx.net (Elfi Heck)
Date: Fri, 30 Mar 2007 20:19:02 +0200
Subject: wikimatrix.org
In-Reply-To: <66666f210703300938qf5b072t93224ba9db270545@mail.gmail.com>
References: <460A598A.4030105@gmx.net>		<460A6783.5050602@gmx.net>		<460BBA8D.2060201@gmx.net>
	<66666f210703300938qf5b072t93224ba9db270545@mail.gmail.com>
Message-ID: <460D5496.3000102@gmx.net>


> Images (syntax): +image+
>   
Oh, and I didn't understand this. Putting +whatever+ in a page gives me 
a regular link to "whatever" I think they meant an image shown directly 
on the page.

Elfi

From philippe.marschall at gmail.com  Fri Mar 30 20:35:33 2007
From: philippe.marschall at gmail.com (Philippe Marschall)
Date: Fri, 30 Mar 2007 20:35:33 +0200
Subject: wikimatrix.org
In-Reply-To: <460D4DFA.6060501@gmx.net>
References: <460A598A.4030105@gmx.net>
	
	<460A6783.5050602@gmx.net>
	
	<460BBA8D.2060201@gmx.net>
	<66666f210703300958w4884bd6cm593f8a0fdea94e29@mail.gmail.com>
	<460D4DFA.6060501@gmx.net>
Message-ID: <66666f210703301135of189667ga5fd35b3d9e71fed@mail.gmail.com>

2007/3/30, Elfi Heck :
> OK, I've entered your information with the following changes:
> > I just found out that no is an answer too, so
> >
> The possible answers for many of the fields are No, Yes, Optional,
> Plugin, Patch
> > Operating System: Windows, MacOS, Linux (maybe Solaris, *BSD and
> > RiscOS, but I don't know about the VM status on these machines)
> >
> I put "anything Squeak runs on" in because the comparison views will
> look awful when the text is too long
> > Webserver: none needed
> >
> I've kept my entry, because that's what "standalone" means, and you have
> yet to convince me that it doesn't run with the other two :-)
> > PostgreSQL: theoricially, probably no is better
> >
> I put in "no"
> > ACL: yes, with Windows Security
> >
> There's only Yes, No, Unknown available, so I chose "Yes"
> > Authentication Backends: no (if I understood correctly)
> >
> > ...
> > Support Forum: no
> > IRC Channel: no
> >
> These are free text fields so I'm simply leaving them empty
> > Conflict Handling: no
> >
> I've kept Unknown for now because Lukas says "Yes", but the available
> options are None, Conflict Detection, Page Locking, Conflict Resolution

Conflict Detection, unless I missed something

> > Namespaces: yes (I think)
> >
> "Yes", it is then
> > Tables: yes (!)
> >
> The choices are simple, complex, simple + complex. I put simple because
> I don't know what their meaning of complex is .

Yes simple is probably right. For example it is not where DocuWiki ist.

> > Double-Click Edit: no
> >
> After reading Lukas' mail I put in "Patch"
>
> The information icons to the right of each field point to a wiki page
> where it's possible to give some details. I'll try to add additional
> information given here to these pages.
>
> I hope I didn't miss anything,
> Elfi
>
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

From philippe.marschall at gmail.com  Fri Mar 30 20:38:59 2007
From: philippe.marschall at gmail.com (Philippe Marschall)
Date: Fri, 30 Mar 2007 20:38:59 +0200
Subject: wikimatrix.org
In-Reply-To: 
References: <460A598A.4030105@gmx.net>
	
	<460A6783.5050602@gmx.net>
	
	<460BBA8D.2060201@gmx.net>
	<66666f210703300958w4884bd6cm593f8a0fdea94e29@mail.gmail.com>
	
Message-ID: <66666f210703301138h30225175h20ca9d99db476dfa@mail.gmail.com>

2007/3/30, Lukas Renggli :
> Some more comments and a few additions:
>
> > Page Redirection: no
>
> Yes, you can do this by adding something like into the body of your
> page:
>
> 

Don't they mean something like in Wikipedia where some pages are just synonyms.
For example:
http://en.wikipedia.org/wiki/Gemstone_Systems

> > Conflict Handling: no
>
> Yes, Magritte does this.
>
> > Namespaces: yes (I think)
>
> Yes, definitely.
>
> > Section Editing: no
> > Double-Click Edit: no
>
> That was also possible some time ago. Should be easy to add if
> somebody wants this.
>
> > Access Keys: yes (I think)
>
> Yes.
>
> > CREOLE support: no
>
> I think it would be cool if somebody implemented that. It is sort of
> a standard nowadays.
>
> > Issue Tracker: http://bugs.squeak.org/ (I think)
>
> Yes.
>
> > InterWiki: yes (I think)
>
> I don't think so.
>
> > Themes & Skins: yes (I think)
>
> Yes, but unfortunately there are no other choices available. It would
> be cool if different skins could be included with the distribution. I
> would also like to have to ugly header table to be removed (I don't
> use it in my personal website) ;-)
>
> > Embedded Video: yes (I think, probably needs testing)
>
> Yes, it works.
>
> > Images (syntax): +image+
>
> Monospace Format:
>
> = Monospace Text 1
> = Monospace Text 2
>
> or via html 
>
> Strikethrough Format: via html 
>
> Superscript Format: via html ^{>
> Subscript Format: via html _{>
> Aligning Text: via html 
>
> Text Indentation: via html 
>
> Definition Lists: via html 
>
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
>
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

From renggli at iam.unibe.ch  Fri Mar 30 21:36:26 2007
From: renggli at iam.unibe.ch (Lukas Renggli)
Date: Fri, 30 Mar 2007 21:36:26 +0200
Subject: wikimatrix.org
In-Reply-To: <460D5027.6000100@gmx.net>
References: <460A598A.4030105@gmx.net>		<460A6783.5050602@gmx.net>		<460BBA8D.2060201@gmx.net>	<66666f210703300958w4884bd6cm593f8a0fdea94e29@mail.gmail.com>
	
	<460D5027.6000100@gmx.net>
Message-ID: 

>>> Conflict Handling: no
>>>
>>
>> Yes, Magritte does this.
>>
> See my answer to Philippe. "Yes" is not an available choice (they are
> Conflict detection, Page locking, Conflict resolution)

Magritte provides conflict detection and conflict resolution.

Cheers,
Lukas

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



From keith_hodges at yahoo.co.uk  Sat Mar 31 01:50:09 2007
From: keith_hodges at yahoo.co.uk (Keith Hodges)
Date: Sat, 31 Mar 2007 00:50:09 +0100
Subject: wikimatrix.org
In-Reply-To: <460D5496.3000102@gmx.net>
References: <460A598A.4030105@gmx.net>		<460A6783.5050602@gmx.net>		<460BBA8D.2060201@gmx.net>	<66666f210703300938qf5b072t93224ba9db270545@mail.gmail.com>
	<460D5496.3000102@gmx.net>
Message-ID: <460DA231.1010403@yahoo.co.uk>

Elfi Heck wrote:
>> Images (syntax): +image+
>>   
>>     
> Oh, and I didn't understand this. Putting +whatever+ in a page gives me 
> a regular link to "whatever" I think they meant an image shown directly 
> on the page.
>
> Elfi
>   
Dear Elfi,

*whatever* is for linking, +whatever+ is for embedding, if 'whatever' 
exists and is an image it will display in the page.

best regards

Keith

From norbert at hartl.name  Sat Mar 31 12:32:23 2007
From: norbert at hartl.name (Norbert Hartl)
Date: Sat, 31 Mar 2007 12:32:23 +0200
Subject: Magritte usage pattern
Message-ID: <1175337143.21739.54.camel@localhost>

Hi,

I'm dealing now quite a bit of time with Magritte to do a 
web application. It took a while to get into Magritte and 
I'm not sure how much I've grasped til now. But I'm quite
impressed by the power of Magritte. It seems to be customiz-
able at the right places which distinguishes it from others. 
At the moment I'm refactoring the code I hacked the last weeks.
I have a few questions about best practice patterns using
Magritte. For the demo, you have a model and you just need
any component, the case is quite easy. aModel asComponent 
will do. But most of the tasks that have to be done for a
web application aren't that trivial. You need to have a 
customized layout (which can be very complex), you need your
own components etc. 

For customization I put every little bit in a wrapper class
around the generated Magritte component. This is for customizing
the generated component as well as to do some manual html if
it isn't avoidable. I have the feeling that this is not the
right way to do but I have no better idea. To minimize the effort
to do a component for a model component I've built a base class
which should ease the customization of the component. The parameters
for the base component are:

- descriptionSelector
  This is a symbol which is invoke on the model if you need a subset
  of the descriptions. The default value is #description

- componentRenderer
  The visitor which is used to render the component

- buttons
  A Collection of Associations (button label -> selector). MAForm-
  Decoration is only useful if you have save and cancel buttons. As the
  selectors are performed on the MAContainerComponent there is no way of
  extending it. I extendend MAFormDecoration to have associations for 
  buttons (to distinguish the button label and the selector to use) and
  to be created with a delegator. The selector is than performed on the 
  delegate which leads to a usage form 
  
  component addDecoration: 
         (WHFormDecoration delegate: self) 
         buttons: #( #ok -> commit. #abbrechen -> abort)

- validation
  There are three choices: 
  * no validation
  * validation by MAValidationDecoration (or similar)
    I must confess that I never understood processChildCallbacks. 
  * manual validation and error handling
    Using the form 
       [self component validate]
          on: MAError
          do: [:anException | self exception: anException].

- answering
  Having a wrapper component I need to process answer in the wrapper.
  This can be customized by defining answerBlock. Default value is 
     self component onAnswer: (
        answerBlock ifNil: [
           [:anAnswer | self answer: anAnswer]
	]
     )

- readonly/readwrite
  I'm mimicking the behaviour in MAElementComponent having
  renderViewerOn:/renderEditorOn:. This is a good way to switch a
  component between readonly and readwrite mode. In my case the layout
  of the component is completely different between those two modes. So
  I use two different renderers for readonly and for readwrite mode.

- really complex layout cases
  I have one case where it is necessary to put css classes to some of
  the components of a form. The best way I found so far (being dirty)
  is to use propertyAt:put: at description level and use this in a
  specialized renderer

So far so good. I like to hear your oppions and experiences doing this
kind of stuff. 

Another problem I have no solution til now is the mixture of models into
one component. Sometimes you build your data model and then page layout
forces you to edit two objects at the same time. I have no problem to
mix descriptions in a desired way. But by invoking asComponentOn: they
would have all the same model which is wrong for a subset of the
descriptions. Is there any clever way to mix descriptions, set the model
accordingly and then produce the component?

thanks in advance,

Norbert



From akuhn at gmx.ch  Sat Mar 31 16:25:33 2007
From: akuhn at gmx.ch (Adrian Kuhn)
Date: Sat, 31 Mar 2007 16:25:33 +0200
Subject: How to add a Smallwiki stylesheet as one of the defaults?
Message-ID: 

Hi Lukas,
Smallwiki rocks! I made a custom stylesheet for Smallwiki, how can I  
add it to the list of defaults?

My stylesheet is called "The Pixel is Dead" and can adapt to any user- 
given font-size in the browser. for an example see http:// 
smallwiki.unibe.ch/moose/

cheers,
AA

From renggli at iam.unibe.ch  Sat Mar 31 19:54:21 2007
From: renggli at iam.unibe.ch (Lukas Renggli)
Date: Sat, 31 Mar 2007 19:54:21 +0200
Subject: How to add a Smallwiki stylesheet as one of the defaults?
In-Reply-To: 
References: 
Message-ID: <5A8C85FE-7127-4BEB-98A4-FCF9761E756A@iam.unibe.ch>

Hi Adrian,

> Smallwiki rocks! I made a custom stylesheet for Smallwiki, how can  
> I add it to the list of defaults?

thanks for the comment.

The list of available styles is defined in the file . If you log-in to  
kilana.unibe.ch you can directly append your style there and it  
should show up on all SmallWiki instances. I don't exactly recall the  
whole implementation, but I think it works like this ...

> My stylesheet is called "The Pixel is Dead" and can adapt to any  
> user-given font-size in the browser. for an example see http:// 
> smallwiki.unibe.ch/moose/

It's a great style, we should probably make it the default SCG style.

I also noticed that you reorganized the front page. It looks much  
better like this.

Cheers,
Lukas

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



From renggli at iam.unibe.ch  Sat Mar 31 20:07:01 2007
From: renggli at iam.unibe.ch (Lukas Renggli)
Date: Sat, 31 Mar 2007 20:07:01 +0200
Subject: Magritte usage pattern
In-Reply-To: <1175337143.21739.54.camel@localhost>
References: <1175337143.21739.54.camel@localhost>
Message-ID: 

Hi Norbert,

> For customization I put every little bit in a wrapper class
> around the generated Magritte component. This is for customizing
> the generated component as well as to do some manual html if
> it isn't avoidable. I have the feeling that this is not the
> right way to do but I have no better idea. To minimize the effort
> to do a component for a model component I've built a base class
> which should ease the customization of the component.

are your convenience classes available somewhere? I think that many  
people could profit from these extensions and they could maybe even  
be integrated somehow into the core package?

> - really complex layout cases
>   I have one case where it is necessary to put css classes to some of
>   the components of a form. The best way I found so far (being dirty)
>   is to use propertyAt:put: at description level and use this in a
>   specialized renderer

You could use #attributes of the descriptions:

	aDescription attributes class: 'foo'

> So far so good. I like to hear your oppions and experiences doing this
> kind of stuff.

Your approach sounds fine to me, I also found myself doing similar  
things.

> Another problem I have no solution til now is the mixture of models  
> into
> one component. Sometimes you build your data model and then page  
> layout
> forces you to edit two objects at the same time. I have no problem to
> mix descriptions in a desired way. But by invoking asComponentOn: they
> would have all the same model which is wrong for a subset of the
> descriptions. Is there any clever way to mix descriptions, set the  
> model
> accordingly and then produce the component?

Indeed you can do that by modifying the accessors of the descriptions  
of referenced objects. I am copying an example from an earlier post  
to this mailing list, where #billingAddress and #shippingAddress are  
weaved into the description of anOrder:

composedDescription := anOrder description copy
     addAll: (anOrder billingAddress description collect: [ :each |
         each copy accessor: (MACascadeAccessor
             accessor: (MASelectorAccessor selector: #billingAddress)
             next: each accessor) ]);
     addAll: (anOrder shippingAddress description collect: [ :each |
         each copy accessor: (MACascadeAccessor
             accessor: (MASelectorAccessor selector: #shippingAddress)
             next: each accessor) ]);
     asComponentOn: anOrder

This looks terribly complicated, but with a simple helper function it  
could made look much simpler.

Cheers,
Lukas

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



From norbert at hartl.name  Sat Mar 31 20:43:47 2007
From: norbert at hartl.name (Norbert Hartl)
Date: Sat, 31 Mar 2007 20:43:47 +0200
Subject: Magritte usage pattern
In-Reply-To: 
References: <1175337143.21739.54.camel@localhost>
	
Message-ID: <1175366627.21739.75.camel@localhost>

On Sat, 2007-03-31 at 20:07 +0200, Lukas Renggli wrote:
> Hi Norbert,
> 
> > For customization I put every little bit in a wrapper class
> > around the generated Magritte component. This is for customizing
> > the generated component as well as to do some manual html if
> > it isn't avoidable. I have the feeling that this is not the
> > right way to do but I have no better idea. To minimize the effort
> > to do a component for a model component I've built a base class
> > which should ease the customization of the component.
> 
> are your convenience classes available somewhere? I think that many  
> people could profit from these extensions and they could maybe even  
> be integrated somehow into the core package?
> 
You are right. I will finish them a little and post them here.

> > - really complex layout cases
> >   I have one case where it is necessary to put css classes to some of
> >   the components of a form. The best way I found so far (being dirty)
> >   is to use propertyAt:put: at description level and use this in a
> >   specialized renderer
> 
> You could use #attributes of the descriptions:
> 
> 	aDescription attributes class: 'foo'
> 
Oh, I should have found that :) Looks much better.

> > So far so good. I like to hear your oppions and experiences doing this
> > kind of stuff.
> 
> Your approach sounds fine to me, I also found myself doing similar  
> things.
> 
> > Another problem I have no solution til now is the mixture of models  
> > into
> > one component. Sometimes you build your data model and then page  
> > layout
> > forces you to edit two objects at the same time. I have no problem to
> > mix descriptions in a desired way. But by invoking asComponentOn: they
> > would have all the same model which is wrong for a subset of the
> > descriptions. Is there any clever way to mix descriptions, set the  
> > model
> > accordingly and then produce the component?
> 
> Indeed you can do that by modifying the accessors of the descriptions  
> of referenced objects. I am copying an example from an earlier post  
> to this mailing list, where #billingAddress and #shippingAddress are  
> weaved into the description of anOrder:
> 
> composedDescription := anOrder description copy
>      addAll: (anOrder billingAddress description collect: [ :each |
>          each copy accessor: (MACascadeAccessor
>              accessor: (MASelectorAccessor selector: #billingAddress)
>              next: each accessor) ]);
>      addAll: (anOrder shippingAddress description collect: [ :each |
>          each copy accessor: (MACascadeAccessor
>              accessor: (MASelectorAccessor selector: #shippingAddress)
>              next: each accessor) ]);
>      asComponentOn: anOrder
> 
Ok, I only imagined to carry more than one model. But to chain selector
invocation is much more clever. It will only work if the objects related
directly but I doubt you need to combine model objects often when they
are not related directly.

For further assistance please remember that you renamed
MACascadeAccessor to MAChainAccessor :) It was in Magritte-Model-206 ;)

> This looks terribly complicated, but with a simple helper function it  
> could made look much simpler.

I didn't try it but it looks not too complicated. 

thanks very much,

Norbert}}}}