Not me, this need some C++/C-guys to work this out. I don't speak C any
longer.🐆

On Sun, Mar 12, 2017 at 7:10 PM, Adam Feng <[email protected]> wrote:

> Seems to be amazing. @sospartan do you have any plan to do this? Or
> anyone volunteer?
>
> On 2017年3月11日 +0800 AM1:03, 大诗胸 <[email protected]>, wrote:
> > The answer is yes. We can access java native object in ndk, and ndk can
> > access V8 javascript object. It's a lot of work to convert to each other.
> > After all, it's doable.
> >
> > On Fri, Mar 10, 2017 at 7:58 PM, Adam Feng <[email protected]> wrote:
> >
> > > Actually It’s possible for iOS, JavascriptCore has mechanism that
> support
> > > to export a “class” or an “object” to Javascript environment, but maybe
> > > it’s difficult for Android,is there any way to do that? I’d be wistful
> to
> > > see some programs working on that 😆
> > >
> > > On 2017年3月10日 +0800 PM7:47, 大诗胸 <[email protected]>, wrote:
> > > > How about remove this whole 'JSON parsing' thing. As far as I seen,
> It's
> > > > doable.
> > > >
> > > > On Fri, Mar 10, 2017 at 5:35 PM, Adam Feng <[email protected]>
> wrote:
> > > >
> > > > > Maybe it’s a good idea, mixing up all the dom APIs into
> `callNative`
> > > > > always takes extra time to do JSON parsing.
> > > > >
> > > > > On 2017年3月10日 +0800 PM3:36, 大诗胸 <[email protected]>, wrote:
> > > > > > Can you explain the reason why API change will cause performance
> > > > > > improvement?
> > > > > >
> > > > > > On Fri, Mar 10, 2017 at 2:26 PM, Hanks Zhang <
> [email protected]
> > > > > wrote:
> > > > > >
> > > > > > > As we discussed before, we should support all top-level DOM
> > > operation
> > > > > APIs
> > > > > > > directly to improve the performance. I have already achieved
> it in
> > > Weex
> > > > > > > runtime, include the following methods:
> > > > > > >
> > > > > > > Format: TAKS -> METHOD
> > > > > > >
> > > > > > > * createBody -> callCreateBody
> > > > > > > * addElement -> callAddElement
> > > > > > > * removeElement -> callRemoveElement
> > > > > > > * moveElement -> callMoveElement
> > > > > > > * updateAttrs -> callUpdateAttrs
> > > > > > > * updateStyle -> callUpdateStyle
> > > > > > > * addEvent -> callAddEvent
> > > > > > > * removeEvent -> callRemoveEvent
> > > > > > >
> > > > > > > Our legacy js framework (known as .we) already support this
> > > feature.
> > > > > > > *However,
> > > > > > > the Vue 2.0 should also support the corresponding feature as
> well.*
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > sospartan
> > > > > > Phone:13588488290
> > > > > > HangZhou
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > sospartan
> > > > Phone:13588488290
> > > > HangZhou
> > >
> >
> >
> >
> > --
> > sospartan
> > Phone:13588488290
> > HangZhou
>



-- 
sospartan
Phone:13588488290
HangZhou

Reply via email to