seaside-dev October 2009

seaside-dev@lists.squeakfoundation.org

19 participants
15 discussions

Seaside on Squeak
by Michael Davies 28 Oct '09

28 Oct '09

Just a note that I've successfully loaded Seaside into Squeak version http://ftp.squeak.org/trunk/Squeak3.10.2-Trunk-091024.zip using (Installer squeaksource project: 'Seaside30') install: 'LoadOrderTest'. There was one minor problem in loading Seaside - in Squeak Trunk, Dictionary>>keys now returns an Array, not a Set, so the attached change to SeasideLoadOrderTests is required. Apart from that hiccup all appears to work well: 1091 run, 1089 passes, 2 expected failures, 0 failures, 0 errors, 0 unexpected passes and functional tests look okay. I chose to run tests while loading, and ended up with many instances of WATestServerAdaptor registered with the server manager - is this expected behaviour? (Note that this isn't me volunteering to support Seaside Squeak!)

4 7

Seaside Swazoo Packages and LGPL
by Lukas Renggli 26 Oct '09

26 Oct '09

Why is Seaside-Adaptors-Swazoo tagged as LGPL but not in the http://www.squeaksource.com/Seaside30LGPL? Shouldn't it just be Seaside-Swazoo that is tagged as LGPL (currently missing)? Lukas -- Lukas Renggli http://www.lukas-renggli.ch

4 3

[ANN] JQWidgetBox now with font effect, week calendar and sheet
by Torsten Bergmann 14 Oct '09

14 Oct '09

The jquery widget box now additionally contains basic wrappers for: http://www.redredred.com.au/projects/jquery-week-calendar/ http://www.iofo.it/jquery/fonteffect/ http://jqueryplugins.weebly.com/jquerysheet.html Download the source for Seaside 3.0. from htt://squeaksource.com/Seaside30Addons and point your browser to http://localhost/browse/jquery-widgets Bye T. -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

1 0

Re: [Seaside-dev] Metacello config for Seaside 3.0
by Dale Henrichs 13 Oct '09

13 Oct '09

Both Metacello and SeasideConfiguration have been ported to Squeak (based on Squeak3..10.10.2-Trunk-090912 with OB loaded). Version 1.0-beta.2 of Metacello runs on both Squeak and Pharo. Load Seaside-Metacello-Configuration-dkh.13 and follow the instuctions below. Dale ----- "Dale Henrichs" <dale.henrichs(a)gemstone.com> wrote: | In the last several weeks I've been working feverishly to bring | Metacello to beta and yesterday I finally made it:). | | Metacello sports a brand spanking new API that takes inspiration from | Flair and constructive criticism from Doru:) In fact, the new API was | driven by some of the awkwardness in the old API when configuring | Seaside3.0. | | To take the loader for a spin, load | Seaside-Metacello-Configuration-dkh.11 from | http://seaside.gemstone.com/ss/Seaside30. Once loaded, you can get | started by trying the helper methods: | | SeasideConfiguration loadLatestPackages. | | SeasideConfiguration loadLatestVersion | SeasideConfiguration loadLatestVersion: { <list of package names> } | | #loadLatestPackages loads the latest version of each Seaside package. | | #loadLatestVersion loads all of the packages associated with the | 3.0.0-alpha5 release. | | If you are interested in loading just a subset of the Seaside | packages, you can use #loadLatestVersion: and pass in a list of | packages like the following: | | SeasideConfiguration loadLatestVersion: | { 'Environment'. 'Flow'. 'Functional Tests'. 'Comanche'. }. | | This is the set of packages I loaded to discover issue 484. In the | above example I am using group names, but specific package names can | be used as well - all of the dependents for that package are loaded. | | Metacello 1.0-beta.1 has only been tested on Pharo and uses the latest | version of Gofer. My next task will be to get Metacello 1.0-beta | running on Squeak and when I do I will make sure that Seaside loads on | Squeak as well. The challenge will be with Gofer, since I've had | Metacello running on Squeak in the past:) | | After the Squeak port, I will port Gofer and Metacello to GemStone and | resume the Seaside3.0 GemStone port. | | I will be working on a tutorial for the new Metacello API over the | next several weeks and until then you can look at | MetacelloReferenceConfig which lists the full API for Metacello | configurations. | | Dale | _______________________________________________ | seaside-dev mailing list | seaside-dev(a)lists.squeakfoundation.org | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

