Today I started exporting my game into CocoonJS and soon realized that TweenLite from GreenSock simply doesn't work for some reason. Basically the code just stops running as soon as it encounters a TweenLite function - the error console stays silent.
Can someone recommend a good javascript tweening engine that is compatible with CocoonJS? Thanks
Personally I've tested and I use Tween.js by sole in GitHub at https://github.com/sole/tween.js/. There may be no better than TweenLite, but it still is fast and fluid (tested on iPhone 3GS and Android Samsung Galaxy S3 ...). In addition, Tween.js is licensed under the MIT, where you can put ads and in-app purchases in your apps free of charge. Unlike TweenLite which you have to pay a professional license ($ 50 / year).
Related
What's going to happen now that Huawei is releasing their new OS? If it blows up, and there's a good chance it will, there'd be a massive gap in access to a whole new platform. I've chosen the easy way out and I've been developing mobile apps for iOS and Android via React-Native. Will React-Native support HarmonyOS?
This question might be better directed towards the React Native Feature Requests page.
I haven't seen any mentions to add support for HarmonyOS at this stage, however the community could add support if there's demand. There's plenty of prior art around for alternative platforms.
If Facebook starts supporting HarmonyOS with its apps, then first-class support is much more likely.
I think we need to wait for HarmonyOS become more popular with
developer & user, currently (Dec 2020), Huawei only shares beta
testing for a limited partner of them after the HDC event, no more
technical docs available for HarmonyOS app developers at this time.
If it becomes more popular & attracts developers, maybe React-Native will support it, For more information, you can find at https://www.huaweicentral.com/harmonyos-hongmeng-os-everything-you-need-to-know/
I've just installed ios7 on my iPhone, however I have not yet downloaded xCode5, so I've been producing my archives using iOS6 SDK and using TestFlight to test them on my phone. When running my app on iOS7, I'm noticing a lot of bugs that I didn't see in iOS6 (some that are unpredictable and very difficult to fix). I've been avoiding downloading xCode7 because I'm not yet ready to make the commitment to the new UI elements, but I'm wondering if I did produce my app using the iOS7 SDK, is it possible some of these bugs could be eliminated?
This is a very broad question. iOS 7, despite its advanced beta count, is still very much a work in progress. There are bugs that should be reported to Apple that should not happen. But beyond that, there are changes in the internal API that influence how the app behaves. Apple has done its best to try and preserve SDK 6 apps as much as possible, but there is breaking API which can cause crashes. One example off the top of my head is the class cluster they are now using with ABPersonViewController. Subclassing that in iOS 6 works fine, but in iOS 7, even when compiled with SDK 6, causes a crash in most cases. These issues can be resolved even with Xcode 4.6 and SDK 6.
Compiling with SDK 7 may help you fix some issues, but it will come with a plethora of issues of its own. Depending on how complex your view hierarchy is, you may have to invest a considerable amount of effort to support the new API and functionality. You don't really have a choice, as this is the future, but you should be prepared for this, and arrange your schedule accordingly.
I often need simple personal apps on my phone and I'd like to make them. I know some programming (C++, Delphi, some Java, MATLAB, Visual Basic). I don't have any idea about where to start, what can I do, how the issue of "app signing" can impact on this.
One app should help to manage links between book pages, basically it has to handle a small database in which I can add books (title, ID) and linked pages (couples of numbers). The database must be obviously persistent.
The other app should let me program a number of time counters. I don't need persistence between app startups.
I tried Qt Creator, but let alone some problems about installation, it looks like it's made for S60 v5. I don't know where to start. I used to make small utilities for my computer in Delphi, which saved me much time; now that I have a small portable PC like the E5, it could be very useful to have, for example, a portable random number generator, or similar simple apps for personal use.
Someone please give me a kick-start!
Update: I've managed to make the timers application in J2ME, it took a week of investigation (1-2 hours a day)
I did software development for Symbian C++ for more then 6 years. I stopped it something like a year ago when Nokia declared that it is going to kill it. Symbian did not became never popular between application developers because it is EXTREMLY complicated to start developing on it. It will take long-long weeks, maybe months to get running something own for the first time. And that time maybe there will be no new Symbian devices sold... you better invest your time in something that has more future.
Qt is good, qt is MUCH easier to start with and the knowledge you gain you can use also for software development for desktop (Windows, OS-X, linux crossplatform) and other embedded (linux) devices. In one word it has some future.
Qt applications run also on 3.2 devices, just you will have to install the Qt runtime on your phone. You also don't have to use the latest SDK but 1.1.2, this has support for older platforms.
If you want to develop only for your own, you can create a "developer certificate" for free that you can use to sign your applications - they will install only on your phones (you have to specify the IMEI of the phone). You can find more info about signing at http://www.symbiansigned.com.
Take a look here: http://www.developer.nokia.com/Community/Wiki/Category:Symbian
There's a lot of information regarding development options available for S60.
I suggest you take a closer look at J2ME, reasons being:
J2ME is a mature & thriving language with a lot of documentation and examples available.
The midlets (apps) you produce can also be installed on S40 devices. S40 is currently the world's most widely used mobile phone platform.
I'm building a small app with Adobe AIR using HTML and JavaScript. When I view the app as a regular website (no matter in which browser), it's all perfectly fine. But when I view it as an AIR app (with the adl command or in a proper package), all the effects, mostly jQuery, make the website lag.
I do not use any fancy effects, it's just about image sliders. Any ideas where this is coming from?
Thanks!
PS: I know it's not because my PC is too slow; I recently bought new hardware for 700 EUR (~980 $; ~620 GBP) :)
I had the same problem.
It turned out, you MUST NOT use box-shadow -webkit-box-shadow or text-shadow css properties in your air app. It works fine in other browsers? but dramatically slowes down air performance.
That worked for me.
I'm working on a JavaScript AIR app at the moment that is running jQuery without a problem on very low spec PC, and is actually impressing me with how fast it is (knock on wood!). Adobe improved JavaScript performance recently, so if you haven't got the latest runtime (currently 2.7) then definitely grab that.
As for the jQuery itself, make sure you are using the minified versions of the jQuery libraries, and only include the ones that you absolutely need. It's always a good idea to compress images as much as you can, as moving big images around will obviously take more processing power.
You could also take a look at this article about performance tuning AIR apps, although it is focussed on Flex and AS development.
http://www.adobe.com/devnet/air/articles/air_performance.html
Good luck!
How to create a WAP website?
What software do I use?
Do I just need to use HTML coding or other type of language?
And after I created it, Can I view it on my own phone?
Do I need a server to let it run or I can just view it on my phone?
Can someone help please, its for my project.
Thanks alot.
What phones are you targeting? Any phone released in the last 3-5 years is able to view standard (X)HTML without issue - except for the fact that they mostly have very small screens.
Some phones do not support Javascript very well (but that is mostly changing, too) and most phones do not support Flash (yet - most newish phones except iPhone will probably support flash "soon", if not already).
The only other main difference is that most phones these days use a touch interface, rather than a traditional keyboard/mouse. That means you can't really do things like hover effects and so on.
But other than the smaller size, everything else is pretty minor.
I agree with the post above that unless you are targeting very old phones, there is probably very little point to working with WAP today - AFAIK the last official version was WAP 2.0 which was circa 2002.
WAP 2.0 used a streamlined version of XHTML. The best way to develop is to either navigate your phone to a standard HTTP server hosting your files - or download and use a simulator. I found the best practice was to develop the app until it worked on the simulator (which could often be directed to load local files) and then do final testing and tweaking with actual devices.