Public Forums 71,145 posts

[dpk Friend dpkJoin date: June 2006Posts: 129Downloads:0Uploads:0 Thanks: 19 Thanked: 2 times in 1 posts]

#158148

Is there a good reason for there to be CSS in the T3 plugin’s folder rather than keeping it all entirely within the blank template’s folder?

[aman204 Friend aman204Join date: January 2010Posts: 1945Downloads:0Uploads:43 Thanks: 11 Thanked: 418 times in 356 posts]

#369564

Probably, It is due to global adaptability for css attributes to T3 powered templates 🙂

As you will notice all the global css properties which apply to all such templates reside in css files of system plugin.Other than this, Css files for templates which provide in specific styling for them reside in template folder

Cheers

[dpk Friend dpkJoin date: June 2006Posts: 129Downloads:0Uploads:0 Thanks: 19 Thanked: 2 times in 1 posts]

#369606

<em>@aman204 212089 wrote:</em><blockquote>Probably, It is due to global adaptability for css attributes to T3 powered templates 🙂

As you will notice all the global css properties which apply to all such templates reside in css files of system plugin.Other than this, Css files for templates which provide in specific styling for them reside in template folder

Cheers</blockquote>

But why is it necessary to have global CSS properties? The plugin cannot be used without a template, so all the CSS acting on the template could be in the template’s folder. Changing CSS in the plugin’s folder means I can’t update the plugin without potentially breaking all templates.

[aman204 Friend aman204Join date: January 2010Posts: 1945Downloads:0Uploads:43 Thanks: 11 Thanked: 418 times in 356 posts]

#369633

<em>@dpk 212144 wrote:</em><blockquote>But why is it necessary to have global CSS properties? The plugin cannot be used without a template, so all the CSS acting on the template could be in the template’s folder. Changing CSS in the plugin’s folder means I can’t update the plugin without potentially breaking all templates.</blockquote>

My thoughts ::

It is mainly to keep css files organized or the template css files would remain clustured with lot of css attributes in them. You can always copy all the css attributes to css files for template 🙂

Also, It would be suggested to post it here in wishlist forum area ::

http://www.joomlart.com/forums/forum/request-and-wishlist/

[dpk Friend dpkJoin date: June 2006Posts: 129Downloads:0Uploads:0 Thanks: 19 Thanked: 2 times in 1 posts]

#369674

<em>@aman204 212186 wrote:</em><blockquote>My thoughts ::

It is mainly to keep css files organized or the template css files would remain clustured with lot of css attributes in them. You can always copy all the css attributes to css files for template :)</blockquote>

True, but it’s best to keep the number of stylesheets and overrides to a minimum.

<em>@aman204 212186 wrote:</em><blockquote>Also, It would be suggested to post it here in wishlist forum area ::

http://www.joomlart.com/forums/forum/request-and-wishlist/</blockquote>

Thank you for pointing that out.

[korb Friend korbJoin date: March 2008Posts: 315Downloads:0Uploads:0 Thanks: 40 Thanked: 48 times in 39 posts]

#369743

Hi,
Why styling within the plugin?
1. The styling within the core T3 Framework plugin provide a skeleton to easily start developing your template in no time. Our team made at least 70% of your work by developing this core styling so you only need to add your own styling with colors, background-images and so on.
2. The idea is to let you style your template, especially your own theme, outside the core styling, so you can easily update the template and avoid layout break after update process. Note that there are lots of users jumping from T3 1.1 to 1.4 and then complain of layout breaks. Wait a second! You have to update step-by-step, with each version compare and monitor code changes so you can do a perfect job.

Why so much styling?
Easy! Because it styles all Joomla! core content extensions, for both RTL and LTR, provide some special styling for IE6, some styling for Mobile Ready features and so on. The idea is to give you power of flexibility and modularity in code so you can disable some of the functions you don’t need.

What you can do?
After customizing your template and content, you can:
1. Delete redundancy code you don’t need (from your temlate)
2. Use CSS & JS optimization features and also template cache just the way you want.

Give a minute to read these instructions:
Cache settings: http://wiki.joomlart.com/wiki/JA_T3_Framework_2/Guides#System_Settings
Optimization settings: http://wiki.joomlart.com/wiki/JA_T3_Framework_2/Guides#Compression_Settings

Have more questions?
Feel free to post them here!

Regards,
Danny

[dpk Friend dpkJoin date: June 2006Posts: 129Downloads:0Uploads:0 Thanks: 19 Thanked: 2 times in 1 posts]

#369944

I don’t see why any of this requires stylesheets to be within the plugin’s folders.

Doesn’t it make more sense for all the themes, blocks, layouts, and styling that act on a template to be part of the base template’s folders?

If all stylesheets were kept within the templates (and none in the plugin), wouldn’t it be easier to update the plugin without breaking users’ own modified templates?

[korb Friend korbJoin date: March 2008Posts: 315Downloads:0Uploads:0 Thanks: 40 Thanked: 48 times in 39 posts]

#370127

Hi,
Trying to get deeper into this… You must understand that the core styling applies to all T3 Framework Templates. JA Designers and generally all other developers and designers don’t have to write this styling for every template over and over again. With a few back-end settings you can achieve whatever Grid system you want, on whatever template width you need. It is a waste of time! So I am telling you my friend, you and just very few are the only to not like this, as you always do it from ground zero to the top.

As for customization… It is almost impossible for an user to loose track of his customization as long as he is workin on his own theme and he updates his template and plugin on every release. JA Extensions Manager really does a great job with file compare feature. Such an efficient way to manage with almost no coding skills required.

I have heard nobody to not be able to update his template without template breaks. I mean there were a few that didn’t get it the first place, but with a little support they did it. Pretty fast I would say and they didn’t seem to be coders or power users, they seem to be regular users having basic understanding of Joomla!, JA Extensions Manager and some CSS skills. Of course there were others who expected everything to be automated 🙂

And when it comes to third party content components styling, users can learn how to use Template Overrides.

Regards,
Danny

[dpk Friend dpkJoin date: June 2006Posts: 129Downloads:0Uploads:0 Thanks: 19 Thanked: 2 times in 1 posts]

#370412

I understand the core styling applies to all templates. Putting it into a file in the template folder doesn’t make any work for anyone. It would keep all the styling in one place and allow modification of the core styling as opposed to overriding it.

Another way to go would be a child theme system. JA Extensions Manager is fine, but it is not a real solution for T3 plugin updates that break templates. The solution is to make it so updates don’t break anything. If Joomla/T3 templates used a child theme system like WordPress, the PHP+HTML and CSS files would all be in the child theme folder and override the “parent” theme so the parent can be updated without adverse effects.

[Author]

Posts