[ANN] Blossom 1.0.0-beta.1 (SproutCore 3 candidate) - SproutCore

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion [ANN] Blossom 1.0.0-beta.1 (SproutCore 3 candidate)
Received-SPF: pass (google.com: domain of fangiotop...@gmail.com designates 209.85.160.45 as permitted sender) client-ip=209.85.160.45;
MIME-Version: 1.0
In-Reply-To: <CAG0GFmx-aC5m16PnZTnEGDFybrFj0sukvAKaPX+0biWrVdq...@mail.gmail.com>
References: <26f37e79-98b1-4b21-9a99-ef0ec5d52...@y17g2000yqg.googlegroups.com>
 <13515688.20.1331225888132.JavaMail.geo-discussion-forums@pbbqc1> <CAG0GFmx-aC5m16PnZTnEGDFybrFj0sukvAKaPX+0biWrVdq...@mail.gmail.com>
From: Topher Fangio <fangiotop...@gmail.com>
Date: Thu, 8 Mar 2012 11:15:32 -0600
Message-ID: <CAG0GFmyYdghsAA2uB8+zik_KPPVZ-Lbha_M-DM9EhqxrP55...@mail.gmail.com>
Subject: Re: [sproutcore] Re: [ANN] Blossom 1.0.0-beta.1 (SproutCore 3 candidate)
To: sproutcore@googlegroups.com
Content-Type: multipart/alternative; boundary=047d7b33d9b8999d1904babe6d3d

--047d7b33d9b8999d1904babe6d3d
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Quick clarification on my last sentence: I didn't mean that usage of the
frameworks would force Blossom to become the new version of Sproutcore. I
meant that usage of the frameworks would probably decide which route was
successful.

--
Topher Fangio

System Architect
Pharos Resources

office: 325.216.2908
mobile: 325.660.7141


On Thu, Mar 8, 2012 at 11:13 AM, Topher Fangio <fangiotop...@gmail.com>wrot=
e:

