seaside-dev January 2010

seaside-dev@lists.squeakfoundation.org

12 participants
20 discussions

GRTestsFunctionalPlatformTest>>#testGarbageCollect
by James Foster 17 Feb '10

17 Feb '10

All, I've updated the SeasideLoadOrderTests and found a problem with GRTestsFunctionalPlatformTest>>#testGarbageCollect. This test exists early and fails until Seaside-Tests-Pharo-Functional is loaded. This indicates some load order dependency. What is in Functional that should be in Core? Or should the test be moved to Functional? Otherwise, things seem to be quite clean! James Loaded Grease-Core-dkh.8.mcz Loaded Grease-Pharo-Core-dkh.4.mcz Loaded Grease-Tests-Core-jf.7.mcz Loaded Grease-Tests-Pharo-Core-dkh.2.mcz 217 run, 214 passes, 2 expected failures, 1 failures, 0 errors, 0 unexpected passes GRTestsFunctionalPlatformTest>>#testGarbageCollect Loaded Seaside-Core-dkh.590.mcz Loaded Seaside-Tests-Core-jf.167.mcz Loaded Seaside-Tests-UTF8-pmm.7.mcz Loaded Seaside-Pharo-Core-jf.3.mcz Loaded Seaside-Tests-Pharo-Core-dkh.6.mcz 595 run, 592 passes, 2 expected failures, 1 failures, 0 errors, 0 unexpected passes GRTestsFunctionalPlatformTest>>#testGarbageCollect Loaded Seaside-Canvas-pmm.74.mcz Loaded Seaside-Pharo-Canvas-jf.2.mcz Loaded Seaside-Tests-Canvas-jf.40.mcz 673 run, 670 passes, 2 expected failures, 1 failures, 0 errors, 0 unexpected passes GRTestsFunctionalPlatformTest>>#testGarbageCollect Loaded Seaside-Session-dkh.125.mcz Loaded Seaside-Tests-Session-jf.33.mcz 721 run, 718 passes, 2 expected failures, 1 failures, 0 errors, 0 unexpected passes GRTestsFunctionalPlatformTest>>#testGarbageCollect Loaded Seaside-Component-lr.79.mcz Loaded Seaside-Tests-Component-lr.26.mcz 734 run, 731 passes, 2 expected failures, 1 failures, 0 errors, 0 unexpected passes GRTestsFunctionalPlatformTest>>#testGarbageCollect Loaded Seaside-RenderLoop-jf.68.mcz Loaded Seaside-Tests-RenderLoop-jf.9.mcz 734 run, 731 passes, 2 expected failures, 1 failures, 0 errors, 0 unexpected passes GRTestsFunctionalPlatformTest>>#testGarbageCollect Loaded Seaside-Tools-Core-jf.12.mcz 734 run, 731 passes, 2 expected failures, 1 failures, 0 errors, 0 unexpected passes GRTestsFunctionalPlatformTest>>#testGarbageCollect Loaded Seaside-Widgets-dkh.7.mcz 734 run, 731 passes, 2 expected failures, 1 failures, 0 errors, 0 unexpected passes GRTestsFunctionalPlatformTest>>#testGarbageCollect Loaded Seaside-Environment-lr.65.mcz Loaded Seaside-Pharo-Environment-jf.4.mcz Loaded Seaside-Tests-Environment-jf.19.mcz 739 run, 736 passes, 2 expected failures, 1 failures, 0 errors, 0 unexpected passes GRTestsFunctionalPlatformTest>>#testGarbageCollect Loaded Seaside-Tests-Functional-pmm.95.mcz Loaded Seaside-Tests-Pharo-Functional-dkh.7.mcz 741 run, 739 passes, 2 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Seaside-Pharo-Continuation-lr.4.mcz Loaded Seaside-Tests-Pharo-Continuation-lr.4.mcz 757 run, 755 passes, 2 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Seaside-Flow-dkh.18.mcz Loaded Seaside-Pharo-Flow-jf.3.mcz Loaded Seaside-Tests-Flow-jf.20.mcz 758 run, 756 passes, 2 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Seaside-Tools-Web-lr.65.mcz Loaded Seaside-Pharo-Tools-Web-jf.6.mcz Loaded Seaside-Tests-Tools-Web-jf.11.mcz 761 run, 759 passes, 2 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Seaside-Development-dkh.122.mcz Loaded Seaside-Pharo-Development-lr.26.mcz Loaded Seaside-Tests-Development-jf.32.mcz Loaded Seaside-Tests-Pharo-Development-jf.3.mcz 765 run, 763 passes, 2 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Seaside-Examples-jf.15.mcz Loaded Seaside-Tests-Examples-jf.6.mcz 767 run, 765 passes, 2 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Seaside-Tools-OmniBrowser-jf.11.mcz Loaded Seaside-Pharo-Tools-OmniBrowser-jf.3.mcz 767 run, 765 passes, 2 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded RSS-Core-jf.56.mcz Loaded RSS-Tests-Core-jf.21.mcz Loaded RSS-Examples-dkh.20.mcz 776 run, 774 passes, 2 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Javascript-Core-dkh.69.mcz Loaded Javascript-Pharo-Core-jf.2.mcz Loaded Javascript-Tests-Core-jf.45.mcz 878 run, 876 passes, 2 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded JQuery-Core-lr.90.mcz Loaded JQuery-Tests-Core-lr.94.mcz Loaded JQuery-UI-lr.42.mcz Loaded JQuery-Tests-UI-lr.56.mcz 1060 run, 1058 passes, 2 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Prototype-Core-jf.12.mcz Loaded Prototype-Tests-Core-jf.5.mcz 1094 run, 1092 passes, 2 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Scriptaculous-Core-jf.93.mcz Loaded Scriptaculous-Tests-Core-dkh.39.mcz Loaded Scriptaculous-Components-dkh.92.mcz Loaded Scriptaculous-Tests-Components-dkh.27.mcz 1105 run, 1103 passes, 2 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Seaside-HTML5-jf.7.mcz Loaded Seaside-Tests-HTML5-jf.14.mcz 1105 run, 1103 passes, 2 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Seaside-InternetExplorer-jf.5.mcz Loaded Seaside-Tests-InternetExplorer-jf.8.mcz 1111 run, 1109 passes, 2 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Seaside-Email-dkh.14.mcz Loaded Seaside-Tests-Email-jf.6.mcz Loaded Seaside-Pharo-Email-dkh.5.mcz 1115 run, 1113 passes, 2 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded DynamicBindings-damiencassou.9.mcz Loaded KomServices-gc.19.mcz Loaded KomHttpServer-damiencassou.47.mcz Loaded Seaside-Adaptors-Comanche-pmm.51.mcz Loaded Seaside-Tests-Adaptors-Comanche-jf.11.mcz 1123 run, 1121 passes, 2 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Comet-Core-jf.42.mcz Loaded Comet-Pharo-Core-jf.3.mcz Loaded Comet-Tests-Core-jf.7.mcz Loaded Comet-Examples-lr.15.mcz 1126 run, 1124 passes, 2 expected failures, 0 failures, 0 errors, 0 unexpected passes

