Re: [binarycloud-dev] Handling of resources/ in htdocs

[Alex B. <en...@tu...>]

> 
> To clear any cloudy air, so accessing ANYTHING in resources/ will be a
> combination of a constant and an absolute path, correct?
> 
> TMPL EG:
> <script src="<?=RESOURCE_CONSTANT?>/what/ever/script.js">
> 
> <img src="<?=RESOURCE_CONSTANT?>/a/b/c/image.jpg">
> 
> <a href="<?=RESOURCE_CONSTANT?>/archive/mp3/any_document.mp3">click to
> download this MP3</a>
> 
> 
> Or is this to simplified?

More like:

<bc:img id="abcimg" />
<bc:js id="moo" inline="true" />
<bc:css id="moo" inline="false" />
<bc:href id="href" href="/archive/mp3/any_document.mp3" usedocroot="true" |
usersrcroot="true" /> (or something)

which will be 'made' into:

<img src="/value/of/rsrc/constant/a/b/c/image.jpg" border="0" width="12"
height="123">

<script language="JavaScript">
function Moo() {
    return;
}
</script>


<link rel="stylesheet" href="/value/of/rsrc/constant/css/moo.css" />

<a href="/value/of/rsrc/constant/archive/mp3/any_document.mp3">Click to
Download MP3</a>

I very much want to avoid the use of "constant echos" that are unnecessary
at runtime: if you already have implicit knowledge about your environment,
there's no reason to repeat the same logic over and over.

What are people's opinions on these 'tags' ?

best,

_alex



> jason
> 
> Alex Black wrote:
>>> I too have wondered this.  I'd vote highly against the use of any
>>> absolute paths unless they are preceed by a definable constant.
>> 
>> Which is exactly what ImageRequestManager will do.
> 
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> https://lists.sourceforge.net/lists/listinfo/binarycloud-dev
>