See https://github.com/angular/angular/blob/master/TOOLS_JS.md

Scope:

• Visual components should be able to have CSS styles;
• Styles can be simple (custom string value) or predefined (value from the predefined list).

Basic project setup should include:

• Gulp with angular2, TypeScript and ES6 build steps;
• ESLint or JSHint support;
• Watch support.

We need concept of base abstract component that can base for the following things:

• UIComponent - ButtonComponent, InputComponent or LabelComponent;
• ServiceComponent - DataSourceComponent or WorkerComponent.

Currently we have too many intermediate elements so that simple div ---> button structure looks like:

• Container component
  • Container content
    • Dynamic component
      • Button component
        • Button content

It's too much and makes styling difficult since only Fx supports display: contents that these intermediate elements can use. So we need to find acceptable solution.

Scope:

• Interfaces and base classes for MessageChannel and Message.

Blocks #11

In this app we should add support of multiple pages apps:

• User can add/remove pages to the app;
• User can setup very basic navigation flow from one page to another.

Scope:

• Events should be able to be serialized/deserialized to/from JSON.

Scope:

• Serialize component tree to JSON string;
• Deserialize JSON string to component tree.

Scope:

• Interfaces and base classes for Action.

Blocks #11

Scope:

• Default app generator will generate web application based on Angular2 lib;
• Stages of component markup generation:
  • Styles are composed to dynamic class;
  • HTML markup;
  • index.html:
    • References to custom stylesheet;
    • References to angular libs;

Properties:

• Url to navigate to.

Scope:

• Properties pane should be displayed;
• Component can be selected;
• Properties pane should respect currently selected control;
• Changes in property pane should immediately be propagated to the work-space;
• Basic properties for this bug are: text and title.

Scope:

• Background color;
• Text color;
• Alignment (flex box).

Scope:

• Control should have predefined list of default values for properties and styles;
• Control should id field to be easily identified.

Chrome/IE doesn't support it yet, and I see bug in firefox with nested containers - need to file a bug.

In this bug we'd like to introduce ChangePropertyAction that will be responsible for changing any control property on any event.

ListControl should support DataSource property.

Scope:

• For now we just need - update control property editor.

Scope:

• Editor should allow to drag controls from control pane to the workspace area;
• Container component should be able to retrieve control that is dragged and render it alongside with the rest of its children.

To begin with action and events we should be able to serialize/deserialize actions/event handlers

Currently URL property has value in "{type}:{value}" format, so we should be able to support "bind:{binding-property-name}" as well

Scope:

• User should be able to set event handlers for the components;
• User should be able to connect events with actions;
• As the first step we'd like to:
  ** Change label name on button click;
  • Change button color on button click;
  • Change label background color on hover.

Dependencies:

• Introduce support of default properties and styles (#14)
• [Events] Implement basic Action entity (#13)
• [Events] Implement MessageChannel and Message (#12)

In the scope of this bug we should have basic app that allows to:

• List all components (left side);
• Editor field.