styles, scripts, and images sounds good to me. i've already started
roller-ui/scripts, and as i move css and img files i'll put those
under
styles and images.
in some cases i have decided not to lump all css, js, and imgs in the
standard directories. for example, the rte editor has a bunch of
resources that it uses and rather than mixing those in with a
bunch of
other stuff so that you can't tell what things are being used for,
instead i created a special directory for the various editor
resources.
so the rte editor stuff is all under roller-ui/authoring/editors/
rte/*
and if someone wants to add new editors they are encouraged to put
the
resources in a similar directory.
-- Allen
Matt Raible wrote:
> I would recommend using WEB-INF/jsp or WEB-INF/pages. As far as
the
> resource directories, I prefer to call them styles, scripts and
> images.
>
> Matt
>
> On 5/26/06, Allen Gilliland <[EMAIL PROTECTED]> wrote:
>> guys,
>>
>> i just wanted to give a heads up that i am shifting a bunch of our
>> /web/* resources around in preparation for the work i'm doing
on Roller
>> 3.0. i've already started this work and done just the easy
stuff that i
>> was pretty certain everyone would be agreed on ...
>>
>> 1. moved all the struts ui jsps to the web/WEB-INF/jsps/*
directory.
>> we've already talked about this and agreed on it a few months ago.
>>
>> 2. moved leftover jsps, css, images, etc, to directories under
>> web/roller-ui/*
>>
>> doing this reorg is very important to the requirements of the
new url
>> structure implementation because it helps us consolidate the
url space
>> in order to help prevent collisions between virtual weblog urls
and real
>> resources.
>>
>> the only decision of any real consequence that i have made so
far is to
>> choose "/roller-ui/*" as the single directory that we would use to
>> consolidate all of our web resources. the plan is to put all
resources
>> used by the authoring/admin ui (css, js, imgs, etc) under here.
>> "/roller-ui/*" is just the name i chose because it seemed to
make sense
>> and coincides with our java package naming as well.
>>
>> does anyone have any objections to this?
>>
>> -- Allen
>>