4 7

Re: ConfigurationOfSeaside available
by Dale Henrichs 31 Jan '10

31 Jan '10

Norbert, If you are intending to use Pier and Seaside3.0 in GemStone, I haven't done the port of Pier2 to GemStone yet ... I need to get to the point where GemStone is using the common configurations for Seaside/Magritte/Pier which I'm aiming for in GLASS 1.0-beta.7 ... Once that's done, the port can follow on. Dale ----- "Norbert Hartl" <norbert(a)hartl.name> wrote: | Dale, | | that is just perfect. Thanks to all porting pier to seaside 3. I tried | to google about the progress of pier on seaside 3. I didn't read this | mailing list the last months. So I'm again right on time to save me | some work. Thanks. We just moved to a new server using openvz so I | have a second machine running gemstone just waiting to load pier2. Are | there any problems known exporting a pier tree from pier1 and import | it into pier2? | | thanks a lot, | | Norbert | | On 27.01.2010, at 02:33, Dale Henrichs wrote: | | > First load the configuration. | > | > For Pharo: | > Gofer new | > squeaksource: 'MetacelloRepository'; | > package: 'ConfigurationOfSeaside'; | > load. | > For Squeak: | > - load the latest version of ConfigurationOfSeaside from | http://www.squeaksource.com/MetacelloRepository | > | > | > Then pick the Seaside variant you want to load: | > | > "Seaside 2.8" | > ConfigurationOfSeaside project latestVersion load: 'Seaside 2.8'. | > ConfigurationOfSeaside project latestVersion load: 'Seaside 2.8 | Examples'. | > ConfigurationOfSeaside project latestVersion load: 'Magritte'. | > ConfigurationOfSeaside project latestVersion load: 'Magritte | Tests'. | > ConfigurationOfSeaside project latestVersion load: 'Pier'. | > ConfigurationOfSeaside project latestVersion load: 'Pier Tests'. | > ConfigurationOfSeaside project latestVersion load: 'Pier AddOns'. | > | > "Seaside 3.0" | > ConfigurationOfSeaside project latestVersion load: 'Seaside 3.0'. | > ConfigurationOfSeaside project latestVersion load: 'Seaside 3.0 | Tests'. | > ConfigurationOfSeaside project latestVersion load: 'Magritte2'. | > ConfigurationOfSeaside project latestVersion load: 'Magritte2 | Tests'. | > ConfigurationOfSeaside project latestVersion load: 'Pier2'. | > ConfigurationOfSeaside project latestVersion load: 'Pier2 Tests'. | > ConfigurationOfSeaside project latestVersion load: 'Pier2 AddOns'. | > | > I've tested the various loads with PharoCore-1.0-10508rc2 and | Squeak3.11-8931-alpha. The tests aren't 100% green on either | platform... | > | > Dale | > _______________________________________________ | > Magritte, Pier and Related Tools ... | > https://www.iam.unibe.ch/mailman/listinfo/smallwiki

