From marianopeck at gmail.com Sun May 3 18:50:26 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Sun, 3 May 2009 13:50:26 -0300 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: <49FA1845.8010201@yahoo.co.uk> References: <49FA1845.8010201@yahoo.co.uk> Message-ID: On Thu, Apr 30, 2009 at 6:29 PM, Keith Hodges wrote: > Mariano Martinez Peck wrote: > > Hi! > > > > I need to do the typical "Contact Us" form where the user can put the > > name the email and the question and then this email to the webmaster > > email account. > > > > I look there was a Pier-EmailSender which seems to do what I need. > > However It has different walkbacks in Pier 1.1.1. > > > > Keith Hodges: do you think it's rather to make it work that doing my own > ? > > > > It is very simple to reproduce. Just open a fresh Pier 1.1.1 and add > > that widget. > > > > Thanks!! > > > > Mariano > The code I am using myself based on this code has been moved into the > Beach project, I think you will find it a bit more workable there. I > dont think it has any dependencies upon beach itself. > > www.squeaksource.com/BeachPostBox-Seaside > Thanks! Now, suppose I want to use it and I want to put the Beach dependency I should need the following information: 1) which are the necessary packages from MC to install 2) in which order should I install them 3) An explanation somewhere which is each package for. I saw some mails in your ANN but there are several packages more. I look at google code wiki and squeaksource wiki but I didn't found any information. I am creating a Pier application and would be nice to detail know how to integrate beach with Pier. Thanks in advance, Mariano > > Keith > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marianopeck at gmail.com Sun May 3 19:47:08 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Sun, 3 May 2009 14:47:08 -0300 Subject: Link to a particular title of a page Message-ID: Hi folks! Suppose you have the common F.A.Q page with and index (with +value:toc+ ) and several numbered questions. I would like to have a link from other page that goes directly to one of the answers of the questions (a particular title with ! or !! or !!!). What I need is what you do in swiki with: *SqueakDBX - Compiling and installing OpenDBX at OpenDBX and FFI* and then in the wiki page "SqueakDBX - Compiling and installing OpenDBX" you put a "@OpenDBX and FFI" in the title. Thanks in advance!! Mariano -------------- next part -------------- An HTML attachment was scrubbed... URL: From keith_hodges at yahoo.co.uk Sun May 3 20:42:40 2009 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Sun, 03 May 2009 19:42:40 +0100 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: References: <49FA1845.8010201@yahoo.co.uk> Message-ID: <49FDE5A0.1080600@yahoo.co.uk> > Thanks! Now, suppose I want to use it and I want to put the Beach > dependency I should need the following information: > The Email Sender is not dependent upon Beach. > 1) which are the necessary packages from MC to install > 2) in which order should I install them > 3) An explanation somewhere which is each package for. I saw some > mails in your ANN but there are several packages more. The information you seek is in the meta-data stored in the Beach-Packages package, which itself depends upon Sake/Packages. This can be installed via Installer install: 'Packages'. > I look at google code wiki and squeaksource wiki but I didn't found > any information. > > I am creating a Pier application and would be nice to detail know how > to integrate beach with Pier. Keith From renggli at gmail.com Sun May 3 21:45:38 2009 From: renggli at gmail.com (Lukas Renggli) Date: Sun, 3 May 2009 21:45:38 +0200 Subject: Link to a particular title of a page In-Reply-To: References: Message-ID: <67628d690905031245h5af3a8c6t8cc433ee3a1ff22b@mail.gmail.com> > What I need is what you do in swiki with: > > *SqueakDBX - Compiling and installing OpenDBX at OpenDBX and FFI* > > and then in the wiki page "SqueakDBX - Compiling and installing OpenDBX" you > put a "@OpenDBX and FFI" in the title. That's exactly the same in Pier. The Pier Wiki Syntax is a superset of the SmallWiki syntax, which is a superset of the SWiki syntax. Put somewhere into your page: @foo And then jump to that location using: *Go To Page Foo>/somepage at foo* Lukas -- Lukas Renggli http://www.lukas-renggli.ch From marianopeck at gmail.com Mon May 4 00:07:57 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Sun, 3 May 2009 19:07:57 -0300 Subject: Link to a particular title of a page In-Reply-To: <67628d690905031245h5af3a8c6t8cc433ee3a1ff22b@mail.gmail.com> References: <67628d690905031245h5af3a8c6t8cc433ee3a1ff22b@mail.gmail.com> Message-ID: On Sun, May 3, 2009 at 4:45 PM, Lukas Renggli wrote: > > What I need is what you do in swiki with: > > > > *SqueakDBX - Compiling and installing OpenDBX at OpenDBX and FFI* > > > > and then in the wiki page "SqueakDBX - Compiling and installing OpenDBX" > you > > put a "@OpenDBX and FFI" in the title. > > That's exactly the same in Pier. The Pier Wiki Syntax is a superset of > the SmallWiki syntax, which is a superset of the SWiki syntax. > I wasn't aware of this "hierarchy" haha. > > Put somewhere into your page: > > @foo > > And then jump to that location using: > > *Go To Page Foo>/somepage at foo* > It works like a charm! thanks a lot!! > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marianopeck at gmail.com Mon May 4 01:09:18 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Sun, 3 May 2009 20:09:18 -0300 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: <49FDE5A0.1080600@yahoo.co.uk> References: <49FA1845.8010201@yahoo.co.uk> <49FDE5A0.1080600@yahoo.co.uk> Message-ID: Keith: should this work on pharo? Installer install: 'Packages'. Installer ss project: 'Beach-Packages'. Because I am having a warning with Utilities #authorInitialsPerSe deprecated. Use instead initialsPerSe. However, I put "proceed" and my image freezes. Cheers, Mariano On Sun, May 3, 2009 at 3:42 PM, Keith Hodges wrote: > > > Thanks! Now, suppose I want to use it and I want to put the Beach > > dependency I should need the following information: > > > The Email Sender is not dependent upon Beach. > > 1) which are the necessary packages from MC to install > > 2) in which order should I install them > > 3) An explanation somewhere which is each package for. I saw some > > mails in your ANN but there are several packages more. > The information you seek is in the meta-data stored in the > Beach-Packages package, which itself depends upon Sake/Packages. This > can be installed via > > Installer install: 'Packages'. > > I look at google code wiki and squeaksource wiki but I didn't found > > any information. > > > > I am creating a Pier application and would be nice to detail know how > > to integrate beach with Pier. > Keith > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From keith_hodges at yahoo.co.uk Mon May 4 15:10:13 2009 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Mon, 04 May 2009 14:10:13 +0100 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: References: <49FA1845.8010201@yahoo.co.uk> <49FDE5A0.1080600@yahoo.co.uk> Message-ID: <49FEE935.4020302@yahoo.co.uk> Mariano Martinez Peck wrote: > Keith: should this work on pharo? > > Installer install: 'Packages'. > Installer ss project: 'Beach-Packages'. > > Because I am having a warning with Utilities #authorInitialsPerSe > deprecated. Use instead initialsPerSe. > > However, I put "proceed" and my image freezes. > > Cheers, > > Mariano I don't use pharo myself. Goodness knows why they break things as simple as author initials. Keith From marianopeck at gmail.com Mon May 4 15:40:00 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Mon, 4 May 2009 12:40:00 -0100 Subject: Reports in Pier In-Reply-To: <67628d690904292336g122f8d3an9f2130d140ac0f2f@mail.gmail.com> References: <67628d690904292336g122f8d3an9f2130d140ac0f2f@mail.gmail.com> Message-ID: On Thu, Apr 30, 2009 at 5:36 AM, Lukas Renggli wrote: > > Which is the easy way to do this with Pier/Magritte ? I thought to > subclass > > PUReportWidget. Should this be a good idea ? > > Yeah, or even PUStructuresWidget a subclass of PUReportWidget, then > you already get the basic functionality to report on structures. > Nice. It worked perfect. I just subclass and redefine rows like this: rows ^ (self context enumeratorFor: self context root) everything contents select: [ :each | (each class = PBPostWithAuthorization) and: [ each notPublished ] ] I would like to put isPostWithAuthorization in PBStructure instead of using class comparisson as there is also isPost but this will requiere a method extension with *-package :( Thanks for the help! > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From johnmci at smalltalkconsulting.com Mon May 4 18:40:32 2009 From: johnmci at smalltalkconsulting.com (John M McIntosh) Date: Mon, 4 May 2009 09:40:32 -0700 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: <49FEE935.4020302@yahoo.co.uk> References: <49FA1845.8010201@yahoo.co.uk> <49FDE5A0.1080600@yahoo.co.uk> <49FEE935.4020302@yahoo.co.uk> Message-ID: <70C524E4-AD95-4715-89DC-8C95425A84DE@smalltalkconsulting.com> On 4-May-09, at 6:10 AM, Keith Hodges wrote: > I don't use pharo myself. Goodness knows why they break things as > simple > as author initials. > > Keith Er because of the re-licensing of the squeak code base and the discovery that using JUST initials made the chore very difficult to determine who wrote the code. So they enforce names now, since Pharo has a more business target and the first question those folks ask, what's the license and code ownership like? -- = = = ======================================================================== John M. McIntosh Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ======================================================================== From rdrvr.biz at gmail.com Mon May 4 19:55:30 2009 From: rdrvr.biz at gmail.com (David Farber) Date: Mon, 4 May 2009 11:55:30 -0600 Subject: ErrorHandler page with site formatting Message-ID: <37126854-CE8E-4789-A459-B0BCC897CAEC@gmail.com> I would like to generate a simple error acknowledgment message whenever a walkback occurs, but I'd like for the page to have my site's standard formatting (i.e. header and footer). How do I do that? Thanks, David ---- 1 Squeak/Seaside/Pier site deployed From ducasse at iam.unibe.ch Mon May 4 21:57:51 2009 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Mon, 4 May 2009 21:57:51 +0200 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: <70C524E4-AD95-4715-89DC-8C95425A84DE@smalltalkconsulting.com> References: <49FA1845.8010201@yahoo.co.uk> <49FDE5A0.1080600@yahoo.co.uk> <49FEE935.4020302@yahoo.co.uk> <70C524E4-AD95-4715-89DC-8C95425A84DE@smalltalkconsulting.com> Message-ID: but this is true that the author code should be cleaned because it was and this is still a mess. Stef On May 4, 2009, at 6:40 PM, John M McIntosh wrote: > > On 4-May-09, at 6:10 AM, Keith Hodges wrote: > >> I don't use pharo myself. Goodness knows why they break things as >> simple >> as author initials. >> >> Keith > > > Er because of the re-licensing of the squeak code base and the > discovery that using JUST > initials made the chore very difficult to determine who wrote the > code. So they enforce names now, > since Pharo has a more business target and the first question those > folks ask, what's the license > and code ownership like? > > -- > = > = > = > = > = > ====================================================================== > John M. McIntosh Twitter: > squeaker68882 > Corporate Smalltalk Consulting Ltd. http:// > www.smalltalkconsulting.com > = > = > = > = > = > ====================================================================== > > > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From ducasse at iam.unibe.ch Mon May 4 22:01:59 2009 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Mon, 4 May 2009 22:01:59 +0200 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: <49FEE935.4020302@yahoo.co.uk> References: <49FA1845.8010201@yahoo.co.uk> <49FDE5A0.1080600@yahoo.co.uk> <49FEE935.4020302@yahoo.co.uk> Message-ID: Because Utilities is giant anthrax. Stef On May 4, 2009, at 3:10 PM, Keith Hodges wrote: > Mariano Martinez Peck wrote: >> Keith: should this work on pharo? >> >> Installer install: 'Packages'. >> Installer ss project: 'Beach-Packages'. >> >> Because I am having a warning with Utilities #authorInitialsPerSe >> deprecated. Use instead initialsPerSe. >> >> However, I put "proceed" and my image freezes. >> >> Cheers, >> >> Mariano > I don't use pharo myself. Goodness knows why they break things as > simple > as author initials. > > Keith > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From keith_hodges at yahoo.co.uk Mon May 4 23:08:32 2009 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Mon, 04 May 2009 22:08:32 +0100 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: <70C524E4-AD95-4715-89DC-8C95425A84DE@smalltalkconsulting.com> References: <49FA1845.8010201@yahoo.co.uk> <49FDE5A0.1080600@yahoo.co.uk> <49FEE935.4020302@yahoo.co.uk> <70C524E4-AD95-4715-89DC-8C95425A84DE@smalltalkconsulting.com> Message-ID: <49FF5950.4010603@yahoo.co.uk> John M McIntosh wrote: > > On 4-May-09, at 6:10 AM, Keith Hodges wrote: > >> I don't use pharo myself. Goodness knows why they break things as simple >> as author initials. >> >> Keith > > > Er because of the re-licensing of the squeak code base and the > discovery that using JUST > initials made the chore very difficult to determine who wrote the > code. So they enforce names now Thats not my point my point is that they broke the code. The way forward is to engineer a solution, not just hack something in that breaks what everyone has already. One could propose a new loadable Author package that handles everything and publish that for everyone that cares to use it, rather than forcing code to break and all manner of nightmares managing two streams per package. > since Pharo has a more business target and the first question those > folks ask, what's the license > and code ownership like? I use Squeak for Business, and I will continue to do so. The whole approach behind pharo is flawed because it is dedicated to making more work for me the coder of stuff that is for all. This is one instance where I feel entirely justified in saying I told you so. Keith From renggli at gmail.com Tue May 5 00:00:29 2009 From: renggli at gmail.com (Lukas Renggli) Date: Tue, 5 May 2009 00:00:29 +0200 Subject: ErrorHandler page with site formatting In-Reply-To: <37126854-CE8E-4789-A459-B0BCC897CAEC@gmail.com> References: <37126854-CE8E-4789-A459-B0BCC897CAEC@gmail.com> Message-ID: <67628d690905041500x3773cb1fladbca97460f00fe1@mail.gmail.com> There are nice error messages in Pier if the page is not found or you don't have enough permissions. I guess what you ask for is something similar for internal errors. This is currently not implemented. My question is what happens if rendering that error message also causes an error, which is in fact quite likely to happen. So maybe you want to just write a Seaside Error handler that serves static HTML using the design of your site? At least that would guarantee stable results. Cheers, Lukas On Mon, May 4, 2009 at 7:55 PM, David Farber wrote: > I would like to generate a simple error acknowledgment message whenever a > walkback occurs, but I'd like for the page to have my site's standard > formatting (i.e. header and footer). ?How do I do that? > > Thanks, > David > ---- > 1 Squeak/Seaside/Pier site deployed > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli http://www.lukas-renggli.ch From rdrvr.biz at gmail.com Tue May 5 01:57:26 2009 From: rdrvr.biz at gmail.com (David Farber) Date: Mon, 4 May 2009 17:57:26 -0600 Subject: ErrorHandler page with site formatting In-Reply-To: <67628d690905041500x3773cb1fladbca97460f00fe1@mail.gmail.com> References: <37126854-CE8E-4789-A459-B0BCC897CAEC@gmail.com> <67628d690905041500x3773cb1fladbca97460f00fe1@mail.gmail.com> Message-ID: On May 4, 2009, at 4:00 PM, Lukas Renggli wrote: > I guess what you ask for is something similar for internal errors. Yes, that is what I am asking. > This is currently not implemented. My question is what happens if > rendering that error message also causes an error, which is in fact > quite likely to happen. So maybe you want to just write a Seaside > Error handler that serves static HTML using the design of your site? > At least that would guarantee stable results. I currently have a static copy of the site design that I use if seaside/pier is completely unresponsive (i.e. there is a 503 error). So, yeah, I could do the same with 500. The "hard work" of putting the static files in the right place and configuring Apache is already done. Ultimately it would be nice if Pier could export a static copy of the site design automatically. But I've had this question pop up before. And I'd almost prefer to *not* go the static route just because I don't know how to dynamically generate the response I want. Yes, as you pointed out, there is the risk of recursive failure, but right now my site is simple enough that I am willing to take the risk. Thanks, David ---- 1 Squeak/Seaside/Pier site deployed From marianopeck at gmail.com Tue May 5 03:15:49 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Mon, 4 May 2009 22:15:49 -0300 Subject: Posts Authorization In-Reply-To: <67628d690904291507s2e986e4fkb158946fcfe1d807@mail.gmail.com> References: <67628d690904270948p4cf880fejaa02d9accf6463a4@mail.gmail.com> <67628d690904271101ta238cdbx2ae03efc29aec2fb@mail.gmail.com> <67628d690904280114i7622e3c8of7dc71065e3c8b2e@mail.gmail.com> <67628d690904290849x2eda945al5ea564140cff399d@mail.gmail.com> <67628d690904291507s2e986e4fkb158946fcfe1d807@mail.gmail.com> Message-ID: On Wed, Apr 29, 2009 at 7:07 PM, Lukas Renggli wrote: > >> Suppose you are a final user with finalUser group. You will be > >> able to add a PRBlogWithAuthorization but won't be able to add a PRBlog. > >> However, both of them are shown in the list. Ok, I that user selects a > >> PRBlog then Pier says "permission denied". But, I would like to avoid > this > >> step. I mean, each user see in that list the thing he has permissions > for. > > > > I'll have to check this, I thought this was filtered? > > You are right, this is something I missed. I fixed this issue in > Pier-Security-lr.137. Please let me know if this solves the problem. > > Name: Pier-Security-lr.137 > Author: lr > Time: 30 April 2009, 12:06:13 am > UUID: 9ddcb800-7198-4937-8413-d979ffb01263 > Ancestors: Pier-Security-lr.136 > - only show the add actions, that the user actually has the permission for > Similar to this, I have another problem. Suppose finalUser group doesn't have view permission (recursively) in /xxx/_System Management but have permission for adding a PRPostWithAuthentication. When a final user goes to add a Post, in the enchantments editor it has the "Link" and "embedded" options and the links they show, are ALL. Not just the links the user have view permission. Is this correct? If this is true, how can I modify it ? Thanks a lot, Mariano > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marianopeck at gmail.com Tue May 5 04:57:15 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Mon, 4 May 2009 23:57:15 -0300 Subject: Login / Logout / loggedinuser Message-ID: hi all! I think I am doing a mess here. I need to have: 1) a Login link if there is no user logged. Something like *Login>.|command=Login* 2) a Logout if there is a logged user. Something like *Logout>.|command=Logout* 3) Display something like what does loggedinuser (Logged in as +value:user+ (+widget+?)) 4) a Register link if there is no user logged. This is to create a new user. But I want all of them ;) Is there a way of put like ifs in a page ? just to know if there is a user logged. Can I do this just with Pier as it is now or I need to extend, modify or create something ? Thanks! Mariano -------------- next part -------------- An HTML attachment was scrubbed... URL: From marianopeck at gmail.com Tue May 5 05:55:31 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Tue, 5 May 2009 00:55:31 -0300 Subject: I don't understand what parameters are in Pier Message-ID: Hi guys! In a page I want to put a link to its parent. I am aware of +value:parent+ but this only prints the name of the parent. I want a link. In Pier documentation ( http://www.piercms.com/doc/syntax?_s=Sm29MDRQBjStQgra&_k=KGUMf85-&_n&18) I read "Furthermore these expressions become a link if you add the parameter link.". So, the question is, what is a parameter in Pier ? how can I do it ? Perhaps adding an example there would be useful for all of us. Thanks in advance! Mariano -------------- next part -------------- An HTML attachment was scrubbed... URL: From marianopeck at gmail.com Tue May 5 06:00:13 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Tue, 5 May 2009 01:00:13 -0300 Subject: Link to a particular title of a page In-Reply-To: References: <67628d690905031245h5af3a8c6t8cc433ee3a1ff22b@mail.gmail.com> Message-ID: On Sun, May 3, 2009 at 7:07 PM, Mariano Martinez Peck wrote: > > > On Sun, May 3, 2009 at 4:45 PM, Lukas Renggli wrote: > >> > What I need is what you do in swiki with: >> > >> > *SqueakDBX - Compiling and installing OpenDBX at OpenDBX and FFI* >> > >> > and then in the wiki page "SqueakDBX - Compiling and installing OpenDBX" >> you >> > put a "@OpenDBX and FFI" in the title. >> >> That's exactly the same in Pier. The Pier Wiki Syntax is a superset of >> the SmallWiki syntax, which is a superset of the SWiki syntax. >> > > I wasn't aware of this "hierarchy" haha. > > >> >> Put somewhere into your page: >> >> @foo >> >> And then jump to that location using: >> >> *Go To Page Foo>/somepage at foo* >> > > It works like a charm! > I forgot to said that despite I didn't know Pier have the subset of wiki sintax I already tested this before your answer. And I didn't work. Then I realized I was puting more than a word (with white spaces). Example: *Go To Page Foo>/somepage at foo another word* That way, it didn't work for me. Is this a bug ? Thanks! Mariano > > thanks a lot!! > > >> >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marianopeck at gmail.com Tue May 5 06:07:06 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Tue, 5 May 2009 01:07:06 -0300 Subject: Question about renaming a Kernel Message-ID: As most of the newbies, my first Pier kernel was 'pier'. I started developing my site over that kernel and now I want to rename it. I went to /System Management/kernel change pier to 'Destino Mochila' (what I want) and some things seem to have changed. For example: - Browser title now shows Destino Mochila instead of pier - When I put export the file is name DestinoMochila.obj instead of Pier.obj - http://localhost:8888/seaside/config in Kernel option I see a PRKernel name: 'Destino Mochila' But, the application is still here: http://localhost:8888/seaside/pier/ shouldn't this be under http://localhost:8888/seaside/DestinoMochila/ or similar ? Thanks! Mariano -------------- next part -------------- An HTML attachment was scrubbed... URL: From renggli at gmail.com Tue May 5 09:06:07 2009 From: renggli at gmail.com (Lukas Renggli) Date: Tue, 5 May 2009 09:06:07 +0200 Subject: Posts Authorization In-Reply-To: References: <67628d690904270948p4cf880fejaa02d9accf6463a4@mail.gmail.com> <67628d690904271101ta238cdbx2ae03efc29aec2fb@mail.gmail.com> <67628d690904280114i7622e3c8of7dc71065e3c8b2e@mail.gmail.com> <67628d690904290849x2eda945al5ea564140cff399d@mail.gmail.com> <67628d690904291507s2e986e4fkb158946fcfe1d807@mail.gmail.com> Message-ID: <67628d690905050006u5812da6dg1fcbf9ad5b11e6f9@mail.gmail.com> > Similar to this, I have another problem. Suppose finalUser group doesn't > have view permission (recursively) in /xxx/_System Management? but have > permission for adding a PRPostWithAuthentication. When a final user goes to > add a Post, in the enchantments editor it has the "Link" and "embedded" > options and the links they show, are ALL. Not just the links the user have > view permission. Is this correct? If this is true, how can I modify it ? That's a bug. Thanks for pointing out. This is fixed in: Name: Pier-EditorEnh-lr.48 Author: lr Time: 5 May 2009, 9:05:28 am UUID: 49418291-6470-4a75-a9f0-dd9cb1cc58dd Ancestors: Pier-EditorEnh-lr.47 - don't display links without view permission Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at gmail.com Tue May 5 09:07:25 2009 From: renggli at gmail.com (Lukas Renggli) Date: Tue, 5 May 2009 09:07:25 +0200 Subject: I don't understand what parameters are in Pier In-Reply-To: References: Message-ID: <67628d690905050007v5b00e120m5fcece738eec75f1@mail.gmail.com> > In a page I want to put a link to its parent. I am aware of +value:parent+ > but this only prints the name of the parent. I want a link. In Pier > documentation > (http://www.piercms.com/doc/syntax?_s=Sm29MDRQBjStQgra&_k=KGUMf85-&_n&18) I > read "Furthermore these expressions become a link if you add the parameter > link.". So, the question is, what is a parameter in Pier ? how can I do it ? +value:parent|link+ Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at gmail.com Tue May 5 09:12:28 2009 From: renggli at gmail.com (Lukas Renggli) Date: Tue, 5 May 2009 09:12:28 +0200 Subject: Link to a particular title of a page In-Reply-To: References: <67628d690905031245h5af3a8c6t8cc433ee3a1ff22b@mail.gmail.com> Message-ID: <67628d690905050012m3ccc43bas18d2be12200ef3d2@mail.gmail.com> > That way, it didn't work for me. Is this a bug ? I don't know. As far as I remember, SWiki used that name verbatim in the resulting HTML back in 2002. I fixed that issue in Pier-Seaside-lr.397. Name: Pier-Seaside-lr.397 Author: lr Time: 5 May 2009, 9:11:42 am UUID: c5eaafef-13a5-4047-93ae-f82e2cd957a2 Ancestors: Pier-Seaside-lr.396 - filter strange characters from anchors, so that it creates valid xhtml Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at gmail.com Tue May 5 09:14:00 2009 From: renggli at gmail.com (Lukas Renggli) Date: Tue, 5 May 2009 09:14:00 +0200 Subject: Question about renaming a Kernel In-Reply-To: References: Message-ID: <67628d690905050014v586658bm8bf599b18f4e99f7@mail.gmail.com> > But, the application is still here: http://localhost:8888/seaside/pier/ > > shouldn't this be under http://localhost:8888/seaside/DestinoMochila/ or > similar ? That's the Seaside path you installed Pier in. You can change it to something else if you go to /seaside/config. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From ducasse at iam.unibe.ch Tue May 5 09:27:41 2009 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Tue, 5 May 2009 09:27:41 +0200 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: <49FF5950.4010603@yahoo.co.uk> References: <49FA1845.8010201@yahoo.co.uk> <49FDE5A0.1080600@yahoo.co.uk> <49FEE935.4020302@yahoo.co.uk> <70C524E4-AD95-4715-89DC-8C95425A84DE@smalltalkconsulting.com> <49FF5950.4010603@yahoo.co.uk> Message-ID: <74857A22-4A0C-4361-B673-CC3B2FD4FB22@iam.unibe.ch> >>> >> >> >> Er because of the re-licensing of the squeak code base and the >> discovery that using JUST >> initials made the chore very difficult to determine who wrote the >> code. So they enforce names now > Thats not my point my point is that they broke the code. > > The way forward is to engineer a solution, not just hack something in > that breaks what everyone has already. > > One could propose a new loadable Author package that handles > everything > and publish that for everyone that cares to use it, rather than > forcing > code to break and all manner of nightmares managing two streams per > package. Yes you are right. But we have pretty limited resources. > >> since Pharo has a more business target and the first question those >> folks ask, what's the license >> and code ownership like? > I use Squeak for Business, and I will continue to do so. The whole > approach behind pharo is flawed because it is dedicated to making more > work for me the coder of stuff that is for all. This is one instance > where I feel entirely justified in saying I told you so. So do not use pharo! Please don't! Stef > > > Keith > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From ducasse at iam.unibe.ch Tue May 5 09:33:17 2009 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Tue, 5 May 2009 09:33:17 +0200 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: <49FF5950.4010603@yahoo.co.uk> References: <49FA1845.8010201@yahoo.co.uk> <49FDE5A0.1080600@yahoo.co.uk> <49FEE935.4020302@yahoo.co.uk> <70C524E4-AD95-4715-89DC-8C95425A84DE@smalltalkconsulting.com> <49FF5950.4010603@yahoo.co.uk> Message-ID: <1F530FD6-596C-4CA3-8D4E-875A6F1FBEA7@iam.unibe.ch> Apparently there is no value in what we are doing: removing etoy, removing a lot of ***SHIT*** from squeak, fixing tons of bugs (the bug archives is full of fixed bugs and fixes problems), writing more tests, cleaning a HUGE spaghetti mess (preferences....). Utilities is one of this crap. And of course Author could be made a bit better. Of course there is no preference to avoid to warn on deprecated call! Apparently you only do stuff right. Perfect! But we will do it our way. Period. May be you should put your code under GPL or something like that we will not even thing that we should have a look at it. What we are doing is totally useless for you. Excellent! Continue to bark if this helps you. Stef On May 4, 2009, at 11:08 PM, Keith Hodges wrote: > John M McIntosh wrote: >> >> On 4-May-09, at 6:10 AM, Keith Hodges wrote: >> >>> I don't use pharo myself. Goodness knows why they break things as >>> simple >>> as author initials. >>> >>> Keith >> >> >> Er because of the re-licensing of the squeak code base and the >> discovery that using JUST >> initials made the chore very difficult to determine who wrote the >> code. So they enforce names now > Thats not my point my point is that they broke the code. > > The way forward is to engineer a solution, not just hack something in > that breaks what everyone has already. > > One could propose a new loadable Author package that handles > everything > and publish that for everyone that cares to use it, rather than > forcing > code to break and all manner of nightmares managing two streams per > package. >> since Pharo has a more business target and the first question those >> folks ask, what's the license >> and code ownership like? > I use Squeak for Business, and I will continue to do so. The whole > approach behind pharo is flawed because it is dedicated to making more > work for me the coder of stuff that is for all. This is one instance > where I feel entirely justified in saying I told you so. > > Keith > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From girba at iam.unibe.ch Tue May 5 09:36:52 2009 From: girba at iam.unibe.ch (Tudor Girba) Date: Tue, 5 May 2009 09:36:52 +0200 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: <1F530FD6-596C-4CA3-8D4E-875A6F1FBEA7@iam.unibe.ch> References: <49FA1845.8010201@yahoo.co.uk> <49FDE5A0.1080600@yahoo.co.uk> <49FEE935.4020302@yahoo.co.uk> <70C524E4-AD95-4715-89DC-8C95425A84DE@smalltalkconsulting.com> <49FF5950.4010603@yahoo.co.uk> <1F530FD6-596C-4CA3-8D4E-875A6F1FBEA7@iam.unibe.ch> Message-ID: <3C099767-00FA-44A4-B4CF-49D81B39BA1F@iam.unibe.ch> Hi guys, I believe this mail exchange belongs to the Pharo and not to the Smallwiki mailing list :). Cheers, Doru On 5 May 2009, at 09:33, st?phane ducasse wrote: > Apparently there is no value in what we are doing: > removing etoy, removing a lot of ***SHIT*** from squeak, fixing tons > of bugs (the bug archives > is full of fixed bugs and fixes problems), writing more tests, > cleaning a HUGE spaghetti mess > (preferences....). Utilities is one of this crap. And of course > Author could be made a bit better. > Of course there is no preference to avoid to warn on deprecated call! > > Apparently you only do stuff right. Perfect! But we will do it our > way. Period. > > May be you should put your code under GPL or something like that > we will not even thing that we should have a look at it. > > What we are doing is totally useless for you. Excellent! Continue to > bark if this > helps you. > > Stef > > > On May 4, 2009, at 11:08 PM, Keith Hodges wrote: > >> John M McIntosh wrote: >>> >>> On 4-May-09, at 6:10 AM, Keith Hodges wrote: >>> >>>> I don't use pharo myself. Goodness knows why they break things as >>>> simple >>>> as author initials. >>>> >>>> Keith >>> >>> >>> Er because of the re-licensing of the squeak code base and the >>> discovery that using JUST >>> initials made the chore very difficult to determine who wrote the >>> code. So they enforce names now >> Thats not my point my point is that they broke the code. >> >> The way forward is to engineer a solution, not just hack something in >> that breaks what everyone has already. >> >> One could propose a new loadable Author package that handles >> everything >> and publish that for everyone that cares to use it, rather than >> forcing >> code to break and all manner of nightmares managing two streams per >> package. >>> since Pharo has a more business target and the first question those >>> folks ask, what's the license >>> and code ownership like? >> I use Squeak for Business, and I will continue to do so. The whole >> approach behind pharo is flawed because it is dedicated to making >> more >> work for me the coder of stuff that is for all. This is one instance >> where I feel entirely justified in saying I told you so. >> >> Keith >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com "What is more important: To be happy, or to make happy?" From johnmci at smalltalkconsulting.com Tue May 5 10:17:26 2009 From: johnmci at smalltalkconsulting.com (John M McIntosh) Date: Tue, 5 May 2009 01:17:26 -0700 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: <1F530FD6-596C-4CA3-8D4E-875A6F1FBEA7@iam.unibe.ch> References: <49FA1845.8010201@yahoo.co.uk> <49FDE5A0.1080600@yahoo.co.uk> <49FEE935.4020302@yahoo.co.uk> <70C524E4-AD95-4715-89DC-8C95425A84DE@smalltalkconsulting.com> <49FF5950.4010603@yahoo.co.uk> <1F530FD6-596C-4CA3-8D4E-875A6F1FBEA7@iam.unibe.ch> Message-ID: Tsk, well I was off to bed, but thought I should make some notes. Last night I push out two electronic books showing smalltalk-80 based source code to Apple for iPhone review. One was based on the latest pharo of end of april 09 with closures the other based on the sq3.10.2-719web09.04.1.zip no closures. The two e-books apps are identical except for the code base. I dropped the wikiserver stuff into both, happy since the changes required were non-existent for pharo and one or two for sq3.10.2 (a) The sq3.10.2 version was missing some of the extra add-on Pier stuff, and has the LGPL Swazoo which makes some folks run for the fire exit. (b) The pharo image is 20.2 mb, the sq3.10.2 is 25.2 mb, so 5MB bigger. (c) The pharo image needed about 35mb of ram to be happy, the sq 3.10.2 about 40mb (c2) The pharo image ramps to the welcome screen using 19.23 mb ram, 97.12mb virtual (c3) The sq 3.10.2 image ramps using 19.05mb and 102.12 virtual. This makes sense because I avoid a full gc and doing allInstances, so the code base is really startup logic and seaside. (I had to fix the sq 3.10.2 image because of ignored bug using allInstances I reported years back, never fixed, but fixed in pharo last fall). (d) The pharo image needs 2.6 to 6.6% cpu on the iphone at idle, the sq 3.10.2 needs 8 to 18% (to be fair here I could bring some fixes into the 3.10.2 image to reduce the cpu time, but really those fixes should have gone in years ago...) (e) The sq 3.10.2 book feels sluggish. the pharo less so. So the sq 3.10.2 excessive CPU usage is the usability killer here. To be fair WikiServer is happy with 20MB of ram with a 10.5MB image size, and runs with a 0 to 0.9% cpu usage at idle, starup ram of 11.69, virtual memory of 90.34 Lots of hours to get there.. PS I see the etoys image is only 16.4 MB, well that doesn't include seaside etc, but if you need that you should start with etoys as the base and add pier and seaside, less bloated I'd guess, and supported for that etoy feature set you need? On 5-May-09, at 12:33 AM, st?phane ducasse wrote: > Apparently there is no value in what we are doing: > removing etoy, removing a lot of ***SHIT*** from squeak, fixing tons > of bugs (the bug archives > is full of fixed bugs and fixes problems), writing more tests, > cleaning a HUGE spaghetti mess > (preferences....). Utilities is one of this crap. And of course > Author could be made a bit better. > Of course there is no preference to avoid to warn on deprecated call! > > Apparently you only do stuff right. Perfect! But we will do it our > way. Period. > > May be you should put your code under GPL or something like that > we will not even thing that we should have a look at it. > > What we are doing is totally useless for you. Excellent! Continue to > bark if this > helps you. > > Stef > -- = = = ======================================================================== John M. McIntosh Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ======================================================================== From ducasse at iam.unibe.ch Tue May 5 10:28:40 2009 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Tue, 5 May 2009 10:28:40 +0200 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: References: <49FA1845.8010201@yahoo.co.uk> <49FDE5A0.1080600@yahoo.co.uk> <49FEE935.4020302@yahoo.co.uk> <70C524E4-AD95-4715-89DC-8C95425A84DE@smalltalkconsulting.com> <49FF5950.4010603@yahoo.co.uk> <1F530FD6-596C-4CA3-8D4E-875A6F1FBEA7@iam.unibe.ch> Message-ID: <028A9603-C2B8-456C-9C05-5C04B2DEE421@iam.unibe.ch> John for your images did you remove tests and other unnecessary stuff? The 10300 is 12.7mb without removing all kind of crap like the scriptLoader and the tests. I hope that we will be able to slowly get more and more modular: once project/bookmorph are gone. I imagine (did not read carefully the details of we got about the chase of the unclosed handles) that the startup behavior could be also improved. Stef On May 5, 2009, at 10:17 AM, John M McIntosh wrote: > Tsk, well I was off to bed, but thought I should make some notes. > > Last night I push out two electronic books showing smalltalk-80 > based source code to Apple for iPhone review. > One was based on the latest pharo of end of april 09 with closures > the other based on the sq3.10.2-719web09.04.1.zip no closures. > The two e-books apps are identical except for the code base. > > I dropped the wikiserver stuff into both, happy since the changes > required were non-existent for pharo and one or two for sq3.10.2 > > (a) The sq3.10.2 version was missing some of the extra add-on Pier > stuff, and has the LGPL Swazoo which makes some folks run for the > fire exit. > > (b) The pharo image is 20.2 mb, the sq3.10.2 is 25.2 mb, so 5MB > bigger. > > (c) The pharo image needed about 35mb of ram to be happy, the sq > 3.10.2 about 40mb > (c2) The pharo image ramps to the welcome screen using 19.23 mb ram, > 97.12mb virtual > (c3) The sq 3.10.2 image ramps using 19.05mb and 102.12 virtual. > This makes sense because I avoid a full gc and doing allInstances, > so the code base is really startup logic and seaside. > (I had to fix the sq 3.10.2 image because of ignored bug using > allInstances I reported years back, never fixed, but fixed in pharo > last fall). > > (d) The pharo image needs 2.6 to 6.6% cpu on the iphone at idle, the > sq 3.10.2 needs 8 to 18% > (to be fair here I could bring some fixes into the 3.10.2 image to > reduce the cpu time, but really those fixes should have gone in > years ago...) > > (e) The sq 3.10.2 book feels sluggish. the pharo less so. So the sq > 3.10.2 excessive CPU usage is the usability killer here. > > To be fair WikiServer is happy with 20MB of ram with a 10.5MB image > size, and runs with a 0 to 0.9% cpu usage at idle, starup ram of > 11.69, virtual memory of 90.34 > Lots of hours to get there.. > > PS I see the etoys image is only 16.4 MB, well that doesn't include > seaside etc, but if you need that you should start with etoys as the > base and add pier and seaside, less bloated I'd guess, and supported > for that etoy feature set you need? > > > On 5-May-09, at 12:33 AM, st?phane ducasse wrote: > >> Apparently there is no value in what we are doing: >> removing etoy, removing a lot of ***SHIT*** from squeak, fixing >> tons of bugs (the bug archives >> is full of fixed bugs and fixes problems), writing more tests, >> cleaning a HUGE spaghetti mess >> (preferences....). Utilities is one of this crap. And of course >> Author could be made a bit better. >> Of course there is no preference to avoid to warn on deprecated call! >> >> Apparently you only do stuff right. Perfect! But we will do it our >> way. Period. >> >> May be you should put your code under GPL or something like that >> we will not even thing that we should have a look at it. >> >> What we are doing is totally useless for you. Excellent! Continue >> to bark if this >> helps you. >> >> Stef >> > > -- > = > = > = > = > = > ====================================================================== > John M. McIntosh Twitter: > squeaker68882 > Corporate Smalltalk Consulting Ltd. http:// > www.smalltalkconsulting.com > = > = > = > = > = > ====================================================================== > > > > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > From andreas.raab at gmx.de Tue May 5 11:07:01 2009 From: andreas.raab at gmx.de (Andreas Raab) Date: Tue, 05 May 2009 02:07:01 -0700 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: References: <49FA1845.8010201@yahoo.co.uk> <49FDE5A0.1080600@yahoo.co.uk> <49FEE935.4020302@yahoo.co.uk> <70C524E4-AD95-4715-89DC-8C95425A84DE@smalltalkconsulting.com> <49FF5950.4010603@yahoo.co.uk> <1F530FD6-596C-4CA3-8D4E-875A6F1FBEA7@iam.unibe.ch> Message-ID: <4A0001B5.6060300@gmx.de> Hi John - John M McIntosh wrote: > (I had to fix the sq 3.10.2 image because of ignored bug using > allInstances I reported years back, never fixed, but fixed in pharo last > fall). [... snip ...] > (to be fair here I could bring some fixes into the 3.10.2 image to > reduce the cpu time, but really those fixes should have gone in years > ago...) Just as an FYI, there is now a well-defined process for contributing stuff to 3.11: http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-February/134095.html If these fixes are on Mantis all you need is to provide an installer script and update its status accordingly. Just try it! Cheers, - Andreas From marianopeck at gmail.com Tue May 5 14:45:17 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Tue, 5 May 2009 11:45:17 -0100 Subject: I don't understand what parameters are in Pier In-Reply-To: <67628d690905050007v5b00e120m5fcece738eec75f1@mail.gmail.com> References: <67628d690905050007v5b00e120m5fcece738eec75f1@mail.gmail.com> Message-ID: On Tue, May 5, 2009 at 6:07 AM, Lukas Renggli wrote: > > In a page I want to put a link to its parent. I am aware of > +value:parent+ > > but this only prints the name of the parent. I want a link. In Pier > > documentation > > (http://www.piercms.com/doc/syntax?_s=Sm29MDRQBjStQgra&_k=KGUMf85-&_n&18) > I > > read "Furthermore these expressions become a link if you add the > parameter > > link.". So, the question is, what is a parameter in Pier ? how can I do > it ? > > +value:parent|link+ > Ahhh those are parameter!!! ;) Works perfect! Thanks! Mariano > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From johnmci at smalltalkconsulting.com Tue May 5 17:49:41 2009 From: johnmci at smalltalkconsulting.com (John M McIntosh) Date: Tue, 5 May 2009 08:49:41 -0700 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: <4A0001B5.6060300@gmx.de> References: <49FA1845.8010201@yahoo.co.uk> <49FDE5A0.1080600@yahoo.co.uk> <49FEE935.4020302@yahoo.co.uk> <70C524E4-AD95-4715-89DC-8C95425A84DE@smalltalkconsulting.com> <49FF5950.4010603@yahoo.co.uk> <1F530FD6-596C-4CA3-8D4E-875A6F1FBEA7@iam.unibe.ch> <4A0001B5.6060300@gmx.de> Message-ID: Well then for http://bugs.squeak.org/view.php?id=6581 who would stick that into 3.11? Let alone that I'm looking at 3.10.2 image Added (partly) http://bugs.squeak.org/view.php?id=7348 On 5-May-09, at 2:07 AM, Andreas Raab wrote: > Hi John - > > John M McIntosh wrote: >> (I had to fix the sq 3.10.2 image because of ignored bug using >> allInstances I reported years back, never fixed, but fixed in pharo >> last fall). > > [... snip ...] > >> (to be fair here I could bring some fixes into the 3.10.2 image to >> reduce the cpu time, but really those fixes should have gone in >> years ago...) > > Just as an FYI, there is now a well-defined process for contributing > stuff to 3.11: > > http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-February/134095.html > > If these fixes are on Mantis all you need is to provide an installer > script and update its status accordingly. Just try it! > > Cheers, > - Andreas -- = = = ======================================================================== John M. McIntosh Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ======================================================================== From johnmci at smalltalkconsulting.com Tue May 5 17:53:20 2009 From: johnmci at smalltalkconsulting.com (John M McIntosh) Date: Tue, 5 May 2009 08:53:20 -0700 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: <028A9603-C2B8-456C-9C05-5C04B2DEE421@iam.unibe.ch> References: <49FA1845.8010201@yahoo.co.uk> <49FDE5A0.1080600@yahoo.co.uk> <49FEE935.4020302@yahoo.co.uk> <70C524E4-AD95-4715-89DC-8C95425A84DE@smalltalkconsulting.com> <49FF5950.4010603@yahoo.co.uk> <1F530FD6-596C-4CA3-8D4E-875A6F1FBEA7@iam.unibe.ch> <028A9603-C2B8-456C-9C05-5C04B2DEE421@iam.unibe.ch> Message-ID: <444B5453-61C2-4362-92F4-9ABA862C0FAF@smalltalkconsulting.com> No, the intent is preserve the images as they are shipped see http://www.mobilewikiserver.com/ST80Docs.html & http://www.mobilewikiserver.com/SqueakDocs.html However if you have a script that removals all the *extra* things that people could run for server images that would be helpful at least to me, I realize that most folks don't care about 8MB, but on tiny devices that 8MB is golden... On 5-May-09, at 1:28 AM, st?phane ducasse wrote: > John > > for your images did you remove tests and other unnecessary stuff? > The 10300 is 12.7mb without removing all kind of crap like the > scriptLoader and the tests. > I hope that we will be able to slowly get more and more modular: > once project/bookmorph are gone. > I imagine (did not read carefully the details of we got about the > chase of the unclosed handles) > that the startup behavior could be also improved. > > Stef > > On May 5, 2009, at 10:17 AM, John M McIntosh wrote: > >> Tsk, well I was off to bed, but thought I should make some notes. >> >> Last night I push out two electronic books showing smalltalk-80 >> based source code to Apple for iPhone review. >> One was based on the latest pharo of end of april 09 with closures >> the other based on the sq3.10.2-719web09.04.1.zip no closures. >> The two e-books apps are identical except for the code base. >> >> I dropped the wikiserver stuff into both, happy since the changes >> required were non-existent for pharo and one or two for sq3.10.2 >> >> (a) The sq3.10.2 version was missing some of the extra add-on Pier >> stuff, and has the LGPL Swazoo which makes some folks run for the >> fire exit. >> >> (b) The pharo image is 20.2 mb, the sq3.10.2 is 25.2 mb, so 5MB >> bigger. >> >> (c) The pharo image needed about 35mb of ram to be happy, the sq >> 3.10.2 about 40mb >> (c2) The pharo image ramps to the welcome screen using 19.23 mb >> ram, 97.12mb virtual >> (c3) The sq 3.10.2 image ramps using 19.05mb and 102.12 virtual. >> This makes sense because I avoid a full gc and doing allInstances, >> so the code base is really startup logic and seaside. >> (I had to fix the sq 3.10.2 image because of ignored bug using >> allInstances I reported years back, never fixed, but fixed in pharo >> last fall). >> >> (d) The pharo image needs 2.6 to 6.6% cpu on the iphone at idle, >> the sq 3.10.2 needs 8 to 18% >> (to be fair here I could bring some fixes into the 3.10.2 image to >> reduce the cpu time, but really those fixes should have gone in >> years ago...) >> >> (e) The sq 3.10.2 book feels sluggish. the pharo less so. So the sq >> 3.10.2 excessive CPU usage is the usability killer here. >> >> To be fair WikiServer is happy with 20MB of ram with a 10.5MB image >> size, and runs with a 0 to 0.9% cpu usage at idle, starup ram of >> 11.69, virtual memory of 90.34 >> Lots of hours to get there.. >> >> PS I see the etoys image is only 16.4 MB, well that doesn't include >> seaside etc, but if you need that you should start with etoys as >> the base and add pier and seaside, less bloated I'd guess, and >> supported for that etoy feature set you need? = = = ======================================================================== John M. McIntosh Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ======================================================================== From andreas.raab at gmx.de Tue May 5 18:05:09 2009 From: andreas.raab at gmx.de (Andreas Raab) Date: Tue, 05 May 2009 09:05:09 -0700 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: References: <49FA1845.8010201@yahoo.co.uk> <49FDE5A0.1080600@yahoo.co.uk> <49FEE935.4020302@yahoo.co.uk> <70C524E4-AD95-4715-89DC-8C95425A84DE@smalltalkconsulting.com> <49FF5950.4010603@yahoo.co.uk> <1F530FD6-596C-4CA3-8D4E-875A6F1FBEA7@iam.unibe.ch> <4A0001B5.6060300@gmx.de> Message-ID: <4A0063B5.2070103@gmx.de> I'll check it out. Also note that cc-ing release at lists.squeakfoundation.org will generally be useful. Cheers, - Andreas John M McIntosh wrote: > Well then for http://bugs.squeak.org/view.php?id=6581 > who would stick that into 3.11? Let alone that I'm looking at 3.10.2 image > > > Added (partly) > http://bugs.squeak.org/view.php?id=7348 > > On 5-May-09, at 2:07 AM, Andreas Raab wrote: > >> Hi John - >> >> John M McIntosh wrote: >>> (I had to fix the sq 3.10.2 image because of ignored bug using >>> allInstances I reported years back, never fixed, but fixed in pharo >>> last fall). >> >> [... snip ...] >> >>> (to be fair here I could bring some fixes into the 3.10.2 image to >>> reduce the cpu time, but really those fixes should have gone in years >>> ago...) >> >> Just as an FYI, there is now a well-defined process for contributing >> stuff to 3.11: >> >> http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-February/134095.html >> >> >> If these fixes are on Mantis all you need is to provide an installer >> script and update its status accordingly. Just try it! >> >> Cheers, >> - Andreas > > -- > =========================================================================== > John M. McIntosh Twitter: > squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > From johnmci at smalltalkconsulting.com Tue May 5 18:09:19 2009 From: johnmci at smalltalkconsulting.com (John M McIntosh) Date: Tue, 5 May 2009 09:09:19 -0700 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: <4A0063B5.2070103@gmx.de> References: <49FA1845.8010201@yahoo.co.uk> <49FDE5A0.1080600@yahoo.co.uk> <49FEE935.4020302@yahoo.co.uk> <70C524E4-AD95-4715-89DC-8C95425A84DE@smalltalkconsulting.com> <49FF5950.4010603@yahoo.co.uk> <1F530FD6-596C-4CA3-8D4E-875A6F1FBEA7@iam.unibe.ch> <4A0001B5.6060300@gmx.de> <4A0063B5.2070103@gmx.de> Message-ID: <5605B2D0-83B4-4F2A-BBEF-3F762703F367@smalltalkconsulting.com> I note if you go to the squeak.org website and tap but report it dumps you into Mantis. However for novices that likely isn't helpful and the link to a mail message from Feb isn't something anyone is going to find, or mmm or remember. On 5-May-09, at 9:05 AM, Andreas Raab wrote: > I'll check it out. Also note that cc-ing release at lists.squeakfoundation.org > will generally be useful. > > Cheers, > - Andreas > > John M McIntosh wrote: >> Well then for http://bugs.squeak.org/view.php?id=6581 >> who would stick that into 3.11? Let alone that I'm looking at >> 3.10.2 image >> Added (partly) >> http://bugs.squeak.org/view.php?id=7348 >> On 5-May-09, at 2:07 AM, Andreas Raab wrote: >>> Hi John - >>> >>> John M McIntosh wrote: >>>> (I had to fix the sq 3.10.2 image because of ignored bug using >>>> allInstances I reported years back, never fixed, but fixed in >>>> pharo last fall). >>> >>> [... snip ...] >>> >>>> (to be fair here I could bring some fixes into the 3.10.2 image >>>> to reduce the cpu time, but really those fixes should have gone >>>> in years ago...) >>> >>> Just as an FYI, there is now a well-defined process for >>> contributing stuff to 3.11: >>> >>> http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-February/134095.html >>> >>> If these fixes are on Mantis all you need is to provide an >>> installer script and update its status accordingly. Just try it! >>> >>> Cheers, >>> - Andreas -- = = = ======================================================================== John M. McIntosh Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ======================================================================== From andreas.raab at gmx.de Tue May 5 18:27:54 2009 From: andreas.raab at gmx.de (Andreas Raab) Date: Tue, 05 May 2009 09:27:54 -0700 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: <5605B2D0-83B4-4F2A-BBEF-3F762703F367@smalltalkconsulting.com> References: <49FA1845.8010201@yahoo.co.uk> <49FDE5A0.1080600@yahoo.co.uk> <49FEE935.4020302@yahoo.co.uk> <70C524E4-AD95-4715-89DC-8C95425A84DE@smalltalkconsulting.com> <49FF5950.4010603@yahoo.co.uk> <1F530FD6-596C-4CA3-8D4E-875A6F1FBEA7@iam.unibe.ch> <4A0001B5.6060300@gmx.de> <4A0063B5.2070103@gmx.de> <5605B2D0-83B4-4F2A-BBEF-3F762703F367@smalltalkconsulting.com> Message-ID: <4A00690A.4050200@gmx.de> Yes, good point. I've put it on the agenda for the board meeting: http://squeakboard.wordpress.com/2009/04/22/initial-agenda-for-may-7th-2009/ Cheers, - Andreas John M McIntosh wrote: > I note if you go to the squeak.org website and tap but report it dumps > you into Mantis. However for novices that likely isn't helpful > and the link to a mail message from Feb isn't something anyone is going > to find, or mmm or remember. > > On 5-May-09, at 9:05 AM, Andreas Raab wrote: > >> I'll check it out. Also note that cc-ing >> release at lists.squeakfoundation.org will generally be useful. >> >> Cheers, >> - Andreas >> >> John M McIntosh wrote: >>> Well then for http://bugs.squeak.org/view.php?id=6581 >>> who would stick that into 3.11? Let alone that I'm looking at 3.10.2 >>> image >>> Added (partly) >>> http://bugs.squeak.org/view.php?id=7348 >>> On 5-May-09, at 2:07 AM, Andreas Raab wrote: >>>> Hi John - >>>> >>>> John M McIntosh wrote: >>>>> (I had to fix the sq 3.10.2 image because of ignored bug using >>>>> allInstances I reported years back, never fixed, but fixed in pharo >>>>> last fall). >>>> >>>> [... snip ...] >>>> >>>>> (to be fair here I could bring some fixes into the 3.10.2 image to >>>>> reduce the cpu time, but really those fixes should have gone in >>>>> years ago...) >>>> >>>> Just as an FYI, there is now a well-defined process for contributing >>>> stuff to 3.11: >>>> >>>> http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-February/134095.html >>>> >>>> >>>> If these fixes are on Mantis all you need is to provide an installer >>>> script and update its status accordingly. Just try it! >>>> >>>> Cheers, >>>> - Andreas > > -- > =========================================================================== > John M. McIntosh Twitter: > squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > From ducasse at iam.unibe.ch Tue May 5 22:18:02 2009 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Tue, 5 May 2009 22:18:02 +0200 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: <444B5453-61C2-4362-92F4-9ABA862C0FAF@smalltalkconsulting.com> References: <49FA1845.8010201@yahoo.co.uk> <49FDE5A0.1080600@yahoo.co.uk> <49FEE935.4020302@yahoo.co.uk> <70C524E4-AD95-4715-89DC-8C95425A84DE@smalltalkconsulting.com> <49FF5950.4010603@yahoo.co.uk> <1F530FD6-596C-4CA3-8D4E-875A6F1FBEA7@iam.unibe.ch> <028A9603-C2B8-456C-9C05-5C04B2DEE421@iam.unibe.ch> <444B5453-61C2-4362-92F4-9ABA862C0FAF@smalltalkconsulting.com> Message-ID: <0A91DC91-7448-4492-92B6-A6E9A118D6CC@iam.unibe.ch> marcus told me once that scriptloader was already getting a big class with a lot of method. For now I do not have something else than removing all tests and scriptloader. I removed a lot of bookMorph but still it is hanging there :) Stef On May 5, 2009, at 5:53 PM, John M McIntosh wrote: > No, the intent is preserve the images as they are shipped see > > http://www.mobilewikiserver.com/ST80Docs.html > & > http://www.mobilewikiserver.com/SqueakDocs.html > > However if you have a script that removals all the *extra* things > that people could run for server images that would be helpful at > least to me, > I realize that most folks don't care about 8MB, but on tiny devices > that 8MB is golden... > > > On 5-May-09, at 1:28 AM, st?phane ducasse wrote: > >> John >> >> for your images did you remove tests and other unnecessary stuff? >> The 10300 is 12.7mb without removing all kind of crap like the >> scriptLoader and the tests. >> I hope that we will be able to slowly get more and more modular: >> once project/bookmorph are gone. >> I imagine (did not read carefully the details of we got about the >> chase of the unclosed handles) >> that the startup behavior could be also improved. >> >> Stef >> >> On May 5, 2009, at 10:17 AM, John M McIntosh wrote: >> >>> Tsk, well I was off to bed, but thought I should make some notes. >>> >>> Last night I push out two electronic books showing smalltalk-80 >>> based source code to Apple for iPhone review. >>> One was based on the latest pharo of end of april 09 with closures >>> the other based on the sq3.10.2-719web09.04.1.zip no closures. >>> The two e-books apps are identical except for the code base. >>> >>> I dropped the wikiserver stuff into both, happy since the changes >>> required were non-existent for pharo and one or two for sq3.10.2 >>> >>> (a) The sq3.10.2 version was missing some of the extra add-on >>> Pier stuff, and has the LGPL Swazoo which makes some folks run for >>> the fire exit. >>> >>> (b) The pharo image is 20.2 mb, the sq3.10.2 is 25.2 mb, so 5MB >>> bigger. >>> >>> (c) The pharo image needed about 35mb of ram to be happy, the sq >>> 3.10.2 about 40mb >>> (c2) The pharo image ramps to the welcome screen using 19.23 mb >>> ram, 97.12mb virtual >>> (c3) The sq 3.10.2 image ramps using 19.05mb and 102.12 virtual. >>> This makes sense because I avoid a full gc and doing allInstances, >>> so the code base is really startup logic and seaside. >>> (I had to fix the sq 3.10.2 image because of ignored bug using >>> allInstances I reported years back, never fixed, but fixed in >>> pharo last fall). >>> >>> (d) The pharo image needs 2.6 to 6.6% cpu on the iphone at idle, >>> the sq 3.10.2 needs 8 to 18% >>> (to be fair here I could bring some fixes into the 3.10.2 image to >>> reduce the cpu time, but really those fixes should have gone in >>> years ago...) >>> >>> (e) The sq 3.10.2 book feels sluggish. the pharo less so. So the >>> sq 3.10.2 excessive CPU usage is the usability killer here. >>> >>> To be fair WikiServer is happy with 20MB of ram with a 10.5MB >>> image size, and runs with a 0 to 0.9% cpu usage at idle, starup >>> ram of 11.69, virtual memory of 90.34 >>> Lots of hours to get there.. >>> >>> PS I see the etoys image is only 16.4 MB, well that doesn't >>> include seaside etc, but if you need that you should start with >>> etoys as the base and add pier and seaside, less bloated I'd >>> guess, and supported for that etoy feature set you need? > > = > = > = > = > = > ====================================================================== > John M. McIntosh Twitter: > squeaker68882 > Corporate Smalltalk Consulting Ltd. http:// > www.smalltalkconsulting.com > = > = > = > = > = > ====================================================================== > > > > > From marianopeck at gmail.com Tue May 5 22:24:33 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Tue, 5 May 2009 19:24:33 -0100 Subject: Pier components internationalization Message-ID: Sorry to bother again with this, but I really need it. I need to internationalize Pier components. I am doing a site with Pier for Spanish people. The final user has access to Pier components. For example, it can leave comments or even post. But pier components have the html outputs in English. For example when you are going to create a post you have "author, publish, tags, ..." and I want "autor, publicacion, etiquetas...". I think Pier give CMS a new and higher level to CMS. I think there is a field in websites that can start being done with Pier, but they are no "CMS traditional". For example, in my case, I am making a tourism website with Pier. This sounds strange isn't it ? However It give me lots of features: 1) Do a lot with very little time and code 2) Dynamism: I can modify my website at any moment just using a browser. 3) The website can be built with business people. For example my friend (Tourisim graduated). Hi doesn't now anything about computer neither wiki. I explained few things: edit a page, add a page, links and now, he is building the website with me. Ok, not all of it, but parts. 4) I am making the first tourism website I know where the final user can be part of. I think Pier+Seaside+Magritte has all the power and capabilities to spread about this new field. But, for this, is very important to have int18. Ok, after said that, I want to add int18 to my website but I don't want to touch Pier code. So, the solution I thought is this: override String #printOn: or Object #printString (which one could be better?) to something like this: (suppose I override printOn:) printOn: aStream "Print inside string quotes, doubling inbedded quotes." self size < 100 ifTrue: [ self localize storeOn: aStream ] ifFalse: [ self storeOn: aStream ] Then I define localize like this: localize ^ WACurrentSession value ifNotNilDo: [ :session | session language localize: self ]. And then the Langauge # localize could be something like this: localize: aString ^self localizationMap at: aString ifAbsent: [ aString ]. Obviously all of this methods will be with category *MiApp (an extension). Could this be a good idea? Any other solution ? Thanks in advance, Mariano -------------- next part -------------- An HTML attachment was scrubbed... URL: From marianopeck at gmail.com Wed May 6 01:09:53 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Tue, 5 May 2009 20:09:53 -0300 Subject: Posts Authorization In-Reply-To: <67628d690905050006u5812da6dg1fcbf9ad5b11e6f9@mail.gmail.com> References: <67628d690904271101ta238cdbx2ae03efc29aec2fb@mail.gmail.com> <67628d690904280114i7622e3c8of7dc71065e3c8b2e@mail.gmail.com> <67628d690904290849x2eda945al5ea564140cff399d@mail.gmail.com> <67628d690904291507s2e986e4fkb158946fcfe1d807@mail.gmail.com> <67628d690905050006u5812da6dg1fcbf9ad5b11e6f9@mail.gmail.com> Message-ID: On Tue, May 5, 2009 at 4:06 AM, Lukas Renggli wrote: > > Similar to this, I have another problem. Suppose finalUser group doesn't > > have view permission (recursively) in /xxx/_System Management but have > > permission for adding a PRPostWithAuthentication. When a final user goes > to > > add a Post, in the enchantments editor it has the "Link" and "embedded" > > options and the links they show, are ALL. Not just the links the user > have > > view permission. Is this correct? If this is true, how can I modify it ? > > That's a bug. Thanks for pointing out. This is fixed in: > You are welcome. > > Name: Pier-EditorEnh-lr.48 > Author: lr > Time: 5 May 2009, 9:05:28 am > UUID: 49418291-6470-4a75-a9f0-dd9cb1cc58dd > Ancestors: Pier-EditorEnh-lr.47 Now it works perfect. However I needed to update some other package. I don't know which one, because I was having a walkback and because of that I updated other packages (pier and magritte). And then It worked perfect. Thanks for the fix! Mariano > > > - don't display links without view permission > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marianopeck at gmail.com Wed May 6 01:20:22 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Tue, 5 May 2009 20:20:22 -0300 Subject: I don't understand what parameters are in Pier In-Reply-To: <67628d690905050007v5b00e120m5fcece738eec75f1@mail.gmail.com> References: <67628d690905050007v5b00e120m5fcece738eec75f1@mail.gmail.com> Message-ID: On Tue, May 5, 2009 at 4:07 AM, Lukas Renggli wrote: > > In a page I want to put a link to its parent. I am aware of > +value:parent+ > > but this only prints the name of the parent. I want a link. In Pier > > documentation > > (http://www.piercms.com/doc/syntax?_s=Sm29MDRQBjStQgra&_k=KGUMf85-&_n&18) > I > > read "Furthermore these expressions become a link if you add the > parameter > > link.". So, the question is, what is a parameter in Pier ? how can I do > it ? > > +value:parent|link+ > I feel like a stupid, but I cannot put an alias. I want a link to the parent but to use a alias instead of the name of the parent. Suppose the name of the parent is "Lists of Blogs" and I want an alias that says "Return to the lists of blogs". How can I do this? I tried several ways, but no one works. It always shows the name of the parent. I tried, for example: +Return to the lists of blogs>value:parent|link+ Thanks! Mariano > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marianopeck at gmail.com Wed May 6 01:26:34 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Tue, 5 May 2009 20:26:34 -0300 Subject: Link to a particular title of a page In-Reply-To: <67628d690905050012m3ccc43bas18d2be12200ef3d2@mail.gmail.com> References: <67628d690905031245h5af3a8c6t8cc433ee3a1ff22b@mail.gmail.com> <67628d690905050012m3ccc43bas18d2be12200ef3d2@mail.gmail.com> Message-ID: On Tue, May 5, 2009 at 4:12 AM, Lukas Renggli wrote: > > That way, it didn't work for me. Is this a bug ? > > I don't know. As far as I remember, SWiki used that name verbatim in > the resulting HTML back in 2002. I fixed that issue in > Pier-Seaside-lr.397. > > Name: Pier-Seaside-lr.397 > Author: lr > Time: 5 May 2009, 9:11:42 am > UUID: c5eaafef-13a5-4047-93ae-f82e2cd957a2 > Ancestors: Pier-Seaside-lr.396 > > - filter strange characters from anchors, so that it creates valid xhtml > It's fixed!!! Again, thanks for the fast bug fix :) It's a pleasure. Greetings, Mariano > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marianopeck at gmail.com Wed May 6 01:29:09 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Tue, 5 May 2009 20:29:09 -0300 Subject: Question about renaming a Kernel In-Reply-To: <67628d690905050014v586658bm8bf599b18f4e99f7@mail.gmail.com> References: <67628d690905050014v586658bm8bf599b18f4e99f7@mail.gmail.com> Message-ID: On Tue, May 5, 2009 at 4:14 AM, Lukas Renggli wrote: > > But, the application is still here: http://localhost:8888/seaside/pier/ > > > > shouldn't this be under http://localhost:8888/seaside/DestinoMochila/ or > > similar ? > > That's the Seaside path you installed Pier in. You can change it to > something else if you go to /seaside/config. > Done. I did a copy of pier I call it destinoMochila and then I remove pier. Thanks! Mariano > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marianopeck at gmail.com Wed May 6 01:46:34 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Tue, 5 May 2009 20:46:34 -0300 Subject: Cancel button doesn't work when creating a new post Message-ID: When adding a new post when you are in the screen where you add all the post information (author, contents, etc...) and you press cancel button, this acts like an accept. The post is created not cancelled. Greetings, Mariano -------------- next part -------------- An HTML attachment was scrubbed... URL: From marianopeck at gmail.com Wed May 6 01:52:34 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Tue, 5 May 2009 20:52:34 -0300 Subject: Preview when creating a post ? Message-ID: Hi! Is it implemented a way to see a preview of what you are editing or creating (for example, creating a post) ? Any tip how to do it ? Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: From marianopeck at gmail.com Wed May 6 05:55:58 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Wed, 6 May 2009 00:55:58 -0300 Subject: multiple word tag for a post Message-ID: Hi! Suppose I have a tag that has more than a word, for example: garbage collector. If I put this in tags, this is interpreted like 2 different tags. Is there a way of scaping this so that it can be considered as one tag ? what about using , or other thing instead of a blank ? Thanks in advance, Mariano -------------- next part -------------- An HTML attachment was scrubbed... URL: From renggli at gmail.com Wed May 6 08:13:38 2009 From: renggli at gmail.com (Lukas Renggli) Date: Wed, 6 May 2009 08:13:38 +0200 Subject: I don't understand what parameters are in Pier In-Reply-To: References: <67628d690905050007v5b00e120m5fcece738eec75f1@mail.gmail.com> Message-ID: <67628d690905052313l66932e45v5156427c01c0a966@mail.gmail.com> > I tried several ways, but no one works. It always shows the name of the > parent. > > I tried, for example: > > +Return to the lists of blogs>value:parent|link+ Hmm, there are bugs with +value:parent+, I fixed them in the latest commit. Relating your question: What you are trying to do is currently not possible. The alias is only displayed in case there is no parent. I realized already a while ago that this is not really intuitive, furthermore it does not allow users to arbitrarily format the generated string. I am thinking of adding something along these lines: +Return to {title}>value:parent|link+ In case this was already at the root, a replacement could be displayed like this: +Return to {title}>value:parent|link|otherwise=You are already at the root+ I don't like the {}-thing though. Maybe there are better ideas there? Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at gmail.com Wed May 6 08:26:25 2009 From: renggli at gmail.com (Lukas Renggli) Date: Wed, 6 May 2009 08:26:25 +0200 Subject: Pier components internationalization In-Reply-To: References: Message-ID: <67628d690905052326m51ba709fx3480631966bf4d8b@mail.gmail.com> > I need to internationalize Pier components. I am doing a site with Pier for > Spanish people. The final user has access to Pier components. For example, > it can leave comments or even post. But pier components have the html > outputs in English. For example when you are going to create a post you have > "author, publish, tags, ..." and I want "autor, publicacion, etiquetas...". Sounds like a really interesting project. Keep us posted on the progress. > Ok, after said that, I want to add int18 to my website but I don't want to > touch Pier code. So, the solution I thought is this: That would be a goal for the next big release then. I created an issue: . We were sort of thinking of providing an internationalization package as part of Seaside 2.9, because this is something quite a lot of people want. Especially in the context of web applications. However we didn't do anything yet. > override String #printOn: or Object #printString???? (which one could be > better?)? to something like this: > (suppose I override printOn:) Uhh, that sounds scary, but I guess you are discussing this already on the Pharo list ;-) > Could this be a good idea? Any other solution ? That's certainly an approach. For Magritte strings (in fact Magritte has already been used in fully localized applications) it would be easy just to change the descriptions. If there is the description: PRStructure>>descriptionTitle (in package Pier-Model) ^ MAStringDescription new accessor: #title; label: 'Title'; yourself You can add the method: PRStructure>>descriptionTitleSpanish: aDescription (in package Pier-Localized-Spanish) ^ aDescription label: 't?tulo' Instead of using a hardcoded string you could also use your own "smart string implementation" that knows how to translate to different languages. At least this is what I've done in various commercial projects. Now that doesn't solve the problems of the Strings in Pier itself. Maybe it is the easiest if you just make a package that overrides the respective methods that you always load after updating to Pier? Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at gmail.com Wed May 6 08:31:07 2009 From: renggli at gmail.com (Lukas Renggli) Date: Wed, 6 May 2009 08:31:07 +0200 Subject: multiple word tag for a post In-Reply-To: References: Message-ID: <67628d690905052331n65dac822ld399dfca4b397e07@mail.gmail.com> > Hi!?? Suppose I have a tag that has more than a word, for example: garbage > collector. If I put this in tags, this is interpreted like 2 different tags. > Is there a way of scaping this so that it can be considered as one tag ? > what about using , or other thing instead of a blank ? The separators of the tags are defined in MATokenDescription. The default tokens recognized are ' ,;' , String crlf , String tab The first one of this list is the default one used to separate the tokens when printing. To allow space separated tokens in Pier simply add the following method as a class extension to PRStructure: descriptionTagsChangeSeparator: aDescription ^ aDescription separators: ',;' , String crlf , String tab " no space there, default is $, " Lukas > > Thanks in advance, > > Mariano > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli http://www.lukas-renggli.ch From renggli at gmail.com Wed May 6 08:42:00 2009 From: renggli at gmail.com (Lukas Renggli) Date: Wed, 6 May 2009 08:42:00 +0200 Subject: Login / Logout / loggedinuser In-Reply-To: References: Message-ID: <67628d690905052342i51d2787cw6d51fb6677ab8cbe@mail.gmail.com> I missed that one ;-) > Can I do this just with Pier as it is now or I need to extend, modify or > create something ? I would create a Seaside component (subclass of PRWidget). That's probably the simplest solution. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From marianopeck at gmail.com Wed May 6 15:03:48 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Wed, 6 May 2009 12:03:48 -0100 Subject: I don't understand what parameters are in Pier In-Reply-To: <67628d690905052313l66932e45v5156427c01c0a966@mail.gmail.com> References: <67628d690905050007v5b00e120m5fcece738eec75f1@mail.gmail.com> <67628d690905052313l66932e45v5156427c01c0a966@mail.gmail.com> Message-ID: On Wed, May 6, 2009 at 5:13 AM, Lukas Renggli wrote: > > I tried several ways, but no one works. It always shows the name of the > > parent. > > > > I tried, for example: > > > > +Return to the lists of blogs>value:parent|link+ > > Hmm, there are bugs with +value:parent+, I fixed them in the latest commit. > Ok, I will see them then. > > Relating your question: > > What you are trying to do is currently not possible. The alias is only > displayed in case there is no parent. I realized already a while ago > that this is not really intuitive, furthermore it does not allow users > to arbitrarily format the generated string. I am thinking of adding > something along these lines: > > +Return to {title}>value:parent|link+ > > In case this was already at the root, a replacement could be displayed > like this: > > +Return to {title}>value:parent|link|otherwise=You are already at the > root+ > > I don't like the {}-thing though. Maybe there are better ideas there? > I think we are mixing 2 features: 1) Being able to have a link to the parent and put the alias you want. For example: +Return to the lists of blogs>value:parent|link+ In this case I put an alias "Return to the lists of blogs" no matter which the parent name is. 2) Being able to put the parent name as part of the alias. Example: +Return to {title}>value:parent|link|otherwise=You are already at the root+ My question was about 1) but having 1) and 2) would be very nice indeed. I haven't any idea but I think {} is fine for me. We cannot put something very common to put in a link because we will then have to scape it. What I don't understand is if "title" not the {} is hardcoded (always have to be title) or I can put whatever I want. Thanks! Mariano > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marianopeck at gmail.com Wed May 6 15:16:42 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Wed, 6 May 2009 12:16:42 -0100 Subject: multiple word tag for a post In-Reply-To: <67628d690905052331n65dac822ld399dfca4b397e07@mail.gmail.com> References: <67628d690905052331n65dac822ld399dfca4b397e07@mail.gmail.com> Message-ID: On Wed, May 6, 2009 at 5:31 AM, Lukas Renggli wrote: > > Hi! Suppose I have a tag that has more than a word, for example: > garbage > > collector. If I put this in tags, this is interpreted like 2 different > tags. > > Is there a way of scaping this so that it can be considered as one tag ? > > what about using , or other thing instead of a blank ? > > The separators of the tags are defined in MATokenDescription. The > default tokens recognized are > > ' ,;' , String crlf , String tab > > The first one of this list is the default one used to separate the > tokens when printing. > > To allow space separated tokens in Pier simply add the following > method as a class extension to PRStructure: > > descriptionTagsChangeSeparator: aDescription > ^ aDescription separators: ',;' , String crlf , String tab " no > space there, default is $, " > Perfect!!! I works nice now. Thank you so much. Mariano > > Lukas > > > > > Thanks in advance, > > > > Mariano > > > > _______________________________________________ > > Magritte, Pier and Related Tools ... > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marianopeck at gmail.com Wed May 6 15:17:35 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Wed, 6 May 2009 12:17:35 -0100 Subject: Login / Logout / loggedinuser In-Reply-To: <67628d690905052342i51d2787cw6d51fb6677ab8cbe@mail.gmail.com> References: <67628d690905052342i51d2787cw6d51fb6677ab8cbe@mail.gmail.com> Message-ID: On Wed, May 6, 2009 at 5:42 AM, Lukas Renggli wrote: > I missed that one ;-) > Yes, it's probable. I am sending lots of mails per day hahaha. > > > Can I do this just with Pier as it is now or I need to extend, modify or > > create something ? > > I would create a Seaside component (subclass of PRWidget). That's > probably the simplest solution. > Ok. I will do it then. Thanks! Mariano > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From keith_hodges at yahoo.co.uk Wed May 6 16:12:13 2009 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Wed, 06 May 2009 15:12:13 +0100 Subject: Login / Logout / loggedinuser In-Reply-To: References: <67628d690905052342i51d2787cw6d51fb6677ab8cbe@mail.gmail.com> Message-ID: <4A019ABD.1000706@yahoo.co.uk> Mariano Martinez Peck wrote: > > > On Wed, May 6, 2009 at 5:42 AM, Lukas Renggli > wrote: > > I missed that one ;-) > > > Yes, it's probable. I am sending lots of mails per day hahaha. > > > > > Can I do this just with Pier as it is now or I need to extend, > modify or > > create something ? > > I would create a Seaside component (subclass of PRWidget). That's > probably the simplest solution. > > > Ok. I will do it then. > > Thanks! > > Mariano > > Hi Mariano, In my environment I am able to subclass the standard renderers, including the PRReferenceRenderer in my subclass I add the following, and it works much better than making a special component for every message that you want to give the user saying "please log in". Keith visitInternalLink: aLink ((link hasParameter: 'loggedout') and: [component context isLoggedIn ]) ifTrue: [ ^ self ]. ((link hasParameter: 'loggedin') and: [component context isLoggedIn not ]) ifTrue: [ ^ self ]. (aLink hasParameter: 'button') ifFalse: [ ^ super visitInternalLink: aLink ]. html form: [ html button attributes: (self attributesFor: aLink); class: 'internal'; title: aLink title; goto: (self contextForInternalLink: aLink); with: [ self visitLink: aLink ] ] From marianopeck at gmail.com Wed May 6 16:23:23 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Wed, 6 May 2009 13:23:23 -0100 Subject: Login / Logout / loggedinuser In-Reply-To: <4A019ABD.1000706@yahoo.co.uk> References: <67628d690905052342i51d2787cw6d51fb6677ab8cbe@mail.gmail.com> <4A019ABD.1000706@yahoo.co.uk> Message-ID: On Wed, May 6, 2009 at 1:12 PM, Keith Hodges wrote: > Mariano Martinez Peck wrote: > > > > > > On Wed, May 6, 2009 at 5:42 AM, Lukas Renggli > > wrote: > > > > I missed that one ;-) > > > > > > Yes, it's probable. I am sending lots of mails per day hahaha. > > > > > > > > > Can I do this just with Pier as it is now or I need to extend, > > modify or > > > create something ? > > > > I would create a Seaside component (subclass of PRWidget). That's > > probably the simplest solution. > > > > > > Ok. I will do it then. > > > > Thanks! > > > > Mariano > > > > > Hi Mariano, > > In my environment I am able to subclass the standard renderers, > including the PRReferenceRenderer > > in my subclass I add the following, and it works much better than making > a special component for every message that you want to give the user > saying "please log in". > > Keith > > visitInternalLink: aLink > > ((link hasParameter: 'loggedout') and: [component context isLoggedIn > ]) ifTrue: [ ^ self ]. > ((link hasParameter: 'loggedin') and: [component context isLoggedIn > not ]) ifTrue: [ ^ self ]. > > (aLink hasParameter: 'button') ifFalse: [ ^ super visitInternalLink: > aLink ]. > > html form: [ > html button > attributes: (self attributesFor: aLink); > class: 'internal'; > title: aLink title; > goto: (self contextForInternalLink: aLink); > with: [ self visitLink: aLink ] > ] > Keith: thanks for the help. I have Beach in mind and I was going to take ideas or just adapt it to run in pharo. At least for the thing I need right now. Now I know where to start from. Thanks again. Mariano > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marianopeck at gmail.com Wed May 6 17:14:28 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Wed, 6 May 2009 14:14:28 -0100 Subject: Pier components internationalization In-Reply-To: <67628d690905052326m51ba709fx3480631966bf4d8b@mail.gmail.com> References: <67628d690905052326m51ba709fx3480631966bf4d8b@mail.gmail.com> Message-ID: On Wed, May 6, 2009 at 5:26 AM, Lukas Renggli wrote: > > I need to internationalize Pier components. I am doing a site with Pier > for > > Spanish people. The final user has access to Pier components. For > example, > > it can leave comments or even post. But pier components have the html > > outputs in English. For example when you are going to create a post you > have > > "author, publish, tags, ..." and I want "autor, publicacion, > etiquetas...". > > Sounds like a really interesting project. Keep us posted on the progress. > Ok. I will do. When I have a beta I will let you know :) > > > Ok, after said that, I want to add int18 to my website but I don't want > to > > touch Pier code. So, the solution I thought is this: > > That would be a goal for the next big release then. I created an > issue: . Thanks. That's all I wanted. > > > We were sort of thinking of providing an internationalization package > as part of Seaside 2.9, because this is something quite a lot of > people want. Especially in the context of web applications. However we > didn't do anything yet. > Good to know :) > > > override String #printOn: or Object #printString (which one could be > > better?) to something like this: > > (suppose I override printOn:) > > Uhh, that sounds scary, but I guess you are discussing this already on > the Pharo list ;-) Yes. I know hahaha > > > > Could this be a good idea? Any other solution ? > > That's certainly an approach. > > For Magritte strings (in fact Magritte has already been used in fully > localized applications) it would be easy just to change the > descriptions. If there is the description: > > PRStructure>>descriptionTitle (in package Pier-Model) > ^ MAStringDescription new > accessor: #title; > label: 'Title'; > yourself > > You can add the method: > > PRStructure>>descriptionTitleSpanish: aDescription (in package > Pier-Localized-Spanish) > ^ aDescription label: 't?tulo' > I didn't understand this. I should do this for all (if not all, which ones ?) the descriptions? I mean, that was just an example, wasn't it ? > > Instead of using a hardcoded string you could also use your own "smart > string implementation" that knows how to translate to different > languages. At least this is what I've done in various commercial > projects. > You mean I can subclass String ? I didn't get it :( > > Now that doesn't solve the problems of the Strings in Pier itself. > Maybe it is the easiest if you just make a package that overrides the > respective methods that you always load after updating to Pier? > A friend of mine, Esteban Lorenzano, did this approach so he can give a hand with it. However, what I will do is to wait until last moment to put int18. Perhaps at that moment the issue is done :) And if not, I do one of these approaches. Thanks for all! Mariano > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marianopeck at gmail.com Wed May 6 17:15:32 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Wed, 6 May 2009 14:15:32 -0100 Subject: Pier components internationalization In-Reply-To: <67628d690905052326m51ba709fx3480631966bf4d8b@mail.gmail.com> References: <67628d690905052326m51ba709fx3480631966bf4d8b@mail.gmail.com> Message-ID: > > > > That would be a goal for the next big release then. I created an > issue: . > > can I add some comments here ? cheers, Mariano -------------- next part -------------- An HTML attachment was scrubbed... URL: From miguel.coba at gmail.com Wed May 6 17:30:24 2009 From: miguel.coba at gmail.com (=?ISO-8859-1?Q?Miguel_Enrique_Cob=E1_Mart=EDnez?=) Date: Wed, 06 May 2009 10:30:24 -0500 Subject: Pier components internationalization In-Reply-To: <67628d690905052326m51ba709fx3480631966bf4d8b@mail.gmail.com> References: <67628d690905052326m51ba709fx3480631966bf4d8b@mail.gmail.com> Message-ID: <4A01AD10.3050401@gmail.com> Lukas Renggli wrote: >> I need to internationalize Pier components. I am doing a site with Pier for >> Spanish people. The final user has access to Pier components. For example, >> it can leave comments or even post. But pier components have the html >> outputs in English. For example when you are going to create a post you have >> "author, publish, tags, ..." and I want "autor, publicacion, etiquetas...". This is how I do it: First I added a new class, suppose it is call MyLocale in the class side you add a method for each message you want to translate to other languages. For example: MyLocale class >> helloWorld ^ "Hello World!" Then, add a subclass for each language, overriding each message in the corresponding language. MyLocaleESMX class >> helloWorld ^ "Hola mundo!" Then in your application, be sure to include this in the session, so that each user has his own language: MySession >> locale ^ locale ifNil: [ locale := MyLocale ] MySession >> locale: anObject locale := anObject MySession >> l10n self isLoggedIn ifTrue: [ ^ self user preferences l10n ]. ^ self locale Then, each user has in the preferences the name of the class he wants for the locale, MyLocale or MyLocaleESMX. This way each user use the class he wants. Now, for use it, for example, in a login component: MyLogin >> renderMessageOn: html html label with: self session l10n helloWorld This will have your component always use the class associated with the user to output messages or, if the user is not logged in, to use a default language. If you need more details, let me know. Miguel Cob? > > Sounds like a really interesting project. Keep us posted on the progress. > >> Ok, after said that, I want to add int18 to my website but I don't want to >> touch Pier code. So, the solution I thought is this: > > That would be a goal for the next big release then. I created an > issue: . > > We were sort of thinking of providing an internationalization package > as part of Seaside 2.9, because this is something quite a lot of > people want. Especially in the context of web applications. However we > didn't do anything yet. > >> override String #printOn: or Object #printString (which one could be >> better?) to something like this: >> (suppose I override printOn:) > > Uhh, that sounds scary, but I guess you are discussing this already on > the Pharo list ;-) > >> Could this be a good idea? Any other solution ? > > That's certainly an approach. > > For Magritte strings (in fact Magritte has already been used in fully > localized applications) it would be easy just to change the > descriptions. If there is the description: > > PRStructure>>descriptionTitle (in package Pier-Model) > ^ MAStringDescription new > accessor: #title; > label: 'Title'; > yourself > > You can add the method: > > PRStructure>>descriptionTitleSpanish: aDescription (in package > Pier-Localized-Spanish) > ^ aDescription label: 't?tulo' > > Instead of using a hardcoded string you could also use your own "smart > string implementation" that knows how to translate to different > languages. At least this is what I've done in various commercial > projects. > > Now that doesn't solve the problems of the Strings in Pier itself. > Maybe it is the easiest if you just make a package that overrides the > respective methods that you always load after updating to Pier? > > Cheers, > Lukas > From marianopeck at gmail.com Wed May 6 17:42:55 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Wed, 6 May 2009 14:42:55 -0100 Subject: Pier components internationalization In-Reply-To: <4A01AD10.3050401@gmail.com> References: <67628d690905052326m51ba709fx3480631966bf4d8b@mail.gmail.com> <4A01AD10.3050401@gmail.com> Message-ID: 2009/5/6 Miguel Enrique Cob? Mart?nez > Lukas Renggli wrote: > >> I need to internationalize Pier components. I am doing a site with Pier >>> for >>> Spanish people. The final user has access to Pier components. For >>> example, >>> it can leave comments or even post. But pier components have the html >>> outputs in English. For example when you are going to create a post you >>> have >>> "author, publish, tags, ..." and I want "autor, publicacion, >>> etiquetas...". >>> >> > This is how I do it: > > First I added a new class, suppose it is call MyLocale > in the class side you add a method for each message you want to translate > to other languages. For example: > > MyLocale class >> helloWorld > ^ "Hello World!" > > Then, add a subclass for each language, overriding each message in the > corresponding language. > > MyLocaleESMX class >> helloWorld > ^ "Hola mundo!" > > Then in your application, be sure to include this in the session, so that > each user has his own language: > > MySession >> locale > ^ locale ifNil: [ locale := MyLocale ] > > MySession >> locale: anObject > locale := anObject > > MySession >> l10n > self isLoggedIn ifTrue: [ ^ self user preferences l10n ]. > ^ self locale > > Then, each user has in the preferences the name of the class he wants for > the locale, MyLocale or MyLocaleESMX. > This way each user use the class he wants. > Now, for use it, for example, in a login component: > > MyLogin >> renderMessageOn: html > html label with: self session l10n helloWorld > > This will have your component always use the class associated with the user > to output messages or, if the user is not logged in, to use a default > language. > First of all thanks for your time writing the email. Your solution can be easily applied for the components I make but it cannot for Pier components. I am right or I am not understanding something ? I mean, I don't want to touch Pier components because then I wont be able to update anymore. Or I will start doing merge all the time. Another thing is that something like this is in the core on Pier. Greetings, Mariano > > If you need more details, let me know. > > Miguel Cob? > > >> Sounds like a really interesting project. Keep us posted on the progress. >> >> Ok, after said that, I want to add int18 to my website but I don't want >>> to >>> touch Pier code. So, the solution I thought is this: >>> >> >> That would be a goal for the next big release then. I created an >> issue: . >> >> We were sort of thinking of providing an internationalization package >> as part of Seaside 2.9, because this is something quite a lot of >> people want. Especially in the context of web applications. However we >> didn't do anything yet. >> >> override String #printOn: or Object #printString (which one could be >>> better?) to something like this: >>> (suppose I override printOn:) >>> >> >> Uhh, that sounds scary, but I guess you are discussing this already on >> the Pharo list ;-) >> >> Could this be a good idea? Any other solution ? >>> >> >> That's certainly an approach. >> >> For Magritte strings (in fact Magritte has already been used in fully >> localized applications) it would be easy just to change the >> descriptions. If there is the description: >> >> PRStructure>>descriptionTitle (in package Pier-Model) >> ^ MAStringDescription new >> accessor: #title; >> label: 'Title'; >> yourself >> >> You can add the method: >> >> PRStructure>>descriptionTitleSpanish: aDescription (in package >> Pier-Localized-Spanish) >> ^ aDescription label: 't?tulo' >> >> Instead of using a hardcoded string you could also use your own "smart >> string implementation" that knows how to translate to different >> languages. At least this is what I've done in various commercial >> projects. >> >> Now that doesn't solve the problems of the Strings in Pier itself. >> Maybe it is the easiest if you just make a package that overrides the >> respective methods that you always load after updating to Pier? >> >> Cheers, >> Lukas >> >> > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From renggli at gmail.com Wed May 6 17:46:49 2009 From: renggli at gmail.com (Lukas Renggli) Date: Wed, 6 May 2009 17:46:49 +0200 Subject: Pier components internationalization In-Reply-To: References: <67628d690905052326m51ba709fx3480631966bf4d8b@mail.gmail.com> Message-ID: <67628d690905060846u653f74c7n937bfead73280a8e@mail.gmail.com> Yes. Please go ahead. On Wednesday, May 6, 2009, Mariano Martinez Peck wrote: > > > That would be a goal for the next big release then. I created an > issue: . > > > can I add some comments here ? > > cheers, > > Mariano > -- Lukas Renggli http://www.lukas-renggli.ch From marianopeck at gmail.com Wed May 6 19:29:49 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Wed, 6 May 2009 16:29:49 -0100 Subject: Pier components internationalization In-Reply-To: <67628d690905060846u653f74c7n937bfead73280a8e@mail.gmail.com> References: <67628d690905052326m51ba709fx3480631966bf4d8b@mail.gmail.com> <67628d690905060846u653f74c7n937bfead73280a8e@mail.gmail.com> Message-ID: done. On Wed, May 6, 2009 at 2:46 PM, Lukas Renggli wrote: > Yes. Please go ahead. > > On Wednesday, May 6, 2009, Mariano Martinez Peck > wrote: > > > > > > That would be a goal for the next big release then. I created an > > issue: . > > > > > > can I add some comments here ? > > > > cheers, > > > > Mariano > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ross at biostat.ucsf.edu Sat May 9 18:13:07 2009 From: ross at biostat.ucsf.edu (Ross Boylan) Date: Sat, 09 May 2009 09:13:07 -0700 Subject: documentation? Message-ID: <1241885587.15790.5.camel@corn.betterworld.us> I'm considering using Pier for a project, but am concerned that the documentation seems quite sparse. I almost certainly will want to extend it. I know there's documentation on Seaside; it's the Pier part that concerns me. Am I missing something? Ross From renggli at gmail.com Sat May 9 21:17:53 2009 From: renggli at gmail.com (Lukas Renggli) Date: Sat, 9 May 2009 21:17:53 +0200 Subject: documentation? In-Reply-To: <1241885587.15790.5.camel@corn.betterworld.us> References: <1241885587.15790.5.camel@corn.betterworld.us> Message-ID: <67628d690905091217o16a44637k17b68d9d00041024@mail.gmail.com> There is www.piercms.com with all documentation needed to get started. There is also my master thesis with more background information, if you need. Cheers, Lukas On Saturday, May 9, 2009, Ross Boylan wrote: > I'm considering using Pier for a project, but am concerned that the > documentation seems quite sparse. ?I almost certainly will want to > extend it. > > I know there's documentation on Seaside; it's the Pier part that > concerns me. > > Am I missing something? > > Ross > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli http://www.lukas-renggli.ch From ross at biostat.ucsf.edu Sat May 9 22:07:10 2009 From: ross at biostat.ucsf.edu (Ross Boylan) Date: Sat, 09 May 2009 13:07:10 -0700 Subject: documentation? In-Reply-To: <67628d690905091217o16a44637k17b68d9d00041024@mail.gmail.com> References: <1241885587.15790.5.camel@corn.betterworld.us> <67628d690905091217o16a44637k17b68d9d00041024@mail.gmail.com> Message-ID: <1241899630.15790.22.camel@corn.betterworld.us> On Sat, 2009-05-09 at 21:17 +0200, Lukas Renggli wrote: > There is www.piercms.com with all documentation needed to get started. > There is also my master thesis with more background information, if > you need. > > Cheers, > Lukas Do you mean http://scg.unibe.ch/archive/masters/Reng06a.pdf for the thesis? That looks helpful. I looked at the documentation on site before sending my query; it seems very minimal. There is neither a user nor a developer guide, just scattered tidbits. Ross > > On Saturday, May 9, 2009, Ross Boylan wrote: > > I'm considering using Pier for a project, but am concerned that the > > documentation seems quite sparse. I almost certainly will want to > > extend it. > > > > I know there's documentation on Seaside; it's the Pier part that > > concerns me. > > > > Am I missing something? > > > > Ross > > > > _______________________________________________ > > Magritte, Pier and Related Tools ... > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > From rdrvr.biz at gmail.com Sun May 10 02:07:51 2009 From: rdrvr.biz at gmail.com (David Farber) Date: Sat, 9 May 2009 18:07:51 -0600 Subject: Two Pier Forms Questions Message-ID: I have a registration form embedded in Pier page. +/mysite/MyForm+ 1) How do I keep a user from submitting the form twice? 2) I would like to show a confirmation page after the form is submitted, but I would like for that page to a Pier-editable page. How could I accomplish that? Thanks, David ---- 1 Squeak/Seaside/Pier site deployed From renggli at gmail.com Sun May 10 07:48:11 2009 From: renggli at gmail.com (Lukas Renggli) Date: Sun, 10 May 2009 07:48:11 +0200 Subject: Two Pier Forms Questions In-Reply-To: References: Message-ID: <67628d690905092248m194a5f63s15a9df09c8484319@mail.gmail.com> On Sun, May 10, 2009 at 2:07 AM, David Farber wrote: > I have a registration form embedded in Pier page. > ?+/mysite/MyForm+ A pier page? Not a component? How do you handle the submission? > 1) How do I keep a user from submitting the form twice? You display something else. > 2) I would like to show a confirmation page after the form is submitted, but > I would like for that page to a Pier-editable page. ?How could I accomplish > that? If you add a description of the type MADocumentDescription you can store one or more wiki documents with your component, that are then displayed instead. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From marianopeck at gmail.com Tue May 12 01:54:10 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Mon, 11 May 2009 20:54:10 -0300 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: <49FEE935.4020302@yahoo.co.uk> References: <49FA1845.8010201@yahoo.co.uk> <49FDE5A0.1080600@yahoo.co.uk> <49FEE935.4020302@yahoo.co.uk> Message-ID: On Mon, May 4, 2009 at 10:10 AM, Keith Hodges wrote: > Mariano Martinez Peck wrote: > > Keith: should this work on pharo? > > > > Installer install: 'Packages'. > > Installer ss project: 'Beach-Packages'. > > > > Because I am having a warning with Utilities #authorInitialsPerSe > > deprecated. Use instead initialsPerSe. > > > > However, I put "proceed" and my image freezes. > > > > Cheers, > > > > Mariano > I don't use pharo myself. Goodness knows why they break things as simple > as author initials. Please. Come back to the original thread. Is there another working way of loading Beach on Pharo ? A MC script or something like that ? I know you don't use Pharo but consider this as a way of expanding, testing and even improving Beach. Cheers, Mariano > > > Keith > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From keith_hodges at yahoo.co.uk Tue May 12 03:48:06 2009 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Tue, 12 May 2009 02:48:06 +0100 Subject: Pier-EmailSender and "Contact Us" In-Reply-To: References: <49FA1845.8010201@yahoo.co.uk> <49FDE5A0.1080600@yahoo.co.uk> <49FEE935.4020302@yahoo.co.uk> Message-ID: <4A08D556.1000805@yahoo.co.uk> Mariano Martinez Peck wrote: > > > On Mon, May 4, 2009 at 10:10 AM, Keith Hodges > > wrote: > > Mariano Martinez Peck wrote: > > Keith: should this work on pharo? > > > > Installer install: 'Packages'. > > Installer ss project: 'Beach-Packages'. > > > > Because I am having a warning with Utilities #authorInitialsPerSe > > deprecated. Use instead initialsPerSe. > > > > However, I put "proceed" and my image freezes. > > > > Cheers, > > > > Mariano > I don't use pharo myself. Goodness knows why they break things as > simple > as author initials. > > > Please. Come back to the original thread. Is there another working way > of loading Beach on Pharo ? A MC script or something like that ? > > I know you don't use Pharo but consider this as a way of expanding, > testing and even improving Beach. > > Cheers, > > Mariano > I think I mentioned Beach-Packages, although written as executable metadata has not been tested because I have not had to load these packages into an image as yet. So I suggested that you Browse the package, and use the metadata to work out what order to load things in. MC1.5 theoretically supports out of order loading so why not just load all the packages in the Beach repo. If that doesnt work then simply load them all twice. Keith From norbert at hartl.name Thu May 14 12:03:48 2009 From: norbert at hartl.name (Norbert Hartl) Date: Thu, 14 May 2009 12:03:48 +0200 Subject: Are pages with HTML markup possible? Message-ID: <1242295428.5284.38.camel@cineflux> Hi, I'm still trying to change my application that is pure seaside to pier. I need to keep the layout of the page that means I need some control over the markup created. On the other hand I want to be able to "document" components that means to be able to put some text before and/or after the component. So imagine a page that contains three components. I want to do some specific markup for the layout of these components. And at the same time I want to be able to press edit and write some help text above component No. 2. Regarding layout I would need to do HTML markup. Can a pier page be enriched by HTML markup? Or is this possible by tweaking the environment? As far as I understand it the contents component in an environment determines the place in the tree where the page is rendered into. Can you have more than one in an environment? thanks, Norbert From renggli at gmail.com Thu May 14 12:22:15 2009 From: renggli at gmail.com (Lukas Renggli) Date: Thu, 14 May 2009 12:22:15 +0200 Subject: Are pages with HTML markup possible? In-Reply-To: <1242295428.5284.38.camel@cineflux> References: <1242295428.5284.38.camel@cineflux> Message-ID: <67628d690905140322o78f7be57g3bf01a133eb4c39c@mail.gmail.com> > So imagine a page that contains three components. I want to > do some specific markup for the layout of these components. > And at the same time I want to be able to press edit and write > some help text above component No. 2. Yes, you can do that. Add a page a page that adds markup before and after your components. The simplest thing is to stick with the Pier markup: | +component1+ | +component2+ | > Regarding layout I would need to do HTML markup. Can a pier > page be enriched by HTML markup? Of course you can also use plain HTML, if you want. Something along:
+component1+
+component2+
> Or is this possible by > tweaking the environment? As far as I understand it the > contents component in an environment determines the place > in the tree where the page is rendered into. Yes, the environment defines the placing of multiple pages. It can also embed pages, or components. Exactly the same way as shown above. The only difference of the environment to a normal page, is that it doesn't surround the wiki text with

