In theory, the index might be an adequate substitute for search. But not every property is listed. 'itemCreationPolicy', for example, isn't. I wonder how many others are missing, hope I don't find out when I really need it.
Even if it's only that the docs are transparent to search engines, so we can use Google, that might be something. But an incomplete index, unsearchable content, and no search field... well it's just not very usable. Search is essential. Thanks for listening. _______________________________________________________________________ Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca Author, Professional Flex 3 :: http://tinyurl.com/proflex3book Alex Harui wrote: > For your particular case, I think you could have used the index. > > The Adobe ASLR does have search. I wonder what it would take to implement > it. > > -Alex > > On 3/21/14 9:40 PM, "Joseph Balderson" <n...@joeflash.ca> wrote: > >> This may sound like a silly question, but how on earth do you search for >> anything in the Apache Docs, if you don't already know in which class it >> resides? >> >> The other day I wanted to know, out of curiosity, how many components >> implemented the itemCreationPolicy property, and I was unable to do a >> search to >> get an answer. >> >> Google 'itemCreationPolicy site:flex.apache.org/asdoc/' and you get 0 >> results. >> The docs themselves do not heave a search field like the old Adobe >> AS3/Flex docs >> have. >> >> This is a problem. I don't often use the search field in the AS3 >> reference, but >> when I do it's usually because I really need it. It is essential that the >> content in the Apache Flex docs also be searchable. >> >> Or am I missing something really simple here? >> >> >> -- >> _______________________________________________________________________ >> >> Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca >> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book > >
