CMS Made Simple Forums

1.  A replacement for the {stylesheet} tag instead of {stylesheet} the default templates will use the new {cms_stylesheet} tag which will
     a) process the stylesheets through smarty
     b) write the processed database stylesheets the tmp/cache directlry
     c) output tags to the cached files
     This will be a big improvement in performance to many sites as the browsers will easily be able to cache stylesheets, while

Je suis très heureux d'entendre cette nouvelle mais j'appuie la demande de dc2 :

I am very happy to hear this news but I support the request of dc2:

Little Question: Will the cached CSS-Files also be minified?

et j'ajoute cette question : Est il envisageable de concaténer les feuilles de style en une feuille de style unique (attention à la distinction des feuilles de style type "print"). En effet, moins de fichiers = moins de requêtes HTTP = plus rapide.

Je ne pense pas que l'ajout de cette fonctionnalité soit couteuse en temps de développement et sera un énorme avantage !

En tout cas merci aux développeurs pour leur travail

and I add this question: Is it possible to concatenate style sheets into a single style sheet (attention to the distinction of style sheets type "print"). Indeed, fewer files = less HTTP requests  = faster.

I do not think that adding this functionality is costly in development time and will be a huge advantage!

Anyway thank you developers for their work;)

(((sob)))

CMSMS isn't for beginners??   NOW you tell me!!  But I've grown to love CMS Made Simple!

I've been farting around with PC's and stuff since CP/M and dual 5 1/4 floppies.  Never had any formal training, just learn through doing.  AND I enjoy nutting out what you guys are doing...

CMSMS is made by professionals, for professionals.

Though anybody can use CMSMS we're not here to teach you how to build websites or about system administration and troubleshooting so use extreme caution and follow all of the forum rules, and do your research before you post oryour post may be ignored, deleted, or you may get a not so nice reply to your not-so-well thought out post.

Little Question: Will the cached CSS-Files also be minified?

Answer: No

Why:  Because on a properly configured server with mod_deflate enabled this is not necessary anyways, the files are gzipped before they're transmitted.  And as long as you're not changing your CSS that much the files will then remain cached on the clients PC.

I wonder if minified css and javascript files run faster in browsers due to less parsing.

Anybody know the answer?

personally, I've done a bit of research, and I think it's just another 'voodoo religion' thing
the goal is to minimize the amount of data transferred, thereby theoretically having a dramatic improvement in website performance.

This would only apply in sites that
a) had abnormally large stylesheets (I've seen some rediculous ones) but those were usually done b 
    people that had little clue about the idea of 'cascading' in cascading stylesheets, and did other similarly
    dumb things.
b) had old/improperly configured server that wouldn't gzip the data that was sent automatically (based on what the browser said it supported).

so, in my vote minifying the css is added complexity that's not really needed.

calguy1000 wrote: personally, I've done a bit of research, and I think it's just another 'voodoo religion' thing
the goal is to minimize the amount of data transferred, thereby theoretically having a dramatic improvement in website performance.

Thou I'd disagree on the 'voodoo religion' part when google, yahoo and ms all list it as a must in their best practices, luckily ScripDeploy does just that, and the new version is going to be super easy to use hopefully. 

But directly to the parsing, the gain is minimal in that area, but the gain is huge in how fast the site loads.. When someone says “My site is slow” ,  “CMSMS runs slow”  This is one of the best simplest  things one can do, so say all the research by those big guys have done, and is why minifaction and joining of scripts is a must for all sites.  This doesn’t give the license do just build massive scripts, or you crest the bell curve of the savings.

The way I look at it, if billion dollar companies say that is what they do to save money, increase user responsiveness etc.. well 'voodoo religion' or not I have built a super tight module just for script handling, editing and deploying the scripts and templates. Little sample http://www.screencast.com/t/Yzk1YjlkOGE

I don’t disagree that something that handles script the ‘right way’ would be bigger than most modules so to that I understand why it’ll be not in the core, thou I believe that it should be in the core of any workflow.  For now I’ll just keep tinkering on the module

gzip a stylesheet vs minified then gzip..  the differences in output size is minimal.  

modern browsers support gzip encoding of css, and so does cmsms. so why add the extra overhead and complexity of a minify routine (and the slight risk it will bork your layout) if it's not really gonna make a difference in the long run?


if you still want to also minify them, you can do that yourself..  minified stylesheets should still be tested prior to implementation, and it's something you should save for when the site design has been tested, is stable, and the site goes to production status... so it's not like you're gonna be doing it every day or something... unless you enjoy wasting time.

I don't think this is the place to talk about it.. but I have post here were Scriptdeploy related issue should go..
http://forum.cmsmadesimple.org/index.ph ... #msg214859

But I did address your concerns kermit  in that post.. Hope that helps.. Cheers -Jeremy

whha je pensais pas susciter autant d'émoi  et au delà du sujet de la minification, qu'en serait il de la concaténation des feuilles de style ?

Oui on peut le faire soit même, mais pouvoir gérer une feuille de style "Core", une "menu" et une "overlay" serait idéal pour laisser le code clair. 

@JeremyBASS : je n'ai pas encore pu tester ton module, il faut absolument que je le fasse !

whha I thought not generating as much excitement and beyond about the minification, what about the concatenation of style sheets?

Yes it can be done is the same, but allow manage a stylesheet "Core", a "menu" and an "overlay" would be ideal to let the code clear.

@JeremyBASS : I have not been able to test your module, it is imperative that I make it !

calguy1000 wrote: Yeah, CMSMS is not for beginners, and why start adding stuff that caters to the people that aren't the ones we want to focus on.

Well combined with e.g. the AdvancedContent Module, this would allow for an easy method to give the developer the ability to allow an editor to maintain a given colour scheme. Assume a corporate web page, where each branch has its own signal colour. Currently you have to copy your styles and templates to maintain different styles for each colour.
With the named combination, you just include a colour select into your template, which translates to different colours in your stylesheet. Your editor is happy, because the CMS is easy to use. You are happy, because you don't have to maintain all of your template copies, each time you have to do even minor updates to your styles.
Well, thats not beginners stuff, but still usefull.

Will 1.8 be released today?

It will be released in some days.... Not today

The last found issues in the beta-versions have to be fixed/tested, before it is released.

Ronny

Okay, thanks for the update 

Well I guess I spoke before I got updated as well...

The things that were reported and needed to be fixed, are fixed and confirmed working.

So expect the new release shortly

Ronny