seaside March 2014

seaside@lists.squeakfoundation.org

27 participants
28 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

Checkbox and AJAX?
by Mariano Martinez Peck 08 Jul '14

08 Jul '14

Hi guys, I have this piece of seaside that renders a checkbox: renderCellFormContent: anObject on: html html form: [ html label:[ html checkbox submitOnClick; value: (self isSelected: anObject); callback: [ :value | self selectRow: anObject value: value ]]] That checkbox is actually one table cell of a row of a table (the first column) to select/unselect items. I would like to make this checkbox go with an AJAX request so that the whole page is not rendered and hence I loose scroll position etc.... So..what I need is that in the onClick of the checkbox I send an AJAX request. The checkbox of course should be updated and I also need to be able to continue executing the callback and the value. Any idea how can I do this in Seaside? Thanks in advance, -- Mariano http://marianopeck.wordpress.com

5 18

debugging javascript within browsers is hard when the browser show the response on a single line
by Nick Ager 05 Jul '14

05 Jul '14

Hi, I wonder if other people suffer from the same problem when debugging javascript: Seaside's response is viewed by browsers as a string without line-breaks. Normally this isn't a problem as the browser "pretty-prints" the output when inspecting the html. However when debugging javascript, either inline or within a file-library the script debugger (I'm currently using Mac Safari) shows the output as a single line - which makes it impossible to interpret any javascript generated errors ("syntax error: line 1"!!) or to set meaningful breakpoints. I've discovered that calling #withInternetLineEndings on the file-library string results in browsers interpreting the line-endings as expected. Locally when I'm debugging I've created a class derived from WAHtmlDocument, which overrides #nextPutAll: WAHtmlDocumentWithInternetLineEndings>>#nextPutAll: aString super nextPutAll: aString withInternetLineEndings and I modify WAFileLibrary>>#handle: modifying the WAResponse>>#document: to: document: ((self documentForFile: fileName) withInternetLineEndings) Is there a better solution? Are there easier workarounds, browser settings etc. I created an issue for this problem: http://code.google.com/p/seaside/issues/detail?id=675 Though if there are easy workaround that I've missed, I'd be delighted to close the issue. Thanks Nick

6 13

Nginx Load-Balancing Experiences ?
by Sven Van Caekenberghe 24 Apr '14

24 Apr '14

Hi, I am about to try to figure out how to do sticky load-balancing for multiple Seaside instances using Nginx (I know how to do it using Apache). I currently have this working: upstream t3-mobile { server localhost:9090; # server localhost:9091; # server localhost:9092; # server localhost:9093; } server { listen 443 ssl; location / { proxy_pass http://t3-mobile; } } I just have to get the stickiness in. There seems to be a difference in available options between the open source and commercial versions. Any experiences, recommendations, pointers ? TIA, Sven

3 5

Re: [Seaside] [BUG] Die on Smalltalk snapshot:andQuit: (was: Nginx reverse proxying seaside problem)
by Laurent Laffont 27 Mar '14

27 Mar '14

Thanks Phil. If I comment code in WAServerManager>>shutDown, then it works (but when I really quit the image I have to manually start the adaptor again) Laurent Le jeudi 27 mars 2014, 11:56:51 phil(a)highoctane.be a écrit : > On Thu, Mar 27, 2014 at 9:32 AM, Laurent Laffont > <laurent.laffont(a)gmail.com>wrote: > > > Hi, > > > > > > > > take a fresh Seaside image > > > > ex: > > https://ci.inria.fr/pharo-contribution/job/Seaside/PHARO=20,VERSION=stable,… > > > > > > > > ZnZincServerAdaptor startOn:8080. > > > > > > > > then go to http://localhost:8080/status > > > > > > > > click 'Save' => boom > > > > > > Looks like it dies in: > > >>send: startUpOrShutDown toClassesNamedIn: startUpOrShutDownList with: > argument > "Send the message #startUp: or #shutDown: to each class named in the list. > The argument indicates if the system is about to quit (for #shutDown:) or if > the image is resuming (for #startUp:). > If any name cannot be found, then remove it from the list." > > | removals errors | > self halt. > removals := OrderedCollection new. > errors := OrderedCollection new. > * startUpOrShutDownList do: [ :name | * > * | class |* > * class := self at: name ifAbsent: [ nil ].* > * class isNil* > * ifTrue: [ removals add: name ]* > * ifFalse: [ * > * self * > * logStartUpErrorDuring: [ class perform: startUpOrShutDown with: argument > ] * > * into: errors * > * tryDebugger: false]].* > "Remove any obsolete entries, but after the iteration" > startUpOrShutDownList removeAll: removals. > ^ errors > > during #startUp > > The debugging of the method is quite hard as weird errors do pop up > > FWIW, the shutdown list looks like this (and I noticed that SpEnvironment > has no '>>isPharo' (isSqueak says 'yes'). :-( > > .[image: Inline image 1] > > Phil > > > > > > Laurent > > > > > > > > > > > > Le mercredi 26 mars 2014, 15:09:16 Sven Van Caekenberghe a écrit : > > > > > > > > > > On 26 Mar 2014, at 14:37, Laurent Laffont <laurent.laffont(a)gmail.com> > > wrote: > > > > > > > > > > > Thanks Johan, > > > > > > > > > > > > I use Seaside 3.1.1, Zinc-Seaside-SvenVanCaekenberghe.40 (.41 seems to > > be a minor change but I will try) > > > > > > > > > > That won't make much difference. I do assume you run the latest Zinc in > > Pharo 2 ? > > > > > > > > > > I have a similar setup and it works perfectly. It would be terrible if a > > simple callback would not work. > > > > > > > > > > There must be another reason, some configuration mismatch some where. I > > guess you can access the running Seaside image directly with success, right > > ? > > > > > > > > > > > Laurent > > > > > > > > > > > > Le mercredi 26 mars 2014, 13:50:14 Johan Brichau a écrit : > > > > > > > Nginx is telling you that the backend died. > > > > > > > > > > > > > > Since you are not reporting any Seaside exception handler popping > > up, it may be the Zinc adaptor. > > > > > > > Can you check that you have the latest Zinc adaptor? > > > > > > > > > > > > > > Also: which version of Seaside are you using? > > > > > > > > > > > > > > Johan > > > > > > > > > > > > > > On 26 Mar 2014, at 13:03, Laurent Laffont <laurent.laffont(a)gmail.com> > > wrote: > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > I have a simple seaside page, pharo 20, ZnZincServerAdaptor, Nginx > > on front, configuration: > > > > > > > > > > > > > > > > server { > > > > > > > > listen 80; > > > > > > > > server_name myserver.mydomain.fr; > > > > > > > > > > > > > > > > location / { > > > > > > > > proxy_pass http://localhost:8085; > > > > > > > > } > > > > > > > > } > > > > > > > > > > > > > > > > > > > > > > > > It works except on this code in a > > > > > > > > > > > > > > > > WAComponent subclass: #MyForm > > > > > > > > renderContentOn:html > > > > > > > > ..... > > > > > > > > ..... > > > > > > > > html submitButton > > > > > > > > callback: [self answer: site]; > > > > > > > > value: 'Save'. > > > > > > > > > > > > > > > > > > > > > > > > when I click the save button, Nginx raises 502 Bad Gateway error. > > In error log: > > > > > > > > > > > > > > > > > > > > > > > > "557 upstream prematurely closed connection while reading response > > header from upstream" > > > > > > > > > > > > > > > > Any idea ? > > > > > > > > > > > > > > > > Regards, > > > > > > > > > > > > > > > > Laurent > > > > > > > > _______________________________________________ > > > > > > > > seaside mailing list > > > > > > > > seaside(a)lists.squeakfoundation.org > > > > > > > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > seaside mailing list > > > > > > seaside(a)lists.squeakfoundation.org > > > > > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > > > > > > > > > > > _______________________________________________ > > seaside mailing list > > seaside(a)lists.squeakfoundation.org > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > >

1 0

Nginx reverse proxying seaside problem
by Laurent Laffont 27 Mar '14

27 Mar '14

Hi, I have a simple seaside page, pharo 20, ZnZincServerAdaptor, Nginx on front, configuration: server { listen 80; server_name myserver.mydomain.fr; location / { proxy_pass http://localhost:8085; } } It works except on this code in a WAComponent subclass: #MyForm renderContentOn:html ..... ..... html submitButton callback: [self answer: site]; value: 'Save'. when I click the save button, Nginx raises 502 Bad Gateway error. In error log: "557 upstream prematurely closed connection while reading response header from upstream" Any idea ? Regards, Laurent

4 6

html select question
by Murtaza Zaidi 26 Mar '14

26 Mar '14

Hi, I have a select list implemented as follows: id := html nextId. widget := html select. widget id: id; style: ('height: %1px; width: %2px; z-index: 101; position: relative; font-size: 11px; ' bindWith: self height printString with: self width printString); list: self getList; selected: self selectedItemString; onChange: (html jQuery ajax serializeThis); onChange: (self renderPortal: [self setSelectedItem: self selectedItem] on: html); callback: [:value | self selectedItem: (self getItemFrom: value)] I'm seeing an issue where sometimes, the second onChange event fires before the callback which produces the wrong result. The correct behaviour would be the execution of events as follows: onChange1 callback onChange2 So far, I've been unable to find a way to do this. Any help would be great. Thanks, Murtaza

2 1

Is the source for squeak.org available as a download
by gettimothy 26 Mar '14

26 Mar '14

First, thank you for the new site. It looks great. Is the source code for squeak.org available for people to putter with and try out new ideas? thx. tty

1 0

new website about Artefact
by olivier 24 Mar '14

24 Mar '14

Hi, A website is now available about Artefact. Documentation and useful informations are grouped to help you to produce many and beautiful PDF documents with Pharo. https://sites.google.com/site/artefactpdf/ The pasta team

2 1

Removing full refresh
by Murtaza Zaidi 24 Mar '14

24 Mar '14

Hi, I have an autocomplete implemented on a text input. It is defined in the following manner: widget := html textInput. widget script: ( html jQuery this autocomplete autoFocus: true; search: [:string | self getRows: string] labels: [:each | each formatSelectionRow] callback: [:value :script | script callback: [self updateValue: value]. self renderOn: html])) It is functional with a full refresh of the screen after a value is selected from the rows that get returned from the search block. I'm trying to remove this full refresh to improve user experience. Any ideas on how to do this? Thanks, Murtaza

4 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside March 2014