From renggli at iam.unibe.ch Sat Apr 1 09:26:57 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sat, 1 Apr 2006 09:26:57 +0200 Subject: "pretty" urls for links to internal pages? In-Reply-To: <59853.137.131.108.119.1143838288.squirrel@webmail.tuffmail.net> References: <59853.137.131.108.119.1143838288.squirrel@webmail.tuffmail.net> Message-ID: <20BE9B07-AA76-43E9-B27D-1599DD50ECE8@iam.unibe.ch> Hi, > I'm new to smalltalk, seaside and pier. I want to use pier to host > a small > site, and if possible, I'd like to change the way internal links to > other > pages are rendered, so that the wiki text: > > *Introduction>introduction* > > produces the link: > http://localhost:9090/seaside/pier/information/introduction > > instead of: > http://localhost:9090/seaside/pier/information/introduction? > view=PRDefaultView&command=PRViewCommand&_k=jFcQckKB&25&_s=lEBbpcqiBRM > HlTFF this is simple to do, have a look #goto: in WAAnchorTag. However I strongly discourage you doing this, since ... - it will start a new session every time you click a link. - you will loose all the state of your application when clicking a link, e.g. most widgets won't work anymore. - waste a lot of memory and cpu-time on the server, because the url has to be parsed and all Seaside components have to be rebuild and reinitialized on every click. > Both links return the same URL when typed into the browser, so clearly > view is the default command. I've tried searching around for > information > about this but I couldn't find anything obvious to me. While > browsing the > source code, I came across WAUrl adaptToContext: and WAAnchorTag > goto:, > which look potentially relevant, but I'm honestly not sure if I'm > on the > right track. I'd appreciate it if someone could point me in the right > direction. Also, if this is a really bad idea for some reason, that > would > also be good to know. Yes, these two methods [1,2] are definitely the ones your are interested in. Let me try to explain the background of these methods: Seaside only parses the URL on the first request, else it will only perform the callback (as defined in [1] by #registerActionCallback:) and ignore all the rest. So why the heck I am doing so many thing with the generated URL, if Seaside is not using it at all? It basically makes it possible to preserve some state when bookmarking the URL, when opening the URL within a new window, or when sending it to friends. If the argument '_s' (Session) is invalid (mostly because of a timeout, or maybe because of a session-protector), Pier will try to restore the state from the URL and bring back the user at the right place. To conclude, you cannot shorten the URL in the anchors without scarifying functionality. That's life, Lukas [1] WAAnchorTag>>goto: aContext "Initialize the receiver to properly activate aContext when being clicked. This includes a callback and a human-readable and bookmarkable url." | actionUrl | aContext isValid ifFalse: [ ^ self class: 'protected'; url: '#' ]. actionUrl := canvas context actionUrl withParameter: (canvas callbacks registerActionCallback: [ PRCurrentContext value: aContext ]). self url: (actionUrl adaptToContext: aContext) displayString [2] WAUrl>>adaptToContext: aContext path := aContext session application baseUrl path copy. aContext structure parents allButFirst do: [ :each | self path add: each name ]. aContext command isView ifTrue: [ self addParameter: 'view' value: aContext command viewComponentClass name asString ]. self addParameter: 'command' value: aContext command class name asString -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Sat Apr 1 09:27:53 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sat, 1 Apr 2006 09:27:53 +0200 Subject: "pretty" urls for links to internal pages? In-Reply-To: <59853.137.131.108.119.1143838288.squirrel@webmail.tuffmail.net> References: <59853.137.131.108.119.1143838288.squirrel@webmail.tuffmail.net> Message-ID: <56134A70-A28A-4805-BD00-65647AD940BD@iam.unibe.ch> On 31 Mar 2006, at 22:51, Brian Chapados wrote: > Hi, > > I'm new to smalltalk, seaside and pier. I want to use pier to host > a small > site, and if possible, I'd like to change the way internal links to > other > pages are rendered, so that the wiki text: > > *Introduction>introduction* > > produces the link: > http://localhost:9090/seaside/pier/information/introduction > > instead of: > http://localhost:9090/seaside/pier/information/introduction? > view=PRDefaultView&command=PRViewCommand&_k=jFcQckKB&25&_s=lEBbpcqiBRM > HlTFF > > Both links return the same URL when typed into the browser, so clearly > view is the default command. I've tried searching around for > information > about this but I couldn't find anything obvious to me. While > browsing the > source code, I came across WAUrl adaptToContext: and WAAnchorTag > goto:, > which look potentially relevant, but I'm honestly not sure if I'm > on the > right track. I'd appreciate it if someone could point me in the right > direction. Also, if this is a really bad idea for some reason, that > would > also be good to know. > > I'm using Sqeak-3.8, Seaside 2.63a3-lr.51 and Pier-all-lr.81 > > Thanks, > > Brian > > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- Lukas Renggli http://www.lukas-renggli.ch From frank.urbach at schmees.com Mon Apr 3 15:17:56 2006 From: frank.urbach at schmees.com (Frank Urbach) Date: Mon, 3 Apr 2006 13:17:56 +0000 Subject: Tabs for pier Message-ID: Hi all, I want to indent some parts of text in pier. But I didn't see in the syntax-introduction these things. Can anybody advise me for this. Thanks in advance. Cheers, Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20060403/279c04e1/attachment.html From renggli at iam.unibe.ch Mon Apr 3 18:58:30 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 3 Apr 2006 18:58:30 +0200 Subject: Tabs for pier In-Reply-To: References: Message-ID: <8FCBF998-58CE-4C13-9E43-3A326E66EFE8@iam.unibe.ch> > I want to indent some parts of text in pier. But I didn't see in > the syntax-introduction these things. Can anybody advise me for this. > Thanks in advance. You could use HTML, something like:
Indented Text
Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Wed Apr 5 13:18:42 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Wed, 5 Apr 2006 13:18:42 +0200 Subject: Re-2: Tabs for pier In-Reply-To: References: Message-ID: <29B3AC39-A3FA-49CE-A3BD-F133D0688EA7@iam.unibe.ch> Hi Frank, > With some easy things in css I was able to realize what I want in > HTML. But what do you think about syntax extension of pier to do > such things like > :indented_text. > I found this behavior in another wiki and it helps for readability > of the text. > Sure I can use HTML but writing of such things written above is > much easier. I tried to keep the syntax as simple as possible. However there were several requests lately for that kind of things. I don't really know, how we could implement that the simplest without bloating the wiki- syntax and while keeping the visitors small that transform the AST into different output-formats (HTML, Text, Latex, etc). The best idea I cam up so far is to add some sort of XML-Tags that can be parsed in a generic fashion, so that extensions can register their own tags. Something along ... The time is now: Time now Would that help? Is something like that of generic interest? > I've been searching in the code for the place of translation from > *..* and others to HTML and coming down to PRDocumentScanner > scanForToken and see the scannerDefinitionComment on class-side. > The next step to define a new element would be very interesting. The scanner and parser is automatically generated from the respective definitions using SmaCC, so you probably don't want to change these methods manually ;-) If you only want to do some simple string transformations when generating HTML you could simply patch the methods from the protocol #visiting-document in the class PRViewRenderer. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From frank.urbach at schmees.com Wed Apr 5 16:05:13 2006 From: frank.urbach at schmees.com (Frank Urbach) Date: Wed, 5 Apr 2006 14:05:13 +0000 Subject: Re-4: Tabs for pier Message-ID: Hi, Lukas! I can understand that a simple syntax keep it easy writing some content. My intention was keeping fingertips writing my ideas in the wiki. On the other side the idea using some sort of XML-tags bring us the possibility write some extensions like a building set. I'm not so familiar with XML but in my understanding of this we could bring the translation to other formats into the tags. With an open repository of these buildingblocks everybody can decide what he want. The loosers in this kind of solution are my fingers ;-). > > Sure I can use HTML but writing of such things written above is > > much easier. > > I tried to keep the syntax as simple as possible. However there were > several requests lately for that kind of things. I don't really know, > how we could implement that the simplest without bloating the wiki- > syntax and while keeping the visitors small that transform the AST > into different output-formats (HTML, Text, Latex, etc). > > The best idea I cam up so far is to add some sort of XML-Tags that > can be parsed in a generic fashion, so that extensions can register > their own tags. Something along ... > > > The time is now: Time now > > > Would that help? Is something like that of generic interest? > > > I've been searching in the code for the place of translation from > > *..* and others to HTML and coming down to PRDocumentScanner > > scanForToken and see the scannerDefinitionComment on class-side. > > The next step to define a new element would be very interesting. > > The scanner and parser is automatically generated from the respective > definitions using SmaCC, so you probably don't want to change these > methods manually ;-) My mistake. Is it possible to add a comment "Do not touch, it's generated"? Cheers, Frank > If you only want to do some simple string transformations when > generating HTML you could simply patch the methods from the protocol > #visiting-document in the class PRViewRenderer. > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > > From philippe.marschall at gmail.com Wed Apr 5 16:50:53 2006 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Wed, 5 Apr 2006 16:50:53 +0200 Subject: Re-2: Tabs for pier In-Reply-To: <29B3AC39-A3FA-49CE-A3BD-F133D0688EA7@iam.unibe.ch> References: <29B3AC39-A3FA-49CE-A3BD-F133D0688EA7@iam.unibe.ch> Message-ID: <66666f210604050750p5c5d6cffka49b8637645c487b@mail.gmail.com> > I tried to keep the syntax as simple as possible. However there were > several requests lately for that kind of things. I don't really know, > how we could implement that the simplest without bloating the wiki- > syntax and while keeping the visitors small that transform the AST > into different output-formats (HTML, Text, Latex, etc). > > The best idea I cam up so far is to add some sort of XML-Tags that > can be parsed in a generic fashion, so that extensions can register > their own tags. Something along ... > > > The time is now: Time now > > > Would that help? Is something like that of generic interest? I like the idea of having the possibility to hook into the document model without having to change the syntax/scanner/parser. Only this makes it possible to combine several of these exentions. Dokuwiki uses a very similar model for it's plugins: http://wiki.splitbrain.org/wiki%3Aplugins I understand you want to keep the syntax as simple as possible but still to differ extensions (or pulgings or whatever we will call them) from normal XML markup I'd like to have a different syntax. Eg: [indented] The time is now: [smalltalk]Time now[/smalltalk] [/indented] They would be parsed into an ExtensionNode or whatever. You could also search the subclasses for the one with the correct tag (eg: "indented") and instantiate this one directly instead of the superclass (ExtensionNode). Cheers Philippe From renggli at iam.unibe.ch Sun Apr 9 23:27:51 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 9 Apr 2006 23:27:51 +0200 Subject: Magritte Load Problem Message-ID: Some people reported problems loading the latest version of Magritte. I renamed a class that registered for system-change notifications and during the load-operation of Monticello it points to an obsolete class making it impossible to compile any method in the system. To solve the problem simply evaluate the expression below, before loading a recent version of Magritte: MABuilder allSubInstancesDo: [ :each | SystemChangeNotifier uniqueInstance noMoreNotificationsFor: each ]. Smalltalk garbageCollect. Sorry for the inconveniance! Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From chad at clearwaterassociates.ca Tue Apr 11 01:10:51 2006 From: chad at clearwaterassociates.ca (Chad Nantais) Date: Mon, 10 Apr 2006 19:10:51 -0400 Subject: Button text in forms Message-ID: <3de931600604101610lefac3bbvb379719d146de16a@mail.gmail.com> When I am rendering a model using "MYQueryModel new asComponent", I want the text on the Magritte-generated form's 'Save' button to read something else like 'Search'. How do I do this, if it is even possible. I am trying to use descriptions for a query object and want the same action as the default 'Save' (to answer the object) , but having a button with that label will confuse users. Thanks in advance. Chad -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20060411/e4eaf87e/attachment.html From renggli at iam.unibe.ch Tue Apr 11 06:52:14 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 11 Apr 2006 06:52:14 +0200 Subject: Button text in forms In-Reply-To: <3de931600604101610lefac3bbvb379719d146de16a@mail.gmail.com> References: <3de931600604101610lefac3bbvb379719d146de16a@mail.gmail.com> Message-ID: <8EC46415-22DF-44DB-BF28-D47A1D17F4B4@iam.unibe.ch> > When I am rendering a model using "MYQueryModel new asComponent", I > want the text on the Magritte-generated form's 'Save' button to > read something else like 'Search'. How do I do this, if it is even > possible. I am trying to use descriptions for a query object and > want the same action as the default 'Save' (to answer the object) , > but having a button with that label will confuse users. So I suppose that MYQueryModel is a subclass of PRCommand, right? If this is the case you should override #asComponent, else I don't quite understand your question. PRComponent>>asComponent ^ super asComponent addValidatedForm; yourself MYQueryModel>>asComponent ^ (self description asComponentOn: self) addValidatedForm: #( search ); yourself Don't forget to add #search as an extension method to MAContainerComponent. Cheers, Luakas -- Lukas Renggli http://www.lukas-renggli.ch From chad at clearwaterassociates.ca Tue Apr 11 16:25:40 2006 From: chad at clearwaterassociates.ca (Chad Nantais) Date: Tue, 11 Apr 2006 10:25:40 -0400 Subject: Button text in forms In-Reply-To: <8EC46415-22DF-44DB-BF28-D47A1D17F4B4@iam.unibe.ch> References: <3de931600604101610lefac3bbvb379719d146de16a@mail.gmail.com> <8EC46415-22DF-44DB-BF28-D47A1D17F4B4@iam.unibe.ch> Message-ID: <3de931600604110725n76490e4dib178e2e8bbbcc64e@mail.gmail.com> Lukas, Sorry for not explaining that I am using Magritte alone, without Pier. I will add #search as an extension method to MAContainerComponent. Thanks for you help, Chad On 4/11/06, Lukas Renggli wrote: > > When I am rendering a model using "MYQueryModel new asComponent", I > > want the text on the Magritte-generated form's 'Save' button to > > read something else like 'Search'. How do I do this, if it is even > > possible. I am trying to use descriptions for a query object and > > want the same action as the default 'Save' (to answer the object) , > > but having a button with that label will confuse users. > > So I suppose that MYQueryModel is a subclass of PRCommand, right? If > this is the case you should override #asComponent, else I don't quite > understand your question. > > PRComponent>>asComponent > ^ super asComponent > addValidatedForm; > yourself > > MYQueryModel>>asComponent > ^ (self description asComponentOn: self) > addValidatedForm: #( search ); > yourself > > Don't forget to add #search as an extension method to > MAContainerComponent. > > Cheers, > Luakas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > From damien.cassou at laposte.net Wed Apr 12 08:01:54 2006 From: damien.cassou at laposte.net (Damien Cassou) Date: Wed, 12 Apr 2006 08:01:54 +0200 Subject: [Magritte] OneToManyRelation and Reports Message-ID: <443C97D2.4060600@laposte.net> Hi, I would like to know why OneToManyRelations are not as configurable as MultipleOptionDescriptions. It would be cool to get #beSortable, #beOrdered, #beRemoveable... Is it just a problem of time or something difficult to implement ? If you take the Magritte exercices, a person manager is developed. The problem is: why is the PersonManager a WAComponent ? Won't it be more interesting if we get a Model and not a component ? The model would have just one description ; something like: descriptionPersons ^ (MAOneToManyRelationDescription auto: 'persons' label: 'Persons') classes: (Array with: MAPersonModel); default: Array new; beOrdered; "to get a 'up' and a 'down' command on each line" beRemoveable; "to get a 'remove' command on each line" beEditable; "to get a 'edit' command on each line" yourself Bye From renggli at iam.unibe.ch Wed Apr 12 08:28:37 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Wed, 12 Apr 2006 08:28:37 +0200 Subject: [Magritte] OneToManyRelation and Reports In-Reply-To: <443C97D2.4060600@laposte.net> References: <443C97D2.4060600@laposte.net> Message-ID: <83CC40D2-F290-4D51-8B89-4F2252E1EF0A@iam.unibe.ch> > I would like to know why OneToManyRelations are not as configurable as > MultipleOptionDescriptions. It would be cool to get #beSortable, > #beOrdered, #beRemoveable... Is it just a problem of time or something > difficult to implement ? It is just that I didn't need it so far, but if you do so, please feel free to add the missing functionality and commit your changes to the public repository. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From ssastre at seaswork.com.ar Wed Apr 12 14:39:55 2006 From: ssastre at seaswork.com.ar (=?iso-8859-1?Q?Sebasti=E1n_Sastre?=) Date: Wed, 12 Apr 2006 09:39:55 -0300 Subject: Pier customized look Message-ID: HI All, how do I (in a *polite* fashion) customize the fonts and header of pier to install a wiki? thanks, Sebasti?n -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20060412/22a40729/attachment.html From renggli at iam.unibe.ch Wed Apr 12 21:01:41 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Wed, 12 Apr 2006 21:01:41 +0200 Subject: Pier customized look In-Reply-To: References: Message-ID: > how do I (in a *polite* fashion) customize the fonts and header of > pier to install a wiki? Currently there is no simple way to do this, because of the lack of configurable styles in Seaside. The standard procedure to change the look is to create your own style library or to directly modify PRPierLibrary. Instead of including the styles from my server you include your own styles. If you only want to modify the existing look you might want to add your own style as an extension method to PRPierLibrary. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From frank.urbach at schmees.com Wed Apr 12 22:02:50 2006 From: frank.urbach at schmees.com (Frank Urbach) Date: Wed, 12 Apr 2006 20:02:50 +0000 GMT Subject: AW: Pier customized look In-Reply-To: References: Message-ID: <912743092-1144872526-cardhu_blackberry.rim.net-32561-@engine05-cell01.bwc.produk.on.blackberry> Hi, Sebasti?n! Try to get the original css-files. Move these files into a structure of an webserver where you can access over. http-protocoll. Alter in class PRPierLibary the accessor style to the location of yor css-files.Then you can edit the file style-contents at point .header .title. Now you can. use fonts you like. Hope this helps. Cheers, Frank, -----Original Message----- From: ssastre at seaswork.com.ar Date: Wed, 12 Apr 2006 14:39:55 To:smallwiki at iam.unibe.ch Subject: Pier customized look HI All, how do I (in a *polite* fashion) customize the fonts and header of pier to install a wiki? thanks, Sebasti?n From hnbeck at t-online.de Fri Apr 14 17:13:08 2006 From: hnbeck at t-online.de (Hans N Beck) Date: Fri, 14 Apr 2006 17:13:08 +0200 Subject: Disable control area in Pier Message-ID: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> Hi, how can I disable the bottom line with "New Session", "Toggle Halo" etc in pier ? The standard web user should not be able to make dangerous things :-) Is that a matter of seaside itself ? Regards and happy Easter ! Hans From cbeler at enit.fr Fri Apr 14 17:22:12 2006 From: cbeler at enit.fr (=?ISO-8859-1?Q?C=E9drick_B=E9ler?=) Date: Fri, 14 Apr 2006 17:22:12 +0200 Subject: Disable control area in Pier In-Reply-To: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> References: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> Message-ID: <443FBE24.5070804@enit.fr> hi it it the deployment mode of all seaside application >Hi, > >how can I disable the bottom line with "New Session", "Toggle Halo" >etc in pier ? The standard web user should not be able to make >dangerous things :-) Is that a matter of seaside itself ? > > > so in the config page, go to configure (click) next to pier and set deployment mode to false >Regards and happy Easter ! > > > Thanks ;) smae for all Bye C?drick From hnbeck at t-online.de Fri Apr 14 17:22:11 2006 From: hnbeck at t-online.de (Hans N Beck) Date: Fri, 14 Apr 2006 17:22:11 +0200 Subject: Update Smallwiki 1 Message-ID: <14964221-D783-452F-8F7F-885F58EDDA3B@t-online.de> Hi, my running Website is a Smallwiki 1 running on Squeak 3.6. Now I want to upgrade on the newest version in Squeak and Smallwiki 1. In the FAQ is mentioned something which relates to Store (and therefore written for VW version of Smallwiki, I guess) and therefore is not matching my environment. So what would be the best strategy in my case ? Using Montecello ? Regards Hans From renggli at iam.unibe.ch Fri Apr 14 17:24:20 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 14 Apr 2006 17:24:20 +0200 Subject: Disable control area in Pier In-Reply-To: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> References: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> Message-ID: <02B75930-B76B-4872-A2CF-AF226AD74FC9@iam.unibe.ch> > how can I disable the bottom line with "New Session", "Toggle Halo" > etc in pier ? The standard web user should not be able to make > dangerous things :-) Is that a matter of seaside itself ? Yes, go to /seaside/config, remove any unused applications and set "deployment mode" of your pier application to true. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From hnbeck at t-online.de Fri Apr 14 17:33:50 2006 From: hnbeck at t-online.de (Hans N Beck) Date: Fri, 14 Apr 2006 17:33:50 +0200 Subject: Disable control area in Pier In-Reply-To: <02B75930-B76B-4872-A2CF-AF226AD74FC9@iam.unibe.ch> References: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> <02B75930-B76B-4872-A2CF-AF226AD74FC9@iam.unibe.ch> Message-ID: Hi, works :-) And how to prevent that everyone can call the ../seaside/config page ? ;-) I think the removing the config is not the best :-) (Ok, this are now very basic seaside questions....) Regards Hans Am 14.04.2006 um 17:24 schrieb Lukas Renggli: >> how can I disable the bottom line with "New Session", "Toggle Halo" >> etc in pier ? The standard web user should not be able to make >> dangerous things :-) Is that a matter of seaside itself ? > > Yes, go to /seaside/config, remove any unused applications and set > "deployment mode" of your pier application to true. > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From cbeler at enit.fr Fri Apr 14 17:46:29 2006 From: cbeler at enit.fr (=?ISO-8859-1?Q?C=E9drick_B=E9ler?=) Date: Fri, 14 Apr 2006 17:46:29 +0200 Subject: Disable control area in Pier In-Reply-To: References: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> <02B75930-B76B-4872-A2CF-AF226AD74FC9@iam.unibe.ch> Message-ID: <443FC3D5.1020800@enit.fr> sorry for the last answer :-[ It was the opposite as Lukas said... Hans N Beck a ?crit : >Hi, > >works :-) > >And how to prevent that everyone can call the ../seaside/config >page ? ;-) I think the removing the config is not the best :-) >(Ok, this are now very basic seaside questions....) > > actually config is protected by a password so it shouldn't be accessible... ;) if you want to change it evaluate WADispatcherEditor initialize See you C?drick From hnbeck at t-online.de Fri Apr 14 18:24:31 2006 From: hnbeck at t-online.de (Hans N Beck) Date: Fri, 14 Apr 2006 18:24:31 +0200 Subject: Disable control area in Pier In-Reply-To: <443FC3D5.1020800@enit.fr> References: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> <02B75930-B76B-4872-A2CF-AF226AD74FC9@iam.unibe.ch> <443FC3D5.1020800@enit.fr> Message-ID: <355B81AD-7FED-4760-9FEC-81997E3FD192@t-online.de> Hi Am 14.04.2006 um 17:46 schrieb C?drick B?ler: > sorry for the last answer :-[ It was the opposite as Lukas said... don't worry, I've got the idea :-) > > Hans N Beck a ?crit : > >> Hi, >> >> works :-) >> >> And how to prevent that everyone can call the ../seaside/config >> page ? ;-) I think the removing the config is not the best :-) >> (Ok, this are now very basic seaside questions....) >> >> > actually config is protected by a password so it shouldn't be > accessible... ;) > if you want to change it evaluate WADispatcherEditor initialize hmm, I have loaded the Pier in a clean 3.8 image (and the Pier unix security package), and there was no password needed to get the config site...... is there any default login ? Regards Hans From cbeler at enit.fr Fri Apr 14 18:37:35 2006 From: cbeler at enit.fr (=?ISO-8859-1?Q?C=E9drick_B=E9ler?=) Date: Fri, 14 Apr 2006 18:37:35 +0200 Subject: Disable control area in Pier In-Reply-To: <355B81AD-7FED-4760-9FEC-81997E3FD192@t-online.de> References: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> <02B75930-B76B-4872-A2CF-AF226AD74FC9@iam.unibe.ch> <443FC3D5.1020800@enit.fr> <355B81AD-7FED-4760-9FEC-81997E3FD192@t-online.de> Message-ID: <443FCFCF.6060909@enit.fr> An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20060414/07678be9/attachment.html From hnbeck at t-online.de Fri Apr 14 21:31:33 2006 From: hnbeck at t-online.de (Hans N Beck) Date: Fri, 14 Apr 2006 21:31:33 +0200 Subject: Disable control area in Pier In-Reply-To: <443FCFCF.6060909@enit.fr> References: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> <02B75930-B76B-4872-A2CF-AF226AD74FC9@iam.unibe.ch> <443FC3D5.1020800@enit.fr> <355B81AD-7FED-4760-9FEC-81997E3FD192@t-online.de> <443FCFCF.6060909@enit.fr> Message-ID: Hi, So now I've looked a little bit in the mailing archive, and I'm a little bit confused: It seems, - that Seaside and Pier (or any other application in Seaside) can have different security models. Both can handle its own user lists and capabilities - that there are 2 different security packages (unix inspired / ACL based) - both Seaside and Pier can add users (or user management in general) only by typing something (what ?) in workspace So if this is all true - what are the plans to make this all more integrated, so that there is only one user management, and an application may only extend the basic mechanism from seaside ? Or I'm completly wrong here ? Regards Hans Am 14.04.2006 um 18:37 schrieb C?drick B?ler: > >> hmm, I have loaded the Pier in a clean 3.8 image (and the Pier unix >> security package), and there was no password needed to get the config >> site...... is there any default login ? >> >> > I think there is a default login when loading directly from the > pier package (that manages to load all depedencies) I dont really > remember but I think its login: admin pass: pier not sure at > all ;) > > anyway, the best is probably to reset the pass by evaluating > WADispatcherEditor initialize > > an interface will ask you for a user login and password that you'll > use for the page > http://localhost:XXXX/seaside/config > > See you > > C?drick > > > _______________________________________________ > 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/20060414/3af4c259/attachment.html From rleon at insario.com Fri Apr 14 21:46:43 2006 From: rleon at insario.com (Ramon Leon) Date: Fri, 14 Apr 2006 12:46:43 -0700 Subject: Disable control area in Pier Message-ID: <24C40DFA333DC44882F9FB0115F33D8F49A471@ARGON.insario.local> > Hi, > > So now I've looked a little bit in the mailing archive, and > I'm a little bit confused: > > It seems, > > - that Seaside and Pier (or any other application in Seaside) > can have different security models. Both can handle its own > user lists and capabilities > - that there are 2 different security packages (unix inspired > / ACL based) > - both Seaside and Pier can add users (or user management in > general) only by typing something (what ?) in workspace > > So if this is all true - what are the plans to make this all > more integrated, so that there is only one user management, > and an application may only extend the basic mechanism from > seaside ? Or I'm completly wrong here ? > > Regards > > Hans Pier is simply a seaside application, its user model is and should be unrelated to anything Seaside does. As far as I know, Seaside doesn't really have any security model, it's just a framework. The config application has users, which I guess you can call part of Seaside, but it's really just another app on top of Seaside like Pier. That Pier offers two security packages, is good, one is simple and written by the author of Pier, and one is more complex, especially in the UI, and offered as an add on by some other author. So, I don't they should be integrated in any way, they really aren't related. I would however, like to see more info on how to integrate custom applications meant to be hosted within Pier, with Piers default Unix Security model. How to manage and register users from the Pier UI, etc. From rleon at insario.com Sat Apr 15 04:59:24 2006 From: rleon at insario.com (Ramon Leon) Date: Fri, 14 Apr 2006 19:59:24 -0700 Subject: Magritte References: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> <02B75930-B76B-4872-A2CF-AF226AD74FC9@iam.unibe.ch> Message-ID: <24C40DFA333DC44882F9FB0115F33D8F1653DD@ARGON.insario.local> Has anyone done, or seen a sample of cascading dialog boxes done with only magritte descriptions? Say I had a dropdown list of classes, and when one was selected, I want the next drop down list to contain methods in that class, or maybe countries and states, or whatever. How can the second MultipleOptionDescription get it's options: from the selector on the instance that the first MultipleOptionDescription set the value on? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/ms-tnef Size: 2929 bytes Desc: not available Url : http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20060415/e826e1ea/attachment-0001.bin From hnbeck at t-online.de Sat Apr 15 08:44:34 2006 From: hnbeck at t-online.de (Hans N Beck) Date: Sat, 15 Apr 2006 08:44:34 +0200 Subject: Disable control area in Pier In-Reply-To: <24C40DFA333DC44882F9FB0115F33D8F49A471@ARGON.insario.local> References: <24C40DFA333DC44882F9FB0115F33D8F49A471@ARGON.insario.local> Message-ID: <2485D42B-53F0-423B-91B8-DED384E68B73@t-online.de> Hi Ramon, > > Pier is simply a seaside application, its user model is and should be > unrelated to anything Seaside does. As far as I know, Seaside doesn't > really have any security model, it's just a framework. The config > application has users, which I guess you can call part of Seaside, but > it's really just another app on top of Seaside like Pier. That Pier > offers two security packages, is good, one is simple and written by > the > author of Pier, and one is more complex, especially in the UI, and > offered as an add on by some other author. So, I don't they should be > integrated in any way, they really aren't related. I would however, > like to see more info on how to integrate custom applications meant to > be hosted within Pier, with Piers default Unix Security model. How to > manage and register users from the Pier UI, etc. > OK. The reason why I said security should be integrated is because I think especially for web applications, security should not be something to install after, or to make need and decision which kind of security one want, it should be a fix and deep rooted part of such a system. like the language E. As an add on, I would afraid that this could be cracked more easily by some bad guys than if it is structural part ...... But I think also this discussion is not new. So thanks for explanation. How can I add users for the Security of Lukas (the unix ispired)? Regards Hans From renggli at iam.unibe.ch Sat Apr 15 09:16:28 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sat, 15 Apr 2006 09:16:28 +0200 Subject: Disable control area in Pier In-Reply-To: <2485D42B-53F0-423B-91B8-DED384E68B73@t-online.de> References: <24C40DFA333DC44882F9FB0115F33D8F49A471@ARGON.insario.local> <2485D42B-53F0-423B-91B8-DED384E68B73@t-online.de> Message-ID: <517CAD46-6040-477F-A2CD-0B06B75E8EC8@iam.unibe.ch> > But I think also this discussion is not new. So thanks for > explanation. How can I add users for the Security of Lukas (the unix > ispired)? Sorry, that this is not possible from the web (yet), I am flooded with work and everybody is asked to contribute ;-) To answer your question: PRKernel instances -> explore the expression -> navigate to kernel of question -> navigate to the dictionary properties Now you can see two sets, one called #groups and the other one called #users, that you can modify to add and remove users. Also have a look at the implementation of PUUser and PUGroup. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Sat Apr 15 09:23:52 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sat, 15 Apr 2006 09:23:52 +0200 Subject: Magritte In-Reply-To: <24C40DFA333DC44882F9FB0115F33D8F1653DD@ARGON.insario.local> References: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> <02B75930-B76B-4872-A2CF-AF226AD74FC9@iam.unibe.ch> <24C40DFA333DC44882F9FB0115F33D8F1653DD@ARGON.insario.local> Message-ID: <1A0CD630-CEF4-4DEF-9B97-F4DE5F726A20@iam.unibe.ch> > Has anyone done, or seen a sample of cascading dialog boxes done > with only magritte descriptions? Say I had a dropdown list of > classes, and when one was selected, I want the next drop down list > to contain methods in that class, or maybe countries and states, or > whatever. How can the second MultipleOptionDescription get it's > options: from the selector on the instance that the first > MultipleOptionDescription set the value on? Yes, however you need to specify the second description on the instance-side to be able to define it according to the state of your model. There are some examples on how to change descriptions on an instance-bases in the slides of my Magritte Tutorial (Dynamic Descriptions, 31-33) at . Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Sat Apr 15 09:58:40 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sat, 15 Apr 2006 09:58:40 +0200 Subject: Magritte In-Reply-To: <1A0CD630-CEF4-4DEF-9B97-F4DE5F726A20@iam.unibe.ch> References: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> <02B75930-B76B-4872-A2CF-AF226AD74FC9@iam.unibe.ch> <24C40DFA333DC44882F9FB0115F33D8F1653DD@ARGON.insario.local> <1A0CD630-CEF4-4DEF-9B97-F4DE5F726A20@iam.unibe.ch> Message-ID: <0CB464E0-4A1A-429A-80B8-F02C92AD6693@iam.unibe.ch> I was just eating breakfast and wondering if it really makes sense to define descriptions on the class-side. Sure this is a meta-thing, but it is not something necessarily belonging to the class as we saw in the mail of the original poster. So it would probably make more sense to put descriptions describing the instance to the instance-side, so that they can be easily created depending on the current model state. The draw-back, there is usually one, would be that retrieving the descriptions would be more expensive as they cannot be cached anymore. What do you think? Lukas On 15 Apr 2006, at 09:23, Lukas Renggli wrote: >> Has anyone done, or seen a sample of cascading dialog boxes done >> with only magritte descriptions? Say I had a dropdown list of >> classes, and when one was selected, I want the next drop down list >> to contain methods in that class, or maybe countries and states, or >> whatever. How can the second MultipleOptionDescription get it's >> options: from the selector on the instance that the first >> MultipleOptionDescription set the value on? > > Yes, however you need to specify the second description on the > instance-side to be able to define it according to the state of your > model. There are some examples on how to change descriptions on an > instance-bases in the slides of my Magritte Tutorial (Dynamic > Descriptions, 31-33) at magritte>. > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- Lukas Renggli http://www.lukas-renggli.ch From hnbeck at t-online.de Sat Apr 15 10:15:12 2006 From: hnbeck at t-online.de (Hans N Beck) Date: Sat, 15 Apr 2006 10:15:12 +0200 Subject: Disable control area in Pier In-Reply-To: <517CAD46-6040-477F-A2CD-0B06B75E8EC8@iam.unibe.ch> References: <24C40DFA333DC44882F9FB0115F33D8F49A471@ARGON.insario.local> <2485D42B-53F0-423B-91B8-DED384E68B73@t-online.de> <517CAD46-6040-477F-A2CD-0B06B75E8EC8@iam.unibe.ch> Message-ID: Hi Lukas, Am 15.04.2006 um 09:16 schrieb Lukas Renggli: >> But I think also this discussion is not new. So thanks for >> explanation. How can I add users for the Security of Lukas (the unix >> ispired)? > > Sorry, that this is not possible from the web (yet), I am flooded > with work and everybody is asked to contribute ;-) I think so......... :-) > > To answer your question: > > PRKernel instances > -> explore the expression > -> navigate to kernel of question > -> navigate to the dictionary properties > > Now you can see two sets, one called #groups and the other one called > #users, that you can modify to add and remove users. Also have a look > at the implementation of PUUser and PUGroup. Thanks for the answer ! Greetings Hans From damien.cassou at laposte.net Sat Apr 15 11:24:56 2006 From: damien.cassou at laposte.net (Damien Cassou) Date: Sat, 15 Apr 2006 11:24:56 +0200 Subject: Magritte In-Reply-To: <0CB464E0-4A1A-429A-80B8-F02C92AD6693@iam.unibe.ch> References: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> <02B75930-B76B-4872-A2CF-AF226AD74FC9@iam.unibe.ch> <24C40DFA333DC44882F9FB0115F33D8F1653DD@ARGON.insario.local> <1A0CD630-CEF4-4DEF-9B97-F4DE5F726A20@iam.unibe.ch> <0CB464E0-4A1A-429A-80B8-F02C92AD6693@iam.unibe.ch> Message-ID: <4440BBE8.9060300@laposte.net> Lukas Renggli wrote: > I was just eating breakfast and wondering if it really makes sense to > define descriptions on the class-side. Sure this is a meta-thing, but > it is not something necessarily belonging to the class as we saw in > the mail of the original poster. > > So it would probably make more sense to put descriptions describing > the instance to the instance-side, so that they can be easily created > depending on the current model state. The draw-back, there is usually > one, would be that retrieving the descriptions would be more > expensive as they cannot be cached anymore. > > What do you think? > Have you tried to remove caching from existing Magritte programs to test if it is really slower? From renggli at iam.unibe.ch Sat Apr 15 13:36:29 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sat, 15 Apr 2006 13:36:29 +0200 Subject: Magritte In-Reply-To: <4440BBE8.9060300@laposte.net> References: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> <02B75930-B76B-4872-A2CF-AF226AD74FC9@iam.unibe.ch> <24C40DFA333DC44882F9FB0115F33D8F1653DD@ARGON.insario.local> <1A0CD630-CEF4-4DEF-9B97-F4DE5F726A20@iam.unibe.ch> <0CB464E0-4A1A-429A-80B8-F02C92AD6693@iam.unibe.ch> <4440BBE8.9060300@laposte.net> Message-ID: <05275683-E3BA-4EC2-BBDF-ECAA5DE257C4@iam.unibe.ch> > Have you tried to remove caching from existing Magritte programs to > test if it is really slower? Sure it is much slower, I profiled it when implementing the cache. I just redid the test in the latest version and it shows that the cache improves the description retrieval by a factor of 7000, of course depending on the object hierarchy of the queried class. The reason it is so slow is basically the use of #allSelector, that could be improved (with more clever code or pragmas). Still I guess the factor of 10^3 would stay the same. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From damien.cassou at laposte.net Sat Apr 15 15:16:45 2006 From: damien.cassou at laposte.net (Damien Cassou) Date: Sat, 15 Apr 2006 15:16:45 +0200 Subject: [Magritte] OneToManyRelation and Reports In-Reply-To: <83CC40D2-F290-4D51-8B89-4F2252E1EF0A@iam.unibe.ch> References: <443C97D2.4060600@laposte.net> <83CC40D2-F290-4D51-8B89-4F2252E1EF0A@iam.unibe.ch> Message-ID: <4440F23D.7040900@laposte.net> Lukas Renggli a ?crit : >> I would like to know why OneToManyRelations are not as configurable as >> MultipleOptionDescriptions. It would be cool to get #beSortable, >> #beOrdered, #beRemoveable... Is it just a problem of time or something >> difficult to implement ? > > It is just that I didn't need it so far, but if you do so, please > feel free to add the missing functionality and commit your changes to > the public repository. I've just committed the 'ordered' part. - ToManyRelationDescriptions can now be ordered. - OneToManyComponents get a 'up' and 'down' command to change the order. Please have a look and tell me if I did something wrong! -- Damien Cassou From bergel at iam.unibe.ch Sat Apr 15 17:00:15 2006 From: bergel at iam.unibe.ch (Bergel, Alexandre) Date: Sat, 15 Apr 2006 16:00:15 +0100 Subject: Bug with Pier 1.0.4 alpha ? Message-ID: <57A67F92-FAD8-4B67-83B7-D48F920799CC@iam.unibe.ch> Hi! I am hopping to find some time to install a pier server at the trinity. I encountered a problem with the last version I found on SqueakMap. If I create a new page, and I put as content: This is a test When I save this page, and I edit it again, I obtain: This+is+a\+test Which produce a very messy output. If I edit the licence page, and I save it without modifying anything, the page completely is messed up. It seems that the space character is replaced by a + I am using Squeak 7021, and I just installed Pier from Squeakmap. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.cs.tcd.ie/Alexandre.Bergel ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. From ssastre at seaswork.com.ar Sat Apr 15 17:03:13 2006 From: ssastre at seaswork.com.ar (=?iso-8859-1?Q?Sebasti=E1n_Sastre?=) Date: Sat, 15 Apr 2006 12:03:13 -0300 Subject: Magritte In-Reply-To: <0CB464E0-4A1A-429A-80B8-F02C92AD6693@iam.unibe.ch> Message-ID: ... > The draw-back, there is usually one, would be that retrieving > the descriptions would be more expensive as they cannot be > cached anymore. Why it can be cached anymore? Can't just be posible to refactor the cache subsystem to work instance based intead of class based? I know that some systems allready have instance based caches. Some of them: GOODS client by Avi Bryant, rST, OmniBase support regards, Sebsatian PD: I'm not familiar with Magritte and recently interested in it because I think it make archivable that an application could have a maintainable web interface and desktop interface at a reasonably cost. From damien.cassou at laposte.net Sat Apr 15 19:01:15 2006 From: damien.cassou at laposte.net (Damien Cassou) Date: Sat, 15 Apr 2006 19:01:15 +0200 Subject: Bug with Pier 1.0.4 alpha ? In-Reply-To: <57A67F92-FAD8-4B67-83B7-D48F920799CC@iam.unibe.ch> References: <57A67F92-FAD8-4B67-83B7-D48F920799CC@iam.unibe.ch> Message-ID: <444126DB.3050404@laposte.net> I get this problem too. Using monticello solved it. -- Damien Cassou From ramonleon at cox.net Sat Apr 15 21:00:56 2006 From: ramonleon at cox.net (Ramon Leon) Date: Sat, 15 Apr 2006 12:00:56 -0700 Subject: Magritte In-Reply-To: <05275683-E3BA-4EC2-BBDF-ECAA5DE257C4@iam.unibe.ch> References: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> <02B75930-B76B-4872-A2CF-AF226AD74FC9@iam.unibe.ch> <24C40DFA333DC44882F9FB0115F33D8F1653DD@ARGON.insario.local> <1A0CD630-CEF4-4DEF-9B97-F4DE5F726A20@iam.unibe.ch> <0CB464E0-4A1A-429A-80B8-F02C92AD6693@iam.unibe.ch> <4440BBE8.9060300@laposte.net> <05275683-E3BA-4EC2-BBDF-ECAA5DE257C4@iam.unibe.ch> Message-ID: <444142E8.9080905@cox.net> >>Have you tried to remove caching from existing Magritte programs to >>test if it is really slower? > > > Sure it is much slower, I profiled it when implementing the cache. I > just redid the test in the latest version and it shows that the cache > improves the description retrieval by a factor of 7000, of course > depending on the object hierarchy of the queried class. The reason it > is so slow is basically the use of #allSelector, that could be > improved (with more clever code or pragmas). Still I guess the factor > of 10^3 would stay the same. > > Lukas Well, being slower, doesn't at all imply that it's too slow, so a better question is in the overall rendering of a page, say a complex edit form, what percentage of total rendering time is taken by retrieving the description both cached and uncached. I mean, it could be dwarfed by the call to goods(or whatever db you use) to actually retrieve the objects, and if that's the case, running uncached may not even be noticeable. Caching may not be necessary at all, in the larger scheme of things, and frankly, I find myself flushing the cache constantly, especially during development. From ramonleon at cox.net Sat Apr 15 21:32:57 2006 From: ramonleon at cox.net (Ramon Leon) Date: Sat, 15 Apr 2006 12:32:57 -0700 Subject: Magritte In-Reply-To: <1A0CD630-CEF4-4DEF-9B97-F4DE5F726A20@iam.unibe.ch> References: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> <02B75930-B76B-4872-A2CF-AF226AD74FC9@iam.unibe.ch> <24C40DFA333DC44882F9FB0115F33D8F1653DD@ARGON.insario.local> <1A0CD630-CEF4-4DEF-9B97-F4DE5F726A20@iam.unibe.ch> Message-ID: <44414A69.5000301@cox.net> Lukas Renggli wrote: >>Has anyone done, or seen a sample of cascading dialog boxes done >>with only magritte descriptions? Say I had a dropdown list of >>classes, and when one was selected, I want the next drop down list >>to contain methods in that class, or maybe countries and states, or >>whatever. How can the second MultipleOptionDescription get it's >>options: from the selector on the instance that the first >>MultipleOptionDescription set the value on? > > > Yes, however you need to specify the second description on the > instance-side to be able to define it according to the state of your > model. There are some examples on how to change descriptions on an > instance-bases in the slides of my Magritte Tutorial (Dynamic > Descriptions, 31-33) at magritte>. > > Cheers, > Lukas Ok, doesn't seem to work, but let me explain what I'm doing. I'm writing a component meant to be hosted in Pier, the component has several settings it needs, and I was using class side descriptions to provide the "settings" interface that Pier offers on any component. However, looking at PRSettingsComponent, I see that it's not asking the instance for it's description, it's asking the class directly, bypassing any overrides I may have attempted on the instance side. Is that the intention? Am I writing components wrong? Should I be subclassing something in Pier rather than my own WAComponent subclass? The Magritte tutorial is great btw, is there something similar for Pier? Now that Pier seems somewhat stable, I'm starting to explore it more as an application container with configurable widgets, digging it so far, just need to get a few things done so I grok the do's and dont's a little better. Great work though, keep it up! From koubo2006 at yengawa.jpn.org Sun Apr 16 04:23:01 2006 From: koubo2006 at yengawa.jpn.org (Koji Yokokawa) Date: Sun, 16 Apr 2006 11:23:01 +0900 Subject: Bug with Pier 1.0.4 alpha ? In-Reply-To: <57A67F92-FAD8-4B67-83B7-D48F920799CC@iam.unibe.ch> References: <57A67F92-FAD8-4B67-83B7-D48F920799CC@iam.unibe.ch> Message-ID: <20060416110023.D9BB.KOUBO2006@yengawa.jpn.org> It's caused by a bug in String>>unescapePercentsWithTextEncoding: Seaside uses this method so that was a problem of the Seaside. Umezawa-san released a patch for it. http://www.kukakuka.jp/squeak/bugs/view.php?id=66 (This site is a Mantise for Japanese community so all in Japanese) You can get the patch from this URL. http://www.kukakuka.jp/squeak/bugs/file_download.php?file_id=42&type=bug This patch fixed the '+' and a wrong UTF decoding problem. Koji On Sat, 15 Apr 2006 16:00:15 +0100 "Bergel, Alexandre" wrote: > Hi! > > I am hopping to find some time to install a pier server at the trinity. > I encountered a problem with the last version I found on SqueakMap. > > If I create a new page, and I put as content: This is a test > When I save this page, and I edit it again, I obtain: This+is+a\+test > Which produce a very messy output. > > If I edit the licence page, and I save it without modifying anything, > the page completely is messed up. > > It seems that the space character is replaced by a + > > I am using Squeak 7021, and I just installed Pier from Squeakmap. > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.cs.tcd.ie/Alexandre.Bergel > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- ! Koji Yokokawa http://yengawa.com/ ^self new! From renggli at iam.unibe.ch Sun Apr 16 10:32:17 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 16 Apr 2006 10:32:17 +0200 Subject: Magritte In-Reply-To: <44414A69.5000301@cox.net> References: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> <02B75930-B76B-4872-A2CF-AF226AD74FC9@iam.unibe.ch> <24C40DFA333DC44882F9FB0115F33D8F1653DD@ARGON.insario.local> <1A0CD630-CEF4-4DEF-9B97-F4DE5F726A20@iam.unibe.ch> <44414A69.5000301@cox.net> Message-ID: <003F9BCC-D4AB-446B-9CE6-FBBA691B0275@iam.unibe.ch> > Ok, doesn't seem to work, but let me explain what I'm doing. I'm > writing a component meant to be hosted in Pier, the component has > several settings it needs, and I was using class side descriptions to > provide the "settings" interface that Pier offers on any component. Yes, this is the usual procedure. > However, looking at PRSettingsComponent, I see that it's not asking > the > instance for it's description, it's asking the class directly, > bypassing > any overrides I may have attempted on the instance side. Is that the > intention? Oups, this seems to be a bug. I fixed it and will publish my changes as soon as I have a propre internet connectionn again. > Am I writing components wrong? Should I be subclassing > something in Pier rather than my own WAComponent subclass? No nothing wrong from your side. You could also subclass PRStructure (as the model) and define the settings on there (to make editing work). Then you could also define views and other commands. > The Magritte tutorial is great btw, is there something similar for > Pier? No, not yet, only the SmallWiki paper from WikiSymposium that is still valid for a big part (minus the name). > Now that Pier seems somewhat stable, I'm starting to explore it more > as an application container with configurable widgets, digging it so > far, just need to get a few things done so I grok the do's and > dont's a > little better. Great work though, keep it up! Thanks a lot! Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Sun Apr 16 10:27:53 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 16 Apr 2006 10:27:53 +0200 Subject: Magritte In-Reply-To: References: Message-ID: >> The draw-back, there is usually one, would be that retrieving >> the descriptions would be more expensive as they cannot be >> cached anymore. > > Why it can be cached anymore? Can't just be posible to refactor the > cache subsystem to work instance based intead of class based? Yes, that should be possible. However Squeak has inherent problems with dictionaries having more than 4000 elements, and even worse, with weak finalization; two things that are very likely to be needed for an instance-based description cache. > I know that some systems allready have instance based caches. Some > of them: > > GOODS client by Avi Bryant, > rST, > OmniBase support Yes, I know GOODS, it gets very slow when the caches grow. OmniBase uses a slightly different approach and has its own fast implementation of an IdentityDictionary. > PD: I'm not familiar with Magritte and recently interested in it > because I > think it make archivable that an application could have a > maintainable web > interface and desktop interface at a reasonably cost. True, however the builder for desktop-interfaces probably needs some more work to be useable in production ;-) Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Sun Apr 16 10:30:05 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 16 Apr 2006 10:30:05 +0200 Subject: Magritte In-Reply-To: <444142E8.9080905@cox.net> References: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> <02B75930-B76B-4872-A2CF-AF226AD74FC9@iam.unibe.ch> <24C40DFA333DC44882F9FB0115F33D8F1653DD@ARGON.insario.local> <1A0CD630-CEF4-4DEF-9B97-F4DE5F726A20@iam.unibe.ch> <0CB464E0-4A1A-429A-80B8-F02C92AD6693@iam.unibe.ch> <4440BBE8.9060300@laposte.net> <05275683-E3BA-4EC2-BBDF-ECAA5DE257C4@iam.unibe.ch> <444142E8.9080905@cox.net> Message-ID: <1278C28A-211C-486B-B1E4-0BD56FEDDA5E@iam.unibe.ch> > Well, being slower, doesn't at all imply that it's too slow, so a > better question is in the overall rendering of a page, say a > complex edit form, what percentage of total rendering time is taken > by retrieving the description both cached and uncached. I mean, it > could be dwarfed by the call to goods(or whatever db you use) to > actually retrieve the objects, and if that's the case, running > uncached may not even be noticeable. Yes, this is true, it won't be noticeable at least for building GUIs: the description is only read once before visiting the descriptions and building the interface. It becomes more of a speed problem when a query is done over a graph with many described objects. > Caching may not be necessary at all, in the larger scheme of > things, and frankly, I find myself flushing the cache constantly, > especially during development. Why that? The cache is automatically flushed when descriptions change in your code. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From damien.cassou at laposte.net Sun Apr 16 18:04:04 2006 From: damien.cassou at laposte.net (Damien Cassou) Date: Sun, 16 Apr 2006 18:04:04 +0200 Subject: Magritte In-Reply-To: <003F9BCC-D4AB-446B-9CE6-FBBA691B0275@iam.unibe.ch> References: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> <02B75930-B76B-4872-A2CF-AF226AD74FC9@iam.unibe.ch> <24C40DFA333DC44882F9FB0115F33D8F1653DD@ARGON.insario.local> <1A0CD630-CEF4-4DEF-9B97-F4DE5F726A20@iam.unibe.ch> <44414A69.5000301@cox.net> <003F9BCC-D4AB-446B-9CE6-FBBA691B0275@iam.unibe.ch> Message-ID: <44426AF4.5020905@laposte.net> >> The Magritte tutorial is great btw, is there something similar for >> Pier? > > No, not yet, only the SmallWiki paper from WikiSymposium that is > still valid for a big part (minus the name). And the documents I wrote: http://smallwiki.unibe.ch/smallwiki/pier -- Damien Cassou From damien.cassou at laposte.net Sun Apr 16 19:05:05 2006 From: damien.cassou at laposte.net (Damien Cassou) Date: Sun, 16 Apr 2006 19:05:05 +0200 Subject: [Magritte] OneToManyRelation and Reports In-Reply-To: <4440F23D.7040900@laposte.net> References: <443C97D2.4060600@laposte.net> <83CC40D2-F290-4D51-8B89-4F2252E1EF0A@iam.unibe.ch> <4440F23D.7040900@laposte.net> Message-ID: <44427941.5090502@laposte.net> New commit: - You can now specify if your ToManyRelationDescriptions contain elements that can be removed or edited. - OneToManycomponents displays #edit and #remove only when necessary. Bye -- Damien Cassou From ramonleon at cox.net Sun Apr 16 22:16:57 2006 From: ramonleon at cox.net (Ramon Leon) Date: Sun, 16 Apr 2006 13:16:57 -0700 Subject: Magritte In-Reply-To: <1278C28A-211C-486B-B1E4-0BD56FEDDA5E@iam.unibe.ch> References: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> <02B75930-B76B-4872-A2CF-AF226AD74FC9@iam.unibe.ch> <24C40DFA333DC44882F9FB0115F33D8F1653DD@ARGON.insario.local> <1A0CD630-CEF4-4DEF-9B97-F4DE5F726A20@iam.unibe.ch> <0CB464E0-4A1A-429A-80B8-F02C92AD6693@iam.unibe.ch> <4440BBE8.9060300@laposte.net> <05275683-E3BA-4EC2-BBDF-ECAA5DE257C4@iam.unibe.ch> <444142E8.9080905@cox.net> <1278C28A-211C-486B-B1E4-0BD56FEDDA5E@iam.unibe.ch> Message-ID: <4442A639.9060301@cox.net> > Yes, this is true, it won't be noticeable at least for building GUIs: > the description is only read once before visiting the descriptions > and building the interface. It becomes more of a speed problem when a > query is done over a graph with many described objects. Ah, I hadn't considered querying. >>things, and frankly, I find myself flushing the cache constantly, >>especially during development. > Why that? The cache is automatically flushed when descriptions change > in your code. Maybe just a habit I got into, looking over other code, I see use of MADynamicObject to handle binding of lists that may change and can't be cached, I think this was the original reason I started flushing the cache. Also, while in development, sometimes I feel like the cache didn't flush when I changed a description, however, there's a good chance that's just a bad perception on my part, like last night when I was trying to do an instance side description override... felt the cache wasn't flushing, turned out instead that SettingsComponent had a bug instead. From bergel at iam.unibe.ch Mon Apr 17 13:35:47 2006 From: bergel at iam.unibe.ch (Bergel, Alexandre) Date: Mon, 17 Apr 2006 12:35:47 +0100 Subject: Bug with Pier 1.0.4 alpha ? In-Reply-To: <20060416110023.D9BB.KOUBO2006@yengawa.jpn.org> References: <57A67F92-FAD8-4B67-83B7-D48F920799CC@iam.unibe.ch> <20060416110023.D9BB.KOUBO2006@yengawa.jpn.org> Message-ID: <79F261D0-F3C4-4B3B-8E21-CACBDF3BCD6C@iam.unibe.ch> It works! Thanks a lot!!! Alexandre Am Apr 16, 2006 um 3:23 AM schrieb Koji Yokokawa: > It's caused by a bug in String>>unescapePercentsWithTextEncoding: > Seaside uses this method so that was a problem of the Seaside. > > Umezawa-san released a patch for it. > http://www.kukakuka.jp/squeak/bugs/view.php?id=66 > (This site is a Mantise for Japanese community so all in Japanese) > You can get the patch from this URL. > http://www.kukakuka.jp/squeak/bugs/file_download.php? > file_id=42&type=bug > This patch fixed the '+' and a wrong UTF decoding problem. > > Koji > > On Sat, 15 Apr 2006 16:00:15 +0100 > "Bergel, Alexandre" wrote: > >> Hi! >> >> I am hopping to find some time to install a pier server at the >> trinity. >> I encountered a problem with the last version I found on SqueakMap. >> >> If I create a new page, and I put as content: This is a test >> When I save this page, and I edit it again, I obtain: This+is+a\+test >> Which produce a very messy output. >> >> If I edit the licence page, and I save it without modifying anything, >> the page completely is messed up. >> >> It seems that the space character is replaced by a + >> >> I am using Squeak 7021, and I just installed Pier from Squeakmap. >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.cs.tcd.ie/Alexandre.Bergel >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> _______________________________________________ >> SmallWiki, Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > -- ! > Koji Yokokawa > http://yengawa.com/ > ^self new! > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.cs.tcd.ie/Alexandre.Bergel ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. From renggli at iam.unibe.ch Mon Apr 17 18:53:26 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 17 Apr 2006 18:53:26 +0200 Subject: [Magritte] OneToManyRelation and Reports In-Reply-To: <4440F23D.7040900@laposte.net> References: <443C97D2.4060600@laposte.net> <83CC40D2-F290-4D51-8B89-4F2252E1EF0A@iam.unibe.ch> <4440F23D.7040900@laposte.net> Message-ID: > I've just committed the 'ordered' part. > - ToManyRelationDescriptions can now be ordered. > - OneToManyComponents get a 'up' and 'down' command to change the > order. > > Please have a look and tell me if I did something wrong! Looks cool, nothing to complain about, I will continue to work on your modifications ;-) The only thing: Where are the tests? Lukas -- Lukas Renggli http://www.lukas-renggli.ch From damien.cassou at laposte.net Mon Apr 17 20:14:41 2006 From: damien.cassou at laposte.net (Damien Cassou) Date: Mon, 17 Apr 2006 20:14:41 +0200 Subject: [Magritte] OneToManyRelation and Reports In-Reply-To: References: <443C97D2.4060600@laposte.net> <83CC40D2-F290-4D51-8B89-4F2252E1EF0A@iam.unibe.ch> <4440F23D.7040900@laposte.net> Message-ID: <4443DB11.3030506@laposte.net> Lukas Renggli a ?crit : >> I've just committed the 'ordered' part. >> - ToManyRelationDescriptions can now be ordered. >> - OneToManyComponents get a 'up' and 'down' command to change the >> order. >> >> Please have a look and tell me if I did something wrong! > > Looks cool, nothing to complain about, I will continue to work on > your modifications ;-) > > The only thing: Where are the tests? Ooops, I'm sorry. Please don't write them for me, I will. -- Damien Cassou From rleon at insario.com Mon Apr 17 20:37:57 2006 From: rleon at insario.com (Ramon Leon) Date: Mon, 17 Apr 2006 11:37:57 -0700 Subject: Pier Commands Message-ID: <24C40DFA333DC44882F9FB0115F33D8F49A47D@ARGON.insario.local> Hi, is there a way, using the Unix security, to restrict a user to only be able to add new pages, and not allow adding of controls or files? From saidani at squeakfr.org Mon Apr 17 22:35:45 2006 From: saidani at squeakfr.org (Samir Saidani) Date: Mon, 17 Apr 2006 22:35:45 +0200 Subject: Update Smallwiki 1 In-Reply-To: <14964221-D783-452F-8F7F-885F58EDDA3B@t-online.de> (Hans N. Beck's message of "Fri, 14 Apr 2006 17:22:11 +0200") References: <14964221-D783-452F-8F7F-885F58EDDA3B@t-online.de> Message-ID: <87k69ohrdq.fsf@info.unicaen.fr> Hi Hans, Use monticello www.squeaksource.com/smallwiki1 (SmallWiki-Stable). If you keep the same name, ensure that the new version you're building for the newest version in Squeak still work with 3.6. If not, I suggest to use a name like SmallWiki-Stable-3.9 or something like that to avoid confusion with the working stable version for 3.6. Let me know if there is any problem. Samir Hans N Beck writes: > Hi, > > my running Website is a Smallwiki 1 running on Squeak 3.6. Now I want > to upgrade on the newest version in Squeak and Smallwiki 1. In the > FAQ is mentioned something which relates to Store (and therefore > written for VW version of Smallwiki, I guess) and therefore is not > matching my environment. > > So what would be the best strategy in my case ? Using Montecello ? > > Regards > > Hans > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From renggli at iam.unibe.ch Mon Apr 17 23:22:20 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 17 Apr 2006 23:22:20 +0200 Subject: Pier Commands In-Reply-To: <24C40DFA333DC44882F9FB0115F33D8F49A47D@ARGON.insario.local> References: <24C40DFA333DC44882F9FB0115F33D8F49A47D@ARGON.insario.local> Message-ID: <0D7C4703-9E9A-413F-A92F-BBA2B54DCA36@iam.unibe.ch> > Hi, is there a way, using the Unix security, to restrict a user to > only > be able to add new pages, and not allow adding of controls or files? No, this is currently not possible, except by hacking this condition into the system. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From damien.cassou at laposte.net Tue Apr 18 09:43:43 2006 From: damien.cassou at laposte.net (Damien Cassou) Date: Tue, 18 Apr 2006 09:43:43 +0200 Subject: [Magritte] OneToManyRelation and Reports In-Reply-To: References: <443C97D2.4060600@laposte.net> <83CC40D2-F290-4D51-8B89-4F2252E1EF0A@iam.unibe.ch> <4440F23D.7040900@laposte.net> Message-ID: <444498AF.4040801@laposte.net> Lukas wrote: > The only thing: Where are the tests? They are commited. -- Damien Cassou From damien.cassou at laposte.net Tue Apr 18 10:05:20 2006 From: damien.cassou at laposte.net (Damien Cassou) Date: Tue, 18 Apr 2006 10:05:20 +0200 Subject: [Magritte] Description properties Message-ID: <44449DC0.8070203@laposte.net> Hi, adding properties to descriptions is a simple but long work. You need to: - add a boolean description (class side) - add a default method (class side) - write accessors (instance side) - write action methods starting like 'beSorted' (instance side) - write testing methods (instance side) When looking at accessors: MAToManyDescription>>ordered ^ self propertyAt: #ordered ifAbsent: [ self class defaultOrdered ] it seems to me it was just a DictionaryAccessor after all. So I tried to use this. - I implemented #at: and #at:put: in MAObject (that were just calling #propertyAt: and #propertyAt:put). - I wrote a new constructor in MADescription: #dictionaryKey:label:default:priority:) - I replaced some properties descriptions by a call to the new constructor. All the tests still worked (not sure any line of what I changed were called during the tests). But then, I didn't know how to replace all the methods that need to be written. Do you have any idea? -- Damien Cassou From hnbeck at t-online.de Tue Apr 18 10:27:30 2006 From: hnbeck at t-online.de (Hans N Beck) Date: Tue, 18 Apr 2006 10:27:30 +0200 Subject: Update Smallwiki 1 In-Reply-To: <87k69ohrdq.fsf@info.unicaen.fr> References: <14964221-D783-452F-8F7F-885F58EDDA3B@t-online.de> <87k69ohrdq.fsf@info.unicaen.fr> Message-ID: <6C13F749-E691-46C1-BE25-E1BEBC90E51E@t-online.de> Hi Samir, > > Use monticello www.squeaksource.com/smallwiki1 (SmallWiki-Stable). If > you keep the same name, ensure that the new version you're building > for the newest version in Squeak still work with 3.6. If not, I > suggest to use a name like SmallWiki-Stable-3.9 or something like that > to avoid confusion with the working stable version for 3.6. Let me > know if there is any problem. Sorry, I don't understand what you're saying. Are you talking about updating Smallwiki on a 3.6 Squeak ? But the question was to setup the newest stable Smallwiki on a Squeak 3.8 (=latest release) with the old content of the now running 3.6 Smallwiki. Or do you think it is unnecessary to go to 3.8 ? In this case, it would be clear what to do. Regards Hans > > Samir > > Hans N Beck writes: > >> Hi, >> >> my running Website is a Smallwiki 1 running on Squeak 3.6. Now I want >> to upgrade on the newest version in Squeak and Smallwiki 1. In the >> FAQ is mentioned something which relates to Store (and therefore >> written for VW version of Smallwiki, I guess) and therefore is not >> matching my environment. >> >> So what would be the best strategy in my case ? Using Montecello ? >> >> Regards >> >> Hans >> >> _______________________________________________ >> 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 From cbeler at enit.fr Tue Apr 18 18:43:33 2006 From: cbeler at enit.fr (=?ISO-8859-1?Q?C=E9drick_B=E9ler?=) Date: Tue, 18 Apr 2006 18:43:33 +0200 Subject: Tutorial problem with cache Message-ID: <44451735.3020305@enit.fr> Hi I was having a look at the last exercices of the tutorial and I'm having a problem with the last exercice with custom descriptions. the custom description are doubled each time I access to them in the container... decription is overriden in MAPersonModel MAPersonModel>>description ^super description copy; addAll: self class customDescription; yourself. copy sould prevent to change the description stored in the cache. Is it correct ? This makes me ask you another question. When a description (class side) is changed, how the cache of the builder is refreshed ? I have no idea Thank you C?drick From renggli at iam.unibe.ch Tue Apr 18 18:48:59 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 18 Apr 2006 18:48:59 +0200 Subject: Tutorial problem with cache In-Reply-To: <44451735.3020305@enit.fr> References: <44451735.3020305@enit.fr> Message-ID: > MAPersonModel>>description > > ^super description copy; > addAll: self class customDescription; > yourself. > > copy sould prevent to change the description stored in the cache. > Is it > correct ? Yes, but you need to remove the colon after the copy ;-) > This makes me ask you another question. When a description (class > side) > is changed, how the cache of the builder is refreshed ? I have no idea Any source-code modification within the system flushes the cache, see MADescriptionBuilder>>flush. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From cbeler at enit.fr Tue Apr 18 18:51:52 2006 From: cbeler at enit.fr (=?ISO-8859-1?Q?C=E9drick_B=E9ler?=) Date: Tue, 18 Apr 2006 18:51:52 +0200 Subject: Magritte In-Reply-To: <05275683-E3BA-4EC2-BBDF-ECAA5DE257C4@iam.unibe.ch> References: <431A4F42-D708-4EE0-AA05-1E491EEE61E1@t-online.de> <02B75930-B76B-4872-A2CF-AF226AD74FC9@iam.unibe.ch> <24C40DFA333DC44882F9FB0115F33D8F1653DD@ARGON.insario.local> <1A0CD630-CEF4-4DEF-9B97-F4DE5F726A20@iam.unibe.ch> <0CB464E0-4A1A-429A-80B8-F02C92AD6693@iam.unibe.ch> <4440BBE8.9060300@laposte.net> <05275683-E3BA-4EC2-BBDF-ECAA5DE257C4@iam.unibe.ch> Message-ID: <44451928.2070800@enit.fr> > The reason it is so slow is basically the use of #allSelector, that could be >improved (with more clever code or pragmas). Still I guess the factor >of 10^3 would stay the same. > maybe putting all descriptions in a single class side method (a Container) could do the job but that's not really nice ;) C?drick From saidani at squeakfr.org Wed Apr 19 00:31:08 2006 From: saidani at squeakfr.org (Samir Saidani) Date: Wed, 19 Apr 2006 00:31:08 +0200 Subject: Update Smallwiki 1 In-Reply-To: <6C13F749-E691-46C1-BE25-E1BEBC90E51E@t-online.de> (Hans N. Beck's message of "Tue, 18 Apr 2006 10:27:30 +0200") References: <14964221-D783-452F-8F7F-885F58EDDA3B@t-online.de> <87k69ohrdq.fsf@info.unicaen.fr> <6C13F749-E691-46C1-BE25-E1BEBC90E51E@t-online.de> Message-ID: <878xq2o6s3.fsf@info.unicaen.fr> Hans N Beck writes: > Hi Samir, > >> >> Use monticello www.squeaksource.com/smallwiki1 (SmallWiki-Stable). If >> you keep the same name, ensure that the new version you're building >> for the newest version in Squeak still work with 3.6. If not, I >> suggest to use a name like SmallWiki-Stable-3.9 or something like that >> to avoid confusion with the working stable version for 3.6. Let me >> know if there is any problem. > > Sorry, I don't understand what you're saying. Are you talking about > updating Smallwiki on a 3.6 Squeak ? But the question was to setup > the newest stable Smallwiki on a Squeak 3.8 (=latest release) with > the old content of the now running 3.6 Smallwiki. Or do you think it > is unnecessary to go to 3.8 ? Indeed I don't think that it is really necessary for the moment. But If you want to do it, you will have to tweak the current stable smallwiki to get it work with Squeak 3.8. Updating Smallwiki-stable for 3.8 means that you have (probably) to modify Smallwiki-stable, right ? (I don't think that it will work straightforward). But we have to ensure that the modification does not break smallwiki code, which means that the smallwiki-stable update (if you do it) should work both for 3.6 and 3.8, do you agree ? Tell me if it is not clear. Cheers, Samir From ramonleon at cox.net Wed Apr 19 06:42:51 2006 From: ramonleon at cox.net (Ramon Leon) Date: Tue, 18 Apr 2006 21:42:51 -0700 Subject: Dangerous Commands In-Reply-To: References: <44451735.3020305@enit.fr> Message-ID: <4445BFCB.1060808@cox.net> Lucas, any chance you could add some javascript confirmations to commands that are unsafe, such as Remove, one small slip of the fingers and bam, a page is gone. From renggli at iam.unibe.ch Wed Apr 19 07:42:05 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Wed, 19 Apr 2006 07:42:05 +0200 Subject: Dangerous Commands In-Reply-To: <4445BFCB.1060808@cox.net> References: <44451735.3020305@enit.fr> <4445BFCB.1060808@cox.net> Message-ID: > Lucas, any chance you could add some javascript confirmations to > commands that are unsafe, such as Remove, one small slip of the > fingers and bam, a page is gone. The simplest thing you could do is to change: PRRemoveCommand>>isQuick ^ false The result doesn't look very nice, but it works. Pier-All-lr.85 does what you suggest using a simple JavaScript confirmation dialog. Hope this helps, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From stephane.ducasse at univ-savoie.fr Wed Apr 19 08:28:23 2006 From: stephane.ducasse at univ-savoie.fr (=?ISO-8859-1?Q?St=E9phane_Ducasse?=) Date: Wed, 19 Apr 2006 08:28:23 +0200 Subject: http://www.logowiki.net Message-ID: <577FB52D-6BBD-4E91-8ACC-6E18709D22F5@univ-savoie.fr> :) read the about :) From tblanchard at mac.com Wed Apr 19 08:40:19 2006 From: tblanchard at mac.com (Todd Blanchard) Date: Tue, 18 Apr 2006 23:40:19 -0700 Subject: http://www.logowiki.net In-Reply-To: <577FB52D-6BBD-4E91-8ACC-6E18709D22F5@univ-savoie.fr> References: <577FB52D-6BBD-4E91-8ACC-6E18709D22F5@univ-savoie.fr> Message-ID: <7DDA59F3-44AE-427B-A446-BA2DAF030771@mac.com> Pretty cool - the spiral produced a browser hang in safari. I also edited the syntax page to recommend span tags with styles for producing colored text - the font tag is deprecated in modern HTML. :-) On Apr 18, 2006, at 11:28 PM, St?phane Ducasse wrote: > :) > read the about :) > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From hnbeck at t-online.de Wed Apr 19 10:44:54 2006 From: hnbeck at t-online.de (Hans N Beck) Date: Wed, 19 Apr 2006 10:44:54 +0200 Subject: http://www.logowiki.net In-Reply-To: <7DDA59F3-44AE-427B-A446-BA2DAF030771@mac.com> References: <577FB52D-6BBD-4E91-8ACC-6E18709D22F5@univ-savoie.fr> <7DDA59F3-44AE-427B-A446-BA2DAF030771@mac.com> Message-ID: <93355819-CBF8-49C4-8BB8-2A9ED08D4CEC@t-online.de> Hi, reallly coool :-) Very nice, the right thing for my son ;-). It's true, the spiral causes Safari blocking Regards Hans Am 19.04.2006 um 08:40 schrieb Todd Blanchard: > Pretty cool - the spiral produced a browser hang in safari. > > I also edited the syntax page to recommend span tags with styles for > producing colored text - the font tag is deprecated in modern > HTML. :-) > > > > On Apr 18, 2006, at 11:28 PM, St?phane Ducasse wrote: > >> :) >> read the about :) >> >> _______________________________________________ >> 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 From philippe.marschall at gmail.com Wed Apr 19 10:54:52 2006 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Wed, 19 Apr 2006 10:54:52 +0200 Subject: http://www.logowiki.net In-Reply-To: <577FB52D-6BBD-4E91-8ACC-6E18709D22F5@univ-savoie.fr> References: <577FB52D-6BBD-4E91-8ACC-6E18709D22F5@univ-savoie.fr> Message-ID: <66666f210604190154w24bd46b9m8d6b7016856204be@mail.gmail.com> 2006/4/19, St?phane Ducasse : > :) Is it intended that anyone can remove pages? From cdegroot at gmail.com Wed Apr 19 11:04:02 2006 From: cdegroot at gmail.com (Cees De Groot) Date: Wed, 19 Apr 2006 11:04:02 +0200 Subject: http://www.logowiki.net In-Reply-To: <577FB52D-6BBD-4E91-8ACC-6E18709D22F5@univ-savoie.fr> References: <577FB52D-6BBD-4E91-8ACC-6E18709D22F5@univ-savoie.fr> Message-ID: <330b6fd60604190204y41af78afq9929117b2b2d7676@mail.gmail.com> Could be cool, but what browser does it need? It doesn't do a thing on my Firefox 1.0.7 nor on IE 6.0... On 4/19/06, St?phane Ducasse wrote: > :) > read the about :) > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > From philippe.marschall at gmail.com Wed Apr 19 11:14:57 2006 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Wed, 19 Apr 2006 11:14:57 +0200 Subject: http://www.logowiki.net In-Reply-To: <330b6fd60604190204y41af78afq9929117b2b2d7676@mail.gmail.com> References: <577FB52D-6BBD-4E91-8ACC-6E18709D22F5@univ-savoie.fr> <330b6fd60604190204y41af78afq9929117b2b2d7676@mail.gmail.com> Message-ID: <66666f210604190214r66f2fce3p804cd4f75151d085@mail.gmail.com> 2006/4/19, Cees De Groot : > Could be cool, but what browser does it need? It doesn't do a thing on > my Firefox 1.0.7 nor on IE 6.0... AFAIK it uses , this only works on Firefox >= 1.5, Safari 2 (should be in KHTML but I'm not sure) and Opera 9. It can be emulated for IE (PlotKit does that) although it doesn't look like it is done. Cheers Philippe From Hans.Baveco at wur.nl Wed Apr 19 12:02:51 2006 From: Hans.Baveco at wur.nl (Baveco, Hans) Date: Wed, 19 Apr 2006 12:02:51 +0200 Subject: http://www.logowiki.net Message-ID: On IE 6.0 the "Run" button is hidden near the left-bottom corner of the light-blue field, but you see a hand appear (and the balloon-help) when you hoover over it with the cursor. (the invisible Save and Reset buttons are under the left-bottom corner of the logo-code view). Though hidden, the buttons work OK Hans -----Original Message----- From: smallwiki-bounces at iam.unibe.ch [mailto:smallwiki-bounces at iam.unibe.ch] On Behalf Of Cees De Groot Sent: woensdag 19 april 2006 11:04 To: SmallWiki, Magritte, Pier and Related Tools ... Subject: Re: http://www.logowiki.net Could be cool, but what browser does it need? It doesn't do a thing on my Firefox 1.0.7 nor on IE 6.0... On 4/19/06, St?phane Ducasse wrote: > :) > read the about :) > > _______________________________________________ > 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 From giuliano at ime.usp.br Wed Apr 19 16:15:41 2006 From: giuliano at ime.usp.br (Giuliano Mega) Date: Wed, 19 Apr 2006 11:15:41 -0300 Subject: http://www.logowiki.net In-Reply-To: References: Message-ID: <7547a9ff0604190715n28df6529x843c9c262a520844@mail.gmail.com> I guess I inadvertently messed with the spiral page, sorry guys. :-( I tried to modify the logo code to see what happens and, when I clicked "run", it seems that my changes were commited. I never though I'd be saving changes by clicking run. Oh well. I'm very sorry for that. As if it weren't enough that I'm not helping with anything. Giuliano On 4/19/06, Baveco, Hans wrote: > On IE 6.0 the "Run" button is hidden near the left-bottom corner of the light-blue field, but you see a hand appear (and the balloon-help) when you hoover over it with the cursor. (the invisible Save and Reset buttons are under the left-bottom corner of the logo-code view). Though hidden, the buttons work OK > > Hans > > -----Original Message----- > From: smallwiki-bounces at iam.unibe.ch [mailto:smallwiki-bounces at iam.unibe.ch] On Behalf Of Cees De Groot > Sent: woensdag 19 april 2006 11:04 > To: SmallWiki, Magritte, Pier and Related Tools ... > Subject: Re: http://www.logowiki.net > > Could be cool, but what browser does it need? It doesn't do a thing on my Firefox 1.0.7 nor on IE 6.0... > > On 4/19/06, St?phane Ducasse wrote: > > :) > > read the about :) > > > > _______________________________________________ > > 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 > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Giuliano Mega From cputney at wiresong.ca Wed Apr 19 16:34:08 2006 From: cputney at wiresong.ca (Colin Putney) Date: Wed, 19 Apr 2006 10:34:08 -0400 Subject: http://www.logowiki.net In-Reply-To: <7DDA59F3-44AE-427B-A446-BA2DAF030771@mac.com> References: <577FB52D-6BBD-4E91-8ACC-6E18709D22F5@univ-savoie.fr> <7DDA59F3-44AE-427B-A446-BA2DAF030771@mac.com> Message-ID: <5A639794-614D-4165-BC0E-8394E388E65C@wiresong.ca> On Apr 19, 2006, at 2:40 AM, Todd Blanchard wrote: > Pretty cool - the spiral produced a browser hang in safari. There was a syntax error in the logo, and our error handling isn't terribly robust yet. Fixed now. We'll see how long it stays that way. Colin From cputney at wiresong.ca Wed Apr 19 17:04:45 2006 From: cputney at wiresong.ca (Colin Putney) Date: Wed, 19 Apr 2006 11:04:45 -0400 Subject: http://www.logowiki.net In-Reply-To: <7547a9ff0604190715n28df6529x843c9c262a520844@mail.gmail.com> References: <7547a9ff0604190715n28df6529x843c9c262a520844@mail.gmail.com> Message-ID: <7F99F5A1-2A28-40A1-A24F-50D4806DA657@wiresong.ca> On Apr 19, 2006, at 10:15 AM, Giuliano Mega wrote: > I guess I inadvertently messed with the spiral page, sorry guys. :-( > I tried to modify the logo code to see what happens and, when I > clicked "run", it seems that my changes were commited. I never though > I'd be saving changes by clicking run. Oh well. Not to worry. Changes are only committed when you click "Save". Colin From ducasse at iam.unibe.ch Wed Apr 19 17:08:13 2006 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Wed, 19 Apr 2006 17:08:13 +0200 Subject: http://www.logowiki.net In-Reply-To: <5A639794-614D-4165-BC0E-8394E388E65C@wiresong.ca> References: <577FB52D-6BBD-4E91-8ACC-6E18709D22F5@univ-savoie.fr> <7DDA59F3-44AE-427B-A446-BA2DAF030771@mac.com> <5A639794-614D-4165-BC0E-8394E388E65C@wiresong.ca> Message-ID: <271B6E23-88B0-4F57-BAB9-7C6011278AB9@iam.unibe.ch> Hi colin this is nice to see a cool use of pier. Just out of curiosity how the animation are done I noticed that sometimes clicking on a button brings me to smallthought. > On Apr 19, 2006, at 2:40 AM, Todd Blanchard wrote: > >> Pretty cool - the spiral produced a browser hang in safari. > > There was a syntax error in the logo, and our error handling isn't > terribly robust yet. Fixed now. We'll see how long it stays that way. > > Colin > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From ramonleon at cox.net Wed Apr 19 17:09:24 2006 From: ramonleon at cox.net (Ramon Leon) Date: Wed, 19 Apr 2006 08:09:24 -0700 Subject: Dangerous Commands In-Reply-To: References: <44451735.3020305@enit.fr> <4445BFCB.1060808@cox.net> Message-ID: <444652A4.8090202@cox.net> > Pier-All-lr.85 does what you suggest using a simple JavaScript > confirmation dialog. > > Hope this helps, > Lukas PRCommand>>isConfirmed, perfect, thanks! From cputney at wiresong.ca Wed Apr 19 17:38:06 2006 From: cputney at wiresong.ca (Colin Putney) Date: Wed, 19 Apr 2006 11:38:06 -0400 Subject: http://www.logowiki.net In-Reply-To: <271B6E23-88B0-4F57-BAB9-7C6011278AB9@iam.unibe.ch> References: <577FB52D-6BBD-4E91-8ACC-6E18709D22F5@univ-savoie.fr> <7DDA59F3-44AE-427B-A446-BA2DAF030771@mac.com> <5A639794-614D-4165-BC0E-8394E388E65C@wiresong.ca> <271B6E23-88B0-4F57-BAB9-7C6011278AB9@iam.unibe.ch> Message-ID: <93AC3D18-932C-4A7C-98FA-A32B8BF654FB@wiresong.ca> Hi St?phane, > this is nice to see a cool use of pier. > Just out of curiosity how the animation are done Drawing is done using the tag in Safari and Firefox. For IE, is emulated using VML. We implemented the logo interpreter in the browser, using Javascript. The tricky part is slowing down the drawing so that you can see the logo program execute. Javascript has no sleep(), so we used window.setTimeout(). > I noticed that sometimes clicking on a button brings me to > smallthought. Odd. Which button is that? Colin From ssastre at seaswork.com.ar Wed Apr 19 19:35:35 2006 From: ssastre at seaswork.com.ar (=?iso-8859-1?Q?Sebasti=E1n_Sastre?=) Date: Wed, 19 Apr 2006 14:35:35 -0300 Subject: Pier customized look In-Reply-To: <912743092-1144872526-cardhu_blackberry.rim.net-32561-@engine05-cell01.bwc.produk.on.blackberry> Message-ID: Dear Frank, thanks for your answer. As a http server is not available for me at this time, I wonder if I can setup it to get the style from local .css files. Do you know if this is feasible? thanks again, Sebastian > -----Mensaje original----- > De: smallwiki-bounces at iam.unibe.ch > [mailto:smallwiki-bounces at iam.unibe.ch] En nombre de Frank Urbach > Enviado el: Mi?rcoles, 12 de Abril de 2006 17:03 > Para: SmallwikiList > Asunto: AW: Pier customized look > > Hi, Sebasti?n! > > Try to get the original css-files. Move these files into a > structure of an webserver where you can access over. > http-protocoll. Alter in class PRPierLibary the accessor > style to the location of yor css-files.Then you can edit the > file style-contents at point .header .title. Now you can. use > fonts you like. > > Hope this helps. > > Cheers, > Frank, > > -----Original Message----- > From: ssastre at seaswork.com.ar > Date: Wed, 12 Apr 2006 14:39:55 > To:smallwiki at iam.unibe.ch > Subject: Pier customized look > > HI All, > > how do I (in a *polite* fashion) customize the fonts and > header of pier to install a wiki? > > thanks, > > Sebasti?n > > > > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From giuliano.mega at gmail.com Wed Apr 19 20:17:42 2006 From: giuliano.mega at gmail.com (Giuliano Mega) Date: Wed, 19 Apr 2006 15:17:42 -0300 Subject: http://www.logowiki.net In-Reply-To: <7F99F5A1-2A28-40A1-A24F-50D4806DA657@wiresong.ca> References: <7547a9ff0604190715n28df6529x843c9c262a520844@mail.gmail.com> <7F99F5A1-2A28-40A1-A24F-50D4806DA657@wiresong.ca> Message-ID: <7547a9ff0604191117p565afa30k5e057c4bad8c6e3@mail.gmail.com> > Not to worry. Changes are only committed when you click "Save". You might want to double check that. I just performed the following test: 1) changed something silly and clicked run; 2) asked a friend of mine who was in another machine to reload the page. My changes were instantly visible to him. Regards, -- Giuliano Mega From chapbr+pier at sciencegeeks.org Thu Apr 20 03:52:43 2006 From: chapbr+pier at sciencegeeks.org (Brian Chapados) Date: Wed, 19 Apr 2006 18:52:43 -0700 (PDT) Subject: Pier customized look In-Reply-To: References: <912743092-1144872526-cardhu_blackberry.rim.net-32561-@engine05-cell01.bwc.produk.on.blackberry> Message-ID: <50854.137.131.108.94.1145497963.squirrel@webmail.tuffmail.net> Hi Sebastian, I'm in the process of putting together a tutorial that covers this information, along with some other aspects of customizing the appearance of Pier using css. I hope to have it completed soon. Until it's finished, here is some info that should help you: * Configure Comanche to serve files Rather than starting Comanche like this: WAEncodedKom startOn: 8080. Go to http://www.shaffer-consulting.com/david/Seaside/GettingSoftware/index.html and use David Shaffer's scripts to kill all existing server instances and start a new instance that serves file from the 'FileRoot' folder. You can rename 'FileRoot' to whatever you want. Just make sure that the directory you choose is in the same directory as your image file. * Get default stylesheets Download the default stylesheets from here: http://impara.de/pipermail/smallwiki/attachments/20060219/5e4f4ed8/css-0001.zip Create a 'styles' dir under 'FileRoot', and expand the zip file in the styles dir. * Use the new stylesheets Change the style accessor method in PRStyleLibrary to return the path to your main style sheet style ^ '@import "/styles/style.css";' Brian > Dear Frank, > > thanks for your answer. As a http server is not available for me at > this time, I wonder if I can setup it to get the style from local .css > files. Do you know if this is feasible? > > thanks again, > > Sebastian > >> -----Mensaje original----- >> De: smallwiki-bounces at iam.unibe.ch >> [mailto:smallwiki-bounces at iam.unibe.ch] En nombre de Frank Urbach >> Enviado el: Mi?rcoles, 12 de Abril de 2006 17:03 >> Para: SmallwikiList >> Asunto: AW: Pier customized look >> >> Hi, Sebasti?n! >> >> Try to get the original css-files. Move these files into a >> structure of an webserver where you can access over. >> http-protocoll. Alter in class PRPierLibary the accessor >> style to the location of yor css-files.Then you can edit the >> file style-contents at point .header .title. Now you can. use >> fonts you like. >> >> Hope this helps. >> >> Cheers, >> Frank, >> >> -----Original Message----- >> From: ssastre at seaswork.com.ar >> Date: Wed, 12 Apr 2006 14:39:55 >> To:smallwiki at iam.unibe.ch >> Subject: Pier customized look >> >> HI All, >> >> how do I (in a *polite* fashion) customize the fonts and >> header of pier to install a wiki? >> >> thanks, >> >> Sebasti?n >> >> >> >> >> >> >> _______________________________________________ >> 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 > > From stephane.ducasse at univ-savoie.fr Mon Apr 24 17:11:06 2006 From: stephane.ducasse at univ-savoie.fr (=?ISO-8859-1?Q?St=E9phane_Ducasse?=) Date: Mon, 24 Apr 2006 17:11:06 +0200 Subject: Any taker to build the same on top of magritte Message-ID: <92C091BD-9979-419A-919E-60533812602C@univ-savoie.fr> http://developer.apple.com/cocoa/coredatatutorial/ From cbeler at enit.fr Mon Apr 24 20:00:05 2006 From: cbeler at enit.fr (=?ISO-8859-1?Q?C=E9drick_B=E9ler?=) Date: Mon, 24 Apr 2006 20:00:05 +0200 Subject: use of reference in a MARelationDescription Message-ID: <444D1225.20102@enit.fr> Hi :) I try to use a MARelationDescription with an object that fetch its description automatically from instances... and I have a problem... To illustrate, let's take the Magritte tutorial example with 2 model classes MAPersonModel and MAAdressModel. In MAPersonModel we have an inst var homeAdress with the corresponding description on the class side: MAPersonModel class>>descriptionHomeAddress ^ (MAToOneRelationDescription auto: 'homeAddress' label: 'Home Address' priority: 40) componentClass: MAInternalEditorComponent; classes: (Array with: MAAddressModel); yourself. and that is enough because MAAdressModel has its descriptions defined (class side). But if descriptions were accessed from instance of MAAdressModel like: MAAdressModel>>descriptionGenerated ^MAPriorityDescription new add: (MAStringDescription auto: 'street' label: 'Street' priority: 10); add: (MAStringDescription auto: 'place' label: 'Place' priority: 30); ... yourself. Then I was thinking it was possible to create the previous description in the following way (say there are no more desciption in the class side of MAAdressModel): MAPersonModel class>>descriptionHomeAddress ^ (MAToOneRelationDescription auto: 'homeAddress' label: 'Home Address' priority: 40) ***reference: MAAdessModel new descriptionGenerated;*** componentClass: MAInternalEditorComponent; classes: (Array with: MAAddressModel); *no more description in the class side of MAAddressModel* yourself. I know in this exemple, the interest of doing that is not obvious but this is because in my case, I have specific description for instances (one part is general whereas the other is created with values affected to the object). Is it possible to do that way ? what is the correct use of #reference: for a MARelationDescription ? choosing a kind of container ? Is there a built-in way to use different descriptions (filtered for instance) than the one accessed from the classe that are in ToOne or ToMany relation ? Thank you C?drick From damien.cassou at laposte.net Mon Apr 24 22:04:36 2006 From: damien.cassou at laposte.net (Damien Cassou) Date: Mon, 24 Apr 2006 22:04:36 +0200 Subject: use of reference in a MARelationDescription In-Reply-To: <444D1225.20102@enit.fr> References: <444D1225.20102@enit.fr> Message-ID: <444D2F54.3040407@laposte.net> Hi, I'm not sure it will help, but did you had a look to MADynamicObject (and the #on: method implement in MAProxyObject) ? -- Damien Cassou From rleon at insario.com Tue Apr 25 18:37:15 2006 From: rleon at insario.com (Ramon Leon) Date: Tue, 25 Apr 2006 09:37:15 -0700 Subject: Deep linking Message-ID: <24C40DFA333DC44882F9FB0115F33D8F49A500@ARGON.insario.local> Hi, where is the code that pier uses to deep link into a site? I have a few installations that seem to have lost the ability to deep link, despite being the latest code, yet deep link just fine if I create a new site. Thought I could save a little time if someone already had the issue, or knows that bit of code. From renggli at iam.unibe.ch Wed Apr 26 03:37:10 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 25 Apr 2006 21:37:10 -0400 Subject: Deep linking In-Reply-To: <24C40DFA333DC44882F9FB0115F33D8F49A500@ARGON.insario.local> References: <24C40DFA333DC44882F9FB0115F33D8F49A500@ARGON.insario.local> Message-ID: <15EE582D-9AD5-4D15-B2A0-99AEC937118D@iam.unibe.ch> > Hi, where is the code that pier uses to deep link into a site? I > have a > few installations that seem to have lost the ability to deep link, > despite being the latest code, yet deep link just fine if I create > a new > site. Thought I could save a little time if someone already had the > issue, or knows that bit of code. Mhh, not much changed in this area for the past few months. The last big change was to make a difference between the title and the name of a page, but the lookup should work for name and title, check-out the mailing-list archive. Can you give some more hints what is not properly working? There are also tests that check all kinds of deep- and relative linking. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From rleon at insario.com Wed Apr 26 19:12:16 2006 From: rleon at insario.com (Ramon Leon) Date: Wed, 26 Apr 2006 10:12:16 -0700 Subject: Deep linking Message-ID: <24C40DFA333DC44882F9FB0115F33D8F49A51A@ARGON.insario.local> > > Hi, where is the code that pier uses to deep link into a > site? I have > > a few installations that seem to have lost the ability to > deep link, > > despite being the latest code, yet deep link just fine if I > create a > > new site. Thought I could save a little time if someone > already had > > the issue, or knows that bit of code. > > Mhh, not much changed in this area for the past few months. > The last big change was to make a difference between the > title and the name of a page, but the lookup should work for > name and title, check-out the mailing-list archive. > > Can you give some more hints what is not properly working? > There are also tests that check all kinds of deep- and > relative linking. > > Cheers, > Lukas I'll see if I can take a look at it tonight, at the moment, I only know it's not working, but haven't fired up the debugger yet. From ramonleon at cox.net Thu Apr 27 03:59:06 2006 From: ramonleon at cox.net (Ramon Leon) Date: Wed, 26 Apr 2006 18:59:06 -0700 Subject: Deep linking In-Reply-To: <24C40DFA333DC44882F9FB0115F33D8F49A51A@ARGON.insario.local> References: <24C40DFA333DC44882F9FB0115F33D8F49A51A@ARGON.insario.local> Message-ID: <4450256A.2030502@cox.net> >>Mhh, not much changed in this area for the past few months. >>The last big change was to make a difference between the >>title and the name of a page, but the lookup should work for >>name and title, check-out the mailing-list archive. >> >>Can you give some more hints what is not properly working? >>There are also tests that check all kinds of deep- and >>relative linking. >> >>Cheers, >>Lukas Ok, solved, turned out I didn't have my base path set to just /, had /site. Set default entry points and then base path to just /, all is well. From ramonleon at cox.net Fri Apr 28 08:56:38 2006 From: ramonleon at cox.net (Ramon Leon) Date: Thu, 27 Apr 2006 23:56:38 -0700 Subject: SSL In-Reply-To: <24C40DFA333DC44882F9FB0115F33D8F49A500@ARGON.insario.local> References: <24C40DFA333DC44882F9FB0115F33D8F49A500@ARGON.insario.local> Message-ID: <4451BCA6.6040107@cox.net> OK, I've got Pier running behind Apache, responding to both http and https via OpenSSL, but I'm running into a problem. All the generated url's are fully qualified, so though it'll respond to SSL, as soon as I click something I'm thrown back into standard http. I figured this had to be common, but after digging around in the archives for a while, I've found nothing that panned out. Now, I can see that Server Protocol is set to http in the site configuration. Can a site only run in one mode or the other? What if I only want two pages to be secure for a checkout but the rest of the site unsecured? I don't know, maybe it's just late and I'm making a simple mistake, but I'm stumped, anyone know how to deal with this? -- Ramon Leon From renggli at iam.unibe.ch Sat Apr 29 23:38:01 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sat, 29 Apr 2006 17:38:01 -0400 Subject: Pier user in context In-Reply-To: <592AC73A-5A71-47B7-BEC1-FB1846CF481B@t-online.de> References: <592AC73A-5A71-47B7-BEC1-FB1846CF481B@t-online.de> Message-ID: <2739B88A-DB19-420A-9823-EFF372B0270C@iam.unibe.ch> Hi Hans, > hope you have has a nice trip to Toronto :-) yep, Canada is great! The Pier & Magritte presentation was a success. > One Question: in the PRContext>>user, there will be set property > user to nil if this property does not exist. Could that be > dangorous ? Should there be set some default user with smallest > rights ? (And should this user come from PRKernel as the smallest > user in current kernel or come from PRUser class as the smallest > thinkable user ?) Yeah, this is not a nice design. Similar as the 'admin' user and 'admin' role, there should be an 'anonymous' user and an 'anonymous' role. There are several checks for nil now, what makes it quite ugly in the oo-world, however I don't think this imposes any security risk ;-) I will have a look at this as soon as possible. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Sun Apr 30 21:55:38 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 30 Apr 2006 15:55:38 -0400 Subject: Pier user in context In-Reply-To: <590EAD3C-B0A1-4815-9B76-FDF561C9ADD3@t-online.de> References: <592AC73A-5A71-47B7-BEC1-FB1846CF481B@t-online.de> <2739B88A-DB19-420A-9823-EFF372B0270C@iam.unibe.ch> <590EAD3C-B0A1-4815-9B76-FDF561C9ADD3@t-online.de> Message-ID: > For security and web, I'm a little bit paranoid, especially at > such powerful systems like Pier ;-) I've discussed security in > Seaside/Pier with a friend, and from this I'm not sure today what I > expect from such systems like seaside/pier. He says, security > belongs only to buisness logic. I'm not so shure, also what to call > buisness logic in Pier...... I will post a related question to the > list later. If your friend means "model" when talking about "business logic", he is right: the security decoration is a pure model object, that works exactly the same for all views, not just seaside one. Thanks to the nature of visitors one can easily control how security concerns are handled when performing operations. > You could help me understand the code answering the following > question: in your security package, every structure element > (decorator or the decorated element) has an owner, and the the > rights of that owner decide what is possible (that the UNIX way, I > think). Is that right ? Yes, the code modeling the unix permissions is quite simple to read, of course you can tweak that behavior if you need to. I think it comes quite close what unix does, but I no unix expert. SUSecurity>>isAllowedCommand: aCommandClass in: aContext (aContext user notNil and: [ aContext user isSuperuser ]) ifTrue: [ ^ true ]. (self owner = aContext user) ifTrue: [ ^ self ownerCommands includes: aCommandClass ]. (self group notNil and: [ self group includes: aContext user ]) ifTrue: [ ^ self groupCommands includes: aCommandClass ]. ^ self otherCommands includes: aCommandClass > But what about the commandos: is the security given by existence > (only the commandos in structure exist, which are executable) or by > right for execution for every commando (as in UNIX file system) ? > That I have not understand until now. I am not quite sure if I understand your question, maybe you can deduce the answer from the above code yourself? Basically every security decoration knows a list of all allowed commands for the owner, the group and all the others, like the unix "rwx", but for all available commands in the system. The security decoration does not care what it decorates, e.g, when giving the permission to admin to remove the root page, he still won't be able to do that simply because the remove-command does not work on the root, something that is enforced by the command itself. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch