It seems from this screenshot template use is going to consist of the following: 1) Users open that dialog and find a template they like 2) Users click install to download and cache the template locally 3) Users then go into a local template browser to pick a template for their project.
Why not cut a step out?
The online repository browser here can download a template (for caching purposes), but also immediately apply it to the current webpage. You can simplify things a bit further but making Local Templates just another repository in the repository browser. Then you have a one spot shop for templates, and one click on a template to download and apply it.
That's just my 2 cents, if you think what you're doing now will work better (and/or I've misinterpreted what you're doing now) by all means continue with it.
one comment
Interesting, but I have a suggestion.
It seems from this screenshot template use is going to consist of the following: 1) Users open that dialog and find a template they like 2) Users click install to download and cache the template locally 3) Users then go into a local template browser to pick a template for their project.
Why not cut a step out?
The online repository browser here can download a template (for caching purposes), but also immediately apply it to the current webpage. You can simplify things a bit further but making Local Templates just another repository in the repository browser. Then you have a one spot shop for templates, and one click on a template to download and apply it.
That's just my 2 cents, if you think what you're doing now will work better (and/or I've misinterpreted what you're doing now) by all means continue with it.