seaside May 2018

seaside@lists.squeakfoundation.org

21 participants
18 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

Hosting Options these days?
by Tim Mackinnon 29 Mar '19

29 Mar '19

Hi everyone - are there any easy hobbyist hosting options for seaside these days? Or do you have to setup an Ec2 instance yourself? Tim

5 15

default exception handler WAWalkbackErrorHandler only present in development, not runtime
by Thomas Brodt 11 Sep '18

11 Sep '18

Hi in Seaside (3.2.0 - JohanBrichau.85 1 in the Visualworks 8.3 port) class WAEnvironment installs WAWalkbackErrorHandler as default exceptionHandler in method #configureApplicationExceptionHandlingDefaults called from initialize. But WAWalkbackErrorHandler is included in package Seaside-Development, so if you build runtimes without Seaside development packages, this fails because WAWalkbackErrorHandler is not present in such runtime images. Shouldn't rather WAHtmlErrorHandler be used as default exception handler which is in the same package as WAEnvironment? And then maybe replaced by WAWalkbackErrorHandler if you additionally load development? Any thoughts? Thomas

2 2

[ANN] Heimdall logging manager for Seaside v1.0.0
by Cyril Ferlicot D. 13 Jun '18

13 Jun '18

Hi! Guillaume Larcheveque begun a simple login manager for Seaside. I just finished to port it to github and we released the v1.0.0. It is still experimental and help is welcomed. Project can be found at: https://github.com/DuneSt/Heimdall -- Cyril Ferlicot https://ferlicot.fr

2 2

Help
by Lorenzo Schiavina 01 Jun '18

01 Jun '18