tags when being rendered. This makes the HTML more clean if you define layout. Have a look at the environment of the default Pier installation. > Can you have > more than one in an environment? Yes, every page can have its own environment. Subpages automatically inherit the environment of the parent page. Go to 'Settings' to change the environment. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From clover at pacbell.net Fri May 15 19:27:54 2009 From: clover at pacbell.net (Alex Roston) Date: Fri, 15 May 2009 10:27:54 -0700 Subject: The "Input is Invalid" Error Message-ID: <4A0DA61A.3080505@pacbell.net> Hello to all, I'm involved in a project which uses the Pier wiki. We hope that this project will have mass appeal and involve many users. Unfortunately, we've seen a problem with the edit box. If one pastes something from a non-UTF-8 compatible world processor, it is rejected with an error message reading, "Input is Invalid." Unfortunately, this is not a very helpful error message, and it will make using the Pier wiki impossible for those of us who aren't at least mid-level geeks. Would it be possible to make some changes which would allow a more user-friendly error message? I see two possible ways to handle this. 1.) Replace the current message with a message that reads, "Your input cannot be read because it is not UTF-8 compatible. Please set your word-processor to produce UTF-8 compatible text and try pasting your input again." Such an error message could even connect to Pier's help system which could explain how to set various word-processors for UTF-8. I'm not a Squeak programmer, but I'd be happy to write help text for the word processing programs I own. 2.) The second is to devise a more forgiving edit window. Instead of giving an error message and rejecting the input, it could accept the input and replace characters it can't read with a question mark, or one of those square boxes, then output an error message, something like: "There was a problem reading your input because your word processor is not set to UTF-8. Characters which could not be read have been replaced with a "?". Please click here to continue." I think this is the better of the two alternatives, though obviously it involves more programming time. A more sophisticated version of the second solution could present users with a small, pop-up edit box containing the text that is causing problems. The users could then use their keyboards to make the appropriate changes. As things stand now, the edit box is very "user-unfriendly." I don't, of course, insist that my solutions be used - it's entirely possible that a better way exists than I imagine above - but the present situation will make things very difficult for users who don't have serious computing skills. Thanks in advance for any help you can offer. Alex From renggli at gmail.com Fri May 15 19:51:41 2009 From: renggli at gmail.com (Lukas Renggli) Date: Fri, 15 May 2009 19:51:41 +0200 Subject: The "Input is Invalid" Error In-Reply-To: <4A0DA61A.3080505@pacbell.net> References: <4A0DA61A.3080505@pacbell.net> Message-ID: <67628d690905151051t5a6ad967vdec937c850849fa@mail.gmail.com> > I'm involved in a project which uses the Pier wiki. If you talk about encodings you should mention the platform you are using, the version of the platform, the server adaptor, the version of Seaside, the version of Magritte and Pier. Encoding problems show up from time to time, but usually they can be solved by fixing the configuration you use. > If one pastes something from a non-UTF-8 > compatible world processor, it is rejected with an error message reading, > "Input is Invalid." What kind of error message? A Magritte error within the page, a Seaside error within a separate page, or even a debugger within the image? Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From clover at pacbell.net Fri May 15 20:03:48 2009 From: clover at pacbell.net (Alex Roston) Date: Fri, 15 May 2009 11:03:48 -0700 Subject: The "Input is Invalid" Error In-Reply-To: <67628d690905151051t5a6ad967vdec937c850849fa@mail.gmail.com> References: <4A0DA61A.3080505@pacbell.net> <67628d690905151051t5a6ad967vdec937c850849fa@mail.gmail.com> Message-ID: <4A0DAE84.6040605@pacbell.net> Lukas Renggli wrote: >> I'm involved in a project which uses the Pier wiki. >> > > If you talk about encodings you should mention the platform you are > using, the version of the platform, the server adaptor, the version of > Seaside, the version of Magritte and Pier. > > Encoding problems show up from time to time, but usually they can be > solved by fixing the configuration you use. > Thanks for the quick reply. Unfortunately, I'm not the admin for this project, so I don't know the details. However, I'll let the systems administrator know I posted, and hopefully he can give you these detais. > >> If one pastes something from a non-UTF-8 >> compatible world processor, it is rejected with an error message reading, >> "Input is Invalid." >> > > What kind of error message? A Magritte error within the page, a > Seaside error within a separate page, or even a debugger within the > image? > I'm not seeing a separate page, or anything that looks like a debugger. The edit box turns pink, and I see the words, "Input is Invalid" above the buttons on the edit box. As far as I'm concerned the important issue is getting users an error message which enlightens and informs so they can a minimal break in their work flow and wish to continue using the product. Thanks, Alex > Cheers, > Lukas > > From clover at pacbell.net Fri May 15 23:00:48 2009 From: clover at pacbell.net (Alex Roston) Date: Fri, 15 May 2009 14:00:48 -0700 Subject: The "Input is Invalid" Error In-Reply-To: <67628d690905151051t5a6ad967vdec937c850849fa@mail.gmail.com> References: <4A0DA61A.3080505@pacbell.net> <67628d690905151051t5a6ad967vdec937c850849fa@mail.gmail.com> Message-ID: <4A0DD800.3030006@pacbell.net> According to our sysadmin, "we're using the Wakom server adapter, plus the most recent version of Magritte, Seaside, and Pier from Lukas, which we updated may 14th." The exact error message we're seeing read, "Contents: Invalid input given." I have included a screen shot, which I hope will not be rejected by the mailing list program. Thanks, Alex Lukas Renggli wrote: >> I'm involved in a project which uses the Pier wiki. >> > > If you talk about encodings you should mention the platform you are > using, the version of the platform, the server adaptor, the version of > Seaside, the version of Magritte and Pier. > > Encoding problems show up from time to time, but usually they can be > solved by fixing the configuration you use. > > >> If one pastes something from a non-UTF-8 >> compatible world processor, it is rejected with an error message reading, >> "Input is Invalid." >> > > What kind of error message? A Magritte error within the page, a > Seaside error within a separate page, or even a debugger within the > image? > > Cheers, > Lukas > > -------------- next part -------------- A non-text attachment was scrubbed... Name: Error_Message.png Type: image/png Size: 49216 bytes Desc: not available URL: From ducasse at iam.unibe.ch Sat May 16 08:45:46 2009 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Sat, 16 May 2009 08:45:46 +0200 Subject: The "Input is Invalid" Error In-Reply-To: <4A0DD800.3030006@pacbell.net> References: <4A0DA61A.3080505@pacbell.net> <67628d690905151051t5a6ad967vdec937c850849fa@mail.gmail.com> <4A0DD800.3030006@pacbell.net> Message-ID: <66544385-D042-44AC-B80B-8114A1EF99F5@iam.unibe.ch> But on which version? Because this is more tricky than that :) On May 15, 2009, at 11:00 PM, Alex Roston wrote: > According to our sysadmin, "we're using the Wakom server adapter, > plus the most recent version of Magritte, Seaside, and Pier from > Lukas, which we updated may 14th." > > The exact error message we're seeing read, "Contents: Invalid input > given." I have included a screen shot, which I hope will not be > rejected by the mailing list program. > > Thanks, > > Alex > > > Lukas Renggli wrote: >>> I'm involved in a project which uses the Pier wiki. >>> >> >> If you talk about encodings you should mention the platform you are >> using, the version of the platform, the server adaptor, the version >> of >> Seaside, the version of Magritte and Pier. >> >> Encoding problems show up from time to time, but usually they can be >> solved by fixing the configuration you use. >> >> >>> If one pastes something from a non-UTF-8 >>> compatible world processor, it is rejected with an error message >>> reading, >>> "Input is Invalid." >>> >> >> What kind of error message? A Magritte error within the page, a >> Seaside error within a separate page, or even a debugger within the >> image? >> >> Cheers, >> Lukas >> >> > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From girba at iam.unibe.ch Sat May 16 09:35:28 2009 From: girba at iam.unibe.ch (Tudor Girba) Date: Sat, 16 May 2009 09:35:28 +0200 Subject: The "Input is Invalid" Error In-Reply-To: <66544385-D042-44AC-B80B-8114A1EF99F5@iam.unibe.ch> References: <4A0DA61A.3080505@pacbell.net> <67628d690905151051t5a6ad967vdec937c850849fa@mail.gmail.com> <4A0DD800.3030006@pacbell.net> <66544385-D042-44AC-B80B-8114A1EF99F5@iam.unibe.ch> Message-ID: <3F30E1B9-D03A-4D7C-9C8D-964AEB6676BD@iam.unibe.ch> Hi, The message is due to the Magritte validation checks of the form. Cheers, Doru On 16 May 2009, at 08:45, st?phane ducasse wrote: > But on which version? > Because this is more tricky than that :) > > On May 15, 2009, at 11:00 PM, Alex Roston wrote: > >> According to our sysadmin, "we're using the Wakom server adapter, >> plus the most recent version of Magritte, Seaside, and Pier from >> Lukas, which we updated may 14th." >> >> The exact error message we're seeing read, "Contents: Invalid input >> given." I have included a screen shot, which I hope will not be >> rejected by the mailing list program. >> >> Thanks, >> >> Alex >> >> >> Lukas Renggli wrote: >>>> I'm involved in a project which uses the Pier wiki. >>>> >>> >>> If you talk about encodings you should mention the platform you are >>> using, the version of the platform, the server adaptor, the >>> version of >>> Seaside, the version of Magritte and Pier. >>> >>> Encoding problems show up from time to time, but usually they can be >>> solved by fixing the configuration you use. >>> >>> >>>> If one pastes something from a non-UTF-8 >>>> compatible world processor, it is rejected with an error message >>>> reading, >>>> "Input is Invalid." >>>> >>> >>> What kind of error message? A Magritte error within the page, a >>> Seaside error within a separate page, or even a debugger within the >>> image? >>> >>> Cheers, >>> Lukas >>> >>> >> >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut." From renggli at gmail.com Sat May 16 09:44:01 2009 From: renggli at gmail.com (Lukas Renggli) Date: Sat, 16 May 2009 09:44:01 +0200 Subject: The "Input is Invalid" Error In-Reply-To: <4A0DD800.3030006@pacbell.net> References: <4A0DA61A.3080505@pacbell.net> <67628d690905151051t5a6ad967vdec937c850849fa@mail.gmail.com> <4A0DD800.3030006@pacbell.net> Message-ID: <67628d690905160044n49292f0cyd50cd1565da8da13@mail.gmail.com> On Fri, May 15, 2009 at 11:00 PM, Alex Roston wrote: > According to our sysadmin, "we're using the Wakom server adapter, plus the > most recent version of Magritte, Seaside, and Pier from Lukas, which we > updated may 14th." Ok, I guess you are on Squeak/Pharo then. > The exact error message we're seeing read, "Contents: Invalid input given." > I have included a screen shot, which I hope will not be rejected by the > mailing list program. Ok, that doesn't look too bad. This is a validation check of Magritte. You can easily change the error message by adding a method like this: PRCase class>>descriptionDocumentYourPackage: aDescription ^ aDescription kindErrorMessage: 'There was a problem reading your input because your word processor is not set to UTF-8.' To be able to investigate the real cause of the problem I need some more information. Could you send step by step introductions on how to reproduce the problem. Maybe together with a Word document (I assume this is the offender?) that I can copy from? Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From clover at pacbell.net Sat May 16 17:36:33 2009 From: clover at pacbell.net (Alex Roston) Date: Sat, 16 May 2009 08:36:33 -0700 Subject: The "Input is Invalid" Error In-Reply-To: <3F30E1B9-D03A-4D7C-9C8D-964AEB6676BD@iam.unibe.ch> References: <4A0DA61A.3080505@pacbell.net> <67628d690905151051t5a6ad967vdec937c850849fa@mail.gmail.com> <4A0DD800.3030006@pacbell.net> <66544385-D042-44AC-B80B-8114A1EF99F5@iam.unibe.ch> <3F30E1B9-D03A-4D7C-9C8D-964AEB6676BD@iam.unibe.ch> Message-ID: <4A0EDD81.7060400@pacbell.net> Thank you Tudor. Does that mean that Magritte should be changed, or that Pier should be changed? Is Pier simply passing on the error message from Magritte? Alex Tudor Girba wrote: > Hi, > > The message is due to the Magritte validation checks of the form. > > Cheers, > Doru > > On 16 May 2009, at 08:45, st?phane ducasse wrote: > >> But on which version? >> Because this is more tricky than that :) >> >> On May 15, 2009, at 11:00 PM, Alex Roston wrote: >> >>> According to our sysadmin, "we're using the Wakom server adapter, >>> plus the most recent version of Magritte, Seaside, and Pier from >>> Lukas, which we updated may 14th." >>> >>> The exact error message we're seeing read, "Contents: Invalid input >>> given." I have included a screen shot, which I hope will not be >>> rejected by the mailing list program. >>> >>> Thanks, >>> >>> Alex >>> >>> >>> Lukas Renggli wrote: >>>>> I'm involved in a project which uses the Pier wiki. >>>>> >>>> >>>> If you talk about encodings you should mention the platform you are >>>> using, the version of the platform, the server adaptor, the version of >>>> Seaside, the version of Magritte and Pier. >>>> >>>> Encoding problems show up from time to time, but usually they can be >>>> solved by fixing the configuration you use. >>>> >>>> >>>>> If one pastes something from a non-UTF-8 >>>>> compatible world processor, it is rejected with an error message >>>>> reading, >>>>> "Input is Invalid." >>>>> >>>> >>>> What kind of error message? A Magritte error within the page, a >>>> Seaside error within a separate page, or even a debugger within the >>>> image? >>>> >>>> Cheers, >>>> Lukas >>>> >>>> >>> >>> _______________________________________________ >>> Magritte, Pier and Related Tools ... >>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > -- > www.tudorgirba.com > > "If you interrupt the barber while he is cutting your hair, you will > end up with a messy haircut." > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > From clover at pacbell.net Sat May 16 18:12:11 2009 From: clover at pacbell.net (Alex Roston) Date: Sat, 16 May 2009 09:12:11 -0700 Subject: The "Input is Invalid" Error In-Reply-To: <67628d690905160044n49292f0cyd50cd1565da8da13@mail.gmail.com> References: <4A0DA61A.3080505@pacbell.net> <67628d690905151051t5a6ad967vdec937c850849fa@mail.gmail.com> <4A0DD800.3030006@pacbell.net> <67628d690905160044n49292f0cyd50cd1565da8da13@mail.gmail.com> Message-ID: <4A0EE5DB.5020707@pacbell.net> Hi Lukas My samples and response to your post are in the moderation queue - apparently they're too big. Sorry about that. I will send them directly to your email. Thanks, Alex Lukas Renggli wrote: > On Fri, May 15, 2009 at 11:00 PM, Alex Roston wrote: > >> According to our sysadmin, "we're using the Wakom server adapter, plus the >> most recent version of Magritte, Seaside, and Pier from Lukas, which we >> updated may 14th." >> > > Ok, I guess you are on Squeak/Pharo then. > > >> The exact error message we're seeing read, "Contents: Invalid input given." >> I have included a screen shot, which I hope will not be rejected by the >> mailing list program. >> > > Ok, that doesn't look too bad. This is a validation check of Magritte. > You can easily change the error message by adding a method like this: > > PRCase class>>descriptionDocumentYourPackage: aDescription > ^ aDescription kindErrorMessage: 'There was a problem reading your > input because your word processor is not set to UTF-8.' > > To be able to investigate the real cause of the problem I need some > more information. Could you send step by step introductions on how to > reproduce the problem. Maybe together with a Word document (I assume > this is the offender?) that I can copy from? > > Cheers, > Lukas > > From clover at pacbell.net Sat May 16 18:14:33 2009 From: clover at pacbell.net (Alex Roston) Date: Sat, 16 May 2009 09:14:33 -0700 Subject: The "Input is Invalid" Error In-Reply-To: <67628d690905160044n49292f0cyd50cd1565da8da13@mail.gmail.com> References: <4A0DA61A.3080505@pacbell.net> <67628d690905151051t5a6ad967vdec937c850849fa@mail.gmail.com> <4A0DD800.3030006@pacbell.net> <67628d690905160044n49292f0cyd50cd1565da8da13@mail.gmail.com> Message-ID: <4A0EE669.7060304@pacbell.net> Hi Lukas, Thank you very much for your interest in this problem. I have sent two sample documents to your regular email address as they are too big for the mailing list. Both are .doc files generated by Open Office 2.4. I generated the error by simply copying and pasting the contents of the documents into Pier's edit box. (I'm using Firefox on Ubuntu Linux.) Sample_One does not work, while Sample_Two works just fine, and the only thing I did in Sample_Two was delete the long dash between the words "conclusion" and "whatever" and replace it with a period. So Magritte is not generating errors based on the encoding of the whole message, it's responding to specific characters (which I assume it can't read.) Thus my suggestion that the problem be solved by simply replacing those characters with a question mark or a box, plus perhaps a message to the user. As to your suggestion that I add some code... I'd love to, but you could put everything I know about Squeak in a thimble and have room left over. (I plan to work on Squeak in my spare moments, but it will be many months before I'm ready to contribute to a sophisticated project.) But I'll happily submit additions to the documentation as appropriate, and supply you with a continuing stream of bug reports as our development goes forward. Thanks, Alex Lukas Renggli wrote: > On Fri, May 15, 2009 at 11:00 PM, Alex Roston wrote: > >> According to our sysadmin, "we're using the Wakom server adapter, plus the >> most recent version of Magritte, Seaside, and Pier from Lukas, which we >> updated may 14th." >> > > Ok, I guess you are on Squeak/Pharo then. > > >> The exact error message we're seeing read, "Contents: Invalid input given." >> I have included a screen shot, which I hope will not be rejected by the >> mailing list program. >> > > Ok, that doesn't look too bad. This is a validation check of Magritte. > You can easily change the error message by adding a method like this: > > PRCase class>>descriptionDocumentYourPackage: aDescription > ^ aDescription kindErrorMessage: 'There was a problem reading your > input because your word processor is not set to UTF-8.' > > To be able to investigate the real cause of the problem I need some > more information. Could you send step by step introductions on how to > reproduce the problem. Maybe together with a Word document (I assume > this is the offender?) that I can copy from? > > Cheers, > Lukas > > From girba at iam.unibe.ch Sat May 16 18:45:58 2009 From: girba at iam.unibe.ch (Tudor Girba) Date: Sat, 16 May 2009 18:45:58 +0200 Subject: The "Input is Invalid" Error In-Reply-To: <4A0EE669.7060304@pacbell.net> References: <4A0DA61A.3080505@pacbell.net> <67628d690905151051t5a6ad967vdec937c850849fa@mail.gmail.com> <4A0DD800.3030006@pacbell.net> <67628d690905160044n49292f0cyd50cd1565da8da13@mail.gmail.com> <4A0EE669.7060304@pacbell.net> Message-ID: <4816DF70-6220-48A2-A823-9A3269303F98@iam.unibe.ch> Hi Alex, Is your application publicly accessible? If yes, we would be interested in adding a link to it from: http://www.piercms.com/doc/examples Cheers, Doru On 16 May 2009, at 18:14, Alex Roston wrote: > Hi Lukas, > > Thank you very much for your interest in this problem. I have sent > two sample documents to your regular email address as they are too > big for the mailing list. Both are .doc files generated by Open > Office 2.4. > I generated the error by simply copying and pasting the contents of > the > documents into Pier's edit box. (I'm using Firefox on Ubuntu Linux.) > > Sample_One does not work, while Sample_Two works just fine, and the > only > thing I did in Sample_Two was delete the long dash between the words > "conclusion" and "whatever" and replace it with a period. So > Magritte is > not generating errors based on the encoding of the whole message, it's > responding to specific characters (which I assume it can't read.) > > Thus my suggestion that the problem be solved by simply replacing > those > characters with a question mark or a box, plus perhaps a message to > the > user. > > As to your suggestion that I add some code... I'd love to, but you > could > put everything I know about Squeak in a thimble and have room left > over. > (I plan to work on Squeak in my spare moments, but it will be many > months before I'm ready to contribute to a sophisticated project.) But > I'll happily submit additions to the documentation as appropriate, and > supply you with a continuing stream of bug reports as our development > goes forward. > > Thanks, > > Alex > > > > > Lukas Renggli wrote: >> On Fri, May 15, 2009 at 11:00 PM, Alex Roston >> wrote: >> >>> According to our sysadmin, "we're using the Wakom server adapter, >>> plus the >>> most recent version of Magritte, Seaside, and Pier from Lukas, >>> which we >>> updated may 14th." >>> >> >> Ok, I guess you are on Squeak/Pharo then. >> >> >>> The exact error message we're seeing read, "Contents: Invalid >>> input given." >>> I have included a screen shot, which I hope will not be rejected >>> by the >>> mailing list program. >>> >> >> Ok, that doesn't look too bad. This is a validation check of >> Magritte. >> You can easily change the error message by adding a method like this: >> >> PRCase class>>descriptionDocumentYourPackage: aDescription >> ^ aDescription kindErrorMessage: 'There was a problem reading your >> input because your word processor is not set to UTF-8.' >> >> To be able to investigate the real cause of the problem I need some >> more information. Could you send step by step introductions on how to >> reproduce the problem. Maybe together with a Word document (I assume >> this is the offender?) that I can copy from? >> >> Cheers, >> Lukas >> >> > > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com "Every now and then stop and ask yourself if the war you're fighting is the right one." From renggli at gmail.com Sat May 16 19:02:02 2009 From: renggli at gmail.com (Lukas Renggli) Date: Sat, 16 May 2009 19:02:02 +0200 Subject: The "Input is Invalid" Error In-Reply-To: <4A0EE669.7060304@pacbell.net> References: <4A0DA61A.3080505@pacbell.net> <67628d690905151051t5a6ad967vdec937c850849fa@mail.gmail.com> <4A0DD800.3030006@pacbell.net> <67628d690905160044n49292f0cyd50cd1565da8da13@mail.gmail.com> <4A0EE669.7060304@pacbell.net> Message-ID: <67628d690905161002pd8c946dr5fa1fe8b4f7061ca@mail.gmail.com> Thanks for sending the sample documents. I tried to reproduce with all of the following 36 possible combinations: - Pier 1.1.1 on Mac / latest Pier on Mac / Pier 1.1.1 on Linux - WAKom / WAKomEncoded - Safari 3 on Mac / IE 6 on Windows / FireFox 3 on Ubuntu Linux - Microsoft Word 2008 on Mac / Open Office 2.4 on Ubuntu Linux I cannot reproduce the problem. Maybe you can try to temporarily replace MAContainerComponent>>validate to see if there is something strange going on with exceptions ... MAContainerComponent>>validate self withContainersDo: [ :each | each doValidate ]. ^ errors isEmpty Cheers, Lukas On Sat, May 16, 2009 at 6:14 PM, Alex Roston wrote: > Hi Lukas, > > Thank you very much for your interest in this problem. I have sent two > sample documents to your regular email address as they are too big for the > mailing list. Both are .doc files generated by Open Office 2.4. > I generated the error by simply copying and pasting the contents of the > documents into Pier's edit box. (I'm using Firefox on Ubuntu Linux.) > > Sample_One does not work, while Sample_Two works just fine, and the only > thing I did in Sample_Two was delete the long dash between the words > "conclusion" and "whatever" and replace it with a period. So Magritte is > not generating errors based on the encoding of the whole message, it's > responding to specific characters (which I assume it can't read.) > > Thus my suggestion that the problem be solved by simply replacing those > characters with a question mark or a box, plus perhaps a message to the > user. > > As to your suggestion that I add some code... I'd love to, but you could > put everything I know about Squeak in a thimble and have room left over. > (I plan to work on Squeak in my spare moments, but it will be many > months before I'm ready to contribute to a sophisticated project.) But > I'll happily submit additions to the documentation as appropriate, and > supply you with a continuing stream of bug reports as our development > goes forward. > > Thanks, > > Alex > > > > > Lukas Renggli wrote: >> >> On Fri, May 15, 2009 at 11:00 PM, Alex Roston wrote: >> >>> >>> According to our sysadmin, "we're using the Wakom server adapter, plus >>> the >>> most recent version of Magritte, Seaside, and Pier from Lukas, which we >>> updated may 14th." >>> >> >> Ok, I guess you are on Squeak/Pharo then. >> >> >>> >>> The exact error message we're seeing read, "Contents: Invalid input >>> given." >>> I have included a screen shot, which I hope will not be rejected by the >>> mailing list program. >>> >> >> Ok, that doesn't look too bad. This is a validation check of Magritte. >> You can easily change the error message by adding a method like this: >> >> PRCase class>>descriptionDocumentYourPackage: aDescription >> ?^ aDescription kindErrorMessage: 'There was a problem reading your >> input because your word processor is not set to UTF-8.' >> >> To be able to investigate the real cause of the problem I need some >> more information. Could you send step by step introductions on how to >> reproduce the problem. Maybe together with a Word document (I assume >> this is the offender?) that I can copy from? >> >> Cheers, >> Lukas >> >> > > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli http://www.lukas-renggli.ch From clover at pacbell.net Sat May 16 19:45:47 2009 From: clover at pacbell.net (Alex Roston) Date: Sat, 16 May 2009 10:45:47 -0700 Subject: The "Input is Invalid" Error In-Reply-To: <67628d690905161002pd8c946dr5fa1fe8b4f7061ca@mail.gmail.com> References: <4A0DA61A.3080505@pacbell.net> <67628d690905151051t5a6ad967vdec937c850849fa@mail.gmail.com> <4A0DD800.3030006@pacbell.net> <67628d690905160044n49292f0cyd50cd1565da8da13@mail.gmail.com> <4A0EE669.7060304@pacbell.net> <67628d690905161002pd8c946dr5fa1fe8b4f7061ca@mail.gmail.com> Message-ID: <4A0EFBCB.5010306@pacbell.net> Hi Lukas, I assume you used the Sample_One document as I explained. I'll check in with my sysadmin and see what he has to say. Thanks for your effort nonetheless. It is appreciated despite the lack of results. Alex Lukas Renggli wrote: > Thanks for sending the sample documents. > > I tried to reproduce with all of the following 36 possible combinations: > > - Pier 1.1.1 on Mac / latest Pier on Mac / Pier 1.1.1 on Linux > - WAKom / WAKomEncoded > - Safari 3 on Mac / IE 6 on Windows / FireFox 3 on Ubuntu Linux > - Microsoft Word 2008 on Mac / Open Office 2.4 on Ubuntu Linux > > I cannot reproduce the problem. > > Maybe you can try to temporarily replace > MAContainerComponent>>validate to see if there is something strange > going on with exceptions ... > > MAContainerComponent>>validate > self withContainersDo: [ :each | each doValidate ]. > ^ errors isEmpty > > Cheers, > Lukas > > On Sat, May 16, 2009 at 6:14 PM, Alex Roston wrote: > >> Hi Lukas, >> >> Thank you very much for your interest in this problem. I have sent two >> sample documents to your regular email address as they are too big for the >> mailing list. Both are .doc files generated by Open Office 2.4. >> I generated the error by simply copying and pasting the contents of the >> documents into Pier's edit box. (I'm using Firefox on Ubuntu Linux.) >> >> Sample_One does not work, while Sample_Two works just fine, and the only >> thing I did in Sample_Two was delete the long dash between the words >> "conclusion" and "whatever" and replace it with a period. So Magritte is >> not generating errors based on the encoding of the whole message, it's >> responding to specific characters (which I assume it can't read.) >> >> Thus my suggestion that the problem be solved by simply replacing those >> characters with a question mark or a box, plus perhaps a message to the >> user. >> >> As to your suggestion that I add some code... I'd love to, but you could >> put everything I know about Squeak in a thimble and have room left over. >> (I plan to work on Squeak in my spare moments, but it will be many >> months before I'm ready to contribute to a sophisticated project.) But >> I'll happily submit additions to the documentation as appropriate, and >> supply you with a continuing stream of bug reports as our development >> goes forward. >> >> Thanks, >> >> Alex >> >> >> >> >> Lukas Renggli wrote: >> >>> On Fri, May 15, 2009 at 11:00 PM, Alex Roston wrote: >>> >>> >>>> According to our sysadmin, "we're using the Wakom server adapter, plus >>>> the >>>> most recent version of Magritte, Seaside, and Pier from Lukas, which we >>>> updated may 14th." >>>> >>>> >>> Ok, I guess you are on Squeak/Pharo then. >>> >>> >>> >>>> The exact error message we're seeing read, "Contents: Invalid input >>>> given." >>>> I have included a screen shot, which I hope will not be rejected by the >>>> mailing list program. >>>> >>>> >>> Ok, that doesn't look too bad. This is a validation check of Magritte. >>> You can easily change the error message by adding a method like this: >>> >>> PRCase class>>descriptionDocumentYourPackage: aDescription >>> ^ aDescription kindErrorMessage: 'There was a problem reading your >>> input because your word processor is not set to UTF-8.' >>> >>> To be able to investigate the real cause of the problem I need some >>> more information. Could you send step by step introductions on how to >>> reproduce the problem. Maybe together with a Word document (I assume >>> this is the offender?) that I can copy from? >>> >>> Cheers, >>> Lukas >>> >>> >>> >> >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> >> > > > > From clover at pacbell.net Sat May 16 18:05:04 2009 From: clover at pacbell.net (Alex Roston) Date: Sat, 16 May 2009 09:05:04 -0700 Subject: The "Input is Invalid" Error In-Reply-To: <67628d690905160044n49292f0cyd50cd1565da8da13@mail.gmail.com> References: <4A0DA61A.3080505@pacbell.net> <67628d690905151051t5a6ad967vdec937c850849fa@mail.gmail.com> <4A0DD800.3030006@pacbell.net> <67628d690905160044n49292f0cyd50cd1565da8da13@mail.gmail.com> Message-ID: <4A0EE430.1020800@pacbell.net> Hi Lukas, Thank you very much for your interest in this problem. I have attached two sample documents, both are .doc files generated by Open Office 2.4. I generated the error by simply copying and pasting the contents of the documents into Pier's edit box. (I'm using Firefox on Ubuntu Linux.) Sample_One does not work, while Sample_Two works just fine, and the only thing I did in Sample_Two was delete the long dash between the words "conclusion" and "whatever" and replace it with a period. So Magritte is not generating errors based on the encoding of the whole message, it's responding to specific characters (which I assume it can't read.) Thus my suggestion that the problem be solved by simply replacing those characters with a question mark or a box, plus perhaps a message to the user. As to your suggestion that I add some code... I'd love to, but you could put everything I know about Squeak in a thimble and have room left over. (I plan to work on Squeak in my spare moments, but it will be many months before I'm ready to contribute to a sophisticated project.) But I'll happily submit additions to the documentation as appropriate, and supply you with a continuing stream of bug reports as our development goes forward. Thanks, Alex Lukas Renggli wrote: > On Fri, May 15, 2009 at 11:00 PM, Alex Roston wrote: > >> According to our sysadmin, "we're using the Wakom server adapter, plus the >> most recent version of Magritte, Seaside, and Pier from Lukas, which we >> updated may 14th." >> > > Ok, I guess you are on Squeak/Pharo then. > > >> The exact error message we're seeing read, "Contents: Invalid input given." >> I have included a screen shot, which I hope will not be rejected by the >> mailing list program. >> > > Ok, that doesn't look too bad. This is a validation check of Magritte. > You can easily change the error message by adding a method like this: > > PRCase class>>descriptionDocumentYourPackage: aDescription > ^ aDescription kindErrorMessage: 'There was a problem reading your > input because your word processor is not set to UTF-8.' > > To be able to investigate the real cause of the problem I need some > more information. Could you send step by step introductions on how to > reproduce the problem. Maybe together with a Word document (I assume > this is the offender?) that I can copy from? > > Cheers, > Lukas > > -------------- next part -------------- A non-text attachment was scrubbed... Name: Sample_One.doc Type: application/msword Size: 104960 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Sample_Two.doc Type: application/msword Size: 104960 bytes Desc: not available URL: From ducasse at iam.unibe.ch Sun May 17 10:07:10 2009 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Sun, 17 May 2009 10:07:10 +0200 Subject: The "Input is Invalid" Error In-Reply-To: <67628d690905161002pd8c946dr5fa1fe8b4f7061ca@mail.gmail.com> References: <4A0DA61A.3080505@pacbell.net> <67628d690905151051t5a6ad967vdec937c850849fa@mail.gmail.com> <4A0DD800.3030006@pacbell.net> <67628d690905160044n49292f0cyd50cd1565da8da13@mail.gmail.com> <4A0EE669.7060304@pacbell.net> <67628d690905161002pd8c946dr5fa1fe8b4f7061ca@mail.gmail.com> Message-ID: <0187D7AF-3CB5-42F8-A90A-51FFFA62B808@iam.unibe.ch> Lukas I would suggest that people should send you exact information of the problem else this is insane to try in the dark. On May 16, 2009, at 7:02 PM, Lukas Renggli wrote: > Thanks for sending the sample documents. > > I tried to reproduce with all of the following 36 possible > combinations: > > - Pier 1.1.1 on Mac / latest Pier on Mac / Pier 1.1.1 on Linux > - WAKom / WAKomEncoded > - Safari 3 on Mac / IE 6 on Windows / FireFox 3 on Ubuntu Linux > - Microsoft Word 2008 on Mac / Open Office 2.4 on Ubuntu Linux > > I cannot reproduce the problem. > > Maybe you can try to temporarily replace > MAContainerComponent>>validate to see if there is something strange > going on with exceptions ... > > MAContainerComponent>>validate > self withContainersDo: [ :each | each doValidate ]. > ^ errors isEmpty > > Cheers, > Lukas > > On Sat, May 16, 2009 at 6:14 PM, Alex Roston > wrote: >> Hi Lukas, >> >> Thank you very much for your interest in this problem. I have sent >> two >> sample documents to your regular email address as they are too big >> for the >> mailing list. Both are .doc files generated by Open Office 2.4. >> I generated the error by simply copying and pasting the contents of >> the >> documents into Pier's edit box. (I'm using Firefox on Ubuntu Linux.) >> >> Sample_One does not work, while Sample_Two works just fine, and the >> only >> thing I did in Sample_Two was delete the long dash between the words >> "conclusion" and "whatever" and replace it with a period. So >> Magritte is >> not generating errors based on the encoding of the whole message, >> it's >> responding to specific characters (which I assume it can't read.) >> >> Thus my suggestion that the problem be solved by simply replacing >> those >> characters with a question mark or a box, plus perhaps a message to >> the >> user. >> >> As to your suggestion that I add some code... I'd love to, but you >> could >> put everything I know about Squeak in a thimble and have room left >> over. >> (I plan to work on Squeak in my spare moments, but it will be many >> months before I'm ready to contribute to a sophisticated project.) >> But >> I'll happily submit additions to the documentation as appropriate, >> and >> supply you with a continuing stream of bug reports as our development >> goes forward. >> >> Thanks, >> >> Alex >> >> >> >> >> Lukas Renggli wrote: >>> >>> On Fri, May 15, 2009 at 11:00 PM, Alex Roston >>> wrote: >>> >>>> >>>> According to our sysadmin, "we're using the Wakom server adapter, >>>> plus >>>> the >>>> most recent version of Magritte, Seaside, and Pier from Lukas, >>>> which we >>>> updated may 14th." >>>> >>> >>> Ok, I guess you are on Squeak/Pharo then. >>> >>> >>>> >>>> The exact error message we're seeing read, "Contents: Invalid input >>>> given." >>>> I have included a screen shot, which I hope will not be rejected >>>> by the >>>> mailing list program. >>>> >>> >>> Ok, that doesn't look too bad. This is a validation check of >>> Magritte. >>> You can easily change the error message by adding a method like >>> this: >>> >>> PRCase class>>descriptionDocumentYourPackage: aDescription >>> ^ aDescription kindErrorMessage: 'There was a problem reading your >>> input because your word processor is not set to UTF-8.' >>> >>> To be able to investigate the real cause of the problem I need some >>> more information. Could you send step by step introductions on how >>> to >>> reproduce the problem. Maybe together with a Word document (I assume >>> this is the offender?) that I can copy from? >>> >>> Cheers, >>> Lukas >>> >>> >> >> >> >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > From norbert at hartl.name Sun May 17 10:35:35 2009 From: norbert at hartl.name (Norbert Hartl) Date: Sun, 17 May 2009 10:35:35 +0200 Subject: value link extendable? Message-ID: <1242549335.5121.41.camel@cineflux> Hi, I try to figure out how to organize my environments in pier. In one area of the site I need only to exchange one single component per navigation level. I'm looking for a way to only specify the environment on the top most node. The structure value link is one thing that might solve this problem. Is there a way to add something to the structure that the value link resolved? Then I could specify something like this +value:structure/neighbours+ to resolve a neighbours entry local to the seen page. This way I can have a more heavy weight environment on the top and would just specify neighbours entries on each page. Or is there another way to accomplish the same? thanks, Norbert From renggli at gmail.com Sun May 17 10:49:10 2009 From: renggli at gmail.com (Lukas Renggli) Date: Sun, 17 May 2009 10:49:10 +0200 Subject: value link extendable? In-Reply-To: <1242549335.5121.41.camel@cineflux> References: <1242549335.5121.41.camel@cineflux> Message-ID: <67628d690905170149w116eb04p9d55465b6f2db9d8@mail.gmail.com> > Or is there another way to accomplish the same? Embed the component 'Document' into your environment. This enables another editable area on every page. In the settings of the component you can specify a default document and tell it to inherit the document from the parent page, if you want. HTH, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From norbert at hartl.name Sun May 17 11:05:12 2009 From: norbert at hartl.name (Norbert Hartl) Date: Sun, 17 May 2009 11:05:12 +0200 Subject: value link extendable? In-Reply-To: <67628d690905170149w116eb04p9d55465b6f2db9d8@mail.gmail.com> References: <1242549335.5121.41.camel@cineflux> <67628d690905170149w116eb04p9d55465b6f2db9d8@mail.gmail.com> Message-ID: <1242551112.5121.43.camel@cineflux> On Sun, 2009-05-17 at 10:49 +0200, Lukas Renggli wrote: > > Or is there another way to accomplish the same? > > Embed the component 'Document' into your environment. This enables > another editable area on every page. In the settings of the component > you can specify a default document and tell it to inherit the document > from the parent page, if you want. > I can't find any 'Document" in my pier installation. I added +document+ in my environment but the only thing I could select is a PRDocumentWidget nothing else with document in it. And there is no instance of PRComponent that is called 'Document'. Is this something very new? I'm on gemstone so this should be pier 1.1, right? Norbert From renggli at gmail.com Sun May 17 11:17:11 2009 From: renggli at gmail.com (Lukas Renggli) Date: Sun, 17 May 2009 11:17:11 +0200 Subject: value link extendable? In-Reply-To: <1242551112.5121.43.camel@cineflux> References: <1242549335.5121.41.camel@cineflux> <67628d690905170149w116eb04p9d55465b6f2db9d8@mail.gmail.com> <1242551112.5121.43.camel@cineflux> Message-ID: <67628d690905170217u241086e8j5208fe6e8cc40d5f@mail.gmail.com> Yes, the PRDocumentWidget is the right thing. I don't know its status on GemStone, but it is already quite an old plugin. Lukas On Sunday, May 17, 2009, Norbert Hartl wrote: > On Sun, 2009-05-17 at 10:49 +0200, Lukas Renggli wrote: >> > Or is there another way to accomplish the same? >> >> Embed the component 'Document' into your environment. This enables >> another editable area on every page. In the settings of the component >> you can specify a default document and tell it to inherit the document >> from the parent page, if you want. >> > I can't find any 'Document" in my pier installation. I added > > +document+ > > in my environment but the only thing I could select is a > PRDocumentWidget nothing else with document in it. And there > is no instance of PRComponent that is called 'Document'. Is > this something very new? I'm on gemstone so this should be > pier 1.1, right? > > Norbert > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli http://www.lukas-renggli.ch From girba at iam.unibe.ch Sun May 17 11:20:42 2009 From: girba at iam.unibe.ch (Tudor Girba) Date: Sun, 17 May 2009 11:20:42 +0200 Subject: value link extendable? In-Reply-To: <67628d690905170217u241086e8j5208fe6e8cc40d5f@mail.gmail.com> References: <1242549335.5121.41.camel@cineflux> <67628d690905170149w116eb04p9d55465b6f2db9d8@mail.gmail.com> <1242551112.5121.43.camel@cineflux> <67628d690905170217u241086e8j5208fe6e8cc40d5f@mail.gmail.com> Message-ID: Hi Norbert, Just embed the document in the environment and you will get an extra place to fill text in when you edit a page with that environment. Cheers, Doru On 17 May 2009, at 11:17, Lukas Renggli wrote: > Yes, the PRDocumentWidget is the right thing. I don't know its status > on GemStone, but it is already quite an old plugin. > > Lukas > > On Sunday, May 17, 2009, Norbert Hartl wrote: >> On Sun, 2009-05-17 at 10:49 +0200, Lukas Renggli wrote: >>>> Or is there another way to accomplish the same? >>> >>> Embed the component 'Document' into your environment. This enables >>> another editable area on every page. In the settings of the >>> component >>> you can specify a default document and tell it to inherit the >>> document >>> from the parent page, if you want. >>> >> I can't find any 'Document" in my pier installation. I added >> >> +document+ >> >> in my environment but the only thing I could select is a >> PRDocumentWidget nothing else with document in it. And there >> is no instance of PRComponent that is called 'Document'. Is >> this something very new? I'm on gemstone so this should be >> pier 1.1, right? >> >> Norbert >> >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge." From norbert at hartl.name Sun May 17 13:05:45 2009 From: norbert at hartl.name (Norbert Hartl) Date: Sun, 17 May 2009 13:05:45 +0200 Subject: value link extendable? In-Reply-To: <67628d690905170217u241086e8j5208fe6e8cc40d5f@mail.gmail.com> References: <1242549335.5121.41.camel@cineflux> <67628d690905170149w116eb04p9d55465b6f2db9d8@mail.gmail.com> <1242551112.5121.43.camel@cineflux> <67628d690905170217u241086e8j5208fe6e8cc40d5f@mail.gmail.com> Message-ID: <1242558345.5121.52.camel@cineflux> On Sun, 2009-05-17 at 11:17 +0200, Lukas Renggli wrote: > Yes, the PRDocumentWidget is the right thing. I don't know its status > on GemStone, but it is already quite an old plugin. > Well, it was broken but I fixed it. There were extra selectors called parameterName: in some descriptions. Did they ever exist in magritte? And there were some message html rendererInstance ... I exchanged them with self context renderer I think it is right. Thanks for helping, now it works and it is _exactly_ what I was looking for. But now I need to reset my kernel because I tried too much weird stuff :) thanks, Norbert > Lukas > > On Sunday, May 17, 2009, Norbert Hartl wrote: > > On Sun, 2009-05-17 at 10:49 +0200, Lukas Renggli wrote: > >> > Or is there another way to accomplish the same? > >> > >> Embed the component 'Document' into your environment. This enables > >> another editable area on every page. In the settings of the component > >> you can specify a default document and tell it to inherit the document > >> from the parent page, if you want. > >> > > I can't find any 'Document" in my pier installation. I added > > > > +document+ > > > > in my environment but the only thing I could select is a > > PRDocumentWidget nothing else with document in it. And there > > is no instance of PRComponent that is called 'Document'. Is > > this something very new? I'm on gemstone so this should be > > pier 1.1, right? > > > > Norbert > > > > _______________________________________________ > > Magritte, Pier and Related Tools ... > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > From norbert at hartl.name Sun May 17 13:11:12 2009 From: norbert at hartl.name (Norbert Hartl) Date: Sun, 17 May 2009 13:11:12 +0200 Subject: value link extendable? In-Reply-To: References: <1242549335.5121.41.camel@cineflux> <67628d690905170149w116eb04p9d55465b6f2db9d8@mail.gmail.com> <1242551112.5121.43.camel@cineflux> <67628d690905170217u241086e8j5208fe6e8cc40d5f@mail.gmail.com> Message-ID: <1242558672.5121.57.camel@cineflux> On Sun, 2009-05-17 at 11:20 +0200, Tudor Girba wrote: > Hi Norbert, > > Just embed the document in the environment and you will get an extra > place to fill text in when you edit a page with that environment. > Thanks, but it is really hard to understand what you are writing. For me as a user of pier "the document" has no meaning. For me it would be "embed a PRDocumentWidget component into the environment". And the phrase "when you edit a page" is right but for me there are so many ways to edit things in pier I didn't figure out you mean "_the_ Edit" :) And while I didn't expect it on the same page where I edit the contents of a page I overlooked the extra textinput field the first time. thanks again, Norbert > Cheers, > Doru > > On 17 May 2009, at 11:17, Lukas Renggli wrote: > > > Yes, the PRDocumentWidget is the right thing. I don't know its status > > on GemStone, but it is already quite an old plugin. > > > > Lukas > > > > On Sunday, May 17, 2009, Norbert Hartl wrote: > >> On Sun, 2009-05-17 at 10:49 +0200, Lukas Renggli wrote: > >>>> Or is there another way to accomplish the same? > >>> > >>> Embed the component 'Document' into your environment. This enables > >>> another editable area on every page. In the settings of the > >>> component > >>> you can specify a default document and tell it to inherit the > >>> document > >>> from the parent page, if you want. > >>> > >> I can't find any 'Document" in my pier installation. I added > >> > >> +document+ > >> > >> in my environment but the only thing I could select is a > >> PRDocumentWidget nothing else with document in it. And there > >> is no instance of PRComponent that is called 'Document'. Is > >> this something very new? I'm on gemstone so this should be > >> pier 1.1, right? > >> > >> Norbert > >> > >> _______________________________________________ > >> Magritte, Pier and Related Tools ... > >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > >> > > > > -- > > Lukas Renggli > > http://www.lukas-renggli.ch > > _______________________________________________ > > Magritte, Pier and Related Tools ... > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > -- > www.tudorgirba.com > > "Yesterday is a fact. > Tomorrow is a possibility. > Today is a challenge." > > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From girba at iam.unibe.ch Sun May 17 13:48:16 2009 From: girba at iam.unibe.ch (Tudor Girba) Date: Sun, 17 May 2009 13:48:16 +0200 Subject: value link extendable? In-Reply-To: <1242558672.5121.57.camel@cineflux> References: <1242549335.5121.41.camel@cineflux> <67628d690905170149w116eb04p9d55465b6f2db9d8@mail.gmail.com> <1242551112.5121.43.camel@cineflux> <67628d690905170217u241086e8j5208fe6e8cc40d5f@mail.gmail.com> <1242558672.5121.57.camel@cineflux> Message-ID: Hi Norbert, Thanks for the feedback. Just to clarify the terms. When we mention verbs related to Pier manipulation, we refer to commands. So, to edit a page means to invoke the Edit command on that page. When we refer to other types of edits we typically name them (e.g., Settings, Edit Design). Related to Document/PRDocumentWidget, the first refers to the way a regular user sees the widget in the Pier UI (when choosing the component class), and the second refers to the name of the Smalltalk class. I understood that you were taking a user point of view, so I am actually confused about how you see PRDocumentWidget in the drop down list when selecting the component class. Cheers, Doru On 17 May 2009, at 13:11, Norbert Hartl wrote: > On Sun, 2009-05-17 at 11:20 +0200, Tudor Girba wrote: >> Hi Norbert, >> >> Just embed the document in the environment and you will get an extra >> place to fill text in when you edit a page with that environment. >> > Thanks, but it is really hard to understand what you are writing. > For me as a user of pier "the document" has no meaning. For me it > would be "embed a PRDocumentWidget component into the environment". > And the phrase "when you edit a page" is right but for me there are > so many ways to edit things in pier I didn't figure out you mean > "_the_ Edit" :) > And while I didn't expect it on the same page where I edit the > contents of a page I overlooked the extra textinput field the first > time. > > thanks again, > > Norbert > >> Cheers, >> Doru >> >> On 17 May 2009, at 11:17, Lukas Renggli wrote: >> >>> Yes, the PRDocumentWidget is the right thing. I don't know its >>> status >>> on GemStone, but it is already quite an old plugin. >>> >>> Lukas >>> >>> On Sunday, May 17, 2009, Norbert Hartl wrote: >>>> On Sun, 2009-05-17 at 10:49 +0200, Lukas Renggli wrote: >>>>>> Or is there another way to accomplish the same? >>>>> >>>>> Embed the component 'Document' into your environment. This enables >>>>> another editable area on every page. In the settings of the >>>>> component >>>>> you can specify a default document and tell it to inherit the >>>>> document >>>>> from the parent page, if you want. >>>>> >>>> I can't find any 'Document" in my pier installation. I added >>>> >>>> +document+ >>>> >>>> in my environment but the only thing I could select is a >>>> PRDocumentWidget nothing else with document in it. And there >>>> is no instance of PRComponent that is called 'Document'. Is >>>> this something very new? I'm on gemstone so this should be >>>> pier 1.1, right? >>>> >>>> Norbert >>>> >>>> _______________________________________________ >>>> Magritte, Pier and Related Tools ... >>>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >>>> >>> >>> -- >>> Lukas Renggli >>> http://www.lukas-renggli.ch >>> _______________________________________________ >>> Magritte, Pier and Related Tools ... >>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> >> -- >> www.tudorgirba.com >> >> "Yesterday is a fact. >> Tomorrow is a possibility. >> Today is a challenge." >> >> >> >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com "Every thing should have the right to be different." From norbert at hartl.name Sun May 17 15:06:42 2009 From: norbert at hartl.name (Norbert Hartl) Date: Sun, 17 May 2009 15:06:42 +0200 Subject: value link extendable? In-Reply-To: References: <1242549335.5121.41.camel@cineflux> <67628d690905170149w116eb04p9d55465b6f2db9d8@mail.gmail.com> <1242551112.5121.43.camel@cineflux> <67628d690905170217u241086e8j5208fe6e8cc40d5f@mail.gmail.com> <1242558672.5121.57.camel@cineflux> Message-ID: <1242565602.5121.58.camel@cineflux> On Sun, 2009-05-17 at 13:48 +0200, Tudor Girba wrote: > Hi Norbert, > > Thanks for the feedback. > > Just to clarify the terms. > > When we mention verbs related to Pier manipulation, we refer to > commands. So, to edit a page means to invoke the Edit command on that > page. When we refer to other types of edits we typically name them > (e.g., Settings, Edit Design). > > Related to Document/PRDocumentWidget, the first refers to the way a > regular user sees the widget in the Pier UI (when choosing the > component class), and the second refers to the name of the Smalltalk > class. > > I understood that you were taking a user point of view, so I am > actually confused about how you see PRDocumentWidget in the drop down > list when selecting the component class. I see only the class names in the drop down. Maybe this is something gemstone dependent. Norbert > Cheers, > Doru > > > On 17 May 2009, at 13:11, Norbert Hartl wrote: > > > On Sun, 2009-05-17 at 11:20 +0200, Tudor Girba wrote: > >> Hi Norbert, > >> > >> Just embed the document in the environment and you will get an extra > >> place to fill text in when you edit a page with that environment. > >> > > Thanks, but it is really hard to understand what you are writing. > > For me as a user of pier "the document" has no meaning. For me it > > would be "embed a PRDocumentWidget component into the environment". > > And the phrase "when you edit a page" is right but for me there are > > so many ways to edit things in pier I didn't figure out you mean > > "_the_ Edit" :) > > And while I didn't expect it on the same page where I edit the > > contents of a page I overlooked the extra textinput field the first > > time. > > > > thanks again, > > > > Norbert > > > >> Cheers, > >> Doru > >> > >> On 17 May 2009, at 11:17, Lukas Renggli wrote: > >> > >>> Yes, the PRDocumentWidget is the right thing. I don't know its > >>> status > >>> on GemStone, but it is already quite an old plugin. > >>> > >>> Lukas > >>> > >>> On Sunday, May 17, 2009, Norbert Hartl wrote: > >>>> On Sun, 2009-05-17 at 10:49 +0200, Lukas Renggli wrote: > >>>>>> Or is there another way to accomplish the same? > >>>>> > >>>>> Embed the component 'Document' into your environment. This enables > >>>>> another editable area on every page. In the settings of the > >>>>> component > >>>>> you can specify a default document and tell it to inherit the > >>>>> document > >>>>> from the parent page, if you want. > >>>>> > >>>> I can't find any 'Document" in my pier installation. I added > >>>> > >>>> +document+ > >>>> > >>>> in my environment but the only thing I could select is a > >>>> PRDocumentWidget nothing else with document in it. And there > >>>> is no instance of PRComponent that is called 'Document'. Is > >>>> this something very new? I'm on gemstone so this should be > >>>> pier 1.1, right? > >>>> > >>>> Norbert > >>>> > >>>> _______________________________________________ > >>>> Magritte, Pier and Related Tools ... > >>>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > >>>> > >>> > >>> -- > >>> Lukas Renggli > >>> http://www.lukas-renggli.ch > >>> _______________________________________________ > >>> Magritte, Pier and Related Tools ... > >>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > >> > >> -- > >> www.tudorgirba.com > >> > >> "Yesterday is a fact. > >> Tomorrow is a possibility. > >> Today is a challenge." > >> > >> > >> > >> _______________________________________________ > >> Magritte, Pier and Related Tools ... > >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > > _______________________________________________ > > Magritte, Pier and Related Tools ... > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > -- > www.tudorgirba.com > > "Every thing should have the right to be different." > > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From norbert at hartl.name Sun May 17 15:15:08 2009 From: norbert at hartl.name (Norbert Hartl) Date: Sun, 17 May 2009 15:15:08 +0200 Subject: value link extendable? In-Reply-To: <67628d690905170217u241086e8j5208fe6e8cc40d5f@mail.gmail.com> References: <1242549335.5121.41.camel@cineflux> <67628d690905170149w116eb04p9d55465b6f2db9d8@mail.gmail.com> <1242551112.5121.43.camel@cineflux> <67628d690905170217u241086e8j5208fe6e8cc40d5f@mail.gmail.com> Message-ID: <1242566108.5121.64.camel@cineflux> On Sun, 2009-05-17 at 11:17 +0200, Lukas Renggli wrote: > Yes, the PRDocumentWidget is the right thing. I don't know its status > on GemStone, but it is already quite an old plugin. > I had anoter look and Pier-Documents in my gemstone is Pier-Documents-lr.12 from http://source.lukas-renggli.ch/pieraddons That is strange. I upgrade to -lr.14 but it doesn't work. Probably I would need a magritte update for parameterName: ? And renderInstance? I saw in PRHaloRenderer but nowhere else. Norbert > Lukas > > On Sunday, May 17, 2009, Norbert Hartl wrote: > > On Sun, 2009-05-17 at 10:49 +0200, Lukas Renggli wrote: > >> > Or is there another way to accomplish the same? > >> > >> Embed the component 'Document' into your environment. This enables > >> another editable area on every page. In the settings of the component > >> you can specify a default document and tell it to inherit the document > >> from the parent page, if you want. > >> > > I can't find any 'Document" in my pier installation. I added > > > > +document+ > > > > in my environment but the only thing I could select is a > > PRDocumentWidget nothing else with document in it. And there > > is no instance of PRComponent that is called 'Document'. Is > > this something very new? I'm on gemstone so this should be > > pier 1.1, right? > > > > Norbert > > > > _______________________________________________ > > Magritte, Pier and Related Tools ... > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > From renggli at gmail.com Sun May 17 15:20:26 2009 From: renggli at gmail.com (Lukas Renggli) Date: Sun, 17 May 2009 15:20:26 +0200 Subject: value link extendable? In-Reply-To: <1242565602.5121.58.camel@cineflux> References: <1242549335.5121.41.camel@cineflux> <67628d690905170149w116eb04p9d55465b6f2db9d8@mail.gmail.com> <1242551112.5121.43.camel@cineflux> <67628d690905170217u241086e8j5208fe6e8cc40d5f@mail.gmail.com> <1242558672.5121.57.camel@cineflux> <1242565602.5121.58.camel@cineflux> Message-ID: <67628d690905170620p1a402272pb03a913efbc92ce4@mail.gmail.com> > I see only the class names in the drop down. Maybe this is something > gemstone dependent. Definitely. Pier normally does not display Smalltalk related concepts in the UI. > I had anoter look and Pier-Documents in my gemstone is > > Pier-Documents-lr.12 > > from > > http://source.lukas-renggli.ch/pieraddons > > That is strange. I upgrade to -lr.14 but it doesn't work. > Probably I would need a magritte update for parameterName: ? > And renderInstance? I saw in PRHaloRenderer but nowhere > else. Yes. This requires you to update to the very latest versions of Magritte-Core, Magritte-Seaside, Pier-Core and Pier-Seaside. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From p3anoman at gmail.com Sun May 17 19:47:04 2009 From: p3anoman at gmail.com (John McKeon) Date: Sun, 17 May 2009 13:47:04 -0400 Subject: value link extendable? In-Reply-To: <67628d690905170620p1a402272pb03a913efbc92ce4@mail.gmail.com> References: <1242549335.5121.41.camel@cineflux> <67628d690905170149w116eb04p9d55465b6f2db9d8@mail.gmail.com> <1242551112.5121.43.camel@cineflux> <67628d690905170217u241086e8j5208fe6e8cc40d5f@mail.gmail.com> <1242558672.5121.57.camel@cineflux> <1242565602.5121.58.camel@cineflux> <67628d690905170620p1a402272pb03a913efbc92ce4@mail.gmail.com> Message-ID: <40f637ec0905171047q5b8f746alfc55195b06b00a5c@mail.gmail.com> On Sun, May 17, 2009 at 9:20 AM, Lukas Renggli wrote: > > I see only the class names in the drop down. Maybe this is something > > gemstone dependent. > > > Definitely. Pier normally does not display Smalltalk related concepts in > the UI. > > > I had anoter look and Pier-Documents in my gemstone is > > > > Pier-Documents-lr.12 > > > > from > > > > http://source.lukas-renggli.ch/pieraddons > > > > That is strange. I upgrade to -lr.14 but it doesn't work. > > Probably I would need a magritte update for parameterName: ? > > And renderInstance? I saw in PRHaloRenderer but nowhere > > else. > > Yes. This requires you to update to the very latest versions of > Magritte-Core, Magritte-Seaside, Pier-Core and Pier-Seaside. > If I could throw in two cents, when you choose the Add command and then select Component (instead of Page), you can choose PRDocumentWidget from the drop down as the component to add. I imagine this is how Norbert is arriving at the point where he sees only component classes in the selection. If a user takes this route is it the same as Add'ing a Page? Not trying to confuse the issue further.... John > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dale.henrichs at gemstone.com Sun May 17 21:19:21 2009 From: dale.henrichs at gemstone.com (Dale Henrichs) Date: Sun, 17 May 2009 12:19:21 -0700 (PDT) Subject: value link extendable? In-Reply-To: <1242565602.5121.58.camel@cineflux> Message-ID: <189344394.927411242587961501.JavaMail.root@gir> Norbert, I've submitted a GemStone bug on this, so you should look forward to fix in the next week or so... Dale ----- "Norbert Hartl" wrote: | On Sun, 2009-05-17 at 13:48 +0200, Tudor Girba wrote: | > Hi Norbert, | > | > Thanks for the feedback. | > | > Just to clarify the terms. | > | > When we mention verbs related to Pier manipulation, we refer to | > commands. So, to edit a page means to invoke the Edit command on | that | > page. When we refer to other types of edits we typically name them | | > (e.g., Settings, Edit Design). | > | > Related to Document/PRDocumentWidget, the first refers to the way a | | > regular user sees the widget in the Pier UI (when choosing the | > component class), and the second refers to the name of the Smalltalk | | > class. | > | > I understood that you were taking a user point of view, so I am | > actually confused about how you see PRDocumentWidget in the drop | down | > list when selecting the component class. | | I see only the class names in the drop down. Maybe this is something | gemstone dependent. | | Norbert | > Cheers, | > Doru | > | > | > On 17 May 2009, at 13:11, Norbert Hartl wrote: | > | > > On Sun, 2009-05-17 at 11:20 +0200, Tudor Girba wrote: | > >> Hi Norbert, | > >> | > >> Just embed the document in the environment and you will get an | extra | > >> place to fill text in when you edit a page with that | environment. | > >> | > > Thanks, but it is really hard to understand what you are writing. | > > For me as a user of pier "the document" has no meaning. For me it | > > would be "embed a PRDocumentWidget component into the | environment". | > > And the phrase "when you edit a page" is right but for me there | are | > > so many ways to edit things in pier I didn't figure out you mean | > > "_the_ Edit" :) | > > And while I didn't expect it on the same page where I edit the | > > contents of a page I overlooked the extra textinput field the | first | > > time. | > > | > > thanks again, | > > | > > Norbert | > > | > >> Cheers, | > >> Doru | > >> | > >> On 17 May 2009, at 11:17, Lukas Renggli wrote: | > >> | > >>> Yes, the PRDocumentWidget is the right thing. I don't know its | | > >>> status | > >>> on GemStone, but it is already quite an old plugin. | > >>> | > >>> Lukas | > >>> | > >>> On Sunday, May 17, 2009, Norbert Hartl | wrote: | > >>>> On Sun, 2009-05-17 at 10:49 +0200, Lukas Renggli wrote: | > >>>>>> Or is there another way to accomplish the same? | > >>>>> | > >>>>> Embed the component 'Document' into your environment. This | enables | > >>>>> another editable area on every page. In the settings of the | > >>>>> component | > >>>>> you can specify a default document and tell it to inherit the | > >>>>> document | > >>>>> from the parent page, if you want. | > >>>>> | > >>>> I can't find any 'Document" in my pier installation. I added | > >>>> | > >>>> +document+ | > >>>> | > >>>> in my environment but the only thing I could select is a | > >>>> PRDocumentWidget nothing else with document in it. And there | > >>>> is no instance of PRComponent that is called 'Document'. Is | > >>>> this something very new? I'm on gemstone so this should be | > >>>> pier 1.1, right? | > >>>> | > >>>> Norbert | > >>>> | > >>>> _______________________________________________ | > >>>> Magritte, Pier and Related Tools ... | > >>>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki | > >>>> | > >>> | > >>> -- | > >>> Lukas Renggli | > >>> http://www.lukas-renggli.ch | > >>> _______________________________________________ | > >>> Magritte, Pier and Related Tools ... | > >>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki | > >> | > >> -- | > >> www.tudorgirba.com | > >> | > >> "Yesterday is a fact. | > >> Tomorrow is a possibility. | > >> Today is a challenge." | > >> | > >> | > >> | > >> _______________________________________________ | > >> Magritte, Pier and Related Tools ... | > >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki | > > | > > _______________________________________________ | > > Magritte, Pier and Related Tools ... | > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki | > | > -- | > www.tudorgirba.com | > | > "Every thing should have the right to be different." | > | > | > | > _______________________________________________ | > Magritte, Pier and Related Tools ... | > https://www.iam.unibe.ch/mailman/listinfo/smallwiki | | _______________________________________________ | Magritte, Pier and Related Tools ... | https://www.iam.unibe.ch/mailman/listinfo/smallwiki From dale.henrichs at gemstone.com Sun May 17 21:27:27 2009 From: dale.henrichs at gemstone.com (Dale Henrichs) Date: Sun, 17 May 2009 12:27:27 -0700 (PDT) Subject: value link extendable? In-Reply-To: <120420185.927441242588137021.JavaMail.root@gir> Message-ID: <32039167.927461242588447905.JavaMail.root@gir> ----- "Lukas Renggli" wrote: | > I had anoter look and Pier-Documents in my gemstone is | > | > Pier-Documents-lr.12 | > | > from | > | > http://source.lukas-renggli.ch/pieraddons | > | > That is strange. I upgrade to -lr.14 but it doesn't work. | > Probably I would need a magritte update for parameterName: ? | > And renderInstance? I saw in PRHaloRenderer but nowhere | > else. | | Yes. This requires you to update to the very latest versions of | Magritte-Core, Magritte-Seaside, Pier-Core and Pier-Seaside. | Lukas, Are these updates part of Pier 1.1.1 (which is what I moved to with GLASS.230-dkh.209)? At the time I moved to 1.1.1 I used the 1.1.1 image that was distributed - at the time there were later versions of some of the packages, but I was reluctant to load packages that may be meant to be part of the release... Is there a later version of Pier available (later than 1.1.1)? I ask, because I have had to make GemStone-specific changes to some of the packages, so it's not quite as easy as just loading the newer versions of the packages... Dale From renggli at gmail.com Sun May 17 21:52:55 2009 From: renggli at gmail.com (Lukas Renggli) Date: Sun, 17 May 2009 21:52:55 +0200 Subject: value link extendable? In-Reply-To: <32039167.927461242588447905.JavaMail.root@gir> References: <120420185.927441242588137021.JavaMail.root@gir> <32039167.927461242588447905.JavaMail.root@gir> Message-ID: <67628d690905171252r1ee0cc4aq2b142364ac1dc162@mail.gmail.com> > Is there a later version of Pier available (later than 1.1.1)? Not yet, many people seem to just use the latest version though. I am not entirely happy with the value links and file handling (both issues were recently discussed here on the list). If these issues are resolved a new version like 1.2 will be necessary ... > I ask, because I have had to make GemStone-specific changes to some of the packages, so it's not quite as easy as just loading the newer versions of the packages... What are these issues? If possible I would like to make this easier. Especially if Pier moves towards Seaside 2.9, I would like to package all platform dependent code separately. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From norbert at hartl.name Sun May 17 22:00:17 2009 From: norbert at hartl.name (Norbert Hartl) Date: Sun, 17 May 2009 22:00:17 +0200 Subject: value link extendable? In-Reply-To: <189344394.927411242587961501.JavaMail.root@gir> References: <189344394.927411242587961501.JavaMail.root@gir> Message-ID: <1242590417.5121.66.camel@cineflux> On Sun, 2009-05-17 at 12:19 -0700, Dale Henrichs wrote: > Norbert, > > I've submitted a GemStone bug on this, so you should look forward to fix in the next week or so... > Great! I could send you my findings but it seems it just happens because of the version mismatch. Norbert > Dale > ----- "Norbert Hartl" wrote: > > | On Sun, 2009-05-17 at 13:48 +0200, Tudor Girba wrote: > | > Hi Norbert, > | > > | > Thanks for the feedback. > | > > | > Just to clarify the terms. > | > > | > When we mention verbs related to Pier manipulation, we refer to > | > commands. So, to edit a page means to invoke the Edit command on > | that > | > page. When we refer to other types of edits we typically name them > | > | > (e.g., Settings, Edit Design). > | > > | > Related to Document/PRDocumentWidget, the first refers to the way a > | > | > regular user sees the widget in the Pier UI (when choosing the > | > component class), and the second refers to the name of the Smalltalk > | > | > class. > | > > | > I understood that you were taking a user point of view, so I am > | > actually confused about how you see PRDocumentWidget in the drop > | down > | > list when selecting the component class. > | > | I see only the class names in the drop down. Maybe this is something > | gemstone dependent. > | > | Norbert > | > Cheers, > | > Doru > | > > | > > | > On 17 May 2009, at 13:11, Norbert Hartl wrote: > | > > | > > On Sun, 2009-05-17 at 11:20 +0200, Tudor Girba wrote: > | > >> Hi Norbert, > | > >> > | > >> Just embed the document in the environment and you will get an > | extra > | > >> place to fill text in when you edit a page with that > | environment. > | > >> > | > > Thanks, but it is really hard to understand what you are writing. > | > > For me as a user of pier "the document" has no meaning. For me it > | > > would be "embed a PRDocumentWidget component into the > | environment". > | > > And the phrase "when you edit a page" is right but for me there > | are > | > > so many ways to edit things in pier I didn't figure out you mean > | > > "_the_ Edit" :) > | > > And while I didn't expect it on the same page where I edit the > | > > contents of a page I overlooked the extra textinput field the > | first > | > > time. > | > > > | > > thanks again, > | > > > | > > Norbert > | > > > | > >> Cheers, > | > >> Doru > | > >> > | > >> On 17 May 2009, at 11:17, Lukas Renggli wrote: > | > >> > | > >>> Yes, the PRDocumentWidget is the right thing. I don't know its > | > | > >>> status > | > >>> on GemStone, but it is already quite an old plugin. > | > >>> > | > >>> Lukas > | > >>> > | > >>> On Sunday, May 17, 2009, Norbert Hartl > | wrote: > | > >>>> On Sun, 2009-05-17 at 10:49 +0200, Lukas Renggli wrote: > | > >>>>>> Or is there another way to accomplish the same? > | > >>>>> > | > >>>>> Embed the component 'Document' into your environment. This > | enables > | > >>>>> another editable area on every page. In the settings of the > | > >>>>> component > | > >>>>> you can specify a default document and tell it to inherit the > | > >>>>> document > | > >>>>> from the parent page, if you want. > | > >>>>> > | > >>>> I can't find any 'Document" in my pier installation. I added > | > >>>> > | > >>>> +document+ > | > >>>> > | > >>>> in my environment but the only thing I could select is a > | > >>>> PRDocumentWidget nothing else with document in it. And there > | > >>>> is no instance of PRComponent that is called 'Document'. Is > | > >>>> this something very new? I'm on gemstone so this should be > | > >>>> pier 1.1, right? > | > >>>> > | > >>>> Norbert > | > >>>> > | > >>>> _______________________________________________ > | > >>>> Magritte, Pier and Related Tools ... > | > >>>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > | > >>>> > | > >>> > | > >>> -- > | > >>> Lukas Renggli > | > >>> http://www.lukas-renggli.ch > | > >>> _______________________________________________ > | > >>> Magritte, Pier and Related Tools ... > | > >>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > | > >> > | > >> -- > | > >> www.tudorgirba.com > | > >> > | > >> "Yesterday is a fact. > | > >> Tomorrow is a possibility. > | > >> Today is a challenge." > | > >> > | > >> > | > >> > | > >> _______________________________________________ > | > >> Magritte, Pier and Related Tools ... > | > >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > | > > > | > > _______________________________________________ > | > > Magritte, Pier and Related Tools ... > | > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > | > > | > -- > | > www.tudorgirba.com > | > > | > "Every thing should have the right to be different." > | > > | > > | > > | > _______________________________________________ > | > Magritte, Pier and Related Tools ... > | > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > | > | _______________________________________________ > | Magritte, Pier and Related Tools ... > | https://www.iam.unibe.ch/mailman/listinfo/smallwiki > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From dale.henrichs at gemstone.com Sun May 17 22:02:23 2009 From: dale.henrichs at gemstone.com (Dale Henrichs) Date: Sun, 17 May 2009 13:02:23 -0700 (PDT) Subject: value link extendable? In-Reply-To: <1242590417.5121.66.camel@cineflux> Message-ID: <713495065.927531242590543968.JavaMail.root@gir> Norbert, If you've got some more detail, I'd appreciate it, especially if the fix is just use the correct set of package versions. Dale ----- "Norbert Hartl" wrote: | On Sun, 2009-05-17 at 12:19 -0700, Dale Henrichs wrote: | > Norbert, | > | > I've submitted a GemStone bug on this, so you should look forward to | fix in the next week or so... | > | Great! I could send you my findings but it seems it just happens | because of the version mismatch. | | Norbert | > Dale | > ----- "Norbert Hartl" wrote: | > | > | On Sun, 2009-05-17 at 13:48 +0200, Tudor Girba wrote: | > | > Hi Norbert, | > | > | > | > Thanks for the feedback. | > | > | > | > Just to clarify the terms. | > | > | > | > When we mention verbs related to Pier manipulation, we refer to | | > | > commands. So, to edit a page means to invoke the Edit command | on | > | that | > | > page. When we refer to other types of edits we typically name | them | > | | > | > (e.g., Settings, Edit Design). | > | > | > | > Related to Document/PRDocumentWidget, the first refers to the | way a | > | | > | > regular user sees the widget in the Pier UI (when choosing the | | > | > component class), and the second refers to the name of the | Smalltalk | > | | > | > class. | > | > | > | > I understood that you were taking a user point of view, so I am | | > | > actually confused about how you see PRDocumentWidget in the | drop | > | down | > | > list when selecting the component class. | > | | > | I see only the class names in the drop down. Maybe this is | something | > | gemstone dependent. | > | | > | Norbert | > | > Cheers, | > | > Doru | > | > | > | > | > | > On 17 May 2009, at 13:11, Norbert Hartl wrote: | > | > | > | > > On Sun, 2009-05-17 at 11:20 +0200, Tudor Girba wrote: | > | > >> Hi Norbert, | > | > >> | > | > >> Just embed the document in the environment and you will get | an | > | extra | > | > >> place to fill text in when you edit a page with that | > | environment. | > | > >> | > | > > Thanks, but it is really hard to understand what you are | writing. | > | > > For me as a user of pier "the document" has no meaning. For me | it | > | > > would be "embed a PRDocumentWidget component into the | > | environment". | > | > > And the phrase "when you edit a page" is right but for me | there | > | are | > | > > so many ways to edit things in pier I didn't figure out you | mean | > | > > "_the_ Edit" :) | > | > > And while I didn't expect it on the same page where I edit | the | > | > > contents of a page I overlooked the extra textinput field the | > | first | > | > > time. | > | > > | > | > > thanks again, | > | > > | > | > > Norbert | > | > > | > | > >> Cheers, | > | > >> Doru | > | > >> | > | > >> On 17 May 2009, at 11:17, Lukas Renggli wrote: | > | > >> | > | > >>> Yes, the PRDocumentWidget is the right thing. I don't know | its | > | | > | > >>> status | > | > >>> on GemStone, but it is already quite an old plugin. | > | > >>> | > | > >>> Lukas | > | > >>> | > | > >>> On Sunday, May 17, 2009, Norbert Hartl | > | wrote: | > | > >>>> On Sun, 2009-05-17 at 10:49 +0200, Lukas Renggli wrote: | > | > >>>>>> Or is there another way to accomplish the same? | > | > >>>>> | > | > >>>>> Embed the component 'Document' into your environment. | This | > | enables | > | > >>>>> another editable area on every page. In the settings of | the | > | > >>>>> component | > | > >>>>> you can specify a default document and tell it to inherit | the | > | > >>>>> document | > | > >>>>> from the parent page, if you want. | > | > >>>>> | > | > >>>> I can't find any 'Document" in my pier installation. I | added | > | > >>>> | > | > >>>> +document+ | > | > >>>> | > | > >>>> in my environment but the only thing I could select is a | > | > >>>> PRDocumentWidget nothing else with document in it. And | there | > | > >>>> is no instance of PRComponent that is called 'Document'. | Is | > | > >>>> this something very new? I'm on gemstone so this should be | > | > >>>> pier 1.1, right? | > | > >>>> | > | > >>>> Norbert | > | > >>>> | > | > >>>> _______________________________________________ | > | > >>>> Magritte, Pier and Related Tools ... | > | > >>>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki | > | > >>>> | > | > >>> | > | > >>> -- | > | > >>> Lukas Renggli | > | > >>> http://www.lukas-renggli.ch | > | > >>> _______________________________________________ | > | > >>> Magritte, Pier and Related Tools ... | > | > >>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki | > | > >> | > | > >> -- | > | > >> www.tudorgirba.com | > | > >> | > | > >> "Yesterday is a fact. | > | > >> Tomorrow is a possibility. | > | > >> Today is a challenge." | > | > >> | > | > >> | > | > >> | > | > >> _______________________________________________ | > | > >> Magritte, Pier and Related Tools ... | > | > >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki | > | > > | > | > > _______________________________________________ | > | > > Magritte, Pier and Related Tools ... | > | > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki | > | > | > | > -- | > | > www.tudorgirba.com | > | > | > | > "Every thing should have the right to be different." | > | > | > | > | > | > | > | > _______________________________________________ | > | > Magritte, Pier and Related Tools ... | > | > https://www.iam.unibe.ch/mailman/listinfo/smallwiki | > | | > | _______________________________________________ | > | Magritte, Pier and Related Tools ... | > | https://www.iam.unibe.ch/mailman/listinfo/smallwiki | > _______________________________________________ | > Magritte, Pier and Related Tools ... | > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From norbert at hartl.name Sun May 17 22:13:08 2009 From: norbert at hartl.name (Norbert Hartl) Date: Sun, 17 May 2009 22:13:08 +0200 Subject: Parameterized component links Message-ID: <1242591188.5121.77.camel@cineflux> Hi, I asked some moons ago about the possibility to have parameterized component links. I'm not that familiar with pier so my solution to this might be a bit cheesy. I wanted to have for multiple reason the ability to do +mycomponent1|key=value+ to parameterize a component at rendering time. The problem is that the string is parsed to a link and the link has the parameters. So the question is how the component gets notice of these. The last possible call to do I recognized to be PRViewRenderer>>visitInternalLinkEmbed: I added the following to it at the beginning (anObject target isComponent) ifTrue: [ anObject parameters do: [:each| (self context componentAt: anObject target) propertyAt: each key put: each value. ] ]. So I just copy all the parameters over to the component. I found that PRComponent has already properties so I'm using these. Is this feasible to do? Is there a better way to do? Can this be added to pier? I use this for two scenarios: - advising a component what type it should filter - to select a child component from a Magritte container (not done, yet) thanks, Norbert From renggli at gmail.com Sun May 17 22:24:29 2009 From: renggli at gmail.com (Lukas Renggli) Date: Sun, 17 May 2009 22:24:29 +0200 Subject: Parameterized component links In-Reply-To: <1242591188.5121.77.camel@cineflux> References: <1242591188.5121.77.camel@cineflux> Message-ID: <67628d690905171324t34e56c4cl8870200276c03b33@mail.gmail.com> > I asked some moons ago about the possibility to have parameterized > component links. I'm not that familiar with pier so my solution to this > might be a bit cheesy. I added this functionality after you asked (see PREmbeddedRenderer>>#visitComponent:). > I wanted to have for multiple reason the ability to do > > +mycomponent1|key=value+ The key is set in the description of the component using #parameterName: Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From dale.henrichs at gemstone.com Sun May 17 22:28:48 2009 From: dale.henrichs at gemstone.com (Dale Henrichs) Date: Sun, 17 May 2009 13:28:48 -0700 (PDT) Subject: value link extendable? In-Reply-To: <1513290606.927581242591785241.JavaMail.root@gir> Message-ID: <524535168.927601242592128344.JavaMail.root@gir> ----- "Lukas Renggli" wrote: | | > I ask, because I have had to make GemStone-specific changes to some | of the packages, so it's not quite as easy as just loading the newer | versions of the packages... | | What are these issues? If possible I would like to make this easier. | Especially if Pier moves towards Seaside 2.9, I would like to package | all platform dependent code separately. The list isn't real big (i'd have to do a diff to get the little changes), but the main change that I'm thinking/worried about is actually a Magritte issue that overflows into Pier. GemStone can't migrate an object that is on the stack (as a receiver), this means that the normal Magritte mechanism for creating variables doesn't work in GemStone...callers of readUsing: ... the solution for GemStone is to flip the logic: if an 'object readUsing: aDescription' fails with an ErrCantBecomeSelfOnStack error, because object is a receiver on the stack, I retry doing 'aDescription accessor read: object'...object isn't on the stack so the migrate succeeds ... unfortunately there are a number of places where I have to insert GemStone-specific code ... in Magritte and Pier ... doing anything else would have been even more intrusive and probably broken a ton of code to boot... Offhand there are probably only 20 methods affected but they are sprinkled around the system... Dale From renggli at gmail.com Sun May 17 22:41:29 2009 From: renggli at gmail.com (Lukas Renggli) Date: Sun, 17 May 2009 22:41:29 +0200 Subject: GemStone Compatibility Message-ID: <67628d690905171341k69a550afv480cad8686cfa37d@mail.gmail.com> > GemStone can't migrate an object that is on the stack (as a receiver), this means that the normal Magritte mechanism for creating variables doesn't work in GemStone...callers of readUsing: ... the solution for GemStone is to flip the logic: I don't understand the problem. As far as I understand this only appears when the MAAutoSelectorAccessor is used. Magritte itself (with the exception of the respective test case) and Pier does not make use of this functionality. Personally I never use MAAutoSelectorAccessor, I rather use the refactoring tools. If nobody opposes I would propose to remove it? Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From obi068 at gmail.com Sun May 17 22:56:53 2009 From: obi068 at gmail.com (Gerhard Obermann) Date: Sun, 17 May 2009 22:56:53 +0200 Subject: GemStone Compatibility In-Reply-To: <67628d690905171341k69a550afv480cad8686cfa37d@mail.gmail.com> References: <67628d690905171341k69a550afv480cad8686cfa37d@mail.gmail.com> Message-ID: <7b7d752d0905171356n146073b0y5f013253e92665c@mail.gmail.com> +1 I always thought that MAAutoSelectorAccessor is not really usefull! Cheers, Gerhard On Sun, May 17, 2009 at 10:41 PM, Lukas Renggli wrote: > > GemStone can't migrate an object that is on the stack (as a receiver), > this means that the normal Magritte mechanism for creating variables doesn't > work in GemStone...callers of readUsing: ... the solution for GemStone is to > flip the logic: > > I don't understand the problem. As far as I understand this only > appears when the MAAutoSelectorAccessor is used. Magritte itself (with > the exception of the respective test case) and Pier does not make use > of this functionality. > > Personally I never use MAAutoSelectorAccessor, I rather use the > refactoring tools. If nobody opposes I would propose to remove it? > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dale.henrichs at gemstone.com Sun May 17 23:04:10 2009 From: dale.henrichs at gemstone.com (Dale Henrichs) Date: Sun, 17 May 2009 14:04:10 -0700 (PDT) Subject: GemStone Compatibility In-Reply-To: <67628d690905171341k69a550afv480cad8686cfa37d@mail.gmail.com> Message-ID: <213461296.927681242594250791.JavaMail.root@gir> If a feature is there it will be used ... I made the changes in response to a bug report by a user. If you get rid of it, I can toss those changes and while I'm at it, I will audit the other GemStone-specific changes and get back to you with the ones that are still problematic. Dale ----- "Lukas Renggli" wrote: | > GemStone can't migrate an object that is on the stack (as a | receiver), this means that the normal Magritte mechanism for creating | variables doesn't work in GemStone...callers of readUsing: ... the | solution for GemStone is to flip the logic: | | I don't understand the problem. As far as I understand this only | appears when the MAAutoSelectorAccessor is used. Magritte itself | (with | the exception of the respective test case) and Pier does not make use | of this functionality. | | Personally I never use MAAutoSelectorAccessor, I rather use the | refactoring tools. If nobody opposes I would propose to remove it? | | Cheers, | Lukas | | -- | Lukas Renggli | http://www.lukas-renggli.ch | _______________________________________________ | Magritte, Pier and Related Tools ... | https://www.iam.unibe.ch/mailman/listinfo/smallwiki From norbert at hartl.name Sun May 17 23:08:48 2009 From: norbert at hartl.name (Norbert Hartl) Date: Sun, 17 May 2009 23:08:48 +0200 Subject: Parameterized component links In-Reply-To: <67628d690905171324t34e56c4cl8870200276c03b33@mail.gmail.com> References: <1242591188.5121.77.camel@cineflux> <67628d690905171324t34e56c4cl8870200276c03b33@mail.gmail.com> Message-ID: <1242594528.5121.96.camel@cineflux> On Sun, 2009-05-17 at 22:24 +0200, Lukas Renggli wrote: > > I asked some moons ago about the possibility to have parameterized > > component links. I'm not that familiar with pier so my solution to this > > might be a bit cheesy. > > I added this functionality after you asked (see > PREmbeddedRenderer>>#visitComponent:). > Didn't you tell me to take care myself about it? Or did you tell me that it is there? Can't remember! But thanks anyway. I shortly browsed the stuff in monticello and that looks quite good. I'm eager to test it. But I'm glad I tried to do it myself.A few things more learned about pier. > > I wanted to have for multiple reason the ability to do > > > > +mycomponent1|key=value+ > > The key is set in the description of the component using #parameterName: > All it needs is another description :) Well done! thanks, Norbert From norbert at hartl.name Sun May 17 23:11:03 2009 From: norbert at hartl.name (Norbert Hartl) Date: Sun, 17 May 2009 23:11:03 +0200 Subject: GemStone Compatibility In-Reply-To: <67628d690905171341k69a550afv480cad8686cfa37d@mail.gmail.com> References: <67628d690905171341k69a550afv480cad8686cfa37d@mail.gmail.com> Message-ID: <1242594663.5121.98.camel@cineflux> On Sun, 2009-05-17 at 22:41 +0200, Lukas Renggli wrote: > > GemStone can't migrate an object that is on the stack (as a receiver), this means that the normal Magritte mechanism for creating variables doesn't work in GemStone...callers of readUsing: ... the solution for GemStone is to flip the logic: > > I don't understand the problem. As far as I understand this only > appears when the MAAutoSelectorAccessor is used. Magritte itself (with > the exception of the respective test case) and Pier does not make use > of this functionality. > > Personally I never use MAAutoSelectorAccessor, I rather use the > refactoring tools. If nobody opposes I would propose to remove it? > I used it in the beginning. Than the black magic scared me to death. Never touched it again! I'm for removing, too! Norbert From renggli at gmail.com Sun May 17 23:13:27 2009 From: renggli at gmail.com (Lukas Renggli) Date: Sun, 17 May 2009 23:13:27 +0200 Subject: GemStone Compatibility In-Reply-To: <213461296.927681242594250791.JavaMail.root@gir> References: <67628d690905171341k69a550afv480cad8686cfa37d@mail.gmail.com> <213461296.927681242594250791.JavaMail.root@gir> Message-ID: <67628d690905171413i572cda2eg66cad59f30fd367e@mail.gmail.com> I think MAAutoAccessor is rarely useful, except when you want to quickly prototype an application and generate inst-vars and accessors automatically. After the initial prototyping phase it is hardly useful to check for accessors and inst-vars on every read and write access. I removed it from the latest commit. If somebody really wants this feature, it can be easily retrieved from the history and packaged separately. Lukas On Sun, May 17, 2009 at 11:04 PM, Dale Henrichs wrote: > If a feature is there it will be used ... I made the changes in response to a bug report by a user. > > If you get rid of it, I can toss those changes and while I'm at it, I will audit the other GemStone-specific changes and get back to you with the ones that are still problematic. > > Dale > > > ----- "Lukas Renggli" wrote: > > | > GemStone can't migrate an object that is on the stack (as a > | receiver), this means that the normal Magritte mechanism for creating > | variables doesn't work in GemStone...callers of readUsing: ... the > | solution for GemStone is to flip the logic: > | > | I don't understand the problem. As far as I understand this only > | appears when the MAAutoSelectorAccessor is used. Magritte itself > | (with > | the exception of the respective test case) and Pier does not make use > | of this functionality. > | > | Personally I never use MAAutoSelectorAccessor, I rather use the > | refactoring tools. If nobody opposes I would propose to remove it? > | > | Cheers, > | Lukas > | > | -- > | Lukas Renggli > | http://www.lukas-renggli.ch > | _______________________________________________ > | Magritte, Pier and Related Tools ... > | https://www.iam.unibe.ch/mailman/listinfo/smallwiki > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli http://www.lukas-renggli.ch From insurgent at embarqmail.com Mon May 18 01:32:32 2009 From: insurgent at embarqmail.com (John Rubier) Date: Sun, 17 May 2009 19:32:32 -0400 Subject: Pier-Twitter Message-ID: <4A109E90.9070701@embarqmail.com> Hi all, I made 2 small changes to the add-on Pier-Twitter so the "agoString" is properly calculated for timezones with offsets other than 0 from UTC. I've posted the mcz file here: http://drop.io/Pier_Twitter_jtr_10 Hopefully it's properly done as I've not used Monticello before other than to load stuff into Squeak. Be sure to let me know if this should be handled in a different manner in the future. Take care, John From renggli at gmail.com Mon May 18 08:44:40 2009 From: renggli at gmail.com (Lukas Renggli) Date: Mon, 18 May 2009 08:44:40 +0200 Subject: Pier-Twitter In-Reply-To: <4A109E90.9070701@embarqmail.com> References: <4A109E90.9070701@embarqmail.com> Message-ID: <67628d690905172344v1df16481kd62d8b34a4824974@mail.gmail.com> Hi John > I made 2 small changes to the add-on Pier-Twitter so the "agoString" is > properly calculated for timezones with offsets other than 0 from UTC. I copied your changes to the repository. This looks cool. > I've posted the mcz file here: http://drop.io/Pier_Twitter_jtr_10 > Hopefully it's properly done as I've not used Monticello before other than > to load stuff into Squeak. Be sure to let me know if this should be handled > in a different manner in the future. Please directly commit to the repository at http://source.lukas-renggli.ch/pieraddons. The repository is public and makes it easy for everybody to load and test. Keep the good work rolling. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From dtrussardi at tiscali.it Mon May 18 15:22:28 2009 From: dtrussardi at tiscali.it (Dario Trussardi) Date: Mon, 18 May 2009 15:22:28 +0200 Subject: GemStone Compatibility References: <67628d690905171341k69a550afv480cad8686cfa37d@mail.gmail.com><213461296.927681242594250791.JavaMail.root@gir> <67628d690905171413i572cda2eg66cad59f30fd367e@mail.gmail.com> Message-ID: <14DC9131B6AD47E6889F0B32A7205151@istcamuno> Excuse for my delay and for my english, but i think MAAutoAccessor is very importan for " dinamic development ". I have a "database of descriptions " for define the base data of my application. For example descriptions about the items article, the contability data ecc... ecc. I don't know at begin, where i use this descriptions, but during the " life cicle of application" ( analisy, development, deployment, maintenance, integration.... ) it's very important use the reference to the database of description for define the "change". After this consideration, i think the MAAutoSelectorAccessor is a good solution for automatic instance varialble definition and accessor. When i do a reference to one description based on autoAccessor, the instanceVariable of the object is automatic update. In Gemstone maybe this support will can increase to manage object "compatibility" / "instance migration". Ciao, Dario >I think MAAutoAccessor is rarely useful, except when you want to > quickly prototype an application and generate inst-vars and accessors > automatically. After the initial prototyping phase it is hardly useful > to check for accessors and inst-vars on every read and write access. > > I removed it from the latest commit. If somebody really wants this > feature, it can be easily retrieved from the history and packaged > separately. > > Lukas > > On Sun, May 17, 2009 at 11:04 PM, Dale Henrichs > wrote: >> If a feature is there it will be used ... I made the changes in response >> to a bug report by a user. >> >> If you get rid of it, I can toss those changes and while I'm at it, I >> will audit the other GemStone-specific changes and get back to you with >> the ones that are still problematic. >> >> Dale >> ://www.iam.unibe.ch/mailman/listinfo/smallwiki From clover at pacbell.net Mon May 18 19:07:31 2009 From: clover at pacbell.net (Alex Roston) Date: Mon, 18 May 2009 10:07:31 -0700 Subject: The "Input is Invalid" Error In-Reply-To: <67628d690905161002pd8c946dr5fa1fe8b4f7061ca@mail.gmail.com> References: <4A0DA61A.3080505@pacbell.net> <67628d690905151051t5a6ad967vdec937c850849fa@mail.gmail.com> <4A0DD800.3030006@pacbell.net> <67628d690905160044n49292f0cyd50cd1565da8da13@mail.gmail.com> <4A0EE669.7060304@pacbell.net> <67628d690905161002pd8c946dr5fa1fe8b4f7061ca@mail.gmail.com> Message-ID: <4A1195D3.4040402@pacbell.net> Hi Lukas, I have sent a login, password, and URL to your private email address, so you can examine the exact Pier installation with which we are having troubles. Thanks, Alex Lukas Renggli wrote: > Thanks for sending the sample documents. > > I tried to reproduce with all of the following 36 possible combinations: > > - Pier 1.1.1 on Mac / latest Pier on Mac / Pier 1.1.1 on Linux > - WAKom / WAKomEncoded > - Safari 3 on Mac / IE 6 on Windows / FireFox 3 on Ubuntu Linux > - Microsoft Word 2008 on Mac / Open Office 2.4 on Ubuntu Linux > > I cannot reproduce the problem. > > Maybe you can try to temporarily replace > MAContainerComponent>>validate to see if there is something strange > going on with exceptions ... > > MAContainerComponent>>validate > self withContainersDo: [ :each | each doValidate ]. > ^ errors isEmpty > > Cheers, > Lukas > > On Sat, May 16, 2009 at 6:14 PM, Alex Roston wrote: > >> Hi Lukas, >> >> Thank you very much for your interest in this problem. I have sent two >> sample documents to your regular email address as they are too big for the >> mailing list. Both are .doc files generated by Open Office 2.4. >> I generated the error by simply copying and pasting the contents of the >> documents into Pier's edit box. (I'm using Firefox on Ubuntu Linux.) >> >> Sample_One does not work, while Sample_Two works just fine, and the only >> thing I did in Sample_Two was delete the long dash between the words >> "conclusion" and "whatever" and replace it with a period. So Magritte is >> not generating errors based on the encoding of the whole message, it's >> responding to specific characters (which I assume it can't read.) >> >> Thus my suggestion that the problem be solved by simply replacing those >> characters with a question mark or a box, plus perhaps a message to the >> user. >> >> As to your suggestion that I add some code... I'd love to, but you could >> put everything I know about Squeak in a thimble and have room left over. >> (I plan to work on Squeak in my spare moments, but it will be many >> months before I'm ready to contribute to a sophisticated project.) But >> I'll happily submit additions to the documentation as appropriate, and >> supply you with a continuing stream of bug reports as our development >> goes forward. >> >> Thanks, >> >> Alex >> >> >> >> >> Lukas Renggli wrote: >> >>> On Fri, May 15, 2009 at 11:00 PM, Alex Roston wrote: >>> >>> >>>> According to our sysadmin, "we're using the Wakom server adapter, plus >>>> the >>>> most recent version of Magritte, Seaside, and Pier from Lukas, which we >>>> updated may 14th." >>>> >>>> >>> Ok, I guess you are on Squeak/Pharo then. >>> >>> >>> >>>> The exact error message we're seeing read, "Contents: Invalid input >>>> given." >>>> I have included a screen shot, which I hope will not be rejected by the >>>> mailing list program. >>>> >>>> >>> Ok, that doesn't look too bad. This is a validation check of Magritte. >>> You can easily change the error message by adding a method like this: >>> >>> PRCase class>>descriptionDocumentYourPackage: aDescription >>> ^ aDescription kindErrorMessage: 'There was a problem reading your >>> input because your word processor is not set to UTF-8.' >>> >>> To be able to investigate the real cause of the problem I need some >>> more information. Could you send step by step introductions on how to >>> reproduce the problem. Maybe together with a Word document (I assume >>> this is the offender?) that I can copy from? >>> >>> Cheers, >>> Lukas >>> >>> >>> >> >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> >> > > > > From obi068 at gmail.com Mon May 18 20:19:08 2009 From: obi068 at gmail.com (Gerhard Obermann) Date: Mon, 18 May 2009 20:19:08 +0200 Subject: Remove Blog component Message-ID: <7b7d752d0905181119t2d5b1695ka1c8de92af9100d3@mail.gmail.com> Hi! How can I remove the blog component for one page! Cheers Gerhard -------------- next part -------------- An HTML attachment was scrubbed... URL: From girba at iam.unibe.ch Mon May 18 21:00:14 2009 From: girba at iam.unibe.ch (Tudor Girba) Date: Mon, 18 May 2009 21:00:14 +0200 Subject: Remove Blog component In-Reply-To: <7b7d752d0905181119t2d5b1695ka1c8de92af9100d3@mail.gmail.com> References: <7b7d752d0905181119t2d5b1695ka1c8de92af9100d3@mail.gmail.com> Message-ID: <0B30B8A3-06E0-467A-9E04-C70DABF6519F@iam.unibe.ch> Hi, I guess you mean the PostTicker component. If so, build a new environment that does not have the component embedded and in the settings of your page choose the new environment. Cheers, Doru On 18 May 2009, at 20:19, Gerhard Obermann wrote: > Hi! > > How can I remove the blog component for one page! > > Cheers > Gerhard > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com "It's not what we do that matters most, it's how we do it." From obi068 at gmail.com Mon May 18 21:11:55 2009 From: obi068 at gmail.com (Gerhard Obermann) Date: Mon, 18 May 2009 21:11:55 +0200 Subject: Remove Blog component In-Reply-To: <0B30B8A3-06E0-467A-9E04-C70DABF6519F@iam.unibe.ch> References: <7b7d752d0905181119t2d5b1695ka1c8de92af9100d3@mail.gmail.com> <0B30B8A3-06E0-467A-9E04-C70DABF6519F@iam.unibe.ch> Message-ID: <7b7d752d0905181211n483171eehe0fab558b2f6b7fe@mail.gmail.com> Yes I already thought to do it in that way but how to create a new environment! Cheers, gerhard On Mon, May 18, 2009 at 9:00 PM, Tudor Girba wrote: > Hi, > > I guess you mean the PostTicker component. If so, build a new environment > that does not have the component embedded and in the settings of your page > choose the new environment. > > Cheers, > Doru > > > > On 18 May 2009, at 20:19, Gerhard Obermann wrote: > > Hi! >> >> How can I remove the blog component for one page! >> >> Cheers >> Gerhard >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> > > -- > www.tudorgirba.com > > "It's not what we do that matters most, it's how we do it." > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From girba at iam.unibe.ch Mon May 18 21:39:04 2009 From: girba at iam.unibe.ch (Tudor Girba) Date: Mon, 18 May 2009 21:39:04 +0200 Subject: Remove Blog component In-Reply-To: <7b7d752d0905181211n483171eehe0fab558b2f6b7fe@mail.gmail.com> References: <7b7d752d0905181119t2d5b1695ka1c8de92af9100d3@mail.gmail.com> <0B30B8A3-06E0-467A-9E04-C70DABF6519F@iam.unibe.ch> <7b7d752d0905181211n483171eehe0fab558b2f6b7fe@mail.gmail.com> Message-ID: Hi, Add a page called MySpecialEnvironment to the root. Copy in there the contents from the page found in /environment. Add another page called MyPageWithSpecialEnvironment and in the Settings point the environment to be MySpecialEnvironment. Cheers, Doru On 18 May 2009, at 21:11, Gerhard Obermann wrote: > Yes I already thought to do it in that way but how to create a new > environment! > > Cheers, > gerhard > > > On Mon, May 18, 2009 at 9:00 PM, Tudor Girba > wrote: > Hi, > > I guess you mean the PostTicker component. If so, build a new > environment that does not have the component embedded and in the > settings of your page choose the new environment. > > Cheers, > Doru > > > > On 18 May 2009, at 20:19, Gerhard Obermann wrote: > > Hi! > > How can I remove the blog component for one page! > > Cheers > Gerhard > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > -- > www.tudorgirba.com > > "It's not what we do that matters most, it's how we do it." > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com "Every thing has its own flow." From marianopeck at gmail.com Tue May 19 02:49:44 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Mon, 18 May 2009 21:49:44 -0300 Subject: Remove Blog component In-Reply-To: References: <7b7d752d0905181119t2d5b1695ka1c8de92af9100d3@mail.gmail.com> <0B30B8A3-06E0-467A-9E04-C70DABF6519F@iam.unibe.ch> <7b7d752d0905181211n483171eehe0fab558b2f6b7fe@mail.gmail.com> Message-ID: On Mon, May 18, 2009 at 4:39 PM, Tudor Girba wrote: > Hi, > > Add a page called MySpecialEnvironment to the root. Copy in there the > contents from the page found in /environment. Add another page called > MyPageWithSpecialEnvironment and in the Settings point the environment to be > MySpecialEnvironment. > It was useful for me and I think could be for someone else coming later to this list. What about putting this question and answer in http://www.piercms.com/doc/faq Sorry, I don't have user/pass. Cheers, Mariano > > Cheers, > Doru > > On 18 May 2009, at 21:11, Gerhard Obermann wrote: > > Yes I already thought to do it in that way but how to create a new >> environment! >> >> Cheers, >> gerhard >> >> >> On Mon, May 18, 2009 at 9:00 PM, Tudor Girba wrote: >> Hi, >> >> I guess you mean the PostTicker component. If so, build a new environment >> that does not have the component embedded and in the settings of your page >> choose the new environment. >> >> Cheers, >> Doru >> >> >> >> On 18 May 2009, at 20:19, Gerhard Obermann wrote: >> >> Hi! >> >> How can I remove the blog component for one page! >> >> Cheers >> Gerhard >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> >> -- >> www.tudorgirba.com >> >> "It's not what we do that matters most, it's how we do it." >> >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> > > -- > www.tudorgirba.com > > "Every thing has its own flow." > > > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From norbert at hartl.name Tue May 19 19:58:52 2009 From: norbert at hartl.name (Norbert Hartl) Date: Tue, 19 May 2009 19:58:52 +0200 Subject: Pier blog and permissions Message-ID: <1242755932.5121.106.camel@cineflux> Hi, I was totally confused about my blog today. I always expected that people can comment on blog posts. Having a look today first showed that there was no entry form for entering a comment. I started to fiddle around with the permissions on the blog page but this was kinda strange. As soon as I added the "Add commment" permission to others a link "add" was added at the bottom beside login and view. Clicking on the link opened the normal add command that would let me add post, component,... Removing the permission again removed the link again. I know this sounds strange and I'm also sure that it is probably not what really happened. Now it is so that only the first post has the comment add form and no other post. Well, it is the only one in this month so it could also be that. Aren't all blog post supposed to be commentable? thanks, Norbert From cdrick65 at gmail.com Tue May 19 20:10:15 2009 From: cdrick65 at gmail.com (=?UTF-8?B?Q8OpZHJpY2sgQsOpbGVy?=) Date: Tue, 19 May 2009 20:10:15 +0200 Subject: Pier blog and permissions In-Reply-To: <1242755932.5121.106.camel@cineflux> References: <1242755932.5121.106.camel@cineflux> Message-ID: uhm, not sure but blogs comments have a validity time and maybe this time is over. You should be able to change that parameter in your blog settings. hth, 2009/5/19 Norbert Hartl : > Hi, > > I was totally confused about my blog today. I always > expected that people can comment on blog posts. Having > a look today first showed that there was no entry form > for entering a comment. > I started to fiddle around with the permissions on the > blog page but this was kinda strange. As soon as I added > the "Add commment" permission to others a link "add" > was added at the bottom beside login and view. Clicking > on the link opened the normal add command that would > let me add post, component,... > Removing the permission again removed the link again. I > know this sounds strange and I'm also sure that it is > probably not what really happened. > > Now it is so that only the first post has the comment > add form and no other post. Well, it is the only one > in this month so it could also be that. Aren't all blog > post supposed to be commentable? > > thanks, > > Norbert > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- C?drick From girba at iam.unibe.ch Tue May 19 20:42:43 2009 From: girba at iam.unibe.ch (Tudor Girba) Date: Tue, 19 May 2009 20:42:43 +0200 Subject: Pier blog and permissions In-Reply-To: References: <1242755932.5121.106.camel@cineflux> Message-ID: Indeed, it is most probably the timeout. You can set the comment timeout by editing (not via settings) the parameters blog. By default it is 14:00:00:00 which means 2 weeks. Cheers, Doru On 19 May 2009, at 20:10, C?drick B?ler wrote: > uhm, not sure but blogs comments have a validity time and maybe this > time is over. > You should be able to change that parameter in your blog settings. > > hth, > > 2009/5/19 Norbert Hartl : >> Hi, >> >> I was totally confused about my blog today. I always >> expected that people can comment on blog posts. Having >> a look today first showed that there was no entry form >> for entering a comment. >> I started to fiddle around with the permissions on the >> blog page but this was kinda strange. As soon as I added >> the "Add commment" permission to others a link "add" >> was added at the bottom beside login and view. Clicking >> on the link opened the normal add command that would >> let me add post, component,... >> Removing the permission again removed the link again. I >> know this sounds strange and I'm also sure that it is >> probably not what really happened. >> >> Now it is so that only the first post has the comment >> add form and no other post. Well, it is the only one >> in this month so it could also be that. Aren't all blog >> post supposed to be commentable? >> >> thanks, >> >> Norbert >> >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> > > > > -- > C?drick > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- www.tudorgirba.com "Relationships are of two kinds: those we choose and those that happen. They both matter." From norbert at hartl.name Tue May 19 23:51:55 2009 From: norbert at hartl.name (Norbert Hartl) Date: Tue, 19 May 2009 23:51:55 +0200 Subject: Pier blog and permissions In-Reply-To: References: <1242755932.5121.106.camel@cineflux> Message-ID: <1242769915.5121.110.camel@cineflux> On Tue, 2009-05-19 at 20:10 +0200, C?drick B?ler wrote: > uhm, not sure but blogs comments have a validity time and maybe this > time is over. > You should be able to change that parameter in your blog settings. > Thanks. I didn't know that. Norbert > hth, > > 2009/5/19 Norbert Hartl : > > Hi, > > > > I was totally confused about my blog today. I always > > expected that people can comment on blog posts. Having > > a look today first showed that there was no entry form > > for entering a comment. > > I started to fiddle around with the permissions on the > > blog page but this was kinda strange. As soon as I added > > the "Add commment" permission to others a link "add" > > was added at the bottom beside login and view. Clicking > > on the link opened the normal add command that would > > let me add post, component,... > > Removing the permission again removed the link again. I > > know this sounds strange and I'm also sure that it is > > probably not what really happened. > > > > Now it is so that only the first post has the comment > > add form and no other post. Well, it is the only one > > in this month so it could also be that. Aren't all blog > > post supposed to be commentable? > > > > thanks, > > > > Norbert > > > > _______________________________________________ > > Magritte, Pier and Related Tools ... > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > > > > -- > C?drick > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From norbert at hartl.name Tue May 19 23:52:54 2009 From: norbert at hartl.name (Norbert Hartl) Date: Tue, 19 May 2009 23:52:54 +0200 Subject: Pier blog and permissions In-Reply-To: References: <1242755932.5121.106.camel@cineflux> Message-ID: <1242769974.5121.111.camel@cineflux> On Tue, 2009-05-19 at 20:42 +0200, Tudor Girba wrote: > Indeed, it is most probably the timeout. You can set the comment > timeout by editing (not via settings) the parameters blog. By default > it is 14:00:00:00 which means 2 weeks. > Thanks, too. Is there an easy answer why I had the "Add" link shown after having added the "Add Comment" permission on the blog? Norbert > Cheers, > Doru > > > On 19 May 2009, at 20:10, C?drick B?ler wrote: > > > uhm, not sure but blogs comments have a validity time and maybe this > > time is over. > > You should be able to change that parameter in your blog settings. > > > > hth, > > > > 2009/5/19 Norbert Hartl : > >> Hi, > >> > >> I was totally confused about my blog today. I always > >> expected that people can comment on blog posts. Having > >> a look today first showed that there was no entry form > >> for entering a comment. > >> I started to fiddle around with the permissions on the > >> blog page but this was kinda strange. As soon as I added > >> the "Add commment" permission to others a link "add" > >> was added at the bottom beside login and view. Clicking > >> on the link opened the normal add command that would > >> let me add post, component,... > >> Removing the permission again removed the link again. I > >> know this sounds strange and I'm also sure that it is > >> probably not what really happened. > >> > >> Now it is so that only the first post has the comment > >> add form and no other post. Well, it is the only one > >> in this month so it could also be that. Aren't all blog > >> post supposed to be commentable? > >> > >> thanks, > >> > >> Norbert > >> > >> _______________________________________________ > >> Magritte, Pier and Related Tools ... > >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > >> > > > > > > > > -- > > C?drick > > > > _______________________________________________ > > Magritte, Pier and Related Tools ... > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > > -- > www.tudorgirba.com > > "Relationships are of two kinds: those we choose and those that > happen. They both matter." > > > > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From norbert at hartl.name Wed May 20 07:51:46 2009 From: norbert at hartl.name (Norbert Hartl) Date: Wed, 20 May 2009 07:51:46 +0200 Subject: google analytics and canonical links Message-ID: <1242798706.5121.115.camel@cineflux> I have added google analytics to my site. I configured it to strip _s, _n and _k from the url. On every page there is the canonical url embedded. In my statistics there is sometimes still the link counter of an url included so there appears /blog?15= /blog?13= and so on. Does anybody know how to get this right? thanks, Norbert From renggli at gmail.com Wed May 20 08:22:37 2009 From: renggli at gmail.com (Lukas Renggli) Date: Wed, 20 May 2009 08:22:37 +0200 Subject: google analytics and canonical links In-Reply-To: <1242798706.5121.115.camel@cineflux> References: <1242798706.5121.115.camel@cineflux> Message-ID: <67628d690905192322v62bcf950q3903c043d6e5cfd7@mail.gmail.com> There is a tutorial at . It removes all parameters, not just _s, _n and _k. Cheers, Lukas On Wed, May 20, 2009 at 7:51 AM, Norbert Hartl wrote: > I have added google analytics to my site. I configured > it to strip _s, _n and _k from the url. On every page > there is the canonical url embedded. > In my statistics there is sometimes still the link counter > of an url included so there appears > > /blog?15= > /blog?13= > > and so on. > > Does anybody know how to get this right? > > thanks, > > Norbert > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli http://www.lukas-renggli.ch From norbert at hartl.name Wed May 20 08:25:08 2009 From: norbert at hartl.name (Norbert Hartl) Date: Wed, 20 May 2009 08:25:08 +0200 Subject: google analytics and canonical links In-Reply-To: <67628d690905192322v62bcf950q3903c043d6e5cfd7@mail.gmail.com> References: <1242798706.5121.115.camel@cineflux> <67628d690905192322v62bcf950q3903c043d6e5cfd7@mail.gmail.com> Message-ID: <1242800708.5121.116.camel@cineflux> On Wed, 2009-05-20 at 08:22 +0200, Lukas Renggli wrote: > There is a tutorial at . > It removes all parameters, not just _s, _n and _k. > thanks, Norbert > Cheers, > Lukas > > On Wed, May 20, 2009 at 7:51 AM, Norbert Hartl wrote: > > I have added google analytics to my site. I configured > > it to strip _s, _n and _k from the url. On every page > > there is the canonical url embedded. > > In my statistics there is sometimes still the link counter > > of an url included so there appears > > > > /blog?15= > > /blog?13= > > > > and so on. > > > > Does anybody know how to get this right? > > > > thanks, > > > > Norbert > > > > _______________________________________________ > > Magritte, Pier and Related Tools ... > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > > > From norbert at hartl.name Wed May 20 08:41:11 2009 From: norbert at hartl.name (Norbert Hartl) Date: Wed, 20 May 2009 08:41:11 +0200 Subject: google analytics and canonical links In-Reply-To: <67628d690905192322v62bcf950q3903c043d6e5cfd7@mail.gmail.com> References: <1242798706.5121.115.camel@cineflux> <67628d690905192322v62bcf950q3903c043d6e5cfd7@mail.gmail.com> Message-ID: <1242801671.5121.120.camel@cineflux> On Wed, 2009-05-20 at 08:22 +0200, Lukas Renggli wrote: > There is a tutorial at . > It removes all parameters, not just _s, _n and _k. > You have a typo in the tutorial. The regex for easier copy-paste is missing an escape It should be ^([^?]*)\?.*$ instead of ^([^?]*)?.*$ In the screenshot it is right. Norbert > Cheers, > Lukas > > On Wed, May 20, 2009 at 7:51 AM, Norbert Hartl wrote: > > I have added google analytics to my site. I configured > > it to strip _s, _n and _k from the url. On every page > > there is the canonical url embedded. > > In my statistics there is sometimes still the link counter > > of an url included so there appears > > > > /blog?15= > > /blog?13= > > > > and so on. > > > > Does anybody know how to get this right? > > > > thanks, > > > > Norbert > > > > _______________________________________________ > > Magritte, Pier and Related Tools ... > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > > > From renggli at gmail.com Wed May 20 09:07:42 2009 From: renggli at gmail.com (Lukas Renggli) Date: Wed, 20 May 2009 09:07:42 +0200 Subject: google analytics and canonical links In-Reply-To: <1242801671.5121.120.camel@cineflux> References: <1242798706.5121.115.camel@cineflux> <67628d690905192322v62bcf950q3903c043d6e5cfd7@mail.gmail.com> <1242801671.5121.120.camel@cineflux> Message-ID: <67628d690905200007u7fb865dao282a427d64d5dac1@mail.gmail.com> True, thanks for pointing out. Cheers, Lukas On Wed, May 20, 2009 at 8:41 AM, Norbert Hartl wrote: > On Wed, 2009-05-20 at 08:22 +0200, Lukas Renggli wrote: >> There is a tutorial at . >> It removes all parameters, not just _s, _n and _k. >> > You have a typo in the tutorial. The regex for easier copy-paste > is missing an escape > > It should be > > ^([^?]*)\?.*$ > > instead of > > ^([^?]*)?.*$ > > In the screenshot it is right. > > Norbert > >> Cheers, >> Lukas >> >> On Wed, May 20, 2009 at 7:51 AM, Norbert Hartl wrote: >> > I have added google analytics to my site. I configured >> > it to strip _s, _n and _k from the url. On every page >> > there is the canonical url embedded. >> > In my statistics there is sometimes still the link counter >> > of an url included so there appears >> > >> > /blog?15= >> > /blog?13= >> > >> > and so on. >> > >> > Does anybody know how to get this right? >> > >> > thanks, >> > >> > Norbert >> > >> > _______________________________________________ >> > Magritte, Pier and Related Tools ... >> > https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> > >> >> >> > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli http://www.lukas-renggli.ch From johnmci at smalltalkconsulting.com Thu May 21 18:13:59 2009 From: johnmci at smalltalkconsulting.com (John M McIntosh) Date: Thu, 21 May 2009 09:13:59 -0700 Subject: WikiServer for the iPhone goes Live Message-ID: <1C0B2C36-3F9D-4AD4-8639-7A59F3EF3279@smalltalkconsulting.com> Well after weeks of delay Apple silently put WikiServer up for sale on the App Store yesterday. http://itunes.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=312622071&mt=8 No doubt I will break out the Champagne tonight. http://www.mobilewikiserver.com -- = = = ======================================================================== John M. McIntosh Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ======================================================================== From johnmci at smalltalkconsulting.com Sat May 23 01:19:08 2009 From: johnmci at smalltalkconsulting.com (John M McIntosh) Date: Fri, 22 May 2009 16:19:08 -0700 Subject: WikiServer for the iPhone goes Live In-Reply-To: <1C0B2C36-3F9D-4AD4-8639-7A59F3EF3279@smalltalkconsulting.com> References: <1C0B2C36-3F9D-4AD4-8639-7A59F3EF3279@smalltalkconsulting.com> Message-ID: Further to this I have a number of coupons (30) that can be redeemed for a free 4 week trial in case some people would like to write a review for the Store. If you would like to write a review please email me, not the list, and we'll see about getting you the magic number. On 21-May-09, at 9:13 AM, John M McIntosh wrote: > Well after weeks of delay Apple silently put WikiServer up for sale > on the App Store yesterday. > > http://itunes.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=312622071&mt=8 > > No doubt I will break out the Champagne tonight. > > http://www.mobilewikiserver.com > -- -- = = = ======================================================================== John M. McIntosh Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ======================================================================== From sean at monkeysnatchbanana.com Sat May 23 05:03:25 2009 From: sean at monkeysnatchbanana.com (Sean Allen) Date: Fri, 22 May 2009 23:03:25 -0400 Subject: blog archive oddness... Message-ID: <3157F0AC-F86C-4DEE-864B-2DFD7C037130@monkeysnatchbanana.com> playing around again with pier. new official image i downloaded a couple days ago... playing around with the blog. i can add new posts but they dont appear in the blog archive until logged in, i visit the blog archive ( environment/blogarchive ) what am i doing wrong? From norbert at hartl.name Sat May 23 08:21:30 2009 From: norbert at hartl.name (Norbert Hartl) Date: Sat, 23 May 2009 08:21:30 +0200 Subject: blog archive oddness... In-Reply-To: <3157F0AC-F86C-4DEE-864B-2DFD7C037130@monkeysnatchbanana.com> References: <3157F0AC-F86C-4DEE-864B-2DFD7C037130@monkeysnatchbanana.com> Message-ID: <1243059690.17256.4.camel@cineflux> On Fri, 2009-05-22 at 23:03 -0400, Sean Allen wrote: > playing around again with pier. > > new official image i downloaded a couple days ago... > > playing around with the blog. > i can add new posts but they dont appear in the blog archive until > logged in, > i visit the blog archive ( environment/blogarchive ) > > what am i doing wrong? > Did you set a public date? Blog posts only show up if there is one set. Norbert From sean at monkeysnatchbanana.com Sat May 23 14:06:39 2009 From: sean at monkeysnatchbanana.com (Sean Allen) Date: Sat, 23 May 2009 08:06:39 -0400 Subject: blog archive oddness... In-Reply-To: <1243059690.17256.4.camel@cineflux> References: <3157F0AC-F86C-4DEE-864B-2DFD7C037130@monkeysnatchbanana.com> <1243059690.17256.4.camel@cineflux> Message-ID: <0C3254A1-B29E-469E-8CEA-207F78A73730@monkeysnatchbanana.com> On May 23, 2009, at 2:21 AM, Norbert Hartl wrote: > On Fri, 2009-05-22 at 23:03 -0400, Sean Allen wrote: >> playing around again with pier. >> >> new official image i downloaded a couple days ago... >> >> playing around with the blog. >> i can add new posts but they dont appear in the blog archive until >> logged in, >> i visit the blog archive ( environment/blogarchive ) >> >> what am i doing wrong? >> > Did you set a public date? Blog posts only show up if there > is one set. Publication date? Yes. The blog entry is listed in the blog, it just doesnt show up in the archive until i visit environment/blogarchive From girba at iam.unibe.ch Sat May 23 14:57:17 2009 From: girba at iam.unibe.ch (Tudor Girba) Date: Sat, 23 May 2009 14:57:17 +0200 Subject: blog archive oddness... In-Reply-To: <0C3254A1-B29E-469E-8CEA-207F78A73730@monkeysnatchbanana.com> References: <3157F0AC-F86C-4DEE-864B-2DFD7C037130@monkeysnatchbanana.com> <1243059690.17256.4.camel@cineflux> <0C3254A1-B29E-469E-8CEA-207F78A73730@monkeysnatchbanana.com> Message-ID: Hi, It could be because the blog archive refreshes only for a new session. Did you try with a new session? Cheers, Doru On 23 May 2009, at 14:06, Sean Allen wrote: > > On May 23, 2009, at 2:21 AM, Norbert Hartl wrote: > >> On Fri, 2009-05-22 at 23:03 -0400, Sean Allen wrote: >>> playing around again with pier. >>> >>> new official image i downloaded a couple days ago... >>> >>> playing around with the blog. >>> i can add new posts but they dont appear in the blog archive until >>> logged in, >>> i visit the blog archive ( environment/blogarchive ) >>> >>> what am i doing wrong? >>> >> Did you set a public date? Blog posts only show up if there >> is one set. > > Publication date? Yes. > > The blog entry is listed in the blog, it just doesnt show up in the > archive > until i visit environment/blogarchive > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com "No matter how many recipes we'll know, we'll still value a chef." From p3anoman at gmail.com Sat May 23 15:04:15 2009 From: p3anoman at gmail.com (John McKeon) Date: Sat, 23 May 2009 09:04:15 -0400 Subject: blog archive oddness... In-Reply-To: <0C3254A1-B29E-469E-8CEA-207F78A73730@monkeysnatchbanana.com> References: <3157F0AC-F86C-4DEE-864B-2DFD7C037130@monkeysnatchbanana.com> <1243059690.17256.4.camel@cineflux> <0C3254A1-B29E-469E-8CEA-207F78A73730@monkeysnatchbanana.com> Message-ID: <40f637ec0905230604w40d097c0nf18fccc3ddf00b63@mail.gmail.com> What about the rights? after you login, and go to environment/blogarchive, click the "change other" command and make sure "view" is set On Sat, May 23, 2009 at 8:06 AM, Sean Allen wrote: > > On May 23, 2009, at 2:21 AM, Norbert Hartl wrote: > > On Fri, 2009-05-22 at 23:03 -0400, Sean Allen wrote: >> >>> playing around again with pier. >>> >>> new official image i downloaded a couple days ago... >>> >>> playing around with the blog. >>> i can add new posts but they dont appear in the blog archive until >>> logged in, >>> i visit the blog archive ( environment/blogarchive ) >>> >>> what am i doing wrong? >>> >>> Did you set a public date? Blog posts only show up if there >> is one set. >> > > Publication date? Yes. > > The blog entry is listed in the blog, it just doesnt show up in the archive > until i visit environment/blogarchive > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sean at monkeysnatchbanana.com Sat May 23 15:19:32 2009 From: sean at monkeysnatchbanana.com (Sean Allen) Date: Sat, 23 May 2009 09:19:32 -0400 Subject: pharo to glass: moving data question... Message-ID: i want to start playing around with putting together a site in pharo on my laptop and then when i have it mostly completed, moving it over to a GLASS installation. i've scanned back through the list since i first signed up last year ( and found numerous interesting tidbits i had missed ), but i can't find anything on this: if i want to move an existing pier site out of a pharo/squeak image and into glass, how do i do that? i assume it would be using monticello. i'm not sure though, how much i need to move. i'm sure there is a simple answer to this, but i still haven't really used monticello much as i have been able to get by without using it yet. From sean at monkeysnatchbanana.com Sat May 23 15:23:08 2009 From: sean at monkeysnatchbanana.com (Sean Allen) Date: Sat, 23 May 2009 09:23:08 -0400 Subject: blog archive oddness... In-Reply-To: References: <3157F0AC-F86C-4DEE-864B-2DFD7C037130@monkeysnatchbanana.com> <1243059690.17256.4.camel@cineflux> <0C3254A1-B29E-469E-8CEA-207F78A73730@monkeysnatchbanana.com> Message-ID: <2F882DE8-F4E4-4D71-88FB-83735CCCCA41@monkeysnatchbanana.com> On May 23, 2009, at 8:57 AM, Tudor Girba wrote: > Hi, > > It could be because the blog archive refreshes only for a new > session. Did you try with a new session? > And that would be the answer. Seems very counter intuitive. How can I get the blog archive to update in the same session? From renggli at gmail.com Sat May 23 16:28:25 2009 From: renggli at gmail.com (Lukas Renggli) Date: Sat, 23 May 2009 16:28:25 +0200 Subject: blog archive oddness... In-Reply-To: <2F882DE8-F4E4-4D71-88FB-83735CCCCA41@monkeysnatchbanana.com> References: <3157F0AC-F86C-4DEE-864B-2DFD7C037130@monkeysnatchbanana.com> <1243059690.17256.4.camel@cineflux> <0C3254A1-B29E-469E-8CEA-207F78A73730@monkeysnatchbanana.com> <2F882DE8-F4E4-4D71-88FB-83735CCCCA41@monkeysnatchbanana.com> Message-ID: <67628d690905230728w5e1d096dm91ef21433ca5c137@mail.gmail.com> > And that would be the answer. Seems very counter intuitive. How can I get the blog archive to update > in the same session? Building the blog archive, related posts, tag cloud, etc. is a potentially expensive operation. Pier only calculates this information once, and assumes that most people are visitors, not editors. For my own use this scheme works perfectly well. If you think this is a bug, please file an issue or commit a fix. Cheers, Lukas > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli http://www.lukas-renggli.ch From dale.henrichs at gemstone.com Sat May 23 17:02:31 2009 From: dale.henrichs at gemstone.com (Dale Henrichs) Date: Sat, 23 May 2009 08:02:31 -0700 (PDT) Subject: pharo to glass: moving data question... In-Reply-To: <457278301.1019781243090518558.JavaMail.root@gir> Message-ID: <392823927.1019821243090951565.JavaMail.root@gir> SSean, Use SIXX. During SIXX testing I was able to move a Pier kernel from Squeak to GemStone. If you run into issues, I will be very interested to fix them, since at the moment I think SIXX is the best alternative. Dale ----- "Sean Allen" wrote: | i want to start playing around with putting together a site in pharo | | on my laptop and then when i have it mostly completed, moving it over | | to a GLASS installation. | i've scanned back through the list since i first signed up last year | | ( and found numerous interesting tidbits i had missed ), but i can't | | find anything on this: | | if i want to move an existing pier site out of a pharo/squeak image | and into glass, how do i do that? i assume it would be using | monticello. i'm not sure though, how much i need to move. i'm sure | there is a simple answer to this, but i still haven't really used | monticello much as i have been able to get by without using it yet. | | | _______________________________________________ | Magritte, Pier and Related Tools ... | https://www.iam.unibe.ch/mailman/listinfo/smallwiki From sean at monkeysnatchbanana.com Sat May 23 18:01:02 2009 From: sean at monkeysnatchbanana.com (Sean Allen) Date: Sat, 23 May 2009 12:01:02 -0400 Subject: pharo to glass: moving data question... In-Reply-To: <392823927.1019821243090951565.JavaMail.root@gir> References: <392823927.1019821243090951565.JavaMail.root@gir> Message-ID: <2EB6BAEE-4826-41FB-B4F2-ED4E9A7C6B9B@monkeysnatchbanana.com> I'll add SIXX on to my ever growing list of things to learn and if I have issues, will be in touch. On May 23, 2009, at 11:02 AM, Dale Henrichs wrote: > SSean, > > Use SIXX. During SIXX testing I was able to move a Pier kernel from > Squeak to GemStone. > > If you run into issues, I will be very interested to fix them, since > at the moment I think SIXX is the best alternative. > > Dale > > ----- "Sean Allen" wrote: > > | i want to start playing around with putting together a site in pharo > | > | on my laptop and then when i have it mostly completed, moving it > over > | > | to a GLASS installation. > | i've scanned back through the list since i first signed up last year > | > | ( and found numerous interesting tidbits i had missed ), but i can't > | > | find anything on this: > | > | if i want to move an existing pier site out of a pharo/squeak image > | and into glass, how do i do that? i assume it would be using > | monticello. i'm not sure though, how much i need to move. i'm sure > | there is a simple answer to this, but i still haven't really used > | monticello much as i have been able to get by without using it yet. > | > | > | _______________________________________________ > | Magritte, Pier and Related Tools ... > | https://www.iam.unibe.ch/mailman/listinfo/smallwiki > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From marianopeck at gmail.com Sat May 23 22:04:55 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Sat, 23 May 2009 17:04:55 -0300 Subject: pharo to glass: moving data question... In-Reply-To: <2EB6BAEE-4826-41FB-B4F2-ED4E9A7C6B9B@monkeysnatchbanana.com> References: <392823927.1019821243090951565.JavaMail.root@gir> <2EB6BAEE-4826-41FB-B4F2-ED4E9A7C6B9B@monkeysnatchbanana.com> Message-ID: Pier (in 1.1.1 I think) has it's own Importer/Exporter. I don't know if it works on Gemstone, but if this is the case is really easy. I do this when move a pier site from one image to another. Cheers, Mariano On Sat, May 23, 2009 at 1:01 PM, Sean Allen wrote: > I'll add SIXX on to my ever growing list of things to learn and if I have > issues, will be in touch. > > > On May 23, 2009, at 11:02 AM, Dale Henrichs wrote: > > SSean, >> >> Use SIXX. During SIXX testing I was able to move a Pier kernel from Squeak >> to GemStone. >> >> If you run into issues, I will be very interested to fix them, since at >> the moment I think SIXX is the best alternative. >> >> Dale >> >> ----- "Sean Allen" wrote: >> >> | i want to start playing around with putting together a site in pharo >> | >> | on my laptop and then when i have it mostly completed, moving it over >> | >> | to a GLASS installation. >> | i've scanned back through the list since i first signed up last year >> | >> | ( and found numerous interesting tidbits i had missed ), but i can't >> | >> | find anything on this: >> | >> | if i want to move an existing pier site out of a pharo/squeak image >> | and into glass, how do i do that? i assume it would be using >> | monticello. i'm not sure though, how much i need to move. i'm sure >> | there is a simple answer to this, but i still haven't really used >> | monticello much as i have been able to get by without using it yet. >> | >> | >> | _______________________________________________ >> | Magritte, Pier and Related Tools ... >> | https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sean at monkeysnatchbanana.com Sat May 23 22:18:51 2009 From: sean at monkeysnatchbanana.com (Sean Allen) Date: Sat, 23 May 2009 16:18:51 -0400 Subject: blog archive oddness... In-Reply-To: <67628d690905230728w5e1d096dm91ef21433ca5c137@mail.gmail.com> References: <3157F0AC-F86C-4DEE-864B-2DFD7C037130@monkeysnatchbanana.com> <1243059690.17256.4.camel@cineflux> <0C3254A1-B29E-469E-8CEA-207F78A73730@monkeysnatchbanana.com> <2F882DE8-F4E4-4D71-88FB-83735CCCCA41@monkeysnatchbanana.com> <67628d690905230728w5e1d096dm91ef21433ca5c137@mail.gmail.com> Message-ID: <24545FD7-DAEE-4723-93D9-A3A245120901@monkeysnatchbanana.com> On May 23, 2009, at 10:28 AM, Lukas Renggli wrote: >> And that would be the answer. Seems very counter intuitive. How can >> I get the blog archive to update >> in the same session? > > Building the blog archive, related posts, tag cloud, etc. is a > potentially expensive operation. Pier only calculates this information > once, and assumes that most people are visitors, not editors. For my > own use this scheme works perfectly well. If you think this is a bug, > please file an issue or commit a fix. Given your explanation, any fix would seem to be worse than the issue for installations with large amounts of data. From johnmci at smalltalkconsulting.com Sat May 23 22:31:32 2009 From: johnmci at smalltalkconsulting.com (John McIntosh) Date: Sat, 23 May 2009 13:31:32 -0700 Subject: pharo to glass: moving data question... In-Reply-To: References: <392823927.1019821243090951565.JavaMail.root@gir> <2EB6BAEE-4826-41FB-B4F2-ED4E9A7C6B9B@monkeysnatchbanana.com> Message-ID: <7158c5640905231331x3327c3dfnc3b751cf4b15fa54@mail.gmail.com> On Sat, May 23, 2009 at 1:04 PM, Mariano Martinez Peck < marianopeck at gmail.com> wrote: > Pier (in 1.1.1 I think) has it's own Importer/Exporter. I don't know if it > works on Gemstone, but if this is the case is really easy. I do this when > move a pier site from one image to another. > > Cheers, > I don't think it handles the "files" directory, there is a comment saying copy by hand. However with a bit of code you could zip it in squeak. Oddly Squeak doesn't handle the ability to compress a directory, so here is some code. I note the unixFileAttributes: is needed to set the directory member with the proper permissions, otherwise on unix or os-x it unzips a directory as rw-rw-rw- obviously a problem, and a bug. addCompleteDirectory: aLocalURI "adds a complete directory structure to the zip archive" |directory slash dirLocalPath| directory := FileDirectory on: aLocalURI. "construct the directory name" slash := directory slash. dirLocalPath := directory localName, slash. self addDirectoryDescend: directory relativePath: dirLocalPath. addDirectory: aFileName as: anotherFileName | newMember | newMember := self memberClass newFromDirectory: aFileName. newMember unixFileAttributes: 8r040755. self addMember: newMember. newMember localFileName: anotherFileName. ^newMember addDirectoryDescend: directory relativePath: dirLocalPath |slash| "self break." slash := directory slash. "add the files" self addDirectory: directory pathName as: dirLocalPath. directory fileNames do: [:fileName| "self break." self addFile: directory pathName, slash, fileName as: dirLocalPath, fileName ]. directory directoryNames do: [:subDirName| self addDirectoryDescend: (directory directoryNamed: subDirName) relativePath: dirLocalPath, subDirName, slash. ]. -- =========================================================================== John M. McIntosh Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com =========================================================================== -------------- next part -------------- An HTML attachment was scrubbed... URL: From norbert at hartl.name Sun May 24 09:47:36 2009 From: norbert at hartl.name (Norbert Hartl) Date: Sun, 24 May 2009 09:47:36 +0200 Subject: Blog management Message-ID: <1243151256.17256.22.camel@cineflux> I'm using the blog on my site for everything I like to add there. But then I would like to subscribe my blog in planet smalltalk. For such meta blogs the mixture of things is not wanted. So how would you solve this? I could have a blog per topic or at least one for things being smalltalk. Then I only need to tweak post ticker component to include more than one blog. I would rather use the opposite approach. I like to put everything in one blog but have the ability to filter the posts by tag or anything else. This might make the subscription Url more ugly. What do you think? Norbert From renggli at gmail.com Sun May 24 09:52:11 2009 From: renggli at gmail.com (Lukas Renggli) Date: Sun, 24 May 2009 09:52:11 +0200 Subject: Blog management In-Reply-To: <1243151256.17256.22.camel@cineflux> References: <1243151256.17256.22.camel@cineflux> Message-ID: <67628d690905240052p2e8c621dybe047df7fcc4287b@mail.gmail.com> > I would rather use the opposite approach. I like to put > everything in one blog but have the ability to filter > the posts by tag or anything else. This might make the > subscription Url more ugly. I would go for this approach. Actually the different blog widgets (Archive, Tags, Related) already implements such a filter, it is just not possible to subscribe to such a filtered view yet. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From sean at monkeysnatchbanana.com Sun May 24 16:49:28 2009 From: sean at monkeysnatchbanana.com (Sean Allen) Date: Sun, 24 May 2009 10:49:28 -0400 Subject: pier addons Message-ID: <017C8F25-48B3-4E8E-A6FC-93FC56BD2862@monkeysnatchbanana.com> is there anywhere where you can get a quick summary of the different add ons? a few are detailed on squeaksource but not all of them. loading in from monticello and checking them out is always an option, but i wanted to see if there was a quicker route. From dale.henrichs at gemstone.com Sun May 24 17:22:58 2009 From: dale.henrichs at gemstone.com (Dale Henrichs) Date: Sun, 24 May 2009 08:22:58 -0700 (PDT) Subject: pharo to glass: moving data question... In-Reply-To: <2060510619.1022951243178549277.JavaMail.root@gir> Message-ID: <1419124045.1022971243178578867.JavaMail.root@gir> Mariano, I haven't had a chance to look at the details of exporter/importer, but I assume that it is based on squeak-based serialization. At the moment SIXX is probably a better option for moving data to GemStone. Dale ----- "Mariano Martinez Peck" wrote: | Pier (in 1.1.1 I think) has it's own Importer/Exporter. I don't know | if it | works on Gemstone, but if this is the case is really easy. I do this | when | move a pier site from one image to another. | | Cheers, | | Mariano | | On Sat, May 23, 2009 at 1:01 PM, Sean Allen | wrote: | | > I'll add SIXX on to my ever growing list of things to learn and if I | have | > issues, will be in touch. | > | > | > On May 23, 2009, at 11:02 AM, Dale Henrichs wrote: | > | > SSean, | >> | >> Use SIXX. During SIXX testing I was able to move a Pier kernel from | Squeak | >> to GemStone. | >> | >> If you run into issues, I will be very interested to fix them, | since at | >> the moment I think SIXX is the best alternative. | >> | >> Dale | >> | >> ----- "Sean Allen" wrote: | >> | >> | i want to start playing around with putting together a site in | pharo | >> | | >> | on my laptop and then when i have it mostly completed, moving it | over | >> | | >> | to a GLASS installation. | >> | i've scanned back through the list since i first signed up last | year | >> | | >> | ( and found numerous interesting tidbits i had missed ), but i | can't | >> | | >> | find anything on this: | >> | | >> | if i want to move an existing pier site out of a pharo/squeak | image | >> | and into glass, how do i do that? i assume it would be using | >> | monticello. i'm not sure though, how much i need to move. i'm | sure | >> | there is a simple answer to this, but i still haven't really | used | >> | monticello much as i have been able to get by without using it | yet. | >> | | >> | | >> | _______________________________________________ | >> | Magritte, Pier and Related Tools ... | >> | https://www.iam.unibe.ch/mailman/listinfo/smallwiki | >> _______________________________________________ | >> Magritte, Pier and Related Tools ... | >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki | >> | > | > _______________________________________________ | > Magritte, Pier and Related Tools ... | > https://www.iam.unibe.ch/mailman/listinfo/smallwiki | > From girba at iam.unibe.ch Sun May 24 18:23:22 2009 From: girba at iam.unibe.ch (Tudor Girba) Date: Sun, 24 May 2009 18:23:22 +0200 Subject: pier addons In-Reply-To: <017C8F25-48B3-4E8E-A6FC-93FC56BD2862@monkeysnatchbanana.com> References: <017C8F25-48B3-4E8E-A6FC-93FC56BD2862@monkeysnatchbanana.com> Message-ID: <506A0181-C95A-403F-ACE0-ECC9AA7B6344@iam.unibe.ch> Some are documented here: http://www.piercms.com/doc/add-ons Cheers, Doru On 24 May 2009, at 16:49, Sean Allen wrote: > is there anywhere where you can get a quick summary of the different > add ons? > > a few are detailed on squeaksource but not all of them. loading in > from monticello > and checking them out is always an option, but i wanted to see if > there was a quicker > route. > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com "Relationships are of two kinds: those we choose and those that happen. They both matter." From sean at monkeysnatchbanana.com Sun May 24 19:06:27 2009 From: sean at monkeysnatchbanana.com (Sean Allen) Date: Sun, 24 May 2009 13:06:27 -0400 Subject: typo in http://www.piercms.com/doc/add-ons Message-ID: <7EDC3074-8C83-4DF1-A0A1-323771884023@monkeysnatchbanana.com> Shout Pier => Syntax highlights Smalltalk expressions and methods. The color scheme can be con gured using a CSS style-sheet. congured should be configured . From girba at iam.unibe.ch Sun May 24 19:09:08 2009 From: girba at iam.unibe.ch (Tudor Girba) Date: Sun, 24 May 2009 19:09:08 +0200 Subject: typo in http://www.piercms.com/doc/add-ons In-Reply-To: <7EDC3074-8C83-4DF1-A0A1-323771884023@monkeysnatchbanana.com> References: <7EDC3074-8C83-4DF1-A0A1-323771884023@monkeysnatchbanana.com> Message-ID: <649CFA7F-1AC6-4D52-9E39-290005586CDB@iam.unibe.ch> Thanks pointing it out. It's fixed now. Cheers, Doru On 24 May 2009, at 19:06, Sean Allen wrote: > Shout Pier => > > Syntax highlights Smalltalk expressions and methods. The color > scheme can be con gured using a CSS style-sheet. > > congured should be configured . > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com "Every thing should have the right to be different." From sean at monkeysnatchbanana.com Sun May 24 19:41:35 2009 From: sean at monkeysnatchbanana.com (Sean Allen) Date: Sun, 24 May 2009 13:41:35 -0400 Subject: pier forms [ was pier addons ] In-Reply-To: <506A0181-C95A-403F-ACE0-ECC9AA7B6344@iam.unibe.ch> References: <017C8F25-48B3-4E8E-A6FC-93FC56BD2862@monkeysnatchbanana.com> <506A0181-C95A-403F-ACE0-ECC9AA7B6344@iam.unibe.ch> Message-ID: thanks. is there any documentation on PierForm somewhere? i'm trying to figure out how to use it and not getting very far. i'm either trying to use it for something it isnt designed for or just doing something fundamentally wrong. i'm trying to use it to create a form to add events to an events page.. so you can reuse the form to add new events, but i'm just not getting it correct. a quick read of any 'pier forms' basics documentation would probably clear up most of my questions. On May 24, 2009, at 12:23 PM, Tudor Girba wrote: > Some are documented here: > http://www.piercms.com/doc/add-ons > > Cheers, > Doru > > > On 24 May 2009, at 16:49, Sean Allen wrote: > >> is there anywhere where you can get a quick summary of the >> different add ons? >> >> a few are detailed on squeaksource but not all of them. loading in >> from monticello >> and checking them out is always an option, but i wanted to see if >> there was a quicker >> route. >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > -- > www.tudorgirba.com > > "Relationships are of two kinds: those we choose and those that > happen. They both matter." > > > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From renggli at gmail.com Sun May 24 19:50:56 2009 From: renggli at gmail.com (Lukas Renggli) Date: Sun, 24 May 2009 19:50:56 +0200 Subject: pier forms [ was pier addons ] In-Reply-To: References: <017C8F25-48B3-4E8E-A6FC-93FC56BD2862@monkeysnatchbanana.com> <506A0181-C95A-403F-ACE0-ECC9AA7B6344@iam.unibe.ch> Message-ID: <67628d690905241050j4f0d41by8b5f5b3ad3fb01aa@mail.gmail.com> > is there any documentation on PierForm somewhere? > i'm trying to figure out how to use it and not getting very far. Yes, in the section "3.6.3 Adaptive Forms" (Page 39). > i'm either trying to use it for something it isnt designed for > or just doing something fundamentally wrong. In its current form the implementation does not allow your more than to enter and edit structured data. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From sean at monkeysnatchbanana.com Sun May 24 20:21:03 2009 From: sean at monkeysnatchbanana.com (Sean Allen) Date: Sun, 24 May 2009 14:21:03 -0400 Subject: pier forms [ was pier addons ] In-Reply-To: <67628d690905241050j4f0d41by8b5f5b3ad3fb01aa@mail.gmail.com> References: <017C8F25-48B3-4E8E-A6FC-93FC56BD2862@monkeysnatchbanana.com> <506A0181-C95A-403F-ACE0-ECC9AA7B6344@iam.unibe.ch> <67628d690905241050j4f0d41by8b5f5b3ad3fb01aa@mail.gmail.com> Message-ID: On May 24, 2009, at 1:50 PM, Lukas Renggli wrote: >> is there any documentation on PierForm somewhere? >> i'm trying to figure out how to use it and not getting very far. > > Yes, in the section > "3.6.3 Adaptive Forms" (Page 39). > >> i'm either trying to use it for something it isnt designed for >> or just doing something fundamentally wrong. > > In its current form the implementation does not allow your more than > to enter and edit structured data. taking the example of the movie actor database from Reng06a.pdf i create a form to add structured actor info. how do i reuse that form? go to an existing entry and copy it and then edit the data? if i have multiple entries, how do have pier display them so you can get to them? values:children will display the title in a page but you cant get to all the structured information. From chaetal at gmail.com Sun May 24 21:53:32 2009 From: chaetal at gmail.com (Dennis Schetinin) Date: Sun, 24 May 2009 23:53:32 +0400 Subject: Exporting problem (Unable to export: 'Trying to write out, AnObsoletePRReportView') Message-ID: <84f77e270905241253q60b6100eo982d7f173fe39b7d@mail.gmail.com> I've upgraded some time ago to a recent version of Pier. Now I've got a problem (see subject) trying to export from the image... Seems like the class (PRReportView?) was removed but the reference is still somewhere in code and/or data. I don't know how to handle such things in Squeak (Pharo). Any help please? -- Dennis Schetinin -------------- next part -------------- An HTML attachment was scrubbed... URL: From renggli at gmail.com Sun May 24 21:57:44 2009 From: renggli at gmail.com (Lukas Renggli) Date: Sun, 24 May 2009 21:57:44 +0200 Subject: Exporting problem (Unable to export: 'Trying to write out, AnObsoletePRReportView') In-Reply-To: <84f77e270905241253q60b6100eo982d7f173fe39b7d@mail.gmail.com> References: <84f77e270905241253q60b6100eo982d7f173fe39b7d@mail.gmail.com> Message-ID: <67628d690905241257la8e207cj17024d616a6182eb@mail.gmail.com> > I've upgraded some time ago to a recent version of Pier. Now I've got a > problem (see subject) trying to export from the image... Seems like the > class (PRReportView?) was removed but the reference is still somewhere in > code and/or data. I don't know how to handle such things in Squeak (Pharo). > Any help please? I would create an empty class of that name, import the snapshot and fix references to this class and its instances manually. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at gmail.com Sun May 24 22:07:39 2009 From: renggli at gmail.com (Lukas Renggli) Date: Sun, 24 May 2009 22:07:39 +0200 Subject: pier forms [ was pier addons ] In-Reply-To: References: <017C8F25-48B3-4E8E-A6FC-93FC56BD2862@monkeysnatchbanana.com> <506A0181-C95A-403F-ACE0-ECC9AA7B6344@iam.unibe.ch> <67628d690905241050j4f0d41by8b5f5b3ad3fb01aa@mail.gmail.com> Message-ID: <67628d690905241307j5fdcaf8fg4373060794a797d7@mail.gmail.com> > i create a form to add structured actor info. > how do i reuse that form? > go to an existing entry and copy it and then edit the data? Yes. The meta-model of the form structure is shared, the model is unique (copied). > if i have multiple entries, how do have pier display them so you > can get to them? values:children will display the title in a page > but you cant get to all the structured information. PRReportView was a useful view on structured data, I removed it from Pier-Seaside a couple of weeks ago. It didn't look too useful in the context of Pier alone. Maybe I should rather have been moved to Pier-Form, because it was a nice view to display a report on structured data. Support for value-links could be improved in the context of Pier-Form, I haven't touched that plugin for years. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From chaetal at gmail.com Sun May 24 22:25:24 2009 From: chaetal at gmail.com (Dennis Schetinin) Date: Mon, 25 May 2009 00:25:24 +0400 Subject: Exporting problem (Unable to export: 'Trying to write out, AnObsoletePRReportView') In-Reply-To: <67628d690905241257la8e207cj17024d616a6182eb@mail.gmail.com> References: <84f77e270905241253q60b6100eo982d7f173fe39b7d@mail.gmail.com> <67628d690905241257la8e207cj17024d616a6182eb@mail.gmail.com> Message-ID: <84f77e270905241325x457d965cme473d26835f66bac@mail.gmail.com> > I've upgraded some time ago to a recent version of Pier. Now I've got a > > problem (see subject) trying to export from the image... Seems like the > > class (PRReportView?) was removed but the reference is still somewhere in > > code and/or data. I don't know how to handle such things in Squeak > (Pharo). > > Any help please? > > I would create an empty class of that name, import the snapshot and > fix references to this class and its instances manually. > > Lukas > I did tried that (created classes named #AnObsoletePRReportView and #PRReportView), but it doesn't help... I've found the error is generated DiskProxy >> #global:selector:args: if the name of the class begins with "AnAbsolete". Commenting those lines gave me the file... Too late now so will be back tomorrow :) -- Dennis Schetinin -------------- next part -------------- An HTML attachment was scrubbed... URL: From sean at monkeysnatchbanana.com Sun May 24 22:27:06 2009 From: sean at monkeysnatchbanana.com (Sean Allen) Date: Sun, 24 May 2009 16:27:06 -0400 Subject: pier forms [ was pier addons ] In-Reply-To: <67628d690905241307j5fdcaf8fg4373060794a797d7@mail.gmail.com> References: <017C8F25-48B3-4E8E-A6FC-93FC56BD2862@monkeysnatchbanana.com> <506A0181-C95A-403F-ACE0-ECC9AA7B6344@iam.unibe.ch> <67628d690905241050j4f0d41by8b5f5b3ad3fb01aa@mail.gmail.com> <67628d690905241307j5fdcaf8fg4373060794a797d7@mail.gmail.com> Message-ID: <5CEC9CB4-3394-4405-9D40-3466AE2DF3EC@monkeysnatchbanana.com> On May 24, 2009, at 4:07 PM, Lukas Renggli wrote: >> if i have multiple entries, how do have pier display them so you >> can get to them? values:children will display the title in a page >> but you cant get to all the structured information. > > PRReportView was a useful view on structured data, I removed it from > Pier-Seaside a couple of weeks ago. It didn't look too useful in the > context of Pier alone. Maybe I should rather have been moved to > Pier-Form, because it was a nice view to display a report on > structured data. > > Support for value-links could be improved in the context of Pier-Form, > I haven't touched that plugin for years. what was Pier-Form used for originally? i'm still having a hard time imaging how it was used. From renggli at gmail.com Sun May 24 22:35:11 2009 From: renggli at gmail.com (Lukas Renggli) Date: Sun, 24 May 2009 22:35:11 +0200 Subject: pier forms [ was pier addons ] In-Reply-To: <5CEC9CB4-3394-4405-9D40-3466AE2DF3EC@monkeysnatchbanana.com> References: <017C8F25-48B3-4E8E-A6FC-93FC56BD2862@monkeysnatchbanana.com> <506A0181-C95A-403F-ACE0-ECC9AA7B6344@iam.unibe.ch> <67628d690905241050j4f0d41by8b5f5b3ad3fb01aa@mail.gmail.com> <67628d690905241307j5fdcaf8fg4373060794a797d7@mail.gmail.com> <5CEC9CB4-3394-4405-9D40-3466AE2DF3EC@monkeysnatchbanana.com> Message-ID: <67628d690905241335s668adbcema66269e5282810ff@mail.gmail.com> > what was Pier-Form used for originally? i'm still having a hard time > imaging how it was used. It serves as a demo for the meta- and meta-meta capabilities of Magritte and Pier. The code was published to accompany the tutorial and to give developers and end-users an idea how to do more advanced stuff with Magritte. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at gmail.com Sun May 24 22:50:45 2009 From: renggli at gmail.com (Lukas Renggli) Date: Sun, 24 May 2009 22:50:45 +0200 Subject: Exporting problem (Unable to export: 'Trying to write out, AnObsoletePRReportView') In-Reply-To: <84f77e270905241325x457d965cme473d26835f66bac@mail.gmail.com> References: <84f77e270905241253q60b6100eo982d7f173fe39b7d@mail.gmail.com> <67628d690905241257la8e207cj17024d616a6182eb@mail.gmail.com> <84f77e270905241325x457d965cme473d26835f66bac@mail.gmail.com> Message-ID: <67628d690905241350o7894c6b8mb9d53d14db8db6e2@mail.gmail.com> Sorry, I misread your mail. I thought you tried to import code that contained this class into an image that did not contain this class. In your case your model already contains these obsolete classes. Try evaluating the following code to fix your model: PRComponent allInstances do: [ :comp | (comp componentClass includesBehavior: PRViewsWidget) ifTrue: [ comp settings at: PRViewsWidget descriptionViewClasses ifPresent: [ :classes | comp settings at: PRViewsWidget descriptionViewClasses put: (classes reject: [ :each | each isObsolete ]) ] ] ] After that the export should work fine. I will add that to the automatic migrations scripts. Cheers, Lukas On Sun, May 24, 2009 at 10:25 PM, Dennis Schetinin wrote: > > >> > I've upgraded some time ago to a recent version of Pier. Now I've got a >> > problem (see subject) trying to export from the image... Seems like the >> > class (PRReportView?) was removed but the reference is still somewhere >> > in >> > code and/or data. I don't know how to handle such things in Squeak >> > (Pharo). >> > Any help please? >> >> I would create an empty class of that name, import the snapshot and >> fix references to this class and its instances manually. >> >> Lukas > > I did tried that (created classes named #AnObsoletePRReportView and > #PRReportView), but it doesn't help... > > I've found the error is generated DiskProxy >> #global:selector:args: if the > name of the class begins with "AnAbsolete". Commenting those lines gave me > the file... Too late now so will be back tomorrow :) > > -- > Dennis Schetinin > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli http://www.lukas-renggli.ch From sean at monkeysnatchbanana.com Sun May 24 22:55:05 2009 From: sean at monkeysnatchbanana.com (Sean Allen) Date: Sun, 24 May 2009 16:55:05 -0400 Subject: pier forms [ was pier addons ] In-Reply-To: <67628d690905241335s668adbcema66269e5282810ff@mail.gmail.com> References: <017C8F25-48B3-4E8E-A6FC-93FC56BD2862@monkeysnatchbanana.com> <506A0181-C95A-403F-ACE0-ECC9AA7B6344@iam.unibe.ch> <67628d690905241050j4f0d41by8b5f5b3ad3fb01aa@mail.gmail.com> <67628d690905241307j5fdcaf8fg4373060794a797d7@mail.gmail.com> <5CEC9CB4-3394-4405-9D40-3466AE2DF3EC@monkeysnatchbanana.com> <67628d690905241335s668adbcema66269e5282810ff@mail.gmail.com> Message-ID: <7A52507C-E53F-4FCC-B1CF-0DEC9EBF3C0D@monkeysnatchbanana.com> On May 24, 2009, at 4:35 PM, Lukas Renggli wrote: >> what was Pier-Form used for originally? i'm still having a hard time >> imaging how it was used. > > It serves as a demo for the meta- and meta-meta capabilities of > Magritte and Pier. The code was published to accompany the tutorial > and to give developers and end-users an idea how to do more advanced > stuff with Magritte. ah. that makes sense. thanks lukas. From marianopeck at gmail.com Mon May 25 02:52:12 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Sun, 24 May 2009 21:52:12 -0300 Subject: Exporting problem (Unable to export: 'Trying to write out, AnObsoletePRReportView') In-Reply-To: <67628d690905241350o7894c6b8mb9d53d14db8db6e2@mail.gmail.com> References: <84f77e270905241253q60b6100eo982d7f173fe39b7d@mail.gmail.com> <67628d690905241257la8e207cj17024d616a6182eb@mail.gmail.com> <84f77e270905241325x457d965cme473d26835f66bac@mail.gmail.com> <67628d690905241350o7894c6b8mb9d53d14db8db6e2@mail.gmail.com> Message-ID: On Sun, May 24, 2009 at 5:50 PM, Lukas Renggli wrote: > Sorry, I misread your mail. I thought you tried to import code that > contained this class into an image that did not contain this class. > > In your case your model already contains these obsolete classes. Try > evaluating the following code to fix your model: > > PRComponent allInstances do: [ :comp | > (comp componentClass includesBehavior: PRViewsWidget) ifTrue: [ > comp settings at: PRViewsWidget descriptionViewClasses > ifPresent: [ :classes | > comp settings > at: PRViewsWidget descriptionViewClasses > put: (classes reject: [ :each | each > isObsolete ]) ] ] ] > > After that the export should work fine. > > I will add that to the automatic migrations scripts. > what are automatic migration scripts ? where are they ? thanks! mariano > > Cheers, > Lukas > > On Sun, May 24, 2009 at 10:25 PM, Dennis Schetinin > wrote: > > > > > >> > I've upgraded some time ago to a recent version of Pier. Now I've got > a > >> > problem (see subject) trying to export from the image... Seems like > the > >> > class (PRReportView?) was removed but the reference is still somewhere > >> > in > >> > code and/or data. I don't know how to handle such things in Squeak > >> > (Pharo). > >> > Any help please? > >> > >> I would create an empty class of that name, import the snapshot and > >> fix references to this class and its instances manually. > >> > >> Lukas > > > > I did tried that (created classes named #AnObsoletePRReportView and > > #PRReportView), but it doesn't help... > > > > I've found the error is generated DiskProxy >> #global:selector:args: if > the > > name of the class begins with "AnAbsolete". Commenting those lines gave > me > > the file... Too late now so will be back tomorrow :) > > > > -- > > Dennis Schetinin > > > > _______________________________________________ > > Magritte, Pier and Related Tools ... > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marianopeck at gmail.com Mon May 25 03:02:03 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Sun, 24 May 2009 22:02:03 -0300 Subject: pharo to glass: moving data question... In-Reply-To: <1419124045.1022971243178578867.JavaMail.root@gir> References: <2060510619.1022951243178549277.JavaMail.root@gir> <1419124045.1022971243178578867.JavaMail.root@gir> Message-ID: On Sun, May 24, 2009 at 12:22 PM, Dale Henrichs wrote: > Mariano, > > I haven't had a chance to look at the details of exporter/importer, but I > assume that it is based on squeak-based serialization. At the moment SIXX is > probably a better option for moving data to GemStone. > I also don't know how it is do it. Lukas, do you know ? Perhaps, extending Pier/Export package using a GemStone compatible serializer (like SIXX) would be a good idea to do. Do you have something like a magic SIXX example to do this? export a pier kernel ? thanks! Mariano > > Dale > > ----- "Mariano Martinez Peck" wrote: > > | Pier (in 1.1.1 I think) has it's own Importer/Exporter. I don't know > | if it > | works on Gemstone, but if this is the case is really easy. I do this > | when > | move a pier site from one image to another. > | > | Cheers, > | > | Mariano > | > | On Sat, May 23, 2009 at 1:01 PM, Sean Allen > | wrote: > | > | > I'll add SIXX on to my ever growing list of things to learn and if I > | have > | > issues, will be in touch. > | > > | > > | > On May 23, 2009, at 11:02 AM, Dale Henrichs wrote: > | > > | > SSean, > | >> > | >> Use SIXX. During SIXX testing I was able to move a Pier kernel from > | Squeak > | >> to GemStone. > | >> > | >> If you run into issues, I will be very interested to fix them, > | since at > | >> the moment I think SIXX is the best alternative. > | >> > | >> Dale > | >> > | >> ----- "Sean Allen" wrote: > | >> > | >> | i want to start playing around with putting together a site in > | pharo > | >> | > | >> | on my laptop and then when i have it mostly completed, moving it > | over > | >> | > | >> | to a GLASS installation. > | >> | i've scanned back through the list since i first signed up last > | year > | >> | > | >> | ( and found numerous interesting tidbits i had missed ), but i > | can't > | >> | > | >> | find anything on this: > | >> | > | >> | if i want to move an existing pier site out of a pharo/squeak > | image > | >> | and into glass, how do i do that? i assume it would be using > | >> | monticello. i'm not sure though, how much i need to move. i'm > | sure > | >> | there is a simple answer to this, but i still haven't really > | used > | >> | monticello much as i have been able to get by without using it > | yet. > | >> | > | >> | > | >> | _______________________________________________ > | >> | Magritte, Pier and Related Tools ... > | >> | https://www.iam.unibe.ch/mailman/listinfo/smallwiki > | >> _______________________________________________ > | >> Magritte, Pier and Related Tools ... > | >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > | >> > | > > | > _______________________________________________ > | > Magritte, Pier and Related Tools ... > | > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > | > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From renggli at gmail.com Mon May 25 08:05:48 2009 From: renggli at gmail.com (Lukas Renggli) Date: Mon, 25 May 2009 08:05:48 +0200 Subject: pharo to glass: moving data question... In-Reply-To: References: <2060510619.1022951243178549277.JavaMail.root@gir> <1419124045.1022971243178578867.JavaMail.root@gir> Message-ID: <67628d690905242305j3fa0a5a4qb33e7d3b8c44897f@mail.gmail.com> > I also don't know how it is do it. Lukas, do you know ?? Perhaps, extending > Pier/Export package using a GemStone compatible serializer (like SIXX) would > be a good idea to do. I agree that extending the exporter to support SIXX would be a good idea. I created an issue: http://code.google.com/p/pier/issues/detail?id=96 Cheers, Lukas > > Do you have something like a magic SIXX example to do this? export a pier > kernel ? > > thanks! > > Mariano > > >> >> Dale >> >> ----- "Mariano Martinez Peck" wrote: >> >> | Pier (in 1.1.1 I think) has it's own Importer/Exporter. I don't know >> | if it >> | works on Gemstone, but if this is the case is really easy. I do this >> | when >> | move a pier site from one image to another. >> | >> | Cheers, >> | >> | Mariano >> | >> | On Sat, May 23, 2009 at 1:01 PM, Sean Allen >> | wrote: >> | >> | > I'll add SIXX on to my ever growing list of things to learn and if I >> | have >> | > issues, will be in touch. >> | > >> | > >> | > On May 23, 2009, at 11:02 AM, Dale Henrichs wrote: >> | > >> | > ?SSean, >> | >> >> | >> Use SIXX. During SIXX testing I was able to move a Pier kernel from >> | Squeak >> | >> to GemStone. >> | >> >> | >> If you run into issues, I will be very interested to fix them, >> | since at >> | >> the moment I think SIXX is the best alternative. >> | >> >> | >> Dale >> | >> >> | >> ----- "Sean Allen" wrote: >> | >> >> | >> | i want to start playing around with putting together a site in >> | pharo >> | >> | >> | >> | on my laptop and then when i have it mostly completed, moving it >> | over >> | >> | >> | >> | to a GLASS installation. >> | >> | i've scanned back through the list since i first signed up last >> | year >> | >> | >> | >> | ( and found numerous interesting tidbits i had missed ), but i >> | can't >> | >> | >> | >> | find anything on this: >> | >> | >> | >> | if i want to move an existing pier site out of a pharo/squeak >> | image >> | >> | and into glass, how do i do that? i assume it would be using >> | >> | monticello. i'm not sure though, how much i need to move. i'm >> | sure >> | >> | there is a simple answer to this, but i still haven't really >> | used >> | >> | monticello much as i have been able to get by without using it >> | yet. >> | >> | >> | >> | >> | >> | _______________________________________________ >> | >> | Magritte, Pier and Related Tools ... >> | >> | https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> | >> _______________________________________________ >> | >> Magritte, Pier and Related Tools ... >> | >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> | >> >> | > >> | > _______________________________________________ >> | > Magritte, Pier and Related Tools ... >> | > https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> | > > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli http://www.lukas-renggli.ch From chaetal at gmail.com Mon May 25 10:03:15 2009 From: chaetal at gmail.com (Dennis Schetinin) Date: Mon, 25 May 2009 12:03:15 +0400 Subject: Exporting problem (Unable to export: 'Trying to write out, AnObsoletePRReportView') In-Reply-To: <67628d690905241350o7894c6b8mb9d53d14db8db6e2@mail.gmail.com> References: <84f77e270905241253q60b6100eo982d7f173fe39b7d@mail.gmail.com> <67628d690905241257la8e207cj17024d616a6182eb@mail.gmail.com> <84f77e270905241325x457d965cme473d26835f66bac@mail.gmail.com> <67628d690905241350o7894c6b8mb9d53d14db8db6e2@mail.gmail.com> Message-ID: <84f77e270905250103w3e8c3167ya94a8a3840a142c@mail.gmail.com> > > PRComponent allInstances do: [ :comp | > (comp componentClass includesBehavior: PRViewsWidget) ifTrue: [ > comp settings at: PRViewsWidget descriptionViewClasses > ifPresent: [ :classes | > comp settings > at: PRViewsWidget descriptionViewClasses > put: (classes reject: [ :each | each > isObsolete ]) ] ] ] > It helps, thank you! -- Dennis Schetinin -------------- next part -------------- An HTML attachment was scrubbed... URL: From damien.cassou at gmail.com Mon May 25 10:22:30 2009 From: damien.cassou at gmail.com (Damien Cassou) Date: Mon, 25 May 2009 10:22:30 +0200 Subject: Remove Blog component In-Reply-To: References: <7b7d752d0905181119t2d5b1695ka1c8de92af9100d3@mail.gmail.com> <0B30B8A3-06E0-467A-9E04-C70DABF6519F@iam.unibe.ch> <7b7d752d0905181211n483171eehe0fab558b2f6b7fe@mail.gmail.com> Message-ID: <6ac749c10905250122n774180a3ld7f2e1116288ab27@mail.gmail.com> On Tue, May 19, 2009 at 2:49 AM, Mariano Martinez Peck wrote: > It was useful for me and I think could be for someone else coming later to > this list. What about putting this question and answer in > http://www.piercms.com/doc/faq http://www.piercms.com/doc/faq#45138032 -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry From girba at iam.unibe.ch Mon May 25 10:33:36 2009 From: girba at iam.unibe.ch (Tudor Girba) Date: Mon, 25 May 2009 10:33:36 +0200 Subject: Remove Blog component In-Reply-To: <6ac749c10905250122n774180a3ld7f2e1116288ab27@mail.gmail.com> References: <7b7d752d0905181119t2d5b1695ka1c8de92af9100d3@mail.gmail.com> <0B30B8A3-06E0-467A-9E04-C70DABF6519F@iam.unibe.ch> <7b7d752d0905181211n483171eehe0fab558b2f6b7fe@mail.gmail.com> <6ac749c10905250122n774180a3ld7f2e1116288ab27@mail.gmail.com> Message-ID: <119295A0-E593-4632-89D9-B288C4D1CF4E@iam.unibe.ch> Thanks, Damien. Doru On 25 May 2009, at 10:22, Damien Cassou wrote: > On Tue, May 19, 2009 at 2:49 AM, Mariano Martinez Peck > wrote: >> It was useful for me and I think could be for someone else coming >> later to >> this list. What about putting this question and answer in >> http://www.piercms.com/doc/faq > > http://www.piercms.com/doc/faq#45138032 > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com "Not knowing how to do something is not an argument for how it cannot be done." From marianopeck at gmail.com Mon May 25 16:35:37 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Mon, 25 May 2009 11:35:37 -0300 Subject: pharo to glass: moving data question... In-Reply-To: <67628d690905242305j3fa0a5a4qb33e7d3b8c44897f@mail.gmail.com> References: <2060510619.1022951243178549277.JavaMail.root@gir> <1419124045.1022971243178578867.JavaMail.root@gir> <67628d690905242305j3fa0a5a4qb33e7d3b8c44897f@mail.gmail.com> Message-ID: On Mon, May 25, 2009 at 3:05 AM, Lukas Renggli wrote: > > I also don't know how it is do it. Lukas, do you know ? Perhaps, > extending > > Pier/Export package using a GemStone compatible serializer (like SIXX) > would > > be a good idea to do. > > I agree that extending the exporter to support SIXX would be a good idea. > > I created an issue: > > http://code.google.com/p/pier/issues/detail?id=96 Thanks Lukas!!! Mariano > > > Cheers, > Lukas > > > > > > Do you have something like a magic SIXX example to do this? export a pier > > kernel ? > > > > thanks! > > > > Mariano > > > > > >> > >> Dale > >> > >> ----- "Mariano Martinez Peck" wrote: > >> > >> | Pier (in 1.1.1 I think) has it's own Importer/Exporter. I don't know > >> | if it > >> | works on Gemstone, but if this is the case is really easy. I do this > >> | when > >> | move a pier site from one image to another. > >> | > >> | Cheers, > >> | > >> | Mariano > >> | > >> | On Sat, May 23, 2009 at 1:01 PM, Sean Allen > >> | wrote: > >> | > >> | > I'll add SIXX on to my ever growing list of things to learn and if I > >> | have > >> | > issues, will be in touch. > >> | > > >> | > > >> | > On May 23, 2009, at 11:02 AM, Dale Henrichs wrote: > >> | > > >> | > SSean, > >> | >> > >> | >> Use SIXX. During SIXX testing I was able to move a Pier kernel from > >> | Squeak > >> | >> to GemStone. > >> | >> > >> | >> If you run into issues, I will be very interested to fix them, > >> | since at > >> | >> the moment I think SIXX is the best alternative. > >> | >> > >> | >> Dale > >> | >> > >> | >> ----- "Sean Allen" wrote: > >> | >> > >> | >> | i want to start playing around with putting together a site in > >> | pharo > >> | >> | > >> | >> | on my laptop and then when i have it mostly completed, moving it > >> | over > >> | >> | > >> | >> | to a GLASS installation. > >> | >> | i've scanned back through the list since i first signed up last > >> | year > >> | >> | > >> | >> | ( and found numerous interesting tidbits i had missed ), but i > >> | can't > >> | >> | > >> | >> | find anything on this: > >> | >> | > >> | >> | if i want to move an existing pier site out of a pharo/squeak > >> | image > >> | >> | and into glass, how do i do that? i assume it would be using > >> | >> | monticello. i'm not sure though, how much i need to move. i'm > >> | sure > >> | >> | there is a simple answer to this, but i still haven't really > >> | used > >> | >> | monticello much as i have been able to get by without using it > >> | yet. > >> | >> | > >> | >> | > >> | >> | _______________________________________________ > >> | >> | Magritte, Pier and Related Tools ... > >> | >> | https://www.iam.unibe.ch/mailman/listinfo/smallwiki > >> | >> _______________________________________________ > >> | >> Magritte, Pier and Related Tools ... > >> | >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > >> | >> > >> | > > >> | > _______________________________________________ > >> | > Magritte, Pier and Related Tools ... > >> | > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > >> | > > > > > > > _______________________________________________ > > Magritte, Pier and Related Tools ... > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marianopeck at gmail.com Mon May 25 16:37:00 2009 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Mon, 25 May 2009 11:37:00 -0300 Subject: pharo to glass: moving data question... In-Reply-To: References: <2060510619.1022951243178549277.JavaMail.root@gir> <1419124045.1022971243178578867.JavaMail.root@gir> <67628d690905242305j3fa0a5a4qb33e7d3b8c44897f@mail.gmail.com> Message-ID: Just for curious, how is do it right now? how it serializes the objects? On Mon, May 25, 2009 at 11:35 AM, Mariano Martinez Peck < marianopeck at gmail.com> wrote: > > > On Mon, May 25, 2009 at 3:05 AM, Lukas Renggli wrote: > >> > I also don't know how it is do it. Lukas, do you know ? Perhaps, >> extending >> > Pier/Export package using a GemStone compatible serializer (like SIXX) >> would >> > be a good idea to do. >> >> I agree that extending the exporter to support SIXX would be a good idea. >> >> I created an issue: >> >> http://code.google.com/p/pier/issues/detail?id=96 > > > > Thanks Lukas!!! > > Mariano > > > >> >> >> Cheers, >> Lukas >> >> >> > >> > Do you have something like a magic SIXX example to do this? export a >> pier >> > kernel ? >> > >> > thanks! >> > >> > Mariano >> > >> > >> >> >> >> Dale >> >> >> >> ----- "Mariano Martinez Peck" wrote: >> >> >> >> | Pier (in 1.1.1 I think) has it's own Importer/Exporter. I don't know >> >> | if it >> >> | works on Gemstone, but if this is the case is really easy. I do this >> >> | when >> >> | move a pier site from one image to another. >> >> | >> >> | Cheers, >> >> | >> >> | Mariano >> >> | >> >> | On Sat, May 23, 2009 at 1:01 PM, Sean Allen >> >> | wrote: >> >> | >> >> | > I'll add SIXX on to my ever growing list of things to learn and if >> I >> >> | have >> >> | > issues, will be in touch. >> >> | > >> >> | > >> >> | > On May 23, 2009, at 11:02 AM, Dale Henrichs wrote: >> >> | > >> >> | > SSean, >> >> | >> >> >> | >> Use SIXX. During SIXX testing I was able to move a Pier kernel >> from >> >> | Squeak >> >> | >> to GemStone. >> >> | >> >> >> | >> If you run into issues, I will be very interested to fix them, >> >> | since at >> >> | >> the moment I think SIXX is the best alternative. >> >> | >> >> >> | >> Dale >> >> | >> >> >> | >> ----- "Sean Allen" wrote: >> >> | >> >> >> | >> | i want to start playing around with putting together a site in >> >> | pharo >> >> | >> | >> >> | >> | on my laptop and then when i have it mostly completed, moving it >> >> | over >> >> | >> | >> >> | >> | to a GLASS installation. >> >> | >> | i've scanned back through the list since i first signed up last >> >> | year >> >> | >> | >> >> | >> | ( and found numerous interesting tidbits i had missed ), but i >> >> | can't >> >> | >> | >> >> | >> | find anything on this: >> >> | >> | >> >> | >> | if i want to move an existing pier site out of a pharo/squeak >> >> | image >> >> | >> | and into glass, how do i do that? i assume it would be using >> >> | >> | monticello. i'm not sure though, how much i need to move. i'm >> >> | sure >> >> | >> | there is a simple answer to this, but i still haven't really >> >> | used >> >> | >> | monticello much as i have been able to get by without using it >> >> | yet. >> >> | >> | >> >> | >> | >> >> | >> | _______________________________________________ >> >> | >> | Magritte, Pier and Related Tools ... >> >> | >> | https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> >> | >> _______________________________________________ >> >> | >> Magritte, Pier and Related Tools ... >> >> | >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> >> | >> >> >> | > >> >> | > _______________________________________________ >> >> | > Magritte, Pier and Related Tools ... >> >> | > https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> >> | > >> > >> > >> > _______________________________________________ >> > Magritte, Pier and Related Tools ... >> > https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> > >> >> >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From renggli at gmail.com Mon May 25 16:55:22 2009 From: renggli at gmail.com (Lukas Renggli) Date: Mon, 25 May 2009 16:55:22 +0200 Subject: pharo to glass: moving data question... In-Reply-To: References: <2060510619.1022951243178549277.JavaMail.root@gir> <1419124045.1022971243178578867.JavaMail.root@gir> <67628d690905242305j3fa0a5a4qb33e7d3b8c44897f@mail.gmail.com> Message-ID: <67628d690905250755t13fc4f8bua6c174dc7cd2b9ad@mail.gmail.com> > Just for curious, how is do it right now? how it serializes the objects? It uses the binary serialization mechanism of Squeak: ReferenceStream. Cheers, Lukas > > On Mon, May 25, 2009 at 11:35 AM, Mariano Martinez Peck > wrote: >> >> >> On Mon, May 25, 2009 at 3:05 AM, Lukas Renggli wrote: >>> >>> > I also don't know how it is do it. Lukas, do you know ?? Perhaps, >>> > extending >>> > Pier/Export package using a GemStone compatible serializer (like SIXX) >>> > would >>> > be a good idea to do. >>> >>> I agree that extending the exporter to support SIXX would be a good idea. >>> >>> I created an issue: >>> >>> http://code.google.com/p/pier/issues/detail?id=96 >> >> Thanks Lukas!!! >> >> Mariano >> >> >>> >>> Cheers, >>> Lukas >>> >>> >>> > >>> > Do you have something like a magic SIXX example to do this? export a >>> > pier >>> > kernel ? >>> > >>> > thanks! >>> > >>> > Mariano >>> > >>> > >>> >> >>> >> Dale >>> >> >>> >> ----- "Mariano Martinez Peck" wrote: >>> >> >>> >> | Pier (in 1.1.1 I think) has it's own Importer/Exporter. I don't know >>> >> | if it >>> >> | works on Gemstone, but if this is the case is really easy. I do this >>> >> | when >>> >> | move a pier site from one image to another. >>> >> | >>> >> | Cheers, >>> >> | >>> >> | Mariano >>> >> | >>> >> | On Sat, May 23, 2009 at 1:01 PM, Sean Allen >>> >> | wrote: >>> >> | >>> >> | > I'll add SIXX on to my ever growing list of things to learn and if >>> >> I >>> >> | have >>> >> | > issues, will be in touch. >>> >> | > >>> >> | > >>> >> | > On May 23, 2009, at 11:02 AM, Dale Henrichs wrote: >>> >> | > >>> >> | > ?SSean, >>> >> | >> >>> >> | >> Use SIXX. During SIXX testing I was able to move a Pier kernel >>> >> from >>> >> | Squeak >>> >> | >> to GemStone. >>> >> | >> >>> >> | >> If you run into issues, I will be very interested to fix them, >>> >> | since at >>> >> | >> the moment I think SIXX is the best alternative. >>> >> | >> >>> >> | >> Dale >>> >> | >> >>> >> | >> ----- "Sean Allen" wrote: >>> >> | >> >>> >> | >> | i want to start playing around with putting together a site in >>> >> | pharo >>> >> | >> | >>> >> | >> | on my laptop and then when i have it mostly completed, moving >>> >> it >>> >> | over >>> >> | >> | >>> >> | >> | to a GLASS installation. >>> >> | >> | i've scanned back through the list since i first signed up last >>> >> | year >>> >> | >> | >>> >> | >> | ( and found numerous interesting tidbits i had missed ), but i >>> >> | can't >>> >> | >> | >>> >> | >> | find anything on this: >>> >> | >> | >>> >> | >> | if i want to move an existing pier site out of a pharo/squeak >>> >> | image >>> >> | >> | and into glass, how do i do that? i assume it would be using >>> >> | >> | monticello. i'm not sure though, how much i need to move. i'm >>> >> | sure >>> >> | >> | there is a simple answer to this, but i still haven't really >>> >> | used >>> >> | >> | monticello much as i have been able to get by without using it >>> >> | yet. >>> >> | >> | >>> >> | >> | >>> >> | >> | _______________________________________________ >>> >> | >> | Magritte, Pier and Related Tools ... >>> >> | >> | https://www.iam.unibe.ch/mailman/listinfo/smallwiki >>> >> | >> _______________________________________________ >>> >> | >> Magritte, Pier and Related Tools ... >>> >> | >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >>> >> | >> >>> >> | > >>> >> | > _______________________________________________ >>> >> | > Magritte, Pier and Related Tools ... >>> >> | > https://www.iam.unibe.ch/mailman/listinfo/smallwiki >>> >> | > >>> > >>> > >>> > _______________________________________________ >>> > Magritte, Pier and Related Tools ... >>> > https://www.iam.unibe.ch/mailman/listinfo/smallwiki >>> > >>> >>> >>> >>> -- >>> Lukas Renggli >>> http://www.lukas-renggli.ch >>> >>> _______________________________________________ >>> Magritte, Pier and Related Tools ... >>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli http://www.lukas-renggli.ch From estebanlm at gmail.com Mon May 25 18:39:06 2009 From: estebanlm at gmail.com (Esteban Lorenzano) Date: Mon, 25 May 2009 13:39:06 -0300 Subject: Why MAFileModel forgot #renderImageOn:? Message-ID: Hi, I wonder why MAFileModel forgot #renderImageOn: (and all that family of renders). Now just shows an anchor :( Cheers, Esteban From renggli at gmail.com Mon May 25 19:05:51 2009 From: renggli at gmail.com (Lukas Renggli) Date: Mon, 25 May 2009 19:05:51 +0200 Subject: Why MAFileModel forgot #renderImageOn:? In-Reply-To: References: Message-ID: <67628d690905251005u2cf387e6yc37328e8ea679260@mail.gmail.com> > Hi, I wonder why MAFileModel forgot #renderImageOn: (and all that family of > renders). > Now just shows an anchor :( Before there were various ways on how a MAFileModel was rendered. This caused some confusion. Sometimes it was Magritte, sometimes the application did something special. Rendering a link to download is always a decent choice, trying to display the uploaded file is often not a good choice. If you want to display an upload also within a Magritte form simply create your own MAFileUploadComponent and set it using #componentClass: in your description. Cheers, Lukas > > Cheers, > Esteban > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli http://www.lukas-renggli.ch From chaetal at gmail.com Tue May 26 16:29:28 2009 From: chaetal at gmail.com (Dennis Schetinin) Date: Tue, 26 May 2009 18:29:28 +0400 Subject: encodings in pharo Message-ID: <84f77e270905260729r71fc6e48l1407afe66d8f6fe1@mail.gmail.com> Got totallly confused with encodings. I try to process strings with russian characters entered through Pier using caracters entered in Pharo itself (using RegEx, for example). But those strings are different. For example, code for russian symbol "No." by Pier string is (SmallInteger) 8470, but by Pharo it's 1069555990. I tried different combinations of #convert(...) methods in String and similar in WAKomEncoding but without any success so far... How can I convert from Pharo's encoding to Pier's one? (...sorry, but I'm unable to follow all those long discussions about encodings in Pharo) -- Dennis Schetinin -------------- next part -------------- An HTML attachment was scrubbed... URL: From cdrick65 at gmail.com Tue May 26 16:57:52 2009 From: cdrick65 at gmail.com (=?UTF-8?B?Q8OpZHJpY2sgQsOpbGVy?=) Date: Tue, 26 May 2009 16:57:52 +0200 Subject: blog archive oddness... In-Reply-To: <24545FD7-DAEE-4723-93D9-A3A245120901@monkeysnatchbanana.com> References: <3157F0AC-F86C-4DEE-864B-2DFD7C037130@monkeysnatchbanana.com> <1243059690.17256.4.camel@cineflux> <0C3254A1-B29E-469E-8CEA-207F78A73730@monkeysnatchbanana.com> <2F882DE8-F4E4-4D71-88FB-83735CCCCA41@monkeysnatchbanana.com> <67628d690905230728w5e1d096dm91ef21433ca5c137@mail.gmail.com> <24545FD7-DAEE-4723-93D9-A3A245120901@monkeysnatchbanana.com> Message-ID: >> Building the blog archive, related posts, tag cloud, etc. is a >> potentially expensive operation. Pier only calculates this information >> once, and assumes that most people are visitors, not editors. For my >> own use this scheme works perfectly well. If you think this is a bug, >> please file an issue or commit a fix. > > Given your explanation, any fix would seem to be worse than the issue for > installations with large amounts of data. maybe a place for annoucements ? -- C?drick From renggli at gmail.com Tue May 26 17:04:30 2009 From: renggli at gmail.com (Lukas Renggli) Date: Tue, 26 May 2009 17:04:30 +0200 Subject: encodings in pharo In-Reply-To: <84f77e270905260729r71fc6e48l1407afe66d8f6fe1@mail.gmail.com> References: <84f77e270905260729r71fc6e48l1407afe66d8f6fe1@mail.gmail.com> Message-ID: <67628d690905260804k5564916pa8bea5600d5d0052@mail.gmail.com> > How can I convert from Pharo's encoding to Pier's one? Pier has no encoding on its own. Encoding depends on what Seaside server adaptor you are using. WAKom: If you use this server adapter no conversion is happening, that means the strings are in UTF-8 and look messed up when being looked at from within the image. Common operation like #size, #includesSubstring:, #matches: and #, might return unexpected results. As long as the strings are sent back verbatim that works well and is very efficient. WAKomEncoded: If you use this server adapter incoming strings are converted from UTF-8 to Squeak, outgoing ones from Squeak to UTF-8. These strings look ok in Squeak, as long as the font you are using supports to display these characters. Conerting from and to UTF-8 is slow, but your regular expressions should work assuming that your regular expression engine works on wide strings. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From chaetal at gmail.com Tue May 26 17:25:52 2009 From: chaetal at gmail.com (Dennis Schetinin) Date: Tue, 26 May 2009 19:25:52 +0400 Subject: encodings in pharo In-Reply-To: <67628d690905260804k5564916pa8bea5600d5d0052@mail.gmail.com> References: <84f77e270905260729r71fc6e48l1407afe66d8f6fe1@mail.gmail.com> <67628d690905260804k5564916pa8bea5600d5d0052@mail.gmail.com> Message-ID: <84f77e270905260825r2ce49312xe2f703eb06f0ba1f@mail.gmail.com> 2009/5/26 Lukas Renggli > > How can I convert from Pharo's encoding to Pier's one? > > Pier has no encoding on its own. Encoding depends on what Seaside > server adaptor you are using. > > WAKomEncoded: I'm using this one. And the strings coming from Pier looks ok. And so the strings I enter manually (e.g. in Workspace) in Pharo do. But they (Pier's and Pharo's ones) are in different encodings actually and can not be compared. I think I have to convert Pharo's strings to Pier's encoding (I know the terms are not correct enough but I hope you'll get the idea)... For example, if I have Doctor instances entered using Pier, I want to find one with a particular name: Doctor allInstances select: [:each | each title = 'some russian here' ] --- this never will work as actual titles are encoded differently than 'some russian here'... So I guess I have to use ('some russian here' convertToEncoding: 'the correct encoding') or something like that... But I don't know what exactly. I found decision in some earlier versions of Pharo/Pier combination... but it doesn't work anymore... -- Dennis Schetinin -------------- next part -------------- An HTML attachment was scrubbed... URL: From renggli at gmail.com Tue May 26 17:41:54 2009 From: renggli at gmail.com (Lukas Renggli) Date: Tue, 26 May 2009 17:41:54 +0200 Subject: encodings in pharo In-Reply-To: <84f77e270905260825r2ce49312xe2f703eb06f0ba1f@mail.gmail.com> References: <84f77e270905260729r71fc6e48l1407afe66d8f6fe1@mail.gmail.com> <67628d690905260804k5564916pa8bea5600d5d0052@mail.gmail.com> <84f77e270905260825r2ce49312xe2f703eb06f0ba1f@mail.gmail.com> Message-ID: <67628d690905260841y4c5cf1a6xd2ea6a4462bd8b7b@mail.gmail.com> > I'm using this one. And the strings coming from Pier looks ok. And so the > strings I enter manually (e.g. in Workspace) in Pharo do. But they (Pier's > and Pharo's ones) are in different encodings actually and can not be > compared. I think I have to convert Pharo's strings to Pier's encoding (I > know the terms are not correct enough but I hope you'll get the idea)... For > example, if I have Doctor instances entered using Pier, I want to find one > with a particular name: There were some recent changes related to encodings in Pharo, but I don't know if this affects Seaside. Can you reproduce the problem in Squeak 3.9.1 for example? Maybe you should report this to the Pharo list instead, I don't know a solution. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From ducasse at iam.unibe.ch Tue May 26 18:04:36 2009 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Tue, 26 May 2009 18:04:36 +0200 Subject: encodings in pharo In-Reply-To: <67628d690905260841y4c5cf1a6xd2ea6a4462bd8b7b@mail.gmail.com> References: <84f77e270905260729r71fc6e48l1407afe66d8f6fe1@mail.gmail.com> <67628d690905260804k5564916pa8bea5600d5d0052@mail.gmail.com> <84f77e270905260825r2ce49312xe2f703eb06f0ba1f@mail.gmail.com> <67628d690905260841y4c5cf1a6xd2ea6a4462bd8b7b@mail.gmail.com> Message-ID: Yes please!!! UTF-8 was changed by mike and we need to shake it. Stef On May 26, 2009, at 5:41 PM, Lukas Renggli wrote: >> I'm using this one. And the strings coming from Pier looks ok. And >> so the >> strings I enter manually (e.g. in Workspace) in Pharo do. But they >> (Pier's >> and Pharo's ones) are in different encodings actually and can not be >> compared. I think I have to convert Pharo's strings to Pier's >> encoding (I >> know the terms are not correct enough but I hope you'll get the >> idea)... For >> example, if I have Doctor instances entered using Pier, I want to >> find one >> with a particular name: > > There were some recent changes related to encodings in Pharo, but I > don't know if this affects Seaside. > > Can you reproduce the problem in Squeak 3.9.1 for example? Maybe you > should report this to the Pharo list instead, I don't know a solution. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From david.tibbe at hpi.uni-potsdam.de Tue May 26 19:52:27 2009 From: david.tibbe at hpi.uni-potsdam.de (David Tibbe) Date: Tue, 26 May 2009 19:52:27 +0200 Subject: Tabbed view on a single object Message-ID: <4A1C2C5B.40908@hpi.uni-potsdam.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have an object with many descriptions. They can be grouped logically into different and disjoint views. I'm dreaming of a simple way to get a tabbed view, e.g. using a SimpleNavigation, for these different description groups. Specially I just want to use only one memento, i.e. I want to make changes in different views before the object is committed completely. Is there a simple way to realize such a thing? Or did anybody already something like that? Regards, David -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkocLFsACgkQY0bVmIBpe6kJAwCfRdanQQX/EHUzLoViF4+5UB+T xcoAnisalgh2ch3btH/9daRoZ3V+8nsz =nlab -----END PGP SIGNATURE----- From chaetal at gmail.com Wed May 27 07:46:31 2009 From: chaetal at gmail.com (Dennis Schetinin) Date: Wed, 27 May 2009 09:46:31 +0400 Subject: encodings in pharo In-Reply-To: References: <84f77e270905260729r71fc6e48l1407afe66d8f6fe1@mail.gmail.com> <67628d690905260804k5564916pa8bea5600d5d0052@mail.gmail.com> <84f77e270905260825r2ce49312xe2f703eb06f0ba1f@mail.gmail.com> <67628d690905260841y4c5cf1a6xd2ea6a4462bd8b7b@mail.gmail.com> Message-ID: <84f77e270905262246r2f4d2340v88853806aaa14d0a@mail.gmail.com> I'll try to arrange some time for the problem anon... Thank you for the replies... 2009/5/26 st?phane ducasse > Yes please!!! > UTF-8 was changed by mike and we need to shake it. > > Stef > > On May 26, 2009, at 5:41 PM, Lukas Renggli wrote: > > I'm using this one. And the strings coming from Pier looks ok. And so the >>> strings I enter manually (e.g. in Workspace) in Pharo do. But they >>> (Pier's >>> and Pharo's ones) are in different encodings actually and can not be >>> compared. I think I have to convert Pharo's strings to Pier's encoding (I >>> know the terms are not correct enough but I hope you'll get the idea)... >>> For >>> example, if I have Doctor instances entered using Pier, I want to find >>> one >>> with a particular name: >>> >> >> There were some recent changes related to encodings in Pharo, but I >> don't know if this affects Seaside. >> >> Can you reproduce the problem in Squeak 3.9.1 for example? Maybe you >> should report this to the Pharo list instead, I don't know a solution. >> >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> > -- Dennis Schetinin -------------- next part -------------- An HTML attachment was scrubbed... URL: From philippe.marschall at gmail.com Wed May 27 14:30:21 2009 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Wed, 27 May 2009 14:30:21 +0200 Subject: encodings in pharo In-Reply-To: <67628d690905260841y4c5cf1a6xd2ea6a4462bd8b7b@mail.gmail.com> References: <84f77e270905260729r71fc6e48l1407afe66d8f6fe1@mail.gmail.com> <67628d690905260804k5564916pa8bea5600d5d0052@mail.gmail.com> <84f77e270905260825r2ce49312xe2f703eb06f0ba1f@mail.gmail.com> <67628d690905260841y4c5cf1a6xd2ea6a4462bd8b7b@mail.gmail.com> Message-ID: <66666f210905270530x70c7d357k3a449cb4de34eb6d@mail.gmail.com> 2009/5/26 Lukas Renggli : >> I'm using this one. And the strings coming from Pier looks ok. And so the >> strings I enter manually (e.g. in Workspace) in Pharo do. But they (Pier's >> and Pharo's ones) are in different encodings actually and can not be >> compared. I think I have to convert Pharo's strings to Pier's encoding (I >> know the terms are not correct enough but I hope you'll get the idea)... For >> example, if I have Doctor instances entered using Pier, I want to find one >> with a particular name: > > There were some recent changes related to encodings in Pharo, but I > don't know if this affects Seaside. If I understand the changes correctly then it shouldn't. Cheers Philippe From rdrvr.biz at gmail.com Wed May 27 20:46:35 2009 From: rdrvr.biz at gmail.com (David Farber) Date: Wed, 27 May 2009 12:46:35 -0600 Subject: Two Pier Forms Questions In-Reply-To: <67628d690905092248m194a5f63s15a9df09c8484319@mail.gmail.com> References: <67628d690905092248m194a5f63s15a9df09c8484319@mail.gmail.com> Message-ID: On May 9, 2009, at 11:48 PM, Lukas Renggli wrote: > On Sun, May 10, 2009 at 2:07 AM, David Farber > wrote: >> I have a registration form embedded in Pier page. >> +/mysite/MyForm+ > > A pier page? Not a component? How do you handle the submission? Right. Sorry. I have a component embedded in a Pier page. Submission works just fine. >> 1) How do I keep a user from submitting the form twice? > > You display something else. Sorry for not being clear. I am displaying something else, but I also want to prevent the user from using the back button to submit a form twice. Is that possible with a Pier component? >> 2) I would like to show a confirmation page after the form is >> submitted, but >> I would like for that page to a Pier-editable page. How could I >> accomplish >> that? > > If you add a description of the type MADocumentDescription you can > store one or more wiki documents with your component, that are then > displayed instead. I am not sure I understand. If I add a PRDocumentDescription, then there is another field on the form (with the text of the confirmation message.) I only want an administrator to be able to see and edit the confirmation message. Thanks, David ---- 1 Squeak/Seaside/Pier site deployed From renggli at gmail.com Wed May 27 21:13:56 2009 From: renggli at gmail.com (Lukas Renggli) Date: Wed, 27 May 2009 21:13:56 +0200 Subject: Two Pier Forms Questions In-Reply-To: References: <67628d690905092248m194a5f63s15a9df09c8484319@mail.gmail.com> Message-ID: <67628d690905271213j2caaa7fbo30a0503f9928ee0d@mail.gmail.com> >>> 1) How do I keep a user from submitting the form twice? >> >> You display something else. > > Sorry for not being clear. ?I am displaying something else, but I also want > to prevent the user from using the back button to submit a form twice. ?Is > that possible with a Pier component? Well, you can't prevent the back button, but your model could detect a double submit and inform the user. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From rdrvr.biz at gmail.com Thu May 28 19:00:41 2009 From: rdrvr.biz at gmail.com (David Farber) Date: Thu, 28 May 2009 11:00:41 -0600 Subject: Two Pier Forms Questions In-Reply-To: <67628d690905271213j2caaa7fbo30a0503f9928ee0d@mail.gmail.com> References: <67628d690905092248m194a5f63s15a9df09c8484319@mail.gmail.com> <67628d690905271213j2caaa7fbo30a0503f9928ee0d@mail.gmail.com> Message-ID: <3BC1DB64-E3AA-4AFB-8593-FED78B449490@gmail.com> On May 27, 2009, at 1:13 PM, Lukas Renggli wrote: >>>> 1) How do I keep a user from submitting the form twice? >>> >>> You display something else. >> >> Sorry for not being clear. I am displaying something else, but I >> also want >> to prevent the user from using the back button to submit a form >> twice. Is >> that possible with a Pier component? > > Well, you can't prevent the back button, but your model could detect a > double submit and inform the user. So there is no way to take advantage of isolate:? David ---- 1 Squeak/Seaside/Pier site deployed From renggli at gmail.com Thu May 28 20:55:41 2009 From: renggli at gmail.com (Lukas Renggli) Date: Thu, 28 May 2009 20:55:41 +0200 Subject: Two Pier Forms Questions In-Reply-To: <3BC1DB64-E3AA-4AFB-8593-FED78B449490@gmail.com> References: <67628d690905092248m194a5f63s15a9df09c8484319@mail.gmail.com> <67628d690905271213j2caaa7fbo30a0503f9928ee0d@mail.gmail.com> <3BC1DB64-E3AA-4AFB-8593-FED78B449490@gmail.com> Message-ID: <67628d690905281155x24e693d5kc3e9690be33bf36e@mail.gmail.com> > So there is no way to take advantage of isolate:? #isolate: wouldn't be useful, because this is not a sequence of components that are called from a single place. However you can build your own #isolate: that does exactly what you want. Lukas -- Lukas Renggli http://www.lukas-renggli.ch