1 0

note to porters
by Julian Fitzell 31 Jan '10

31 Jan '10

Since I fixed Issue 405, ServerAdaptors should now be ensuring that the URL put into the Request includes the queryString parameters. You should also now use #setPostFields: instead of #setFields: and ensure that it contains only the POST body fields. Julian

3 3

Re: [Seaside Commits] Seaside 3.0: Seaside-Core-lr.607.mcz
by Julian Fitzell 29 Jan '10

29 Jan '10

So, wouldn't it be better to store this on the RenderContext? Or even change CallbackRegistry to store the lastId instead of the nextId. Seems weird adding this instance variable to the Renderer, particularly when the answer the question really should be valid across any renderer within the same context. Julian On Thu, Jan 28, 2010 at 12:05 PM, <squeak-dev-noreply(a)lists.squeakfoundation.org> wrote: > Lukas Renggli uploaded a new version of Seaside-Core to project Seaside 3.0: > http://www.squeaksource.com/Seaside30/Seaside-Core-lr.607.mcz > > ==================== Summary ==================== > > Name: Seaside-Core-lr.607 > Author: lr > Time: 28 January 2010, 9:04:43 pm > UUID: ecc7667e-df27-4509-9f21-a08c6b875c20 > Ancestors: Seaside-Core-jok.606 > > - removed #peekNextId, never saw any users of that > - added #lastId, which is extremely useful for labels and also nicer for people that used #peekNextId > > =============== Diff against Seaside-Core-jok.606 =============== > > Item was changed: > WAObject subclass: #WARenderer > + instanceVariableNames: 'context lastId' > - instanceVariableNames: 'context' > classVariableNames: '' > poolDictionaries: '' > category: 'Seaside-Core-Rendering'! > WARenderer class > instanceVariableNames: 'default'! > > !WARenderer commentStamp: 'jf 2/13/2009 19:57' prior: 0! > A Renderer provides methods for rendering data (typically HTML) onto a Document. It gets all the information needed to do its work from a RenderContext, which is passed in on initialization. > > Renderer are typically controlled by a Painter.! > > Item was changed: > ----- Method: WARenderer>>nextId (in category 'public') ----- > nextId > + "Answer an identifier string that is unique within this RenderContext." > - "Return a identifier string that is unique within this RenderContext." > > + ^ lastId := 'id' , self callbacks advanceKey! > - ^ 'id' , self callbacks advanceKey! > > Item was added: > + ----- Method: WARenderer>>lastId (in category 'public') ----- > + lastId > + "Answer the last identifier that was generated with #nextId." > + > + ^ lastId! > > Item was removed: > - ----- Method: WARenderer>>peekNextId (in category 'public') ----- > - peekNextId > - "Return the indentifier string that will be returned by the next call to #nextId." > - > - ^ 'id' , self callbacks nextKey! > > > _______________________________________________ > commits mailing list > To unsubscribe, email commits-leave(a)lists.seaside.st > http://lists.seaside.st/listinfo/commits >

