On 01/11/2011 12:55 PM, Jerome Velociter wrote: > Hello devs, > > I've just hit an issue where my application relies on CSS styles > definitions that are being dropped between 2.7 and 3.0, namely all the > dashboardXXX classes, abandoned in favor of the new dashboard macro > styles. > While I reckon those CSS classes were never explicitly defined as > being APIs developers should rely on, I think we should offer better > backward compatibility for those who did rely on them, just like we do > with JavaScript code (see > http://dev.xwiki.org/xwiki/bin/view/Community/DevelopmentPractices#HBackwardcompatibilityanddeprecation > ) > > What we could do is introduce a compatibility.css file holding styles > for such deprecated classes, and decide if we want it or not included > by default (The JavaScript compatibility.js file is included by > default, for example, although the rules states that XE releases > should work just the same without it, of course).
Well, this rule is broken, since the core still uses ajaxSuggest (hardcoded in c.x.x.objects.classes.DBListClass#displayEdit or something like that). +1 for deprecated.css -- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