Hi, I am new to Seaside and I was following the tutorial. In the chapter 17.1 I was trying to follow this instruction: To tell Seaside about the part of the URL that you left out in your rendering code you have to go to the application configuration page (at http://localhost:8080/config) and specify the Resource Base URL in the server settings. Just enter http://www.seaside.st. Seaside will automatically prepend this string to all URLs specified using resourceUrl:>>resourceUrl:. This reduces your code size and can be very useful if you want to move the resource location during deployment. I execute the instruction and when I reentered into Seaside I receive the following page: For any operation I try to do I receive: /http%3A/www.seaside.st/config not found I do not know how to recover my work. Does anybody can help me? Grazie mille. Lorenzo

3 4

help to use routing with seaside
by feav feav 17 May '18

17 May '18

I have to develop a web application with seaside and i don't know how to build routing system like /app/user /app/user/message and others *Cordialement, Armel EMBOLO* <https://accounts.google.com/SignOutOptions?hl=fr&continue=https://mail.goog…> *Ingénieur de travaux en Informatique de Gestion / Analyste programmeur* *Elève Ingénieur de Conception en Génie Logiciel* *Université de Maroua, Ecole Nationale Supérieure Polytechnique de Maroua (ex ISS)* *Facebook : Armel Embolo <https://www.facebook.com/armel.embolo>* *Linkedin : armel embolo <https://www.linkedin.com/profile/view?id=AAMAABYswuMBn33mi4o_x8R49OxfxiIQVA…>* *Tel : (+237) 650231339/698594740*

6 8

Re: [Seaside] How best to report (loading) errors in latest Seaside on Pharo?
by Thomas Brodt 17 May '18

17 May '18

Hi Tim yes, we have our own Errorhandler class that replaces the Seaside one. But our build process logs the Undeclared WAWalkbackErrorHandler because Development is not loaded in our runtime build. So it leaves at least a "code smell" where I would like to have clean builds. We use Seaside with Visualworks, so I also didn't know how to propose a fix for Pharo, which indeed seems on a transition to git, which makes it even harder. Thomas Am 17.05.2018 um 12:32 schrieb Tim Mackinnon: > Hi Thomas - what did you do to fix it, reinitialise it in your code afterwards? > > I seem to recall that seaside is exported to git so I’m not sure if a simple pull request can do it - and it’s also tricky as you need to consider all dialects - still I’m guessing the ci should help try a fix. > > I’ll see if I can propose a fix, at least for the Pharo bits > > Tim > > Sent from my iPhone > >> On 17 May 2018, at 07:59, Thomas Brodt <thomas.brodt.lists(a)porabo.ch> wrote: >> >> For 3) I already asked in this list in february if the standard error handler should be WAHtmlErrorHandler, and only be replaced by WAWalkbackErrorHandler when Development is loaded. This sounds right to me, but I didn't get any answer to my request, though. >> >> Maybe your email triggers enough interest for this? >> >> Thomas >> >>> Am 16.05.2018 um 23:08 schrieb Tim Mackinnon: >>> Hi guys - I’ve finally got my simple application CI working (and still contemplating using SmalltalkCI) and it immediately failed as I look for Undeclared classes on load and Seaside has a bunch of them on Pharo 6. I think all libraries should load clean (a noble goal - but useful in a dynamic language) >>> >>> I’ve inherited a spec from Willow which is; >>> >>> baseline: 'Seaside3' >>> with: [ spec >>> repository: 'github://SeasideSt/Seaside:v3.2.4/repository'; >>> loads: #('Seaside-Environment' 'JQuery' 'Zinc') ]; >>> project: 'Seaside3-Tests' copyFrom: 'Seaside3' with: [ spec loads: #('Seaside-Tests-Core') ]. >>> >>> >>> The following come up: >>> >>> 1. BaselineOfGrease>>initializeLatin1ToUtf8Encodings (GRUtf8CodecStream is Undeclared) >>> 2. GRSmallDictionary>>explorerContents (ObjectExplorerWrapper is Undeclared) >>> 3. WAEnvironment class>>configureApplicationExceptionHandlingDefaults (WAWalkbackErrorHandler is Undeclared) >>> >>> 1. This seems to be in the doit category of BaselineOfGrease>>initializeLatin1ToUtf8Encodings which seems to be a GemStone thing so not sure why its in a Pharo image? >>> 2. This seems to be in GRSmallDictionary>>explorerContents which seems to be in Grease-Pharo60-Core - this doesn’t look familiar so not sure if its some old remnant? >>> 3. This one looks more serious - WAEnvironment>>configureApplicationExceptionHandlingDefaults which is in Seaside-Environment, however WAWalkbackErrorHandler is defined in Seaside-Development - Core (so its at the wrong level?) >>> >>> >>> Do I log something for them? I think they are easy enough to fix - I guess I could try and do a pull request (but its still early days for me on that front). >>> >>> Tim >>> _______________________________________________ >>> 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

How best to report (loading) errors in latest Seaside on Pharo?
by Tim Mackinnon 17 May '18

17 May '18

Hi guys - I’ve finally got my simple application CI working (and still contemplating using SmalltalkCI) and it immediately failed as I look for Undeclared classes on load and Seaside has a bunch of them on Pharo 6. I think all libraries should load clean (a noble goal - but useful in a dynamic language) I’ve inherited a spec from Willow which is; baseline: 'Seaside3' with: [ spec repository: 'github://SeasideSt/Seaside:v3.2.4/repository'; loads: #('Seaside-Environment' 'JQuery' 'Zinc') ]; project: 'Seaside3-Tests' copyFrom: 'Seaside3' with: [ spec loads: #('Seaside-Tests-Core') ]. The following come up: 1. BaselineOfGrease>>initializeLatin1ToUtf8Encodings (GRUtf8CodecStream is Undeclared) 2. GRSmallDictionary>>explorerContents (ObjectExplorerWrapper is Undeclared) 3. WAEnvironment class>>configureApplicationExceptionHandlingDefaults (WAWalkbackErrorHandler is Undeclared) 1. This seems to be in the doit category of BaselineOfGrease>>initializeLatin1ToUtf8Encodings which seems to be a GemStone thing so not sure why its in a Pharo image? 2. This seems to be in GRSmallDictionary>>explorerContents which seems to be in Grease-Pharo60-Core - this doesn’t look familiar so not sure if its some old remnant? 3. This one looks more serious - WAEnvironment>>configureApplicationExceptionHandlingDefaults which is in Seaside-Environment, however WAWalkbackErrorHandler is defined in Seaside-Development - Core (so its at the wrong level?) Do I log something for them? I think they are easy enough to fix - I guess I could try and do a pull request (but its still early days for me on that front). Tim

2 1

Ci automated deploy of seaside to Digital Ocean
by Tim Mackinnon 13 May '18

13 May '18

Hi - having run through the simple tutorial of getting a seaside app up and running on digital ocean - I’m interested in the next steps of doing it more continuously- does anyone have any tips ? Eg. I know how to build an image with ci (like gitlab), having produced one I guess I can ssh to copy it, but do I really need to ps to find my running image to kill it and restart with the new replacement? I’m wondering if there are some simple tricks I’m missing? Tim Sent from my iPhone

6 20

Implementing a session timeout counter
by jtuchel＠objektfabrik.de 08 May '18

08 May '18

Hi, I'd like to present our users a countdown in the browser that shows the remaining time until the session times out. The problems I see are not JavaScript timouts and stuff to make this thing count down. My problem is more related to how to keep the counter in sync with the server side timeout. I am not talking about msecs or such, but the fact that there are at least two things that reset the counter on the server side and that needs to be communicated to the client: one is every standard callback processing, the other is Ajax (and maybe in some applications we also have WebSockets involved). I guess the best way to communicate the fact that the counter is back to (say) 40 minutes is to use an HTTP Header that gets added to every response, be it from some normal callback or Ajax callback. Do you guys agree? If we agree so far, we'd have to add some javascript code to all our rendered pages that ask for that Header and reset/restart the countdown. In case of complete-re-renders of a page this is probably something in the load script, right? For Ajax, I'd use JQuery's .ajaxComplete() to do the same. I guess there is some way to access the headers and restart the timer. Am I on the right track? Has anybody done this before? Maybe there already is something available in Seaside? The next wish on our list would be a button that a user can press in order to keep the session alive without doing anything else. This, I think, would be easy by just sending a little ajax request to the server that does basically nothing. Everything else is implemented already when the above-mentioned steps are done... right? Bonus question: Should the http header be filled with the end datetime of the session or the last tiome it was reset and to which value? In the former case, how can I determine it on the server, given I don't want to have the session timeout time in two places or a global Thanks for your ideas and thoughts, Joachim -- ----------------------------------------------------------------------- Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de Fliederweg 1 http://www.objektfabrik.de D-71640 Ludwigsburg http://joachimtuchel.wordpress.com Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1

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