From maarten.mostert at wanadoo.fr Thu Apr 2 12:26:14 2015 From: maarten.mostert at wanadoo.fr (Maarten Mostert) Date: Thu Apr 2 12:26:19 2015 Subject: [Seaside] Bootstrap Modal in Appex Message-ID: Hi, I have the following line of html I need to modal in javascript in order to get the closing cross in my bootstrap modal dialog. Bootstrap uses >× in order to show the multiplication cross character I use the following script to make the buttton. var aModalTopCloseButton = this.elementNameClass("button","close"); aModalTopCloseButton.setAttribute("data-dismiss", "modal"); var aSpan1 = document.createElement("span"); aSpan1.setAttribute("aria-hidden", "true"); aSpan1.appendChild(document.createTextNode("×")); aModalTopCloseButton.appendChild(aSpan1 ); aModalTopCloseButton.appendChild(this.spanWithClassText("sr-only","Close") ); The above however doesn't work it'll show me the modal like this. https://www.dropbox.com/s/m504ar91d4bhe3f/2015-04-02_14-13-50.png?dl=0 While it should look like this: https://www.dropbox.com/s/3x7izhemm4r7e8q/2015-04-02_14-14-50.png?dl=0 I am pritty sure there is a small detail I don't get. Thanks for any help. Maarten MOSTERT -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20150402/f378794b/attachment.htm From jtuchel at objektfabrik.de Thu Apr 2 12:41:18 2015 From: jtuchel at objektfabrik.de (Joachim Tuchel) Date: Thu Apr 2 12:41:15 2015 Subject: [Seaside] Bootstrap Modal in Appex Message-ID: I think you should just add the semicolon and a space at tehe end of the text node, just like in the html code Am 02.04.2015 14:26 schrieb Maarten Mostert : > > Hi, > > ? > > I have the following line of html I need to modal in javascript in order to get the closing cross in my bootstrap modal dialog. > > ? > > > > ? > > Bootstrap uses?>×??in order to show the?multiplication cross character > > ? > > I use the following script to make the buttton. > > ? > > var aModalTopCloseButton = this.elementNameClass("button","close"); > ? ? ? aModalTopCloseButton.setAttribute("data-dismiss", "modal"); > var aSpan1 = document.createElement("span");? > ? ? ? aSpan1.setAttribute("aria-hidden", "true"); > ? ? ? aSpan1.appendChild(document.createTextNode("×")); > > ? > > aModalTopCloseButton.appendChild(aSpan1 ); > aModalTopCloseButton.appendChild(this.spanWithClassText("sr-only","Close") );? > > ? > > The above however doesn't work it'll show me the modal like this. > https://www.dropbox.com/s/m504ar91d4bhe3f/2015-04-02_14-13-50.png?dl=0 > While it should look like this: > https://www.dropbox.com/s/3x7izhemm4r7e8q/2015-04-02_14-14-50.png?dl=0 > > ? > > I am pritty sure there is a small detail I don't get. > > ? > > Thanks for any help. > > ? > > ? > > Maarten MOSTERT From bsselfridge at gmail.com Thu Apr 2 19:19:24 2015 From: bsselfridge at gmail.com (bsselfridge@gmail.com) Date: Thu Apr 2 19:31:16 2015 Subject: [Seaside] JQMobile - MessageNotUnderstood: WADefaultScriptGenerator>>close:on:pageId: Message-ID: <1428002364570-4817026.post@n4.nabble.com> Getting the following error when rendering Seaside - JQMobile pages. Working with Pharo 3.0, Seaside 3, and latest JQMobile. Somewhere Seaside is still picking up the WADefaultScriptGenerator rather than the JQMScriptGenerator. ----- Brad Selfridge -- View this message in context: http://forum.world.st/JQMobile-MessageNotUnderstood-WADefaultScriptGenerator-close-on-pageId-tp4817026.html Sent from the Seaside General mailing list archive at Nabble.com. From pdebruic at gmail.com Thu Apr 2 21:17:12 2015 From: pdebruic at gmail.com (Paul DeBruicker) Date: Thu Apr 2 21:29:02 2015 Subject: [Seaside] Re: JQMobile - MessageNotUnderstood: WADefaultScriptGenerator>>close:on:pageId: In-Reply-To: <1428002364570-4817026.post@n4.nabble.com> References: <1428002364570-4817026.post@n4.nabble.com> Message-ID: <1428009432828-4817053.post@n4.nabble.com> Can you browse references to the WADefaultScriptGenerator class and go from there? I don't have JQMobile loaded so can't check it out. bsselfridge@gmail.com wrote > Getting the following error when rendering Seaside - JQMobile pages. > Working with Pharo 3.0, Seaside 3, and latest JQMobile. Somewhere Seaside > is still picking up the WADefaultScriptGenerator rather than the > JQMScriptGenerator. -- View this message in context: http://forum.world.st/JQMobile-MessageNotUnderstood-WADefaultScriptGenerator-close-on-pageId-tp4817026p4817053.html Sent from the Seaside General mailing list archive at Nabble.com. From sm at planage.com Fri Apr 3 05:53:31 2015 From: sm at planage.com (Sanjay Minni) Date: Fri Apr 3 06:05:25 2015 Subject: [Seaside] Dialog boxes initially display even with autoOpen: false Message-ID: <1428040411898-4817123.post@n4.nabble.com> Hi in the site uxfin.com i have some text content in the top 3 menu bar buttons. Though set to autoOpen: false - the page initially displays the contents and then hides after quite a delay. Is there a way to overcome this behaviour or should I change my design. Code snippet... html break. html div id: ( id := html nextId ); script: ( html jQuery new dialog title: 'Lightbox Dialog 1'; autoOpen: false; modal: true ); with: [ self renderUsersGuide: html ]. html anchor onClick: ( html jQuery id: id ) dialog open; with: 'Open lightbox 1'. regards Sanjay ----- --- Regards, Sanjay -- View this message in context: http://forum.world.st/Dialog-boxes-initially-display-even-with-autoOpen-false-tp4817123.html Sent from the Seaside General mailing list archive at Nabble.com. From stephan at stack.nl Fri Apr 3 08:25:41 2015 From: stephan at stack.nl (Stephan Eggermont) Date: Fri Apr 3 08:25:55 2015 Subject: [Seaside] Re: JQMobile - MessageNotUnderstood: WADefaultScriptGenerator>>close:on:pageId: In-Reply-To: <1428002364570-4817026.post@n4.nabble.com> References: <1428002364570-4817026.post@n4.nabble.com> Message-ID: On 02/04/15 21:19, bsselfridge@gmail.com wrote: > Getting the following error when rendering Seaside - JQMobile pages. Working > with Pharo 3.0, Seaside 3, and latest JQMobile. Somewhere Seaside is still > picking up the WADefaultScriptGenerator rather than the JQMScriptGenerator. Which version and what groups do you have loaded (of both Seaside and JQMobile)? I see that the last configuration was from 9 september 2012. That sounds like it was not kept up to date with the latest changes. A quick look in the configuration shows spec project: 'SeasideCore' with: [ spec className: 'ConfigurationOfSeaside30'; versionString: #stable; repository: 'http://www.squeaksource.com/MetacelloRepository' ]. You probably want to refer to both a newer repo, and a release version. And to be up to date with the latest seaside, you'll need a few changes Stephan From dmitri at zagidulin.net Fri Apr 10 17:51:22 2015 From: dmitri at zagidulin.net (Dmitri Zagidulin) Date: Fri Apr 10 17:51:25 2015 Subject: [Seaside] Seaside One Click Experience on Pharo 4? Message-ID: Are there any plans to update the old Seaside One Click Experience for Pharo 4.0 (and the latest stable Seaside)? And if not, what would be the level of effort required? (And/or, who would be the people to talk to, to set it up?) The reason I ask is, users new to web development on Pharo overwhelmingly get recommended to use the One Click images. - on http://www.seaside.st/download/pharo - "The Seaside One-Click Experience is the easiest way to get started with Seaside." Uses Pharo 1.4, I believe. - Learning Web Development with Seaside 3 ( http://seaside.gemtalksystems.com/tutorial/chapter01.pdf ) also points to the Pharo download link above. Same deal, 1.4. - Dynamic Web Development with Seaside (http://book.seaside.st/book ) also points to the One-Click. - Countless blog posts / tutorials link to it. - And, finally, Updated Pharo By Example (the Seaside chapter), also recommends the One Click image. Given how much work the community has done since Pharo 1.4, would it not make sense to update the integrated images? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20150410/e286d983/attachment.htm From johan at inceptive.be Sat Apr 11 07:43:24 2015 From: johan at inceptive.be (Johan Brichau) Date: Sat Apr 11 07:43:26 2015 Subject: [Seaside] Pillar package dependency Message-ID: Hi all, Can someone give me access to the Pillar repository or fix the issue below? I was trying to play around with Pier3 (which uses Pillar) but immediately hit an issue. When loading: Metacello new configuration: 'Pier3'; version: #'release3.1'; load. And then opening localhost:8080 pier gives you a DNU on MacOSXPlatform>>pillarLineEnding The issue is that the code of Pillar-Model (which is loaded by Pier) is dependent on Pillar-ExporterCore (which contains the method above). I think two things need to be done: - move the #pillarLineEnding method to the Pillar-Model - move the #pillarLineEnding method from Platform class to GRPlatform class to ease porting to other Smalltalks thanks Johan From hilaire at drgeo.eu Sat Apr 11 12:49:29 2015 From: hilaire at drgeo.eu (Hilaire) Date: Sat Apr 11 12:49:58 2015 Subject: [Seaside] Can't set id attribute Message-ID: Dear all, In the following circumstance the id is not set as an attribute of the inputField (last line): renderWidgetId: id on: html | tag inputField | tag := (html span) with: [ inputField := (html textInput) value: input; size: 10; callback: [ :val | self input: val ]. [...] ]; yourself. inputField id: id. Only when the id is set immediately, the id is correctly set: renderWidgetId: id on: html | tag inputField | tag := (html span) with: [ inputField := (html textInput) value: input; size: 10; id: id; callback: [ :val | self input: val ]. [...] ]; yourself. I need to set the id afterwards to factor out some code. There are probably other way I can do it, but I am really curious to know why the former code does not work. Thanks! Hilaire -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu From garduino at gmail.com Sat Apr 11 13:49:06 2015 From: garduino at gmail.com (garduino) Date: Sat Apr 11 14:01:58 2015 Subject: [Seaside] Re: [OT] Bootstrap resources In-Reply-To: References: Message-ID: <1428760146128-4819059.post@n4.nabble.com> Thanks for sharing Torsten! -- View this message in context: http://forum.world.st/OT-Bootstrap-resources-tp4813140p4819059.html Sent from the Seaside General mailing list archive at Nabble.com. From arning315 at comcast.net Sat Apr 11 15:01:10 2015 From: arning315 at comcast.net (Bob Arning) Date: Sat Apr 11 15:01:14 2015 Subject: [Seaside] Can't set id attribute In-Reply-To: References: Message-ID: <55293736.9070804@comcast.net> That's because when you reach the end of the with: block for the span, it flushes the canvas which closes the currentBrush (the textInput) if needed. IOW, by the time you try to set the id, all the html for the textInput has already been written. Try putting a self halt before inputField id: id and then explore html to see that this is the case On 4/11/15 8:49 AM, Hilaire wrote: > Dear all, > > In the following circumstance the id is not set as an attribute of the > inputField (last line): > > renderWidgetId: id on: html > | tag inputField | > tag := (html span) > with: [ > inputField := (html textInput) > value: input; > size: 10; > callback: [ :val | self input: val ]. > [...] > ]; > yourself. > inputField id: id. > > > Only when the id is set immediately, the id is correctly set: > > renderWidgetId: id on: html > | tag inputField | > tag := (html span) > with: [ > inputField := (html textInput) > value: input; > size: 10; > id: id; > callback: [ :val | self input: val ]. > [...] > ]; > yourself. > > > I need to set the id afterwards to factor out some code. There are > probably other way I can do it, but I am really curious to know why the > former code does not work. > > Thanks! > > Hilaire > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20150411/2999b210/attachment-0001.htm From hilaire at drgeo.eu Sat Apr 11 17:14:05 2015 From: hilaire at drgeo.eu (Hilaire) Date: Sat Apr 11 17:14:24 2015 Subject: [Seaside] Re: [OT] Bootstrap resources In-Reply-To: <1428760146128-4819059.post@n4.nabble.com> References: <1428760146128-4819059.post@n4.nabble.com> Message-ID: Yes, the examples looks great! Thanks Le 11/04/2015 15:49, garduino a ?crit : > Thanks for sharing Torsten! > > > > -- > View this message in context: http://forum.world.st/OT-Bootstrap-resources-tp4813140p4819059.html > Sent from the Seaside General mailing list archive at Nabble.com. -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu From self at je77.com Tue Apr 14 19:50:10 2015 From: self at je77.com (J.F. Rick) Date: Tue Apr 14 19:50:14 2015 Subject: [Seaside] Doubled Form Submit Message-ID: I've noticed that it happens occasionally that a user double clicks the form submit button, sending the form content to the server twice. Is there a standard way / pattern to avoid a post getting added twice? Cheers, Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20150414/7c6845ed/attachment.htm From emaringolo at gmail.com Tue Apr 14 19:52:11 2015 From: emaringolo at gmail.com (Esteban A. Maringolo) Date: Tue Apr 14 19:52:53 2015 Subject: [Seaside] Doubled Form Submit In-Reply-To: References: Message-ID: A javascript event handler to disable the submit button (and maybe form submission as well) once clicked. Regards! Esteban A. Maringolo 2015-04-14 16:50 GMT-03:00 J.F. Rick : > I've noticed that it happens occasionally that a user double clicks the form > submit button, sending the form content to the server twice. Is there a > standard way / pattern to avoid a post getting added twice? > > Cheers, > > Jeff > > _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > From philippe.marschall at gmail.com Wed Apr 15 08:02:16 2015 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Wed Apr 15 08:02:20 2015 Subject: [Seaside] Doubled Form Submit In-Reply-To: References: Message-ID: On Tue, Apr 14, 2015 at 9:50 PM, J.F. Rick wrote: > I've noticed that it happens occasionally that a user double clicks the form > submit button, sending the form content to the server twice. Is there a > standard way / pattern to avoid a post getting added twice? You could implement your own callback that is executed only once [1] [1] https://code.google.com/p/seaside/issues/detail?id=157 Cheers Philippe From self at je77.com Wed Apr 15 17:09:49 2015 From: self at je77.com (J.F. Rick) Date: Wed Apr 15 17:09:56 2015 Subject: [Seaside] Doubled Form Submit In-Reply-To: References: Message-ID: I ended up implementing the javascript event handler to disable the submit button (not too difficult). It seems crazy that a browser even allows for a form to be submitted multiple times. I once got into trouble because I was transferring money to my Paypal account and accidentally double clicked the submit button. It ended up processing the request twice and almost cost me an overdraft fee. It would be nice if seaside provided an elegant way to ensure that a form is only processed once. Cheers, Jeff On Wed, Apr 15, 2015 at 4:02 AM Philippe Marschall < philippe.marschall@gmail.com> wrote: > On Tue, Apr 14, 2015 at 9:50 PM, J.F. Rick wrote: > > I've noticed that it happens occasionally that a user double clicks the > form > > submit button, sending the form content to the server twice. Is there a > > standard way / pattern to avoid a post getting added twice? > > You could implement your own callback that is executed only once [1] > > [1] https://code.google.com/p/seaside/issues/detail?id=157 > > Cheers > Philippe > _______________________________________________ > 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/20150415/ac74ec11/attachment.htm From astares at gmx.de Thu Apr 16 10:43:30 2015 From: astares at gmx.de (Torsten Bergmann) Date: Thu Apr 16 10:43:32 2015 Subject: [Seaside] [ANN] Pharo 4.0 is released! Message-ID: see http://lists.squeakfoundation.org/pipermail/seaside-dev/2015-April/006438.htm From dmitri at zagidulin.net Thu Apr 16 15:08:18 2015 From: dmitri at zagidulin.net (Dmitri Zagidulin) Date: Thu Apr 16 15:08:20 2015 Subject: [Seaside] [ANN] Pharo 4.0 is released! In-Reply-To: References: Message-ID: That link gives a Not Found for me. Is there another one? On Thu, Apr 16, 2015 at 6:43 AM, Torsten Bergmann wrote: > see > http://lists.squeakfoundation.org/pipermail/seaside-dev/2015-April/006438.htm > _______________________________________________ > 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/20150416/13a49f33/attachment.htm From hilaire at drgeo.eu Mon Apr 20 09:04:51 2015 From: hilaire at drgeo.eu (Hilaire) Date: Mon Apr 20 09:04:54 2015 Subject: [Seaside] Re: Doubled Form Submit In-Reply-To: References: Message-ID: <5534C133.1020801@drgeo.eu> Hi, So Paypal does not have this level of safty.. Can you share your implementation? It very likely be useful to the communnity the next time one wants to learn from it. Thanks Hilaire Le 15/04/2015 19:09, J.F. Rick a ?crit : > I ended up implementing the javascript event handler to disable the > submit button (not too difficult). It seems crazy that a browser even > allows for a form to be submitted multiple times. I once got into > trouble because I was transferring money to my Paypal account and > accidentally double clicked the submit button. It ended up processing > the request twice and almost cost me an overdraft fee. It would be > nice if seaside provided an elegant way to ensure that a form is only > processed once. -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu From hilaire at drgeo.eu Wed Apr 22 16:34:32 2015 From: hilaire at drgeo.eu (Hilaire) Date: Wed Apr 22 16:34:47 2015 Subject: [Seaside] Seaside and Ajax Message-ID: Hi, This is a newbie question: What is the Seaside extension and documentation a beginner should look at regarding state of the start Ajax with Seaside? I read Scriptaculous, JQuery, Bootstrap but I don't know what to look at first and where to spend try & test time on. Thanks a lot Hilaire -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu From bsselfridge at gmail.com Wed Apr 22 18:13:04 2015 From: bsselfridge at gmail.com (bsselfridge@gmail.com) Date: Wed Apr 22 18:27:15 2015 Subject: [Seaside] Re: Seaside and Ajax In-Reply-To: References: Message-ID: <1429726384893-4821220.post@n4.nabble.com> Are you looking for some Seaside Ajax examples? ----- Brad Selfridge -- View this message in context: http://forum.world.st/Seaside-and-Ajax-tp4821173p4821220.html Sent from the Seaside General mailing list archive at Nabble.com. From johan at inceptive.be Wed Apr 22 18:37:19 2015 From: johan at inceptive.be (Johan Brichau) Date: Wed Apr 22 18:37:26 2015 Subject: [Seaside] Seaside and Ajax In-Reply-To: References: Message-ID: <81EED03F-03AB-4163-AF91-167DC975B72C@inceptive.be> Hi Hilaire, If you want to do ajax requests in Seaside, jQuery is the way to go. Scriptaculous itself is outdated (last update was 5 years ago) and everything you want to do with that can be done using jQuery and jQuery-UI. Bootstrap is a different thing: there are javascript components and styling elements (maybe a bit similar to jQuery-UI and some parts of scriptaculous). Take a look at the jQuery examples provided with Seaside (http://localhost:8080/javascript/jquery ) or the subclasses of JQFunctionalTest. I *know* there is a need for more elaborate documentation (in the book), though it?s really not that hard to understand from the examples. The *biggest* thing is that you must understand what jQuery is and does. If you try understanding how to work with jQuery by only looking at the Seaside binding, you _will_ get lost. Sorry if I try to stress too much, but I think this is where most Smalltalkers are going wrong: they don?t take a look at the jQuery documentation. So? my advice is: read jQuery documentation and examples, then take a look at how Seaside binds to that library. I?m sure you will understand. And I?m happy to answer questions if you have any on the road :) Johan > On 22 Apr 2015, at 18:34, Hilaire wrote: > > Hi, > > This is a newbie question: > > What is the Seaside extension and documentation a beginner should look > at regarding state of the start Ajax with Seaside? > I read Scriptaculous, JQuery, Bootstrap but I don't know what to look at > first and where to spend try & test time on. > > Thanks a lot > > Hilaire > > -- > Dr. Geo - http://drgeo.eu > iStoa - http://istoa.drgeo.eu > > > _______________________________________________ > 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/20150422/ea7e3858/attachment.htm From self at je77.com Fri Apr 24 15:37:36 2015 From: self at je77.com (J.F. Rick) Date: Fri Apr 24 15:37:40 2015 Subject: [Seaside] Re: Doubled Form Submit In-Reply-To: <5534C133.1020801@drgeo.eu> References: <5534C133.1020801@drgeo.eu> Message-ID: Sure. Though it is mainly a client-side solution. Here is the Javascript function: // jQuery plugin to prevent double submission of forms jQuery.fn.preventDoubleSubmission = function() { $(this).on('submit',function(e){ var $form = $(this); if ($form.data('submitted') === true) { // Previously submitted - don't submit again e.preventDefault(); } else { // Mark it so that the next submit can be ignored $form.data('submitted', true); } }); // Keep chainability return this; }; Then, here is how I used it in Seaside: (1) I give the form a unique ID (html nextId) and have that in a temporary variable id. (2) After the form has been added, I add the following to trigger the Javascript: html script: '$("#', id asString, '").preventDoubleSubmission;'. What this does is that it overrides default behavior to only submit the form once. It would be much nicer if this were taken care of at the server-side (something like "html submitOnceForm" instead of "html form") as you can never count on the client side to behave properly. Cheers, Jeff On Mon, Apr 20, 2015 at 5:05 AM Hilaire wrote: > Hi, > > So Paypal does not have this level of safty.. > Can you share your implementation? It very likely be useful to the > communnity the next time one wants to learn from it. > > Thanks > > Hilaire > > Le 15/04/2015 19:09, J.F. Rick a ?crit : > > I ended up implementing the javascript event handler to disable the > > submit button (not too difficult). It seems crazy that a browser even > > allows for a form to be submitted multiple times. I once got into > > trouble because I was transferring money to my Paypal account and > > accidentally double clicked the submit button. It ended up processing > > the request twice and almost cost me an overdraft fee. It would be > > nice if seaside provided an elegant way to ensure that a form is only > > processed once. > > -- > Dr. Geo - http://drgeo.eu > iStoa - http://istoa.drgeo.eu > > _______________________________________________ > 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/20150424/69beb3f5/attachment.htm From self at je77.com Fri Apr 24 15:49:34 2015 From: self at je77.com (J.F. Rick) Date: Fri Apr 24 15:49:37 2015 Subject: [Seaside] Infinite Scrolling Message-ID: I'm implementing a blog with many posts. I'd like to implement infinite scrolling so that only a few posts get loaded initially and then subsequent posts get loaded once the person scrolls to the bottom of the page. I'd like to use AJAX prepend to make this happen. Has anyone implemented something similar? Is there a good way to trigger a seaside ajax call based on an element appearing on screen or a scroll event reaching near the bottom? Cheers, Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20150424/b7f823b1/attachment.htm From mike at sharedlogic.ca Fri Apr 24 19:48:06 2015 From: mike at sharedlogic.ca (Michael J. Forster) Date: Fri Apr 24 20:02:31 2015 Subject: [Seaside] Re: Seaside and Ajax In-Reply-To: References: Message-ID: <1429904886101-4821712.post@n4.nabble.com> Hi Hilaire, To Johan's advice I'll simply add that Seaside's jQuery integration is fantastic. Once you understand jQuery itself, a regular Seaside component can be tweaked to use jQuery very easily. Cheers, Mike Forster -- View this message in context: http://forum.world.st/Seaside-and-Ajax-tp4821173p4821712.html Sent from the Seaside General mailing list archive at Nabble.com. From pbpublist at gmail.com Fri Apr 24 21:04:52 2015 From: pbpublist at gmail.com (Phil (list)) Date: Fri Apr 24 21:03:35 2015 Subject: [Seaside] Seaside form issue in Firefox and multiple open instances/windows Message-ID: <1429909492.2366.12.camel@gmail.com> I've been running into a situation where when I have the same page loaded in multiple browser windows. The page contains a form where the form fields will not be selectable (i.e. can't click to edit a text field) in the window having the 'oldest' (i.e. first loaded) page. My best guess is that there's a page element that needs a unique name/id that is shared between both windows as that's the only time I recall seeing anything similar to this before (the issue I'm remembering had nothing to do with Seaside though.) This isn't happening all of the time and I haven't yet been able to narrow it down to a reproducible test case but was wondering if this rings a bell with anyone who might have a solution or scenarios I should be looking out for? I'm running the latest Pharo-based Seaside with Firefox on Linux (haven't noticed this issue under Chrome yet) Thanks, Phil From hilaire at drgeo.eu Sat Apr 25 08:54:22 2015 From: hilaire at drgeo.eu (Hilaire) Date: Sat Apr 25 08:54:24 2015 Subject: [Seaside] Re: Doubled Form Submit In-Reply-To: References: <5534C133.1020801@drgeo.eu> Message-ID: <553B563E.60302@drgeo.eu> Le 24/04/2015 17:37, J.F. Rick a ?crit : > Sure. Though it is mainly a client-side solution. Here is the > Javascript function: Thanks to share. Hilaire -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu From hilaire at drgeo.eu Sat Apr 25 08:54:04 2015 From: hilaire at drgeo.eu (Hilaire) Date: Sat Apr 25 08:54:30 2015 Subject: [Seaside] Re: Seaside and Ajax In-Reply-To: <81EED03F-03AB-4163-AF91-167DC975B72C@inceptive.be> References: <81EED03F-03AB-4163-AF91-167DC975B72C@inceptive.be> Message-ID: Johan et al. Thanks for your tips. Hilaire Le 22/04/2015 20:37, Johan Brichau a ?crit : > If you want to do ajax requests in Seaside, jQuery is the way to go. > Scriptaculous itself is outdated (last update was 5 years ago) and > everything you want to do with that can be done using jQuery and > jQuery-UI. > Bootstrap is a different thing: there are javascript components and > styling elements (maybe a bit similar to jQuery-UI and some parts of > scriptaculous). > -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu From hilaire at drgeo.eu Sat Apr 25 09:47:37 2015 From: hilaire at drgeo.eu (Hilaire) Date: Sat Apr 25 09:48:01 2015 Subject: [Seaside] Re: Seaside and Ajax In-Reply-To: <81EED03F-03AB-4163-AF91-167DC975B72C@inceptive.be> References: <81EED03F-03AB-4163-AF91-167DC975B72C@inceptive.be> Message-ID: Le 22/04/2015 20:37, Johan Brichau a ?crit : > Take a look at the jQuery examples provided with Seaside > (http://localhost:8080/javascript/jquery) or the subclasses of > JQFunctionalTest. > Sadly this URL does not work from my Seaside previously installed on Pharo3 with the following script: Gofer new url:'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; package: 'ConfigurationOfSeaside3'; load. ((Smalltalk at: #ConfigurationOfSeaside3) project version: #stable) load. I guess some initialization was not properly done (the panel access was not present in the world menu as well). Thanks Hilaire -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu From hilaire at drgeo.eu Sat Apr 25 09:51:49 2015 From: hilaire at drgeo.eu (Hilaire) Date: Sat Apr 25 09:55:07 2015 Subject: [Seaside] Re: Seaside and Ajax In-Reply-To: References: <81EED03F-03AB-4163-AF91-167DC975B72C@inceptive.be> Message-ID: Le 25/04/2015 11:47, Hilaire a ?crit : > I guess some initialization was not properly done (the panel access was > not present in the world menu as well). Oops, no it is present. It was missing in another installation, and very likely a different setup. -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu From hilaire at drgeo.eu Sat Apr 25 12:28:34 2015 From: hilaire at drgeo.eu (Hilaire) Date: Sat Apr 25 12:28:49 2015 Subject: [Seaside] Re: Seaside and Ajax In-Reply-To: References: <81EED03F-03AB-4163-AF91-167DC975B72C@inceptive.be> Message-ID: One need to install at least Javascript-Test-Core and JQuery-Tests-Core. Should it not be in the ConfigurationOfSeaside as the Seaside welcome page comes with two links to jQuery and JQueryUI demos? Le 25/04/2015 11:47, Hilaire a ?crit : > Le 22/04/2015 20:37, Johan Brichau a ?crit : >> Take a look at the jQuery examples provided with Seaside >> (http://localhost:8080/javascript/jquery) or the subclasses of >> JQFunctionalTest. >> > Sadly this URL does not work from my Seaside previously installed on > Pharo3 with the following script: > > Gofer new > > url:'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; > package: 'ConfigurationOfSeaside3'; > load. > ((Smalltalk at: #ConfigurationOfSeaside3) project version: #stable) load. > > > I guess some initialization was not properly done (the panel access was > not present in the world menu as well). > > Thanks > > Hilaire > -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu From sean at clipperadams.com Sat Apr 25 14:40:40 2015 From: sean at clipperadams.com (Sean P. DeNigris) Date: Sat Apr 25 14:55:09 2015 Subject: [Seaside] Re: Warning on installing Seaside(3.1) on Pharo4.0 (build 40366) In-Reply-To: <1415857538034-4789949.post@n4.nabble.com> References: <1415857538034-4789949.post@n4.nabble.com> Message-ID: <1429972840113-4821799.post@n4.nabble.com> Sanjay Minni wrote > on trying to install Seaside on Pharo4 I get the following warning popup Sanjay, I stumbled upon this old thread. Hoepfully, you got this sorted long ago, but if not, Seaside 3.1 can now be installed on Pharo 4.0 via the Configuration Browser. HTH. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Warning-on-installing-Seaside-3-1-on-Pharo4-0-build-40366-tp4789949p4821799.html Sent from the Seaside General mailing list archive at Nabble.com. From sean at clipperadams.com Sat Apr 25 17:46:47 2015 From: sean at clipperadams.com (Sean P. DeNigris) Date: Sat Apr 25 18:01:18 2015 Subject: [Seaside] ConfigurationOfSeasideRest Message-ID: <1429984007523-4821836.post@n4.nabble.com> Is this obsolete now? I seemed to get the behavior with "ConfigurationOfSeaside3 load: 'REST'"... ----- Cheers, Sean -- View this message in context: http://forum.world.st/ConfigurationOfSeasideRest-tp4821836.html Sent from the Seaside General mailing list archive at Nabble.com. From johan at inceptive.be Sun Apr 26 12:37:18 2015 From: johan at inceptive.be (Johan Brichau) Date: Sun Apr 26 12:37:23 2015 Subject: [Seaside] ConfigurationOfSeasideRest In-Reply-To: <1429984007523-4821836.post@n4.nabble.com> References: <1429984007523-4821836.post@n4.nabble.com> Message-ID: Sean, REST is included in Seaside since 3.1 (as a group in the ConfigurationOfSeaside3), so the separate ConfigurationOf is only useful for Seaside 3.0 cheers Johan > On 25 Apr 2015, at 19:46, Sean P. DeNigris wrote: > > Is this obsolete now? I seemed to get the behavior with > "ConfigurationOfSeaside3 load: 'REST'"... > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/ConfigurationOfSeasideRest-tp4821836.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 From philippe.marschall at gmail.com Sun Apr 26 17:27:25 2015 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Sun Apr 26 17:27:28 2015 Subject: [Seaside] Seaside form issue in Firefox and multiple open instances/windows In-Reply-To: <1429909492.2366.12.camel@gmail.com> References: <1429909492.2366.12.camel@gmail.com> Message-ID: On Fri, Apr 24, 2015 at 11:04 PM, Phil (list) wrote: > I've been running into a situation where when I have the same page > loaded in multiple browser windows. The page contains a form where the > form fields will not be selectable (i.e. can't click to edit a text > field) in the window having the 'oldest' (i.e. first loaded) page. Can you inspect it with firebug or similar? Is it disabled in the DOM? Cheers Philippe From hilaire at drgeo.eu Sun Apr 26 21:47:16 2015 From: hilaire at drgeo.eu (Hilaire) Date: Sun Apr 26 21:47:32 2015 Subject: [Seaside] Jquery select then hide Message-ID: Hi, A classic problem I can't get through: Depending on a select answer I want to hide or show a node in the DOM tree. So far I try this with mixed result: (field := mold at: #civility) "a select tag" onChange: [ :aHtml | aHtml jQuery ajax serialize: aHtml jQuery this]; customize: [:selectTag | "just set the seside callback to the select tag" selectTag callback: [: val | field input: val. html jQuery ajax script: [ :s | val == #miss ifTrue: [s << (s jQuery: #maiden) show] ifFalse: [s << (s jQuery: #maiden) hide]] ] ]. The serialize part work (it took me some time to realize jQuery>>serialize does not much, but JAjax>serialize runs the form callback) The script part does not work. What I am mssing? A question about load: is it about updating a node with refreshed html rendering from the server? Thanks -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu From arning315 at comcast.net Sun Apr 26 22:57:00 2015 From: arning315 at comcast.net (Bob Arning) Date: Sun Apr 26 22:57:02 2015 Subject: [Seaside] Jquery select then hide In-Reply-To: References: Message-ID: <553D6D3C.4050507@comcast.net> This works for me: renderXYZ02: html | s1 choiceMade | choiceMade := '?'. html form with: [ html div id: 'maiden'; style: 'display: none'; with: [ html text: 'Enter maiden name' ]. s1 := html jQuery ajax callback: [ :value | choiceMade := value. ] value: (JSStream on: 'options[selectedIndex].text'); script: [ :s | choiceMade = 'miss' ifTrue: [s << (s jQuery: #maiden) show] ifFalse: [s << (s jQuery: #maiden) hide] ]. html select list: #('mr' 'ms' 'miss'); beOptional; onChange: s1; selected: nil. ]. On 4/26/15 5:47 PM, Hilaire wrote: > Hi, > > A classic problem I can't get through: Depending on a select answer I > want to hide or show a node in the DOM tree. > > So far I try this with mixed result: > > > (field := mold at: #civility) "a select tag" > onChange: [ :aHtml | aHtml jQuery ajax serialize: > aHtml jQuery this]; > customize: [:selectTag | "just set the seside > callback to the select tag" > selectTag callback: [: val | > field input: val. > html jQuery ajax script: [ :s | > val == #miss > ifTrue: [s << (s jQuery: #maiden) show] > ifFalse: [s << (s jQuery: #maiden) > hide]] > ] > ]. > > > The serialize part work (it took me some time to realize > jQuery>>serialize does not much, but JAjax>serialize runs the form callback) > The script part does not work. What I am mssing? > > > A question about load: is it about updating a node with refreshed html > rendering from the server? > > > Thanks > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20150426/c0f086a6/attachment-0001.htm From hilaire at drgeo.eu Mon Apr 27 08:50:34 2015 From: hilaire at drgeo.eu (Hilaire) Date: Mon Apr 27 08:51:13 2015 Subject: [Seaside] Re: Jquery select then hide In-Reply-To: <553D6D3C.4050507@comcast.net> References: <553D6D3C.4050507@comcast.net> Message-ID: Thanks for your tips. Based on your tips, I have to do it a bit differently as my select list is built from symbols (#mister, #miss #misses) and Seaside in that case, only store index number in the option list value attribute: Therefore the (JSStream on: 'options[selectedIndex].text') sent to the ajax callback these index number (1 2 or 3) and not my symbol. However I discover the 'html jQuery ajax serialize:' does two things: send the jqueried input field value to the server and fire its Seaside callback, where my symbol are known. (field := mold at: #civility) onChange: [ :aHtml | html jQuery ajax serialize: html jQuery this; script: [ :s | field input == #missis ifTrue: [s << (s jQuery: #maiden) show] ifFalse: [s << (s jQuery: #maiden) hide]] Now it seems to work locally, but stuff is uncoupled and asynchrone: do I have the risk the script is fired before the serialize is terminated? Thanks Hilaire Le 27/04/2015 00:57, Bob Arning a ?crit : > This works for me: > -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu From arning315 at comcast.net Mon Apr 27 10:24:53 2015 From: arning315 at comcast.net (Bob Arning) Date: Mon Apr 27 10:24:57 2015 Subject: [Seaside] Re: Jquery select then hide In-Reply-To: References: <553D6D3C.4050507@comcast.net> Message-ID: <553E0E75.3090503@comcast.net> no. if you put halts in the places shown below s1 := html jQuery ajax serialize: html jQuery this; script: [ :s | *self halt.* choiceMade = 'miss' ifTrue: [s << (s jQuery: #maiden) show] ifFalse: [s << (s jQuery: #maiden) hide] ]. html select list: #('mr' 'ms' 'miss'); beOptional; onChange: s1; callback: [ :value | *self halt.* choiceMade := value. ]; selected: nil. you'll see that the callback: happens before the script: because WACallbackRegistry has sorted the callbacks by priority before running them. On 4/27/15 4:50 AM, Hilaire wrote: > do I have the risk the script is fired before the serialize is terminated? > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20150427/e24b24d0/attachment.htm From pdebruic at gmail.com Mon Apr 27 23:20:14 2015 From: pdebruic at gmail.com (Paul DeBruicker) Date: Mon Apr 27 23:35:04 2015 Subject: [Seaside] Re: Infinite Scrolling In-Reply-To: References: Message-ID: <1430176814666-4822313.post@n4.nabble.com> I made an JQWidgetBox endless scroll widget a while ago, but never shared it I guess. I just uploaded it to Smalltalkhub. see: http://smalltalkhub.com/#!/~Seaside/JQueryWidgetBox Its a plugin for https://github.com/fredwu/jQuery-Endless-Scroll I'm not sure if/how the Widget is out of sync with the JS code in the git repo but its a start. I used it like this: renderEndlessScroll: html with: aRequest with: id html script: (((html jQuery id: id) endlessScroll) fireDelay: 5000; fireOnce: true; bottomPixels: 850; insertAfter: '.results:visible:last'; visible: '#' , id; callback: (html jQuery ajax script: [ :s | s << (s jQuery class: 'loader') show. s << (s jQuery class: 'results:visible:last') replaceWith: [ :h | | moreItems | moreItems := self getMoreResults: aRequest. self renderMoreItems: moreItems from: aRequest at: id on: h ]. s << (s jQuery class: 'shown:visible') replaceWith: [ :h | (h span) class: 'shown'; with: [html strong: aRequest results oldResults size asStringWithCommas ] ] ])) jrick wrote > I'm implementing a blog with many posts. I'd like to implement infinite > scrolling > <http://www.sitepoint.com/jquery-infinite-scrolling-demos/> so > that only a few posts get loaded initially and then subsequent posts get > loaded once the person scrolls to the bottom of the page. I'd like to use > AJAX prepend to make this happen. > > Has anyone implemented something similar? Is there a good way to trigger a > seaside ajax call based on an element appearing on screen or a scroll > event > reaching near the bottom? > > Cheers, > > Jeff > > _______________________________________________ > seaside mailing list > seaside@.squeakfoundation > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside -- View this message in context: http://forum.world.st/Infinite-Scrolling-tp4821669p4822313.html Sent from the Seaside General mailing list archive at Nabble.com. From johan at inceptive.be Tue Apr 28 07:21:05 2015 From: johan at inceptive.be (Johan Brichau) Date: Tue Apr 28 07:21:09 2015 Subject: [Seaside] Jquery select then hide In-Reply-To: References: <553D6D3C.4050507@comcast.net> Message-ID: Hi Hilaire, I wonder: do you really need the value server-side? If you just want to manipulate the DOM but not send any value server-side, I would do it like this: (field := mold at: #civility) onChange: (html jQuery this value) equals: ?missis? asJavascript then: (html jQuery: #maiden) show then: (html jQuery: #maiden) hide) This will avoid doing a server-side call and has the advantage of immediate updating on your webbrowser without the delay of a server round-trip. Also, in this case, the generation of the javascript is small and readable, but for such ?static? javascript, it?s better to put them in a separate file and only call the necessary function from your Seaside code. For example: (field := mold at: #civility) onChange: (html javascript call: ?maidenToggle? with: (html jQuery this)) cheers, Johan > On 27 Apr 2015, at 10:50, Hilaire wrote: > > Thanks for your tips. > > Based on your tips, I have to do it a bit differently as my select list > is built from symbols (#mister, #miss #misses) and Seaside in that case, > only store index number in the option list value attribute: > > > > > > > Therefore the (JSStream on: 'options[selectedIndex].text') sent to the > ajax callback these index number (1 2 or 3) and not my symbol. > > However I discover the 'html jQuery ajax serialize:' does two things: > send the jqueried input field value to the server and fire its Seaside > callback, where my symbol are known. > > (field := mold at: #civility) > onChange: [ :aHtml | > html jQuery ajax > serialize: html jQuery this; > script: [ :s | > field input == #missis > ifTrue: [s << (s jQuery: #maiden) show] > ifFalse: [s << (s jQuery: #maiden) hide]] > > Now it seems to work locally, but stuff is uncoupled and asynchrone: > do I have the risk the script is fired before the serialize is terminated? > > Thanks > > Hilaire > > Le 27/04/2015 00:57, Bob Arning a ?crit : >> This works for me: >> > > -- > Dr. Geo - http://drgeo.eu > iStoa - http://istoa.drgeo.eu > > > _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside From johan at inceptive.be Tue Apr 28 07:24:37 2015 From: johan at inceptive.be (Johan Brichau) Date: Tue Apr 28 07:24:41 2015 Subject: [Seaside] Seaside and Ajax In-Reply-To: References: <81EED03F-03AB-4163-AF91-167DC975B72C@inceptive.be> Message-ID: The ConfigurationOfSeaside3 for all 3.1 versions only loads Seaside core as a default. You need to add groups to your load expression if you want them. This was done with the mindset of customizable loads for everyone but ... Since people expected the inverse, the configuration for 3.2 has changed this and will load everything by default. If people want specific groups only, they can still do it. However, we should not change this for 3.1 as it might break other configurations, so we have to live with it until 3.2 is the stable version. Johan > On 25 Apr 2015, at 14:28, Hilaire wrote: > > One need to install at least Javascript-Test-Core and JQuery-Tests-Core. > Should it not be in the ConfigurationOfSeaside as the Seaside welcome > page comes with two links to jQuery and JQueryUI demos? > > Le 25/04/2015 11:47, Hilaire a ?crit : >> Le 22/04/2015 20:37, Johan Brichau a ?crit : >>> Take a look at the jQuery examples provided with Seaside >>> (http://localhost:8080/javascript/jquery) or the subclasses of >>> JQFunctionalTest. >>> >> Sadly this URL does not work from my Seaside previously installed on >> Pharo3 with the following script: >> >> Gofer new >> >> url:'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; >> package: 'ConfigurationOfSeaside3'; >> load. >> ((Smalltalk at: #ConfigurationOfSeaside3) project version: #stable) load. >> >> >> I guess some initialization was not properly done (the panel access was >> not present in the world menu as well). >> >> Thanks >> >> Hilaire >> > > > -- > Dr. Geo - http://drgeo.eu > iStoa - http://istoa.drgeo.eu > > > _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside From self at je77.com Tue Apr 28 14:08:07 2015 From: self at je77.com (J.F. Rick) Date: Tue Apr 28 14:08:14 2015 Subject: [Seaside] Re: Infinite Scrolling In-Reply-To: <1430176814666-4822313.post@n4.nabble.com> References: <1430176814666-4822313.post@n4.nabble.com> Message-ID: Cool. Thanks for sharing. On Mon, Apr 27, 2015 at 7:35 PM Paul DeBruicker wrote: > I made an JQWidgetBox endless scroll widget a while ago, but never shared > it > I guess. I just uploaded it to Smalltalkhub. see: > http://smalltalkhub.com/#!/~Seaside/JQueryWidgetBox > > Its a plugin for https://github.com/fredwu/jQuery-Endless-Scroll > > I'm not sure if/how the Widget is out of sync with the JS code in the git > repo but its a start. > > > I used it like this: > > > renderEndlessScroll: html with: aRequest with: id > > html > script: > (((html jQuery id: id) endlessScroll) > fireDelay: 5000; > fireOnce: true; > bottomPixels: 850; > insertAfter: '.results:visible:last'; > visible: '#' , id; > callback: > (html jQuery ajax > script: [ > :s | > s > << (s jQuery class: 'loader') show. > s > << (s jQuery class: 'results:visible:last') > > replaceWith: [ :h | | moreItems | > > moreItems := self getMoreResults: aRequest. > > self renderMoreItems: moreItems from: aRequest at: id on: h ]. > s > << (s jQuery class: 'shown:visible') > > replaceWith: [ :h | > > (h span) > > class: 'shown'; > > with: [html strong: aRequest results oldResults size > asStringWithCommas ] ] ])) > > > > > jrick wrote > > I'm implementing a blog with many posts. I'd like to implement infinite > > scrolling > > <http://www.sitepoint.com/jquery-infinite-scrolling-demos/> so > > that only a few posts get loaded initially and then subsequent posts get > > loaded once the person scrolls to the bottom of the page. I'd like to use > > AJAX prepend to make this happen. > > > > Has anyone implemented something similar? Is there a good way to trigger > a > > seaside ajax call based on an element appearing on screen or a scroll > > event > > reaching near the bottom? > > > > Cheers, > > > > Jeff > > > > _______________________________________________ > > seaside mailing list > > > seaside@.squeakfoundation > > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > > > > -- > View this message in context: > http://forum.world.st/Infinite-Scrolling-tp4821669p4822313.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/20150428/dc83e79e/attachment-0001.htm From redtexture at gmail.com Tue Apr 28 17:31:45 2015 From: redtexture at gmail.com (Mark RD Jones) Date: Tue Apr 28 17:32:31 2015 Subject: [Seaside] Re: Infinite Scrolling In-Reply-To: References: <1430176814666-4822313.post@n4.nabble.com> Message-ID: Commentary on Infinite Scrolling, and the better and worse varieties of implemetation. Hacker News - April 22, 2015 "Ask HN: Please stop making infinite scrolling websites" https://news.ycombinator.com/item?id=9416017 On Tue, Apr 28, 2015 at 10:08 AM, J.F. Rick wrote: > Cool. Thanks for sharing. > > On Mon, Apr 27, 2015 at 7:35 PM Paul DeBruicker wrote: >> >> I made an JQWidgetBox endless scroll widget a while ago, but never shared >> it >> I guess. I just uploaded it to Smalltalkhub. see: >> http://smalltalkhub.com/#!/~Seaside/JQueryWidgetBox >> >> Its a plugin for https://github.com/fredwu/jQuery-Endless-Scroll >> >> I'm not sure if/how the Widget is out of sync with the JS code in the git >> repo but its a start. >> >> >> I used it like this: >> >> >> renderEndlessScroll: html with: aRequest with: id >> >> html >> script: >> (((html jQuery id: id) endlessScroll) >> fireDelay: 5000; >> fireOnce: true; >> bottomPixels: 850; >> insertAfter: '.results:visible:last'; >> visible: '#' , id; >> callback: >> (html jQuery ajax >> script: [ >> :s | >> s >> << (s jQuery class: 'loader') show. >> s >> << (s jQuery class: 'results:visible:last') >> >> replaceWith: [ :h | | moreItems | >> >> moreItems := self getMoreResults: aRequest. >> >> self renderMoreItems: moreItems from: aRequest at: id on: h ]. >> s >> << (s jQuery class: 'shown:visible') >> >> replaceWith: [ :h | >> >> (h span) >> >> class: 'shown'; >> >> with: [html strong: aRequest results oldResults size >> asStringWithCommas ] ] ])) >> >> >> >> >> jrick wrote >> > I'm implementing a blog with many posts. I'd like to implement infinite >> > scrolling >> > <http://www.sitepoint.com/jquery-infinite-scrolling-demos/> so >> > that only a few posts get loaded initially and then subsequent posts get >> > loaded once the person scrolls to the bottom of the page. I'd like to >> > use >> > AJAX prepend to make this happen. >> > >> > Has anyone implemented something similar? Is there a good way to trigger >> > a >> > seaside ajax call based on an element appearing on screen or a scroll >> > event >> > reaching near the bottom? >> > >> > Cheers, >> > >> > Jeff >> > >> > _______________________________________________ >> > seaside mailing list >> >> > seaside@.squeakfoundation >> >> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> >> >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Infinite-Scrolling-tp4821669p4822313.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 > > > _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > From self at je77.com Tue Apr 28 21:29:26 2015 From: self at je77.com (J.F. Rick) Date: Tue Apr 28 21:29:28 2015 Subject: [Seaside] Re: Infinite Scrolling In-Reply-To: References: <1430176814666-4822313.post@n4.nabble.com> Message-ID: Yep, infinite scrolling can be a bad idea. That said, you really need it if you are going to do an updating feed, like Facebook. Cheers, Jeff On Tue, Apr 28, 2015 at 1:32 PM Mark RD Jones wrote: > Commentary on Infinite Scrolling, > and the better and worse varieties of implemetation. > > Hacker News - April 22, 2015 > "Ask HN: Please stop making infinite scrolling websites" > https://news.ycombinator.com/item?id=9416017 > > > On Tue, Apr 28, 2015 at 10:08 AM, J.F. Rick wrote: > > Cool. Thanks for sharing. > > > > On Mon, Apr 27, 2015 at 7:35 PM Paul DeBruicker > wrote: > >> > >> I made an JQWidgetBox endless scroll widget a while ago, but never > shared > >> it > >> I guess. I just uploaded it to Smalltalkhub. see: > >> http://smalltalkhub.com/#!/~Seaside/JQueryWidgetBox > >> > >> Its a plugin for https://github.com/fredwu/jQuery-Endless-Scroll > >> > >> I'm not sure if/how the Widget is out of sync with the JS code in the > git > >> repo but its a start. > >> > >> > >> I used it like this: > >> > >> > >> renderEndlessScroll: html with: aRequest with: id > >> > >> html > >> script: > >> (((html jQuery id: id) endlessScroll) > >> fireDelay: 5000; > >> fireOnce: true; > >> bottomPixels: 850; > >> insertAfter: '.results:visible:last'; > >> visible: '#' , id; > >> callback: > >> (html jQuery ajax > >> script: > [ > >> :s | > >> > s > >> << (s jQuery class: 'loader') show. > >> > s > >> << (s jQuery class: 'results:visible:last') > >> > >> replaceWith: [ :h | | moreItems | > >> > >> moreItems := self getMoreResults: aRequest. > >> > >> self renderMoreItems: moreItems from: aRequest at: id on: h ]. > >> > s > >> << (s jQuery class: 'shown:visible') > >> > >> replaceWith: [ :h | > >> > >> (h span) > >> > >> class: 'shown'; > >> > >> with: [html strong: aRequest results oldResults size > >> asStringWithCommas ] ] ])) > >> > >> > >> > >> > >> jrick wrote > >> > I'm implementing a blog with many posts. I'd like to implement > infinite > >> > scrolling > >> > <http://www.sitepoint.com/jquery-infinite-scrolling-demos/> so > >> > that only a few posts get loaded initially and then subsequent posts > get > >> > loaded once the person scrolls to the bottom of the page. I'd like to > >> > use > >> > AJAX prepend to make this happen. > >> > > >> > Has anyone implemented something similar? Is there a good way to > trigger > >> > a > >> > seaside ajax call based on an element appearing on screen or a scroll > >> > event > >> > reaching near the bottom? > >> > > >> > Cheers, > >> > > >> > Jeff > >> > > >> > _______________________________________________ > >> > seaside mailing list > >> > >> > seaside@.squeakfoundation > >> > >> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > >> > >> > >> > >> > >> > >> -- > >> View this message in context: > >> http://forum.world.st/Infinite-Scrolling-tp4821669p4822313.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 > > > > > > _______________________________________________ > > seaside mailing list > > seaside@lists.squeakfoundation.org > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > _______________________________________________ > 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/20150428/4a5d30ac/attachment.htm From hilaire at drgeo.eu Wed Apr 29 12:23:25 2015 From: hilaire at drgeo.eu (Hilaire) Date: Wed Apr 29 12:23:27 2015 Subject: [Seaside] Re: Jquery select then hide In-Reply-To: References: <553D6D3C.4050507@comcast.net> Message-ID: <5540CD3D.4020606@drgeo.eu> Le 28/04/2015 09:21, Johan Brichau a ?crit : > onChange: (html jQuery this value) equals: ?missis? asJavascript > then: (html jQuery: #maiden) show > then: (html jQuery: #maiden) hide) I understand the intend but not the syntax. I can see #then:else: message but no #equals: jquery instance But I am curious to learn how to -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu From pbpublist at gmail.com Thu Apr 30 10:57:23 2015 From: pbpublist at gmail.com (Phil (list)) Date: Thu Apr 30 10:56:03 2015 Subject: [Seaside] Seaside form issue in Firefox and multiple open instances/windows In-Reply-To: References: <1429909492.2366.12.camel@gmail.com> Message-ID: <1430391443.2835.20.camel@gmail.com> On Sun, 2015-04-26 at 19:27 +0200, Philippe Marschall wrote: > On Fri, Apr 24, 2015 at 11:04 PM, Phil (list) wrote: > > I've been running into a situation where when I have the same page > > loaded in multiple browser windows. The page contains a form where the > > form fields will not be selectable (i.e. can't click to edit a text > > field) in the window having the 'oldest' (i.e. first loaded) page. > > Can you inspect it with firebug or similar? Is it disabled in the DOM? > It doesn't appear to be. I took a look at attributes on both the form itself and a textarea on the form but didn't see any obvious differences (the disabled property on the textarea is set to false on both the working and non-working forms as well and various other properties I've looked at on the form and textarea properties also match) One additional detail I did notice is that none of the edit fields on the entire page/tab are working when this occurs. i.e. neither the location text field nor the search text field are selectable either. I am able to select text and copy/paste it into another application but can't type anything into any text fields in the tab. If I close the tab and re-open with a new session, this appears to temporarily work around the issue. > Cheers > Philippe > _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside From self at je77.com Thu Apr 30 17:39:34 2015 From: self at je77.com (J.F. Rick) Date: Thu Apr 30 17:39:38 2015 Subject: [Seaside] Detect window size, etc. Message-ID: I'm trying to detect which device is browsing my seaside site. While I can deduce some things from the header information, I'd like to also gather the window width and height and screen orientation. Is there a good example of how to gather such information inside a seaside task (perhaps loading a page with the javascript to detect the information and then a redirect to go to the appropriate root object)? Cheers, Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20150430/21364d69/attachment.htm