seaside-dev January 2011

seaside-dev@lists.squeakfoundation.org

12 participants
16 discussions

Seaside.st Redesign
by Avi Shefi 29 Jan '11

29 Jan '11

Hi, Seems to me that seaside.st could use a redesign, especially due to the fact that the navigation can be sometimes confusing. Here are some suggestions: - Create a simpler layout for the homepage, which depicts Seaside's key features (currently lacking). - Organize website sections in order to flatten the structure. Downloading Seaside, for example, takes a few clicks until you actually get to the download link. - Use better graphics. With all the bleeding-edge features of Seaside the current design somehow lags behind. Other suggestions are welcome. Cheers, Avi.

2 1

Seaside 3.X for upcoming Pharo-dev 1.2
by Torsten Bergmann 28 Jan '11

28 Jan '11

Dont know about OB problem, looks like I havent followed all threads. Can you summarize the problem in short. I just downloaded one of the dev images built yesterday and I'm able to load Seaside 3.0.3, run it, browse and code with the browser as usual. Only "Finder" seems to have a problem with the styler... https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/ Bye T. -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone

2 1

Seaside 3.X for upcoming Pharo-dev 1.2
by Torsten Bergmann 27 Jan '11

27 Jan '11

Pharo-dev 1.2 gets more in more into shape, so the question comes up on plans for a Seaside 3.X for Pharo 1.2. Looks like it basically runs but some tests use Preferences. See also: http://code.google.com/p/pharo/issues/detail?id=3601 Any comments? Bye T. -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone

2 1

[OT] HTML 5 Logo
by Torsten Bergmann 20 Jan '11

20 Jan '11

If your seaside app is HTML 5 ready there is now a new logo to express this: http://www.w3.org/html/logo/ http://www.w3.org/News/2011.html#entry-8992 Would it make sense to add it to the Seaside.st page since Seaside is HTML aware? Thx T. -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail

2 1

Issue 634/633 initializeMemorySettingsProfileSeaside
by Torsten Bergmann 19 Jan '11

19 Jan '11

http://code.google.com/p/seaside/issues/detail?id=633 created by me http://code.google.com/p/seaside/issues/detail?id=634 created by Phillipe both are the same - while #634 is fixed by Phillipe, I cant change the status of #633. Anyone able to merge the issues or give me more rights on the issue tracker (which would be helpfull anyway). Thx T. -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl

2 1

working on porting Seaside3.0 to latest GemStone3.0 ... need to reserve a version number
by Dale Henrichs 18 Jan '11

18 Jan '11

There have been some significant changes to GemStone3.0 as GemStone3.0 in the last three months as GemStone3.0 enters beta. Those changes have perturbed the Seaside3.0 implementation a bit and I've got a good bit of work to bring GLASS and Seaside3.0 back up to snuff and as a consequence I will be making sets of GemStone-specific changes to Grease and Seaside3.0 over the next several weeks. My inclination is to use version 3.0.3.x for the GemStone-specific mods (I don't expect to be making any changes to the common code base) and I just want to let you folks know that I'll be spinning away on this one for awhile ... if in the interim there is a need to push out a 3.0.4, then I'll plan on syncing up and moving forward with 3.0.4.1 ... Dale

2 1

P2P CMS/PM system with SeaSide and TeaTime
by Torsten Bergmann 12 Jan '11

12 Jan '11

>out including Seaside which seems like it could the ideal >technology to build our system in. Yes, but it really depends on what you want to achieve. Note that Seaside is web server based ... and you want a P2P system A decentralized approach could make a good replacement for Dispora, which is a nice and funded idea - but nothing more than that - it has too many bugs and security problems - too complicated to install and setup in an environment (compared to Pharo/Seaside/PierCMS one click images) Maybe they should have choosen a more productive and easier to use technology like Smalltalk ;) Phillipe wrote: >I didn't get which part would be browser based and which >part would be P2P. Yes. Tell us more how the system should look like from your POV... What about a local server (standalone comanche with seaside) that is usable via webbrowser from your machine and that can also server others via network. If they setup their own machine assets like projects, blog contents (bound to users) could be moved. Thx T. P.S: Auckland is a nice place, was there two times and I really enjoyed it! -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

2 1

P2P CMS/PM system with SeaSide and TeaTime
by Aran Dunkley 12 Jan '11

12 Jan '11

Hi, I'm part of a development team who are helping an organisation to architect a free CMS based project-management system that they want to work in a P2P network rather than using a centralised web-server. We've researched existing CMS's such as Plone to see if they could be modified to operate on top of a DHT but found that they rely too heavily on querying methodologies that are incompatible with the P2P paradigm. I talked to the OpenCobalt developers and they were very positive about the feasibility of the idea and gave me a lot of good advice and links to check out including Seaside which seems like it could the ideal technology to build our system in. We have a specific application in mind that we'd like to develop which is a project-management/workflow environment running in a CMS with some other standard tools such as wiki/blog, but rather than a web-server we'd be using a local P2P app as the backend. I'm wondering what you guys, the Seaside developers think of the idea of extracting the TeaTime P2P aspect of OpenCobalt and running Seaside on it so we could build P2P browser-based applications? We have a good budget available for this and will be developing it as a completely free open source system, so we'd also like to hear from developers who may be interested in working on the project too. Thanks a lot, Aran

3 6

Re: [Seaside-dev] Seaside and exception behaviour
by mkobetic＠cincom.com 10 Jan '11

10 Jan '11

