Just wondering if it there is an option to have linked LS files in a similar way to importing Linked CSS?
There isn't, but it doesn't sound like a bad idea for a feature request if you need to include mysource design areas within javascript files. Don't know how much use this would get though…
Short answer: no, but it could if someone were to request development for it.
[quote]There isn’t, but it doesn’t sound like a bad idea for a feature request if you need to include mysource design areas within javascript files. Don’t know how much use this would get though…
Short answer: no, but it could if someone were to request development for it.
[right][post=“9338”]<{POST_SNAPBACK}>[/post][/right][/quote]
Ahhh thats cool will have a think about it then and see if there is some other way of linking js files to a particular design customisation…
Just on another note, not sure if it is in 3.8 or not but would be nice with asset lists, to be able to select status of object similar to whats new etc? so that we know that only say Live assets are displayed or atleast if your logged in the item appears with {{Item}} etc as with the normal menus?
You can upload them as associated files to the customisation and refer to them as mysource_files ... of course, that all depends on what you need to do, and it sounds like you've got a good handle on what you can do with your current version.
[quote]Just on another note, not sure if it is in 3.8 or not but would be nice with asset lists, to be able to select status of object similar to whats new etc?[/quote]
Asset listings in 3.8 allow you to do this.
To include the Prototype and Lightbox javascript libraries in a page, the method I've used on the Matrix website is to dump them into a standard page and apply a design with a really basic content-type setting design:
Then you can include the JS anywhere you like as normal:
(where 1234 is the assetID of the standard page with JS in it (+ JS design applied)
Works like a charm. Is this what you're after?
Surely a text file asset is the solution here? It's editable in the backend and will always print itself on the frontend without a design. The only reason the CSS file asset exists is so that you can have a mysource_files alias like in the parse file of a design, and this is much less likely to be needed in a JS file.
[quote]Surely a text file asset is the solution here? It’s editable in the backend and will always print itself on the frontend without a design. The only reason the CSS file asset exists is so that you can have a mysource_files alias like in the parse file of a design, and this is much less likely to be needed in a JS file.
[right][post=“9357”]<{POST_SNAPBACK}>[/post][/right][/quote]
Yeah that sounds like more of the option to do that… Then couldn’t I then link to the text asset using a constant_button design area, and printing the url of the asset? as the script src?
And then if there was a constant being used i could also set
<MySource_SET name="assetid" value="777" />
as a default asset ID if there is a global JS being used?
That sounds right to me.