And already fixed!
The fix is in
https://github.com/appcelerator/titanium_mobile/commit/80547393e763f38e344c33504ad80326a61f546f
and will make it into the upcomming GA releas of Titanium SDK 1.8.0.1 on
monday!
Best regards.
Dietrich.
Am 15.12.2011 16:10, schrieb Dietrich Streifert:
> Yes! I'
Am 15.12.2011 11:30, schrieb Stefan Andersson:
>Btw: what runtime do you use in android? Is it Rhino or V8?
Android v 2.2 and concomitant js
Yes but which runtime? Do you use SDK before 1.8? Then you use Rhino.
Starting with SDK 1.8 you have the choice between V8 and Rhino.
--
Yes! I've got now a reaction from Marshall Culpepper, member of the
Appcelerator core team:
http://developer.appcelerator.com/question/129475/v8-runtime-defines-objectprototypeextend-which-may-break-compatibility-to-javascript-framework#answer-225485
He opened an issue in the titanium jira:
htt
Very nice, Dietrich, you're stirring it all up :).
T.
On 12/15/2011 10:32 AM, Dietrich Streifert wrote:
> Am 14.12.2011 21:44, schrieb Dietrich Streifert:
>> Am 14.12.2011 17:44, schrieb thron7:
>>> Thanks, Dietrich, for digging into this so well. Could you open a bug
>>> for it and attach your f
Extending Object is still regarded as a sin of the general js community. This
opinion can be bypassed by an access pointer instead of "inheritance".
Stefan
--
10 Tips for Better
>Btw: what runtime do you use in android? Is it Rhino or V8?
Android v 2.2 and concomitant js
Stefan
--
10 Tips for Better Server Consolidation
Server virtualization is being dri
>How do you manage the *.js file loading in your app.js?
Titanium.include('view/Translation.js');
that is static and Titanium handles the code inside the package.
We have looked at dynamic as well but not tested enough to say anything clearly
about it.
>Have you intercepted the titanium buil
Am 14.12.2011 21:44, schrieb Dietrich Streifert:
> Am 14.12.2011 17:44, schrieb thron7:
>> Thanks, Dietrich, for digging into this so well. Could you open a bug
>> for it and attach your findings?! That would be great.
>>
>> Thanks,
>> T.
>>
> Done:
>
> http://bugzilla.qooxdoo.org/show_bug.cgi?id=5
Am 14.12.2011 17:44, schrieb thron7:
> Thanks, Dietrich, for digging into this so well. Could you open a bug
> for it and attach your findings?! That would be great.
>
> Thanks,
> T.
>
Done:
http://bugzilla.qooxdoo.org/show_bug.cgi?id=5951
-
Am 14.12.2011 17:44, schrieb thron7:
> Thanks, Dietrich, for digging into this so well. Could you open a bug
> for it and attach your findings?! That would be great.
>
> Thanks,
> T.
>
Will open the bug tomorrow.
Tests with standalone v8 on centos 6 (d8 respectively) show that
Object.prototype.ex
Thanks, Dietrich, for digging into this so well. Could you open a bug
for it and attach your findings?! That would be great.
Thanks,
T.
On 12/14/2011 03:27 PM, Dietrich Streifert wrote:
> Am 14.12.2011 15:16, schrieb Dietrich Streifert:
>> Back from my lunch break:
>>
>> I've startet a debugger
Am 14.12.2011 15:16, schrieb Dietrich Streifert:
> Back from my lunch break:
>
> I've startet a debugger session in Titanium Studio and set a
> breakpoint at line 3 of qx-oo-noopt.js which is the first instruction
> allowing to do so. Now I've been stepping through the code while
> evaluating "c
Am 14.12.2011 13:12, schrieb thron7:
>
> On 12/14/2011 12:51 PM, thron7 wrote:
>> On 12/14/2011 12:17 PM, Dietrich Streifert wrote:
>>> Meanwhile I "solved?!?!?" the exception by moving the declaration of the
>>> methods "extendClass" and "getKeys" up to qx.Bootstrap (starting on line
>>> 64) right
Am 14.12.2011 12:52, schrieb Stefan Andersson:
> We used a little different strategy by wrapping the GUI function calls
> of Titanium in qooxdoo mobile and don't see this problem.
>
> Stack trace, please!
>
> Stefan
Btw: what runtime do you use in android? Is it Rhino or V8?
---
On 12/14/2011 12:51 PM, thron7 wrote:
>
> On 12/14/2011 12:17 PM, Dietrich Streifert wrote:
>> Meanwhile I "solved?!?!?" the exception by moving the declaration of the
>> methods "extendClass" and "getKeys" up to qx.Bootstrap (starting on line
>> 64) right before method "define". Down at
>> qx.Bo
Am 14.12.2011 12:52, schrieb Stefan Andersson:
> We used a little different strategy by wrapping the GUI function calls
> of Titanium in qooxdoo mobile and don't see this problem.
Hi Stefan!
How do you manage the *.js file loading in your app.js?
Have you intercepted the titanium build process
We used a little different strategy by wrapping the GUI function calls of
Titanium in qooxdoo mobile and don't see this problem.
Stack trace, please!
Stefan
--
Cloud Computing -
On 12/14/2011 12:17 PM, Dietrich Streifert wrote:
> Meanwhile I "solved?!?!?" the exception by moving the declaration of the
> methods "extendClass" and "getKeys" up to qx.Bootstrap (starting on line
> 64) right before method "define". Down at
> qx.Bootstrap.define("qx.Bootstrap", I replaced the
Am 14.12.2011 11:48, schrieb thron7:
>> The next step is to "port" the iOS app to android (v 2.2+ ) which uses
>> the v8 javascript engine.
>>
>> The problem is that during load of the qx-oo.js (or qx-oo-noopt.js) I'm
>> getting an error "Object # has no method 'extendClass'" in
>> qx.Bootstrap.
On 12/14/2011 09:24 AM, Dietrich Streifert wrote:
> Hello Everybody,
>
> I've successfully build an iOS app using Appcelrator Titanium and qx-oo
> version 1.6 for business logic (oo features, properties, events mainly)
> which (hopefully) will be distributed through app store this week.
Wow, con
Hello Everybody,
I've successfully build an iOS app using Appcelrator Titanium and qx-oo
version 1.6 for business logic (oo features, properties, events mainly)
which (hopefully) will be distributed through app store this week.
The next step is to "port" the iOS app to android (v 2.2+ ) which u
21 matches
Mail list logo
