I wish your daughter is better just now.
Very exciting to see this advance.
I hope your daughter is better now. This time of year is risky for getting sick.
Thank you again, I
can not will wait
I have some more updated coming for Boiler. This next version will be release as a 1.0, so hold tight on using it in production until then.
I am running a little behind because my daughter was very ill last week, so when I get caught up I will try and get these changes merged and and push them out to you guys.
I guess that really depends on the site in question, if you have a large left column - then I could see this being a concern.
While I wrote boiler to not require changing the html markup - for some sites that may be a necessity.
If I had a left column that wasn't always necessary - I would probably do what I did to the menu and make it collapsed by default.
What I may do is allow you to set the order of blocks, and then they will by default collapses ltr
[L] [C] [R]
[C] [L] [R]
[L] [R] [C]
I have one suggestion for the "flow" skin. The flow is a semantic and responsive skin. The issue is the left block. The left block should be going down, so that the (middle) content is present on top always. Otherwise the user has to scroll a lot.
What do you think about it?
I read it on twitter as well. This is turning out to be a huge modernisation of the themeing capabilities of ImpressCMS. Thanks for the initiative, and I'm following this with much interest.
Yeah, I heard about it over Twitter from him. I can not wait ...
I am glad everyone enjoys it so far. I have some more changes coming down the pipe that adress some little bugs I have uncovered - as well as some excellent work done by Matt(sublime) integrating less into boiler.
I'm very impressed. A very great work! Right now, I could not find any issues.
You really did a great job on this theme. Thanks for this. I'm glad to see you more active again..
I would think we would cache results based on the template creation timestamp. There is no reason to build on every page if we don't have to. The purpose of the concatenator I wrote up is to put the weight of fetching the files on the server and not on the client.
If we cached it with a random filename - or even a logical filename based on its build time and what zone it is in, then we just cachebust it with the last cache clear timestamp value. If i recall correctly don't we store that info somewhere already?
hmm, what else...
I have begun playing with a concatenator - this php file (boiler.php) is in the extras folder - place it in your icms root path and enable the option in theme_settings or skin_settings. Used little at this time, but it will get better over time. You could find this very useful if for example you used the extra meta file to include your own scripts. concatenate them to reduce http requests people.
One consideration I am thinking about is putting all the media queries into a single css file instead of making so many requests - this might be a little more user friendly - far less files to deal with...
I'll have to check this out asap! I'm quite impressed by this list of added features.
Thank you again, let me testing from Monday. It's is a very great html5 framework, I like it really.
A lot more work has gone into this version - I will highlight the major stuff here, and you can find the others as you play.
The first is that a new skin 'flow' has been added. This is a responsive skin! open up theme_settings.html and set it as the active skin to check it out.
After a lot of consideration - I have selected a 'skin first' approach instead of 'mobile first'. Typically the buzz is more for mobile first - but this is a lot of work for the end user, and in my travels - you don't typically see people restyling the whole site because of device - instead they typically tweek the design to make it work on these smaller/larger devices. So boom - "skin first responsive design" is born. Screw the preachy fanboys - it is more important to offer a simple system to our users imo. Let me know if you dig or hate.
Quite a bit of markup skeleton tweeks.
So I have added an array of common lookups for you to use in your scripts.
Here is the array:
I didn't mean add it to the core. I meant instead of adding something like that to the module - spend that time on making a theme ACP interface
I don't believe editing files on the web server from a web interface is something that needs to be in the core. Most people won't use it. It's tricky securty-wise as well.
You could offer it in a ACP-only module for example.
it might serve an intermediate purpose true - but I wouldn't call it an end-all solution.
The question is - is the time it would take to implement such a feature better spent advancing the core?
This may be slightly relevent - but one nice feature in the Sprocket toolkit module is the ability to edit css files from the admin area.
If we could provide themes with a standard "config" type file, and allow this to be edited in much the same way - it could allow us to create and set up values to control the whole theme from an admin side.