We spoke about this on another thread, but the issue was not resolved. where shall plugins keep any support files which are needed to be publically accessible (to be read by a browser)? I suggest that the distribution comes with a general farm/pub/ folder and an appropiate .htaccess file in it. This folder could have subfolders, ie. images/ for replacing the icons/ folder, and java/ or js/ for any generic javascript files a plugin may wish to use. Plugins could have custom subfolders if they have need for it. Skins can be left as current in individual subfolders in the dedicated skins/ folder.
What you think? And for clarification: What skin template variable are available for the various system paths? What is the preferred syntax? I like to make new plugins more standard conform, but I need a pub folder, sinc ei don't wan t plugins loading css styles or javascripts unnecessarily, which may be the case if i use pages in code pages. Thanks, ~Hans --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. 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/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