1 0

Metacello config for Seaside 3.0
by Dale Henrichs 11 Oct '09

11 Oct '09

In the last several weeks I've been working feverishly to bring Metacello to beta and yesterday I finally made it:). Metacello sports a brand spanking new API that takes inspiration from Flair and constructive criticism from Doru:) In fact, the new API was driven by some of the awkwardness in the old API when configuring Seaside3.0. To take the loader for a spin, load Seaside-Metacello-Configuration-dkh.11 from http://seaside.gemstone.com/ss/Seaside30. Once loaded, you can get started by trying the helper methods: SeasideConfiguration loadLatestPackages. SeasideConfiguration loadLatestVersion SeasideConfiguration loadLatestVersion: { <list of package names> } #loadLatestPackages loads the latest version of each Seaside package. #loadLatestVersion loads all of the packages associated with the 3.0.0-alpha5 release. If you are interested in loading just a subset of the Seaside packages, you can use #loadLatestVersion: and pass in a list of packages like the following: SeasideConfiguration loadLatestVersion: { 'Environment'. 'Flow'. 'Functional Tests'. 'Comanche'. }. This is the set of packages I loaded to discover issue 484. In the above example I am using group names, but specific package names can be used as well - all of the dependents for that package are loaded. Metacello 1.0-beta.1 has only been tested on Pharo and uses the latest version of Gofer. My next task will be to get Metacello 1.0-beta running on Squeak and when I do I will make sure that Seaside loads on Squeak as well. The challenge will be with Gofer, since I've had Metacello running on Squeak in the past:) After the Squeak port, I will port Gofer and Metacello to GemStone and resume the Seaside3.0 GemStone port. I will be working on a tutorial for the new Metacello API over the next several weeks and until then you can look at MetacelloReferenceConfig which lists the full API for Metacello configurations. Dale

1 0

[ANN] Seaside 3.0a5
by Julian Fitzell 09 Oct '09

09 Oct '09

