On Tue, Nov 26, 2013 at 12:59:44PM +0000, Ming, Bai wrote: > > XWalkCmdLineStrategy (maybe there is a better name): > > - A strategy class encapsulating cmd line parsing and showing a browser > > window or invoking an app (depending on cmd line parameters) > > - Owned by XWalkContentBrowserClient Hi,
> > - XWalkCmdLineStrategy will encapsulate the logic currently present at > > ApplicationSystem's HandleApplicationManagementCommands() and > > LaunchFromCommandLine() methods and also at > > part of XWalkBrowserMainParts::PreMainMessageLoopRun() logic. > > [Ming, Bai] Do we still need to support command line options for > each application/browser launching? I think after the shared > runtime process mode is ready, we need to remove the simple browser > mode, and merge the functionality to xwalk-launcher, like > xwalk-launcher --launch="http://ffda"; or anything like that. The > command line parsing will only happen once, when the daemon starts > up. That's a good point. At some point we will phase them out. Mikhail, instead of having one more abstraction, could you just call a function in ApplicationSystem to handle command line? Cheers, Caio _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
