PDA

View Full Version : New Sencha 2.2 : new features ?



huberte
10 Jan 2013, 2:01 PM
Hi,

Since Android is now the first mobile OS, I would like to know if :

1. the native android back button will be implemented

2. The native openurl (like in ios) will be implemented (for native packaging)

3. The LVL licence protection for Android, since google will let the other protection down.

thanks

mitchellsimoens
12 Jan 2013, 9:40 AM
It has more activations but stats that you get online aren't always 100% true or the most devices you will see using your app.

Will these features be in 2.2.0, not everything will. Do we want to support them, yes.

ingo.hefti
13 Jan 2013, 5:40 AM
+1 (especially #1 and #2! Pleaaaaaaase!!)

andrewx
14 Jan 2013, 6:17 AM
It has more activations but stats that you get online aren't always 100% true or the most devices you will see using your app.

Will these features be in 2.2.0, not everything will. Do we want to support them, yes.

I think that's a bit of BS - some of us target Android because we have a lot more users on that platform than iOS (and we have the logs to back it up).

huberte
24 Jan 2013, 4:03 PM
If I may ask, I don't quite understand the plan for the next version of sencha...

Android was the first os in US (worldwide too) at the end of 2012, you have plenty of articles on the web about this fact.

Windows 8 could rapidly grow, but its performance in US market is underwhelming (ok in europe they maybe have 5 or 10 %)

If you look at some specific market (european countries) you see that Android is the most used os, and sometimes (like in France) by a large factor (Android 60 % , iOS : 25 %)

My question is : why don't you focusing your development on the top used OS, particularly on the top lack of features which are draining lot of questions on this forum (see 1 and 2 above)

I thought it would be logical, first fill the gap, then developing on other platform, then the world :)...

But again I could miss some strategical points...

huberte
2 Mar 2013, 9:07 PM
Any news on this, should we create a poll ? and then could you make it sticky ?

rgporter
6 Mar 2013, 7:43 AM
It's not that simple. It depends on what you mean by "first os". The stats are all over the place, in such a way that both Android and iOS are equally important. If you're developing a web-based app, iOS is the most important as web traffic is higher for iOS than Android. This is because a lot of Androids that are sold have no data plan, or the user is just getting a cheap phone and doesn't care that it has a web browser and never uses it.

Sales for Androids are higher, meaning there are more out there. But if people use them differently (and they do) then you have to pay attention to that.

Re: Android back button - it already works fine, I'm not sure why you're asking about that. Use URI schemes/routing in your app and the back button will work.



If I may ask, I don't quite understand the plan for the next version of sencha...

Android was the first os in US (worldwide too) at the end of 2012, you have plenty of articles on the web about this fact.

Windows 8 could rapidly grow, but its performance in US market is underwhelming (ok in europe they maybe have 5 or 10 %)

If you look at some specific market (european countries) you see that Android is the most used os, and sometimes (like in France) by a large factor (Android 60 % , iOS : 25 %)

My question is : why don't you focusing your development on the top used OS, particularly on the top lack of features which are draining lot of questions on this forum (see 1 and 2 above)

I thought it would be logical, first fill the gap, then developing on other platform, then the world :)...

But again I could miss some strategical points...

ingo.hefti
6 Mar 2013, 7:48 AM
Re: Android back button - it already works fine, I'm not sure why you're asking about that. Use URI schemes/routing in your app and the back button will work.
Can you show us some sample code how you did that for a native app?

huberte
6 Mar 2013, 8:20 AM
It's not that simple. It depends on what you mean by "first os". The stats are all over the place, in such a way that both Android and iOS are equally important. If you're developing a web-based app, iOS is the most important as web traffic is higher for iOS than Android. This is because a lot of Androids that are sold have no data plan, or the user is just getting a cheap phone and doesn't care that it has a web browser and never uses it.

Sales for Androids are higher, meaning there are more out there. But if people use them differently (and they do) then you have to pay attention to that.

Interesting, I never thought about performance issue or usage. I think most of the android phone are under 3.X, and with low performance not usable for sencha... :-?


Re: Android back button - it already works fine, I'm not sure why you're asking about that. Use URI schemes/routing in your app and the back button will work.

Great ! A link ? A sample code ? /:)

NineBerry
7 Mar 2013, 2:04 AM
Back Button will work if you execute your Sencha app in a web browser, but it will not work in a native packaged app.