We are happy to announce the release of Seaside 3.0a5. The first thing you will notice is that, as announced at ESUG, we have changed the naming from 2.9 to 3.0. This is the same line of development but we felt that the improvements in architecture justified increasing the major version number. Seaside 3.0 will provide a solid base for more incremental changes moving forward. We expect that this will be the final alpha release before moving to beta. Bugs fixed and major changes since 2.9a4 are listed under "Closed Issues" below. 1. The Seaside Builder ====================== As with the previous release, the easiest way to load it is to use the Seaside Builder to load the Seaside 3.0 packages you want into any recent Pharo image. Do not try to load into an image that already contains Seaside 2.8, such as the Pharo-web images. http://builder.seaside.st While it is theoretically possible to upgrade a 2.9a4 image to this release using Monticello, we don't recommend it. Figuring what order to load all the packages can be tricky and you can quickly find yourself in a mess. Please note, that the package Seaside-Tools-OmniBrowser requires a recent installation of OmniBrowser, such as 2.0.3. You should load this before loading Seaside as the the Builder does not currently load it for you. 2. Things to be aware of ======================== Please remember that this is an Alpha release and things are still subject to change. You'll find a list of current migration issues at <http://seaside.st/documentation/migration/28to29>. 3. When things go wrong ======================= If you run into problems, please let us know using the issue tracker at <http://code.google.com/p/seaside/issues/list> or through the mailing list. 4. Closed Issues ================ Issue 406: incremental load test failures after loading Environment tests Issue 407: JQuery slider demo is broken Issue 411: MNU when starting a comanche adaptor with WAKom Issue 412: entry points can be registered in to Dispatchers at once and the parent is wrong in one Issue 413: setting current request is spread around the codebase Issue 401: replace Character class >> #value: with Character class >> #codePoint: Issue 419: WARequest missing http version Issue 371: improper encoding in 2.9a3 Issue 422: WAChoiceDialog specifying the default selected item Issue 426: Broken link on seaside.st Issue 424: WAUrl doesn't remember trailing slash Issue 431: CTPusher>>#javascript: is broken after Javascript #renderContext and #rendererClass refactoring Issue 429: Scriptaculous and JQuery Demos Issue 116: Improve profiler on Squeak Issue 357: Almost imposible to create a functonal SUUpdater without using the 'html' Issue 430: Screenshot application broken in the latest Pharo Issue 89: Provide an AJP connector Issue 398: default quality of WAAccpet should be 1 Issue 437: WASession >> #updateRoot: shouldn't do any HTML Issue 352: WAUrlEncodingFunctionalTest broken on Swazoo Issue 433: Rename "-Squeak" to "-Pharo" in Package names Issue 439: Support JSON dictionary serialization Issue 440: provide access to unconsumed path elements Issue 428: loading an image seems to start all server adaptors Issue 416: add WARegistry>>handlers? (and WAApplication>>sessions?) Issue 445: WABasicFormTag does not honour character encoding setting Issue 450: Cure from swine flu Issue 420: no tests for #readFrom: Issue 361: Click on Start button in the empty Seaside control panel gives DNU Issue 215: Several packages have soft dependencies on the Session package Issue 409: Component package should not depend on Canvas package Issue 301: add control panel command to clear config cache Issue 423: 2 tests for WAPlatform current readWriteStream fail Issue 309: WACurrentSessionContinuationTest Issue 384: WAClosureFunctionalTest "go with ensure" Issue 448: remove name from WAEntryPoint Issue 235: WAExternalFileLibraryTest>>testPathForRequest fails on windows Issue 427: Right mouse button doesn't work in Seaside one-click 2.8.4 Windows Issue 446: One-Click settings are wrong Issue 457: add /seaside redirect handler Issue 432: Tutorial is outdated Issue 418: WARequest missing 'body' Issue 456: WADispatcherComponentTest >> #testNestedDispatcher fails Issue 458: Need a functional test for WARequest>>body Issue 442: Server manager doesn't detect failed adaptor startup Issue 459: Incorrect reference to Pharo Browser class on Seaside-Development Issue 460: Prototype #triggerForm: is broken Issue 464: WARequest>>bodyDecoded sends unimplemented #bodyAsStringUsing: message Issue 468: Use of Delay on CTPusher class>>startUp and pingProcess Issue 470: add conditional comment support for IE 8 Issue 463: WAXmlRoot sends #defaultCharSet ... not implemented Issue 465: RRRfc822DateTime>>encodeOn: should use English locale date names on all platforms Issue 461: WAUrl >> #encodeOn: assumes HTML Issue 454: remove parent from WAEntry point Issue 217: WACollectionAttribute Issue 477: multiple copies of timing filter and and deprecation filter added

4 4

Re: [Seaside Commits] Seaside 3.0: Seaside-Pharo-Development-obi.17.mcz
by Lukas Renggli 08 Oct '09

08 Oct '09

