From cyril.ferlicot at gmail.com Tue Aug 2 08:21:38 2016 From: cyril.ferlicot at gmail.com (Cyril Ferlicot Delbecque) Date: Tue Aug 2 08:21:43 2016 Subject: [Seaside] Execute code after an ajax code ended Message-ID: Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160802/eaa699b5/signature.pgp From cyril.ferlicot at gmail.com Tue Aug 2 08:37:12 2016 From: cyril.ferlicot at gmail.com (Cyril Ferlicot Delbecque) Date: Tue Aug 2 08:37:17 2016 Subject: [Seaside] Re: Execute code after an ajax code ended In-Reply-To: References: Message-ID: Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160802/3f30deb7/signature.pgp From marianopeck at gmail.com Mon Aug 8 16:58:48 2016 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Mon Aug 8 16:58:49 2016 Subject: [Seaside] FontAwesome update? Message-ID: Hi Torsten, We are using your great FontAwesome project since several months so far. Really nice! Thank you. Now, let me ask, is there a way to easily update it to 4.4? I guess you did not create all the extension methods by hand, so if it was a script maybe it is not that hard to update. Not only I would like to use new icons, but also some of the facilities like "Rotated & Flipped" that you can read in http://fontawesome.io/examples/. Finally.... if you can also provide that "magic" script to update, that would be terrific, so that we can easily update again for newer versions. Thank you very much in advance, -- Mariano http://marianopeck.wordpress.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160808/bc664748/attachment.htm From astares at gmx.de Mon Aug 8 17:57:02 2016 From: astares at gmx.de (Torsten Bergmann) Date: Mon Aug 8 17:57:05 2016 Subject: [Seaside] Aw: FontAwesome update? In-Reply-To: References: Message-ID: An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160808/3c9ba881/attachment.htm From marianopeck at gmail.com Mon Aug 8 18:45:38 2016 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Mon Aug 8 18:45:41 2016 Subject: [Seaside] Re: FontAwesome update? In-Reply-To: References: Message-ID: On Mon, Aug 8, 2016 at 2:57 PM, Torsten Bergmann wrote: > Dear Mariano, > > answer is simple: there is no (magic) script. So far the changes > between the versions were not much > and it was easy to update and provide them. > > What I usually did: > - create a separate new metadata file library and import the updated > new lib from a directory into Seaside > so that the methods for the CSS and fonts are created > - the move the methods to the appropriate FontAwesome class (either > developmont or deployment class > or the superclass if shared) > - add the necessary extension methods - each one with a test case > > May sound like boring work to create a method for each new possibility of > FontAwesome (and yes it is) - > but it helped me to go through all the features understand what can be > done with the framework. > Sorry if you thought there is magic involved... > > Hi Torsten, Thanks for your answer. I understand now. Sorry, I thought you had as script for that. Now...let's say I can live with hardcoding the css class of each icon..say: html span fontAwesome; fontAwesome2x; with: [ html span class: 'fa-header' ]. Then...all I would have to do is to update #cssfontawesomeCssContent to the latest CSS File and I should be ready to go, correct? Thanks in advance! > Thanks > Torsten > > *Gesendet:* Montag, 08. August 2016 um 18:58 Uhr > *Von:* "Mariano Martinez Peck" > *An:* "Seaside - general discussion" > *Cc:* "Torsten Bergmann" > *Betreff:* FontAwesome update? > Hi Torsten, > > We are using your great FontAwesome project since several months so far. > Really nice! Thank you. > > Now, let me ask, is there a way to easily update it to 4.4? I guess you > did not create all the extension methods by hand, so if it was a script > maybe it is not that hard to update. Not only I would like to use new > icons, but also some of the facilities like "Rotated & Flipped" that you > can read in http://fontawesome.io/examples/. > > Finally.... if you can also provide that "magic" script to update, that > would be terrific, so that we can easily update again for newer versions. > > Thank you very much in advance, > > -- > Mariano > http://marianopeck.wordpress.com > -- Mariano http://marianopeck.wordpress.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160808/e139e881/attachment-0001.htm From marianopeck at gmail.com Mon Aug 8 18:52:21 2016 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Mon Aug 8 18:52:23 2016 Subject: [Seaside] Re: FontAwesome update? In-Reply-To: References: Message-ID: On Mon, Aug 8, 2016 at 3:45 PM, Mariano Martinez Peck wrote: > > > On Mon, Aug 8, 2016 at 2:57 PM, Torsten Bergmann wrote: > >> Dear Mariano, >> >> answer is simple: there is no (magic) script. So far the changes >> between the versions were not much >> and it was easy to update and provide them. >> >> What I usually did: >> - create a separate new metadata file library and import the updated >> new lib from a directory into Seaside >> so that the methods for the CSS and fonts are created >> - the move the methods to the appropriate FontAwesome class (either >> developmont or deployment class >> or the superclass if shared) >> - add the necessary extension methods - each one with a test case >> >> May sound like boring work to create a method for each new possibility of >> FontAwesome (and yes it is) - >> but it helped me to go through all the features understand what can be >> done with the framework. >> Sorry if you thought there is magic involved... >> >> > > Hi Torsten, > > Thanks for your answer. > > I understand now. Sorry, I thought you had as script for that. > Now...let's say I can live with hardcoding the css class of each icon..say: > > html span > fontAwesome; > fontAwesome2x; > with: [ html span class: 'fa-header' ]. > > Then...all I would have to do is to update #cssfontawesomeCssContent to > the latest CSS File and I should be ready to go, correct? > > mmm I may also need to update the fonts methods such as #fontsfontawesomewebfontEotContent in case they changed with latest release... Do you recall how to generated those methods? Because we must create the ByteArray thingy out of those svg, ttf, file Thanks! > Thanks in advance! > > > >> Thanks >> Torsten >> >> *Gesendet:* Montag, 08. August 2016 um 18:58 Uhr >> *Von:* "Mariano Martinez Peck" >> *An:* "Seaside - general discussion" >> *Cc:* "Torsten Bergmann" >> *Betreff:* FontAwesome update? >> Hi Torsten, >> >> We are using your great FontAwesome project since several months so far. >> Really nice! Thank you. >> >> Now, let me ask, is there a way to easily update it to 4.4? I guess you >> did not create all the extension methods by hand, so if it was a script >> maybe it is not that hard to update. Not only I would like to use new >> icons, but also some of the facilities like "Rotated & Flipped" that you >> can read in http://fontawesome.io/examples/. >> >> Finally.... if you can also provide that "magic" script to update, that >> would be terrific, so that we can easily update again for newer versions. >> >> Thank you very much in advance, >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > > > -- > Mariano > http://marianopeck.wordpress.com > -- Mariano http://marianopeck.wordpress.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160808/9a8c49fb/attachment.htm From astares at gmx.de Mon Aug 8 21:56:32 2016 From: astares at gmx.de (Torsten Bergmann) Date: Mon Aug 8 21:56:34 2016 Subject: [Seaside] Aw: Re: FontAwesome update? In-Reply-To: References: , Message-ID: Mariano wrote: >mmm I may also need to update the fonts methods such as #fontsfontawesomewebfontEotContent in case they changed with latest release... >Do you recall how to generated those methods?? Because we must create the ByteArray thingy out of those svg, ttf, file As I said: 1. create a temporary package "MyTempPackage", create a simple class "MyTempLib" as subclass of WAFileMetadataLibrary 2. Extract the FontAwesome download into a directory and then evaluate MyTempLib recursivelyAddAllFilesIn: 'c:\pathToFontAwesome\' 3. now you have all the resources generated as methods in this temporary class. Now copy or move these methods over to the appropriate: Put it into - "FAWDevelopmentLibrary" when the resource is DEVELOPMENT related (for instance #cssfontawesomeCss with #cssfontawesomeCssContent - "FAWDeploymentLibrary" when the resource is DEPLOYMENT related (minified versions like #cssfontawesomeminCss with #cssfontawesomeminCssContent If a resource method is necessary for DEVELOPMENT and DEPLOYMENT move/copy it to the common superclass FAWFileLibrary This is because for easy debugging/development one would choose the FAWDevelopmentLibrary and for later deployment one would used the FAWDeploymentLibrary which provides the minimized versions. When are finished moving the methods over and it was already an existing method the Pharo diff tool in Monticello could show you if they really changed for the new FontAwesome version or stay with the same contents. Mostly all the files (also the fonts) change for an updated FontAwesome version, havent checked for the latest one. 4. Provide implementation and test methods: a) In package "FontAwesome-Core" add the necessary extension methods to class "WATagBrush" for the new provided FontAwesome CSS classes Follow the naming convention and let the method name start with "fontAwesome..." b) Dont forget to add a testcase for each of the new extension methods This can be done in package "FontAwesome-Tests-Core-Canvas" in Sunit class "FAWCanvasBrushTest" 5. Check if the example already includes the new stuff, for instance icons will be added automagicaly when following the naming convention. See FAWExamplesHome>>renderIconsOn: method how this is implemented. You can also add other examples to the class FAWExamplesHome. Double check that it is working on http://localhost:8080/fontawesome 6. When stable and all tests pass I usually update the ConfiguratonOfFontAwesome and release a new version (also in Catalog) Thats it. Hope it helps reproducing my steps. Thanks T. From manaa.sabine at gmail.com Wed Aug 10 11:39:48 2016 From: manaa.sabine at gmail.com (Sabine Manaa) Date: Wed Aug 10 11:39:51 2016 Subject: [Seaside] WAUrl absolute encoding for url with @ Message-ID: <1470829188890-4910307.post@n4.nabble.com> Hi, I want to add the following url to my header. aHtmlRoot script url: (WAUrl absolute: 'https://npmcdn.com/leaflet@1.0.0-rc.3/dist/leaflet.js') It fails (because of the encoding(?)) - it tries to load this: https://npmcdn.com/leaflet%401.0.0-rc.3/dist/leaflet.js Can anyone give me a hint what to do with the WAUrl to render correctly? I assume it is easy but I don't get it. Regards Sabine -- View this message in context: http://forum.world.st/WAUrl-absolute-encoding-for-url-with-tp4910307.html Sent from the Seaside General mailing list archive at Nabble.com. From karsten at heeg.de Wed Aug 10 12:43:22 2016 From: karsten at heeg.de (Karsten Kusche) Date: Wed Aug 10 12:43:49 2016 Subject: [Seaside] WAUrl absolute encoding for url with @ In-Reply-To: <1470829188890-4910307.post@n4.nabble.com> References: <1470829188890-4910307.post@n4.nabble.com> Message-ID: Hi Sabine, That?s probably a bug in one of the #decode: methods on class-side or #encodeOn: decides to encode the @ as Percent-Encoding. If it?s a bug in the #decode: methods you can create an empty WAUrl and add parts to the path manually. If it?s a bug in the #encodeOn: Methode you may need to fix the method. Karsten Am 10. August 2016 um 13:39:59, Sabine Manaa (manaa.sabine@gmail.com) schrieb: Hi, I want to add the following url to my header. aHtmlRoot script url: (WAUrl absolute: 'https://npmcdn.com/leaflet@1.0.0-rc.3/dist/leaflet.js') It fails (because of the encoding(?)) - it tries to load this: https://npmcdn.com/leaflet%401.0.0-rc.3/dist/leaflet.js Can anyone give me a hint what to do with the WAUrl to render correctly? I assume it is easy but I don't get it. Regards Sabine -- View this message in context: http://forum.world.st/WAUrl-absolute-encoding-for-url-with-tp4910307.html Sent from the Seaside General mailing list archive at Nabble.com. _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160810/118be7b6/attachment.htm From manaa.sabine at gmail.com Wed Aug 10 13:28:51 2016 From: manaa.sabine at gmail.com (Sabine Manaa) Date: Wed Aug 10 13:28:53 2016 Subject: [Seaside] Re: WAUrl absolute encoding for url with @ In-Reply-To: References: <1470829188890-4910307.post@n4.nabble.com> Message-ID: Hi Karsten, thank you! I just found out that aHtmlRoot javascript url: ' http://npmcdn.com/leaflet@1.0.0-rc.3/dist/leaflet.js' works. Regards Sabine 2016-08-10 14:43 GMT+02:00 Karsten Kusche [via Smalltalk] < ml-node+s1294792n4910313h98@n4.nabble.com>: > Hi Sabine, > > That?s probably a bug in one of the #decode: methods on class-side or > #encodeOn: decides to encode the @ as Percent-Encoding. > If it?s a bug in the #decode: methods you can create an empty WAUrl and > add parts to the path manually. If it?s a bug in the #encodeOn: Methode you > may need to fix the method. > > Karsten > > Am 10. August 2016 um 13:39:59, Sabine Manaa ([hidden email] > ) schrieb: > > Hi, > > I want to add the following url to my header. > aHtmlRoot script url: (WAUrl absolute: > 'https://npmcdn.com/leaflet@1.0.0-rc.3/dist/leaflet.js') > > It fails (because of the encoding(?)) - it tries to load this: > https://npmcdn.com/leaflet%401.0.0-rc.3/dist/leaflet.js > > Can anyone give me a hint what to do with the WAUrl to render correctly? > I assume it is easy but I don't get it. > > Regards > Sabine > > > > -- > View this message in context: http://forum.world.st/WAUrl- > absolute-encoding-for-url-with-tp4910307.html > Sent from the Seaside General mailing list archive at Nabble.com. > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > http://forum.world.st/WAUrl-absolute-encoding-for-url- > with-tp4910307p4910313.html > To start a new topic under Seaside General, email > ml-node+s1294792n86180h75@n4.nabble.com > To unsubscribe from WAUrl absolute encoding for url with @, click here > > . > NAML > > -- View this message in context: http://forum.world.st/WAUrl-absolute-encoding-for-url-with-tp4910307p4910321.html Sent from the Seaside General mailing list archive at Nabble.com. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160810/fa6d39d5/attachment-0001.htm From tudor at tudorgirba.com Thu Aug 25 09:56:24 2016 From: tudor at tudorgirba.com (Tudor Girba) Date: Thu Aug 25 09:56:29 2016 Subject: [Seaside] [ann] seaside gtdebugger Message-ID: Hi, As presented at ESUG on Monday, we now have a custom GTDebugger for Seaside. This was built by Andrei as an initial experiment. As we do not know much about Seaside-specific debugging problems, we asked a couple of Seaside users to describe issues that would be useful to be addressed in the debugger, and Andrei allocated some 4h to construct some of these in an custom debugger for Seaside. Two of the issues that popped up are: - get a quick view of the current request context - get an overview of the current component nesting They are now addressed like depicted in the screenshot below. You should look at this debugger as a beginning. Beside the current basic extensions one added value is that we now have the scaffolding to build more. Please take a look at it and let?s try to identify more concrete issues that might be addressed. It would be great if this would be taken over by the Seaside community. The debugger can be loaded on top of a Pharo 6.0 with Seaside inside like this: Gofer new smalltalkhubUser: 'Moose' project: 'GToolkit'; package: 'GT-SeasideDebugger'; load. #GTSeasideDebugger asClass register Cheers, Doru -- www.tudorgirba.com www.feenk.com "The coherence of a trip is given by the clearness of the goal." -------------- next part -------------- Skipped content of type multipart/related