[Seaside] VW Seaside problems continue
Pennell, David
DPennell at quallaby.com
Thu Sep 11 18:26:54 CEST 2003
> I enter the username and password I just created in the web
> browser and
> an exception is raised. The method
> Seaside.WADispachcher>>decodeAuthorization: uses (see below)
> the class
> Base64MimeConverter, which is not in my image. So an exception is
> raised when Seaside tries to decode the username and password it was
> sent. Does anyone know where to find this class?
>
> Seaside.WADispachcher>>decodeAuthorization: aString
> ^(Base64MimeConverter mimeDecodeToChars:
> (ReadStream on: (aString findTokens: ' ') last))
> contents
Mea culpa. That one is still on the to-do list. I haven't used the
configuration application or authentication so it hasn't bothered me.
As to Base64MimeConverter, I need to do a little research on it before
deciding what to do.
> sortBy: is a Squeak method on arrays, which does not exist in VW. Of
> course this is fixed with:
>
> Array>>sortBy: aBlock
> ^self asSortedCollection: aBlock
>
> But now the two problems begin to make me think that there
> may be some
> VW-Squeak compatibility package that I am missing. Is this the case?
No. #sortBy: is only used by WAApplicationList, and one other place.
I just haven't run across it yet. This is a judgement call, but in other
situations like this, Avi simply modified Seaside to be more platform
neutral.
Early versions of the 2.3 port had a lot more Squeak dependencies than does
the current version.
>
> Which reminds me, shouldn't the package Seaside-WebToolKit be
> listed as
> a prereq for the package Seaside? Seaside-WebToolKit contains the
> Seaside namespace, so one can not load Seaside first.
Several people expressed a desire for the VW port to not be locked into
WebToolKit. If I made Seaside-WebToolKit a prereq for Seaside, then when
somebody else adds Seaside-Swazoo, you would be stuck. OK, I just realized
that I could just make Seaside be a sub-bundle of Seaside-WebToolKit and
you would have your one click load. BTW - Cincom (Alan Knight) was
soliciting
input on StORE improvements at Smalltalk Solutions. I believe that better
tools for browsing the repository were on the list.
> I realize that I could make this change on the cincom repository, but
> am still new enough at Seaside that I am not sure what I am doing.
I'm pretty new at using the public repository, new with Seaside and new
with a major platform port. Avi and I are in discussion about ways to
simplify the porting process so that future versions can be re-ported
as simply as possible. I think the ball is currently in my court...
In the meantime, please keep the messages coming.
More information about the Seaside
mailing list