seaside May 2011

seaside@lists.squeakfoundation.org

48 participants
51 discussions

Re: [Seaside] onClick notifications for check box or multiSelect
by jsavidge＠texas.net 11 May '11

11 May '11

Greetings Lukas, On 5/10/11 11:47 AM, Lukas Renggli wrote: > #with: has to be last in the cascade. Always. Slime can detect this problem. > > Also there seems to be something wrong with the callbacks. You have > two independent AJAX requests. I don't think you need the #onClick: > one. I moved the >>with: to the end of the cascade, and I removed the >>onClick:, but that didnt seem to make a difference. The Transcript printing in my callback: was never executed. > There is a functional form test/example that demonstrates all the > form elements. I had been looking at examples before I got to this point, but I must not be looking at the correct ones. Are you referring to any of the following, or are there other examples that you would suggest? JQFormFunctionalTest>>renderCheckBoxOn: JQFormFunctionalTest>>renderMultiSelectListOn: JQButtonFunctionalTest>>renderCheckBoxOn: Scriptaculous.SUFormTest>>renderCheckBoxOn: Scriptaculous.SUFormTest>>renderMultiSelectListOn James T. Savidge, [jsavidge(a)texas.net], Tuesday, May 10, 2011 -- Dont worry Bob. Heres what to do. ... Raise the Exception, walkback, and nobody gets hurt. > HTH, > Lukas > > > > > On Tuesday, 10 May 2011, <jsavidge(a)texas.net> wrote: >> Greetings, >> >> Despite trying to follow the suggestions I have seen in the discussions and in >> the documentation, I cant seem to get onClick notifications to work on >> checkbox(s) or multiSelect. >> >> My goal is to present the user with a list of selections, and when they click >> on one of the items in the list, I want to refresh a secondary list with data >> that is related to selection they made in the first list. >> >> Attached is a file out for my attempt to get onClick to work on a checkbox by >> modifying the WACounter example. >> >> My testing have been in VisualWorks 7.7.1 + Seaside 3.0 - 7, and also in >> WebVelocity 1.1. Ive tried this in Firefox 3.x, 4.x, and Internet Explorer 8. >> >> Here is the method that is included in the attached file-out: >> >> ---------------------------------------------------------- >> WACounter>>renderContentOn: html >> html form: [ >> html heading: count. >> html anchor >> callback: [ self increase ]; >> with: '++'. >> html space. >> html anchor >> callback: [ self decrease ]; >> with: '--'. >> html checkbox >> with: 'Checkbox test'; >> onChange: ( html jQuery ajax serializeThisWithHidden ); >> onClick: ( html jQuery ajax callback: [ :selection | Transcript >> show: 'checkbox onClick hit.'. ] ); >> callback: [ :selection | Transcript show: 'checkbox callback hit.'. ]. >> ]. >> ---------------------------------------------------------- >> >> Am I missing something? >> >> James T. Savidge, [jsavidge(a)texas.net], Monday, May 9, 2011 >> -- >> >> Dont worry Bob. Heres what to do. ... Raise the Exception, walkback, and >> nobody gets hurt. >> >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

2 1

Re: [Seaside] Jquery dialog open vs. Chrome
by Robert Sirois 11 May '11

11 May '11

You know, I've had strange problems with chrome, too. Even had to go so far as rebooting, even though other browsers didn't have an issue. Gotta love technology ;) RS Thierry Thelliez <thierry.thelliez.tech(a)gmail.com> wrote: >Thanks for checking my code. I added the autoOpen. > >Restarting Chrome made it work. Strange... > >Thierry >_______________________________________________ >seaside mailing list >seaside(a)lists.squeakfoundation.org >http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >

1 0

Jquery dialog open vs. Chrome
by Thierry Thelliez 11 May '11

11 May '11

Hello, While creating a dialog with JQuery, I found that the following code works with FF, but not with Chrome. Under the later, nothing happens when clicking the 'Test' link. html div id: (id := html nextId); script: (html jQuery new dialog html: aComponent; title: 'Title'; height: 200; width: 400; resizable: false; modal: true). html anchor onClick: (( html jQuery id: id) dialog open); with: 'Test'. If I replace the anchor with a submitButton, the dialog works fine in the two browsers. Adding a fake url like 'url: '#'' did not help (it did help getting the right cursor type). Any suggestions? Thanks, Thierry

3 3

Re: [Seaside] JQuery / GLASS(Seaside 2.8)
by Robert Sirois 10 May '11

10 May '11

You don't really need seaside 3... you can always use the javascript facilities and write out the code in js. RS Sebastian Van Lacke <svanlacke(a)caesarsystems.com> wrote: >Hi, I need to know if It is possible to use JQuery within a Glass >1.0-beta.8.5 version (Seaside 2.8 ). Or, is it only available for Seaside >3.0? >I want to use the JQuery lightbox widget in particular, I understand it's on >JQuery-UI library. >If it is possible, how should* I *proceed to use it? > >Thanks > >Sebastian > >-- > >sebastian van lacke* *| web developer* *| *caesar systems *| *see clearly. >decide smarter.* > >svanlakce(a)caesarsystems.com <gamaral(a)caesarsystems.com> | t: +1.281.598.8790 >| t: +54.11.4389.0126 | petrovr.blogspot.com | www.caesarsystems.com > >**This message and any attached documents contain information from Caesar >Systems LLC that may be confidential/trade secret and/or privileged. If you >are not the intended recipient, you may not read, copy, distribute or use >this information. If you have received this transmission in error, please >notify the sender immediately by telephone or by reply e-mail and then >delete this message. > >_______________________________________________ >seaside mailing list >seaside(a)lists.squeakfoundation.org >http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

