<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>Re: [Seaside] Re: Confused over the use of WAExternalFileLibrary...</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>That's actually something Cincom added I believe.<BR>
<BR>
Cheers!<BR>
<BR>
-Boris (via BlackBerry)<BR>
<BR>
----- Original Message -----<BR>
From: Rick Flower <rickf@ca-flower.com><BR>
To: Boris Popov<BR>
Cc: seaside@lists.squeakfoundation.org <seaside@lists.squeakfoundation.org><BR>
Sent: Mon Jun 16 18:08:38 2008<BR>
Subject: Re: [Seaside] Re: Confused over the use of WAExternalFileLibrary...<BR>
<BR>
Thanks Boris.. I guess I have to get my feet wet with modifying<BR>
something within Seaside at some point eh!? This class looks<BR>
nice-n-small so it's a good candidate.. Of course I'll let you-all that<BR>
know more about ST than I do, review it..<BR>
<BR>
-- Rick<BR>
<BR>
On Mon, June 16, 2008 5:59 pm, Boris Popov wrote:<BR>
> Sure, submit it as a patch for Cincom to review. I imagine<BR>
subdirectories<BR>
> should be part of basic functionality for file serving.<BR>
><BR>
> Cheers!<BR>
><BR>
> -Boris (via BlackBerry)<BR>
><BR>
> ----- Original Message -----<BR>
> From: seaside-bounces@lists.squeakfoundation.org<BR>
> <seaside-bounces@lists.squeakfoundation.org><BR>
> To: Seaside - general discussion <seaside@lists.squeakfoundation.org><BR>
Sent: Mon Jun 16 17:58:04 2008<BR>
> Subject: Re: [Seaside] Re: Confused over the use of<BR>
> WAExternalFileLibrary...<BR>
><BR>
> Ok.. In thinking about the big picture here and trying to<BR>
> help perspective future users of this class.. I'm wondering IF<BR>
> I were to alter the existing WAExternalFileLibrary to be more<BR>
> flexible (add support for subdirectories + more obvious config<BR>
> features), would that annoy other users of this class? I'm not<BR>
> sure how many people are actually using it for anything --<BR>
> comments? At a minimum I'll certainly document the current<BR>
> behavior including where the 'files' directory lives within the<BR>
> VW tree which was half the problem for me to guess.<BR>
><BR>
> -- Rick<BR>
><BR>
> On Sun, June 15, 2008 8:07 pm, Richard E. Flower wrote:<BR>
>> This is really odd to me.. I finally got it working. In my case, I<BR>
used the name "include" in the dispatch editor for Seaside (where the<BR>
configuration of the WAExternalFileLibrary lives) and my links needed<BR>
to be named "include/external/foo.jpg" but the files live in<BR>
>> the VW image directory as "vw7.6/image/files/foo.jpg".. It also does<BR>
not appear to handle subdirectories from what I've seen.. I guess I'll<BR>
have to spend some time looking into Apache again since this isn't<BR>
doing what I was hoping.. Oh well..<BR>
>> -- Rick<BR>
>> On Jun 13, 2008, at 2:21 PM, Magnus Schwarz wrote:<BR>
>>> Hi Rick,<BR>
>>> although the files reside in the /files directory (i.e. /files/<BR>
myFile.jpg), the proper URL in Seaside is files/external/myFile.jpg.<BR>
(This may IMHO be a bit confusing...)<BR>
>>> Regards,<BR>
>>> Magnus<BR>
>>> seaside-request@lists.squeakfoundation.org schrieb:<BR>
>>>> 1. Confused over the use of WAExternalFileLibrary...<BR>
>>>> (Richard E. Flower)<BR>
>>>> ----------------------------------------------------------------------<BR>
Message: 1<BR>
>>>> Date: Thu, 12 Jun 2008 23:02:12 -0700<BR>
>>>> From: "Richard E. Flower" <rickf@ca-flower.com><BR>
>>>> Subject: [Seaside] Confused over the use of WAExternalFileLibrary...<BR>
To: Seaside - general discussion <seaside@lists.squeakfoundation.org><BR>
Message-ID: <416C80A3-37ED-4704-B5D6-815F2DC1EE1E@ca-flower.com><BR>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes<BR>
Ok.. I've gotten past my initial hurdles with Boris' help but none of<BR>
my css files or images are getting pulled in due<BR>
>>>> to the deprecated API that I was using w/ Seaside 2.6 (besides the<BR>
move from Webtoolkit to Opentalk)..<BR>
>>>> Anyway, in perusing the old mail messages from the list, it<BR>
>>>> appears that WAExternalFileLibrary may be the solution<BR>
>>>> I'm looking for but I'm stuck with trying to get it to work. I've<BR>
created a "Files" entry point as indicated and named it "include".<BR>
Now, I've changed one of my image references to point to /seaside/<BR>
files/image.jpg but its never found.. The docs are very terse on the<BR>
usage.. Am I missing something? Where does the directory lie in the<BR>
filesystem for VW? I've tried the top-level VW directory along with<BR>
the 'image' subdirectory... Also, if I want to have one directory<BR>
w/ css and another with images how is that done? Thanks!<BR>
>>>> -- Rick<BR>
>>> --<BR>
>>> Magnus Schwarz * certified Scrum Master / Smalltalk architect *<BR>
<A HREF="mailto:magnus.schwarz@heeg.de">mailto:magnus.schwarz@heeg.de</A><BR>
>>> phone:+49 231 97599-0 * fax:+49 231 97599-20<BR>
>>> Georg Heeg eK Dortmund<BR>
>>> Handelsregister: Amtsgericht Dortmund A 12812<BR>
>>> ---------------------------------------------------<BR>
>>> PGP PUBLIC KEY BLOCK via <A HREF="http://www.heeg.de/~magnus">http://www.heeg.de/~magnus</A><BR>
>>> _______________________________________________<BR>
>>> seaside mailing list<BR>
>>> seaside@lists.squeakfoundation.org<BR>
>>> <A HREF="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</A><BR>
>> _______________________________________________<BR>
>> seaside mailing list<BR>
>> seaside@lists.squeakfoundation.org<BR>
>> <A HREF="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</A><BR>
><BR>
><BR>
> _______________________________________________<BR>
> seaside mailing list<BR>
> seaside@lists.squeakfoundation.org<BR>
> <A HREF="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</A><BR>
><BR>
<BR>
<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>