On Tue, Jan 11, 2011 at 3:36 PM, Marius Dumitru Florea <[email protected]> wrote: > On 01/11/2011 01: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). >> > >> WDYT ? > > How would you detect that a style is deprecated?
I think there is no way of doing that except tracing the style in firebug or equivalent and see it is in the compatibility file. So indeed, you can't really warn the developer he is using deprecated classes/styles. But it does not mean we should drop compatibility because of that IMO. What we could do is in the release notes list all classes or IDs for which styles have been deprecated. WDYT ? > > Thanks, > Marius > >> >> Jérôme. >> _______________________________________________ >> devs mailing list >> [email protected] >> http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
