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 we
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 interfa
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 interface, now it's maybe time to start
thinking about freezing
Hi Laurent,
Sure, I'm in no hurry at all to start work at this.
Just saying that my preference would be this path.
Which was actually meant more to keep the people on this list in the
loop on stuff
we discuss elsewhere than for you :-)
- Eloy
PS: Could you point me to exactly which db's you
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 interface, now it's maybe time to start
thinking about freezing some parts of the API (most probably the
mapp
On Dec 3, 2008, at 12:56 AM, Eloy Duran wrote:
OK; here's a partly-baked idea, loosely inspired by Python
docstrings.
The HC declarations are (I assume) stashing information away in
some
sort of data structure. If not, they certainly could be (:-).
Once
the information is availabl
Hi Eloy,
On Dec 3, 2008, at 12:46 AM, Eloy Duran wrote:
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 thi
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
_
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
OK; here's a partly-baked idea, loosely inspired by Python
docstrings.
The HC declarations are (I assume) stashing information away in some
sort of data structure. If not, they certainly could be (:-). Once
the information is available at runtime, any HC script could
retrieve
them for
On Dec 2, 2008, at 10:17 PM, Rich Morin wrote:
Consequently, IMHO, the question of whether HC _should_ include
zillions
of random frameworks is rather off the mark. Clearly, if HC becomes
even
slightly popular, community members _will_ be creating these
frameworks.
The critical question
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, e
On 3 Dec 2008, at 04:05, Richard Kilmer wrote:
The mapping files do create data structures, I was totally going to
get these to produce documentation on what was mapped, what the
defaults were, what custom methods exist, etc. Its pretty easy to
do I think. The issue I ran into was I want
I think its interesting that Hot Cocoa in inspiring such different
ideas, I must admit my thoughts had not run anywhere as complex as
those below.
My first thought was "Wow! I can make a generic (or fairly static)
launcher and get it to load remotely both my view and model from ruby
file
On Dec 2, 2008, at 9:00 PM, Chris McGrath wrote:
On 3 Dec 2008, at 00:45, Rich Morin wrote:
At 01:27 + 12/3/08, Chris McGrath wrote:
One thing I've been considering since watching your RubyConf
presentation via confreaks is ...
Just to be clear, Rich Kilmer is the HC developer that ma
On 3 Dec 2008, at 00:45, Rich Morin wrote:
At 01:27 + 12/3/08, Chris McGrath wrote:
One thing I've been considering since watching your RubyConf
presentation via confreaks is ...
Just to be clear, Rich Kilmer is the HC developer that made the
RubyConf presentation; I'm just a MacRuby and
At 01:27 + 12/3/08, Chris McGrath wrote:
> One thing I've been considering since watching your RubyConf
> presentation via confreaks is ...
Just to be clear, Rich Kilmer is the HC developer that made the
RubyConf presentation; I'm just a MacRuby and HotCocoa wannabe...
> ... auto-generating
On 2 Dec 2008, at 22:48, Rich Morin wrote:
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
At 10:10 -0500 11/12/08, Richard Kilmer wrote:
>> "HotCocoa is an idiomatic Ruby API that simplifies the configuration
>> and wiring together of complex ObjC/Cocoa classes."
>>
>> I realize this will not be all things to all people, and that some
>> may not see the much value in this. I do, and I t
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 i
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 com
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 complex ObjC/Cocoa classes."
I realize this will not be
22 matches
Mail list logo
