Magento 2.0: Amazingly-Featured & Advanced Version of Magento 1.x
|
This article highlights some major points of Magento 2.0 that has grabbed the attention of all and sundry since its rollout in the web world. The latest version is not like Magento 1.x rather it’s got a set of modules that come with high code coupled between each other. Moreover Magento 2.0 is also not containing class alias, rather all the objects are generated through createObject () factory by passing full class name. There are not any more definitions of class aliases in configuration.
Magento 2.0 isn’t similar to Magento 1.x
Magento 2.0 hasn’t been structured like Magento 1.x. It is a very improved version and has got a lot of amazing features that will allure the Magento buffs a lot.
Component Oriented Modules
The Magento 2.0 has been built-in with a set of modules that contains high code joining between each other. So, some components can be easily disabled or/and replaced. Plus, there’re interfaces that help to organize relations among components. Those interfaces ought to be executed in your component. In this way, customer components, checkout, sales, etc can be disabled with a lot of ease.
Good Bye Class Alias
The Magento 2.0 does not have class alias, instead all the objects are brought about with the help of createObject() factory by passing full class name.
View Modularity
All the created custom themes will be having directories according to per module view. So if you wish to replace some layout, template, you’ll have to bring about directory similar to the module name; for example: Namespace Module not Namespace/Module), and put there overridden file.
Infinite Themes Inheritance
It also allows for the creation of custom fallbacks for themes, as per browser, holiday, store, etc. Thus, you can render highly clear theme structure for your customers, at the end, you can chuck out copy-pasted data.
Just do a small customization to core/design package model, override _fallback method and call parent with extra $fallbackScheme rules.
Good Bye EAV?
Though not finally decided, they are planning to replace EAV with simpler key/value execution for RDBMS, providing you with an alternative of selecting NoSQL adapter rather than RDBMS.
Integration Tests
They’re planning to write integration test (non-isolated) that engulfs legacy functionality in core. At present, they’re having around 47 percent code coverage for Mage Catalog and 53 percent for Mage Core.
Different Directory Structure
In Magento root, only five directories are to be left rather than present 9. The pub directly will be having all the publicity available files, rather than available “media”, “js”, “skin”, “error”.
Magento Contributions
Last but not the least; there is going to be more crystal clear process of including community into developing Magento 2.0. The process can be seen in public Jira.
SynapseIndia is leading Magento Development Company that has extensively experienced Magento developers who leave no stone unturned in terms of quality and reliability.
|
|
Author Resource:-
This article has been written by a technical writer working at SynapseIndia - a Magento Development company of India offering the services of professional Magento developers to the worldwide clients at very affordable cost.
|
By :
Jesse Zargosky
Submitted
2012-01-04 08:50:07 |
Article From Article Mayhem
 Ezine ready view |
|
|
|
Related Articles
|
|
|
![[Valid RSS feed]](http://www.articlemayhem.com/images/icon_Rss.png "XML Feed For RSS"){kind=icon}
Category Rss Feed![[Valid RSS feed]](http://www.articlemayhem.com/images/rss.jpg "XML Feed For RSS")