Minimalist SVG icons.

The metron cli already uses the markdown library, the framework library should as well.

Need to add console logging for exceptions and validation.

The current library depends on RSVP.js as a way to do JavaScript Promises and pollyfill them in the absence of native browser support. I want to replace this dependency with a custom solution than can be included natively in the library.

Instead of standard show/hide, incorporate pivoting for cycling through controls.

For example: new, cancel, delete, etc.

Not sure if these should be properties off the root of the form object or a public fields object that they sit in--leaning towards the latter.

Want to move towards two-way data binding with this.

Write a JS script to preload the data.

For example: metron.tools.A_REGISTERED_FUNCTION

If custom code is run first, auto-loading can then be prevented from running a second time if someone forgets to add data-m-autoload="false' to their HTML. This would then make the data-m-autoload attribute unnecessary.

This will break older applications, so saving it for 2.0. All list/form or list/view showing and hiding should be controlled by the pivot.

For example, when there is a list and form on the same HTML page, but the URL and hash change based on if the list or form is visible, if you copy the URL for the form, and send it to someone, when they click on the link, it should load/pivot the form, not the list.

The data bindings should match exactly, and any selected values should be cleared.

Templating currently works for repeated rows in lists, but needs to also be added to data-m-segment types of view. The entire DOM will need to be processed, but also repeaters within the DOM. "If" conditionals will also be needed.

See the app.ts file of the metron.space web site.

After the form loads with data on an edit, check for a data-m-format attribute on the form element, and then process the value of the form element according to that formatting method.

For example, an Active/InActive filter where the values were written out in HTML, but the selection of one of those values filters the listing should execute the callListing() method without having to write a custom change event.

The value passed should be the name of the template object array to iterate over.

Awesomplete is being used as an optional dependency for autocomplete functionality. I'd like to swap this out with a custom solution so that it's native.

The metron.ts file can simply import all other files, and then wrap them in an export with the module/namespace being metron.

This is not used anywhere.

Right now it is loaded synchronously, which throws a warning in the console.

Two scenarios:

• Filtering a list, clicking on an action (e.g., edit) taking the user to a different page to do something with that item, then returning after clicking another action (e.g., save, close) needs to result in the list remaining filtered since it's within context of the experience.
• Filtering a list, clicking away from the list, returning to the list via the back button needs to also maintain the filters.

This can be accomplished by either utilizing the querystring or browser storage (e.g., IndexedDB, sessionStorage). The latter will allow for the URL to be shareable.