Hi, Thanks for your feedback. And I must say - you are fully right about the process and separating the major versions from Patches. But, as probably you already realized, in 4.5.0 version there is a lot of important issues left. One of major features/news in version 4.5.0 was new frontend theme with major changes in related concepts. So now big part of issues upcoming from that version - are related to the template changes. We always tried to keep the procedure as you told: - Patches will contain only bugfixes, which doesn't need template and DB changes, - features, template changes, DB changes -> only to Updates (4.x versions).
Exceptions for Patches were allowed only on important cases. And this Patch (4.5.1) is an exception in default process - it will include lot of changes in templates, structure of javascript and css, picture handling, cleaned some stuff and done for more easily maintenance and customizations. Also new places for blocks will be introduced in templates. So - we are very sorry about double work needed for some stuff on your side, and that we didn't managed to do all that stuff in 4.5.0. But anyway we think that this will help to improve eShop in general and we'll do our best to avoid such cases in future. Best regards, Dainius Bigelis -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of anzido GmbH Sent: Tuesday, June 28, 2011 6:30 PM To: [email protected] Subject: Re: [oxid-dev-general] Split CSS files to smaller ones [T-OTTKKCGSHA-05] Hi, I'm not sure I got this right: the 4.5.1 patch will contain several template and css (and probably javascript) changes? If the oxValidate css class will be renamed to js-oxValidate in the 4.5.1 version and the jquery scripts will be changed accordingly, then this will probably mean that the customized templates that we built for the 4.5.0 release will no longer work with the javascript field validation unless we go through all the templates that we changed and replace the style class with js-oxValidate...? Luckily we only got one 4.5 project at the moment and we changed only a few templates, keeping most of the design adjustments to the css files (which we will need to change ;-) ), so I guess that won't be that much trouble actually. But I'm not really happy with front-end changes like that being introduced into a patch-release... I thought that patch-releases (4.5.x) were only meant for bugfixes and should keep frontend changes to a minimum (and introduce no api changes)... Anyway, I noticed some things in the list of removed / renamed css classes: * oxError -> oxInValid : maybe you should rename this to oxInvalid instead of oxInValid (no capital "V") because oxInValid suggests "ox in valid" - being in a list of valid elements - instead of invalid (not valid) ;-) * hreview, hreview-aggregate, hproduct, dtreviewed etc.: aren't these necessary for the microformats? If you remove them, then google won't interpret the reviews and products for the microformat values and won't show rating stars next to search results etc, or am i mistaken? Like I said: frontend changes, api changes and database changes mean that updates will cause some work for OXID partners, especially developers of 3rd party modules that are used in several shops that aren't maintained by the module developers themselves. If you could keep such changes to the update-releases (4.x) instead of the patch-releases (4.5.x) then this would mean that OXID partners will have less trouble updating shops to those versions. It would also mean that 3rd party module developers could expect their modules to work with all revisions of an update version (4.5) instead of having to check and probably release a new module version for each patch-release (4.5.x)... I know it's not so easy to separate the development of new features or frontend and api changes from pure bugfixes, but that would make the life of OXID partners a lot easier ;-) By the way: from what I can see the template blocks mechanism and some of the other new stuff in the 4.5 release is really really great and I believe it will eventually make it much more easier to write 3rd party modules for OXID eShop with much less need to change the original templates - this is a good step towards modules that can be installed by a mouse-click (without further changes) :-) Best regards from Dortmund! Robert Rosendahl | Entwicklung u. Support -- anzido GmbH Kirchhörder Str. 12 44229 Dortmund Tel.: 0231 - 60 71 079 Fax.: 0231 - 60 71 081 Mobil:0176 - 8325 1488 Email: [email protected] Web: http://www.anzido.com ( http://www.anzido.com/ ) USt-ID: DE257982972 Geschäftsführung: Andreas Ziethen Amtsgericht Dortmund HRB 20883 -----Ursprüngliche Daten----- Datum: 28.06.2011 16:22:34 Von: Linas Kukulskis <[email protected]> An: [email protected] <[email protected]> Betreff: Re: [oxid-dev-general] Split CSS files to smaller ones Vorgang: T-OTTKKCGSHA-05 > Hi, all > > After long discutions finaly, for 4.5.1 version we decided simplify css > structure (combine some files) and remove all unused css classes (do > cleanup). > In the future we will do some spike test for measuring how much refactoring > can improve performance and how css can be simplified and truncated. > > Since next Patch new structure of css files will be used: > all theme css are placed in folder out/theme/src/css/. This folder contains > subfolder out/theme/src/css/lib/ and 3 css files: > reset.css - resets all different default browsers attributes; ie.css - > used only for IE bugs or hacks; oxid.css - file for styling theme. > ../css/lib/ - folder contains css files, which are used by third party > components. > > All unused css classes from *.css files and from templates: > http://wiki.oxidforge.org/Removed_deprecated_source#Removed > > > Linas Kukulskis > Developer > > [email protected] > Phone +370 37 333053 > Fax +370 37 333054 > www.oxid-esales.com > > > OXID eSales AG > Bertoldstraße 48, 79098 Freiburg, Germany > > Lithuanian Division > K. Petrausko g. 26-316, Kaunas LT-44158, Lithuania > > > Sales tax identification number: DE 231 450 866 Board of directors > authorized to represent the company: > Roland Fesenmayr (chairman), Eric Jankowfsky, Andrea Seeger Chairman > of the supervisory board: Harald Fuchs Head office Freiburg: > Bertoldstraße 48, 79098 Freiburg, Germany Court of registration: > Amtsgericht Freiburg i. Br., HRB 701648, Office reference number: > 06/447/41949 > > > > The next Generation of Premium eCommerce > > > Latest version OXID eShop 4 as open source > > > > _______________________________________________ > dev-general mailing list > [email protected] > http://dir.gmane.org/gmane.comp.php.oxid.general _______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general _______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
