1 While the editor is not to bad at present there are a few fundimental
2 issues with the design, that could do with some thought
5 The application builder itself core window is a huge tree that describes the UI
6 This makes working on the thing slower as it's often more difficult to find the related code.
8 - Big handlers and methods on objects
9 Kind of related to the big tree issue, the was it's possible to add methods to objects
10 results in quite a bit of the code getting added to a variety of objects in the code
12 - Breaking code into 'groups'
13 The cleaner idea here would be to break the code into groups, in such a way that all the 'special'
14 methods for a group of elements would be always at the 'top' level.
16 Currently all generated code looks like
18 Window = new XObject({
19 ...... (the tree goes in here..)
22 ... Window.init() <<< This actually causes a build..
23 << It could probably be done outside...
24 XObject.cache['/Windows'] = 'Window'
35 -- GTK code needs simplifing so it works better 'out the box'
36 ** get rid of the 'init' methods
37 - basically the XObject base code should handle stuff that is in there.
38 ** this has a knock on effect that we will provide additional 'children' to the tree structure though..
40 eg. to fake a table - we would do something like this..
48 Building a reference for adding one element to another..
50 a widget being added to a box...:
51 a property with 'parent:' describes how it get's added to the parent..
53 parent:add_mnemonic_label = this
68 - what it can be added to, and args that need/can to be used..