Will pull2refresh and listpaging be included in this version

I am really missing this ..

Thanks in advance

I just signed up for your newsletter. Is there a way I can get the archive of that “detailed walkthrough of porting an app from ST1 to ST2?”

ST1 need more time to start APP -> ST2 is more faster and better

ST1 is more faster that ST2

Is st2 better ?

Thanks for the update.  I understand the tendency to “shy away” from dates.  As a Director of Development I, too, don’t like to give dates especially without LOE’s or worse, specs.  But I have to assume when a preview of a pending release is announced that the LOE’s and specs are in place which means a date can be calculated.  I push back all the time when I don’t know but when I do know, I announce it (internally and externally) with a road map and a timeline.  I cannot imagine that your processes are any different.

Turning to “what other people have written” - that is a good marketing confirmation statement; however, for someone new to this and having to make a decision about future products, I cannot in good conscience make any decision based on what I now know as an older version and what I don’t know, what a new version may entail.  Since I don’t know your track record that isn’t important to me - a road map is - our customers expect that from us and we expect it in turn whether it is Microsoft, CodeJock, or whomever.  Think of it this way - I don’t want to schedule resource burn rates based on something that I know will change, especially when I have limited resources for planning, scheduling, and commitments.  In short, our customers expect that from us and we, as your customers (or potential), expect that in turn so we can bubble up our release dates, expectations, and road maps.

Again, if you want assistance in this area I will be glad to help.

Steve

Thanks for the update. The question below relates to a bug in the current build (as demo’ed in the show and tell of this blog.). Maybe someone from your team can verify if it is a known issue?

>> The SDK for Mac crashes on install due to some 3rd party dependencies (at post install step) on Mac OS X 10.7.2..

We’ve already shipped PR2 of Sencha Touch, and in today’s newsletter (which you should sign up for) there’s a detailed walkthrough of porting an app from ST1 to ST2.

We’re shying away from giving specific dates for betas or releases, but as guidance, Ext JS 4 took about 3 months from first preview to release and Sencha Touch 1 took five months from first beta to release. Other projects keep their releases in alpha and beta status for over a year before release - we don’t do that and it’s not our track record.

My team just started to talk about jquery because we don’t have any idea when the version two is going to be release. We felt that sencha is not supporting us anymore… that is really sad. We see more roadmap in opensource projects than here… it is really sad!

I am trying to hold the next version of my mobile app just because I want to upgrade to ST2, but I think maybe it is time to move forward and really look other options… I don’t think there is other framework better then ST2, but the way things are going it is better to have other options…

My team just started to talk about jquery because we don’t have any idea when the version two is going to be release. We felt that sencha is not supporting us anymore… that is really sad. We see more roadmap in opensource projects than here… it is really sad!

I am trying to hold the next version of my mobile app just because I want to upgrade to ST2, but I think maybe it is time to move forward and really look other options… I don’t think there is other framework better then ST2, but the way things are going it is better to have other options…

“I’m glad there’s a v2 that addresses at least some of this, but without some guidance as to what the rollout schedule is, it’s impossible to make a decision on whether or not to abandon the v1 code and start investing time in ST2, since a lot of code will need to be re-written. Can Sencha PLEASE at least sketch out a roadmap?”

I’m glad there’s a v2 that addresses at least some of this, but without some guidance as to what the rollout schedule is, it’s impossible to make a decision on whether or not to abandon the v1 code and start investing time in ST2, since a lot of code will need to be re-written. Can Sencha PLEASE at least sketch out a roadmap?

Finally - why is there all this focus on native packaging, when there are several other, much more mature projects out there to do that and there are so many basic problems with the Sencha Touch platform itself?

Perf is feeling great in this version! There’s some important features missing, which necessitated some javascript hackery, but otherwise, I’m really looking forward to the next release

It will be great to have some answers on several questions. Does it have sense to begin a new project using Sencha Touch 2.0 PR2? Is it possible to use Sencha Touch 2.0 PR2 using MVC pattern? It’s very important to know because in the other case I will try with Sencha Touch 1.1.1.

I love the new API document!

But I test the new 2.0 example on my Android (Samsung ST5570),
I don’t see any performance on my machine,
is my phone’s hardware too slow ?

I am wondering if the Ext.regApplication” is part of the preview version?
Cannot find this function anywhere.

kind regards.

Thanks

If we have access to the internal SQLite database in iOS with Sencha Touch 2?

I will tell you as soon as I’m ready.

But what about the LokalTreeStore? Is it possible to make a local store for TreeStore?

@phil you’re referring to the Getting Started guide for Touch 2? Those links are hard coded in the guide, seems unlikely that you’d see that error for that reason…

