Change the order of groups on dartdoc pages

[Hixie]

The order right now is a bit weird (especially that typedefs come so early on the library page).

Here are the suggested new orders:

• Top-level page: flutter, dart core, flutter_markdown, flutter_test, flutter_driver.
• Library pages: classes, constants, properties, functions, enums, typedefs, exceptions.
• Enum pages: constants, properties, methods, operators.
• Class pages: constructors, properties, methods, operators, static methods, constants.

cc @sethladd

[sethladd]

This list is approved. Go forth and make it awesome.

[sethladd]

cc @astashov if you're looking for one P2, this one is an easy one :)

[jcollins-g]

This has two parts influencing it: the script that constructs the "package" that dartdoc actually documents for flutter, and the dartdoc internal category sorting. Starting work on the latter, first.

[jcollins-g]

@Hixie / @sethladd : it would be easier to do this automatically with flutter_driver before flutter_markdown and flutter_test. Would that be acceptable? I'll have to add a flag to specify ordering otherwise.

[Hixie]

It's probably fine, but it's definitely suboptimal. We ideally want flutter_test (unit tests) above flutter_driver (integration tests, more complicated), and ideally want flutter_markdown (a flutter runtime package) before the test packages.

Might be worth just giving us explicit control (maybe default to the order on the command line, say), that way you never have to worry about it again. :-)

[jcollins-g]

Sounds good. I'll still improve the automatic categorizing but give you control on the command line to override it.

[Hixie]

Also any improvement is an improvement, we're happy to take things bit by bit if that's more tractable than going all the way to space in one step. :-)

[jcollins-g]

It's alright, this isn't nearly as painful as #1334 turned out to be :-)

[jcollins-g]

Static properties weren't mentioned under classes in the order above, so moving them to before static methods.

[jcollins-g]

Can't fix this without touching the code for #1225, so fixing that too.

[jcollins-g]

Done, cleaned up and has tests, but stuck behind #1368. Some examples below from Flutter.

Top level, with new --category-order flag set to:
"flutter,Dart Core,flutter_markdown,flutter_test,flutter_driver":

Library:

Class:

Enum:

[Hixie]

That is gorgeous.

[Hixie]

It looks like the order of groups on library, enum, and class pages hasn't changed. Should I file a separate bug to track those?

[jcollins-g]

This is fixed in head as screenshots indicate, but until #1390 lands to correct the many broken links from doc references introduced in #1368 it's not really usable yet.