On 2/28/17, 11:51 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>Hi, > >>> Having a document somewhere listing what is implement and what isn’t >>> would be useful I think rather than having to hunt through examples / >>> mailing list etc etc. >> >> There is ASDoc [1][2]. > >ASDocs are the API docs so I’m not 100% sure this would be the best place >to document this or where documentation unreleased to a class would go. There's also the beginnings of Tour De FlexJS. Volunteers are needed there as well. If you have a better idea of where to document it, go for it. IMO, we want ASDoc and Tour to have some search feature so you could type in "Download" and see some offerings. IMO, if a class does downloading, it should mention that, so it wouldn't be unrelated to the class. Also, if you want to package up your code into a component with the name Download in it, that might help as well. FlexJS is still a beta. We need more contributors, but those contributors will have to be pioneers for the short term, willing to work on the bleeding edge. In US history, the first pioneers heading west from the more developed eastern US followed roads to St Louis where they then had to cross wide fields of grasslands with almost no trail features to navigate by. Later, other pioneers could follow the wagon wheel ruts of the first pioneers and read accounts from those prior travelers. Each year, it got a little easier. Only now are there paved roads, highway signs, Trip Advisor. Documentation will get better over time. Faster if more volunteers pitch in. Flex had 8 years with a lot more people to pave the roads, make the signs, etc just like the eastern US in the early 1800's. We are blazing a new trail west from there into JS land. We've only had about 5 years with many fewer people. My 2 cents, -Alex
