Re: [binarycloud-dev] binarycloud/base/mod

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

> Hi,
> 
> Jepp, sounds good. But only for "required-by-core-modules". Other more
> independent but still default suff should go to user/default/mod, I think.

Agreed.

These are modules which should _always_ be static, and required by the
system. I'm thinking things like the module for CSS and JS requests (maybe
images, also...).. etc.

Actually...

Is anyone interested in an ImageRequestManager which would use a static
embed tag like the module embeds:

<bc:image id="SomeImageID" />

the reason I thought of doing this:
    -if people use this 'embed' tag, the make system can use a central image
info repository to build well-formed tags that include alts, the _real_
width and height of an image, etc. Of course we could allow overrides:

<bc:image id="SomeImageID" alt="Some Other Alt You want" width="20" />

but in general you'd just use the simple tag.

I can imagine that being convenient for me... would it be convenient for
anyone else?

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

best,

_alex




> Andi
> 
> 
> 
>> makes sense to me... seems like the best place to put "factory"
>> modules.
> 
> alex black wrote:
>> what does everyone think about having binarycloud/base/mod/ in the source
>> tree?
>> I'm thinking that we're going to have a set of modules that will be
> required
>> by certain builders and managers ( the JSRequest and CSSRequest Managers
>> come to mind)
>> 
>> thoughts?
> 
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> https://lists.sourceforge.net/lists/listinfo/binarycloud-dev
> 
> 
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> https://lists.sourceforge.net/lists/listinfo/binarycloud-dev
>