2 4

Re: [Seaside-dev] ConfigurationOfSeaside available
by Dale Henrichs 28 Jan '10

28 Jan '10

I've just loaded and ran tests on Squeak3.11-8931-alpha: Seaside2.8: 3 failures MAExtentsionsTest>>testTimePrintOn: WABacktrackingTest>>testDictionary WABacktrackingTest>>testOrderedCollection 9 errors WAFileLibraryTests attempting removeAllFoundIn: on an Array and ending with a shouldNotImplement Seaside3.0: 2 failures MAExtentsionsTest>>testTimePrintOn: WABacktrackingTest>>testDictionary BTW, how do you used Installer to get the latest package loaded? I tried (Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfSeaside'. When anm older version of ConfigurationOfSeaside was already loaded. I was hoping Installer would load the later version of the package (Gofer does). Dale ----- "Dale Henrichs" <dale.henrichs(a)gemstone.com> wrote: | A new version of ConfigurationOfSeaside has been pushed (1.0.1) and | all of the tests are green for seaside2.8/magritte/pier and | seaside3.0/magritte/pier (on pharo). | | The scripts stay the same since they use #latestVersion... | | Dale | ----- "Dale Henrichs" <dale.henrichs(a)gemstone.com> wrote: | | | I took the latest code as of (1/22/2010 12:06) ... I'll update push | a | | newer version out ... | | | | Dale | | ----- "Lukas Renggli" <renggli(a)gmail.com> wrote: | | | | | 2010/1/27 Dale Henrichs <dale.henrichs(a)gemstone.com>: | | | > Out of 5219 tests rung: | | | > | | | > Errors: | | | > WAPharoFunctionalTestsDefaultHandlersTest>>testAllTests | | | > Failures: | | | > WACanvasBrushTest>>testMultiSelectTag | | | > WACanvasBrushTest>>testSelectTag | | | | | | These 3 I fixed recently. Did you load the latest code? | | | | | | Lukas | | | | | | | | | > WAPackagingTest>>testPackagingValidity | | | > | | | > The error looks like an initialization issue. the two select | tag | | | failures aren't obvious to me. the WAPackagingTest is on me... | | | > | | | > Dale | | | > ----- "Dale Henrichs" <dale.henrichs(a)gemstone.com> wrote: | | | > | | | > | I will take a closer look today. | | | > | | | | > | Dale | | | > | | | | > | ----- "Dale Henrichs" <dale.henrichs(a)gemstone.com> wrote: | | | > | | | | > | | I haven't looked ... at first blush I figured that things | | were | | | in | | | > | | development and I didn't take the next step:( | | | > | | | | | > | | Dale | | | > | | ----- "Lukas Renggli" <renggli(a)gmail.com> wrote: | | | > | | | | | > | | | > "Seaside 2.8" | | | > | | | > ConfigurationOfSeaside project latestVersion load: | | | 'Seaside | | | > | | 2.8'. | | | > | | | > ConfigurationOfSeaside project latestVersion load: | | | 'Seaside | | | > | 2.8 | | | > | | | Examples'. | | | > | | | > ConfigurationOfSeaside project latestVersion load: | | | 'Magritte'. | | | > | | | > ConfigurationOfSeaside project latestVersion load: | | | 'Magritte | | | > | | | Tests'. | | | > | | | > ConfigurationOfSeaside project latestVersion load: | | 'Pier'. | | | > | | | > ConfigurationOfSeaside project latestVersion load: | 'Pier | | | > | Tests'. | | | > | | | > ConfigurationOfSeaside project latestVersion load: | 'Pier | | | > | | AddOns'. | | | > | | | > | | | > | | | > "Seaside 3.0" | | | > | | | > ConfigurationOfSeaside project latestVersion load: | | | 'Seaside | | | > | | 3.0'. | | | > | | | > ConfigurationOfSeaside project latestVersion load: | | | 'Seaside | | | > | 3.0 | | | > | | | Tests'. | | | > | | | > ConfigurationOfSeaside project latestVersion load: | | | > | 'Magritte2'. | | | > | | | > ConfigurationOfSeaside project latestVersion load: | | | 'Magritte2 | | | > | | | Tests'. | | | > | | | > ConfigurationOfSeaside project latestVersion load: | | | 'Pier2'. | | | > | | | > ConfigurationOfSeaside project latestVersion load: | | 'Pier2 | | | > | | Tests'. | | | > | | | > ConfigurationOfSeaside project latestVersion load: | | 'Pier2 | | | > | | AddOns'. | | | > | | | > | | | > | | | > I've tested the various loads with | PharoCore-1.0-10508rc2 | | | and | | | > | | | Squeak3.11-8931-alpha. The tests aren't 100% green on | | either | | | > | | | platform... | | | > | | | | | | > | | | That's cool. I am going to use that on the build server. | | | > | | | | | | > | | | Why are the tests not green? | | | > | | | | | | > | | | Lukas | | | > | | | | | | > | | | -- | | | > | | | Lukas Renggli | | | > | | | http://www.lukas-renggli.ch | | | > | | _______________________________________________ | | | > | | seaside-dev mailing list | | | > | | seaside-dev(a)lists.squeakfoundation.org | | | > | | | | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev | | | > | | | | | | | | | | | | -- | | | Lukas Renggli | | | http://www.lukas-renggli.ch | | | _______________________________________________ | | | seaside-dev mailing list | | | seaside-dev(a)lists.squeakfoundation.org | | | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev | | _______________________________________________ | | seaside-dev mailing list | | seaside-dev(a)lists.squeakfoundation.org | | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

