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

Strategy for upcoming UI advancement #110

Open
raDiesle opened this issue Jul 29, 2014 · 1 comment
Open

Strategy for upcoming UI advancement #110

raDiesle opened this issue Jul 29, 2014 · 1 comment
Labels

Comments

@raDiesle
Copy link

Sers,

Longterm thoughts: As UI is going to become more and more complex
I suggest the following changes to code, having in mind, that administrators&coders have a nice network bandwidth & computers anyway to check phantomas:

  • moving client rendering to the browser only
  • using a framework like angular & bootstrap ui
  • reevaluating charting
  • not reason for minifcation
  • grouping functionality in folders/files

How do you think about it?

@stefanjudis
Copy link
Owner

👍

I'm thinking about exactly the same things.
But these are all things that belongs in a different project.

In my personal roadmap this project needs to be moved somewhere else so that the grunt-plugin only is a wrapper for this project.

So my steps would be:

  • start new project
  • remove grunt dependency
  • wrap new project with grunt-phantomas over even change this one to really execute phantomas only

Actually I don't want to get it bigger and bigger, because it's already way to heavy for a grunt-plugin.

After that I'm almost open for all your suggestions. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants