pier and seaside 3.0
jfitzell at gmail.com
Tue Jan 5 19:38:19 MET 2010
On Tue, Jan 5, 2010 at 5:59 AM, Lukas Renggli <renggli at gmail.com> wrote:
>> BTW the load errors:
>> "FileList2 is Undeclared", in MAFileMorph - doesn't seem too concerning as
>> I'm only interested in the seaside bindings.
> Yep, the Magritte-Morph is not really required.
>> I ignored the error: "Pier-Core depends on PRPackage class>>pierTestsModel"
>> PRCommandTest>>testDate(WAPlatform is undefined)
>> PRCommandTest>>testTimestamp (WAPlatform is Undeclared)
>> PRPersistencyTest>>testMutexForked(WAPlatform is undefined)
>> PRSegmentPersistency>>cleanupSeaside (WAEntryPoint is Undeclared)
>> Should I be concerned by any of these load errors?
> That looks like there is version mismatch between Magritte/Pier and Seaside.
> The port of of Magritte/Pier was done for VA Smalltalk by Julian, and
> it looks like the code hasn't been adapted to very latest version of
> Seaside. Also the code is quite behind the Magritte/Pier code for
> Seaside 2.8. Shame on me that I still didn't had time to look into
Mmm... yes, I'm having trouble recalling now. Did I do the initial
port against Seaside 3.0a4? It's been a couple of months since I
branched, so the Magritte/Pier code would definitely be a bit behind
the 2.8 codebase and I wouldn't be surprised to know it needs minor
updates for the latest Seaside one way or another.
I'm also, unfortunately, not actually *using* the port. As Lukas said,
I did the port as part of work to then port it to VA smalltalk.
Nationaal Spaarfonds would be using it with the version of Seaside
distributed by Instantiations (though that should now be a5, so they
may need updates as well) but even they aren't yet actively using it I
Someone, either a Pier developer or a user, needs to start actually
*using* the code with the latest Seaside release (I would suggest
maybe not the bleeding edge code, though, or nobody will be able to
follow) so they can stay on top of fixes and merging in code from the
other branch. Otherwise the code will rot, which would be kind of a
shame. The changes weren't even that major, but they did require
repackaging which makes maintaining the two branches more complicated
- I had hoped primary development could move to the new repositories
before they diverged too much.
More information about the smallwiki