huberte
7 Mar 2013, 2:34 AM
Of course, thanks a lot for this news.. (:|

rgporter mentioned something else, let him show how he does that ^_^

NineBerry
7 Mar 2013, 2:42 AM
I think, rgporter was probably not aware, we were talking about native packaged apps.

huberte
9 Mar 2013, 12:53 PM
He should have red the thread, then... :(

composer47
19 Mar 2013, 12:13 PM
If you package your Sencha Touch app with PhoneGap, you can easily bind the Android back button to your own javascript function like this:



document.addEventListener("backbutton", Ext.bind(onBackKeyDown, this), false); // add back button listener


From here, you implement that function onBackKeyDown, which can get a reference to your Sencha Touch application, and in turn get access to its state. This means, whenever you hit the back, that function needs to determine what view is shown to the user so you can take appropriate action. For our app, its pretty simple:

Login View = exit app on back
Main View (NavigationView) = back button pops a view, if there is only 1 view, then it exits app

It's actually pretty easily to implement. I can't speak for apps packaged with Sencha Native Packager, as we use PhoneGap.

Cheers,
Scott

ingo.hefti
19 Mar 2013, 11:20 PM
If you package your Sencha Touch app with PhoneGap, you can easily bind the Android back button to your own javascript function....
Thank you for sharing! But that is the catch: you still need PhoneGap to do that. But this thread is about new features for ST2.2 (=no PhoneGap)...


I can't speak for apps packaged with Sencha Native Packager, as we use PhoneGap.
As I said: some of the most basic functions for a native app are not possible with plain ST... :(

venkatesh.R
20 Mar 2013, 5:00 AM
@Mitchell,

I would like to know about whether sencha touch 2.2 supports Auto Complete(Text Field) Component.
If it comes with new ST 2.2 , i would be very happy :-?


Thanks,

composer47
20 Mar 2013, 5:43 AM
Thank you for sharing! But that is the catch: you still need PhoneGap to do that. But this thread is about new features for ST2.2 (=no PhoneGap)...


As I said: some of the most basic functions for a native app are not possible with plain ST... :(

Actually this thread is not about new features of ST 2.2 - this thread is about someone's wishlist for Sencha Touch and Android. The title of the thread is misleading. As Mitchell stated from the 2nd post, there are a lot of things they want to support, but I doubt you will see them 2.2. If you've been following what 2.2 is mainly about - it's all about setting up the framework to support different browsers besides webkit. This involves going through all of the styles and breaking them out into a base stylesheet and then implement specific browser stylesheets that are loaded by the microloader. This is a great direction for the framework.

Personally, I would like to see the Sencha team focus on improving their framework (and especially Sencha Cmd- its horrible), and not focusing on the native aspect, as PhoneGap already implements most of the native hooks you'll want to do. You can create a wishlist all you want, but my original post was telling you that there are ways to accomplish what you want today, and even tools to help (http://www.sencha.com/forum/showthread.php?251684-Sencha-Cordova-Builder-Automated-Builds-for-PhoneGap-Projects) you with it.

huberte
20 Mar 2013, 7:49 PM
The title of the thread is misleading.

Misleading ? did you read the first post ? Is my english so bad ? there is no possible confusion, imho...


Personally, I would like to see the Sencha team focus on improving their framework (and especially Sencha Cmd- its horrible), and not focusing on the native aspect, as PhoneGap already implements most of the native hooks you'll want to do. You can create a wishlist all you want, but my original post was telling you that there are ways to accomplish what you want today, and even tools to help (http://www.sencha.com/forum/showthread.php?251684-Sencha-Cordova-Builder-Automated-Builds-for-PhoneGap-Projects) you with it.

Sencha cmd is quite good. i choose sencha at the first place because it's (almost) the only framework who can pack native app.

I don't quite understand what you would like in sencha 2.2.... What I could say is that I can build nice, responsive app, quite fast, but the lack of android hardware implementation is a pain on native app.

By the way, do you have application in production with cordova on ios or android market ? I'd like to see them, because (and I know those tools) when I tried to build them, the app speed has declined significantly. I red a lot about that, and the fact that you add a ton of js and calls when you use phonegap....

Again, if you make a poll, I don't think your wishes will be the same as many other users asking the same feature on this forum...

EDIT : A great tool on ST2 and ST2 : superant from Ross, https://vimeo.com/47215405

ingo.hefti
24 Mar 2013, 7:33 AM
Actually this thread is not about new features of ST 2.2 - this thread is about someone's wishlist for Sencha Touch and Android.
Ok, ok. You are quite right on the subject. But still there a lot of questions in the forums about missing back button support for native Android and stuff that work on one platform but wasn't implemented (yet?) on another...