|
From: Andreas A. (Thyrell) <a.a...@th...> - 2001-09-10 19:24:26
|
Hi Alex,
> Is anyone interested in an ImageRequestManager which would use a
> static embed tag like the module embeds:
> <bc:image id="SomeImageID" />
that's groovy.
> I can imagine that being convenient for me...
> would it be convenient for anyone else?
Ohhh most defenetly yes.
> The xml would probably look like:
<!-- binarycloud image repository example file -->
<!--
used in conjunction with:
<bc:image id="SomeImageID" />
-->
<images>
<image>
<!--
This ID is used by the make system. Required.
-->
<id>bcFire</id>
<!--
The image source. We could set a constant called
BC_PATH_IMAGES or something that would allow make
to know that it should prepend that value to all
image paths
-->
<src>resources/images/binarycloud/tmpl/fire.jpg</src>
<!--
The value of the 'name' attribute in the img tag
-->
<name>ImageName</name>
<!--
The alt attribute. Note the language reference
-->
<alt:en>binarycloud fire</alt:en>
<!--
The 'align' attribute in the img tag
-->
<align>left</align>
<hspace>10</hspace>
<vspace>10</vspace>
<!--
If left undefined, this is assumed to be 0
-->
<border>0</border>
<usemap>#moo</usemap>
<!--
only specify these if you want to override the make system's
automatic image-checking features
-->
<width>400</width>
<height>20</height>
</image>
</images>
> Of course the other possibility is to turn this into an Entity, and > run
image makes from the database... hehehe
Groovy again. That would be cool. It would also be cool to have a central
resource entity/table that holds text, imagedata, imageurls, urls etc. So we
can dynamically pull out images from database on runtime (i.e. a images
linked to a specific news article).
Nevertheless we should consider well and take care not exaggerating with
this abstraction stuff.
Andi
|