Fwd: Writing Code in Stories or Media Elements ?

>
> Hi all -
>
> I'm revisiting the question of whether I should create
story  
> elements for my css, javascript and php include files,
or  should I  
> use a media elements as David suggests below.
>
> On 9-Apr-07, at 1:06 PM, David E. Wheeler wrote:
>
>> On Apr 9, 2007, at 06:57, Phillip Smith wrote:
>>
>>
>>> I've been wondering about this for a while now
-- so I'm glad to  
>>> see some examples of people using stories for
front-end includes  
>>> and the like. I've used media documents to
date, but media  
>>> documents lack a lot of the things that made me
think about using  
>>> stories in the first place, e.g., direct
editing in the UI,  
>>> visual diffs, etc. Certainly, for our CSS
files, it is a bit  
>>> cumbersome to have to download the latest file,
edit / test, then  
>>> upload and publish it; given that it's just
text it would be  
>>> great to just edit it directly and re-publish.
>>>
>>
>> These features could easily be added for media
documents with a  
>> content type of "text/*".
>>
>
> (The whole thread can be followed here: http://marc.info/? 
> l=bricolage-general&m=117613810919021&w=2)
>
>
> I know I can add a 'Source Code' text field to an
element of type  
> 'Other Media' - which is how I would define a css style
sheet.   
> However it seems a media element also expects a media
file (i.e  
> screen.css) to be uploaded in order to do anything with
that file,  
> and will not publish the media element to my site if a
file is not  
> associated. Also it seems the extra css code I would
have added via  
> the 'Source Code' field are of no use unless I call
them somehow  
> from a story template.
>
> So David - what do you mean by:
>
>
>> These features could easily be added for media
documents with a  
>> content type of "text/*".
>>
>
> So far I see no good reason to use media files for
css,js ect  
> documents that I want to edit on a regular basis.
However if I am  
> missing some benefit please let me know.
>
> thank you,
> Dawn

On Sep 20, 2007, at 20:45, Dawn Buie wrote:

>> So David - what do you mean by:
>>
>>> These features could easily be added for media
documents with a  
>>> content type of "text/*".

I mean that someone could pretty easily add a feature to
Bricolage  
where, if the uploaded media file is of type text/something,
 
Bricolage could provide a text field to edit it right in the
UI. Of  
course, this depends on a file being uploaded when a
document is  
first created -- or else someone implementing another new
feature: a  
constraint on media element types that limits the uploaded
documents  
to particular mime types, in which case, if it happens to
start with  
"text/", we could just provide the field without
requiring that a  
file be uploaded.

>> So far I see no good reason to use media files for
css,js ect  
>> documents that I want to edit on a regular basis.
However if I am  
>> missing some benefit please let me know.

If you prefer editing documents from within Bricolage, there
is no  
benefit. Personally, I'd rather use the virtual FTP server
and edit  
media documents on a locally mounted FTP volume. But that's
just me. 

Best,

David