tl;dr: Users need to be able to manage their components. We need to set up some Angular templates to let them do CRUD operations on them.
A components looks something like this:
The url is inputted by the user. We'll then run out and grab the component at the URL and parse the name. We should provide feedback if the component is malformed. Reasons for being malformed could be:
I'm sure there are a bunch more, but the infrastructure for these is a good start.
We can also provide feedback about the listeners, name, broadcasts and public methods. This will help a user troubleshoot potential problems with their component.
This is a pretty normal listing of the user's components.
On load of this view, we should run out and update the details of their component in the same way we do during create. We should also let them modify the URL.
Good ol' delete. I'd prefer a "delete" and undo rather than a confirm.
Angular!!! My weeklong love (with a bit of hate) affair finally pays off. On it.
@dethe I'd like to see the model when you've got a draft of it.
Why do we need to do URL parsing? We should simply suggest that all URLs be relative.
This stuff should live in mozilla-appmaker/appmaker repo and get its own controller (i.e. routes/components.js)
Sure, as soon as I get that far, will send model around.
URL parsing is for mapping github URL entered by user to our proxy.
I'll move it to a controller in appmaker, just wanted to grapple with it standalone first to understand the pieces.
It's not only for github URLs, no? I had pictured something like this:
done for now