seaside September 2016

seaside@lists.squeakfoundation.org

6 participants
8 discussions

isolate
by recursive68＠gmail.com 26 Nov '19

26 Nov '19

Hi, Given it looks like the isolate method is never going to added back to the current or future versions of Seaside as it's been an open bug issue for the last 5 years, how in general would go about replicating it's behaviour ? I think it's a shame as I think this sort of functionality made Seaside standout from the crowd as a web framework. Thanks

4 5

Seaside 3.2.0 final
by Johan Brichau 16 Aug '17

16 Aug '17

Hi everyone, Seaside 3.2.0 is now final: https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog <https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog> Check out the Github pages for more information: - https://github.com/SeasideSt/Seaside <https://github.com/SeasideSt/Seaside> - https://github.com/SeasideSt/Seaside/wiki <https://github.com/SeasideSt/Seaside/wiki> If you experience issues, do not hesitate to report an issue via Github. Special thanks goes to all those who have helped, tested or contributed in some other way!

14 26

Execute jQuery script upon #onAjaxComplete?
by Mariano Martinez Peck 26 Sep '16

26 Sep '16

Hi guys, I am trying to make some alerts/notifications to be displayed to users. For some internal reasons, these notifications are at server side. I have main component that on the #renderContentOn: does the render of the needed notifications. This works fine for normal requests as any "interaction" from the user with the app, will make a normal request causing a re-render of everything, included the notification component. The problem, as usual, is all ajax requests (and my app is now almost everything with ajax). I need to hook on ajax calls so that I could also re-render the notifications components as there could have been new notifications since the last rendering. I tried the following: html document addLoadScript: (html jQuery document onAjaxComplete: ( (html jQuery id: self systemMessageNotifier mainDivId) replaceWith: [:r | self systemMessageNotifier renderContentOn: r. ] )). But obviously that doesn't work because the onAjaxComplete: scripts ends being a hardcoded to the html of the current systemMessageNotifier component. In other words, the #renderContentOn: of the systemMessageNotifier is called only once...and not on every ajax complete. And I understand why. What I don't know how to do is what I want hahhaa. I would try to avoid WebSockets for the moment. I thought maybe doing some jQuery polling ? Thoughts? Thanks in advance, -- Mariano http://marianopeck.wordpress.com

2 7

Custom error handler for Seaside expiration and AJAX errors [ WAS ] Re: [Seaside] [AJAX] #script: & #html: vs #onSuccess: & #load & #html:
by Mariano Martinez Peck 24 Sep '16

24 Sep '16

