Oh "PackRat", do you happen to have the version that has *contents*? :)
(Scary: you have a three year old file WITH NOTHING IN IT lying around, and
you can get at it easily :))
As for size, my current toy Server folder is about 18k uncompressed, so I
don't think it's that big a deal. The other possibility is to make a helper
class that can write out the Server files/structure and file *that* out.
That way, one isn't dependant on outside of Squeak tool. Heck, if one
wanted to be clever, one could put that class on an update server, and have
PWS>>initializeAll fetch the update first. That way, only folks who wanted
to use PWS would get the "bloat", but they'd have the ability to generate a
fresh Server file with easy.
Indeed, this is only a marginal simplificaiton for the sake of history.
Today, I think that the use of SSP for templates would be far superior (you
get versioning). Plus, for all but the most trivial apps, you'd want to
cache the formatter.
Which reminds me (while I'm at it): Do the GATech Squeaker want to host a
stop of the Squeak World tour?
http://wiki.cs.uiuc.edu/CampSmalltalk/Squeak+World+Tour
It might be especially neat to focus on a networking clean up. If Craig
Latta, John McIntosh, John Maloney, et al were to come (or some sutible
fraction of them) it could give the rather heterogenous and aging squeak
networking stuff a good push.
Cheers,
Bijan.
--On Monday, September 25, 2000, 11:23 AM -0400 Mark Guzdial
<[EMAIL PROTECTED]> wrote:
> Does "PackRat" Guzdial happen to have a nearly three year old file
> sitting around? OF COURSE, I DO! Attached.
>
> How big will it be gzipped? SC will be concerned about the image bloat
> cost...
>
> Mark
>
>> The "Comment" application seems not to be working. There definitely is a
>> missing template file "ShowAllComments.html". There's also a problem with
>> initializing the notes ivar in Discussion (it's lazily done in #at:put:,
>> but I suspect that's not sufficient).
>>
>> Mark, do you ahve a ShowAllComments.html lying about, or should we just
>> excise this example entirely? Removing the classes, eliminating the two
>> templates that *are* there, removing the comment link form pws.html, and
>> killing the setup in PWS>>initializeAll should do it.
>>
>> I also want to slurp the PWS setup files into the image, perhaps
>> gzipped. A class var in PWS should do the job. That way, folks don't have
>> to find the latest server.tar/.sea.
>>
>> Cheers,
>> Bijan.
>
