[eluser]jaswinder_rana[/eluser]
Thanks. And that library looks promising and easy to use.
My main problem here is CSS and JS. I understand that they shouldn't be in views folder. So, it means I need to go with similar structure for them. I was hoping to avoid that and check if there's another solution but seems not.
So far, after reading few threads, I have come up with following.
Code:
-system
--application
---views
-----VIEW_1
-----VIEW_2
----themes
-----theme_1
------header.php
------footer.php
-----theme_2
------header.php
------footer.php
-public_html
--assets
---modules (Using http://codeigniter.com/wiki/Asset_Helper/)
----theme_1
-----css
-----image
-----js
----theme_2
-----css
-----image
-----js
What I am trying to avoid is, having to copy views. In this case, my views will be same and only header and footer will change. So, it doesn't make sense to have views for all themes.
But, I think there might be another way that your library can be used.
- I can go with my method and then change themes
But I can combine it with your template and have different output formats like
Code:
-system
--application
---views
-----HTML
------VIEW_1
------VIEW_2
-----themes
------theme_1
-------header.php
-------footer.php
------theme_2
-------header.php
-------footer.php
------VIEW_1
------VIEW_2
----RSS
-----themes
------theme_1
-------header.php
-------footer.php
------theme_2
-------header.php
-------footer.php
I can't (yet) see cons to this method. As you can see, just throwing the idea around has helped me enhance my original structure a bit.
I just want someone to look at this and suggest if I am going the right way or not
Thanks