Hi Cyril, For seaside expiration I do not hook on EACH ajax call but with a global handler: html document addLoadScript: (html jQuery document onAjaxError: (self ajaxErrorHandler asFunction: #('event' 'jqxhr' 'settings' 'exception'))). Note that this handler will take care of seaside expiration as well as errors in either rendering phase or callback phase from ajax calls. ajaxErrorHandler " If the ajax callback error was timeout...then we alert the user and forward to login again. If it was an ajax error callback, then we display a modal showing all the available error information. See #renderSupportForAjaxErrorHandlerOn: for more details. Also... note that in DpQuuveProductionWalkbackErrorHandler >> open: (our custom Seaside error handler for GemStone), when there is an AJAX error, in the response object we write a JSON serialized dictionary with all the error information (see #respondFromAjaxRequestWith:continuation:). Therefore, what we must do here is to read the response (will be JSON), parse that, and get the useful information. Finally, refresh the 'ajaxErrorDialog' with the error info we got and finally show the dialog. " ^ ' if (jqxhr.status == 403) { alert("For security reasons we sign people out during periods of inactivity. Please sign in again."); window.location.href = settings.url.split("?")[0].replace("help",""); } else { // This is on purpose because sometimes with TinyMCE we would get status 0 and empty error...when there was no error // The reason is explained in: http://bartwullems.blogspot.com.ar/2012/02/ajax-request-returns-status-0.ht… if (jqxhr.readyState == 0 || jqxhr.status == 0) { return; //Skip this error }; // Lets write to console all error info possbile var requestResponse = { url: settings.url, method: settings.type, data: settings.data, httpStatus: jqxhr.status, error: exception || jqxhr.statusText, data: settings.data }; responseText = jqxhr.responseText; responseText.replace(/[\\"'']/g, ''\\$&'').replace(/\u0000/g, ''\\0''); jsonValue = jQuery.parseJSON(responseText); console.error(jsonValue); $(''#ajaxErrorDialog'').find(''.errorTitle'').html(''<span style="color:#4F2817;">''+jsonValue.errorTitle+''</span>''); $(''#ajaxErrorDialog'').find(''.exceptionDescription'').html(''<span style="color:#4F2817;">''+jsonValue.exceptionDescription+''</span>''); $(''#ajaxErrorDialog'').find(''.dateAndTime'').html(''<span style="color:#4F2817;">''+jsonValue.dateAndTime+''</span>''); $(''#ajaxErrorDialog'').find(''.continuationOop'').html(''<span style="color:#4F2817;">''+jsonValue.continuationOop+''</span>''); $(''#ajaxErrorDialog'').find(''.packagesVersions'').html(''<span style="color:#4F2817;">''+jsonValue.packagesVersions+''</span>''); $(''#ajaxErrorDialog'').find(''.sitePrefix'').html(''<span style="color:#4F2817;">''+jsonValue.sitePrefix+''</span>''); $(''#ajaxErrorDialog'').find(''.user'').html(''<span style="color:#4F2817;">''+jsonValue.user+''</span>''); $(''#ajaxErrorDialog'').find(''.gemPid'').html(''<span style="color:#4F2817;">''+jsonValue.gemPid+''</span>''); $(''#ajaxErrorDialog'').find(''.gemSessionID'').html(''<span style="color:#4F2817;">''+jsonValue.gemSessionID+''</span>''); $(''#ajaxErrorDialog'').modal(''show''); }' And then, I also render my "ajaxErrorDialog" which is the component/dialog rendered when there is an ajax error: renderSupportForAjaxErrorHandlerOn: html html tbsModal id: 'ajaxErrorDialog'; with: [ html tbsModalDialog: [ html tbsModalContent: [ html tbsModalHeader: [ html tbsModalTitle level: 4; with: [ html tbsAlert beDanger with: [ html tbsGlyphIcon iconTime. html space. html text: 'Unexpected Error!'. html span style: 'text-color: white'; with: [ html tbsModalCloseIcon ] ] ] ]. html tbsModalBody: [ "This is a template div that is filled/replaced with the real text from DpQuuve >> ajaxErrorHandler" html text: 'The operation you tried failed because of an unexpected error. You may want to either try again, sign out and sign in and try again, or contact us about the error. However, note that other aspects of the program should continue to work normally.'. html break; break. html div with: [ html text: 'Error description: '. html span class: 'exceptionDescription' ]. html break. html div with: [ html text: 'Error ID: '. html span class: 'continuationOop' ]. html break. html div with: [ html text: 'Generated at: '. html span class: 'dateAndTime' ]. html break. html div with: [ html text: 'By user: '. html span class: 'user' ]. html break. html div with: [ html text: 'Site url: '. html span class: 'sitePrefix' ]. html break. html div with: [ html text: 'Packages: '. html span class: 'packagesVersions' ]. html break. html div with: [ html text: 'Gem PID: '. html span class: 'gemPid' ]. html break. html div with: [ html text: 'Gem Session ID: '. html span class: 'gemSessionID' ]. ] "html tbsModalFooter: [ html tbsButton: 'Close'. html tbsButton bePrimary; with: 'Save changes' ]" ] ] ] Hope this helps. Let me know if it is clear. If it is not yet, I can do (and I should do!) a blog post explaining better. Cheers, On Sat, Sep 24, 2016 at 8:15 AM, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com > wrote: > Le 24/09/2016 à 08:48, Johan Brichau a écrit : > > Hi Mariano, > > > > First button does a single ajax call and responds a js script. > > Second button does two ajax calls, first one without a response content, > second one with a html response content. > > > > Both achieve the same end result but the second one requires two > request-response cycles to your server. > > The second one will thus achieve the end result slower than the first > one. > > > > We typically also try to optimize as much as possible into single ajax > requests. > > > > Mind that you _can_ combine a single primary and multiple secondary > callback blocks into a single ajax call. > > A primary callback is a callback that responds a content to the client > (#script:, #html:, #json:, #text, ….) > > A secondary callback is a callback that does not respond content > (#callback:value:, #callback:passengers:, #callback:json: , …) > > There is an exception to this rule, #callback: is implemented in the > Seaside jQuery binding as a primary callback, even if it does not return > any content. > > > > Although for this example, I would actually write it as follows, because > the #callback: block is a primary callback. > > > > html button > > bePush; > > onClick: (html jQuery id: ‘myDivId’ load html: [:r > | | … do some other stuff …. then ... self renderMyDivOn: r. ] ) > > value: ‘Test’ > > > > Hi! > > With this example how is manage the case where the session expire? > In general I do: > > onClick: (html jQuery ajax > callback: [ ]; > onSuccess: ( (html jQuery id: 'myDivId') load html: [ :r | self > renderMyDivOn: r. ]); > onError: 'location.reload();' "probably session expiration"); > > > > Now, it also depends of the ‘myDivId’ is known when rendering the button > or not, but in this simple example this would yield the same result ;) > > > > cheers > > Johan > > > > > > _______________________________________________ > > seaside mailing list > > seaside(a)lists.squeakfoundation.org > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > > > -- > Cyril Ferlicot > > http://www.synectique.eu > > 2 rue Jacques Prévert 01, > 59650 Villeneuve d'ascq France > > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > -- Mariano http://marianopeck.wordpress.com

2 1

[AJAX] #script: & #html: vs #onSuccess: & #load & #html:
by Mariano Martinez Peck 24 Sep '16

24 Sep '16

Hi guys, Today I have a discussion with Esteban Maringolo and it looks we are both doing something different for a classical AJAX example. Consider the typical example of a click on a button that should trigger the re-render of a given DIV. I was using #script together with #html: while Esteban was using #onSuccess:/#onError: with #load and #html: I created a class for testing the differences. Very simple: renderContentOn: html self renderMyDivOn: html. html form: [ html button bePush; onClick: *(html jQuery ajax* * script: [ :s | **s << ((s jQuery id: 'myDivId' ) html: [:r | **self renderMyDivOn: r. **]) **]* * );* value: 'Test with #script: '. html button bePush; onClick: *(html jQuery ajax* * callback: [ ];* * onSuccess: ( (html jQuery id: 'myDivId') load html: [ :r | self renderMyDivOn: r. ] ) * *);* value: 'Test with #onSuccess:'. ] And renderMyDivOn: html html div id: 'myDivId'; with: [ html text: DateAndTime now greaseString. ] Both solutions works. But of course, they are different. The generated HTML is different too of course: <form accept-charset="utf-8" method="post" action="/reps?_s=pbHnnKA9Ys-E9FtR&_k=Wktdp8ek0iMZdSUY"> *<button onclick="$.ajax({"dataType":"script","url":"/reps","data":["_s=pbHnnKA9Ys-E9FtR","_k=Wktdp8ek0iMZdSUY","156"].join("&")})" type="button" class="button">Test with #script:</button>* *<button onclick="$.ajax({"url":"/reps","data":["_s=pbHnnKA9Ys-E9FtR","_k=Wktdp8ek0iMZdSUY","157"].join("&"),"success":function(){$("#myDivId").load("/reps",["_s=pbHnnKA9Ys-E9FtR","_k=Wktdp8ek0iMZdSUY","158"].join("&"))}})" type="button" class="button">Test with #onSuccess:</button>* </form> I am not an AJAX expert, so I wonder what are the differences, which is the recommended approach, and why. Thank you very much in advance. -- Mariano http://marianopeck.wordpress.com

3 3

Re: [Pharo-dev] [ANN] Material Design For Seaside V1.0.0
by Cyril Ferlicot D. 23 Sep '16

23 Sep '16

Le 23/09/2016 à 15:53, Christophe Demarey a écrit : > Cool! > Could you share a picture of the widgets by email or put it in the GitHub README? > > Thanks, > Christophe > Oups, I made "respond" instead of "respond to all". You can find the demo here: http://eph-b922e2d9.swarm.pharocloud.com/MDLComponentsDemoApplication Note that the code shown is decompile code. In the real application the names are better :) > > -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques Prévert 01, 59650 Villeneuve d'ascq France

1 0

seaside front-end testing tool pharo4.0
by lesage yann 23 Sep '16

23 Sep '16

Hello, I work for Synectique. We are trying to test telescope and all front end of our website. We have started to write tests in js on client-side with mocha on DOM(number of element, element visibility or css change...) We want to automate our tests with Jenkins and optionally launch this test from the Pharo image. We have planed to make this with mocha, xml reporter and take syntaxe from TestCase class. To avoid to reinvent the wheel, we have searched for existants solutions and found : - SeasideTesting -> don't load in Pharo 4.0 - Albatros : we have found the repo but the last version dates from 2010 and is based on squeak. So is there someone who test front-end in pharo4.0 with seaside and how ? Is There an existants and functional project ? Thanks for your answers Yann Lesage

3 5

[ANN] Material Design For Seaside V1.0.0
by Cyril Ferlicot D. 23 Sep '16

23 Sep '16

Hi everyone! I am happy to announce the version 1 of Material Design Lite for seaside. This version contains all components from V1.2.1 of Google's Material Design Lite (https://github.com/google/material-design-lite, http://getmdl.io) This version also contains some widget build in top of MDL as: Pagination widget Sorted Paginated Table Select Widget Poll Widget Calendar Widget Nested List with dynamic loading and search function Thanks to Kévin Lanvin, Olivier Auverlot, Thomas Heniart, Merwan Ouddane and Guillaume Larcheveque who helped to release this version. Thanks to Sabine Mana for the feedback she gave. You can find the project on: https://github.com/DuneSt/MaterialDesignLite There is some documentation of the README. If you find a bug you can open an issue on the repository. If you have some question I will be happy to answer. -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques Prévert 01, 59650 Villeneuve d'ascq France

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside September 2016