seaside March 2017

seaside@lists.squeakfoundation.org

16 participants
16 discussions

isolate
by recursive68＠gmail.com 26 Nov '19

26 Nov '19

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

4 5

Seaside 3.2.0 final
by Johan Brichau 16 Aug '17

16 Aug '17

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

14 26

bind onScroll event with Ajax call to body tag
by Sabine Manaa 31 Mar '17

31 Mar '17

Hi, til now, I was adding an onScroll event (with an Ajax call) to a part of my layout like this here: html mdlLayoutContent onScroll: (html jQuery ajax script: [ :s | ...do something with my model so I don't want use pure javascript... ]); with: aBlock. This worked fine. But now I have to change this and I have to put the onScroll event to the body tag: I know that I could in updateRoot do this: aHtmlRoot bodyAttributes at: 'onScroll' put: 'alert(''D'')'. But I have to make an Ajax call (getting next domain objects to show). So my question is how can can I put an Ajax call to body onScroll that the result is similar to this: <body onscroll="if( do some js check){$.ajax({"dataType":"script","url":"/RKA","data":["_s=KFxTxw2Prts-ZMLU","_k=Zp8eG2nIxTNYJAlE","37"].join("&")})}"> I would be very happy for a hint... Sabine -- View this message in context: http://forum.world.st/bind-onScroll-event-with-Ajax-call-to-body-tag-tp4940… Sent from the Seaside General mailing list archive at Nabble.com.

2 4

JQAjax>>#script: in GemStone 3.3.1 with Seaside 3.2.1 works differently than in pharo
by PAUL DEBRUICKER 27 Mar '17

27 Mar '17

In Pharo I can use a #script: send like this html jQuery ajax callback: [ :json | self setMapBoundsFrom: json ] json: (JSStream on: 'map.getBounds()'); script: [ :s | s << ((s jQuery id: #'results') html: [ :r | self renderResultsOn: r ]) ] And the #results id has its content set to the value of the #renderResultsOn: method. In GemStone it seems like a page refresh is happening instead. Has anyone else seen this? I think it was happening in older versions too but I am not sure of what version combination.

3 4

Re: [Seaside] [Glass] Why session locking is necessary for Seaside?
by Mariano Martinez Peck 24 Mar '17

24 Mar '17

On Tue, Mar 21, 2017 at 5:57 PM, Dale Henrichs via Glass < glass(a)lists.gemtalksystems.com> wrote: > > > On 03/21/2017 12:25 PM, Mariano Martinez Peck via Glass wrote: > > Hi, > > I was reading this old post from Dale [1] which explains the topic very > nice. After having watched the #seasideProcessRequestWithRetry:resultBlock: > and WASession >> handle: and the post, I have some questions. > > On one paragraph you said: > > *"Object locking as a technique for avoiding commit conflicts shares the > ‘retry on failure’ model of WATally, so it isn’t necessarily superior to > ‘retry on commit failure’. It is a superior technique, if you need to > protect logical updates where a physical conflict cannot be guaranteed > (i.e., updates to different portions of an object graph).* > *"* > > *And that's EXACTLY what I was wondering... why the commit failure > (conflicts) / abort / retry would NOT be enough for sessions and avoid the > lock? *Is that because of that sentence "* if you need to protect > logical updates where a physical conflict cannot be guaranteed" * > So that's the case for Seaside sessions? It's not safe to update (without > conflict) different parts of the session subgraph ? > > The primary reason for the Seaside session object lock is that Seaside > itself had (and presumably still has) a mutex on the session object that > only allows Pharo-based Seaside to handle one request at a time in a single > vm. > I wonder if that's still the case on latest Seaside. Do you have a clue where I can check myself? > The session object lock emulates the in-vm mutex semantics for multi-gem > GemStone and guarantees logical consistency for the session state. > I am intrigued about the ORIGINAL needs of such a need. Because as Pharo and GemStone and too it makes me wonder if the lock would be needed on GemStone. > Unfortunately it is not enough to rely conflicts to guarantee logical > consistency. > Do you have more details about this? An example maybe? > > > This is sad, because many many many requests would be read-only to what > the session matters (unless there is something obvious I am not seeing?) > and in that case, the requests WOULD be able to be parallelized on > different Gems. > > On the other hand, if you know that you have read-only requests, you could > arrange for a pool of seaside gems to be serving read-only requests by > putting the gems behind a different ip address, disabling the session lock > altogether and unconditionally aborting after finishing request processing > (this is roughly the equivalent of what Johan is doing with his pool of > REST gems -- I think). I suppose you could embed something in the http > request itself to tell the server to process a read only request as well... > that way your entire pool of seaside gems could alternate between server > session-based requests and session-less requests ... > > > I just analyzed this carefully, and I cannot guarantee my requests are fully read only ahahahahhaha. > I know Johan recommends session affinity [2] and I understand why. It's > just that I would prefer to be able to have multiple requests to the same > session in parallel in different gems. At least those that wouldn't fail > due to a commit conflict on the session. > > This does bring up a question that I haven't thought about before: > > How does an Ajax request "bypass" the session mutex in a Pharo-based > Seaside vm? > > Does it? > Dale > > _______________________________________________ > Glass mailing list > Glass(a)lists.gemtalksystems.com > http://lists.gemtalksystems.com/mailman/listinfo/glass > > -- Mariano http://marianopeck.wordpress.com

3 4

[ANN] MaterialDesignLite for Seaside v1.1.0
by Cyril Ferlicot D. 22 Mar '17

22 Mar '17

Hello everyone, Today I released the version v1.1.0 of MaterialDesignLite for Seaside. (https://github.com/DuneSt/MaterialDesignLite) Since this is a minor version it shouldn't break anything existing, but nobody can avoid bugs. If you encounter a regression, feel free to open an issue and I'll try to commit a hotfix soon. Thanks to Philippe Back, Paul Debruicker, Sabine Mana, Tobias Pape, Guillaume Larcheveque and Yann Lesage for the contributions and the feedback. Also thanks to everyone using this project. You can now find an image with the project on pharo-contribution's Jenkins and on PharoLauncher. (https://ci.inria.fr/pharo-contribution/job/MaterialDesignLite) You can find more detail on the README.md to start with the project. One of the future goal would be to add Functional tests with Parasol. Here is the changelog. You can find a more readable version at: https://github.com/DuneSt/MaterialDesignLite/blob/v1.1.0/CHANGELOG.md # [v1.1.0](https://github.com/DuneSt/MaterialDesignLite/compare/v1.0.2...v1.1.… (2017-03-22) ## Bug Fixes * **SelectWidget: Do not upgrade the dom at all node insertion** ([59c2534](https://github.com/DuneSt/MaterialDesignLite/commit/59c2534)) * **MDLDialog>>openButtonId: missing .close eventListener** ([262e6f3](https://github.com/DuneSt/MaterialDesignLite/commit/262e6f3)) * **Chips: Use #ensureId rather than overriding #id & #id:** ([40fcca5](https://github.com/DuneSt/MaterialDesignLite/commit/40fcca5)) * **SortableTable: Visible page might end up out of bounds** ([b1833e8](https://github.com/DuneSt/MaterialDesignLite/commit/b1833e8)) * **NestedList: Tooltips are unusable** ([5ef2a08](https://github.com/DuneSt/MaterialDesignLite/commit/5ef2a08)) ## Features * **Anchors as buttons** This add the possibility to have links with the style of buttons to not break semantic ([ba3f0f7](https://github.com/DuneSt/MaterialDesignLite/commit/ba3f0f7)) * **Sliders: New features** This add a label with MD style, possibility to add an icon, possibility to add an output, show the bounds and a demo ([b203a1f](https://github.com/DuneSt/MaterialDesignLite/commit/b203a1f)) * **Dialog: Multiple opening buttons for a dialog** ([209d49a](https://github.com/DuneSt/MaterialDesignLite/commit/209d49a)) * **SelectWidget: Allow to customize the field** ([ace3e31](https://github.com/DuneSt/MaterialDesignLite/commit/ace3e31)) * **SelectWidget: Add tooltips on entries** ([14466d2](https://github.com/DuneSt/MaterialDesignLite/commit/14466d2)) * **SortableTable: Allow to have no pagination** ([aaa6c19](https://github.com/DuneSt/MaterialDesignLite/commit/aaa6c19)) * **SortableTable: Allow to personalize the style** ([69284d7](https://github.com/DuneSt/MaterialDesignLite/commit/69284d7)) * **NestedList: Add way to customize style + add some default styles** ([5f5088c](https://github.com/DuneSt/MaterialDesignLite/commit/5f5088c)) * **NestedList: Ajax actions on clic** ([feaba43](https://github.com/DuneSt/MaterialDesignLite/commit/feaba43)) * **NestedList: possibility to customize an entry** ([9421917](https://github.com/DuneSt/MaterialDesignLite/commit/9421917)) * **NestedList: Possibility to have an icon to the right of the list** ([27fa1fa](https://github.com/DuneSt/MaterialDesignLite/commit/27fa1fa)) * **NestedList: Add a filter** ([9ecffad](https://github.com/DuneSt/MaterialDesignLite/commit/9ecffad)) * **NestedList: Dynamically load children** ([5ef2a08](https://github.com/DuneSt/MaterialDesignLite/commit/5ef2a08)) * **NestedList: Search and loading should add a spinner while executing** ([5ef2a08](https://github.com/DuneSt/MaterialDesignLite/commit/5ef2a08)) * **Tooltip: API should let choose the position of the tooltip** ([de33e68](https://github.com/DuneSt/MaterialDesignLite/commit/de33e68)) ## Cleaning * **Dialogs** Clean javascript ([262e6f3]https://github.com/DuneSt/MaterialDesignLite/commit/262e6f3)) * **NestedList** Extract the javascript into a file and use dataset instead of ids ([21c0535](https://github.com/DuneSt/MaterialDesignLite/commit/21c0535)) * **Extract Material Colors in another project** New repositories to get only the MDLColors: [https://github.com/DuneSt/MaterialColors](https://github.com/DuneSt/Materia… ([2efac41](https://github.com/DuneSt/MaterialDesignLite/commit/2efac41)) * **Improve Chips loading scripts** ([b366ddd](https://github.com/DuneSt/MaterialDesignLite/commit/b366ddd)) ## Infrastructure * **Travis and Appveyor CI** ([1afa628](https://github.com/DuneSt/MaterialDesignLite/commit/1afa628)) ## Compatibility ### Squeak * **`MDColor` has a lowercase class variable** ([888fb39](https://github.com/DuneSt/MaterialDesignLite/commit/888fb39)) ### Gemstone * **Use string in baseline and remove #asString** ([868f71b](https://github.com/DuneSt/MaterialDesignLite/commit/868f71b)) -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques Prévert 01, 59650 Villeneuve d'ascq France

1 0

Workaround to browser maximum connection limit ?
by Mariano Martinez Peck 21 Mar '17

21 Mar '17

Hi guys, In my app I have one scenario where we render huge reports. These reports could have say... 20/30 large tables as well as quite some charts and some other report elements. Previously we were using a single ajax request to generate the whole report html but that was a pain because client machine would have a really large TTFB. So I was wasting CPU and network at client machine while waiting. What we did now is that each report element renders a title + spinning while and does an ajax request which, on success does a #replaceWith: with the real contents. The idea is to show the report as soon as possible and start replacing spinning wheels with real contents as soon as content is ready. That way I maximize CPU and network on client side. The second thing is that making this on AJAX calls, that would end up on different Gems on my GemStone which was very performant. I have 10 Seaside gems on a 8 cores CPU so all those AJAX request were load balanced via nginx over the 10 seaside gems, which on the other hand were split across all cores. Previously, with a single request, only one Gem took care and hence only one CPU core was used. This change was nice and improved performance. However, when I analyze requests, I see that I have many that are "Stalled". And yeah, on Chrome, they are all stalled when there is more than 6 requests to the same location. To conclude, it looks like i am doing what is called "Loading page content with many Ajax requests" [1]. But I still don't find an easy workaround. I would like to be able to use my 10 Gems over the 8 CPU cores.... Any idea? Thanks in advance, [1] http://sgdev-blog.blogspot.com.ar/2014/01/maximum-concurrent-connection-to-… -- Mariano http://marianopeck.wordpress.com

2 4

WAStatus not displaying in Squeak 5.1
by Tim Johnson 18 Mar '17

18 Mar '17

Hello friends, I was excited that Metacello, Seaside, and even KomHttpServer load in Squeak 5.1. (Sure, I should probably be using WebClient instead... but it seems to leave handlers or listeners laying around? Not sure.) Some things seem to be not quite right in my install or setup or image, though. http://localhost:8080/status just shows an empty box. Is it something to do with Grease strings? Any idea what's wrong? Also, error messages look different than I'm accustomed; there is no more stack trace and option to debug. Maybe the Debug handler is not the default anymore? Thanks, Tim

2 1

Re: [Seaside] Http POST problems
by David Pennington 14 Mar '17

14 Mar '17

I am sorry but I can't see any directions here, just some bullet points on a slideshow. David --------- Original Message --------- From: "phil(a)highoctane.be" <phil(a)highoctane.be> To: "David Pennington" <david(a)totallyobjects.com>, "Seaside - general discussion" <seaside(a)lists.squeakfoundation.org> Subject: Re: [Seaside] Http POST problems Date: 03/13/2017 22:35:05 (Mon) For POST, there is the WARestComponentFilter http://esug.org/data/ESUG2014/4%20thursday/1400-1530%20Seaside/AdvancedSeas… So you can expose a REST endpoint. Phil On Mon, Mar 13, 2017 at 11:21 PM, David Pennington <david(a)totallyobjects.com> wrote: I asked recently if there was a way to do a POST through Seaside but didn't get an answer. I have worked at it and got it going but I am confused abut a few things. My Web Page that is the target for the POST is subclassed from WAComponent. I have two issue that I have had to deal with. The first is that processing of the POST incoming data requires two instance variables to exist - seasideMimeDocument seasideMimeDocumentType I had to add these to my top level class and then everything seemed OK except that the data was missing. In the WARequest object there is a variable called postFields so someone had foreseen the need for handling a POST but this field is empty. There is a field in the headers called content_type and for now I have replaced the more usual "application/json" with my json data and I can get it from there. Can anyone give me a clue what I can do to fix this? David -------------------------------------------------- Message sent using Winmail Mail Server _______________________________________________ seaside mailing list seaside(a)lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside Message sent using Winmail Mail Server

2 1

How do I create a seaside page to respond to a PUT
by David Pennington 14 Mar '17

14 Mar '17

Hello everyone. I am writing a mobile app that needs to talk back to a server using REST. I have set up Seaside pages that respond to GET requests in the form 'http://mydomain.com/MySeasidePage?username:password:dataRequest. This works fine.Now, however, I have to start updating the data on the server and I think that I should not use GET to change the data (web crawlers can do bad damage that way). So, my question is, if I formulate a correct PUT request, is there a way to get the Seaside page to respond correctly to it buy taking the data and using it, then sending back an HTML response?David Message sent using Winmail Mail Server

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside March 2017