I guess I should clarify: by project, I mean the project I'm using Django to build, not Django itself...
On Tuesday, June 25, 2013 10:19:52 AM UTC-7, Stryder Crown wrote: > > Awesome, thanks for the reply. Makes sense re: resource for template > (designers). I guess I see it also as a way to maybe better engineer some > self documenation for my PM and future devs that get brought onto the > project. I'll see what I can come up with. > > Stryder > > On Monday, June 24, 2013 4:01:09 PM UTC-7, Russell Keith-Magee wrote: >> >> >> On Tue, Jun 25, 2013 at 2:01 AM, Stryder Crown <[email protected]> wrote: >> >>> Couple questions maybe someone can elucidate... >>> >>> When Model docs are generated, why are only methods that take no >>> arguments (save self) documented? >>> >> >> Because admindocs isn't documenting the models. It's a resource for >> templates. It lists template tags, filters, and any model method that can >> be invoked by a template -- that is, methods that take no arguments. >> >> >>> Any work been done to allow 'extending' the doc via a plugin or method >>> load? I have some internal classes on my model that I'd like to appear in >>> the docs, but they'd need some custom wiring because of their own innate >>> wonkiness... >>> >>> When viewing the list of Models, (main model doc page) what about >>> extending it with the same 'list_display' feature that we do on the >>> AdminModels? Granted, it wouldn't have fields the same way, but it might be >>> handy to have additional columns of meta data to show using functions, or >>> even if I could just show the primary doc string/description itself, that'd >>> be kinda nice. >>> >> >> I'm not aware of any efforts to extend admindocs. However, details >> notwithstanding, it doesn't seem like a completely daft idea. Whether >> ModelAdmin is the right place to do that … I'm not convinced, but I >> couldn't hurt to see a more detailed proposal. >> >> Yours, >> Russ Magee %-) >> > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
