seaside April 2017

seaside@lists.squeakfoundation.org

9 participants
8 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

how to stopInterval which was created by JSObject>>interval:
by Sabine Manaa 28 Apr '17

28 Apr '17

Hi, I use JSObject>>interval: (thanks Johan) for my report generation: first I show a spinner. Every 2 seconds, I try to reload the reports png file (it takes a little time to generate it). This works but I have one final problem: how can I stop the interval? Four intervals are started each time the user selects a trip and wants the reports to be shown (there are 4 report types currently). I have to stop them, if not, they overlap with the old reports. Below is a part of the code I use. As far as I understand, I need an ID of the interval to call clearInterval(timerId); In the onComplete: of the load I want to call clearInterval() with this timerId. html div ... script: ((html jQuery id: anId) load html: [ :r | ...show the report file... ]; interval: 2 seconds); It creates this JS setInterval(function(){$("#imageVehicleReport").load("/RKA",["_s=sW0fUJ73IwxSs_bo","_k=b14htm7FJ6AWvWeW","4152"].join("&"))},2000) How can I stop it? Regards Sabine

3 3

Re: [Seaside] [squeak-dev] About loading Seaside into Squeak6.0a-17082 ....
by H. Hirzel 27 Apr '17

27 Apr '17

Hello Tobias Your hint [1] and the remarks by Esteban and Dale allowed me to load Seaside into a Squeak6.0alpha-17082 image (points a and b below) and the most recent Squeak6.0alpha-17227 (point c below) with some workarounds. a) I had to patch [2] MetacelloSqueakPlatform>>defaultPlatformAttributes in a way so that it gives the same result as in Squeak 5.1 where everything works fine [3] b) Before opening the Seaside control panel (World menu / open) I had to call the following initialisation code manually. WAServerManager initialize. WAKeyGenerator initialize. WAResponse initialize. With this the initial Seaside screen came up and I could create a component and browse the examples. Maybe there are more objects to initialize, however the tests (see point c) seem to indicate that it is probably sufficient. It seems that some startup / initialisation code does not get registered / called after loading. c) Points a) and b) are for Squeak6.0alpha-17082 and for Squeak 6.0alpha-17227 (= the most recent one). So this point is about what you have to do in addition to make Seaside load in Squeak 6.0alpha-17227. In Squeak6.0alpha-17082 we still have the class BlockContext. In the more recent versions (current is 17227) the classes BlockContext and ContextPart are no longer in the image. Only Context. To load MetaCello you need to add a (temporary) subclass to context Context variableSubclass: #BlockContext instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'Kernel-Methods' And for Seaside to load Context variableSubclass: #ContextPart instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'Kernel-Methods' With this workaround Seaside loads fine and when I run all tests in categories starting with 'Seaside-Tests-' then I get 914 passes out ot 915. [4] Conclusion: ---------------- It seems that there are no changes in Squeak6.0a so far which are show stoppers for Seaside. The current result is fine for me at the moment and I will look into this issue later in the release cycle of Squeak 6.0a. The remarks by Dale will be helpful to do so. Esteban, Dale and Tobias, thank you for your help. Regards --Hannes //////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// [1] defaultPlatformAttributes On 4/26/17, Tobias Pape <Das.Linux(a)gmx.de> wrote: [snip] > > Hannes, since I have not much time atm for Seaside, can you try out a bit > yourself? > You should get things loaded at least if you make > `MetacelloSqueakPlatform>>defaultPlatformAttributes` return #'squeak5.0' > > best regards > -Tobias > [2] MetacelloSqueakPlatform>>defaultPlatformAttributes defaultPlatformAttributes "self new defaultPlatformAttributes" | attributes | attributes := OrderedCollection with: #squeakCommon with: #squeak. Smalltalk at: #SystemVersion ifPresent: [:cl | |versionString| versionString := cl current version asString. " Major version " #( 'Squeak3.10' (#'squeak3.10.x' ()) 'Squeak4' (#'squeak4.x' ( 'Squeak4.1' #'squeak4.1.x' 'Squeak4.2' #'squeak4.2.x' 'Squeak4.3' #'squeak4.3.x' 'Squeak4.4' #'squeak4.4.x' 'Squeak4.5' #'squeak4.5.x' 'Squeak4.6' #'squeak4.6.x')) 'Squeak5' (#'squeak5.x' ( 'Squeak5.0' #'squeak5.0.x'))) pairsDo: [:major :allAttributes | (versionString beginsWith: major) ifTrue: [ attributes add: allAttributes first. allAttributes second ifNotEmpty: [:minorVersions | minorVersions pairsDo: [:minor :attribute | (versionString beginsWith: minor) ifTrue: [ attributes add: attribute. ^ attributes]]]]]]. "HACK HJH to load Seaside into Squeak6.0a" attributes add: #'squeak5.x'. ^ attributes //////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// [3] Seaside runs fine in Squeak 5.1 as show here https://travis-ci.org/SeasideSt/Seaside Seaside loads fine in Squeak 5.1 https://travis-ci.org/SeasideSt/Seaside/jobs/204692009 //////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// [4] The test which fails is WAGenericCodecTest testGenericCodecMacRoman | codec | codec := GRCodec forEncoding: 'mac-roman'. self assert: (codec isKindOf: GRPharoGenericCodec). self assert: codec name = 'mac-roman'. self assert: codec url name = 'utf-8'. self assert: (codec url isKindOf: GRPharoUtf8Codec). self assert: (codec encode: self latin1String) = self macromanString. self assert: (codec url encode: self latin1String) = self utf8String. self assert: (codec decode: self macromanString) = self latin1String. self assert: (codec url decode: self utf8String) = self latin1String

