OS: Kubuntu 10.10
Webbrowser: FF 3.6.13

Regards.

I might be a bit much to require people to buy an Ext license if they only want to use charting.

Although we haven’t put it into the preview release yet, we already have most of the work done to support full keyboard navigation for Ext 4 doing exactly the thing you are describing. Expect to see it land soon into one of the next beta releases.

Ext.define(‘Ext.Component’, {

  /* Begin Definitions */

  alias: [‘widget.component’, ‘widget.box’],

  extend: ‘Ext.AbstractComponent’,

  uses: [
      ‘Ext.Layer’,
      ‘Ext.resizer.Resizer’,
      ‘Ext.util.ComponentDragger’,
      ‘Ext.fx.Anim’,
      ‘Ext.state.Manager’,
      ‘Ext.util.DelayedTask’
  ],

Only edit/combo boxes and buttons have correct focus feedbacks, but this is the default behaviour for HTML forms. Speaking of complex, non-HTML widgets like tabs, grids and trees, how can the user find out where the focus is at a given time?
Standard navigation keys like TAB, SHIFT+TAB should always switch between widgets and sublayouts, not between items/rows inside a single widget.

At this time, Ext JS framework looks very mouse-oriented and therefore cannot compete with mature desktop widget sets.
Should I expect improvement in focus handling and keyboard navigation?

Just as a first feedback concerning the API docs: Currently, on the API documenation’s index page, the tree on the left shows the same icon for all ExtJS 4 classes. This is a step backwards compared to 3.x and even 2.x where “visual” classes could be distinguished from “non-visual” classes instantly because they had a different icon (the green puzzle piece icon).

I’m with you on sleep loss—I forced myself to stop working and do something else to settle my mind: 22hrs today.

I’m very excited about Ext JS 4—I’ve looked over a lot of the code in the last 22hrs and while there remains work (as the code comments state, too), it’s quite well done.

Best of wishes to the whole team!

Hope people understand the sarcastic undertone in your post

I think part of the problem was that our whole dev team was sleeping right after we released because most of us hadn’t slept more then 15 hours in the last week. This caused us to be not very responsive the first hours after we released. I understand people’s concern with some functionality not being in a stable state yet, but like you said, thats why we call this a preview release. We are confident we will be able to get the framework in the best state it has ever been in and hope that till then all of you will become just as excited about the new features and API’s as we internally are by testing and using our preview and beta releases.

I’d say you made 1 glaring mistake though: Way too many people on here are looking at the DEVELOPER preview who must not be developers—maybe 100em font would make it easier for them?  Perhaps adding in RTFM and RTFC (last letter meaning “Code”)?

Documentation wrong on the Ext.data.Model.load and that means it’s the end of the world as we know it?  Or, maybe a developer might read a little further down than the descriptive summary for the example which has the event handler receiving 2 parameters, not 1 and ask, “Why?”—you know, where the function is actually documented, not just demonstrated?  And, of course, programmers have always been known for the easiest-to-follow, most-comprehensive documentation! BTW: What were you thinking on your blog post that links to DataDemo—not everyone can find it and then copy-and-paste develop!  Get it together Sencha People!

Something’s not present?  Really?  Maybe you should have said in your original post something like, oh, say, “We’ve kept a couple [features] back to give them some extra polish, notably…”  But, maybe I missed a change in the definition of “notably”—it means you’re giving an example of some things, right?

My favorite was, “our goal based on the date published”  I mean seriously Sencha People!  Someone has a GOAL and you’re supposed to have a rock-solid DATE PUBLISHED!  How dare you release stuff early so people can get familiar with it?  I mean take Windows Vista, for example: Huge company, lots of profit, release dates set in stone, absolutely no bugs, and given to developers and OEM well in advance of the release! (OK, actual developers, stop rolling around on the floor—it’s dangerous to your electronics.)  Just remember, this is computer science, not computer art—when you’re programming, you really ought to know exactly how long it’s going to take you—the HTML 5 specification (which you’ve had the nerve to go ahead and start supporting) released just 3 days ago that it wouldn’t be a formal recommendation for 3 more years (that’s a good example of knowing exactly how long something will take, right?)

Well, I guess since some have gone ahead and built major aspects of their business around your target release date, that they’ll just have to go find another application-oriented, MVC-paradigm, feature-rich JavaScript framework that’s better.  I can’t really think of one, but hey, you Sencha People aren’t perfect, so what’s someone to do?  Build their own?

Just couldn’t resist sharing a little comedic relief with you in a time where I’m sure you’re sleeping as little as I trying to get your bread and butter prepared.

Again, well done and us developers are really looking forward to the value behind this well-engineered and implemented upgrade and are truly grateful for this preview release which allows us time to prepare for our upcoming (and passing) deadlines.

Thanks

It will be great to have (in the future releases) a kind of control package which will be dealing with application bootstrapping, configuration and tuning,  Just to have a global point for the whole application.

We are proud of your work, Simply we plan our goal based on the date published by sencha.Our company has developed a software which makes amazing use of sencha chart, This is the fundamental reason for our expectancy, our company are anxiously awaiting a stable version of extjs4, because we are preparing an update to our aplicacón,

Regards

One thing we were hoping to see in the preview was more detailed info on the new MVC and application structuring guidelines.  We reviewed the videos from the conference, which contained some good tidbits, but would be great to get some more meaty detail/examples, just so we can start planning ahead….

Are there any plans of setting up an extension team or development company to work along side or follow the releases as no doubt some of the plugins will have started to find their way into commercial applications?

The reason we called this a “preview” not a “beta” was that we’re missing some key features (like tree) and the testing time for some of the new features means that there are lots of known bugs. We don’t expect you to put this into production. As far as the dev team being non-responsive, Tommy and Jamie are both active on the thread further up, and we’ll be looking at the bugs in code and documentation that are found as quickly as we can.

We’ve said before that we’re delivering a little later than we liked because a number of the components took more time to stabilize than we expected. We do hope we can keep our delivery pretty close in time to what our original goal was. Thanks for being a part of the Ext JS community, we appreciate the feedback. We’re not perfect but I can guarantee you that we’re putting 100% effort into getting this out as soon as possible and as high quality as possible.

You are a damn rude with the Ext team…. Before telling that “nothing is working or it’s broken”, you should try to calm down, breath slowly and try to remember your first steps to the framework.

This is a “preview release” so it mean that is a “preview” .. a “sneak peak” and it give time to developer to adapt themselve to the mass of new things slowly.
I did not expect to have a preview that quickly so I’m damn really happy.

About where to start, If you have learned to use the previous release of ExtJS , well you should be accomodated and should know where to start : playing with examples, hacking the examples and reading the documentation to find out how it is overall architectured ... Well if you are a new ExtJS developer, I uderstand why you are lost.

Another way to discover changes is to use some of your Ext 3.3.1 codes with the new one to find out what have changed.
I found that the error/exception are much much more explicit so I already know what to do to make my old code work on the new one (use the developper console firebug etc.).

The data package is broken ? I don’t think so .... just give a another look at the samples and test again ... lots of them make use of data so I don’t think it’s broken.

So keep in mind that is a preview release for testing purpose only ! So be patient ....

The documentation is really really great and it’s so much a pleasure to navigate in it (althought there are still some buggy things but not annoying)

We feel the same in our company, we also have Sencha licenses and have outstanding commitments with our clients.

Eduard

Maybe you should make a list of the thing we CAN test in this developer preview?

Plus, the new theme(s) everybody was so excited about is missing.

Sencha, what happened there?... The developer preview is really UNUSABLE!

What’s the purpose of releasing it? Looks like nothing more than a bone thrown to a community growing anxious.

Now we know for sure there’s no hope in hell of having a working beta on February 28th, not to mention a full release. Well, I guess nobody really expected a full release in the end of the month, but an official statement about this would be nice, not to mention POLITE. After all, you’re trying to sell the damn thing, aren’t you?

Plus, nobody from the development team is answering, which is not exactly a surprise, we’ve started to get used to it.

Now, I’ve been to the conference and listened to the whole marketing hipe about the completely revamped architecture, completely new fabulous data package and the best documentation ever. What’s the use of having the best, most complete documentation ever if the product DOESN’T WORK AS DOCUMENTED?

Maybe this whole “major release” was too bold of a goal for such a short(?) dev time?

Sorry about flaring up like this, but my company bought a few licenses on the premise of a February-March release date, we’re waiting for it for a couple of new projects and now things are looking like we have to wait more. And the thing that pisses me off the most is that nobody cares to answer these questions!...

And before coming up with the line “it’s ready when it’s ready” - which is fine for open-source completely-free projects like jquery, think again that you’re trying to sell the product. You’re trying to boost your sales based on the promise on Ext4. Which will be a great product, I have no doubt about it, and 2 and 3 were great products too, but you guys need to learn to COMMUNICATE with your community/users/customers. You’re selling a product and you shouldn’t behave like a bunch of smart and bonny college kids working in their garage…

For those wondering what happened to the theme they saw at the conference, our first priority is to get all the components into a correct visual state by porting the Ext 3.3 theme into the new theming system. Note that all rounded corners and images used for framing etc are actually generated by our theming system. This means that the tabs you are seeing in IE are actually automatically generated based of CSS gradients and border-radius properties. None of them have actually been copied over from Ext 3. Once we get the 3.3 theme into a solid state we can look at implementing different themes using the new awesome SASS based theming system we have in place now.

Excellent work guys.

Thanks.

Great work guys!!