Hi Saulius,
that's the way I did it. All module files should be encapsulated in the
module folder, like you suggested. But additionally it has to respect
the active theme in order to be able to style frontend components
according to the theme.
Meanwhile I found a working solution. As you can see here
https://github.com/DSB/Oxid-oTranCe-Connector/blob/master/modules/otrance-connector/core/otc_otcViewConfig_oxViewConfig.php
I created some getters for my module.
But regarding the fact that each module needs to be able to fetch its
own css/js/image files, my solution feels dirty. When I think of a shop
with 20 modules and each implements an own way to get files from within
its own folder .. no, I don't want to think of that. ;)
Are there any ready-to-use getters I haven't found? If not, I'd suggest
to add something like that to the OXID core.
Best regards,
Daniel Schlichtholz
Am 26.03.2013 10:16, schrieb Saulius Stasiukaitis:
Hi,
There is no strong requirement where to store JS and CSS files. My suggestion
would be to keep them inside your module directory. Create out/src/js/ and
out/src/css/ directories so it fit Shop structure and would be easier to debug
for other people. You can use something like this to include your scripts in to
templates:
[{oxscript include=$oViewConf->getModuleUrl("{moduleID}",
"out/src/js/{js_fle_name}.js")}]
Saulius Stasiukaitis
OXID Developer
-----Original Message-----
From: dev-general-boun...@lists.oxidforge.org
[mailto:dev-general-boun...@lists.oxidforge.org] On Behalf Of Daniel
Schlichtholz
Sent: Wednesday, March 20, 2013 3:41 PM
To: Oxid Dev-List
Subject: [oxid-dev-general] Images, Javascript and CSS files in modules
Hi list,
I want to create a module in Oxid 4.7.x that needs to add its own CSS-,
Javascript- and Image-Files.
What is the best practise to do that?
_______________________________________________
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general
