seaside July 2014

seaside@lists.squeakfoundation.org

15 participants
14 discussions

[ANN] Rickshaw.js charting library for Seaside
by Esteban A. Maringolo 01 Oct '14

01 Oct '14

I just uploaded to SmalltalkHub an initial wrapper for the Rickshaw.js charting library (http://code.shutterstock.com/rickshaw/). As usual, you can load it with the following expression: Gofer it smalltalkhubUser: 'emaringolo' project: 'rickshaw'; package: 'ConfigurationOfRickshaw'; load. (Smalltalk at: #ConfigurationOfRickshaw) project development load: 'All' This will load all the packages, including a Seaside component installed at '/rickshaw' containing various examples. It is an initial version and my first package uploaded to SmalltalkHub, so bugs and and mistakes are expected :) Questions are welcome too. Regards, Esteban A. Maringolo

7 20

Re: Call for problems to be discussed at the Tutorial on Advanced Web Applications with Seaside
by Stephan Eggermont 22 Jul '14

22 Jul '14

Mike wrote: >I would really appreciate to hear a tutorial on sessions in Seaside. >I recently stumbled over the misuse of this object in my application and I found myself in a lot of bad code to have a workaround. The approach we use in Deltawerken and QCMagritte seems to work pretty well. Take a look at QCComponent, QCPageChoice, QCSession Stephan

1 0

Call for problems to be discussed at the Tutorial on Advanced Web Applications with Seaside
by Johan Brichau 22 Jul '14

22 Jul '14

Dale Henrichs, Philippe Marschall and myself organise a 'Sophisticated Web Applications with Seaside' tutorial on thursday at the ESUG Conference. We want this tutorial to be as practical as possible, so please send in the topics, problems, suggestions, you want to see discussed. Sending in a topic does not guarantee that we will handle it during the tutorial, but it will help us make the session as applied as possible. The abstract of the tutorial is: If you want to know everything about building sophisticated web applications with Seaside using tightly-integrated client-side libraries and frameworks (jQuery, jQuery++, jQuery-UI, Bootstrap, jQuery-Mobile,...), transparent persistence, RESTful webservices, etc or just about what's new in Seaside, then this tutorial is for you. We will skip the basics (see the excellent online tutorials [1][2] and book [3]) and jump right into the advanced uses of jQuery, the intricate details of ajax callbacks, the extensible framework, the transparent persistence in GemStone Web Edition (GLASS), and much more. We will reserve ample time for Q&A, so bring your questions to the session! See you at ESUG Johan

4 3

Rendering components in ajax
by Esteban A. Maringolo 21 Jul '14

21 Jul '14

Hi, I'm having a weird system lock-up situation with a component I render via JQLoad. And I started wondering if I'm doing something not appropriate in terms of seaside component rendering. tl;dr: I don't know the possible unwanted side effects and constraints of doing stuff like: ... (html jQuery: #mainContent) ajax load: [:ajaxHtml | ajaxHtml render: ComponentB new ] Long question: Basically I have an ajaxified component A, which renders a ComponentB, which in turns have javascript event handlers to do the same thing with a ComponentC, it is... in ComponentB I also have a JS event handler doing something like: ... (html jQuery: #detailView) ajax load: [:ajaxHtml | ajaxHtml render: ComponentC new ] ComponentC has some JS callbacks too, to perform some xhr calls to the server, etc. So far it works, but as said I don't know how this actually DOES work, because I can't see the JavaScript code of ComponentB and ComponentC in the Chrome DevTools, and I don't know if I'm leaking callbacks (attached to JS events) that will never be called in the server side. But what really is confusing me, is why if add a form (WAFormTag or TBSFormTag) to ComponentC, it locks up the image while rendering ComponentC. I don't know why this is so, but commenting out the rendering of the form keeps everything working as described above. Any clues? Thank you! Esteban A. Maringolo

2 2

How to built a JQDialog with a width that comes from a variable?
by Mariano Martinez Peck 17 Jul '14

17 Jul '14

Hi guys, I am currently creating a JQDialog. Such an object allows one to define a 'width'. But it can only be passed a number (pixels). In my case I want a special default..say $(window).width() * 0.9 I tried many ways of dealing with that and I failed completly. The way I create the script is this: scriptToOpenDialogOn: html value: value ((html jQuery: '#popupContainer') dialog close), ((html jQuery: '#popupContainer') dialog title: value second; html: value first; modal: false; autoOpen: true; draggable: true; resizable: false; position: 'top'; closeOnEscape: true; width: 900; addButton: 'Close' do: (html jQuery: '#popupContainer') dialog close) And that is appended to #script: of an ajax callback: scriptForPopupClickHandlerOn: html | val | val := ValueHolder new. ^ html jQuery this on: 'click' selector: '.clickablePopup' do: ((html jQuery ajax callback: [:pass | val contents: pass first ] passengers: (html jQuery this); script: [ :s | s << (self scriptToOpenDialogOn: s value: val contents) ]) asFunction: #(event)) Any ideas how could i make those 900 pixels to be a % of say..the width of the root document? Thanks in advance, -- Mariano http://marianopeck.wordpress.com

4 3

Re: problem loading seaside 3 in pharo 3
by Stephan Eggermont 15 Jul '14

15 Jul '14

>I’m trying to load ‘release3.0’ in Pharo 3 and I’m getting some warnings while trying to load grease… >I suppose I can load 3.1, but I juts wanted to let you know :) Yes, you could adapt the changes done for 3.1 (mostly FileSystem related, a.o. ensureCreateDirectory), and do a new version. No difficult changes, just boring work. Stephan

2 1

problem loading seaside 3 in pharo 3
by Esteban Lorenzano 15 Jul '14

15 Jul '14

Hi, I’m trying to load ‘release3.0’ in Pharo 3 and I’m getting some warnings while trying to load grease… I suppose I can load 3.1, but I juts wanted to let you know :) Esteban

1 0

Re: [Seaside] Basic question about AJAX and callbacks
by Winfried Jacobs 11 Jul '14

11 Jul '14

(sorry if this message comes up multiple times) Hello Mariano, JQAjax>>script: ist a callback, so you don't need both #callback: and #script: . Instead, you should merge both of your callback blocks into one: html jQuery ajax serializeChildren: (html jQuery: '#myFormID'); script: [ :s | "code from your first #callback: goes in here." "..." self halt. s << (s jQuery id: ('tr1')) replaceWith:[:r | r html: 'mariano' ] ] One possible reason why your code doesn't work: #callback: and #script: are primary callbacks, but you can only register one primary callback for an ajax object. However, you could register multiple secondary callbacks like #callback:value: #callback:json: etc. But in your case, a secondary callback is unnecessary. Cheers Winfried > Mariano Martinez Peck <marianopeck(a)gmail.com> hat am 11. Juli 2014 um 04:23 > geschrieben: > > Well...not there yet...now I am able to render the new table row with all the >'mariano'. And the row itself seems to reflect changes (the callback of the >ajax is really executed). The problem now is that I don't know how to make my >render script to happen AFTER the callback of the ajax. I tried #script: , >#onComplete: and #onSuccess: (just in case). What I need is to make the ajax >call, serialize the form, execute the ajax callback, and then do the replace of >the tr (with a script). > > The only one that seems to be executed later is #script: but when I do this, >the callback of the ajax is not executed. > > Any ideas? > > Thanks, > > > On Thu, Jul 10, 2014 at 6:22 PM, Mariano Martinez Peck <marianopeck(a)gmail.com ><mailto:marianopeck@gmail.com> > wrote: > > > ouuuuch > > > > sorrryyyy by bad hahahhaha. Very funny. I will explain later. Don't loose > >your time. > > > > Best, > > > > > > > > On Thu, Jul 10, 2014 at 6:00 PM, Esteban A. Maringolo > ><emaringolo(a)gmail.com <mailto:emaringolo@gmail.com> > wrote: > > > > > Maybe you should use #onComplete: instead of #script: in your > >JQAjax object. > > > _______________________________________________ > > > seaside mailing list > > > seaside(a)lists.squeakfoundation.org > > ><mailto:seaside@lists.squeakfoundation.org> > > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > > > -- > Mariano > http://marianopeck.wordpress.com > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >

2 2

The return of the Seaside control panel
by Johan Brichau 11 Jul '14

11 Jul '14

Hi, Latest Seaside 3.1.2 (soon to be released) features the Seaside Control Panel again that was broken in the previous versions on Pharo 3. Not all the functionality from the OB-based tool (dating back to Pharo 1.4) has been added yet, but at least you don't need to search for the code snippet to start an adaptor anymore. If you're interested to help out on some of the issues (like the new Spec-based control panel), join us for the Seaside sprint at ESUG in Cambridge! cheers! Johan

1 0

Basic question about AJAX and callbacks
by Mariano Martinez Peck 11 Jul '14

11 Jul '14

Hi guys, I am trying to have a button that instead of doing a form submit and a whole page render, simply serializes the form and tries to re-render something. My code is this: html tbsButton bePrimary; bePush; value: 'Save'; onClick: (html jQuery ajax serializeChildren: (html jQuery: '#myFormID'); callback: [ self halt. ] ; script: [ :s | self halt. s << (s jQuery id: ('tr1')) replaceWith:[:r | r html: 'mariano' ]] ) So I am declaring this button which is #bePush (to avoid a whole page render). Then with #serializeChildren I serialize the form (is this correct?), and finally with #script: I try to re-render again that row (in the example I simply display 'mariano'). 'tr1' is the correct id of the correct TR. I want #script: to be called AFTER the ajax callback. But it seems that if I define a #script: then the AJAX callback is not executed :( If I don't put the #script:, it is called... Also..when I click on that button, in the FF dev console I see "Use of attributes' specified attribute is deprecated. It always returns true.". Any ideas what I am doing wrong? Probably many things... Thanks in advance, -- Mariano http://marianopeck.wordpress.com

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside July 2014