1 0

Following chapter 12.2 and encountering difficulties with my interpretation of
by Fritz Schenk 09 May '11

09 May '11

chapter 11.5 handling of the Cancel button. 1. A first try at following 11.5 fails when a second click on the Cancel button results in "Error: Object is not in the collection."; I am deleting aContact a second time. The copy is indeed added to the collection but it does not replace the collection entry corresponding to where aContact was obtained. 2. Further the editor subcomponent does not revert to its original state. 3. The list component is not updated when the contact name is changed. It appears that the callback containing the editor reference should be updated. A possible solution would be to deep copy the copy reference back into the aContact reference and do not remove the aContact entry. I need help in understanding how to properly handle Cancel when embedded components are involved. The code I have in the editContact method is <code> editContact: aContact | copy | copy := aContact copy. (editor contact: aContact) onAnswer: [ :answer | answer ifFalse: [ "aContact has changed contact regardless of whether editor answers true or false; copy has the original" MyContact removeContact: aContact. MyContact addContact: copy. "the editor view still has changed value; the view should be rerendered with original value (the copy)". ] </code>

1 2

Re: Seaside application deployment/migration/update
by Stephan Eggermont 05 May '11

05 May '11

Francois wrote: >How do you update your code and deal with model changes ? We develop in Pharo and run production in Gemstone. We started just scp-ing the monticello files and use Gemtools over remote X on ssh. Some model changes need migration scripts, but automigrate is enough about 70% of the iterations. We then moved to a combination of puppet (no server) and git, bash scripts, monticello files, gofer, and topaz scripts. Some patches we do directly with Gemtools. We are now moving to jenkins, vagrant and chef. Stephan

3 2

Re: [Seaside] Re: Seaside application deployment/migration/update
by Robert Sirois 04 May '11

04 May '11

Version uploader in tools is probably the easiest way to go. If you change something in your model such as deleting a variable, then that data goes away.. otherwise you can add on all you want. If you want to make a major change, you would want to merge the data to your new objects somehow. RS Francois Stephany <tulipe.moutarde(a)gmail.com> wrote: >> Hi the seaside admistrator app has a tool to upload a mcz with a new version and save the image or you can update a package from a monticello repository via RFB or Screen shot tools. > >I'm not that found of a GUI tool to administrate a server. Doesnt RFB >add too much bloat ? > >Is there any command line tool to do that ? > >> Whe you talk about change, how long are that changes. ? Is The new model incompatibe with the older.? >> Remember when you change the class structure, the compiler make the changes for all instances. > >But what happens to your existing data ? I know that I should store data >in a separate database but for the sake of simplicity I prefer to keep >my objects in the image while there are not too many data (the >application I have in mind is pretty simple concerning storage). > >> But that not enogh. You can persist the data in a chunck and recover late. > >So basically I could just serialize my data, throw the image and reload >the data in a new fresh image ? > >What do people generally do ? > >_______________________________________________ >seaside mailing list >seaside(a)lists.squeakfoundation.org >http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >

5 4

Seaside application deployment/migration/update
by Francois Stephany 04 May '11

04 May '11

Hi guys, I'm about to release my first real world Seaside app but I'm a bit confused. How do you update your code and deal with model changes ? My first guess would be "upload an mcz file in a folder and load it from the image (on a regular basis or by manually triggering an action in the admin section of my web application)." Do you have any other way to do it ? How do handle big changes in your models ? Do you use some sort of migration ? An other problem for me is how do you deal with multiple environments ? I'm used to have a development, a staging and a production environment. In dev for example, I want to use S3 in staging and prod but not in dev. Is there any convention/approach in this field ? I use migrations, Vlad the deployer and Rails.env everyday in ruby/rails and I wonder how to tackle them in Smalltalk/Seaside... Thanks, Francois

4 4

ajax html callback
by Milan Mimica 02 May '11

02 May '11

Hi! I've got a div that I want to re-render using an AJAX callback. The rendering of this div is isolated in a helper method: MyWAComopnent >> renderDivOn: html | id | html div id: (id := html nextId); with: [ html render: content ]. html ... (html jQuery id: id) load html: [ :h | self renderDivOn: h ]. The above does not work as expected because the AJAX actually replaces the *contents* of the queried DOM element, leaving you with an additional nested div tag on each rendering. Is there an easy fix to this, other than moving the rendering of the div tag to the outer level? -- Milan Mimica http://sparklet.sf.net

4 6

Seaside Sprint at ESUG this year?
by Donald MacQueen 02 May '11

02 May '11

Does anyone know if there are plans for this? -- Donald [|] A bad day in [] is better than a good day in {}

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 May 2011