it looks like the version 1.xx

Absolutely…...

@Mike will probably be week after next but no guarantees

Malky

Any information as to when the next DP drops?

The only stumbling block is that you will need to create a touch keyboard if you want to enter data.
I’ve created my own by extending Ext.Sheet, It behaves like any mobile browser keyboard, popping up
whenever a text field is entered into. I’ll have to stick it up on github soon.

You don’t need to worry about all the performance issues you see talked about both here on the forums and elsewhere, in my experience. Tweet me @mwrf if you have any questions.

@Claudio we’re tentatively expecting history to come back in either the next release or the one immediately after it

@Jack thanks, docs have been a high priority for us (we’re not done yet though!)

Really like the new features but if I’m honest it took me a LONG time to wrap my head around how to lay out the application. The automatic getter generation threw me.

To save others the trouble I put a simple MVC app-scaffold together on github using ExtJS4.0 MVC as a reference. Fork it here:

https://github.com/FrancisShanahan/SenchaTouch2MVCHelloworld

Again, nice work.
-fs

I agree, documentation is quite well. I was having some issues at first but documentation got me through without having to nag support or my nerdy friends.

But the nestedlist example can’t not show the lists, it’s all empty.

It’s seems the 2.0 version have good performance enhancement on Android, I want to try this preview version on my production as soon as possible.

Can you give me some advice to try new nestedlist ?

@Others who are looking at upgrading - The new interfaces have a changed a bit, and the Docs and examples are still being filled in.  If your processes are like ours - you’ll likely want to put this in a future release schedule, rather than immediate change.  It is cleaner and faster though - awesome job team Sencha.

Well, I already have two different provisioning for my Sencha Touch app: one for me, and one for the company I’m building for.  So, I brought over my www folder from phonegap, and wrote a quick configuration file.  When I run “sencha package config.json”, I get that error.  The problem seems to be that it doesn’t know whether to use my certificate or the company’s certificate.  I’d like to help it out (use my certificate now, and switch to company’s later).

@Rob are you referring to the provisioning part of the process, before the actual packaging?

I see the entire library (compressed) grew a couple hundred K. What’s included in the 93K sencha-touch.js lib?

Also, I’m not sure how to properly fill in certificateAlias for iOS as there’s no example.

However forms are still broken and it’s a deal breaker. When you try to enter something into the Name field in the Forms example the second edit field appears, partially overlaying the first one. Tested on Android 2.3.3.

Keep up the great work, Sencha. I am a huge fan and hope to have a handful of Sencha Touch 2.0 apps by the end of the year.

Am i doing something wrong or is this a bug?

And I have another question..
if sencha touch2 will be released some day. 
Do Sencha Touch1 live also… and update new version…  1.2.. 1.3… 1.4 ...?? or Died??

this is a great news!

@Zoltan definitely

Great work! fantastic as always!

Ext.applyIf(Ext.fx.Manager, Ext.util.Observable.prototype);

Ext.util.Observable is undefined.

@Michael thanks :D More to follow on Ext JS 4/ST2 convergence (it’s non trivial…)

@lee native packaging for Android is already supported

@Eric conference is in 2 weeks, videos will take longer. We’ll put something up in the meantime to make life easier. Compatibility is explicitly not included in this preview though

@mwrf yes the native packager creates Android build, we just accidentally clipped that out of the guide. We’ll push an update shortly

@Christian more theme options are on the way

@David windows phone has such a tiny share that we’re concentrating on the bigger players first. However, we have been removing webkit-specific stuff where possible to make supporting platforms like windows phone easier to add

What about Windows Phone support ?
Is there an official platform support doc ? Would be great to see a matrix like the one from JQuery Mobile guys

I don’t see any mention of the packager working with android or blackberry.
Is this expected to be available closer to full release?

Also, Is there any example of how Native API’s will be exposed to us?

Can you tell anything about SCSS changes? Did the structure/variables change very much?

Thanks!

@eliss we de-emphasized gaining good compatibility for this preview release as not everything is finalized yet. As well as rounding that out (we are able to do a full diff between 1.1 API and 2.0 API to verify) we’ll be providing a migration guide once we hit that milestone

I tried dropping this in straight up, and got a regModel error, but I’m assuming there will be some sort of v1 to v2 migration document

can’t wait for the final release

I’m hoping that the documentation in this version will get me enthusiastic again.
I don’t mind working hard to learn something new but I need the appropriate documentation to do that.

Experienced developers forget that even the basics is not obvious when you start something new.

I know its not a final version but I should be able to tell quickly if I can wrap my mind around it.

Good luck to both of us.

Would appreciate a feedback comment.