Comments on: SproutCore 1.0 gets closer; new demos too

By: lukesh

lukesh — Sat, 02 Jan 2010 23:42:23 +0000

My blog response to the Sproutcore project http://lukesh.wordpress.com/2010/01/02/thoughts-on-sproutcore-and-app-dev-in-general/

By: daanlib

daanlib — Thu, 29 Oct 2009 12:02:46 +0000

The demos are full of bugs in FF3. I guess they aren’t as close to 1.0 as they seem to think…

By: qualityking

qualityking — Thu, 29 Oct 2009 07:41:02 +0000

where is the dropdown ? Well not impressive… did anyone check in FF3 …

By: rubley

rubley — Wed, 28 Oct 2009 20:38:30 +0000

I don’t understand the “load the data dynamically” models like the “big_list” demo. First of all, the largest dataset for the demo is 1,000 items. Guess what, loading a table with 1,000 cells would be faster, and it would scroll smoothly. So then the response will be “What if there are 100,000 items?” and the answer is: No one scrolls through a list of 100,000 items. Ever. Large datasets require advanced searching capabilities, not advanced scrolling. It’s a solution in search of a problem.

By: juanpin

juanpin — Wed, 28 Oct 2009 17:27:58 +0000

Yves, interesting point. Let me give you a very brief response on this. Sproutcore is currently imitating the same keyboard navigation as the Mac has enabled by default (only jump between textfields, you can change this in macs in system preferences).

I did some work to enable keyboard navigation through all the controls, using tab. Also I did make sure that all controls (buttons, sliders, etc) respond to arrow keys, returns,etc if they have focus. I would put some of my time to put together a demo.

As a final note, this is a very hard problem as every browser or platform behaves in a different way and there is questions like: should the library imitate the platform? or should we force users into what we believe is a better experience?. when should a textfield loose focus?

My conclusion so far is that nobody has a final answer on this questions, but I would like to hear what people have to say about this.

(excuse my english, if I made any mistakes)

By: MartijnHoutman

MartijnHoutman — Wed, 28 Oct 2009 15:47:39 +0000

Agreed, especially from a release candidate I would expect it to be more accessible. There seems to be some sort of keyboard navigation though; it is, however, not really clear what item currently has focus.

It seems that most projects focus on features first, exceptions later. YMMV, but I think it is a reasonable approach. Most features seem to be complete (for now), so I suppose now is the time for accessibility and exceptional cases such as images failing to load etc.

By: Yves

Yves — Wed, 28 Oct 2009 13:53:37 +0000

Why every library has to be totally non-accessible ?
I can’t use keyboard navigation, what happens if the images fails to load, I can’t properly zoom in text-only mode, …
People should really focus more on these points, instead of building the same kind of libraries over and over again.