2 2

[Seaside] [Seaside-dev] Seaside components
by Maximiliano Taborda 28 Jan '10

28 Jan '10

Hello. I am thinking of using seaside to develop a web based application, but I really do not know how seaside can satisfy my needs. I read the book at the seaside site and all is well with the development in the seaside-way. Although, I have the following questions: I would have components like a grid and graphs in my application. Is this possible? I see that seaside includes Scriptaculous and jQuery, so could I use something like this: http://trirand.com/blog/jqgrid/jqgrid.html? This component (or any other like this) exists or, if not, how difficult is to build it? Another example. Searching the web I found this thing called ZK: http://www.zkoss.org/zkdemo/userguide/. There are at seaside grids, graphics and windows as shown in this demo? Thanks in advance for any help. Regards. Maxi

2 2

Re: [Seaside] [Seaside-dev] Seaside components
by Maximiliano Taborda 28 Jan '10

28 Jan '10

2010/1/27 Sean Allen <sean(a)monkeysnatchbanana.com> > > > On Wed, Jan 27, 2010 at 9:18 AM, Maximiliano Taborda <mtaborda(a)gmail.com>wrote: > >> Hello. >> >> I am thinking of using seaside to develop a web based application, but I >> really do not know how seaside can satisfy my needs. >> I read the book at the seaside site and all is well with the development >> in the seaside-way. >> >> Although, I have the following questions: >> I would have components like a grid and graphs in my application. Is this >> possible? >> > > You could write components that create grids and graphs. > If you can do it in html/javascript, you can write a component in seaside > to create a > reusable component to do the same. > > >> I see that seaside includes Scriptaculous and jQuery, so could I >> use something like this: http://trirand.com/blog/jqgrid/jqgrid.html? This component >> (or any other like this) exists or, if not, how difficult is to build it? >> > > There are none included w/ Seaside itself although someone might have > written something like that. I'm not aware of it though. > The difficulty isnt that great, you are taking the html and javascript that > would be used and write code that given a certain set > of inputs would create the appropriate output. Its basically the same as > how it would be in any other language/framework except that seaside > components are > stateful so in some ways, once you know what you are doing, its easier. > > > >> Another example. Searching the web I found this thing called ZK: >> http://www.zkoss.org/zkdemo/userguide/. There are at seaside grids, >> graphics and windows as shown in this demo? >> > > I don't understand this last question. If you are asking if seaside has > built in componenets similiar to that then the answer is no. > Yes, that was my question. Thanks. Maxi > > My general statement would be, yes all of this is possible, the learning > curve might be a little high for someone starting out with Seaside. > > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > >

