Hi there,

Could you create a Google Document where you describe your exact plan in
details and then share it here?

Thanks in advance,
Kenneth

On Thu, Apr 23, 2015 at 7:44 PM Sam Nazi <snazi.andr...@gmail.com> wrote:

> As indicated in our Issue
> <https://confluence.ntent.com/display/MOBILE/Crosswalk+Development+Plan#CrosswalkDevelopmentPlan-anchor_issue>,
> we need to be able to mix Java UI with Web content.  To that end, we
> propose taking all of the good work that XWalkView does and break it into
> several smaller components that each perform a separate task.
>
> Additionally, our solution aims to address XWALK-3545
> <https://crosswalk-project.org/jira/browse/XWALK-3545>
> <https://crosswalk-project.org/jira/browse/XWALK-3545>, XWALK-3971
> <https://crosswalk-project.org/jira/browse/XWALK-3971>, and XWALK-3888
> <https://crosswalk-project.org/jira/browse/XWALK-3888> and probably
> others as we get deeper into the code.
>
> Affected Component: Crosswalk Project for Android
> <https://crosswalk-project.org/jira/browse/XWALK/component/10022/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel>
>
> Related Feature: XWALK-4002
> <https://crosswalk-project.org/jira/browse/XWALK-4002>
>
> Target Release: Crosswalk 15
>
> Implementation Details:
>
> We see three general areas of work to be done:
>
>    1. A ContentContainer object that represents a series of screens.
>    There can be any number of ContentContainers in the application, and each
>    can have any number of Content that can be rendered into a View.
>    2. We should create a singleton whose job is to manage global state.
>    This includes initialization, storing/loading serialized ContentContainers,
>    changing global settings, etc.
>    3. A View object that strips out the majority of the web- and
>    content-based features from XWalkView and instead ONLY renders the web
>    content.
>       1. We should also have an interface that represents that the
>       implementing class is capable of providing the UI for a particular
>       Content.  This way, we clearly define which Views can render Content.
>
> _______________________________________________
> Crosswalk-dev mailing list
> Crosswalk-dev@lists.crosswalk-project.org
> https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
>
_______________________________________________
Crosswalk-dev mailing list
Crosswalk-dev@lists.crosswalk-project.org
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev

Reply via email to