Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Template import #2

Closed
marpontes opened this issue Jun 13, 2015 · 0 comments
Closed

Implement Template import #2

marpontes opened this issue Jun 13, 2015 · 0 comments
Milestone

Comments

@marpontes
Copy link
Owner

There's already a button on admin-ui [the plus central button located on the header] that is supposed to call the template-import use-case.

When the button is clicked, the user is supposed to choose a zipped file from his machine and the system is then supposed to upload it, check for pre-existing folders with the same name of the zipped folder within and then place it on the right spot : resources/templates/.

If there's already a template with the same [folder]name, the process should be intelligent enough to determine a new folder-name.

Even though there's a minimal structure for a template, we shouldn't do many checks at this point. The system should be intelligent enough for not listing/controlling badly structured templates.

The zip file should have the minimal template structure which is:

  • my-template.zip
    • my_template/
      • template-confir.json
      • index.html
      • assets/ [public-files inside]
        • [...]

This issue should deliver:

  • The uploader view on admin-ui with a nice and modern interface
  • An Pentaho uploader endpoint
  • kettle Endpoints to handle the process
@marpontes marpontes modified the milestone: 0.3.0 Sep 15, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant