Doing something better with the admin hstore is definitely something I'd like to see land.
1. I'd like more input on the features people feel are essential. Something that allows you to add/change/delete keys is all you need to start with. Features like soft delete can be added later. 2. Is there a guide somewhere to styles and markup to be used in admin templates? No, in short. Keep it simple seems to be the best advice I can give - most of the code is very old. 3. I plan to pull in another icon from FA, but it appears the one we currently use for "inline delete" is customised from the original. Does anyone know who made these changes and how? No idea sorry. On 7 March 2016 at 22:57, Josh Smeaton <josh.smea...@gmail.com> wrote: > I wouldn't drop it if I were you. I (think) I watched you demo the hstore > admin field at melbdjango and it looked cool to me. If I used hstorefield > I'd be interested in the implementation. The dev ML isn't really indicative > of the broader django community I feel, because only a small portion of the > community seem to participate. Deafening silence here may still lead to > cheers elsewhere once it's available. > > If I were you, I'd make a small screencast/gifv of the feature in action, > reach out to some people that you know are using contrib.postgres (starting > with Marc), and explicitly solicit their feedback on usefulness. If you > still don't feel there is a real desire to have in core, could you release > it as a 3rd party project? If it requires hooks in core to support custom > fields then push those changes through separately. > > My 2c :) > > On Tuesday, 8 March 2016 08:18:59 UTC+11, Curtis Maloney wrote: >> >> >> >> On 08/03/16 02:43, Tim Graham wrote: >> > 1. Merging something minimal always help to get feature requests. :-) >> >> >> >> > 2. Could you be more specific about what you're looking for? All the >> > existing documentation for style related stuff is at >> > >> https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/coding-style/. >> >> > I also thought of ticket https://code.djangoproject.com/ticket/14831. >> >> This is no way covers the HTML or CSS structures used in admin. >> >> Given the deafening roar of absolutely no interest in this feature, I >> guess I'll drop it. >> >> -- >> C >> > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/f6144212-cdde-4729-9d42-3d79397079ed%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/f6144212-cdde-4729-9d42-3d79397079ed%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMwjO1Gboz0crk9gGV%3DO%2BW%2BxoHy4BvfR%3DjqDUXGE-9k8B%2B3OVA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
