Morph updated – new versions across the board
The downloads area is now updated with new versions of pretty much everything (Morph related at least).
The new versions are aimed at addressing all the issues that have been reported on the forums, as well as introduce a few new features. See the individual changelogs below for details.
You will notice that all the themelets have been updated, but the updates were limited to just what was necessary for the new Morph / Configurator changes, such as the backend editor, new module positions, etc.
General Quick Installer updated to 0.03
- Updated the sidebar module positions to use Morph’s new positions.
- Upgraded the Advanced Modules extension to 1.03.
Configurator updated to 1.04
- Updated the LiveDocs url with the new version.
- Updated the Help tab content about where to get help.
- Updated the Inner & Outer sidebar tabs with the new module names.
- Added new Code Editor feature in Configurator (tools > code editor).
- Updated some PHP 5.3 deprecated functions.
- Added new tab for Lazyload plugin (plugins > lazyload).
- Added new tab for Colorbox lightbox plugin (plugins > lightbox).
- Changed the memory limit to set only if less than 64mb.
- Added new tool to move modules from old sidebar positions (tools > module migrator).
- Removed the rounded corners tab to avoid confusion until its full implemented.
- Added auto remove of version cookies when upgrading from Configurator.
- Fixed PHP memory_limit reduction and upgrade errors.
- Removed the progressive enhancement tab as it was not really needed.
- Added click event to color picker for selecting colors on click.
- Corrected incorrect titles on some dialogs.
Morph updated to 1.05
- Updated the content>section html overrides with the language updates.
- Set the column wrapping div to only load if 2 or more modules are loaded & general code cleanup.
- Updated the pathway code (stripping the subtext) to work with php 5.3.
- Updated all the instances of the old sidebar module positions.
- Implemented new split menu to dynamically use the parent item as the module heading.
- Removed the main content wrapper margin if no outer sidebar is published.
- Fixed the Zero Javascript option.
- Re-implemented the &unpack_css/&unpack_js url switches.
- Added a close button to the devbar (only works if js is enabled).
- Implemented the lazyload jQuery plugin.
- Number of fixes for PHP5.3 deprecated & directory separator issues.
- Implemented Colorbox lightbox – more options and docs coming soon!
- Added option to disable the tp=1 switch (thanks Pembaris for suggesting & Joomlaworks / Corywebb for the tip).
Vanilla updated to 1.04
- Fixed the issue with subtext menu’s in accordions.
- Set a fixed width on the category table numbers column & centered the text.
- Removed the author name capitalize from the blog and article views.
- Fixed the article row spacing to be consistent on single rows and columns.
- Updated the themelets xml with the new sidebar module position names.
- Updated the custom css/js/php/script files to pull from the database.
- Added an iphone css override & did a couple of tweaks to be inline with the themelet style.
Light Candy updated to 1.02
- Updated the custom css/js/php/script files to work with the built in editor updates.
- Updated the sidebar module positions in the xml to reflect Morph’s new sidebar positions.
Ultra Candy updated to 0.02
- Updated the custom css/js/php/script files to work with the built in editor updates.
- Updated the sidebar module positions in the xml to reflect Morph’s new sidebar positions.
Leblanc updated to 0.02
- Updated the custom css/js/php/script files to work with the built in editor updates.
- Updated the sidebar module positions in the xml to reflect Morph’s new sidebar positions.
Explorer updated to 0.02
- Updated the custom css/js/php/script files to work with the built in editor updates.
- Updated the sidebar module positions in the xml to reflect Morph’s new sidebar positions.
As always, if you come across anything that is out of place, please let us know.
Liked this post? Help spread the word by sharing it!
Tags: Candy, framework, Joomla, Le Blanc, Morph, Quick Installer, vanilla
Hm,… I really try to understand the Morph and I have to say all this “frameworks” emerging this days… but i don’t get it. Basically as a designer I change the design of a website not more than once a year. Not to mention my clients – once the site is set they hate to make any changes!!
But your effort and of all “commercial template designers” goes in the direction to have one template suitable for all. So this templates have a humongous amount of different setting no one use it. That’s why I make a custom design for every client and it’s light, light, light with no excessive coding.
I really don’t get it boys!
Cheers,
Dorjano
Hey Dorjano,
Our aim with Morph is provide a tool that helps speed up the process from taking a project from a concept to a finished site. I’m sure in your own way you are using your own “framework” of reusable code snippets and tried and tested practices. This is exactly what we’ve done with Morph. Instead of recreating the codebase with each new release, we decided to standardize the base which in turn allows us to release our concepts faster. Configurator as a gui is a means to manage all aspects of this and gives the user control. Again, this isn’t going to appeal to everyone, but so far the feedback we have received has been amazing and many users have come back and said that its really helped them “go live faster” which means we’re doing something right.
Frameworks aren’t for everyone and that’s ok
As for the excessive coding, while there will always undoubtedly be more code involved in a comprehensive framework, that doesn’t necessarily mean it has to impact a sites performance. Since Morph is always the same template (an approach that is unique to Morph), it allows us to keep on refining the core and already its on par with other leading “performance” templates out there. We’ll be publishing more info on the performance side of Morph in the weeks to come, but if there is no noticeable performance loss and it gives you the flexibility to take a concept and have it as a working prototype in a matter of hours, then it cant be all bad.
Another aspect of Morph which i’d like to touch on is the ongoing flexibility it gives you. Your example of clients redesigning once a year is valid, however it doesn’t take into consideration the ongoing growth of a site. From our own experience of doing client work over the years, was that websites need to grow as your business does. A client’s requirements may start off with a really simple 1 column basic holding page, then expand into a 2 column as more content is added, then extended navigation, possibly adding in a shelf, a second sidebar to accomodate some new content, adding a blog, etc etc. Obviously Joomla gives the user this flexibility, but unless a template developer has thoughout all the possible future requirements that their customer may have, then this generally gets added on bit by bit. With Morph, all of that is there and is only ever loaded when its needed. Our aim being that the template is flexibile enough to grow with your business.
Another aspect of what you are leaving your client with is the other built in tools that are part of the Morph Toolset. For example, the page class suffixes which enable your client to easily change their sidebar layouts for any given page or component, or the mix and match module styles that allow them hundreds of different module style combinations.
Again though, frameworks aren’t for everyone, but having built Joomla templates for years and seeing the difference it makes in my own workflow, i’m pretty stoked with what we have managed to achieve with Morph.
Hope that gives you some insight into our motivation behind creating Morph and helps you see that while Morph may not be for everyone, there are many many users out there that can benefit from the work we are doing – even if that isn’t you
Cheers,
Chris
Chris´s last blog ..Morph updated – new versions across the board