Enhanced admin roadmap for 1.0.0

padrino / padrino-framework

Padrino is a full-stack ruby framework built upon Sinatra.

http://www.padrinorb.com

MIT License

3.37k stars 509 forks source link

Enhanced admin roadmap for 1.0.0 #1154

Open dariocravero opened 11 years ago

dariocravero commented 11 years ago

[ ] Revamp the concept and make it completely data driven.
[ ] Super dynamic. Think Backbone and async.
[ ] Super mobile friendly. It's better now than it was before but there's still lots of work to be done.
[ ] Add filters, search, infinite-scroll or pagination, etc.
[ ] Use whatever pipeline to compile assets the app uses beneath?
[ ] Impersonation feature. See #156. (maybe as an addon/contrib?)
[ ] Forgot your password feature. (maybe as an addon/contrib?)
[ ] Foreign key support #1524

Let's discuss this in more depth @padrino/core-members, @tomatuxtemple and everyone else :)

ujifgc commented 11 years ago

Infinite scroll for admin panel is not an option.

DAddYE commented 11 years ago

@ujifgc but?

dariocravero commented 11 years ago

@ujifgc I reckon we can discuss that further but a smart use of replaceState and pushState and a good algorithm to predict "page" jumps may give users an amazing experience. It's all about modern and flexible user interfaces at the end of the day. At the same time, it doesn't have to be mandatory.

sonoman commented 11 years ago

I think I sent a feature but it got lost somewhere...would it be nice that padrino admin generator was able to recognize child relationships defined in Mongomapper model and gives you the option to generate a Master-Child admin-page ? Something similar to Django, where you register an admin model for EntityA (the "1" side on a 1:N association), and for that model you specify that ChildEntity (the "N" side) should be treated inline (thus, generating a "Master Child Page"

dariocravero commented 11 years ago

@sonoman you're more than welcome to provide an implementation for it. The thing this kind of features is that eventually they should be functional on all the ORMs we support on the admin and it can get quite tricky if we start messing around with all of those. However, I agree it could be quite useful.

wakatara commented 10 years ago

I'd also suggest using datatables. I'm doing this currently and it works fabulously with the admin interface. Also, avoids too much fancyness - additionally with some simply rabl templating and remote-source you can get a really nice, speedy interface and works nicely with will_paginate.

Will post code/blog post as soon as I've figured out why my destroy link_to doesn't work.

ujifgc commented 10 years ago

Yes, I use datatables in my CMS admin panel and it indeed works fabulously with XHR, sorting, filtering, all the things. I had to write a separate controller for the background requests but it was worth it.

wakatara commented 10 years ago

Also, ran across dynatable (http://www.dynatable.com/) recently which looked very, very nice but still, been using datatables myself.

kkirsche commented 9 years ago

How would I go about assisting with rewriting the admin front end interface? I'd be interested in helping put together a new admin section using Bootstrap and Angular as this combo would work nicely

dariocravero commented 9 years ago

@kkirsche thanks for your help. The current implementation of the admin is already using bootstrap. I would be slightly concerned about forcing a UI framework but I'd say that, true to the agnostic approach of Padrino, it might be a good idea to open the door for multiple UI implementations of it. We would need to finalise the admin's internal API that @skade suggested a while ago before jumping on this though I think.