<div dir="ltr"><div>> And a continuous integration server would really help catch these issues</div>
<div> </div>
<div>I currently run only a drop or 2 behind (except on your especially productive days) and ENVY (our library control system) is very picky about dependencies -- so I do find them about as soon as they appear (this is how Issue #133 got opened). I have worked around most of the dependencies by splitting up my platform-specific packages so that I have:</div>
<div> </div>
<div>* a VA Smalltalk 'Preload' package, loaded before Seaside-Core, that provides all the Squeak porting extensions as well as a sufficient subset of SeasidePlatformSupport to satisfy Seaside-Core's initialization requests</div>
<div>* a VA Smalltalk 'Continuations' package, loaded before Seaside-Core, substantially the same as the Squeak 'Continuations' package</div>
<div>* a VA Smalltalk 'Core' package, loaded after Seaside-Core, containing the platform codecs and most of the rest of SeasidePlatformSupport</div>
<div>* a VA Smalltalk 'DevelopmentPreload' package, loaded before Seaside-Development-Core, that contains the development-specific bit of SeasidePlatformSupport and other odds and ends needed to support the various development tools</div>
<div> </div>
<div>This organization seems to work for me -- although I need to tune it occasionally as stuff gets refactored in the various Seaside packages. However, I think I would prefer lazy-initialization to my current approach since it would relieve me of the (also error-prone) refactoring of my several 'preload' packages.</div>
<div><br clear="all">John O'Keefe [|], Principal Smalltalk Architect, Instantiations Inc.<br><br><br></div>
<div class="gmail_quote">On Fri, Sep 5, 2008 at 3:44 PM, Philippe Marschall <span dir="ltr"><<a href="mailto:philippe.marschall@gmail.com" target="_blank">philippe.marschall@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi Gerhard<br><br>Thanks for testing, I had a look unfortunately there are indeed<br>several severe problems left. If we had looked more exactly at the<br>
dependency diagram then we would have found that out. What we did:<br>- Seaside-Core expects a WAContinuation class, because of this we made<br>a Seaside-Squeak-Continuation package and moved it there<br>- Seaside-Core expects also a WAProcess variable class, so I moved it<br>
there as well<br><br>What we overlooked:<br>- Several classes in Seaside-Core expect a working<br>SeasidePlatformSupport and send messages to it during class<br>initialization, examples include, WAExternalID, WAFileLibrary,<br>
WAHtmlEncoder, WAUrlEncoder<br>- WASqueakPlatfrom depends on other classes like WAGenericSqueakCodec<br>and WAUtf8SqueakCodec<br>- WAUtf8SqueakCodec and WAGenericSqueakCodec depend on WACodec<br><br>I see two options, both of them are ugly:<br>
1. Merge Seaside-Squeak-Core and Seaside-Squeak-Continuation and load<br>it before Seaside-Core. WAUtf8SqueakCodec and WAGenericSqueakCodec<br>would have to become subclasses of Object which is ugly because they<br>implement the WACodec "interface".<br>
2. Lazily initialize the WAExternalID, WAFileLibrary, WAHtmlEncoder,<br>WAUrlEncoder classes from Seaside-Squeak-Core which is ugly because it<br>is error prone and we have an undeclared in Seaside-Core for a short<br>time.<br>
<br>Preferences? Other options?<br><br>And a continuous integration server would really help catch these issues<br><br>Cheers<br>Philippe<br><br>2008/9/5 Gerhard Obermann <<a href="mailto:obi068@gmail.com" target="_blank">obi068@gmail.com</a>>:<br>
<div>
<div></div>
<div>> Hi!<br>><br>> I have tried to load Seaside 2.9 starting with an empty Pahro developer<br>> image.<br>> I followed the loading steps from <a href="http://squeaksource.com/" target="_blank">squeaksource.com</a> but<br>
> its currently not possible to load Seaside-Core because<br>> it has references to SeasidePlatformSupport which will be initialized<br>> with the next package Seaside-Squeak-Core.<br>> Of course its also not possible to load Seaside-Squeak-Core before.<br>
><br>> br<br>> Gerhard<br>><br>><br></div></div>> _______________________________________________<br>> seaside-dev mailing list<br>> <a href="mailto:seaside-dev@lists.squeakfoundation.org" target="_blank">seaside-dev@lists.squeakfoundation.org</a><br>
> <a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>><br>><br>_______________________________________________<br>
seaside-dev mailing list<br><a href="mailto:seaside-dev@lists.squeakfoundation.org" target="_blank">seaside-dev@lists.squeakfoundation.org</a><br><a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
</blockquote></div><br></div>