From squeakman at gmail.com Sun Jun 1 18:13:27 2008 From: squeakman at gmail.com (Squeaker) Date: Sun, 01 Jun 2008 12:13:27 -0400 Subject: MAReport - question on #refresh Message-ID: Greetings, I am learning Magritte and following the exercises that Lukas has in his tutorial. I am stuck on Exercise 12. > Exercise 12 When having tested the new report, you have probably > noticed that the report doesn?t update itself when adding new persons, > call #refresh to do so. When I send #refresh to aMAReport nothing happens. (I attempted to trace thru the code but cannot figure out what is going wrong.) I appreciate any help you can offer. Thanks, Frank From renggli at iam.unibe.ch Thu Jun 5 13:32:15 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Thu, 5 Jun 2008 13:32:15 +0200 Subject: a couple of questions on magritte In-Reply-To: <9aa6ae270805290722w6d054516u74c287b49f94c434@mail.gmail.com> References: <9aa6ae270805290722w6d054516u74c287b49f94c434@mail.gmail.com> Message-ID: <4B2312AC-3211-4182-9A14-BF61E825603F@iam.unibe.ch> >> -How do I add a "caption" (title) to a form created with >> "asComponent". I can add a decoration, but I wonder if there are a >> more "standard" way. That's the standard ;-) Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Thu Jun 5 13:48:34 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Thu, 5 Jun 2008 13:48:34 +0200 Subject: MAReport - question on #refresh In-Reply-To: References: Message-ID: <8E9742EE-669F-45E5-B342-CAC1F3B74EE8@iam.unibe.ch> Hi Frank, > I am learning Magritte and following the exercises that Lukas has in > his > tutorial. I am stuck on Exercise 12. > >> Exercise 12 When having tested the new report, you have probably >> noticed that the report doesn?t update itself when adding new > persons, > call #refresh to do so. > > When I send #refresh to aMAReport nothing happens. (I attempted to > trace > thru the code but cannot figure out what is going wrong.) > > I appreciate any help you can offer. Thank you for reporting, I believe that this is a bug. Try loading the latest version of Magritte-Seaside and the problem should disappear. As a workaround you could also re-assign the collection of elements to the report using #rows:. Hope this helps, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From estebanlm at gmail.com Thu Jun 5 14:46:52 2008 From: estebanlm at gmail.com (Esteban Lorenzano) Date: Thu, 5 Jun 2008 09:46:52 -0300 Subject: Grouping blogs Message-ID: <1A52EA88-73E1-4D58-BC8A-78D8E936B82B@gmail.com> Hi, I want to add a "grouping blogs" feature to my "in construction" page (http://www.smallworks.com.ar ), and a group rss feeder, such as that one on seaside site... which addon is it? Thanks, Esteban "Querer es suscitar las paradojas" Camus - El mito de S?sifo From renggli at iam.unibe.ch Thu Jun 5 16:06:44 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Thu, 5 Jun 2008 16:06:44 +0200 Subject: Grouping blogs In-Reply-To: <1A52EA88-73E1-4D58-BC8A-78D8E936B82B@gmail.com> References: <1A52EA88-73E1-4D58-BC8A-78D8E936B82B@gmail.com> Message-ID: > I want to add a "grouping blogs" feature to my "in construction" > page (http://www.smallworks.com.ar > ), and a group rss feeder, such as that one on seaside site... which > addon is it? Wow, very cool web-site, although I don't understand much. The blog plugin comes with the 'Post Ticker' component. You can probably subclass it easily to aggregate multiple blog instances on the same Pier installation. The plugin used on seaside.st is more complicated, because it aggregates external blogs. It is called TopFeeder (as opposed to BottomFeeder) and you find it in the pieraddons repository. It is a bit difficult to work with, because properly decoding and parsing feeds is quite hard. Load first the Audioscrobbler plugin from the same repository. You are also required to load XML-Parser from SqueakSource. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From squeakman at gmail.com Fri Jun 6 20:02:19 2008 From: squeakman at gmail.com (Squeaker) Date: Fri, 06 Jun 2008 14:02:19 -0400 Subject: Magritte - how to add Submit Buttons to a form Message-ID: Hello, I am using Magritte to display a standard form for my model. I have code that looks like this: form := self asComponent addValidatedForm; yourself; html render: form. This gives me a nice form with the standard 'Save' and 'Cancel' buttons. I would like to add an additional button to the form. I see that MAContainerComponent>>#addValidatedForm is where the Save and Cancel buttons are added but I cannot figure out how to add my own button so that it appears in the same div as the Save and Cancel buttons. How do I add a new button to the form? Thanks for any help you can provide, Frank From renggli at iam.unibe.ch Fri Jun 6 20:08:21 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 6 Jun 2008 20:08:21 +0200 Subject: Magritte - how to add Submit Buttons to a form In-Reply-To: References: Message-ID: <222AD76D-C1AF-4842-AF8F-29097966D276@iam.unibe.ch> > How do I add a new button to the form? Replace #addValidatedForm with something like: addValidatedForm: #( save cancel apply ) Then add the method #apply as an extension method to MAContainerComponent. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From keith_hodges at yahoo.co.uk Mon Jun 9 19:48:38 2008 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Mon, 09 Jun 2008 18:48:38 +0100 Subject: chainTo: and chainUnlinkLast Message-ID: <484D6CF6.70308@yahoo.co.uk> Dear Lukas, your rewrite of MAChainAccessor provoked some panic here! Just to let you know that I had written a couple of chaining and unchaining operaterations, which I use for mapping a flat db query into a magritte model. It allows me to treat a chain accessor as a kind of stack as the model is traversed. These are #last #chainTo: #chainUnlinkLast: I thought that you might be interested in adopting these (now they are fixed for the latest) as utilities into MA-Model. If you are interested then you will find them in the latest Magritte-RDB package in magritte addons. best regards Keith From renggli at iam.unibe.ch Mon Jun 9 22:04:16 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 9 Jun 2008 22:04:16 +0200 Subject: chainTo: and chainUnlinkLast In-Reply-To: <484D6CF6.70308@yahoo.co.uk> References: <484D6CF6.70308@yahoo.co.uk> Message-ID: <8027B2EA-D3D8-4C77-B30B-77DA1F8AA226@iam.unibe.ch> Hi Keith, > your rewrite of MAChainAccessor provoked some panic here! sorry, I didn't expect that anybody was using those. I think with the refactoring they became more useful, especially since you don't need to know anymore about the details. You can now just write aDescription accessor: #foo and it will automatically create the appropriate accessor object for you. The same for aDescription accessor: #(foo bar) will chain #foo to #bar. > Just to let you know that I had written a couple of chaining and > unchaining operaterations, which I use for mapping a flat db query > into a magritte model. It allows me to treat a chain accessor as a > kind of stack as the model is traversed. I don't know if that is useful in general? If you think so, please feel free to add it to Magritte-Core. I saw that you use it to build a stack. Wouldn't it be much simpler if you just kept the selectors in an OrderedCollection and sent #asAccessor if required? Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From keith_hodges at yahoo.co.uk Tue Jun 10 03:24:23 2008 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Tue, 10 Jun 2008 02:24:23 +0100 Subject: chainTo: and chainUnlinkLast In-Reply-To: <8027B2EA-D3D8-4C77-B30B-77DA1F8AA226@iam.unibe.ch> References: <484D6CF6.70308@yahoo.co.uk> <8027B2EA-D3D8-4C77-B30B-77DA1F8AA226@iam.unibe.ch> Message-ID: <484DD7C7.6090204@yahoo.co.uk> Lukas Renggli wrote: > Hi Keith, > > >> your rewrite of MAChainAccessor provoked some panic here! >> > > sorry, I didn't expect that anybody was using those. > > I think with the refactoring they became more useful, especially since > you don't need to know anymore about the details. You can now just write > > aDescription accessor: #foo > > and it will automatically create the appropriate accessor object for > you. The same for > > aDescription accessor: #(foo bar) > > will chain #foo to #bar. > > >> Just to let you know that I had written a couple of chaining and >> unchaining operaterations, which I use for mapping a flat db query >> into a magritte model. It allows me to treat a chain accessor as a >> kind of stack as the model is traversed. >> > > I don't know if that is useful in general? If you think so, please > feel free to add it to Magritte-Core. I saw that you use it to build a > stack. Wouldn't it be much simpler if you just kept the selectors in > an OrderedCollection and sent #asAccessor if required? > I have to say that this is a very bumpy migration! I have over 900 existing instances and the new implementation is reversing the instVars. At present I am attempting to reverse them by hand but it is tricky. Keith From evaklo at gmail.com Tue Jun 10 16:48:49 2008 From: evaklo at gmail.com (=?ISO-8859-1?Q?Lautaro_Fern=E1ndez?=) Date: Tue, 10 Jun 2008 11:48:49 -0300 Subject: Permalinks Message-ID: <36ce93cf0806100748h35161bc9r738e90a48c136486@mail.gmail.com> Hi list, I wonder if someone has implemented a permalink for Pier, because if I have a link like this http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Smalltalks+servers?_s=123xyz&_k=zyx123&_n&22 I could make a permalink like this: http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Smalltalks%20servers Which is: a) changing all the "+" for a "%20" b) and erasing from "?" to the end of the string And the (new) generated URL does work and it's shareable with others browsers/people. If not, where should I put this to "pre" generate permalinks for all pages, and show them properly (like the one in the image http://i296.photobucket.com/albums/mm197/evaklo/permalink.png )? Thanks for your time, Lautaro Fern?ndez -- Luke LAut SkyFernadezWalker -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20080610/af3c7e77/attachment.html From renggli at iam.unibe.ch Tue Jun 10 19:49:23 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 10 Jun 2008 19:49:23 +0200 Subject: Permalinks In-Reply-To: <36ce93cf0806100748h35161bc9r738e90a48c136486@mail.gmail.com> References: <36ce93cf0806100748h35161bc9r738e90a48c136486@mail.gmail.com> Message-ID: <3AD54693-947E-4FAA-A8C9-C1AD8D774D2E@iam.unibe.ch> > I wonder if someone has implemented a permalink for Pier, because if > I have a link like this > http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Smalltalks+servers?_s=123xyz&_k=zyx123&_n&22 This is actually a permalink. There is some noise after the ? that you can ignore. If people bookmark the link or send it around, that's no problem. > I could make a permalink like this: > http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Smalltalks%20servers This is the same permalink as above. > Which is: > a) changing all the "+" for a "%20" > b) and erasing from "?" to the end of the string a) As far as i know, this modification doesn't change anything about the link, it is just a different encoding. The resulting URL is the same. b) As long as you only remove the _s, _k, _n and [0-9]+ keys that doesn't change anything, you will only loose the session information. The blog component actually does something like that to display a nicer link. > And the (new) generated URL does work and it's shareable with others > browsers/people. If not, where should I put this to "pre" generate > permalinks for all pages, and show them properly (like the one in > the image http://i296.photobucket.com/albums/mm197/evaklo/permalink.png > )? Doing absolutely clean URLs is possible, however it requires some heavy Seaside hackery to avoid loosing functionality. Unfortunately my time working on Pier is very limited at the moment. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From evaklo at gmail.com Wed Jun 11 01:54:16 2008 From: evaklo at gmail.com (=?ISO-8859-1?Q?Lautaro_Fern=E1ndez?=) Date: Tue, 10 Jun 2008 20:54:16 -0300 Subject: Permalinks In-Reply-To: <3AD54693-947E-4FAA-A8C9-C1AD8D774D2E@iam.unibe.ch> References: <36ce93cf0806100748h35161bc9r738e90a48c136486@mail.gmail.com> <3AD54693-947E-4FAA-A8C9-C1AD8D774D2E@iam.unibe.ch> Message-ID: <36ce93cf0806101654x1b6ba71m37d21b71f22a3b9b@mail.gmail.com> Hi Lukas, 2008/6/10 Lukas Renggli : > >[...] > > > http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Smalltalks+servers?_s=123xyz&_k=zyx123&_n&22 > > This is actually a permalink. There is some noise after the ? that you > can ignore. If people bookmark the link or send it around, that's no > problem. Sorry to disagree with you, but that link isn't shareable (the one which has the "+" instead of the "%20"). Now I'm at home, and if I click it I got the following error: *Error: "/seaside/go/pier/Wiki/Smalltalks+servers" not found.* So there must be a problem with Seaside or maybe Pier. The URL I can see after clicking is: http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Smalltalks%2Bservers Notice that the "+" has changed into a "%2B", which is a "+" in ASCII code, and it seems that Pier can't process it in a good way. That is because the page name isn't "Smalltalks+servers", actually is "Smalltalks servers". > > I could make a permalink like this: > > > http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Smalltalks%20servers > > This is the same permalink as above. This link (with the %20) is showed properly here, in my home. Do you think that my installation of Pier (or maybe Seaside) isn't working well? > > Which is: > > a) changing all the "+" for a "%20" > > b) and erasing from "?" to the end of the string > > a) As far as i know, this modification doesn't change anything about > the link, it is just a different encoding. The resulting URL is the > same. > b) As long as you only remove the _s, _k, _n and [0-9]+ keys that > doesn't change anything, you will only loose the session information. > The blog component actually does something like that to display a > nicer link. > > > And the (new) generated URL does work and it's shareable with others > > browsers/people. If not, where should I put this to "pre" generate > > permalinks for all pages, and show them properly (like the one in > > the image http://i296.photobucket.com/albums/mm197/evaklo/permalink.png > > )? > > Doing absolutely clean URLs is possible, however it requires some > heavy Seaside hackery to avoid loosing functionality. Unfortunately my > time working on Pier is very limited at the moment. But if you insert a link like this: http://yourHost:aPort/seaside/go/pier/Wiki/Talks , the part of "/pier/Wiki/Talks" is traceable, so if you click http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Talks you will be able to see the "Talks" page in Pier. Isn't this an absolutely clean URL for the "Talks" page? Cheers, > Lukas Thanks in advance for your answers, Lautaro Fern?ndez -- Luke LAut SkyFernadezWalker -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20080611/c703b3e2/attachment.html From renggli at iam.unibe.ch Wed Jun 11 07:58:41 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Wed, 11 Jun 2008 07:58:41 +0200 Subject: Permalinks In-Reply-To: <36ce93cf0806101654x1b6ba71m37d21b71f22a3b9b@mail.gmail.com> References: <36ce93cf0806100748h35161bc9r738e90a48c136486@mail.gmail.com> <3AD54693-947E-4FAA-A8C9-C1AD8D774D2E@iam.unibe.ch> <36ce93cf0806101654x1b6ba71m37d21b71f22a3b9b@mail.gmail.com> Message-ID: > So there must be a problem with Seaside or maybe Pier. The URL I can > see after clicking is: > http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Smalltalks%2Bservers > Notice that the "+" has changed into a "%2B", which is a "+" in > ASCII code, and it seems that Pier can't process it in a good way. > That is because the page name isn't "Smalltalks+servers", actually > is "Smalltalks servers". I only realize now that you are on VisualWorks. Looks like a bug in the request parsing and URL decoding there. It works without problems in Squeak, no matter if I use + or %20 in my URLs. > But if you insert a link like this: http://yourHost:aPort/seaside/go/ > pier/Wiki/Talks , the part of "/pier/Wiki/Talks" is traceable, so > if you click http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Talks > you will be able to see the "Talks" page in Pier. > Isn't this an absolutely clean URL for the "Talks" page? Yes, it is. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From evaklo at gmail.com Wed Jun 11 08:25:49 2008 From: evaklo at gmail.com (=?ISO-8859-1?Q?Lautaro_Fern=E1ndez?=) Date: Wed, 11 Jun 2008 03:25:49 -0300 Subject: Permalinks In-Reply-To: References: <36ce93cf0806100748h35161bc9r738e90a48c136486@mail.gmail.com> <3AD54693-947E-4FAA-A8C9-C1AD8D774D2E@iam.unibe.ch> <36ce93cf0806101654x1b6ba71m37d21b71f22a3b9b@mail.gmail.com> Message-ID: <36ce93cf0806102325n17c88ffbp2e50eddd431507f5@mail.gmail.com> 2008/6/11 Lukas Renggli : > > So there must be a problem with Seaside or maybe Pier. The URL I can > > see after clicking is: > > > > http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Smalltalks%2Bservers > > Notice that the "+" has changed into a "%2B", which is a "+" in > > ASCII code, and it seems that Pier can't process it in a good way. > > That is because the page name isn't "Smalltalks+servers", actually > > is "Smalltalks servers". > > I only realize now that you are on VisualWorks. Looks like a bug in > the request parsing and URL decoding there. It works without problems > in Squeak, no matter if I use + or %20 in my URLs. > Ok, thanks. I'll try to find the way to fix this. > > > But if you insert a link like this: http://yourHost:aPort/seaside/go/ > > pier/Wiki/Talks , the part of "/pier/Wiki/Talks" is traceable, so > > if you click > http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Talks > > you will be able to see the "Talks" page in Pier. > > Isn't this an absolutely clean URL for the "Talks" page? > > Yes, it is. > =] Thanks, Lautaro > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Luke LAut SkyFernadezWalker -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20080611/b0fe78fb/attachment-0001.html From merlyn at stonehenge.com Wed Jun 11 15:17:59 2008 From: merlyn at stonehenge.com (Randal L. Schwartz) Date: Wed, 11 Jun 2008 06:17:59 -0700 Subject: Permalinks In-Reply-To: (Lukas Renggli's message of "Wed, 11 Jun 2008 07:58:41 +0200") References: <36ce93cf0806100748h35161bc9r738e90a48c136486@mail.gmail.com> <3AD54693-947E-4FAA-A8C9-C1AD8D774D2E@iam.unibe.ch> <36ce93cf0806101654x1b6ba71m37d21b71f22a3b9b@mail.gmail.com> Message-ID: <86iqwgyut4.fsf@blue.stonehenge.com> >>>>> "Lukas" == Lukas Renggli writes: Lukas> I only realize now that you are on VisualWorks. Looks like a bug in Lukas> the request parsing and URL decoding there. It works without problems Lukas> in Squeak, no matter if I use + or %20 in my URLs. >From the very early days in the web, + and %20 have been considered interchangeable in a URL. However, it's an easy part of the spec to overlook, or an easy thing not to know if you haven't been around since the early days. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion From keith_hodges at yahoo.co.uk Thu Jun 12 04:22:10 2008 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Thu, 12 Jun 2008 03:22:10 +0100 Subject: [Ann] Pier-Jetsam-Environment with Themeable classic Pier 1.0.0 ui In-Reply-To: <483AA688.4020806@yahoo.co.uk> References: <483AA688.4020806@yahoo.co.uk> Message-ID: <48508852.5060208@yahoo.co.uk> In the Pier-Jetsam-Environment package, I have moved the "layout settings" group of definitions out of PRStructure, since the structure itself doesn't need to know anything about how it is to be displayed. Instead the chosen parent frame can add its own "layout settings" descriptions to structures. As an example of how this works, the "admin" frame adds a "Theme Color" setting, other frames add settings according to their own needs. I am now attempting and failing to put a link to the PRSettingsCommand in the seaside toolbar, is this possible? cheers Keith > Hello All, > > Pier-Jetsam-Environment moves all configuration and initialization of a > pier kernel to subclasses of PRPierFrame. > > 1. Just switch your seaside application's PRPierFrame component to > switch to a different style and layout (even switch to a different style > framework). > > 2. Set up a second entry point to your Pier instance with a different > style. e.g. http://admin.mypier.example > this allows a simple way to support admin users without needing > Pier-Security. > > 3. Embed your pier instance in another seaside app, with a specialised > style for that app as provided by the root frame component that you > choose to embed. > > 4. The standard scheme of user editable environments still works as > before except that new environments get auto initialized. > > enjoy > > Keith > > p.s. feedback invited > > =========== > > > PRPierFrameStandardBP > ================== > The same policies and layout as the current pier release, except that no > 'environment' is initially needed. If you provide 'environment' with > empty contents it will be initialized automatically. > > PRPierFrameNewBP > ================ > As above except that the layout is obtained/initialized in > $environment/layout > > > PRPierFrameCWS and subclasses > ======================== > > As above except that the style framework is based upon "Content With > Style" css framework. > The framework uses a single layout definition, but provides a number of > common layouts via CSS variants. > > The options are > > "#layout1colCss > " #layoutnavtopsubrightCss > "#layoutnavtop3colCss > "" #layoutnavtop1colCss > "" #layoutnavleft1colCss > "" #layoutnavleft2colCss > "" #layoutnavtoplocalleftCss > " > see: http://www.contentwithstyle.co.uk/Articles/17/a-css-framework > > PRPierFrameAdminBP - Themeable classic pier 1.0.0 ui > ======================================== > The old classic pier admin UI (including the tree navigation widget) > > All colors in css are referenced to method selectors for easy theming. > (Subclass and override #colorMethods) > Updated to use "Nifty Corners" so that rounded corners show in Internet > Explorer. > Updated to use transparent png, so that the color of the banner and the > logo can be changed in a single method. > > There is still a little bit of work to get the css working cross browser > > feedback as always appreciated > > Keith > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > From renggli at iam.unibe.ch Thu Jun 12 11:08:44 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Thu, 12 Jun 2008 11:08:44 +0200 Subject: [Ann] Pier-Jetsam-Environment with Themeable classic Pier 1.0.0 ui In-Reply-To: <48508852.5060208@yahoo.co.uk> References: <483AA688.4020806@yahoo.co.uk> <48508852.5060208@yahoo.co.uk> Message-ID: > In the Pier-Jetsam-Environment package, I have moved the "layout > settings" group of definitions out of PRStructure, since the structure > itself doesn't need to know anything about how it is to be displayed. Why not? I have websites where every top level structure has its own look. > I am now attempting and failing to put a link to the PRSettingsCommand > in the seaside toolbar, is this possible? Ouch, Seaside Toolbar? I usually keep that disabled. Sure, you can render a link to a specific Pier page from any Seaside component. Assuming that "self context" is the current context you can write: html anchor goto: (self context command: PRSettingsCommand); with: 'Settings' Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From keith_hodges at yahoo.co.uk Thu Jun 12 15:44:29 2008 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Thu, 12 Jun 2008 14:44:29 +0100 Subject: [Ann] Pier-Jetsam-Environment with Themeable classic Pier 1.0.0 ui In-Reply-To: References: <483AA688.4020806@yahoo.co.uk> <48508852.5060208@yahoo.co.uk> Message-ID: <4851283D.6020401@yahoo.co.uk> Lukas Renggli wrote: >> In the Pier-Jetsam-Environment package, I have moved the "layout >> settings" group of definitions out of PRStructure, since the structure >> itself doesn't need to know anything about how it is to be displayed. >> > > Why not? I have websites where every top level structure has its own > look. > Sure that's what I do too. But the structure itself has nothing to do with determining its usage or look. It does keep hold of arbitrary properties, but those properties are specified by the "frame" that is going to be displaying the structure, not by the structure itself. As an example the "AdminFrame" stores the current theme colour in the structure's properties. Since the "AdminFrame" has a fixed layout determined by the class, there is no need for structures to have an #environment or #stylesheet setting wen displayed with the "AdminFrame" The "ContentWithStyle" frame stores the current layout selection in the structures properties, there are 7 choices. 1 col, 2 col, 3 col etc etc. So in my model, structures have their properties, which the display frame may make use of. However Structures have no knowledge of their own as to how they are to be used. Its the same "children" shouldnt know too much about their "parents" use-cases issue. >> I am now attempting and failing to put a link to the PRSettingsCommand >> in the seaside toolbar, is this possible? >> > > Ouch, Seaside Toolbar? I usually keep that disabled. > I agree it would be simpler if it was factored out... I have factored it out into a decoration-helper. I am still hoping that you will see your way to support Session/Decoration helpers in 2.9. For me the Toolbar decoration becomes enabled via the ToolbarHelper when a suitably qualified user logs in. > Sure, you can render a link to a specific Pier page from any Seaside > component. Assuming that "self context" is the current context you can > write: > > html anchor > goto: (self context command: PRSettingsCommand); > with: 'Settings' > > Unfortunately the WAToolbar frame is outside of withContextDo: So I dont think that this will work. Keith From renggli at iam.unibe.ch Thu Jun 12 16:15:48 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Thu, 12 Jun 2008 16:15:48 +0200 Subject: [Ann] Pier-Jetsam-Environment with Themeable classic Pier 1.0.0 ui In-Reply-To: <4851283D.6020401@yahoo.co.uk> References: <483AA688.4020806@yahoo.co.uk> <48508852.5060208@yahoo.co.uk> <4851283D.6020401@yahoo.co.uk> Message-ID: >>> In the Pier-Jetsam-Environment package, I have moved the "layout >>> settings" group of definitions out of PRStructure, since the >>> structure >>> itself doesn't need to know anything about how it is to be >>> displayed. >>> >> >> Why not? I have websites where every top level structure has its own >> look. >> > Sure that's what I do too. > > But the structure itself has nothing to do with determining its > usage or > look. It does keep hold of arbitrary properties, but those properties > are specified by the "frame" that is going to be displaying the > structure, not by the structure itself. Sorry, I didn't express myself clearly. What I ment is that the look (or environment) changes on different structures. For example the Seaside web-site has a different look in the root than on all other pages. Or my blog has a different look as all the other pages. > So in my model, structures have their properties, which the display > frame may make use of. However Structures have no knowledge of their > own > as to how they are to be used. Its the same "children" shouldnt know > too > much about their "parents" use-cases issue. I don't see the relation. The environment is just a pointer from one structure to another one. That's it. It is only the Seaside view that knows how to interpret this. The OmniBrowser view has a different engine to display structure. >>> I am now attempting and failing to put a link to the >>> PRSettingsCommand >>> in the seaside toolbar, is this possible? >>> >> >> Ouch, Seaside Toolbar? I usually keep that disabled. >> > I agree it would be simpler if it was factored out... I have > factored it > out into a decoration-helper. I am still hoping that you will see your > way to support Session/Decoration helpers in 2.9. For me the Toolbar > decoration becomes enabled via the ToolbarHelper when a suitably > qualified user logs in. In Seaside 2.9 the toolbar is a decoration on the root component. I wonder why you don't just embed the components that make up the toolbar as pages in Pier that have admin privileges. This is what I do for the config application, that is sometimes handy to have. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From keith_hodges at yahoo.co.uk Thu Jun 12 17:50:27 2008 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Thu, 12 Jun 2008 16:50:27 +0100 Subject: [Ann] Pier-Jetsam-Environment with Themeable classic Pier 1.0.0 ui In-Reply-To: References: <483AA688.4020806@yahoo.co.uk> <48508852.5060208@yahoo.co.uk> <4851283D.6020401@yahoo.co.uk> Message-ID: <485145C3.1070905@yahoo.co.uk> Lukas Renggli wrote: >>>> In the Pier-Jetsam-Environment package, I have moved the "layout >>>> settings" group of definitions out of PRStructure, since the >>>> structure >>>> itself doesn't need to know anything about how it is to be >>>> displayed. >>>> >>>> >>> Why not? I have websites where every top level structure has its own >>> look. >>> >>> >> Sure that's what I do too. >> >> But the structure itself has nothing to do with determining its >> usage or >> look. It does keep hold of arbitrary properties, but those properties >> are specified by the "frame" that is going to be displaying the >> structure, not by the structure itself. >> > > Sorry, I didn't express myself clearly. > > What I ment is that the look (or environment) changes on different > structures. For example the Seaside web-site has a different look in > the root than on all other pages. Or my blog has a different look as > all the other pages. > Yes I understood entirely. The same scheme is preserved with my approach, if you use the PRPierFrameStandardBP then it specifies the policy that structures have #localEnvironment and #localStyleSheet properties, and it alone controls how they are used. However if you display with, PRPierFrameAdmin then the fixed (non BP) layout is defined in the class, no pages in the kernel are used in the display, so #localEnvironment doesn't mean anything, however #headerColor is used in order to offer an example of a themeable environment. If you display with PRPierFrameCWS then the layout is defined as one standard layout. But with 7 css controlled display choices, again #localEnvironment is not needed. If you display with PRPierFrameSwitching then the layout is defined at any level, by a choice of any one of the above. This allows me to specify my "Admin" pages to be displayed with the Admin frame, but my main site pages to be displayed with the standard frame. >> So in my model, structures have their properties, which the display >> frame may make use of. However Structures have no knowledge of their >> own >> as to how they are to be used. Its the same "children" shouldnt know >> too >> much about their "parents" use-cases issue. >> > > I don't see the relation. > PRStructure is a model class. Yet it defines view related behavior. > The environment is just a pointer from one structure to another one. > That's it. It is only the Seaside view that knows how to interpret > this. Exactly, so I am just saying that the "Seaside View" could define these property descriptions. Change the seaside view and the property descriptions may also change. > The OmniBrowser view has a different engine to display structure. > > >>>> I am now attempting and failing to put a link to the >>>> PRSettingsCommand >>>> in the seaside toolbar, is this possible? >>>> >>>> >>> Ouch, Seaside Toolbar? I usually keep that disabled. >>> >>> >> I agree it would be simpler if it was factored out... I have >> factored it >> out into a decoration-helper. I am still hoping that you will see your >> way to support Session/Decoration helpers in 2.9. For me the Toolbar >> decoration becomes enabled via the ToolbarHelper when a suitably >> qualified user logs in. >> > > In Seaside 2.9 the toolbar is a decoration on the root component. I > wonder why you don't just embed the components that make up the > toolbar as pages in Pier that have admin privileges. This is what I do > I already do this when I am in control of the layout, but I want to simplify so that the user can specify the bare layout that they want, without knowing about complex things such as privileges. I dont really need security loaded for some of my future sites. > for the config application, that is sometimes handy to have. > > Lukas cheers Keith From squeakman at gmail.com Mon Jun 16 14:50:12 2008 From: squeakman at gmail.com (Squeaker) Date: Mon, 16 Jun 2008 08:50:12 -0400 Subject: Embedding a Magritte component in another component Message-ID: Greetings, I have built a component called "VeComponent", with an embedded Magritte component. The code for rendering looks like: VeComponent>>renderContentOn: html html render: self model asComponent addValidatedForm; yourself. html submitButton callback: [self answer: someValue]; text: 'Done' To test this code I call it from aWATask like this: go>> returnValue := self call: aVeComponent. self halt. This works, I get to the halt. If I embed aVeComponent in another component then it appears that the "self answer: someValue" in VeComponent>>renderContentOn: does not work. What I observe is that clicking on the 'Done' button results in the re-displaying of aVeComponent. How is it that the code works when called from aWATask but it does not work if it is contained in another component? Can anyone explain what I am doing wrong? Many Thanks, Frank From renggli at iam.unibe.ch Mon Jun 16 15:04:54 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 16 Jun 2008 15:04:54 +0200 Subject: Embedding a Magritte component in another component In-Reply-To: References: Message-ID: There are several (Seaside related) problems with your code: > I have built a component called "VeComponent", with an embedded > Magritte component. The code for rendering looks like: > > VeComponent>>renderContentOn: html > html render: self model asComponent addValidatedForm; yourself. > html submitButton callback: [self answer: someValue]; > text: 'Done' This instantiates a new component every-time the page is refreshed. You have to initialize the component outside the rendering method, for example when assigning the model to your component: VeComponent>>model: aModel model := aModel. component := aModel asComponent addValidatedForm; yourself VeComponent>>renderContentOn: html html render: component. html submitButton callback: [self answer: someValue]; text: 'Done' Furthermore you have to answer the component as a child: VeComponent>>children ^ Array with: component > If I embed aVeComponent in another component then it appears that the > "self answer: someValue" in VeComponent>>renderContentOn: does not > work. Initialize your component so that it passes the answer event to the outer component: component := aModel asComponent addValidatedForm; onAnswer: [ :value | self answer: value ]; yourself > What I observe is that clicking on the 'Done' button results in the > re-displaying of aVeComponent. That's the standard if no answer handler is defined. Also note that a task runs as a loop. So when the go method finishes, it is automatically restarted. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From cdrick65 at gmail.com Mon Jun 16 15:07:51 2008 From: cdrick65 at gmail.com (cdrick) Date: Mon, 16 Jun 2008 14:07:51 +0100 Subject: Embedding a Magritte component in another component In-Reply-To: References: Message-ID: Hi > > If I embed aVeComponent in another component then it appears that the > "self answer: someValue" in VeComponent>>renderContentOn: does not work. > > What I observe is that clicking on the 'Done' button results in the > re-displaying of aVeComponent. > > How is it that the code works when called from aWATask but it does not > work if it is contained in another component? > > Can anyone explain what I am doing wrong? You need to place your call: in a callback, not "directly" in renderContentOn: like: html anchor callback: [self call: aVeComponent]; ... hth c?drick -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20080616/d3c8b45f/attachment.html From girba at iam.unibe.ch Fri Jun 20 02:30:23 2008 From: girba at iam.unibe.ch (Tudor Girba) Date: Fri, 20 Jun 2008 02:30:23 +0200 Subject: css problem Message-ID: <860CFE8B-F4FC-4B2F-B7AC-863B8A420D60@iam.unibe.ch> Hi, It looks like Pier does not take into account the changes made to the CSS using the Edit Design command. You can reproduce the error by just: - Edit Design - add: body { background: yellow;} - save and nothing happens. The strange thing is that the changes are stored, they just do not affect the rendering. Cheers, Doru -- www.tudorgirba.com www.tudorgirba.com/blog "What we can governs what we wish." From cappadonza at hotmail.com Fri Jun 20 17:02:34 2008 From: cappadonza at hotmail.com (Isaiah Perumalla) Date: Fri, 20 Jun 2008 08:02:34 -0700 (PDT) Subject: Pier-Blog, PostArchive component Message-ID: <18031433.post@talk.nabble.com> When i add a PostArchive component to my page , the component renderes as "(no blog found)" even thought is a Blog present. How do you specify the blog for a PostArchive component ? thanks -- View this message in context: http://www.nabble.com/Pier-Blog%2C-PostArchive-component-tp18031433p18031433.html Sent from the SmallWiki mailing list archive at Nabble.com. From renggli at iam.unibe.ch Fri Jun 20 17:08:07 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 20 Jun 2008 17:08:07 +0200 Subject: Pier-Blog, PostArchive component In-Reply-To: <18031433.post@talk.nabble.com> References: <18031433.post@talk.nabble.com> Message-ID: > When i add a PostArchive component to my page , the component > renderes as > "(no blog found)" even thought is a Blog present. How do you specify > the > blog for a PostArchive component ? It is only active, if one of the contextual parents is a blog. This means you have to browse a blog or one of its child structures. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From cappadonza at hotmail.com Fri Jun 20 17:13:54 2008 From: cappadonza at hotmail.com (Isaiah Perumalla) Date: Fri, 20 Jun 2008 08:13:54 -0700 (PDT) Subject: Pier-Blog, PostArchive component In-Reply-To: References: <18031433.post@talk.nabble.com> Message-ID: <18031704.post@talk.nabble.com> ok I got a page with the following components embedded +Blog+ +PostTicker+ +PostArchives+ +Tags+ What am i Doing wrong For example how do you configure the component for your blog thanks Lukas Renggli-2 wrote: > >> When i add a PostArchive component to my page , the component >> renderes as >> "(no blog found)" even thought is a Blog present. How do you specify >> the >> blog for a PostArchive component ? > > It is only active, if one of the contextual parents is a blog. This > means you have to browse a blog or one of its child structures. > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > -- View this message in context: http://www.nabble.com/Pier-Blog%2C-PostArchive-component-tp18031433p18031704.html Sent from the SmallWiki mailing list archive at Nabble.com. From ducasse at iam.unibe.ch Sun Jun 22 16:28:13 2008 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Sun, 22 Jun 2008 16:28:13 +0200 Subject: getting started with pier Message-ID: Hi all I would like to know, is thedefault persistency mechanism of pier on when we start the plain default seaside image? Stef PS: I found the PierImagePersistency but there is not even a single comment. :( From renggli at iam.unibe.ch Sun Jun 22 16:50:44 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 22 Jun 2008 16:50:44 +0200 Subject: Pier-Blog, PostArchive component In-Reply-To: <18031704.post@talk.nabble.com> References: <18031433.post@talk.nabble.com> <18031704.post@talk.nabble.com> Message-ID: <413F6FAA-F42C-481C-9546-E52041C404AA@iam.unibe.ch> > ok I got a page with the following components embedded > > +Blog+ +PostTicker+ +PostArchives+ +Tags+ > > What am i Doing wrong > > For example how do you configure the component for your blog You have to add PostTicker, PostArchives, and Tags to the environment in which the blog is displayed. Then when browsing the blog, these components correctly display the posts of the blog. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Sun Jun 22 16:53:08 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 22 Jun 2008 16:53:08 +0200 Subject: getting started with pier In-Reply-To: References: Message-ID: <1B744C9E-36AD-478D-9B33-067848433FAE@iam.unibe.ch> > I would like to know, is thedefault persistency mechanism of pier on > when we start the plain default seaside image? Open an explorer on the kernel of your Pier instance: PRKernel instances explore Select the kernel and evaluate: self persistency: PRImagePersistency new From then on it should automatically take snapshots every hour when something changed. Also it automatically backups the images. Pay attention not set the image persistency while loading code or while doing development. Unfortunately saving the image while code is compiled can screw up your changes. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From ducasse at iam.unibe.ch Sun Jun 22 17:29:04 2008 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Sun, 22 Jun 2008 17:29:04 +0200 Subject: getting started with pier In-Reply-To: <1B744C9E-36AD-478D-9B33-067848433FAE@iam.unibe.ch> References: <1B744C9E-36AD-478D-9B33-067848433FAE@iam.unibe.ch> Message-ID: <7F155E44-EE32-404D-855C-A5ACD635E501@iam.unibe.ch> Ok what will happen if I do PRImagePersistency new snapshot :) like I did to try :) is there a command that could be used to let the user decide when to snapshot? Stef On Jun 22, 2008, at 4:53 PM, Lukas Renggli wrote: >> I would like to know, is thedefault persistency mechanism of pier on >> when we start the plain default seaside image? > > Open an explorer on the kernel of your Pier instance: > > PRKernel instances explore > > Select the kernel and evaluate: > > self persistency: PRImagePersistency new > > From then on it should automatically take snapshots every hour when > something changed. Also it automatically backups the images. > > Pay attention not set the image persistency while loading code or > while doing development. Unfortunately saving the image while code is > compiled can screw up your changes. > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From renggli at iam.unibe.ch Sun Jun 22 17:38:42 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 22 Jun 2008 17:38:42 +0200 Subject: getting started with pier In-Reply-To: <7F155E44-EE32-404D-855C-A5ACD635E501@iam.unibe.ch> References: <1B744C9E-36AD-478D-9B33-067848433FAE@iam.unibe.ch> <7F155E44-EE32-404D-855C-A5ACD635E501@iam.unibe.ch> Message-ID: > Ok > what will happen if I do > PRImagePersistency new snapshot :) like I did to try :) That will take a snapshot. > is there a command that could be used to let the user decide when to > snapshot? There are components to manager users, groups and the system. The system component has a button to trigger the snapshot manually. I usually add these three components to a protected admin page. Cheers, Lukas > > > Stef > > On Jun 22, 2008, at 4:53 PM, Lukas Renggli wrote: > >>> I would like to know, is thedefault persistency mechanism of pier >>> on >>> when we start the plain default seaside image? >> >> Open an explorer on the kernel of your Pier instance: >> >> PRKernel instances explore >> >> Select the kernel and evaluate: >> >> self persistency: PRImagePersistency new >> >> From then on it should automatically take snapshots every hour when >> something changed. Also it automatically backups the images. >> >> Pay attention not set the image persistency while loading code or >> while doing development. Unfortunately saving the image while code is >> compiled can screw up your changes. >> >> Cheers, >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> >> _______________________________________________ >> SmallWiki, Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- Lukas Renggli http://www.lukas-renggli.ch From ducasse at iam.unibe.ch Sun Jun 22 17:41:31 2008 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Sun, 22 Jun 2008 17:41:31 +0200 Subject: getting started with pier In-Reply-To: <1B744C9E-36AD-478D-9B33-067848433FAE@iam.unibe.ch> References: <1B744C9E-36AD-478D-9B33-067848433FAE@iam.unibe.ch> Message-ID: <693AE538-39E5-48E4-9FE6-9433A3919F42@iam.unibe.ch> lukas can add add that to the class comment of PRImagePersistency Tx On Jun 22, 2008, at 4:53 PM, Lukas Renggli wrote: >> I would like to know, is thedefault persistency mechanism of pier on >> when we start the plain default seaside image? > > Open an explorer on the kernel of your Pier instance: > > PRKernel instances explore > > Select the kernel and evaluate: > > self persistency: PRImagePersistency new > > From then on it should automatically take snapshots every hour when > something changed. Also it automatically backups the images. > > Pay attention not set the image persistency while loading code or > while doing development. Unfortunately saving the image while code is > compiled can screw up your changes. > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From ducasse at iam.unibe.ch Sun Jun 22 17:42:08 2008 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Sun, 22 Jun 2008 17:42:08 +0200 Subject: getting started with pier In-Reply-To: References: <1B744C9E-36AD-478D-9B33-067848433FAE@iam.unibe.ch> <7F155E44-EE32-404D-855C-A5ACD635E501@iam.unibe.ch> Message-ID: Ok excellent I will paly with it. For now I want to use pier for a private locate pier as I did in the past with SmallWiki. stef On Jun 22, 2008, at 5:38 PM, Lukas Renggli wrote: >> Ok >> what will happen if I do >> PRImagePersistency new snapshot :) like I did to try :) > > That will take a snapshot. > >> is there a command that could be used to let the user decide when to >> snapshot? > > There are components to manager users, groups and the system. The > system component has a button to trigger the snapshot manually. I > usually add these three components to a protected admin page. > > Cheers, > Lukas > >> >> >> Stef >> >> On Jun 22, 2008, at 4:53 PM, Lukas Renggli wrote: >> >>>> I would like to know, is thedefault persistency mechanism of pier >>>> on >>>> when we start the plain default seaside image? >>> >>> Open an explorer on the kernel of your Pier instance: >>> >>> PRKernel instances explore >>> >>> Select the kernel and evaluate: >>> >>> self persistency: PRImagePersistency new >>> >>> From then on it should automatically take snapshots every hour when >>> something changed. Also it automatically backups the images. >>> >>> Pay attention not set the image persistency while loading code or >>> while doing development. Unfortunately saving the image while code >>> is >>> compiled can screw up your changes. >>> >>> Cheers, >>> Lukas >>> >>> -- >>> Lukas Renggli >>> http://www.lukas-renggli.ch >>> >>> >>> _______________________________________________ >>> SmallWiki, Magritte, Pier and Related Tools ... >>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> >> >> _______________________________________________ >> SmallWiki, Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From cdrick65 at gmail.com Sun Jun 22 18:54:43 2008 From: cdrick65 at gmail.com (cdrick) Date: Sun, 22 Jun 2008 18:54:43 +0200 Subject: getting started with pier In-Reply-To: References: <1B744C9E-36AD-478D-9B33-067848433FAE@iam.unibe.ch> <7F155E44-EE32-404D-855C-A5ACD635E501@iam.unibe.ch> Message-ID: >> is there a command that could be used to let the user decide when to >> snapshot? > > There are components to manager users, groups and the system. The > system component has a button to trigger the snapshot manually. I > usually add these three components to a protected admin page. > > Same, I use the exact same layout + shortcut to environments. if you try quicly this adress, you can see it Steph http://www.squeakside.com/seaside/pier/Admin?_s=U7SEOg2yds3EUzZ4&_k=H-JkZOZD&_n&14 Maybe this could be a good default page to have (the admin one) ? as a blog page with archives and other related component. Cheers C?drick >Cheers, > Lukas > >> >> >> Stef >> >> On Jun 22, 2008, at 4:53 PM, Lukas Renggli wrote: >> >>>> I would like to know, is thedefault persistency mechanism of pier >>>> on >>>> when we start the plain default seaside image? >>> >>> Open an explorer on the kernel of your Pier instance: >>> >>> PRKernel instances explore >>> >>> Select the kernel and evaluate: >>> >>> self persistency: PRImagePersistency new >>> >>> From then on it should automatically take snapshots every hour when >>> something changed. Also it automatically backups the images. >>> >>> Pay attention not set the image persistency while loading code or >>> while doing development. Unfortunately saving the image while code is >>> compiled can screw up your changes. >>> >>> Cheers, >>> Lukas >>> >>> -- >>> Lukas Renggli >>> http://www.lukas-renggli.ch >>> >>> >>> _______________________________________________ >>> SmallWiki, Magritte, Pier and Related Tools ... >>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> >> >> _______________________________________________ >> SmallWiki, Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > From renggli at iam.unibe.ch Sun Jun 22 18:55:01 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 22 Jun 2008 18:55:01 +0200 Subject: getting started with pier In-Reply-To: <693AE538-39E5-48E4-9FE6-9433A3919F42@iam.unibe.ch> References: <1B744C9E-36AD-478D-9B33-067848433FAE@iam.unibe.ch> <693AE538-39E5-48E4-9FE6-9433A3919F42@iam.unibe.ch> Message-ID: <3F6439A6-973A-416C-AB71-837BD41A4B6E@iam.unibe.ch> Done. On Jun 22, 2008, at 17:41 , st?phane ducasse wrote: > lukas can add add that to the class comment of PRImagePersistency > > Tx > > On Jun 22, 2008, at 4:53 PM, Lukas Renggli wrote: > >>> I would like to know, is thedefault persistency mechanism of pier >>> on >>> when we start the plain default seaside image? >> >> Open an explorer on the kernel of your Pier instance: >> >> PRKernel instances explore >> >> Select the kernel and evaluate: >> >> self persistency: PRImagePersistency new >> >> From then on it should automatically take snapshots every hour when >> something changed. Also it automatically backups the images. >> >> Pay attention not set the image persistency while loading code or >> while doing development. Unfortunately saving the image while code is >> compiled can screw up your changes. >> >> Cheers, >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> >> _______________________________________________ >> SmallWiki, Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- Lukas Renggli http://www.lukas-renggli.ch From ducasse at iam.unibe.ch Sun Jun 22 21:10:45 2008 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Sun, 22 Jun 2008 21:10:45 +0200 Subject: getting started with pier In-Reply-To: References: <1B744C9E-36AD-478D-9B33-067848433FAE@iam.unibe.ch> <7F155E44-EE32-404D-855C-A5ACD635E501@iam.unibe.ch> Message-ID: <4BAA6FAA-6BF0-4E84-93F1-EBC61251CBC0@iam.unibe.ch> > > >> is there a command that could be used to let the user decide when to >> snapshot? > > There are components to manager users, groups and the system. The > system component has a button to trigger the snapshot manually. I > usually add these three components to a protected admin page. I tried during 15 min to find them but I failed. Should I load something? Else how do I access them? Setf From renggli at iam.unibe.ch Sun Jun 22 21:25:37 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 22 Jun 2008 21:25:37 +0200 Subject: getting started with pier In-Reply-To: <4BAA6FAA-6BF0-4E84-93F1-EBC61251CBC0@iam.unibe.ch> References: <1B744C9E-36AD-478D-9B33-067848433FAE@iam.unibe.ch> <7F155E44-EE32-404D-855C-A5ACD635E501@iam.unibe.ch> <4BAA6FAA-6BF0-4E84-93F1-EBC61251CBC0@iam.unibe.ch> Message-ID: <7A1AF5FA-6B75-414C-BBBF-845832970620@iam.unibe.ch> >>> is there a command that could be used to let the user decide when to >>> snapshot? >> >> There are components to manager users, groups and the system. The >> system component has a button to trigger the snapshot manually. I >> usually add these three components to a protected admin page. > > I tried during 15 min to find them but I failed. > Should I load something? > Else how do I access them? 1. Create a page containing: !Users +users+ !Groups +groups+ !System +system+ 2. Subsequently click on the non-existing links and add a Component. Select 'System Users', 'System Groups' and 'System' as the instance for each of them Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From ducasse at iam.unibe.ch Sun Jun 22 21:35:54 2008 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Sun, 22 Jun 2008 21:35:54 +0200 Subject: getting started with pier In-Reply-To: <7A1AF5FA-6B75-414C-BBBF-845832970620@iam.unibe.ch> References: <1B744C9E-36AD-478D-9B33-067848433FAE@iam.unibe.ch> <7F155E44-EE32-404D-855C-A5ACD635E501@iam.unibe.ch> <4BAA6FAA-6BF0-4E84-93F1-EBC61251CBC0@iam.unibe.ch> <7A1AF5FA-6B75-414C-BBBF-845832970620@iam.unibe.ch> Message-ID: >>>> 1. Create a page containing: > > !Users > +users+ > > !Groups > +groups+ > > !System > +system+ > > 2. Subsequently click on the non-existing links and add a Component. > Select 'System Users', 'System Groups' and 'System' as the instance > for each of them Thanks I did that But I do not get a save button on any of them. (I loaded Pier Setup as suggested by doru) so may be this is because of that. Stef From ducasse at iam.unibe.ch Sun Jun 22 21:39:56 2008 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Sun, 22 Jun 2008 21:39:56 +0200 Subject: About move Message-ID: <069EDDDF-F1E4-4ACD-B5F1-0951410ACA66@iam.unibe.ch> stupidly I created an admin page in the blog and I wanted to move it elsewehere. So I clicked on move and I tried / but I'm not allowed /AnotherPage and I always get Move: 'PAD' can not be a child of 'Passes' So what is the solution? Doru lukas I can tell you that I can really be a guinea pig about usability because I just crash in everything. Stef From renggli at iam.unibe.ch Sun Jun 22 21:46:07 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 22 Jun 2008 21:46:07 +0200 Subject: getting started with pier In-Reply-To: References: <1B744C9E-36AD-478D-9B33-067848433FAE@iam.unibe.ch> <7F155E44-EE32-404D-855C-A5ACD635E501@iam.unibe.ch> <4BAA6FAA-6BF0-4E84-93F1-EBC61251CBC0@iam.unibe.ch> <7A1AF5FA-6B75-414C-BBBF-845832970620@iam.unibe.ch> Message-ID: <18040265-2E2A-4158-B374-7BCCA0F37DEB@iam.unibe.ch> You only see the save button, when logged in as admin. On Jun 22, 2008, at 21:35 , st?phane ducasse wrote: >>>>> 1. Create a page containing: >> >> !Users >> +users+ >> >> !Groups >> +groups+ >> >> !System >> +system+ >> >> 2. Subsequently click on the non-existing links and add a Component. >> Select 'System Users', 'System Groups' and 'System' as the instance >> for each of them > > > Thanks > I did that > But I do not get a save button on any of them. (I loaded Pier Setup as > suggested by doru) so > may be this is because of that. > > Stef > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Sun Jun 22 21:49:33 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 22 Jun 2008 21:49:33 +0200 Subject: About move In-Reply-To: <069EDDDF-F1E4-4ACD-B5F1-0951410ACA66@iam.unibe.ch> References: <069EDDDF-F1E4-4ACD-B5F1-0951410ACA66@iam.unibe.ch> Message-ID: <61DB4793-E539-45A7-8592-4D887A4A5C6D@iam.unibe.ch> I don't understand what you are trying to do. I don't know what PAD, Passes, AnotherPage is. The commands essentially follow the Unix counterparts. Move is the same as mv. - Target is the new parent where you want to move this structure to. - Name is the new name (rename) you want this structure to have. Lukas On Jun 22, 2008, at 21:39 , st?phane ducasse wrote: > stupidly I created an admin page in the blog and I wanted to move it > elsewehere. > So I clicked on move and I tried > > / but I'm not allowed > /AnotherPage > > and I always get Move: 'PAD' can not be a child of 'Passes' > > So what is the solution? > > Doru lukas I can tell you that I can really be a guinea pig about > usability > because I just crash in everything. > > Stef > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- Lukas Renggli http://www.lukas-renggli.ch From ducasse at iam.unibe.ch Sun Jun 22 21:55:29 2008 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Sun, 22 Jun 2008 21:55:29 +0200 Subject: getting started with pier In-Reply-To: <18040265-2E2A-4158-B374-7BCCA0F37DEB@iam.unibe.ch> References: <1B744C9E-36AD-478D-9B33-067848433FAE@iam.unibe.ch> <7F155E44-EE32-404D-855C-A5ACD635E501@iam.unibe.ch> <4BAA6FAA-6BF0-4E84-93F1-EBC61251CBC0@iam.unibe.ch> <7A1AF5FA-6B75-414C-BBBF-845832970620@iam.unibe.ch> <18040265-2E2A-4158-B374-7BCCA0F37DEB@iam.unibe.ch> Message-ID: <9125B9FD-4C6A-4742-8FC6-7E32300454B3@iam.unibe.ch> I found the password by accident. But when I browsed System or groups or users I do not get a save button. Stef > You only see the save button, when logged in as admin. From renggli at iam.unibe.ch Sun Jun 22 21:57:31 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 22 Jun 2008 21:57:31 +0200 Subject: About move In-Reply-To: <61DB4793-E539-45A7-8592-4D887A4A5C6D@iam.unibe.ch> References: <069EDDDF-F1E4-4ACD-B5F1-0951410ACA66@iam.unibe.ch> <61DB4793-E539-45A7-8592-4D887A4A5C6D@iam.unibe.ch> Message-ID: >> and I always get Move: 'PAD' can not be a child of 'Passes' Normally you get this error when trying to move something into yourself. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From ducasse at iam.unibe.ch Sun Jun 22 22:01:38 2008 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Sun, 22 Jun 2008 22:01:38 +0200 Subject: About move In-Reply-To: <61DB4793-E539-45A7-8592-4D887A4A5C6D@iam.unibe.ch> References: <069EDDDF-F1E4-4ACD-B5F1-0951410ACA66@iam.unibe.ch> <61DB4793-E539-45A7-8592-4D887A4A5C6D@iam.unibe.ch> Message-ID: <6A1EA29C-2A5A-47B4-9F83-1A62FFAA34CC@iam.unibe.ch> On Jun 22, 2008, at 9:49 PM, Lukas Renggli wrote: > I don't understand what you are trying to do. I don't know what PAD, > Passes, AnotherPage is. I created a page PierADmin = PAD under Blog and I created Passes a Page under Pier and AnotherPage = AnotherPage > The commands essentially follow the Unix counterparts. Move is the > same as mv. I can tell you that we can do a real evaluation of what an idiot user like me can think about an interface and some messages even for something as simple as move are not clear. > - Target is the new parent where you want to move this structure to. > - Name is the new name (rename) you want this structure to have. I do not why I cannot move to anything. When I click on browse I imagine that I should click on the target Now I even lost the blog. I will let you conclude. I'm certainly an idiot. Stef > > > Lukas > > > > On Jun 22, 2008, at 21:39 , st?phane ducasse wrote: > >> stupidly I created an admin page in the blog and I wanted to move it >> elsewehere. >> So I clicked on move and I tried >> >> / but I'm not allowed >> /AnotherPage >> >> and I always get Move: 'PAD' can not be a child of 'Passes' >> >> So what is the solution? >> >> Doru lukas I can tell you that I can really be a guinea pig about >> usability >> because I just crash in everything. >> >> Stef >> >> _______________________________________________ >> SmallWiki, Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > From ducasse at iam.unibe.ch Sun Jun 22 22:06:13 2008 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Sun, 22 Jun 2008 22:06:13 +0200 Subject: About move In-Reply-To: References: <069EDDDF-F1E4-4ACD-B5F1-0951410ACA66@iam.unibe.ch> <61DB4793-E539-45A7-8592-4D887A4A5C6D@iam.unibe.ch> Message-ID: A non-text attachment was scrubbed... Name: Picture 2.pdf Type: application/pdf Size: 12749 bytes Desc: not available Url : http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20080622/dbdd4dbb/Picture2-0001.pdf -------------- next part -------------- I wanted to move an item to the top because the nested was too low After I wanted to move it to the page /Passes and give it another name -------------- next part -------------- A non-text attachment was scrubbed... Name: Picture 3.pdf Type: application/pdf Size: 26364 bytes Desc: not available Url : http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20080622/dbdd4dbb/Picture3-0001.pdf -------------- next part -------------- On Jun 22, 2008, at 9:57 PM, Lukas Renggli wrote: >>> and I always get Move: 'PAD' can not be a child of 'Passes' > > Normally you get this error when trying to move something into > yourself. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From renggli at iam.unibe.ch Sun Jun 22 22:07:22 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 22 Jun 2008 22:07:22 +0200 Subject: About move In-Reply-To: <6A1EA29C-2A5A-47B4-9F83-1A62FFAA34CC@iam.unibe.ch> References: <069EDDDF-F1E4-4ACD-B5F1-0951410ACA66@iam.unibe.ch> <61DB4793-E539-45A7-8592-4D887A4A5C6D@iam.unibe.ch> <6A1EA29C-2A5A-47B4-9F83-1A62FFAA34CC@iam.unibe.ch> Message-ID: <6BCAFEC7-ABEB-4298-B17A-4B10962462D9@iam.unibe.ch> >> I don't understand what you are trying to do. I don't know what PAD, >> Passes, AnotherPage is. > > I created a page PierADmin = PAD under Blog Normally the system does not let you create a page within a blog. Only posts can be added to a blog. > and I created Passes a Page under Pier > and AnotherPage = AnotherPage Mhh? >> - Target is the new parent where you want to move this structure to. >> - Name is the new name (rename) you want this structure to have. > > I do not why I cannot move to anything. Send a screenshot, so that I can see what you are trying to do. > When I click on browse I imagine that I should click on the target Yes, the page will then become a child of the target. > Now I even lost the blog. I will let you conclude. I'm certainly an > idiot. I am not saying that. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Sun Jun 22 22:08:51 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 22 Jun 2008 22:08:51 +0200 Subject: About move In-Reply-To: References: <069EDDDF-F1E4-4ACD-B5F1-0951410ACA66@iam.unibe.ch> <61DB4793-E539-45A7-8592-4D887A4A5C6D@iam.unibe.ch> Message-ID: <1F00080D-F293-49AC-87A4-736707B97766@iam.unibe.ch> Ahh, now I understand. You didn't create a page, but a post. And posts can only live within a blog. So you can't move it outside. Sorry. Cheers, Lukas On Jun 22, 2008, at 22:06 , st?phane ducasse wrote: > > > I wanted to move an item to the top because the nested was too low > > > After I wanted to move it to the page /Passes and give it another name > > > > On Jun 22, 2008, at 9:57 PM, Lukas Renggli wrote: > >>>> and I always get Move: 'PAD' can not be a child of 'Passes' >> >> Normally you get this error when trying to move something into >> yourself. >> >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> >> _______________________________________________ >> SmallWiki, Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- Lukas Renggli http://www.lukas-renggli.ch From ducasse at iam.unibe.ch Sun Jun 22 22:20:47 2008 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Sun, 22 Jun 2008 22:20:47 +0200 Subject: About move In-Reply-To: <6BCAFEC7-ABEB-4298-B17A-4B10962462D9@iam.unibe.ch> References: <069EDDDF-F1E4-4ACD-B5F1-0951410ACA66@iam.unibe.ch> <61DB4793-E539-45A7-8592-4D887A4A5C6D@iam.unibe.ch> <6A1EA29C-2A5A-47B4-9F83-1A62FFAA34CC@iam.unibe.ch> <6BCAFEC7-ABEB-4298-B17A-4B10962462D9@iam.unibe.ch> Message-ID: <94725FDD-6BDB-4C16-A31D-BA9474376676@iam.unibe.ch> On Jun 22, 2008, at 10:07 PM, Lukas Renggli wrote: >>> I don't understand what you are trying to do. I don't know what PAD, >>> Passes, AnotherPage is. >> >> I created a page PierADmin = PAD under Blog > > Normally the system does not let you create a page within a blog. Only > posts can be added to a blog. I just did one. I do not know how. >> and I created Passes a Page under Pier >> and AnotherPage = AnotherPage > > Mhh? Just another page to make experiment > > >>> - Target is the new parent where you want to move this structure to. >>> - Name is the new name (rename) you want this structure to have. >> >> I do not why I cannot move to anything. > > Send a screenshot, so that I can see what you are trying to do. > >> When I click on browse I imagine that I should click on the target > > Yes, the page will then become a child of the target. > >> Now I even lost the blog. I will let you conclude. I'm certainly an >> idiot. > > I am not saying that. I know :) I'm just terribly frustrated. You cannot imagine how difficult it is to systematically bump in UI glitch. All the time all the time. So I can really do an analysis of Pier if you want. I try and try and you will see that I will bump into problems. > > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From ducasse at iam.unibe.ch Sun Jun 22 22:22:48 2008 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Sun, 22 Jun 2008 22:22:48 +0200 Subject: About move In-Reply-To: <1F00080D-F293-49AC-87A4-736707B97766@iam.unibe.ch> References: <069EDDDF-F1E4-4ACD-B5F1-0951410ACA66@iam.unibe.ch> <61DB4793-E539-45A7-8592-4D887A4A5C6D@iam.unibe.ch> <1F00080D-F293-49AC-87A4-736707B97766@iam.unibe.ch> Message-ID: <85AF8F3D-ADAF-43FA-83FF-B318CC49E72B@iam.unibe.ch> On Jun 22, 2008, at 10:08 PM, Lukas Renggli wrote: > Ahh, now I understand. > > You didn't create a page, but a post. And posts can only live within a > blog. So you can't move it outside. Sorry. ah. But I could add component inside so I thought it was a page (because it is). So may be you should have a better error message. I'm dead tired yesterday I "finish" to clean up the walls I broke, painted and today i cut the garden so 4 hours cutting the "haie" I'm dead. Stef > > > Cheers, > Lukas > > > > On Jun 22, 2008, at 22:06 , st?phane ducasse wrote: > >> >> >> I wanted to move an item to the top because the nested was too low >> >> >> After I wanted to move it to the page /Passes and give it another >> name >> >> >> >> On Jun 22, 2008, at 9:57 PM, Lukas Renggli wrote: >> >>>>> and I always get Move: 'PAD' can not be a child of 'Passes' >>> >>> Normally you get this error when trying to move something into >>> yourself. >>> >>> Lukas >>> >>> -- >>> Lukas Renggli >>> http://www.lukas-renggli.ch >>> >>> >>> _______________________________________________ >>> SmallWiki, Magritte, Pier and Related Tools ... >>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> >> >> _______________________________________________ >> SmallWiki, Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > From renggli at iam.unibe.ch Sun Jun 22 22:28:13 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 22 Jun 2008 22:28:13 +0200 Subject: About move In-Reply-To: <85AF8F3D-ADAF-43FA-83FF-B318CC49E72B@iam.unibe.ch> References: <069EDDDF-F1E4-4ACD-B5F1-0951410ACA66@iam.unibe.ch> <61DB4793-E539-45A7-8592-4D887A4A5C6D@iam.unibe.ch> <1F00080D-F293-49AC-87A4-736707B97766@iam.unibe.ch> <85AF8F3D-ADAF-43FA-83FF-B318CC49E72B@iam.unibe.ch> Message-ID: <606E23A8-3E1C-43D6-88DF-262B88221985@iam.unibe.ch> > But I could add component inside so I thought it was a page (because > it is). Yeah, posts can have other structures (images, components, etc.) as children again. A post is a page, but it has much more properties like post-date, editor, ... > So may be you should have a better error message. I agree that the error message is bad. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From cappadonza at hotmail.com Sun Jun 22 23:51:37 2008 From: cappadonza at hotmail.com (Isaiah Perumalla) Date: Sun, 22 Jun 2008 14:51:37 -0700 (PDT) Subject: Pier-Blog, PostArchive component In-Reply-To: <413F6FAA-F42C-481C-9546-E52041C404AA@iam.unibe.ch> References: <18031433.post@talk.nabble.com> <18031704.post@talk.nabble.com> <413F6FAA-F42C-481C-9546-E52041C404AA@iam.unibe.ch> Message-ID: <18059379.post@talk.nabble.com> Thanks Lukas So does it mean you have more than one Environment per PRKernel ? Lukas Renggli-2 wrote: > >> ok I got a page with the following components embedded >> >> +Blog+ +PostTicker+ +PostArchives+ +Tags+ >> >> What am i Doing wrong >> >> For example how do you configure the component for your blog > > You have to add PostTicker, PostArchives, and Tags to the environment > in which the blog is displayed. Then when browsing the blog, these > components correctly display the posts of the blog. > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > -- View this message in context: http://www.nabble.com/Pier-Blog%2C-PostArchive-component-tp18031433p18059379.html Sent from the SmallWiki mailing list archive at Nabble.com. From renggli at iam.unibe.ch Sun Jun 22 23:56:44 2008 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 22 Jun 2008 23:56:44 +0200 Subject: Pier-Blog, PostArchive component In-Reply-To: <18059379.post@talk.nabble.com> References: <18031433.post@talk.nabble.com> <18031704.post@talk.nabble.com> <413F6FAA-F42C-481C-9546-E52041C404AA@iam.unibe.ch> <18059379.post@talk.nabble.com> Message-ID: > So does it mean you have more than one Environment per PRKernel ? Usually I have several, yes. seaside.st has one for the root, and two (a small and a wide one) for the inner pages. lukas-renggli.ch has two, one for the blog and one for the rest. Cheers, Lukas > > > Lukas Renggli-2 wrote: >> >>> ok I got a page with the following components embedded >>> >>> +Blog+ +PostTicker+ +PostArchives+ +Tags+ >>> >>> What am i Doing wrong >>> >>> For example how do you configure the component for your blog >> >> You have to add PostTicker, PostArchives, and Tags to the environment >> in which the blog is displayed. Then when browsing the blog, these >> components correctly display the posts of the blog. >> >> Cheers, >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> >> _______________________________________________ >> SmallWiki, Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> >> > > -- > View this message in context: http://www.nabble.com/Pier-Blog%2C-PostArchive-component-tp18031433p18059379.html > Sent from the SmallWiki mailing list archive at Nabble.com. > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- Lukas Renggli http://www.lukas-renggli.ch From cappadonza at hotmail.com Mon Jun 23 00:18:20 2008 From: cappadonza at hotmail.com (Isaiah Perumalla) Date: Sun, 22 Jun 2008 15:18:20 -0700 (PDT) Subject: Pier-Blog, PostArchive component In-Reply-To: References: <18031433.post@talk.nabble.com> <18031704.post@talk.nabble.com> <413F6FAA-F42C-481C-9546-E52041C404AA@iam.unibe.ch> <18059379.post@talk.nabble.com> Message-ID: <18059835.post@talk.nabble.com> Thanks Lukas. I got it working, it really interesting, very flexible. I was getting confused between environment and Target, i realised they are completely different things. Thanks Isaiah Lukas Renggli-2 wrote: > >> So does it mean you have more than one Environment per PRKernel ? > > Usually I have several, yes. > > seaside.st has one for the root, and two (a small and a wide one) for > the inner pages. > > lukas-renggli.ch has two, one for the blog and one for the rest. > > Cheers, > Lukas > >> >> >> Lukas Renggli-2 wrote: >>> >>>> ok I got a page with the following components embedded >>>> >>>> +Blog+ +PostTicker+ +PostArchives+ +Tags+ >>>> >>>> What am i Doing wrong >>>> >>>> For example how do you configure the component for your blog >>> >>> You have to add PostTicker, PostArchives, and Tags to the environment >>> in which the blog is displayed. Then when browsing the blog, these >>> components correctly display the posts of the blog. >>> >>> Cheers, >>> Lukas >>> >>> -- >>> Lukas Renggli >>> http://www.lukas-renggli.ch >>> >>> >>> _______________________________________________ >>> SmallWiki, Magritte, Pier and Related Tools ... >>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/Pier-Blog%2C-PostArchive-component-tp18031433p18059379.html >> Sent from the SmallWiki mailing list archive at Nabble.com. >> >> >> _______________________________________________ >> SmallWiki, Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > -- View this message in context: http://www.nabble.com/Pier-Blog%2C-PostArchive-component-tp18031433p18059835.html Sent from the SmallWiki mailing list archive at Nabble.com. From ducasse at iam.unibe.ch Wed Jun 25 20:49:33 2008 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Wed, 25 Jun 2008 20:49:33 +0200 Subject: getting started with pier In-Reply-To: <7A1AF5FA-6B75-414C-BBBF-845832970620@iam.unibe.ch> References: <1B744C9E-36AD-478D-9B33-067848433FAE@iam.unibe.ch> <7F155E44-EE32-404D-855C-A5ACD635E501@iam.unibe.ch> <4BAA6FAA-6BF0-4E84-93F1-EBC61251CBC0@iam.unibe.ch> <7A1AF5FA-6B75-414C-BBBF-845832970620@iam.unibe.ch> Message-ID: <8C2C47E1-46C0-4055-ACDB-6B952DBA9979@iam.unibe.ch> Hi lukas I redid the complete steps you describe but I do not get a save command. Stef >>>> is there a command that could be used to let the user decide when >>>> to >>>> snapshot? >>> >>> There are components to manager users, groups and the system. The >>> system component has a button to trigger the snapshot manually. I >>> usually add these three components to a protected admin page. >> >> I tried during 15 min to find them but I failed. >> Should I load something? >> Else how do I access them? > > 1. Create a page containing: > > !Users > +users+ > > !Groups > +groups+ > > !System > +system+ > > 2. Subsequently click on the non-existing links and add a Component. > Select 'System Users', 'System Groups' and 'System' as the instance > for each of them > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From jborden23 at mac.com Sat Jun 28 21:03:23 2008 From: jborden23 at mac.com (John Borden) Date: Sat, 28 Jun 2008 14:03:23 -0500 Subject: [ANN] Seaside+Pier+Magma image available In-Reply-To: <2A3B1429-D0D5-489D-AD8B-A7633404940D@iam.unibe.ch> References: <45023E95.8030106@yahoo.co.uk> <2A3B1429-D0D5-489D-AD8B-A7633404940D@iam.unibe.ch> Message-ID: <2015AF3C-E04B-41FE-ADAF-BF7E1EEC802F@mac.com> Keith, Is there a more up-to-date image available? I tried loading PierMagma from mc.lukas-renggli.ch/pier, but it requires MagmaDictionaryRoot. Thanks, John On Sep 9, 2006, at 2:57 AM, st?phane ducasse wrote: > Cool > I think that this is really important for pier to get multiple back > end systems so that we can > choose and make sure that we can never lost the data. > > Stef > > On 9 sept. 06, at 06:09, Keith Hodges wrote: > >> First (alpha!) release of Pier running with Magma Persistency. >> >> Image available from ftp.seasidehosting.st >> User: preloaded Password: squeak >> >> enjoy >> >> Keith >> ------ >> Image Use Instructions >> In pier configuration click on 'Magma Control Panel', which will >> inform >> you that the repository does not exist. If you have placed this >> image on >> seasidehosting then you will have to manually create the repository >> directory. Given the list of options as to what repository to create, >> click the 'create' button (and wait). The existing pier kernel >> should >> appear in the list with a 'persist' button next to it, click >> 'persist'. >> Then try it and see! >> ------ >> ------ >> Detailed Log of Image Creation Steps (alternative title: "monticello >> tutorial") >> >> This image was prepared as follows: >> Beginning with Squeak3.8-6555full >> >> Initial start asks for updates: select "do not ask again" - this is >> important should you wish to deploy. Headless servers (e.g. >> seasidehosting) cannot handle user interaction and will stop at >> this point. >> >> From "world menu > open.... > Monticello Browser" >> Browser opens with (Monticello....) >> >> Click the "+Repository Button", select "HTTP" as the repository type, >> and enter >> >> MCHttpRepository >> location: 'http://www.squeaksource.com/Seaside' >> user: '' >> password: '' >> >> as the repository info (if you have a login on Squeaksource then >> you can >> enter your initials >> as the 'user' above.) >> >> Add the following repository for Monticello. >> >> MCHttpRepository >> location: 'http://www.squeaksource.com/Monticello' >> user: '' >> password: '' >> >> Add the following repository for Magma. >> >> MCHttpRepository >> location: 'http://www.squeaksource.com/MagmaTester' >> user: '' >> password: '' >> >> and the following two repositories for Magritte and Pier >> >> MCHttpRepository >> location: 'http://mc.lukas-renggli.ch/magritte' >> user: '' >> password: '' >> >> MCHttpRepository >> location: 'http://mc.lukas-renggli.ch/pier' >> user: '' >> password: '' >> >> also: >> >> MCHttpRepository >> location: 'http://www.squeaksource.com/OmniBrowser' >> user: '' >> password: '' >> >> (to edit this information: >> click the menu button in the right hand pane of the Monticello >> Browser) >> ---- >> Loading Latest Monticello. >> >> More recent versions of Monticello provide better feedback as to >> which >> packages are currently loaded. >> >> Select the http://www.squeaksource.com/Monticello repository, click >> "open", select the latest package (Monticello-avi.279) from the main >> "Monticello" branch, and click "load". >> >> Select the Monticello package on the left hand pane, and the >> squeaksource/Monticello repository in the right hand pane. Click >> 'open'. >> In the repository browser, click on the latest version >> (Monticello-avi.279.mcz) and click 'Load'. >> ---- >> Loading Seaside >> >> Select "world menu > open... SqueakMap"... and a dialog will ask if >> you >> wish to upgrade SqueakMap. Which you do. Notice that SMBase, SMLoader >> packages appeaer in the Monticello browser, since the upgrade is >> performed by loading Monticello packages. >> >> In SqueakMap, select the ever so convenient "Seaside Installer" which >> should load in the whole of seaside with its dependencies in one >> go. To >> do this select the left had pane menu button, "install". (Part way >> through the install you will be prompted to enter an admin username >> (seaside) and password (admin)) >> >> (if SqueakMap doesnt work it is being knobbled by a more recent >> package-cache, remove it and try again) >> >> Select the seaside repositoryClick the "open" and the repository >> browser >> will open. >> >> Select Seaside2.6b1 which is the current latest. In the right hand >> pane >> are the releases. Releases may be made by anyone and they may be >> small >> branches off from the main stream. Periodically an effort will be >> made >> to ensure that all changes are merged. Click the history button in >> order >> to browse the history of this package to get some idea of what is >> going >> on. Look at the ancestors of a package to see if one version is being >> sequentially built on the next, or whether any branching is >> occurring. >> Seaside is fairly mature and changes infrequent, therefore it is >> likely >> to be safe to grab the latest version. >> >> Loaded Seaside2.6b1-mb.79 >> Loaded Scriptaculous-lr.137 >> >> To start Seaside doit: >> WAKom startOn: 8080. >> ( Or use the "beach flags" SeasideMorph >> available from: http://minnow.cc.gatech.edu/squeak/5862 ) >> >> To test if everything is running, check the following url in your >> normal >> web browser. >> http://localhost:8080/seaside/config >> >> you should be prompted for you username and password (as given >> earlier). >> ---- >> Loading Magma >> >> Back to the Monticello Browser. Deselect the selected package by >> clicking on it once. This should re-reveal all of the registered >> repositories. >> >> (It is worth saving this. In the right hand side pane menu button >> there >> is a menu item: "Save Repositories", which writes a simple >> configuration >> script to the working directory.) >> >> Select the http://www.squeaksource.com/MagmaTester repository, and >> click >> "open". >> >> Select MagmaServerLoader, and click "load". (it takes a while!) >> >> loaded MagmaServerLoader-cmm.21 >> loaded Ma client server-cmm.123 >> loaded Ma exception handling-cmm.22 >> loaded Ma time objects-cmm.37 >> ---- >> Load Magma Seaside Integration Package >> >> Select "Magma Seaside" (lhs) and the latest package and click "load", >> >> loaded Magma Seaside-kph.18 >> ---- >> Load Magma Seaside Sushi Store Demo fixes >> >> loaded Seaside-Examples-Store-Magma.kph-11 >> ---- >> >> Before using Magma may need to execute the following. >> >> MagmaSession initialize. >> MagmaRepositoryController initialize. >> >> useful snippets >> MagmaSession allInstances cleanUp. >> MagmaSession disconnectAndCloseAllConnectedSessions. >> >> ---- >> Load Magritte >> loaded Magritte-All-lr.171 >> Load Pier >> loaded Pier-All-lr.109 >> Load OmniBrowser >> loaded OmniBrowser-avi.258 >> loaded Pier-OmniBrowser-lr.19 >> ---- >> Latest Pier-Magma code >> >> loaded Pier-Model-kph.80 >> loaded Pier-Seaside-kph.80 >> loaded Pier-Magma-kph.1 >> ---- >> Pre-upload actions: >> >> Monticello Browser - "flush cached versions". >> ---- >> Release Preloaded Image as Sqk3.8f-smp.image >> >> >> >> >> >> >> ___________________________________________________________ >> The all-new Yahoo! Mail goes wherever you go - free your email >> address from your Internet provider. http://uk.docs.yahoo.com/ >> nowyoucan.html >> >> _______________________________________________ >> 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 keith_hodges at yahoo.co.uk Sat Jun 28 23:38:16 2008 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Sat, 28 Jun 2008 22:38:16 +0100 Subject: [ANN] Seaside+Pier+Magma image available In-Reply-To: <2015AF3C-E04B-41FE-ADAF-BF7E1EEC802F@mac.com> References: <45023E95.8030106@yahoo.co.uk> <2A3B1429-D0D5-489D-AD8B-A7633404940D@iam.unibe.ch> <2015AF3C-E04B-41FE-ADAF-BF7E1EEC802F@mac.com> Message-ID: <4866AF48.80502@yahoo.co.uk> John Borden wrote: > Keith, > Is there a more up-to-date image available? I tried loading > PierMagma from mc.lukas-renggli.ch/pier, but it requires > MagmaDictionaryRoot. > > Thanks, > John > > Hi, you need to load from Sake/Packages or Universes so that dependencies get satisfied. In an LPF image... Installer install: 'Packages'. Installer sake install: 'PierMagma'. should do the trick Keith