I have something preliminary committed to SVN.  In your case Adrian, 
your external JS file doesn't have file extension so you have to specify 
it differently - like so:

<key name="carousel">
    <array>
        <element value="prototype.js,effects.js,carousel.js" />
        <element>
            <struct>
                <key name="paths" 
value="http://maps.google.com/maps/api/js?sensor=false"; />
                <key name="type" value="js"/>
            </struct>
        </element>
    </array>
</key>

It's impossible for us to auto-detect the type of asset without the file 
extension (makes sense).  Let me know if what I already committed works 
for you.

Best,
.Peter

P.s. It looking like I need to improve the auto-detection routine (it 
allows you to mix .js / .css file types)Depending on your combination of 
files in a single "," comma list  -- it can make css files in <script> 
tags, etc.  It's a separate issue here which I'll file in the tracker in 
a bit.

Adrian Scott said the following on 09/10/2009 02:51 PM:
> Hi Peter, yes I think it'd be a fair assumption to consider http://
> and https:// as the only external references for now (I can't think of
> a time that I've used anything other than those protocols).  Thanks
> for the FYI, I'll make sure I code things using that methodology from
> now on.
>
> I've created a ticket: 
> http://greatbiztoolsllc.trac.cvsdude.com/mach-ii/ticket/380
>
> Adrian.
>
> On Sep 10, 12:26 pm, "Peter J. Farrell" <[email protected]> wrote:
>   
>> Would it be safe to assume that the external JS / CSS files will always
>> begin with either "http://"; or "https://";?  I'm asking because we have
>> to distinguish from local files versus external files because cannot
>> compute an asset timestamp for external files.  I am assuming that those
>> are the only two protocols we need to support for external files (http
>> and https).
>>
>> FYI, you can change:
>>
>> <key name="map">
>>   <array>
>>     <element value="http://maps.google.com/maps/api/js?sensor=false,map.js"; 
>> />
>>     <element value="map.css" />
>>   </array>
>> </key>
>>
>> To this if you want:
>>
>> <key name="map" 
>> value="http://maps.google.com/maps/api/js?sensor=false,map.js,map.css"; />
>>
>> Best,
>> .Peter
>>
>> Peter J. Farrell said the following on 09/10/2009 01:59 PM:
>>
>>     
>>> Adrian,
>>>       
>>> Please file a ticket for this.  Seems to be a rather reasonable and
>>> logical extension of what the HTMLHelperProperty offers.  I'll see what
>>> I can do.
>>>       
>>> http://trac.mach-ii.com
>>>       
>>> FYI, we are to upgrade the <script> and <style> tags in the view custom
>>> library so you can access the HTMLHelperProperty in a nice tag based
>>> format as well.  We current have <img> and <meta> tags implemented.  The
>>> <script> and <style> tags still need to be hooked up.
>>>       
>>> Best,
>>> .Peter
>>>       
>>> Adrian Scott said the following on 09/10/2009 01:21 PM:
>>>       
>>>> Hi all,
>>>>         
>>>> I really love using the HTMLHelperProperty library, though there's
>>>> been one thing that I've really been desiring and either haven't
>>>> gotten it to work correctly or it's not a part of the tool (yet).
>>>>         
>>>> Essentially what I want to do is use asset packages for not only my
>>>> local .js files, but also externally hosted JavaScript (e.g. Google
>>>> APIs).
>>>>         
>>>> I've attempted to create an asset package thusly:
>>>>         
>>>> <key name="map">
>>>>   <array>
>>>>     <element value="http://maps.google.com/maps/api/js?
>>>> sensor=false,map.js" />
>>>>     <element value="map.css" />
>>>>   </array>
>>>> </key>
>>>>         
>>>> Of course what is appended to the <head /> tag is:
>>>>         
>>>> <script type="text/javascript" src="scripts/http://maps.google.com/
>>>> maps/api/js?sensor=false.js"></script>
>>>> <script type="text/javascript" src="scripts/map.js"></script>
>>>> <link type="text/css" href="styles/map.css" rel="stylesheet" />
>>>>         
>>>> I'm assuming this is likely desired behavior at the moment, but is
>>>> there any plans of being able to do this in the future?
>>>>         
>>>> Thanks,
>>>>         
>>>> Adrian.
>>>>         
> >
>   


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to Mach-II for CFML list.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/mach-ii-for-coldfusion?hl=en
SVN: http://greatbiztoolsllc.svn.cvsdude.com/mach-ii/
Wiki / Documentation / Tickets: 
http://greatbiztoolsllc.trac.cvsdude.com/mach-ii/
-~----------~----~----~----~------~----~------~--~---

Reply via email to