Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-18469] Android: Convert HAL to connect with V8

GitHub Issuen/a
TypeNew Feature
PriorityLow
StatusOpen
ResolutionUnresolved
Affected Version/sn/a
Fix Version/sn/a
ComponentsAndroid
Labelsn/a
ReporterIngo Muschenetz
AssigneeUnknown
Created2015-01-29T21:36:58.000+0000
Updated2018-02-28T19:54:55.000+0000

Description

Currently HAL is a C++ <-> JavaScriptCore bridge. We need to convert this to connect to V8.

Comments

  1. Andrew McElroy 2015-03-21

    why do this? Didn't Appc already port JSC to Android or was that approach completely abandoned? https://github.com/appcelerator/hyperloop/wiki/Shrinking-JavaScriptCore
  2. Ingo Muschenetz 2015-03-24

    [~sophrinix] Thanks for reminding me of this comment. The utility of this is to make it easier to use HAL in ti.current for modules for Android.
  3. me@gmail.com 2015-04-07

    @ingo I am not sure the reason for making that call, but I know personally I would rather see effort directed to just getting Ti.Next out the door vs Ti.Next type features in Ti.Current. Just my vote... not that I get one :)
  4. Ingo Muschenetz 2015-04-08

    [~mapperson] One of the major requests by customers is for Ti.Current and Ti.Next is to use native APIs directly in JavaScript. I see this as part of that effort, and I don't believe detracts from the overall goals.
  5. me@gmail.com 2015-04-08

    I 100% want that in Ti.Next. Why Ti.Current though? I mean it would be nice, but at the expense of a delay to getting Ti.Next out the door? To me this seems like a lot of effort to add a feature to Ti.Current, what will (hopefully soon?) be a legacy codebase. Am I just over estimating the effort needed to do this?
  6. Ingo Muschenetz 2015-04-08

    I can't commit to a definite level-of-effort here yet without a bit more investigation, however I do recognize your concerns and will keep them in mind.
  7. me@gmail.com 2015-04-08

    Is the plan to support BOTH JSCore AND V8 or just V8 on android?
  8. Ingo Muschenetz 2015-04-08

    It depends on several factors so I can't say for sure. The long-term preference is a single JS engine across all platforms, but again, depending on effort, there may be strong rationale for supporting multiple version in the interim.
  9. me@gmail.com 2015-04-08

    I know the Ti.Forward effort is happy to maintain or help maintain the JSCore version... for what that is worth.

JSON Source