From nick.ager at gmail.com Fri Dec 2 19:19:01 2011 From: nick.ager at gmail.com (Nick Ager) Date: Fri, 2 Dec 2011 18:19:01 +0000 Subject: serving stylesheets Message-ID: Hi, For all the Pier distribution I've checked I've noticed that for each request the stylesheet was being served from a new Url. The relevant implementation is: MAFileModel>>url "Answer a link to a request handler for the given file." | handler | handler := MAFileModelHandler on: self. ^ WACurrentRequestContext value registry register: handler; urlFor: handler Which means that for every request for a file model's url, a new MAFileModelHandler is being created and registered. The result is: * The browser never caches the stylesheet * Each page request unnecessarily adds to the application's collection of handlers. Note: This is a generic Pier issue for PRFile requests, unless the url includes the query ?view=PRDownloadView OR MAExternalFileModel class baseUrl: has been defined). One solution would be to add ?view=PRDownloadView to the url for stylesheet requests or possibly for all file requests (modify MAExternalFileModel>>url to add ?view=PRDownloadView). However pondering the problem I've prototyped a solution in which PRFile have a custom view component "PRFileView" which responds with it's associated PRFile file directly, rather than delegating to MAFileModelHandler. The logic is that, by default, PRFile>>#url responds with a fully qualified path to itself within the pier structure e.g. /pier/template/style.css then PRFileView>>#initialRequest checks the request to see if it matches the mime-type of it's associated PRFile's mime-type, if so it will respond true to PRFileView>#isFullResponse and serve the file directly in PRFileView>#respondUsing: MAExternalFileModel class>>#baseUrl still works as intended and MAFileModel>>#url (and friends) remains unchanged. The result appears to be a neater solution than modify MAExternalFileModel>>url to add ?view=PRDownloadView, but I might be suffering from implementors bias :-) I thought I should check that: 1) people think it looks like a sensible fix and improvement 2) if (1) then whether I should delete MAFileModel>>#url (and friends), deprecate them, or leave them as is. Thanks Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From renggli at gmail.com Fri Dec 2 19:35:58 2011 From: renggli at gmail.com (Lukas Renggli) Date: Fri, 2 Dec 2011 19:35:58 +0100 Subject: serving stylesheets In-Reply-To: References: Message-ID: > However pondering the problem I've prototyped a solution in which PRFile > have a custom view component "PRFileView" which responds with it's > associated PRFile file directly, rather than delegating > to?MAFileModelHandler. The logic is that, by default, PRFile>>#url responds > with a fully qualified path to itself within the pier structure > e.g.?/pier/template/style.css then?PRFileView>>#initialRequest checks the > request to see if it matches the?mime-type of it's associated PRFile's > mime-type, if so it will respond true to??PRFileView>#isFullResponse and > serve the file directly in??PRFileView>#respondUsing: The problem is that like this you cannot easily navigate to the resource anymore. Lukas -- Lukas Renggli www.lukas-renggli.ch From nick.ager at gmail.com Fri Dec 2 19:49:18 2011 From: nick.ager at gmail.com (Nick Ager) Date: Fri, 2 Dec 2011 18:49:18 +0000 Subject: serving stylesheets In-Reply-To: References: Message-ID: > > The problem is that like this you cannot easily navigate to the > resource anymore. PRFileView>#isFullResponse only returns true is the mime-types match. So you can navigate to an image through the web interface as normal as the request mime-type will be text/html and not match the file's mime-type -------------- next part -------------- An HTML attachment was scrubbed... URL: From renggli at gmail.com Fri Dec 2 20:07:57 2011 From: renggli at gmail.com (Lukas Renggli) Date: Fri, 2 Dec 2011 20:07:57 +0100 Subject: serving stylesheets In-Reply-To: References: Message-ID: Aha, that sounds like a cool trick. Didn't think of that. So go for it. Lukas On 2 December 2011 19:49, Nick Ager wrote: >> The problem is that like this you cannot easily navigate to the >> resource anymore. > > > ?PRFileView>#isFullResponse only returns true is the mime-types match. So > you can navigate to an image through the web interface as normal as the > request mime-type will be text/html and not match the file's mime-type > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- Lukas Renggli www.lukas-renggli.ch From nick.ager at gmail.com Fri Dec 2 23:34:25 2011 From: nick.ager at gmail.com (Nick Ager) Date: Fri, 2 Dec 2011 22:34:25 +0000 Subject: serving stylesheets In-Reply-To: References: Message-ID: I've checked in the changes. After some more testing more I found that stylesheet requests for files are unhelpfully for mime-type "*/*" so I modified PRFileView to assume a #isFullResponse by default unless the request is a mime-type of WAMimeType textHtml. On 2 December 2011 19:07, Lukas Renggli wrote: > Aha, that sounds like a cool trick. Didn't think of that. So go for it. > > Lukas > > On 2 December 2011 19:49, Nick Ager wrote: > >> The problem is that like this you cannot easily navigate to the > >> resource anymore. > > > > > > PRFileView>#isFullResponse only returns true is the mime-types match. So > > you can navigate to an image through the web interface as normal as the > > request mime-type will be text/html and not match the file's mime-type > > > > _______________________________________________ > > Magritte, Pier and Related Tools ... > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > > -- > Lukas Renggli > 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 nick.ager at gmail.com Mon Dec 5 17:55:43 2011 From: nick.ager at gmail.com (Nick Ager) Date: Mon, 5 Dec 2011 16:55:43 +0000 Subject: pier admin update Message-ID: Hi, Since my initial post about Pier Admin I've fixed numerous bugs, added documentation and simplified the configuration. The WYSIWYG parser now parses tables, embedded lists, book index and reference links. To the best of my knowledge it should either understand or preserve all Pier markup. Let me know if not. I've also created a new book view - BOAggregatedView. From it's comment: I display my own structure and all my child structures if I answer true to > #isPublication. I format publication numbers as the default book template. > I provide an edit link for each child structure. The view allows you to view all the contents of a chapter or section at once. I'm couldn't find anything similar already in Pier, is there? I've discovered some cool Pier-EditorEnh functionality that I didn't know existed. If you click on a link button (in the enhanced wiki editor) without any text highlighted a popup window displays the site map and the available value links. Very cool. There was a small bug which prevented it working in Pier2, which should now be fixed. As ever Pier admin can be installed with: Gofer it > renggli: 'pier2addons'; > package: 'ConfigurationOfPierAdmin'; > load. > ConfigurationOfPierAdmin loadBleedingEdge. Let me know how you get along - feedback always appreciated. Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From gaston.dalloglio at gmail.com Mon Dec 5 22:23:10 2011 From: gaston.dalloglio at gmail.com (=?ISO-8859-1?Q?Gast=F3n_Dall=27_Oglio?=) Date: Mon, 5 Dec 2011 18:23:10 -0300 Subject: pier admin update In-Reply-To: References: Message-ID: Hi Nick. Is pieradmin.seasidehosting.st updated too? Are possible to add a text in the Pier Admin, where the users can see what version is running of it? I like very much Pier Admin. Thanks! 2011/12/5 Nick Ager > Hi, > > Since my initial post about Pier Admin I've fixed numerous bugs, added > documentation and simplified the configuration. The WYSIWYG parser now > parses tables, embedded lists, book index and reference links. To the best > of my knowledge it should either understand or preserve all Pier markup. > Let me know if not. > > I've also created a new book view - BOAggregatedView. From it's comment: > > I display my own structure and all my child structures if I answer true to >> #isPublication. I format publication numbers as the default book template. >> I provide an edit link for each child structure. > > > The view allows you to view all the contents of a chapter or section at > once. I'm couldn't find anything similar already in Pier, is there? > > I've discovered some cool Pier-EditorEnh functionality that I didn't know > existed. If you click on a link button (in the enhanced wiki editor) > without any text highlighted a popup window displays the site map and the > available value links. Very cool. There was a small bug which prevented it > working in Pier2, which should now be fixed. > > As ever Pier admin can be installed with: > > Gofer it >> renggli: 'pier2addons'; >> package: 'ConfigurationOfPierAdmin'; >> load. >> ConfigurationOfPierAdmin loadBleedingEdge. > > > Let me know how you get along - feedback always appreciated. > > Nick > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nick.ager at gmail.com Tue Dec 6 08:57:55 2011 From: nick.ager at gmail.com (Nick Ager) Date: Tue, 6 Dec 2011 07:57:55 +0000 Subject: pier admin update In-Reply-To: References: Message-ID: Hi Gast?n, Is pieradmin.seasidehosting.st updated too? > I updated it middle of last week - it isn't running the latest version, but a version with the parsing fixes in place. > Are possible to add a text in the Pier Admin, where the users can see what > version is running of it? > Possibly, though I think once Pier Admin seems stable enough I'll create a version 1.0 in the Metacello configuration (ConfigurationOfPierAdmin) - think Metacello versions are probably the best way to tracking versions as Pier Admin is build on top of many different components, so a Metacello snap-shot of components it probably the best way to handle this. > > I like very much Pier Admin. Thanks! > Good to hear, thanks Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From nick.ager at gmail.com Tue Dec 6 12:07:22 2011 From: nick.ager at gmail.com (Nick Ager) Date: Tue, 6 Dec 2011 11:07:22 +0000 Subject: Pier mobile view Message-ID: Hi, I vaguely remember some work was undertaken making a mobile view for Pier. Is it still available? How did/does it work? Custom templates, views? Did/does it select the view based on user agent? I was wondering about using jQueryMobile to create a mobile view - though as I write this perhaps a mobile rss reader and using Pier's rss support would fulfil a similar purpose? Thoughts? Cheers Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From gaston.dalloglio at gmail.com Tue Dec 6 13:19:15 2011 From: gaston.dalloglio at gmail.com (=?ISO-8859-1?Q?Gast=F3n_Dall=27_Oglio?=) Date: Tue, 6 Dec 2011 09:19:15 -0300 Subject: pier admin update In-Reply-To: References: Message-ID: Hi Nick > I updated it middle of last week - it isn't running the latest version, > but a version with the parsing fixes in place. > Fine, so the version online is continuously updated. I asked you because I would like share this with some friends.... > > Possibly, though I think once Pier Admin seems stable enough I'll create a > version 1.0 in the Metacello configuration (ConfigurationOfPierAdmin) - > think Metacello versions are probably the best way to tracking versions as > Pier Admin is build on top of many different components, so a Metacello > snap-shot of components it probably the best way to handle this. > Yes, of course at install level. But I'm thinking in the editors of the site, how know what is the version of Pier Admin (for choose doc to read for example)? But, maybe that is not very important for now. > > Good to hear, thanks > I'm very interested in the book format of Pier, with it I made the help system for my desktop apps running in the intranet, and now Pier Admin clean and simplify the work. Cheers. > > Nick > > _______________________________________________ > 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 Tue Dec 6 13:42:11 2011 From: renggli at gmail.com (Lukas Renggli) Date: Tue, 6 Dec 2011 13:42:11 +0100 Subject: Pier mobile view In-Reply-To: References: Message-ID: It was a new view using a new entry point. Should be easy to dispatch depending on user-agent using Seaside-REST or Apache. Was based on some Javascript/CSS iPhone library/theme. I think you can find it on my SqueakSource under the name iSea. Lukas On Tuesday, 6 December 2011, Nick Ager wrote: > Hi, > I vaguely remember some work was undertaken making a mobile view for Pier. Is it still available? How did/does it work? Custom templates, views? Did/does it select the view based on user agent? > I was wondering about using jQueryMobile to create a mobile view - though as I write this perhaps a mobile rss reader and using Pier's rss support would fulfil a similar purpose? Thoughts? > Cheers > Nick -- Lukas Renggli (mobile) http://www.lukas-renggli.ch -------------- next part -------------- An HTML attachment was scrubbed... URL: From nick.ager at gmail.com Tue Dec 6 15:08:39 2011 From: nick.ager at gmail.com (Nick Ager) Date: Tue, 6 Dec 2011 14:08:39 +0000 Subject: Pier mobile view In-Reply-To: References: Message-ID: Hi Lukas, I think you can find it on my SqueakSource under the name iSea. > Thanks - its really cool. Makes me realise that nothing is new - you had a jQueryMobile-lite implementation 3+years ago - amazing! Cheers Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From renggli at gmail.com Tue Dec 6 15:28:06 2011 From: renggli at gmail.com (Lukas Renggli) Date: Tue, 6 Dec 2011 15:28:06 +0100 Subject: Pier mobile view In-Reply-To: References: Message-ID: Ehh well, unfortunately it never made it quite out of the "hack" state. Great that you could pick it up. I guess it is not worth more than to demonstrate how to create an alternative web view. Lukas On Tuesday, 6 December 2011, Nick Ager wrote: > Hi Lukas, > >> I think you can find it on my SqueakSource under the name iSea. > > Thanks - its really cool. Makes me realise that nothing is new - you had a jQueryMobile-lite implementation 3+years ago - amazing! > Cheers > Nick > > -- Lukas Renggli (mobile) http://www.lukas-renggli.ch -------------- next part -------------- An HTML attachment was scrubbed... URL: From yanni at rogers.com Tue Dec 6 21:26:19 2011 From: yanni at rogers.com (Yanni Chiu) Date: Tue, 06 Dec 2011 15:26:19 -0500 Subject: Pier mobile view In-Reply-To: References: Message-ID: On 06/12/11 6:07 AM, Nick Ager wrote: > > I was wondering about using jQueryMobile to create a mobile view - > though as I write this perhaps a mobile rss reader and using Pier's rss > support would fulfil a similar purpose? Thoughts? All I did was: PRPierFrame subclass: #JQMPierFrame ... JQMPierFrame>>registerAsApplication: aString kernel: aKernel "self registerAsApplication: 'pier' kernel: (PRKernel instanceNamed: 'pier')" | app | app := JQMAdmin register: self asApplicationAt: aString. self configureApplication: app. app preferenceAt: #kernel put: aKernel. ^ app I can't remember all the additional tweaks I had to make, to get a mostly workable jQueryMobile look. (The Pier Browse view will need re-working to fit in with JQM, so that's a TODO). Unfortunately, the changes are one-way - i.e. the non-JQM web look is not easily available. It would be great to be able to choose the view based on user agent. I can put together what I have as a PierAddon, and then we can try to make it switchable based on user agent. Is there interest in doing this? From nick.ager at gmail.com Tue Dec 6 23:12:04 2011 From: nick.ager at gmail.com (Nick Ager) Date: Tue, 6 Dec 2011 22:12:04 +0000 Subject: Pier mobile view In-Reply-To: References: Message-ID: Hi Yanni, I can put together what I have as a PierAddon, and then we can try to make > it switchable based on user agent. Is there interest in doing this? > Sounds good. I'm still experimenting too. I was thinking that a good mobile view of the blog would be a good start. Followed by a way of reading pier books on a mobile device, that feels a little like the e-reader apps but delivered to the browser. A secondary focus would be to enable the administration tools within a mobile app. Something like the wordpress iOS app - http://ios.wordpress.org/ Still more thoughts than concrete ideas, but I would love to collaborate. Cheers Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From yanni at rogers.com Thu Dec 8 08:11:21 2011 From: yanni at rogers.com (Yanni Chiu) Date: Thu, 08 Dec 2011 02:11:21 -0500 Subject: Pier-JQueryMobile-Core uploaded to pier2addons Message-ID: The Pier-JQueryMobile-Core package, along with the attached 3 changesets (which override Pier/Magritte methods), need to be installed. Then run: PRJQueryMobileDistribution new register It's unfortunate that the changesets are needed. Maybe someone has a better way. Also attached are two screen shots of what you should see. You should have a default jQueryMobile UI for Pier. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: MAContainerDecoration-renderButtonsOn.st URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: MAContainerDecoration-renderContentOn.st URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: PREmbeddedRenderer-visitPage.st URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Picture 1.png Type: image/png Size: 228712 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Picture 4.png Type: image/png Size: 96472 bytes Desc: not available URL: From yanni at rogers.com Sun Dec 11 00:04:31 2011 From: yanni at rogers.com (Yanni Chiu) Date: Sat, 10 Dec 2011 18:04:31 -0500 Subject: Pier-JQueryMobile-Core uploaded to pier2addons In-Reply-To: References: Message-ID: On 08/12/11 2:11 AM, Yanni Chiu wrote: > The Pier-JQueryMobile-Core package, along with the attached 3 changesets > (which override Pier/Magritte methods), need to be installed. Oops, two more changesets attached. Fixes a problem with select lists. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: MAListCompositonComponent-renderEditorAvailableOn.st URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: MAListCompositonComponent-renderEditorSelectedOn.st URL: From sergiolist at village-buzz.com Sun Dec 11 06:42:29 2011 From: sergiolist at village-buzz.com (sergio_101) Date: Sun, 11 Dec 2011 00:42:29 -0500 Subject: using external design and css files.. Message-ID: was wondering how feasible it would be to use external design and css files with pier.. the thing i am finding is that i can fly through editing such files in my native text editor, but having to edit them in the web interface is slow and error prone. any ideas? thanks! -- ---- peace, sergio photographer, journalist, visionary http://www.CodingForHire.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101 From renggli at gmail.com Sun Dec 11 10:46:45 2011 From: renggli at gmail.com (Lukas Renggli) Date: Sun, 11 Dec 2011 10:46:45 +0100 Subject: using external design and css files.. In-Reply-To: References: Message-ID: I have the CSS of all my sites external. Just create a Seaside File Library, override #updateRoot: and load whatever styles, scripts, ... you need. Lukas On 11 December 2011 06:42, sergio_101 wrote: > was wondering how feasible it would be to use external design and css > files with pier.. > > the thing i am finding is that i can fly through editing such files in > my native text editor, but having to edit them in the web interface is > slow and error prone. > > any ideas? > > thanks! > > -- > ---- > peace, > sergio > photographer, journalist, visionary > > http://www.CodingForHire.com > http://www.coffee-black.com > http://www.painlessfrugality.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101 > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- Lukas Renggli www.lukas-renggli.ch From sergiolist at village-buzz.com Mon Dec 12 04:17:14 2011 From: sergiolist at village-buzz.com (sergio_101) Date: Sun, 11 Dec 2011 22:17:14 -0500 Subject: using external design and css files.. In-Reply-To: References: Message-ID: thanks, lukas.. i will do just that.. On Sun, Dec 11, 2011 at 4:46 AM, Lukas Renggli wrote: > I have the CSS of all my sites external. Just create a Seaside File > Library, override #updateRoot: and load whatever styles, scripts, ... > you need. > -- ---- peace, sergio photographer, journalist, visionary http://www.CodingForHire.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101 From sergiolist at village-buzz.com Thu Dec 15 03:18:36 2011 From: sergiolist at village-buzz.com (sergio_101) Date: Wed, 14 Dec 2011 21:18:36 -0500 Subject: using external design and css files.. In-Reply-To: References: Message-ID: oh! got the stylesheets.. what about the design files? can these be external? On Sun, Dec 11, 2011 at 4:46 AM, Lukas Renggli wrote: > I have the CSS of all my sites external. Just create a Seaside File > Library, override #updateRoot: and load whatever styles, scripts, ... > you need. > > Lukas > > On 11 December 2011 06:42, sergio_101 wrote: >> was wondering how feasible it would be to use external design and css >> files with pier.. >> >> the thing i am finding is that i can fly through editing such files in >> my native text editor, but having to edit them in the web interface is >> slow and error prone. >> >> any ideas? >> >> thanks! >> >> -- >> ---- >> peace, >> sergio >> photographer, journalist, visionary >> >> http://www.CodingForHire.com >> http://www.coffee-black.com >> http://www.painlessfrugality.com >> http://www.twitter.com/sergio_101 >> http://www.facebook.com/sergio101 >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > > -- > Lukas Renggli > www.lukas-renggli.ch > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- ---- peace, sergio photographer, journalist, visionary http://www.CodingForHire.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101 From b.prior at ieee.org Sat Dec 24 01:05:49 2011 From: b.prior at ieee.org (Bruce Prior) Date: Fri, 23 Dec 2011 16:05:49 -0800 Subject: Adding Seaside Components to Pier Blog Message-ID: <4EF5175D.7030703@ieee.org> I'm having little success with this. Nick Ager's recent documentation regarding Pier Admin has been very helpful in many other respects and has inspired me to pursue Pier further, but embedding a Seaside component or application seems to elude me. If I create a small Seaside application, how do I reference it so that it embeds in my blog? A small example sure would help. Many thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lenglish5 at cox.net Sat Dec 24 01:38:57 2011 From: lenglish5 at cox.net (Lawson English) Date: Fri, 23 Dec 2011 17:38:57 -0700 Subject: Adding Seaside Components to Pier Blog In-Reply-To: <4EF5175D.7030703@ieee.org> References: <4EF5175D.7030703@ieee.org> Message-ID: <4EF51F21.4080709@cox.net> About 2:20 into my tutorial: http://www.youtube.com/watch?v=vXb0A9o_u_k Lawson On 12/23/11 5:05 PM, Bruce Prior wrote: > I'm having little success with this. Nick Ager's recent documentation > regarding Pier Admin has been very helpful in many other respects and > has inspired me to pursue Pier further, but embedding a Seaside > component or application seems to elude me. > > If I create a small Seaside application, how do I reference it so that > it embeds in my blog? A small example sure would help. > Many thanks. > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -------------- next part -------------- An HTML attachment was scrubbed... URL: From b.prior at ieee.org Sat Dec 24 22:10:59 2011 From: b.prior at ieee.org (Bruce Prior) Date: Sat, 24 Dec 2011 13:10:59 -0800 Subject: Adding Seaside Components to Pier Blog In-Reply-To: <4EF51F21.4080709@cox.net> References: <4EF51F21.4080709@cox.net> Message-ID: <4EF63FE3.6080109@ieee.org> Hi Lawson, I see what you have done in your tutorial video, but I don't see how you got your Factorial1 component included in the component dropdown list in the first place so that you could select it. So I guess my question is: how do I add Seaside components or applications to the Pier component selection dropdown list? And a related question would be: does the component have to be a Seaside application or can it be a Seaside class component, ie a subclass of WAComponent? Many thanks for you help. Your video has been very useful to me. -------------- next part -------------- An HTML attachment was scrubbed... URL: From p3anoman at gmail.com Sat Dec 24 23:12:31 2011 From: p3anoman at gmail.com (John McKeon) Date: Sat, 24 Dec 2011 17:12:31 -0500 Subject: Adding Seaside Components to Pier Blog In-Reply-To: <4EF63FE3.6080109@ieee.org> References: <4EF51F21.4080709@cox.net> <4EF63FE3.6080109@ieee.org> Message-ID: Hi Bruce On Sat, Dec 24, 2011 at 4:10 PM, Bruce Prior wrote: > Hi Lawson, > > I see what you have done in your tutorial video, but I don't see how you > got your Factorial1 component included in the component dropdown list in > the first place so that you could select it. > > So I guess my question is: how do I add Seaside components or applications > to the Pier component selection dropdown list? > Implement canBeRoot on the class side of your component and make it ^true > > > And a related question would be: does the component have to be a Seaside > application or can it be a Seaside class component, ie a subclass of > WAComponent? > > Many thanks for you help. Your video has been very useful to me. > > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From b.prior at ieee.org Sun Dec 25 00:10:58 2011 From: b.prior at ieee.org (Bruce Prior) Date: Sat, 24 Dec 2011 15:10:58 -0800 Subject: Adding Seaside Components to Pier Blog In-Reply-To: References: Message-ID: <4EF65C02.5040800@ieee.org> Thankyou, John. I do have canBeRoot implemented. Perhaps I'm missing something obvious here? I am running Pier, and I'm in a blog, and I select Add. I get a dropdown menu named Type:. I select Component and then click the Add button. I get another dropdown menu named Component Class:. It has a long list of options but doesn't include the Seaside component that I want to embed and doesn't offer any other option that would lead me there. On Lawson's video it appears that he selects his component from this list but he says, "it's at the bottom where you can't see it." -------------- next part -------------- An HTML attachment was scrubbed... URL: From p3anoman at gmail.com Sun Dec 25 00:29:27 2011 From: p3anoman at gmail.com (John McKeon) Date: Sat, 24 Dec 2011 18:29:27 -0500 Subject: Adding Seaside Components to Pier Blog In-Reply-To: <4EF65C02.5040800@ieee.org> References: <4EF65C02.5040800@ieee.org> Message-ID: Pier also "humanizes" the name of the component for rendering the list. If your component class is ABComponentUI it will show up as Component U I (the common convention being that the first two letters of the class form the package prefix and are removed). This might cause it to show up in an unexpected sort order in the list On Saturday, December 24, 2011, Bruce Prior wrote: > > > Thankyou, John. I do have canBeRoot implemented. > Perhaps I'm missing something obvious here? I am running Pier, and I'm in a blog, and I select Add. I get a dropdown menu named Type:. > I select Component and then click the Add button. I get another dropdown menu named Component Class:. > It has a long list of options but doesn't include the Seaside component that I want to embed and doesn't offer any other option that would lead me there. On Lawson's video it appears that he selects his component from this list but he says, "it's at the bottom where you can't see it." > -------------- next part -------------- An HTML attachment was scrubbed... URL: From b.prior at ieee.org Sun Dec 25 06:11:19 2011 From: b.prior at ieee.org (Bruce Prior) Date: Sat, 24 Dec 2011 21:11:19 -0800 Subject: Adding Seaside Components to Pier Blog In-Reply-To: References: Message-ID: <4EF6B077.6000104@ieee.org> Many thanks, John. That was the clue I needed. My test component is BPPierTest. The dropdown menu includes an item named Pier Test. I had not recognized it as my component. It all works now. I think I'll leave Pier alone now for a few days and enjoy the holidays. Merry Christmas to you and to Lawson English. You were both a big help. Bruce -------------- next part -------------- An HTML attachment was scrubbed... URL: