seaside June 2016

seaside@lists.squeakfoundation.org

13 participants
11 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

Twitter Bootstrap and Accordion
by Torsten Bergmann 22 Jul '16

22 Jul '16

3 3

Seaside-Security for GemStone [WAS] Re: [Seaside] Seaside Error - No Secure Generator Available
by Mariano Martinez Peck 01 Jul '16

01 Jul '16

On Thu, Jun 30, 2016 at 2:45 PM, Johan Brichau <johan(a)inceptive.be> wrote: > Hi, > > This should only happen if you have Seaside-Security loaded. > Hi Johan, Nice package!! I wasn't aware of it. It contains some nice filters. Do you know if it works in GemStone too (from what I could see in the configuration, it's only for Pharo)? Thanks in advance, Cheers, -- Mariano http://marianopeck.wordpress.com

3 3

RE: [Seaside] Seaside Error - No Secure Generator Available
by mldavis＠chaparralwest.com 01 Jul '16

01 Jul '16

David, Many thanks. I would never have figured this out. It worked exactly as you said, in all my images. Some of these are on different machines and yet, they all suddenly started with this same error, all the same day???? At least two of these have been running for over a week without the error (starting, stopping, making changes etc). I wonder what triggered it.. Anyway thank you so much: It was in Seaside 3.2 loaded into Pharo 5 build 50760 running on Zinc server on Windows 10 latest stable. Regards, mike From: David Pennington [mailto:lhdavid@me.com] Sent: Thursday, June 30, 2016 9:21 AM To: mldavis(a)chaparralwest.com; Seaside - general discussion <seaside(a)lists.squeakfoundation.org> Subject: Re: [Seaside] Seaside Error - No Secure Generator Available I had this problem when running seaside in my VAST Smalltalk image. I was advised as follows by Instantiations: I can reproduce this. Looks like Seaside wants to generate random numbers to use as keys for session caches. If a secure RNG (via OpenSSL) is not available in Vast then it produces this walkback...even for http. If it's not found at startup, then it installs a 'WANoSecureKeyGeneratorAvailable' which produces an error when asked for a key. To get around this, try changing the key generator method to the following below. This will force it to fallback to using EsRandom as the RNG. In the meantime, we will revisit this internally to see if we can disconnect the OpenSSL requirement from the session cache keys. Thanks for bringing this up....please let me know if the change described below solves your issue. WANoSecureKeyGeneratorAvailable>>keyOfLength: anInteger ^super keyOfLength: anInteger Long Haired David A.K.A. David Pennington lhdavid(a)icloud.com <mailto:lhdavid@icloud.com> On 30 Jun 2016, at 15:33, mldavis(a)chaparralwest.com <mailto:mldavis@chaparralwest.com> wrote: Seaside 3.1 & 3.2 running on Windows 10 Since yesterday, all of my images of Seaside on two different machines are getting this error when I connect to them from <http://localhost:8080/> http://localhost:8080 : Seaside Walkback ---------------------------------------------------------------------------- ------ WAError: no secure key generator availble because seeding failed Debug Full Stack Stack Trace thisContext WANoSecureKeyGeneratorAvailable class(GRObject class)>>error: self WANoSecureKeyGeneratorAvailable thisContext WANoSecureKeyGeneratorAvailable(GRObject)>>error: self a WANoSecureKeyGeneratorAvailable thisContext WANoSecureKeyGeneratorAvailable>>keyOfLength: self a WANoSecureKeyGeneratorAvailable thisContext WAHashCache>>store: self a WAHashCache thisContext [ cache store: anObject ] in WAMutualExclusionCache>>store: self a WAMutualExclusionCache ---------------------------------------------------------------------------- - The multi image & different machine impact makes me wonder if this was caused by a Windows 10 update, which come without warning now? Can anyone help me? Thanks, mike <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai gn=sig-email&utm_content=emailclient&utm_term=icon> Virus-free. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai gn=sig-email&utm_content=emailclient&utm_term=link> www.avast.com _______________________________________________ seaside mailing list <mailto:seaside@lists.squeakfoundation.org> seaside(a)lists.squeakfoundation.org <http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

3 2

Seaside Error - No Secure Generator Available
by mldavis＠chaparralwest.com 30 Jun '16

30 Jun '16

Seaside 3.1 & 3.2 running on Windows 10 Since yesterday, all of my images of Seaside on two different machines are getting this error when I connect to them from http://localhost:8080 : Seaside Walkback ---------------------------------------------------------------------------- ------ WAError: no secure key generator availble because seeding failed Debug Full Stack Stack Trace thisContext WANoSecureKeyGeneratorAvailable class(GRObject class)>>error: self WANoSecureKeyGeneratorAvailable thisContext WANoSecureKeyGeneratorAvailable(GRObject)>>error: self a WANoSecureKeyGeneratorAvailable thisContext WANoSecureKeyGeneratorAvailable>>keyOfLength: self a WANoSecureKeyGeneratorAvailable thisContext WAHashCache>>store: self a WAHashCache thisContext [ cache store: anObject ] in WAMutualExclusionCache>>store: self a WAMutualExclusionCache ---------------------------------------------------------------------------- - The multi image & different machine impact makes me wonder if this was caused by a Windows 10 update, which come without warning now? Can anyone help me? Thanks, mike --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

1 0

Pharo 5, seaside 3.2 and magritte 3
by francescoagati 30 Jun '16

30 Jun '16

Hi, i have try yo use magritte 3 and seaside 3.2 inside pharo 5. With seaside works all good. But when i try to install magritte 3. Magritte say that need the seaside html5 canvas package. The error is: 'Error name not found: Seaside-HTML5' These are the packages i use: Metacello new configuration: 'Seaside3'; repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; version: ’3.2.0'; load Gofer it smalltalkhubUser: 'Pharo' project: 'MetaRepoForPharo50'; configurationOf: 'Magritte3'; loadVersion: #stable. There is compatibility between magritte3 and seaside 3.2 on pharo 5? Thanks Francesco -- View this message in context: http://forum.world.st/Pharo-5-seaside-3-2-and-magritte-3-tp4903247.html Sent from the Seaside General mailing list archive at Nabble.com.

2 1

GRInvalidUtf8Error: Invalid UTF-8 input
by Hilaire 28 Jun '16

28 Jun '16

Hi, I have this pdf file (joined here) which always produce this error when I try to upload it in Seaside. It seems to be true whenever the filename comes with non ascii characters. All in all, it looks likes GRPharoUtf8Codec is wrong in decoding filename with non ascii characters. It happens with Seaside3.1, Pharo4, newest Grease-Pharo30-Core package When using the Seaside Functional Test Suite / Upload test, the same problem occurs. What did I miss? Thanks Hilaire -- Dr. Geo http://drgeo.eu

5 24

jQueryMobile for Seaside 3.2.0?
by Michael J. Forster 22 Jun '16

22 Jun '16

I see the last mention of jQueryMobile on this list was Esteban A. M.'s inquiry in late 2013. Has anyone tried it with Seaside 3.2.0? I ask because I'm interested in using it, but I find installation of the existing version pulls in an older Seaside and dependencies. I would be happy to collaborate or assist with an update to support Seaside 3.2.0 if anyone is interested. Best, Mike -- View this message in context: http://forum.world.st/jQueryMobile-for-Seaside-3-2-0-tp4901968.html Sent from the Seaside General mailing list archive at Nabble.com.

3 3

Initialisation of componentClass
by Iwan Vosloo 18 Jun '16

18 Jun '16

Hi there, We have an issue related to magritte-seaside. When you set the Component to be used on a MADescription, eg: descriptionThings ^ MAToManyRelationDescription new ... componentClass: MyFancyTableComponent; yourself .. then there is no way (that I am aware of) to initialize the created MyFancyTableComponent in a customised way. In the example above, for instance one may have a MyFancyTableComponent that divides its items into several pages (like an MAReport would do). The number of items displayed per page has to be hard-coded in MyFancyTableComponent. It would be nice to have a way to initialize a newly created instance, something like: descriptionThings ^ MAToManyRelationDescription new ... componentClass: MyFancyTableComponent; initializeComponent: [ :newlyCreatedComponent| newlyCreatedComponent itemsPerPage: 40 ]; yourself There are, of course, several ways one could do this. I am not necessarily suggesting the above example as the way to do it... I am just illustrating the point. If you do not have such a mechanism, the only thing you can do is subclass MyFancyTableComponent with the express motivation - to be able to set a new instance up a certain way. We have a log of code that does this sort of subclassing. It makes things go really messy eventually. We'd like to get rid of all those subclasses and rather let the user of a component 'configure' it appropriately. Building something like what I am proposing means changes to magritte-seaside code though. So, if we do it we'd prefer to contribute upstream. Has anyone else come across this issue? Any ideas? Worthwhile to others too? Regards - Iwan -- Reahl, the Python only web framework: http://www.reahl.org

4 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside June 2016