Sproutcore 1.5 released
blog.sproutcore.com
Sproutcore 1.5 released
1–10 of 28 posts
Re: Sproutcore 1.5 released
#2I'm sure it's got its merits but the Sproutcore site does a horrible job explaining what it excels at.
For example, on the Demos and Sample Code page it has me install a ruby gem.
http://www.sproutcore.com/demos/
What the hell? You lost my interest at ruby and the command line.
Re: Sproutcore 1.5 released
#3I'm sure it's got its merits but the Sproutcore site does a horrible job explaining what it excels at. For example, on the Demos and Sample Code page it has me install a ruby gem. http://www.sproutcore.com/demos/ What the hell? You lost my interest at ruby and the command line.
> What the hell? You lost my interest at ruby and the command line.
I install all my dev stuff with the command line (npm, gem, easy_python etc). What's wrong with that?
Re: Sproutcore 1.5 released
#4I'm sure it's got its merits but the Sproutcore site does a horrible job explaining what it excels at. For example, on the Demos and Sample Code page it has me install a ruby gem. http://www.sproutcore.com/demos/ What the hell? You lost my interest at ruby and the command line.
I'm sorry that you were turned off by the Ruby build tools.
Many people see the build tools and assume that you need to know Ruby to use SproutCore. This isn't true. SproutCore apps are written 100% in JavaScript, and Ruby just happens to be the language we used to create the tooling needed to build serious web applications.
For example, the build tools will automatically concatenate your JavaScript and CSS files, minify them, ensure that dependencies are loaded in the correct order, provide a proxy so you can work around the single-origin policy during development, generate unit tests, and much more. We think that the trade-off is worth it, especially since all Linux and Mac OS X distributions come with Ruby and RubyGems.
One of the guiding principles behind SproutCore is that it allows you to build well-architected JavaScript applications where the separation of concerns is clear. Being able to organize your JavaScript files is an important part of that. I think you'll find that when you start building web apps of any serious scale, you'll end up assembling a collection of command-line tools that do all of these things. We just put them all in one place for you.
Re: Sproutcore 1.5 released
#5I'm sure it's got its merits but the Sproutcore site does a horrible job explaining what it excels at. For example, on the Demos and Sample Code page it has me install a ruby gem. http://www.sproutcore.com/demos/ What the hell? You lost my interest at ruby and the command line.
> What the hell? You lost my interest at ruby and the command line. I install all my dev stuff with the command line (npm, gem, easy_python etc). What's wrong with that?
...the problem is that there is no reason that a demo for a web framework should require an install in the first place--I mean you're already on a web page to look at it aren't you?...sure it's easy enough to install (i did it)...but it seems lazy especially if the intent is to promote usage of the framework.
Re: Sproutcore 1.5 released
#6Earlier quoted context omitted.
> What the hell? You lost my interest at ruby and the command line. I install all my dev stuff with the command line (npm, gem, easy_python etc). What's wrong with that?
...the problem is that there is no reason that a demo for a web framework should require an install in the first place--I mean you're already on a web page to look at it aren't you?...sure it's easy enough to install (i did it)...but it seems lazy especially if the intent is to promote usage of the framework.
We have a link to our, albeit totally old and crappy, demos right on that page: http://demo.sproutcore.com/
We're working on new demos, and a new website. Demos feature much more heavily in the new design, and you definitely don't (and won't) need to install the build tools to run them!
Re: Sproutcore 1.5 released
#7Earlier quoted context omitted.
...the problem is that there is no reason that a demo for a web framework should require an install in the first place--I mean you're already on a web page to look at it aren't you?...sure it's easy enough to install (i did it)...but it seems lazy especially if the intent is to promote usage of the framework.
We have a link to our, albeit totally old and crappy, demos right on that page: http://demo.sproutcore.com/ We're working on new demos, and a new website. Demos feature much more heavily in the new design, and you definitely don't (and won't) need to install the build tools to run them!
I would encourage you to make that a priority. Every time I see something about SproutCore, I'm interested but end up not doing anything with it. I keep hearing about the demos being out of date.
Things like this: "we have a great new default theme called Ace 2.0"
Sounds great, how about a screenshot or two, if not a demo?
And this: "looks at home on ... mobile operating systems"
More info please? I'm interested but I see no examples, screenshots or other info about doing mobile dev. Device, browser and OS support?
Re: Sproutcore 1.5 released
#8Earlier quoted context omitted.
We have a link to our, albeit totally old and crappy, demos right on that page: http://demo.sproutcore.com/ We're working on new demos, and a new website. Demos feature much more heavily in the new design, and you definitely don't (and won't) need to install the build tools to run them!
I would encourage you to make that a priority. Every time I see something about SproutCore, I'm interested but end up not doing anything with it. I keep hearing about the demos being out of date. Things like this: "we have a great new default theme called Ace 2.0" Sounds great, how about a screenshot or two, if not a demo? And this: "looks at home on ... mobile operating systems" More info please? I'm interested but…
agree with the above...went through some eval on SC a few months back. We didn't go with SC, not for the lack of the demo link (swear the demo link wasn't there then :)), but I recall being a bit off put about it as well
...seems there has been a lot of development since though, some updated demos would really be nice.
Re: Sproutcore 1.5 released
#9Leaving out screenshots or a demo of the new theme was definitely an oversight on our part. Sorry!
I've put up a build of our sample controls app that demonstrates the new controls:
Re: Sproutcore 1.5 released
#10Earlier quoted context omitted.
We have a link to our, albeit totally old and crappy, demos right on that page: http://demo.sproutcore.com/ We're working on new demos, and a new website. Demos feature much more heavily in the new design, and you definitely don't (and won't) need to install the build tools to run them!
I would encourage you to make that a priority. Every time I see something about SproutCore, I'm interested but end up not doing anything with it. I keep hearing about the demos being out of date. Things like this: "we have a great new default theme called Ace 2.0" Sounds great, how about a screenshot or two, if not a demo? And this: "looks at home on ... mobile operating systems" More info please? I'm interested but…
Fair points all around; I agree wholeheartedly. Here's what the problem has been thus far: do we focus on making the framework better, or do we focus on selling it? Personally, I'm much more comfortable with making sure we deliver the goods before we try to sell it. That's what SproutCore 1.5 is about. This is the first smoke signal of where we want to head with the framework, and people can take that for what it is. The core of the framework is amazing and fun to work with, but a lot of our demos are old and ugly. In many cases, our documentation has been or is still lacking and we're working on that too.
This obviously makes it a tougher sell. However, when people actually start building apps, their responses are overwhelmingly positive and they're very happy with their decision. I would much rather this problem than vise versa. We're going to work on the outward facing stuff, I promise.