1 0

About loading Seaside into Squeak6.0a-17082 ....
by H. Hirzel 26 Apr '17

26 Apr '17

Hello Loading Seaside into Squeak6.0a-17082 .... gives the following error Character(Object)>>doesNotUnderstand: #greaseInteger Details [1] Is there a particular Squeak6.0a version where Seaside loads fine? http://files.squeak.org/6.0alpha/ Any suggestions how a fix to Grease should look like? Regards --Hannes --------------------------------------------------------------------------------------------- Character(Object)>>doesNotUnderstand: #greaseInteger Receiver: Character null Arguments and temporary variables: aMessage: greaseInteger exception: MessageNotUnderstood: Character>>greaseInteger resumeValue: nil Receiver's instance variables: Character null WAUrlEncoder class>>encode:on: Receiver: WAUrlEncoder Arguments and temporary variables: aCharacter: Character null aStream: a WriteStream printer: a GRNumberPrinter Receiver's instance variables: superclass: WATableBasedEncoder methodDict: a MethodDictionary() format: 65538 instanceVariables: nil organization: ('as yet unclassified') subclasses: nil name: #WAUrlEncoder classPool: nil sharedPools: nil environment: Smalltalk category: #'Seaside-Core-Document' table: #(nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil ni...etc... WAUrlEncoder class>>initializeTable Receiver: WAUrlEncoder Arguments and temporary variables: stream: a WriteStream characterLimit: 255 index: 0 character: Character null value: nil Receiver's instance variables: superclass: WATableBasedEncoder methodDict: a MethodDictionary() format: 65538 instanceVariables: nil organization: ('as yet unclassified') subclasses: nil name: #WAUrlEncoder classPool: nil sharedPools: nil environment: Smalltalk category: #'Seaside-Core-Document' table: #(nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil ni...etc...

4 8

redirect user if session dead without clicking him at the page itself
by Sabine Manaa 21 Apr '17

21 Apr '17

Hi, is anyone having an idea for a solution of this problem: I want that my seaside web app redirects the user to another page (login page) if the session is "dead*". The special point I am looking for is: This should happen ALSO if the user does NOT click on this page or does something. Also if the user switches to another tab. So, if he comes back to the browser/to my apps tab, he should see a message "you have already been logged out". I assume I have to periodically check if the session is alive and played around with html paragraph script: (html jQuery this load html: [ :r | "here check for session and if not there, redirect" (Array with: self currentPerson with: (self application sessions includes: self session)) inspect ]; interval: 30 seconds); with: [ html render: something]. but if the session is dead, the code "here check ..." is no longer executed. I am not sure if this is the right idea... Anyone already implemented something like this? I am not looking for a redirect after clicking somewhere in the app, I have this and it works fine. Regards Sabine * I have read a little about "dead" sessions and know that they are collected away at unpredictable time. With "dead" I mean that if the user would click at the app, he would be transferred away.

2 2

How can I change default AJAX settings?
by Mariano Martinez Peck 15 Apr '17

15 Apr '17

Hi guys, I have a few places where I am reaching the limit of URL size due to AJAX serialziation. I can manually fix the places where I serialize a bunch and do: jQuery ajax type: 'POST'; serializeForm; ... But I am wondering if I can change this globally, for all AJAX requests. I tried this: html jQuery ajaxSetup type: 'POST' But doesn't seem to work. Does someone know how to? In addition, I wonder, is it a bad idea to set 'POST' as default? Thanks in advance, -- Mariano http://marianopeck.wordpress.com

2 1

best replacement for beSubmitOnChange
by Johannes Brauer 09 Apr '17

09 Apr '17

Hi, I am porting an Seaside 2 app to Seaside 3 and I am looking for a replacement for beSubmitOnChange. What is the best (shortest?) way to do this? Johannes

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside April 2017