First of all, thanks for finally rolling out a new release. I'm loving the completeness of the documentation so far. I mean, there's a change-log, a real actual up-to-date change-log! That makes me very happy indeed.
Having said that, I do have some small nitpicks that might be easy to fix and would make the new docs even better:
- First of all, ya'll need a 'beer me' button so I can donate beer to anyone who took on the probably mind-numbingly boring task of updating the change-logs.
- Next, that baby blue is supernova bright! It kinda hurts the eyes and I'm having real trouble skimming through the lists on the Namespaces and Kinds pages as a result. If the blue color could be darkened some this would greatly improve legibility.
- Third, there is a toggler to show/hide private items. However, when the private items are shown, they are not visually distinguished from the public ones. It'd be nice if they could be visually different either by having another color, or by having a label, something like that.
- Finally, there change-logs are quite long and complicated. This is of course a good thing, because it means you improved many things and documented all of them. However it'd be really cool if there was a label or some other visual indicator to distinguish breaking changes from non-breaking changes.
Other than that, great work! I'm looking forward to making some room on our road-map to upgrade to v2.5.x
0 ·
Comments
UiComponent.resized()
changed toUiComponent.resize()
Didn't see it in the change log, but it was a function i used quite a bit
One thing I just ran across: enyo.Application is a type of enyo.ViewController that encapsulates a collection of ERROR: INVALID LINK FOR "
enyo.FloatingLayer
, for instance), rather than just their methods. It's those kinds that are not visually distinct.