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. > 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? Phantom.js uses webkit as the rendering engine [1], much like an AIR app. We could theoretically write an AIR app that does a similar thing (although making it run in a X11-less server is almost impossible and AFAIK is probably against Adobe's EULA for AIR) Google probably has a phantom.js like setup which simply consumes the web application like a normal user and then indexes the generate HTML files locally. [1] http://phantomjs.org/supported-web-standards.html > > I haven't looked yet, but aren't these solved problems? > > -Alex > >