> Mario,
>
> I believe the failure Erich was referring to was the mini-disaster and
> confusion surrounding Sproutcore 2 and how it broke off and is a separate
> project from Sproutcore. I don't think Ember.js is dead. I also don't
> believe that Ember.js and Sproutcore/Blossom are meant to even be
> competitors. They are different frameworks with different priorities.
> Ember.js is geared towards developing rich websites. Sproutcore and Bloss=
om
> are geared towards developing enterprise-class, desktop-like experiences =
on
> the web.
>
> It is Erich's goal that Blossom become the next iteration of Sproutcore.
> The core team and Sproutcore community have not come to a decision on
> whether or not that will happen, but honestly, I think time and usage of
> the frameworks will ultimately force that decision.
>
> --
> Topher Fangio
>
> System Architect
> Pharos Resources
>
> office: 325.216.2908
> mobile: 325.660.7141
>
>
> On Thu, Mar 8, 2012 at 10:58 AM, Mario Gutierrez <
> mario.l.gutier...@gmail.com> wrote:
>
>> "after the failure of Sproutcore 2" ... so people should stop using
>> Ember.js? And this will replace it?
>>
>>
>> On Friday, March 2, 2012 12:11:56 AM UTC-8, Erich Ocean wrote:
>>>
>>> The Blossom 1.0.0-beta.1 was released on March 1, 2012. You can learn
>>> more here:
>>>
>>>     https://github.com/fohr/**blossom <https://github.com/fohr/blossom>
>>>
>>> SproutCore is now in de facto maintenance mode. It's time to re-asses
>>> what we, as a community, want SproutCore to be.
>>>
>>> As many of you know, Blossom is a serious attempt to advance
>>> SproutCore 1.x forward after the failure of SproutCore 2. I put
>>> forward the rational behind Blossom in early December, 2011 (http://
>>> bit.ly/future-of-sproutcore) and also demo'd early work I had done on
>>> Blossom at the SproutCore User Group in Washington D.C. late January,
>>> 2012.
>>>
>>> The Blossom 1.0.0-beta.1 (available today) has:
>>>
>>> - A 100% Node.js native build system, including framework and app
>>> distribution and reuse via npm, the Node Package Manager.
>>>
>>> - A completely rewritten view layer built around two new classes,
>>> SC.Surface and SC.Layer. Surfaces support GPU-accelerated 3D
>>> transitions, and layers are a wrapper in the style of Core Animation
>>> around HTML 5's Canvas2D. All drawing in Blossom is done via Canvas2D =
=96
>>>  you never write HTML or CSS.
>>>
>>> - The latest datastore and statechart code from SproutCore 1.8.
>>>
>>> - The fast, small and stable runtime from SproutCore 1.4.5. In
>>> addition, the responder subsystem was fully audited and dramatically
>>> reduced in size and complexity.
>>>
>>> - Pervasive use of assertions (sc_assert), node-based unit tests for
>>> foundation and datastore, and a specialized "fuzz testing" app for the
>>> new view layer that has resulted in extremely robust view handling. SC
>>> 1.x DOM-based bugs are hopefully a thing of the past.
>>>
>>> - A much more approachable code base, centered around three
>>> frameworks: foundation (node, browser), datastore (node, browser), and
>>> application (browser). Blossom re-envisions SproutCore as a "batteries
>>> included" framework.
>>>
>>> - No support for mobile browsers. Current usage indicates that
>>> SproutCore is a poor fit for mobile browsers at this time, but...
>>>
>>> - Blossom supports the ability to compile a SproutCore app to run
>>> _natively_ on mobile devices such as iOS and Android, using a native
>>> (not WebView-based) runtime. The first two native runtimes (iOS and
>>> Mac OS X) are due on April 1, but you can start writing code now,
>>> since the API is identical.
>>>
>>> Blossom is designed to become the future of SproutCore, but it also
>>> stands on its own. It's amazing how much progress can be made in a
>>> short about of time by people dedicated to advancing the state of the
>>> art. I want to take this opportunity to thank all of the people on the
>>> #blossom IRC channel who chatted with me endlessly about design
>>> decisions throughout Blossom's development. Your feedback has made a
>>> huge difference. And also xTuple, without their support Blossom would
>>> not have been possible.
>>>
>>> Here's the release notes for the beta:
>>>
>>> > Blossom's API and feature set are now stable enough to begin
>>> developing production applications with, and Blossom includes the lates=
t
>>> Statechart and Datastore code from SproutCore 1.8.
>>>
>>>  >This is an early beta for experienced SproutCore developers
>>> targeting the latest releases of the Google Chrome and Apple Safari
>>> desktop web browsers. The public API is 99.9% stable (the only
>>> breaking changes going forward will be to accommodate bug fixes).
>>>
>>> > Only Blossom's application framework differs from SproutCore in terms
>>> of the public API (the foundation and datastore frameworks remain
>>> unchanged), so the vast majority of your existing knowledge re: how to
>>> write SproutCore apps still applies.
>>>
>>> > Note: Print-to-PDF support is missing, although Blossom's drawing
>>> model does support it correctly, so any SC.View and/or SC.Layer drawing
>>> code you write today will be supported when Print-to-PDF is enabled in =
a
>>> future release.
>>>
>>> Best, Erich Ocean
>>
>>  --
>> You received this message because you are subscribed to the Google Group=
s
>> "SproutCore" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/sproutcore/-/O7TFTOjJIwIJ.
>>
>> To post to this group, send email to sproutcore@googlegroups.com.
>> To unsubscribe from this group, send email to
>> sproutcore+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/sproutcore?hl=3Den.
>>
>
>

--047d7b33d9b8999d1904babe6d3d
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Quick clarification on my last sentence: I didn&#39;t mean that usage of th=
e frameworks would force Blossom to become the new version of Sproutcore. I=
 meant that usage of the frameworks would probably decide which route was s=
uccessful.<br clear=3D"all">

<div><br></div><div>--</div>Topher Fangio<br><br>System Architect<br>Pharos=
 Resources<br><br>office: 325.216.2908<br>mobile: 325.660.7141<br>
<br><br><div class=3D"gmail_quote">On Thu, Mar 8, 2012 at 11:13 AM, Topher =
Fangio <span dir=3D"ltr">&lt;<a href=3D"mailto:fangiotop...@gmail.com">fang=
iotop...@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

Mario,<div><br></div><div>I believe the failure Erich was referring to was =
the mini-disaster and confusion surrounding Sproutcore 2 and how it broke o=
ff and is a separate project from Sproutcore. I don&#39;t think Ember.js is=
 dead. I also don&#39;t believe that Ember.js and Sproutcore/Blossom are me=
ant to even be competitors. They are different frameworks with different pr=
iorities. Ember.js is geared towards developing rich websites. Sproutcore a=
nd Blossom are geared towards developing enterprise-class, desktop-like exp=
eriences on the web.</div>


<div><br></div><div>It is Erich&#39;s goal that Blossom become the next ite=
ration of Sproutcore. The core team and Sproutcore community have not come =
to a decision on whether or not that will happen, but honestly, I think tim=
e and usage of the frameworks will ultimately force that decision.</div>


<div><br></div><div><div class=3D"im"><div>--</div>Topher Fangio<br><br>Sys=
tem Architect<br>Pharos Resources<br><br>office: <a href=3D"tel:325.216.290=
8" value=3D"+13252162908" target=3D"_blank">325.216.2908</a><br>mobile: <a =
href=3D"tel:325.660.7141" value=3D"+13256607141" target=3D"_blank">325.660.=
7141</a><br>


<br><br></div><div><div class=3D"h5"><div class=3D"gmail_quote">On Thu, Mar=
 8, 2012 at 10:58 AM, Mario Gutierrez <span dir=3D"ltr">&lt;<a href=3D"mail=
to:mario.l.gutier...@gmail.com" target=3D"_blank">mario.l.gutier...@gmail.c=
om</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
&quot;after the failure of Sproutcore 2&quot; ... so people should stop usi=
ng Ember.js? And this will replace it?<div><div><div><br><div><br>On Friday=
, March 2, 2012 12:11:56 AM UTC-8, Erich Ocean wrote:<blockquote class=3D"g=
mail_quote" style=3D"margin:0;margin-left:0.8ex;border-left:1px #ccc solid;=
padding-left:1ex">


The Blossom 1.0.0-beta.1 was released on March 1, 2012. You can learn
<br>more here:
<br>
<br>=A0 =A0 <a href=3D"https://github.com/fohr/blossom" target=3D"_blank">h=
ttps://github.com/fohr/<u></u>blossom</a>
<br>
<br>SproutCore is now in de facto maintenance mode. It&#39;s time to re-ass=
es
<br>what we, as a community, want SproutCore to be.
<br>
<br>As many of you know, Blossom is a serious attempt to advance
<br>SproutCore 1.x forward after the failure of SproutCore 2. I put
<br>forward the rational behind Blossom in early December, 2011 (http://
<br><a href=3D"http://bit.ly/future-of-sproutcore" target=3D"_blank">bit.ly=
/future-of-sproutcore</a>) and also demo&#39;d early work I had done on
<br>Blossom at the SproutCore User Group in Washington D.C. late January,
<br>2012.
<br>
<br>The Blossom 1.0.0-beta.1 (available today) has:
<br>
<br>- A 100% Node.js native build system, including framework and app
<br>distribution and reuse via npm, the Node Package Manager.
<br>
<br>- A completely rewritten view layer built around two new classes,
<br>SC.Surface and SC.Layer. Surfaces support GPU-accelerated 3D
<br>transitions, and layers are a wrapper in the style of Core Animation
<br>around HTML 5&#39;s Canvas2D. All drawing in Blossom is done via Canvas=
2D =96
<br>=A0you never write HTML or CSS.
<br>
<br>- The latest datastore and statechart code from SproutCore 1.8.
<br>
<br>- The fast, small and stable runtime from SproutCore 1.4.5. In
<br>addition, the responder subsystem was fully audited and dramatically
<br>reduced in size and complexity.
<br>
<br>- Pervasive use of assertions (sc_assert), node-based unit tests for
<br>foundation and datastore, and a specialized &quot;fuzz testing&quot; ap=
p for the
<br>new view layer that has resulted in extremely robust view handling. SC
<br>1.x DOM-based bugs are hopefully a thing of the past.
<br>
<br>- A much more approachable code base, centered around three
<br>frameworks: foundation (node, browser), datastore (node, browser), and
<br>application (browser). Blossom re-envisions SproutCore as a &quot;batte=
ries
<br>included&quot; framework.
<br>
<br>- No support for mobile browsers. Current usage indicates that
<br>SproutCore is a poor fit for mobile browsers at this time, but...
<br>
<br>- Blossom supports the ability to compile a SproutCore app to run
<br>_natively_ on mobile devices such as iOS and Android, using a native
<br>(not WebView-based) runtime. The first two native runtimes (iOS and
<br>Mac OS X) are due on April 1, but you can start writing code now,
<br>since the API is identical.
<br>
<br>Blossom is designed to become the future of SproutCore, but it also
<br>stands on its own. It&#39;s amazing how much progress can be made in a
<br>short about of time by people dedicated to advancing the state of the
<br>art. I want to take this opportunity to thank all of the people on the
<br>#blossom IRC channel who chatted with me endlessly about design
<br>decisions throughout Blossom&#39;s development. Your feedback has made =
a
<br>huge difference. And also xTuple, without their support Blossom would
<br>not have been possible.
<br>
<br>Here&#39;s the release notes for the beta:
<br>
<br>&gt; Blossom&#39;s API and feature set are now stable enough to begin d=
eveloping production applications with, and Blossom includes the latest Sta=
techart and Datastore code from SproutCore 1.8.
<br>
<br>=A0&gt;This is an early beta for experienced SproutCore developers
<br>targeting the latest releases of the Google Chrome and Apple Safari
<br>desktop web browsers. The public API is 99.9% stable (the only
<br>breaking changes going forward will be to accommodate bug fixes).
<br>
<br>&gt; Only Blossom&#39;s application framework differs from SproutCore i=
n terms of the public API (the foundation and datastore frameworks remain u=
nchanged), so the vast majority of your existing knowledge re: how to write=
 SproutCore apps still applies.
<br>
<br>&gt; Note: Print-to-PDF support is missing, although Blossom&#39;s draw=
ing model does support it correctly, so any SC.View and/or SC.Layer drawing=
 code you write today will be supported when Print-to-PDF is enabled in a f=
uture release.
<br>
<br>Best, Erich Ocean</blockquote></div></div>

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;SproutCore&quot; group.<br></div></div>
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msg/sproutcore/-/O7TFTOjJIwIJ" target=3D"_blank">https://groups.google=
.com/d/msg/sproutcore/-/O7TFTOjJIwIJ</a>.<div><div>
<br>=20
To post to this group, send email to <a href=3D"mailto:sproutcore@googlegro=
ups.com" target=3D"_blank">sproutcore@googlegroups.com</a>.<br>
To unsubscribe from this group, send email to <a href=3D"mailto:sproutcore%=
2Bunsubscribe@googlegroups.com" target=3D"_blank">sproutcore+unsubscribe@go=
oglegroups.com</a>.<br>

For more options, visit this group at <a href=3D"http://groups.google.com/g=
roup/sproutcore?hl=3Den" target=3D"_blank">http://groups.google.com/group/s=
proutcore?hl=3Den</a>.<br>


</div></div></blockquote></div><br></div></div></div>
</blockquote></div><br>

--047d7b33d9b8999d1904babe6d3d--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
