TEMPLATE POSITIONS

Already mentioned some ideas elsewhere, and also on Skype chat. There were already other topics, but I will post here, because it fits...

I think, the new Joomlart T3 v3 is a good inspiration and maybe code-source for a universal cobalt template builder. I could also live with a fixed-all-purpose template like Seblod's CCK 42. But did someone notice the new Joomlart framework with Bootstrap support and new backend configuration?

I think, this could be a great start for an** interactive layout editor**. Or quick-layout editor. Bootstrap grid system supports nested grids, which is really helpful to integrate a cobalt template into the main joomla template.

You can see the Joomlart visual editor in action here: - Docs - Video

I could also live with a fixed-all-purpose template like Seblod's CCK 42

Seblod - default template positions

Or: a module to insert Cobalt record fields.

You could then have similar results and flexibility without a custom template! :)

Best Regards,

Jeff

FYI - Bootstrap Form Builder

Maybe useful resources for a quick-template editor and Drag'N'Drop of fields ;-)

GitHub project

GitHub project (fork)

FYI - Gridster.JS

Gridster is a jQuery plugin that makes building intuitive draggable layouts from elements spanning multiple columns. You can even dynamically add and remove elements from the grid.

Homepage

Github project

Example:

Gridster Wordpress plugin, which makes use of Gridster plus additional Inline-Editing and Saving.

Github project

**pepperstreet **

I could also live with a fixed-all-purpose template like Seblod's CCK 42.

I initially liked that concept when I started using Seblod, until I discovered the enormous amount of extra markup that was added. Later on I started used Simons simple template.

Tweaking vs hacking

Like Clowride and pepperstreet have suggested, there is a valid need for positioning elements/fields instead of creating a custom template for that purpose. Why? Because it will speed and simplify the developing of web apps. It is tweaking vs hacking, and I prefer to tweak.

Cobalt template positions vs making Cobalt modular

Pepperstreet already mentioned the example of how a template framework deals with modules display and positioning. That is why I suggest making Cobalt modular instead of templating it. Imagine assigning fields, section menu's, etc to module positions. You would have ultimate flexibility and choice without adding extra markup into Cobalt.

Addressing responsive design issues

As we all know, mobile browsing is the future, and it is already here. Making a responsive web app usable and practical on a smartphone is a big challenge because you have to deal with speed issues.

The beauty of css is that we can create different kind of css for each media size. I know I can display modules depending on media size also. I can even decide which js to load depending on media size (if I put them in a module).

A general rule for addressing responsive design issues for mobile users, is to purposely hide information that unnecessarily increases response time.

Now let's get back to making Cobalt modular. Imagine having a section menu as a module. You could create a simplified version for mobile users. For example one without Google maps and Timeline and without the extra scripts involved. Or you could decide to show certain fields to full screen viewers only.

YooTheme's new Warp7 Framework makes it possible to assign modules to different devices. Nonumber's Advanced Module Manager offers the same functionality.

Any thoughts on this matter are welcome :)

Best regards,

Jeff

Media CSS allows to hide modules depending on the browser width.

BTW mobile browsing (in my opinion) is not the future, but part of it. It has the screen limitations and bandwidth issues still associated.

stblink

BTW mobile browsing (in my opinion) is not the future

Well, no one can look into the future of coarse, but some figures are hard to ignore :)

stblink

BTW mobile browsing (in my opinion) is not the future

stblink

It has the screen limitations and bandwidth issues still associated.

Yes, I agree. That's why I mentioned the future :)

But maybe it's just a matter of time that bandwidth isn't an issue anymore. And don't forget the success of mobile phone apps, where the screen size isn't a limitation but an advantage.

BTW, your comment reminds me of discussions I had with fellow multimedia developer students, back in 1995. It was all about CD-ROM, CD-I and information kiosks, internet wasn't even an option because of exactly the same arguments you just gave :) No one had ever thought of the concept of (powerful) mobile smartphones or tablet pc's for the masses. You have to agree that we live in an exciting era in terms of technology.

Yes, mobile browsing is indeed a part of the future, we just don't know how big that part's gonna be :)

True, we still live upon a generation that is not used to use cellphones for internet. But that generation is diying and those who were bourn in the Digital Era will be raised using cellphones/tablets/pc's/consoles which is more easier to learn at their age.

As the statistics link you mentioned. Cellphone internet usage is growing (nothing new) but for Iphone usage for example it's used only 20% for web browsing.

Meaning that, in my opinion even if i'm browsing a responsive website on my cellphone, i only use it if it's urgent and i don't have my laptop with me. It's way much faster and less eye-consuming.

Of course we are talking about the current devices... in 2 years the cellphone market will be a completely different market, with new technology. The day that a cellphone surpass the screen limitations (3d projection for example) it will be a completely different scenario.

stblink

Meaning that, in my opinion even if i'm browsing a responsive website on my cellphone, i only use it if it's urgent and i don't have my laptop with me. It's way much faster and less eye-consuming.

Same with me. On the road I'm only using apps to get my info from the net. My Twitter and Google Plus accounts are catching dust and I refuse to use Facebook (I recently set up an account for testing purposes only)

I guess I am not an average mobile phone user. And that's ok, because I am not building sites for people like me.

IMHO I think responsive webdesign is not the holy grail, but used smartly, it can be a cheap and effective way to satisfy your mobile viewers. Maybe Joomla has adopted the Bootstrap framework for that same reason. There's still a huge gap between building a normal website or building an IPhone app, and I am happy to fill it. :D

refuse to use Facebook

Same with me... i aknoledge that is a fantastic tool for marketing but other then that... spare me! And people like you and me are more and more, no wonder facebook is going the same way hi5 did.

refuse to use Facebook

IMHO I think responsive webdesign is not the holy grail, but used smartly, it can be a cheap and effective way to satisfy your mobile viewers.

Agreed. The cheepest way indeed, it's a matter of analyzing Google Analytics to know how much users use mobile to visit our sites to see if it really is worth the job.

I mostly use RT templates which are already responsive but the problem is mostly with the apps that we use for specific functionalities. But even asking a freelancer to make changes, it still is way more cheap then an app.

pepperstreet

Hiding things with media queries and CSS does not lower your bandwidth. You still have to transfer and download everything.

Agree. But a some tweaking is possible. Deciding which components, javascript and css to load for example.

Which means filtering content and functionality per screen width. It is all doable without complex programming, by combining existing templates, plugins, components and modules. All it takes is a lot of preparation and a different mindset: create the mobile website first and then the rest.

pepperstreet

Hiding things with media queries and CSS does not lower your bandwidth. You still have to transfer and download everything.

pepperstreet

So, performance on the devices is not so important, its the bandwidth and current limitations for mobile contracts.

Bandwith is not the biggest issue, it's latency. The signal that reaches mobile users takes 4x longer from and to their devices, even if they use a 4G network. So reducing html-requests and using a cdn should be on your priority list if you want to speed up mobile browsing.

My Twitter and Google Plus accounts are catching dust and I refuse to use Facebook

Wow, and i thought i'm the last dinosaur without a twitter and facebook account ... :D

I have installed Shape5 Vertex Framework and the free template.

Works good for me, and only small problems with some cobalt templates being not 'responsive' - but am working on that.

http://www.shape5.com/product_details/free_templates/

Hope this helps.

D.