On 12/16/16, 11:28 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:
>On Fri, Dec 16, 2016 at 9:45 PM, Alex Harui <aha...@adobe.com> wrote: > >> >> >> On 12/16/16, 7:05 PM, "omup...@gmail.com on behalf of OmPrakash >>Muppirala" >> <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote: >> >> >On Dec 16, 2016 3:15 PM, "Alex Harui" <aha...@adobe.com> wrote: >> > >> >Or could our framework dump out the resulting DOM and generate the >>static >> >HTML that way? >> > >> > >> >You are probably the only person who could build and maintain this :-) >> >I would say, XSLT sounds easier than this. >> > >> >> Maybe I'm not understanding something, but IMO, XSLT is an alternative >>for >> ASDoc, but isn't an alternative for all other FlexJS applications. > > >XSLT is a tool/language to modify the generated AsDoc into HTML. As I >said >earlier, we could also build the docs as an interactive web app. One does >not have to necessarily replace another. > Maybe I'm too idealistic, but IMO, since we are project for RIAs, it bugs me every time our web presence displays data without using Flex or FlexJS. That's why Peter is trying to build out the team page as a FlexJS app. So my line of thinking is: folks have limited time to contribute, so spending that limited resource on static site generation of data is a bit contradictory. We should spend that limited time on making sure that FlexJS apps don't have limitations that make even us choose not to use our own product. > >> Is the >> only way FlexJS apps can work with search engines going to be to use >> PhantomJS or can we and should make something better? >> >> Thinking about static generation from a FlexJS app, it seems to be there >> are several pieces: >> 1) when is all data loaded and JS run so we can start the dump? >> 2) the dump is a simple DOM tree walk >> 3) how do we save the dump? >> > >I don't understand your proposal. We have javascript, css and json as >separate entities. You need to have a (headless) browser running the code >and consuming the json to generate the HTML. Are you proposing that a DOM >is created without a browser? Sort of. This is a totally new idea to me, so I haven't spent too much time thinking about it, but last night I had the idea of using AIR. Maybe we can build an AIR app that loads the output from FlexJS, and basically crawls it, but saves out the DOM tree as HTML. Of course, I could just be dreaming... Thoughts? -Alex
