Community
Participate
Working Groups
We decided to adopt the qooxdoo version currently used by RAP instead of migrating to a newer version. To do so, we should apply the patches currently stored in the qx.build project to our qx codebase.
I think the first classes we should adjust are Widget, Parent and Terminator: Put them in our namespace, change formatting, remove unused code, remove superfluous comments, split Widget.js to extract the queue-system. In the long run, they the queue and layouting system should also be simplified and properties replaced by normal setter/getter.
With the fix for Bug 328382, i introcued org.eclipse.rwt.HtmlUtil, which should become the new central place for browser-abstraction regarding creating HTML/CSS content. (Should not include eventhandling, javascript-helper, or getting client info.) We should collect all existing code that maches this task here, including from: - qx.bom.element.* and qx.html.* (*) - qx.ui.core.Widget - org.eclipse.rwt.widgets.MultiCellWidget - org.eclipse.swt.widgets.TableItem - org.eclipse.rwt.widgets.TreeRow (*) What doesn't fit into HtmlUtil thematically should either fit in another new Util-class or be deletable.
Opend a blocking Bug 330225: [client] move/merge/delete Widgets remaining in qx.ui namespace. I now think (even though stated otherwise before) that Widget, Parent and Terminator should be among the last widgets to be moved/refactored.
I think what was the main goal of this bug has been achieved, the client can no longer be considered part qooxdoo/part rap, even though there are a lot of qooxdoo artifacts remaining, but that will realistically always be the case. I'll update Bug 330225 to cover whats left and still relevant in my opinion.
