On 10/16/2009 11:12 AM, Guillaume Lerouge wrote: > Hi Anca, > > On Fri, Oct 16, 2009 at 10:54 AM, Anca Luca<[email protected]>wrote: > >> On 10/16/2009 10:44 AM, Guillaume Lerouge wrote: >>> Hi Anca, >>> >>> On Thu, Oct 15, 2009 at 9:07 PM, Anca Luca<[email protected]> >> wrote: >>> >>>> Hi Guillaume, >>>> >>>> Guillaume Lerouge wrote: >>>>> Hi Anca, >>>>> Do you plan on using GWT to achieve this? If not, what's the best way >> to >>>>> code it in a cross-browser, maintainable way? Using one of the JS >> library >>>>> already embedded in XWiki such as Prototype I guess? >>>> >>>> I don't have a plan. >>>> >>> >>> Good luck. >> >> The only problem with GWT is that the javascript is not editable right >> away: it >> goes through compilation (so the source itself is not the "executable" >> anymore, >> as in standard interpreted languages which js is) whereas a jsx, for >> example, is >> editable from the wiki. Again, an admin / programmer in a wiki could go in >> and >> tweak some js without access to the server fs, or a GWT compiler, or >> downloading >> sources, or etc. >> >> However, the main advantage of GWT is its cross-browser-ness, the precious >> selection API we have and easy development in the more "stable" Java. >> > > Is there a way to have GWT retrieve values for some CSS properties from > XObjects? > > For instance, is the GWT-based UI could retrieve its CSS color codes from a > ColorTheme object it would allow you to code in GWT while still giving the > wiki admin some control over the annotations' look. > > Is that doable?
Styling was never an issue with GWT code. Editing the source javascript is, and it's not possible to do it. What's doable is to have a mix of GWT and plain javascript, like a core functionality and API in GWT, which is used by a JSX to provide the UI. But this only increases the complexity, and doesn't add the advantages of both frameworks, on the contrary, it only sums their disadvantages. Still, why do you think that GWT is more cross-browser than Prototype? IIRC, there were lots of problems with GWT code, too, and the main problem with both JS and GWT code is not the code itself, but the very general rules in the core skin, which have many side effects hard to overcome. Am I right? So, personally I prefer the Prototype way, but Anca's vote counts more, since she'll have to write the code. By the way, +1 for the general goals, Anca. -- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
