Welcome!

From the Creator of SproutCore and CEO of Sproutit

Charles Jolley

Subscribe to Charles Jolley: eMailAlertsEmail Alerts
Get Charles Jolley via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by Charles Jolley

The Frozen Canuck is at it again.  This time with I think the first public explanation of how to build a custom view with the new SC.View class. Notice that SproutCore 1.0 views are built using a simple render() method where you generate HTML.  It’s a really easy API and it just so happens to be extremely fast, especially in IE where DOM manipulation is very expensive. Check it: Creating a Simple Custom View in SproutCore: Part1 ... (more)

Memory Optimization By @SproutCore | @DevOpsSummit [#DevOps]

The next release candidate for 1.11.0 will be out very shortly, but I thought it best to post a brief update on the past week’s work as this week saw a concentrated effort on core optimization. First we took another look at the use of arguments lists throughout the framework and found several more occurrences of it being accessed in an inefficient manner. Depending on the browser, accessing arguments in such a way that causes it to be allocated can be up to 80% slower and so it’s really good to have these all fixed. The other piece of optimization work undertaken has been much mo... (more)

Aspect-Oriented Programming and You

One of the coolest parts of the new SproutCore View layer is its ability to use aspect-based programming to add behaviors to views. Aspect-based programming is built on the premise that often objects that don’t follow from the same class hierarchy may in fact need similar behaviors. This is especially true in GUI programming when designers come to you and say something like “I came up with this new widget - it looks kind of like a progress bar but it acts like a button when you click on it”. In SproutCore, you capture these common behaviors in a “mixin”.  A mixin is just a colle... (more)

What Server Does SproutCore Run On?

Ha ha! Trick question! SproutCore is a client-side application framework (unlike, say, Google Web Toolkit). No part of SproutCore “runs” on the server, and SproutCore contains no “server-side” libraries. A web server (Apache, for example) is only used to deliver plain old HTML, CSS, and JavaScript to the browser. Once those initial files have been served, a SproutCore-based application runs entirely in the browser (and can easily be run “offline”, with no network access at all). Any server that can receive HTTP requests (which is all of them) can interact with a running SproutC... (more)

"From where we sit now, the code is shaping up quite nicely. Soon enough, if you have a SproutCore..."

“From where we sit now, the code is shaping up quite nicely. Soon enough, if you have a SproutCore app, you’ll be able to just drop an editor right into your app. As of today, anyone with a website can grab a copy of Bespin and include the editor component very simply in their pages. We figure that we’ve got another month of work to do before we’re ready to update bespin.mozilla.com. We have a whole bunch of features to port over from the old code and we need to make good on another big part of the Reboot promise: opening Bespin up for plugins. It’s been hard even for Bespin core... (more)