Here's maybe a bit more concise example. If you run the thing below in a workspace, it should return 'Squeak' in Squeak and 'VW' in VW [ [ [ self error: 'trigger error' ] on: ZeroDivide do: [ :ex | 'Squeak' ] ] on: Error do: [ :ex | 3 / 0 ] ] on: ZeroDivide do: [ :ex | 'VW' ] HTH, Martin "Alan Knight"<knight(a)acm.org> wrote: > To more concretely illustrate what I'm talking about, consider defining > an exception class ExceptionOne. Then define a class First with a method > startHere > "First new startHere" > [Second new doStuff] on: Error do: [:ex | Transcript cr; show: > 'exception in startHere'. ExceptionOne signal]. > > And a class Second, with > doStuff > [self doMoreStuff] on: ExceptionOne do: [:ex | Transcript cr; show: > 'Exception in doStuff']. > > and > > doMoreStuff > Transcript cr; show: 'Doing more stuff...'. > 3 / 0. > > In VisualWorks and VisualAge that results in an uncaught ExceptionOne > and a debugger. In Pharo 1.1 one-click it just prints 3 things to the > Transcript, the same behaviour I'd get in VisualWorks if I change the > startHere method to do "ex resiganlAs: ExceptionOne new" > > -- > Alan Knight [|], Engineering Manager, Cincom Smalltalk > knight(a)acm.org > aknight(a)cincom.com > http://www.cincom.com/smalltalk > > > _______________________________________________ > seaside-dev mailing list > seaside-dev(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev >

3 2

Re: [squeak-dev] Re: [Seaside-dev] Seaside and exception behaviour
by Julian Fitzell 10 Jan '11

10 Jan '11

Hi Andreas, A neat approach, but I don't think it quite works (yet, anyway). Although it has the correct behaviour when the exception action is invoked, it doesn't behave correctly for #defaultAction. According to 5.5.2.1 in the spec, "The #defaultAction method is executed in the context of the signaling environment." So, taking an example of an existing #defaultAction method that signals an exception: [ Error signal ] on: UnhandledError do: [ :ex | 'ANSI says so' ] returns 'ANSI says so' without your change but brings up a debugger with it. Julian On Sat, Jan 8, 2011 at 7:34 PM, Andreas Raab <andreas.raab(a)gmx.de> wrote: > Thanks for the test case. I've posted a possible fix for Squeak to the inbox > (Kernel-ar.540) but I'd like people to review the change first since it's a > fairly critical part of the system. I'd appreciate if someone could look at > the fix and comment on whether that's the sensible thing to do. > > Cheers, > - Andreas > > On 1/8/2011 6:02 PM, Julian Fitzell wrote: >> >> On Wed, Jan 5, 2011 at 8:15 AM, Paolo Bonzini<bonzini(a)gnu.org> wrote: >>> >>> On 01/05/2011 04:58 PM, mkobetic(a)cincom.com wrote: >>>> >>>>>> Here's maybe a bit more concise example. If you run the thing below >>>>>> in a workspace, >>>>>> it returns 'Squeak' in Squeak and 'VW' in VW >>>>>> >>>>>> [ [ [ self error: 'trigger error' >>>>>> ] on: ZeroDivide do: [ :ex | 'Squeak' ] >>>>>> ] on: Error do: [ :ex | 3 / 0 ] >>>>>> ] on: ZeroDivide do: [ :ex | 'VW' ] >>>>> >>>>> It returns 'Squeak' on GNU Smalltalk. This is consistent with my >>>>> analysis of Alan's snippet. Unfortunately I don't have at hand my >>>>> copy >>>>> of the standard. >>>> >>>> FWIW, Smalltalk/X returns 'VW' >>> >>> That's the correct behavior. The standard says the search should proceed >>> from the last exception handler that was created up to the oldest. >> >> Agreed. The ANSI standard seems quite clear about that: >> >> 5.4.3.3: "If signaling of an exception results in evaluation of action >> the evaluation will occur in the context of the handler environment." >> >> 5.5.2.1: "If a matching handler is found, the exception action of the >> handler is evaluated in the exception environment that was current >> when the handler was created and the state of the current exception >> environment is preserved as the signaling environment." >> >>> (That said, Squeak/gst's behavior is quite easy to justify, as stack >>> unwinding hasn't happened yet. I'll wait for this thread to settle >>> before >>> changing it in gst). >> >> But stack unwinding shouldn't need to happen until one of the #on:do: >> calls is actually ready to return. Until then, its all just searching. >> >> I think Squeak/Pharo's problem is that it doesn't maintain a first >> class "exception environment" as described by the glossary in the ANSI >> standard: "An abstract entity that is a LIFO list of exception >> handlers. An exception environment may be logically searched starting >> from the most recently "pushed" exception handler." >> >> Squeak/Pharo simply (ab)uses the context chain, walking it looking for >> the next handler (see the implementation of #signal, which always >> starts searching from thisContext). This works fine most of the time >> but not when you need to temporarily restore a previous exception >> environment. #handleSignal: does go to the effort of setting a >> handlerContext on the signaled exception before calling the action >> block. This is necessary to implement #pass, #isNested, and so on but >> would also need to be put somewhere that #signal could get at it to >> use as a starting point for the search. >> >> This seems like a squeak/pharo bug to me. I don't much feel like >> fixing it in Grease given that Grease is supposed to assume correct >> ANSI implementation as a pre-requisite. Perhaps we can broker a deal >> where Squeak/Pharo will fix this and VW (finally) fixes its signaling >> behaviour so we can drop GRError, etc. entirely. >> >> In the meantime, though, how would we fix the Seaside code assuming we >> had ANSI-correct exception handling implementations? >> >> Julian >> >> > > >

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev January 2011