#15516: Update the ticket life cycle diagram
-------------------------------------+-------------------------------------
Reporter: ramiro | Owner: tswicegood
Type: | Status: new
Cleanup/optimization | Component: Documentation
Milestone: | Severity: Normal
Version: SVN | Keywords:
Resolution: | Has patch: 0
Triage Stage: Accepted | Needs tests: 0
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Comment (by gabrielhurley):
I'll second the suggestion of SVG... as much as SVG can be difficult to
work with and has its own painful limitations I think it is sufficient for
our needs and is one of the few open formats that's continued to have
broad support.
Moreover, browser support is coming to a point where it would not be
unreasonable to directly embed SVG into the docs as opposed to converting
it to an image. This would require some minor hacks to support older
versions of IE, but the tools are readily available and easily bundled.
Choosing a standard (such as SVG) for images in the docs and making sure
we thoroughly support it would also go a long way towards making it easier
to add images elsewhere in the docs as well (as per Steve Holden's talk on
why the docs suck).
Lastly, SVG can actually be properly version-controlled since it's text-
based, which is a big plus.
--
Ticket URL: <https://code.djangoproject.com/ticket/15516#comment:7>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
