Coder Social home page Coder Social logo

gooey's People

Contributors

slurmulon avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

Forkers

linecode

gooey's Issues

DOM Templating "Language"

Proposal

We need to support transparent two-way data binding between the JS model service layer and the DOM.
Creating a DOM data binding syntax not only brings familiarity to developers (at least users of Angular, React, Ember, etc.) but also greatly improves data transparency.

Syntax

{scopeVar} or
|scopeVar|

I personally like |scopeVar| because it's easier to distinguish from many server-side template languages such as Moustache.

Tag Attributes

Assuming we are using |, I'm proposing that |- can be used to explicitly reference Gooey components. The following example is a basic usage of gooey.components.core.model where foo is a value present on the scope:

<input type="text" |-model="foo" />

Integrate ES6 Proxies into gooey.Service.data and gooey.Service.publish

http://www.2ality.com/2014/12/es6-proxies.html

Ensure data is a Proxy object that integrates proxy event handlers into gooey.Service.publish

This will be useful as it is a native abstraction for intercepting property requests on objects. This will allow us to more easily support model/view two-way data synchronization.

  • If data is a proxy, concurrent Service subscription handlers will be able to more easily synchronize data mutation events (order specification, conflict resolution fn, etc.), especially those between sibling Services that are mutating identical data points.
  • This is easier on the developer because we can trigger native events when data is mutated, and therefore we can trigger a recursive publication of that data change. can provide a "weight" heuristic to automatically resolve any remaining conflicts

Support additional matching mechanisms

It's been a while since I worked on this, but ran into some issues on personal projects that could benefit from fancy PubSub.

One of the main annoyances I find is only being able to match with json-where. It would be nice if we also supported the following matching mechanisms:

  • Arbitrary String
  • JSON Schema

This will require refactoring the matching functionality a bit (obviously), most likely involves adding a new layer of abstraction so that we can disambiguate what sort of matching pattern is applied (JSON Schema, json-where, exact string, etc.)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.