Any reasoning in particular for this outlook? I'm all for it, but I only suggested the incremental switch as a means to ease developers into a changeover. Is it primarily because you'd like to minimize code quality-degradation that would likely accompany disjoint development patterns?
It's worth noting that although the administration area and the customer front-end of nopCommerce come in a single package, they really are essentially separate applications. Really, there isn't any compelling reason that the development of one must hinge on that of the other. Personally, I think it would be interesting to see the development of the storefront and the administration area become entirely decoupled so that they can each be maintained semi-independently of one another, which in turn would open up the door for forked projects like a Silverlight administration area or similar
It's worth noting that although the administration area and the customer front-end of nopCommerce come in a single package, they really are essentially separate applications. Really, there isn't any compelling reason that the development of one must hinge on that of the other. Personally, I think it would be interesting to see the development of the storefront and the administration area become entirely decoupled so that they can each be maintained semi-independently of one another, which in turn would open up the door for forked projects like a Silverlight administration area or similar
Maybe, but two separate applications will require store owner to install two applications. It's unacceptable. It will also make impossible to install nopCommerce using WPI (web platform installer).
