milanaleksic/baobab

SWT UI described in JSON

Hi there 👋

• 🔭 I’m currently working on the cloud backend in Soda.io (mostly Java and Python)
• 🌱 I’m currently learning Zig
• 📫 How to reach me: @milanaleksic on Twitter, via LinkedIn, or via email [email protected]
• ⚡ Entire CV is available on https://aleksic.dev

baobab's Issues

If object is named starting with "_", don't add it to Transformation Context

Investigate utilizing ReflectASM to speed-up the reflection-based code

Add implicit object reference: parent for parent container

Use a single configuration XML instead of multiple properties files

Improve documentation readability

• add contents notes
• use google prettify with some dark theme for contrast

Make EmbeddedListener work for methods!

Exception handling is not possible if Method-Level event listeners are used

Generate Constants class from GUI file

It should be possible to create something like JPA metamodel based on the GUI file (for start, only names of the created components should be present, for easier referencing in Java files)

Rename reference.conf config keys to full package names for SGT

Annotation for model methods which trigger update

Migrate to Java 8

... and by doing so try to eliminate Guava altogether

Includes of partial GUI files

Because: this will increase modularity and make Baobab more cool

Introduce jacoco support in gradle build

Editor should handle GUI files without shell root control

To support partial definition of the UI in the GUI files, Editor should be able to allow GUI files whose root element is not of "Shell" type.

This can be done by using "ghost" shell which will be the parent of the prototype dialog, instead of the Editor's shell itself. In case the created shell does not contain as a child a new shell, it might mean that the GUI file wanted to create a partial GUI presentation.

StringConverter: use state machine instead of regex - to allow multiple replacements of different templates

Enable extensibility of the builders

Currently you can't extend it unless you change the swt-gui-transformer-core artifact

List all widgets available in context inside the editor

Move build to Gradle

Parser to replace JSON

It is perhaps better approach to make a real parser instead of using JSON. Maybe ANTLR?

Generate complete Java file based on GUI files

Why does Travis CI fail to download deps for SWT from maven.milanaleksic.net?

Model class with embedded Observer pattern for automated mvc

Support more than one property of a component in model

This means that @TransformerProperty needs to be extended to have an attribute "compnonent" which is stronger than the fieldName when searching for the form's component that should be binded

Implement @TransformerModel to wrap the component details

Idea is that components are getting defined in an independent model class, which when modified will be pushing changes to view, or, using property listeners, back to the controller class.

Current idea:

{
    "_type" : "shell",
    "layout" : {
        "_type" : "gridLayout"
    },
    "_children" : {
        "text(text1,{border})" : {}
    }
}

and on the controller side:

...
@TransformerModel 
MainFormModel model;
...

where the model would look like:

class MainFormModel {
  private ManagedString text1;
}

Manually calculate Maxs in ASM code

Editor: when trans. error occurs, graceful closing is not possible

Widget.setData is not supported

Shorter children notation

A shorter notation for children might be possible.

One suggestion: instead of writing:

"_children" : [
    {
        "_type" : "button",
        "_name" : "btnAccept",
        "text" : "[global.save]",
        "layoutData" : "[gridData](center,center,false,false)"
    },
    {
        "_type" : "button",
        "_name" : "btnClose",
        "text" : "[global.cancel]",
        "layoutData" : "[gridData](center,center,false,false)"
    }
]

you could write:

"_children" : {
    "button(btnAccept)" : {
        "text" : "[global.save]",
        "layoutData" : "[gridData](center,center,false,false)"
    },
    "button(btnClose)" : {
        "text" : "[global.cancel]",
        "layoutData" : "[gridData](center,center,false,false)"
    }
}

which is 4 lines less (but lines that appear often).

Remove ".gui.json" + explanation why it was needed from pages

Support Linux build servers

Replace hashcode with equals for arrays

Introduce SLF4J logging facade

Find text in Editor

Avoid "visiting" synthetic fields of model objects

Remove array syntax for children

{
    "_children": [
        {
            "canvas(canvas)": {
                // ...
            }
        },
        {
            "label(_)": {
                // ...
            }
        }
    ]
}

will become:

{
    "_children": {
        "canvas(canvas)": {
            // ...
        }
        "label(_)": {
            // ...
        }
    }
}

When updating from model update only affected components if possible

If @TransformerFireUpdate is used, entire form must be updated

Use java.beans.Introspector instead of your bean analysis

Move shortcut mappings to a separate file, away from ObjectConverter

Update deployment script to have partial "-all" artifact as before in Maven

Introduce MongoDB-like syntax for special properties

Whic means: replace "_<special_tag>" with "$<special_tag>" to be consistent with how some other major framework solved the same problem you're having

Think about moving to YAML for GUI files

SnakeYAML seems like a good library for it. There exists a Jackson adapter as well so the evolution should be easier

Remove "oldschool" child creation

This will simplify code base and avoid 2 ways of doing stuff.