Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of flexcapacitor@gmail.com
 designates 209.85.214.175 as permitted sender)
Received-SPF: pass (google.com: domain of flexcapacitor@gmail.com designates
 10.60.13.1 as permitted sender) client-ip=10.60.13.1;
MIME-Version: 1.0
Date: Wed, 22 Feb 2012 04:23:15 -0600
Message-ID: 
 <CANcBHEBWPbVQw=qnrmYK42bpg4zrcze6GKj5xsNt5i6KS_E4tQ@mail.gmail.com>
Subject: [RT] Inventing on principle
From: jude <flexcapacitor@gmail.com>
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=e89a8ff250085c540a04b98aeacd

--e89a8ff250085c540a04b98aeacd
Content-Type: text/plain; charset=ISO-8859-1

There are some things in here that may be interesting to think about going
forward pertaining to compiler and design view type discussions:

http://vimeo.com/36579366

I found it interesting that the decisions he makes in his development tools
are based on his principle, "Creators need an immediate connection to what
they create." In other words, when you're making something, if you make a
change or a decision you need to see the effect of that immediately.

It reminds me of something Dan (polygeeks) said when he sets out to create
something (possible total misquote- sorry Dan), "I imagine how I'd like it
to be in a perfect world and then I try to make that happen."

--e89a8ff250085c540a04b98aeacd--