How can other projects use Lovelace without dirtying the repo?

jacopotarantino / Lovelace

Styleguide and language-agnostic UI component framework.

6 stars 0 forks source link

How can other projects use Lovelace without dirtying the repo? #3

Open jacopotarantino opened 9 years ago

jacopotarantino commented 9 years ago

As another developer consuming the Lovelace project, I would like to add my own components without polluting the repository by adding new code to the /components directory.

Perhaps /components isn't checked-in code?
If Lovelace doesn't check in an example setup, there needs to be an example directory or project consuming Lovelace so that devs can see how the code is supposed to work.
Maybe Lovelace should really be a yeoman generator?

jacopotarantino commented 9 years ago

Client-side apps might be able to take a remote URL as a location for templates instead of using the built array. If so, that might be bundled into a release that allows for all manner of components to fetch templates/files from a remote server.

jacopotarantino commented 9 years ago

#init method for node ✓
method for ruby ✓
method for client
update example apps to use method
update all tests
update documentation

jacopotarantino commented 9 years ago

Client API doesn't need an init method since the files will already be built server-side(unless fetching from an endpoint?). Client build process should take a root_component_path flag and use that to find target files.