Seaside for Dolphin alpha
Locked
 
|
http://www.seaside.st/Download/Dolphin/
need to download my swazoo port as well http://www.arcturus.com.au/dolphin/ (I really should update that, sorry Janko!) |
Re: Seaside for Dolphin alpha
|
|
Hi,
Excelent news! :-) What's the status of the Swazoo port? I mean, AFAIR there are two or three different versions around, being some of them branched. Sean: from what branch does your version descend? Janko: Does your version includes what's in the Sean version? What are the differences with the "Hyper swazoo" version from B. Badger/OpenSkills? Best regards, -- Esteban. |
|
|
In reply to this post by Sean M-8
Just to report my experience loading the provided packages...
The following are defined in Swazoo but replace identical (?) methods in the Dolphin package: KernelLibrary>>getSystemTime: TimeStamp class>>currentUTC SYSTEMTIME class>>nowUTC The following globals are referenced in Seaside but not defined (causing errors on load): Browser Month Text James "Sean M" <[hidden email]> wrote in message news:R0xdg.2483$[hidden email]... > http://www.seaside.st/Download/Dolphin/ > > need to download my swazoo port as well > > http://www.arcturus.com.au/dolphin/ > > (I really should update that, sorry Janko!) > > > |
|
|
And to report my experience when attempting to run the counter demo...
Internal Error WAStateHolder does not understand #snapshotCopy a MessageNotUnderstood('WAStateHolder does not understand #snapshotCopy') WAStateHolder(Object)>>doesNotUnderstand: WAStateRegistry>>registerObject: WASession>>registerObjectForBacktracking: WAStateHolder class>>new WAWalkback(WAComponent)>>initializeDecoration WAWalkback class(WAComponent class)>>new WAWalkbackErrorHandler>>handleError: WAWalkbackErrorHandler class(WAErrorHandler class)>>handleError: [] in WASession>>withErrorHandler: [] in MessageNotUnderstood(Exception)>>_evaluateHandler:in: BlockClosure>>ifCurtailed: BlockClosure>>ensure: MessageNotUnderstood(Exception)>>_evaluateHandler:in: MessageNotUnderstood(Exception)>>_propagateFrom: MessageNotUnderstood(Exception)>>_propagate MessageNotUnderstood(Exception)>>signal MessageNotUnderstood class>>receiver:message: WAStateHolder(Object)>>doesNotUnderstand: WAStateRegistry>>registerObject: WASession>>registerObjectForBacktracking: |
|
|
In reply to this post by Esteban A. Maringolo
Hi Esteban,
Esteban A. Maringolo wrote: > Hi, > > Excelent news! :-) > > What's the status of the Swazoo port? > I mean, AFAIR there are two or three different versions around, being > some of them branched. > > Sean: from what branch does your version descend? > Janko: Does your version includes what's in the Sean version? Yes, I just solved some bugs and from installing Seaside on my version right now, it works. I already proposed to Sean to check it again and upgrade package on his web page. Btw: two Timestamp methods are missing: Timestamp>>asSeconds ^self date asSeconds + self time asSeconds Timestamp class>>fromSeconds: aNumber | ts | ts := TimeStamp fromSeconds: aNumber . ^self new initializeWithDate: ts date time: ts time What are > the differences with the "Hyper swazoo" version from B. > Badger/OpenSkills? Ask Bruce Best regards Janko |
|
|
Sean and Esteban,
I just posted new Swazoo with Timestamp methods included and Seaside install and run nicely on it: ftp://ftp.eranova.si/aida/aida-5.0-dolphin-beta.zip Best regards Janko Janko Mivsek wrote: > Hi Esteban, > > Esteban A. Maringolo wrote: >> Hi, >> >> Excelent news! :-) >> >> What's the status of the Swazoo port? >> I mean, AFAIR there are two or three different versions around, being >> some of them branched. >> >> Sean: from what branch does your version descend? >> Janko: Does your version includes what's in the Sean version? > > Yes, I just solved some bugs and from installing Seaside on my version > right now, it works. I already proposed to Sean to check it again and > upgrade package on his web page. > > Btw: two Timestamp methods are missing: > > Timestamp>>asSeconds > ^self date asSeconds + self time asSeconds > > Timestamp class>>fromSeconds: aNumber > | ts | > ts := TimeStamp fromSeconds: aNumber . > ^self new initializeWithDate: ts date time: ts time > > > What are >> the differences with the "Hyper swazoo" version from B. >> Badger/OpenSkills? > > Ask Bruce > > Best regards > Janko |
|
|
In reply to this post by Esteban A. Maringolo
On Fri, 26 May 2006 07:00:01 -0700, Esteban A. Maringolo wrote:
> Sean: from what branch does your version descend? Janko: Does your > version includes what's in the Sean version? What are the differences > with the "Hyper swazoo" version from B. Badger/OpenSkills? Hyper is just giving a name to the HTTP server part of Swazoo that we have been using for the past few years. Our work was not folded back into the Swazoo 1.x stream, unfortunately, and some people were confused when we said we used the Swazoo HTTP server, and yet the "official" Swazoo version did not contain the library we used. Naming the HTTP server we use Hyper has cleared up this confusion. Hyper is implemented in terms of Sport and so can run anywhere Sport has been ported. I have not personally implemented Sport in Dolphin, but I understand some work has been done on this. I have run Hyper in VW, GemStone, VAST and Squeak. Hyper is available under the LGPL, which is the same license Swazoo uses. This means that Swazoo could adopt the Hyper HTTP server or just lift out individual bits and pieces. There you go :-) All the best, Bruce |
|
|
In reply to this post by Sean M-8
When I load these packages into a clean 6.0.2 image I get the following
errors: Error: WASession>>checkForCookies at line 1: undeclared 'Duration' Error: WADateTimeSelector>>dateAndTime at line 1: undeclared 'DateAndTime' Error: WAResponse>>deleteCookieAt: at line 1: undeclared 'Duration' Error: WACookie>>expireIn: at line 1: undeclared 'DateAndTime' Error: WABrowser class>>fullOnClass: at line 1: undeclared 'Browser' Error: WACookieTest>>go at line 1: undeclared 'Duration' Error: WABrowser>>initialize at line 1: undeclared 'Browser' Error: WAMiniCalendar>>months at line 1: undeclared 'Month' Error: WADateSelector>>privateIsValidDay:monthNumber:year: at line 1: undeclared 'Month' Error: WABrowser>>text at line 1: undeclared 'Text' Error: WAMiniCalendar>>year: at line 1: undeclared 'Month' What other packages should be loaded? James "Sean M" <[hidden email]> wrote in message news:R0xdg.2483$[hidden email]... > http://www.seaside.st/Download/Dolphin/ > > need to download my swazoo port as well > > http://www.arcturus.com.au/dolphin/ > > (I really should update that, sorry Janko!) > > > |
Re: Seaside for Dolphin alpha
|
|
James Foster escribió:
> When I load these packages into a clean 6.0.2 image I get the following > errors: > > Error: WASession>>checkForCookies at line 1: undeclared 'Duration' > Error: WADateTimeSelector>>dateAndTime at line 1: undeclared 'DateAndTime' > Error: WAResponse>>deleteCookieAt: at line 1: undeclared 'Duration' > Error: WACookie>>expireIn: at line 1: undeclared 'DateAndTime' > Error: WABrowser class>>fullOnClass: at line 1: undeclared 'Browser' > Error: WACookieTest>>go at line 1: undeclared 'Duration' > Error: WABrowser>>initialize at line 1: undeclared 'Browser' > Error: WAMiniCalendar>>months at line 1: undeclared 'Month' > Error: WADateSelector>>privateIsValidDay:monthNumber:year: at line 1: > undeclared 'Month' > Error: WABrowser>>text at line 1: undeclared 'Text' > Error: WAMiniCalendar>>year: at line 1: undeclared 'Month' > > > What other packages should be loaded? Duration can be obtained from Ian's goodies "IDB Duration", AFAIR. Month corresponds to the "Chronology" package in Squeak*. Browser isn't defined in Dolphin, and I don't know if it will be. The Duration, Month, and other classes from the Chronology framework were ported to VisualWorks using it Namespaces capabilities, it will be hard to port it to Dolphin, without generating many global collisions. Namespaces are good for this kind of stuff, they allow to get into the many "garbage"[2], but without disturbing the base system. How hard will be to add namespaces support to Dolphin? Perhaps in D7? [2] I.e. the VW port of Seaside includes a port of the Squeak chronology, so you end having two distinct TimeStamp classes, one from VW, and the other from Chronology. We will see if the Sport portability layer aids in the inter-dialect development, with time we will know. Regards, -- Esteban. |
|
|
Unfortunately, loading the IDB Duration package causes other errors
("WAStateHolder does not understand #snapshotCopy"). I'd like to hear from anyone who is using Seaside in Dolphin. Are you loading just the packages as distributed into a clean image and getting these errors? If so, do you anticipate that a later package will be able to load into a clean image without reporting errors? If not, how are you avoiding these errors? James "Esteban A. Maringolo" <[hidden email]> wrote in message news:[hidden email]... > James Foster escribió: >> When I load these packages into a clean 6.0.2 image I get the following >> errors: >> >> Error: WASession>>checkForCookies at line 1: undeclared 'Duration' >> Error: WADateTimeSelector>>dateAndTime at line 1: undeclared >> 'DateAndTime' >> Error: WAResponse>>deleteCookieAt: at line 1: undeclared 'Duration' >> Error: WACookie>>expireIn: at line 1: undeclared 'DateAndTime' >> Error: WABrowser class>>fullOnClass: at line 1: undeclared 'Browser' >> Error: WACookieTest>>go at line 1: undeclared 'Duration' >> Error: WABrowser>>initialize at line 1: undeclared 'Browser' >> Error: WAMiniCalendar>>months at line 1: undeclared 'Month' >> Error: WADateSelector>>privateIsValidDay:monthNumber:year: at line 1: >> undeclared 'Month' >> Error: WABrowser>>text at line 1: undeclared 'Text' >> Error: WAMiniCalendar>>year: at line 1: undeclared 'Month' >> >> >> What other packages should be loaded? > > Duration can be obtained from Ian's goodies "IDB Duration", AFAIR. > Month corresponds to the "Chronology" package in Squeak*. > > Browser isn't defined in Dolphin, and I don't know if it will be. > > The Duration, Month, and other classes from the Chronology framework > were ported to VisualWorks using it Namespaces capabilities, it will be > hard to port it to Dolphin, without generating many global collisions. > > Namespaces are good for this kind of stuff, they allow to get into the > many "garbage"[2], but without disturbing the base system. How hard will > be to add namespaces support to Dolphin? Perhaps in D7? > > [2] I.e. the VW port of Seaside includes a port of the Squeak > chronology, so you end having two distinct TimeStamp classes, one from > VW, and the other from Chronology. > > We will see if the Sport portability layer aids in the inter-dialect > development, with time we will know. > > Regards, > > -- > Esteban. > > |
Re: Seaside for Dolphin alpha
|
|
To the person making a port I would suggest making STS project for
Seaside and then exporting a complete zipped project edition for the Seaside project. A project groups all package versions together and also defines the load order of specific packages. That way everyone could have a working version of Seaside. A project export file is a file with .STP extension which contains zipped source code for all packages which belong to the specific version of a project. It is an ideal way to exchange Dolphin code for projects that involve more than just one package. Best regards, David Gorisek James Foster wrote: > Unfortunately, loading the IDB Duration package causes other errors > ("WAStateHolder does not understand #snapshotCopy"). I'd like to hear from > anyone who is using Seaside in Dolphin. Are you loading just the packages as > distributed into a clean image and getting these errors? If so, do you > anticipate that a later package will be able to load into a clean image > without reporting errors? If not, how are you avoiding these errors? > > James > > "Esteban A. Maringolo" <[hidden email]> wrote in message > news:[hidden email]... >> James Foster escribió: >>> When I load these packages into a clean 6.0.2 image I get the following >>> errors: >>> >>> Error: WASession>>checkForCookies at line 1: undeclared 'Duration' >>> Error: WADateTimeSelector>>dateAndTime at line 1: undeclared >>> 'DateAndTime' >>> Error: WAResponse>>deleteCookieAt: at line 1: undeclared 'Duration' >>> Error: WACookie>>expireIn: at line 1: undeclared 'DateAndTime' >>> Error: WABrowser class>>fullOnClass: at line 1: undeclared 'Browser' >>> Error: WACookieTest>>go at line 1: undeclared 'Duration' >>> Error: WABrowser>>initialize at line 1: undeclared 'Browser' >>> Error: WAMiniCalendar>>months at line 1: undeclared 'Month' >>> Error: WADateSelector>>privateIsValidDay:monthNumber:year: at line 1: >>> undeclared 'Month' >>> Error: WABrowser>>text at line 1: undeclared 'Text' >>> Error: WAMiniCalendar>>year: at line 1: undeclared 'Month' >>> >>> >>> What other packages should be loaded? >> Duration can be obtained from Ian's goodies "IDB Duration", AFAIR. >> Month corresponds to the "Chronology" package in Squeak*. >> >> Browser isn't defined in Dolphin, and I don't know if it will be. >> >> The Duration, Month, and other classes from the Chronology framework >> were ported to VisualWorks using it Namespaces capabilities, it will be >> hard to port it to Dolphin, without generating many global collisions. >> >> Namespaces are good for this kind of stuff, they allow to get into the >> many "garbage"[2], but without disturbing the base system. How hard will >> be to add namespaces support to Dolphin? Perhaps in D7? >> >> [2] I.e. the VW port of Seaside includes a port of the Squeak >> chronology, so you end having two distinct TimeStamp classes, one from >> VW, and the other from Chronology. >> >> We will see if the Sport portability layer aids in the inter-dialect >> development, with time we will know. >> >> Regards, >> >> -- >> Esteban. >> >> > > |
«
Return to Dolphin Smalltalk
|
1 view|%1 views
| Free forum by Nabble | Edit this page |