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

Poll: Suggestion for better Interface UI/UX #2

Open
mitulgolakiya opened this issue Apr 20, 2016 · 3 comments
Open

Poll: Suggestion for better Interface UI/UX #2

mitulgolakiya opened this issue Apr 20, 2016 · 3 comments

Comments

@mitulgolakiya
Copy link
Member

I am creating this thread where people can submit the idea like what changes we can make to existing builder UI to make it even better in terms of UI/UX.

Please submit your idea or any example that helps to make it even better.

@dhsont
Copy link

dhsont commented Apr 20, 2016

Thanks for builder @mitulgolakiya

you can see https://github.com/LaravelDaily/quickadmin for reference.

Suggestions

  1. select box for db types
  2. multi select box for validations
  3. use full width of browser so it can fit all fields properly (or use smaller check boxes)
  4. Auto capital first char of model name
  5. display old generated scaffolds ( where we can delete some old scaffolds)
  6. confirmation message before generating scaffold
  7. Notification after completion
  8. progress bar
  9. length field for db

I will add more as i play with package

@NightZpy
Copy link

Use this datatables plugin for dinamice datatables:

https://editor.datatables.net/examples/inline-editing/simple.html

Is a inline editor for data in datatables, have three ways:

  • inlin.
  • form popup
  • bubble.

@phillipmadsen
Copy link
Contributor

Love the way this is coming along. My thoughts on things this will need.

  • Relationship addon (User hasOne Profile) (automatically adds user_id -> profile_id relationship)
  • Ability to use other tables / models in one crud (example $user->profile->company)
  • Ability to generate views with different prefixes for the same shared resources (example below)
  • USERS CRUD
    • admin views (prefix:_admin_) (create, index, edit, show, data, table, fields, show_fields)
    • frontend user profile and account views (prefix:_account_) (profile, account, social)
    • development (prefix:_dev_) (design, create, todo, task-milestones)

Thoughts on existing setup.

  • Change DB Type to dropdown
  • add checkbox for default, nullable, index, unique, foreign, unsigned, pivot
  • When add primary button is clicked it should always be first the list.

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

No branches or pull requests

4 participants