Wouldn't it make more sense to add an additional field called 'license' to WAPackage that is #MIT by default but can be changed to #LGPL? 2009/10/6 <squeak-dev-noreply(a)lists.squeakfoundation.org>: > Gerhard Obermann uploaded a new version of Seaside-Pharo-Development to project Seaside 3.0: > http://www.squeaksource.com/Seaside30/Seaside-Pharo-Development-obi.17.mcz > > ==================== Summary ==================== > > Name: Seaside-Pharo-Development-obi.17 > Author: obi > Time: 7 October 2009, 7:41:59 am > UUID: 19eb022f-9992-cf48-9aa1-258b1615e973 > Ancestors: Seaside-Pharo-Development-obi.16 > > - really use LGPL packages > > =============== Diff against Seaside-Pharo-Development-obi.16 =============== > > Item was changed: > ----- Method: WADevelopment class>>packagesLGPL (in category 'accessing') ----- > packagesLGPL > "Answer a list of Seaside LGPL licensed packages as PackageInfo instances. Its a hack because only the description can be currently used to filter the LGPL packages" > + ^ ((GRPackage packages select: [:each | each description notNil and: [each description includesSubString: '(LGPL)'] ]) sortBy: [ :a :b | a name < b name ]) collect: [ :each | PackageInfo named: each name ]! > - ^ ((GRPackage packages select: [:each | each description notNil and: ['*(LGPL)*' match: each description ] ]) sortBy: [ :a :b | a name < b name ]) collect: [ :each | PackageInfo named: each name ]! > > Item was changed: > ----- Method: WADevelopment class>>packagesMIT (in category 'accessing') ----- > packagesMIT > "Answer a list of Seaside MIT licensed packages as PackageInfo instances." > + ^ ((GRPackage packages select: [:each | each description isNil or: [(each description includesSubString: '(LGPL)') not] ]) sortBy: [ :a :b | a name < b name ]) collect: [ :each | PackageInfo named: each name ]! > - ^ ((GRPackage packages select: [:each | each description notNil and: [('*(LGPL)*' match: each description) not] ]) sortBy: [ :a :b | a name < b name ]) collect: [ :each | PackageInfo named: each name ]! > > Item was added: > + ----- Method: WADevelopment class>>addSeasideLGPLRepository (in category 'monticello-repositories') ----- > + addSeasideLGPLRepository > + self addRepository: self defaultLGPLRepository toWorkingCopies: (self workingCopiesFor: self packagesLGPL)! > > Item was added: > + ----- Method: WADevelopment class>>defaultLGPLRepository (in category 'monticello-repositories') ----- > + defaultLGPLRepository > + ^ self seaside30LGPLRepository! > > Item was removed: > - ----- Method: WADevelopment class>>addSeasideRepositoryLGPL (in category 'monticello-repositories') ----- > - addSeasideRepositoryLGPL > - self addRepository: self defaultRepository toWorkingCopies: (self workingCopiesFor: self packagesLGPL)! > > > _______________________________________________ > commits mailing list > To unsubscribe, email commits-leave(a)lists.seaside.st > http://lists.seaside.st/listinfo/commits > -- Lukas Renggli http://www.lukas-renggli.ch

4 3

Re: [Seaside-dev] registering a callback
by sebastian＠flowingconcept.com 08 Oct '09

08 Oct '09

#withoutParameters should not be sent if _s and _k is needed. Fixed and translated to a more clean version: ^ JSFunction new add: (html javascript goto: (html prototype request callback:[self defaultCallbackAction]; fullUrl)); yourself Note: the prototype way is the same as jquery but it requires the fullUrl method to be implemented in PTAjax thanks to Esteban Lorenzano sebastian ----- Original Message ----- From: sebastian(a)flowingconcept.com To: "seaside-dev" <seaside-dev(a)lists.squeakfoundation.org> Sent: Wednesday, October 7, 2009 11:21:57 PM (GMT-0300) Auto-Detected Subject: [Seaside-dev] registering a callback Hi there, if is needed to register a callback in order to make a typical seaside (non ajaxian) callback, would you use a snippet of code like this: callbackId := html callbacks store: (WAActionCallback on: [self defaultCallbackAction]). actionUrl := html context actionUrl withoutParameters addParameter: callbackId. ^ JSFunction new add: ('window.location.href="',actionUrl asString,'"') asJSObject; yourself or.. do you see something wrong on using that? thanks, sebastian _______________________________________________ seaside-dev mailing list seaside-dev(a)lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

1 0

registering a callback
by sebastian＠flowingconcept.com 08 Oct '09

08 Oct '09

Hi there, if is needed to register a callback in order to make a typical seaside (non ajaxian) callback, would you use a snippet of code like this: callbackId := html callbacks store: (WAActionCallback on: [self defaultCallbackAction]). actionUrl := html context actionUrl withoutParameters addParameter: callbackId. ^ JSFunction new add: ('window.location.href="',actionUrl asString,'"') asJSObject; yourself or.. do you see something wrong on using that? thanks, sebastian

1 0

speedup WAEncoder
by Torsten Bergmann 07 Oct '09

07 Oct '09

>The attached changeset What's the license? Hopefully this is MIT, not GNU. Bye T. -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev October 2009