Hi listees,
The critical question, then, is how to create an environment that
allows
(nay, encourages!) frameworks to be created, tested, polished,
documented,
indexed, shared, etc. My intuition is that GitHub should be part of
this,
because it promotes free-flowing cooperation, merging,
Hi Chris,
What a coincidence :) gen_bridge_doc is the tool I was speaking of in
an email I've just send in this thread :)
Eloy
On Dec 3, 2008, at 9:34 AM, Chris McGrath wrote:
On 3 Dec 2008, at 04:05, Richard Kilmer wrote:
The mapping files do create data structures, I was totally going
On 3 Dec 2008, at 06:17, John Shea wrote:
I experimented and sure enough I could deliver to my client (me in
this experiment ;-) ) rapidly changing versions of a beautiful GUI
app (1 button) by only changing the source file on the server.
Very cool!
Chris
On Dec 3, 2008, at 11:26 AM, Laurent Sansonetti wrote:
On Dec 3, 2008, at 2:09 AM, Eloy Duran wrote:
Hi Laurent,
I agree HotCocoa should be covered by tests, at least to catch
regressions.
HotCocoa was initially started as an experiment and we (well,
Rich) iterated a lot on the
On Dec 3, 2008, at 2:56 AM, Eloy Duran wrote:
On Dec 3, 2008, at 11:26 AM, Laurent Sansonetti wrote:
On Dec 3, 2008, at 2:09 AM, Eloy Duran wrote:
Hi Laurent,
I agree HotCocoa should be covered by tests, at least to catch
regressions.
HotCocoa was initially started as an experiment and
On Nov 12, 2008, at 9:16 AM, Richard Kilmer wrote:
All,
As the main author of HotCocoa let me chime in on what I see its
main purpose is.
In a nutshell here is my 5 second primary definition:
HotCocoa is an idiomatic Ruby API that simplifies the configuration
and wiring together of
Hi Rich,
That seems like a sensible list to me.
Thanks for the info!
- Eloy
On Nov 12, 2008, at 4:10 PM, Richard Kilmer wrote:
On Nov 12, 2008, at 9:16 AM, Richard Kilmer wrote:
All,
As the main author of HotCocoa let me chime in on what I see its
main purpose is.
In a nutshell here