1 0

Re: [Seaside-dev] ConfigurationOfSeaside available
by Dale Henrichs 28 Jan '10

28 Jan '10

I took the latest code as of (1/22/2010 12:06) ... I'll update push a newer version out ... Dale ----- "Lukas Renggli" <renggli(a)gmail.com> wrote: | 2010/1/27 Dale Henrichs <dale.henrichs(a)gemstone.com>: | > Out of 5219 tests rung: | > | > Errors: | > WAPharoFunctionalTestsDefaultHandlersTest>>testAllTests | > Failures: | > WACanvasBrushTest>>testMultiSelectTag | > WACanvasBrushTest>>testSelectTag | | These 3 I fixed recently. Did you load the latest code? | | Lukas | | | > WAPackagingTest>>testPackagingValidity | > | > The error looks like an initialization issue. the two select tag | failures aren't obvious to me. the WAPackagingTest is on me... | > | > Dale | > ----- "Dale Henrichs" <dale.henrichs(a)gemstone.com> wrote: | > | > | I will take a closer look today. | > | | > | Dale | > | | > | ----- "Dale Henrichs" <dale.henrichs(a)gemstone.com> wrote: | > | | > | | I haven't looked ... at first blush I figured that things were | in | > | | development and I didn't take the next step:( | > | | | > | | Dale | > | | ----- "Lukas Renggli" <renggli(a)gmail.com> wrote: | > | | | > | | | > "Seaside 2.8" | > | | | > ConfigurationOfSeaside project latestVersion load: | 'Seaside | > | | 2.8'. | > | | | > ConfigurationOfSeaside project latestVersion load: | 'Seaside | > | 2.8 | > | | | Examples'. | > | | | > ConfigurationOfSeaside project latestVersion load: | 'Magritte'. | > | | | > ConfigurationOfSeaside project latestVersion load: | 'Magritte | > | | | Tests'. | > | | | > ConfigurationOfSeaside project latestVersion load: 'Pier'. | > | | | > ConfigurationOfSeaside project latestVersion load: 'Pier | > | Tests'. | > | | | > ConfigurationOfSeaside project latestVersion load: 'Pier | > | | AddOns'. | > | | | > | > | | | > "Seaside 3.0" | > | | | > ConfigurationOfSeaside project latestVersion load: | 'Seaside | > | | 3.0'. | > | | | > ConfigurationOfSeaside project latestVersion load: | 'Seaside | > | 3.0 | > | | | Tests'. | > | | | > ConfigurationOfSeaside project latestVersion load: | > | 'Magritte2'. | > | | | > ConfigurationOfSeaside project latestVersion load: | 'Magritte2 | > | | | Tests'. | > | | | > ConfigurationOfSeaside project latestVersion load: | 'Pier2'. | > | | | > ConfigurationOfSeaside project latestVersion load: 'Pier2 | > | | Tests'. | > | | | > ConfigurationOfSeaside project latestVersion load: 'Pier2 | > | | AddOns'. | > | | | > | > | | | > I've tested the various loads with PharoCore-1.0-10508rc2 | and | > | | | Squeak3.11-8931-alpha. The tests aren't 100% green on either | > | | | platform... | > | | | | > | | | That's cool. I am going to use that on the build server. | > | | | | > | | | Why are the tests not green? | > | | | | > | | | Lukas | > | | | | > | | | -- | > | | | Lukas Renggli | > | | | http://www.lukas-renggli.ch | > | | _______________________________________________ | > | | seaside-dev mailing list | > | | seaside-dev(a)lists.squeakfoundation.org | > | | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev | > | | | | -- | Lukas Renggli | http://www.lukas-renggli.ch | _______________________________________________ | seaside-dev mailing list | seaside-dev(a)lists.squeakfoundation.org | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

2 3

ConfigurationOfSeaside available
by Dale Henrichs 27 Jan '10

27 Jan '10

First load the configuration. For Pharo: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside'; load. For Squeak: - load the latest version of ConfigurationOfSeaside from http://www.squeaksource.com/MetacelloRepository Then pick the Seaside variant you want to load: "Seaside 2.8" ConfigurationOfSeaside project latestVersion load: 'Seaside 2.8'. ConfigurationOfSeaside project latestVersion load: 'Seaside 2.8 Examples'. ConfigurationOfSeaside project latestVersion load: 'Magritte'. ConfigurationOfSeaside project latestVersion load: 'Magritte Tests'. ConfigurationOfSeaside project latestVersion load: 'Pier'. ConfigurationOfSeaside project latestVersion load: 'Pier Tests'. ConfigurationOfSeaside project latestVersion load: 'Pier AddOns'. "Seaside 3.0" ConfigurationOfSeaside project latestVersion load: 'Seaside 3.0'. ConfigurationOfSeaside project latestVersion load: 'Seaside 3.0 Tests'. ConfigurationOfSeaside project latestVersion load: 'Magritte2'. ConfigurationOfSeaside project latestVersion load: 'Magritte2 Tests'. ConfigurationOfSeaside project latestVersion load: 'Pier2'. ConfigurationOfSeaside project latestVersion load: 'Pier2 Tests'. ConfigurationOfSeaside project latestVersion load: 'Pier2 AddOns'. I've tested the various loads with PharoCore-1.0-10508rc2 and Squeak3.11-8931-alpha. The tests aren't 100% green on either platform... Dale

2 5

Seaside components
by Torsten Bergmann 27 Jan '10

27 Jan '10

Hi, Seaside as a framework (only the vehicle) - so dont expect all widgets you find neat already wrapped there. But there is support code in the framework and there are additional projects like the JQueryWidgetBox project [1]. Just click on "Wiki" on this site to see which jquery components are already wrapped in the box. If you want to try JQueryWidgetBox in your image just use the short guide in [2] or [3]. Seaside also comes with default jquery stuff (like jquery UI). And there is Scriptaculous. There are also various chart and component libraries for Seaside wrapped (see [4], [5], [6] and [7] for more examples). Just google for Seaside, charts, SVG and the like or ask on the list. You can also visit http://www.seaside.st/about/examples So many things are there to build your application. But it depends on your needs - if you need specific widgets you may have to implement them. Best way is to browse the code and learn how it is done - then you can use any component, script, ... you find on the net. Bye T. [1] http://www.squeaksource.com/JQueryWidgetBox.html [2] http://lists.squeakfoundation.org/pipermail/seaside/2010-January/022335.html [3] http://astares.blogspot.com/2010/01/pharo-10-release-candidate-2-and-image.… [4] http://astares.blogspot.com/2008/12/flash-charts-for-seaside.html [5] http://shorecomponents.seasidehosting.st [6] http://astares.blogspot.com/2008/04/seaside-and-svg_18.html [7] http://seachart.seasidehosting.st/ -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev January 2010