Closed rjrudin closed 7 years ago
I suggest using angular-translate for the human-friendly labels. It also allows applying different ui-languages easily. Should be default part of slush I think.
Re nested structures: I think it would make sense to walk across nested structures too, and search for values on any depth. wrapping properties/elements could be shown as headings between the key/value pairs. Otherwise this mechanism would only work for simplest XML and JSON, which would be a bit pity..
how does this look? http://marianoguerra.github.io/json.human.js/
Both of those look good. Is it worth adding one of them to the default slush UI, or maybe just a Wiki page providing references to these?
Bit of a techy look. I have done something that looks more natural on a page, did that with a recursive angular template. Wasn't too complex actually.
Downside: could we come up with something that looks (pretty much) the same for JSON and XML, provided we are talking about data-centric XML..
The new map theme (currently going through latest stages in ui-themes branch) has an infoWindow that was not showing our sample data very nicely. So I played around a little, and came up with this relatively simple recursive template:
Wondering if that could be a nice default for the details page..
I took a bunch of ideas from several projects, included the map details code, and wrapped that in a new reusable component: https://grtjn.github.io/view-file-ng/#/
Not fully finished yet, but working well enough to be published..
We're adding view-file-ng together with cards theme..
Fixed in cards branch..
As a user of a slush-generated app I want to view HTML keys/values on the detail page in my slush-generated app So that I have a reasonable human-friendly detail page, preventing stakeholders from immediately saying, "Well the users aren't going to want to see XML or JSON", as well as something I can further customize