I'd like to second the question on HotCocoa status - is it dead, in limbo, quietly flourishing, ??? Mike On Mar 23, 2011, at 7:38 PM, macruby-devel-request@lists.macosforge.org wrote:
Message: 3 Date: Wed, 23 Mar 2011 22:52:42 +0100 From: Vincenzo Piombo <vipenzo@gmail.com> To: macruby-devel@lists.macosforge.org Subject: [MacRuby-devel] is hotcocoa dead ? Message-ID: <AANLkTimHhksDr6hswT9Fpowxw_JkA_GZu5dneT2PEuc0@mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1"
Hello all, I discovered macruby since a few weeks and I'm really enthusiast. I begun playing with it and really like the hotcocoa approach, but it seems stopped since more than a year, is it still maintained ?
Anyway, I think I found a bug in the hotcocoa canvas part: the text method draws at a very big size regardless of the chosen font. The problem is that the transformation matrix for the text is not set.
Here is the fix if anyone needs it:
module HotCocoa::Graphics class Canvas def text(txt="A", x=0, y=0) affine = CGContextGetCTM(@ctx) CGContextSetTextMatrix (@ctx, affine); txt = txt.to_s unless txt.kind_of?(String) if @registration == :center width = textwidth(txt) x = x - width / 2 y = y + @fsize / 2 end CGContextShowTextAtPoint(@ctx, x, y, txt, txt.length) end end end
On Thu, 24 Mar 2011 11:53:23 -0600 Michael Gehl <mike@vail.net> wrote:
I'd like to second the question on HotCocoa status - is it dead, in limbo, quietly flourishing, ???
As others have said, it seems to be in limbo (which strikes me as a great shame). Would anyone who was previously involved in the maintenance of the project explain what would be involved in a new set of people maintaining the code base? Perry -- Perry E. Metzger perry@piermont.com
On Mar 24, 2011, at 6:57 PM, Perry E. Metzger wrote:
Would anyone who was previously involved in the maintenance of the project explain what would be involved in a new set of people maintaining the code base?
The blessed repository is on GitHub [1]. I'm sure Rich would love to accept patches for the from anyone who's interested in working on it. Manfred [1] https://github.com/richkilmer/hotcocoa
Rich just sold his company to Living Social and I'm sure he's really busy ATM. If people are willing to hack on this project and maintain it (the core team won't), we probably should move it to its own repo and give commit rights to people. Who's interested in created a HotCocoa team? Thanks, - Matt On Thu, Mar 24, 2011 at 11:37 AM, Manfred Stienstra <manfred@gmail.com>wrote:
On Mar 24, 2011, at 6:57 PM, Perry E. Metzger wrote:
Would anyone who was previously involved in the maintenance of the project explain what would be involved in a new set of people maintaining the code base?
The blessed repository is on GitHub [1]. I'm sure Rich would love to accept patches for the from anyone who's interested in working on it.
Manfred
[1] https://github.com/richkilmer/hotcocoa _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
For me, I've basically dropped HotCocoa. After doing a few apps with it I quickly came to realize that I liked IB and building apps that way. The thing that I've missed from HotCocoa is all the little Ruby-ish extensions that it added to various classes. As I've built other apps I've been collecting up a few of those and decided to stuff them into a gem. You can see them at https://github.com/dj2/Bean if you're interested. Out of curiosity, what's the correct way to mark a gem as MacRuby only so I can push it up to rubygems.org? dan On Mar 24, 2011, at 8:56 PM, Matt Aimonetti wrote:
Rich just sold his company to Living Social and I'm sure he's really busy ATM. If people are willing to hack on this project and maintain it (the core team won't), we probably should move it to its own repo and give commit rights to people.
Who's interested in created a HotCocoa team?
Thanks,
- Matt
On Thu, Mar 24, 2011 at 11:37 AM, Manfred Stienstra <manfred@gmail.com> wrote:
On Mar 24, 2011, at 6:57 PM, Perry E. Metzger wrote:
Would anyone who was previously involved in the maintenance of the project explain what would be involved in a new set of people maintaining the code base?
The blessed repository is on GitHub [1]. I'm sure Rich would love to accept patches for the from anyone who's interested in working on it.
Manfred
[1] https://github.com/richkilmer/hotcocoa _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Out of curiosity, what's the correct way to mark a gem as MacRuby only so I can push it up to rubygems.org?
Currently, there isn't any because rubygems only has a concept of platform and not of Ruby engine :( - Matt On Thu, Mar 24, 2011 at 6:21 PM, dan sinclair <dj2@everburning.com> wrote:
For me, I've basically dropped HotCocoa. After doing a few apps with it I quickly came to realize that I liked IB and building apps that way. The thing that I've missed from HotCocoa is all the little Ruby-ish extensions that it added to various classes. As I've built other apps I've been collecting up a few of those and decided to stuff them into a gem.
You can see them at https://github.com/dj2/Bean if you're interested.
Out of curiosity, what's the correct way to mark a gem as MacRuby only so I can push it up to rubygems.org?
dan
On Mar 24, 2011, at 8:56 PM, Matt Aimonetti wrote:
Rich just sold his company to Living Social and I'm sure he's really busy ATM. If people are willing to hack on this project and maintain it (the core team won't), we probably should move it to its own repo and give commit rights to people.
Who's interested in created a HotCocoa team?
Thanks,
- Matt
On Thu, Mar 24, 2011 at 11:37 AM, Manfred Stienstra <manfred@gmail.com> wrote:
On Mar 24, 2011, at 6:57 PM, Perry E. Metzger wrote:
Would anyone who was previously involved in the maintenance of the project explain what would be involved in a new set of people maintaining the code base?
The blessed repository is on GitHub [1]. I'm sure Rich would love to accept patches for the from anyone who's interested in working on it.
Manfred
[1] https://github.com/richkilmer/hotcocoa _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Currently, there isn't any because rubygems only has a concept of platform and not of Ruby engine :(
Is that a potential feature they might be willing to add or is it in the roadmap? --- Buddy Lindsey http://www.buddylindsey.com http://www.twitter.com/buddylindsey On Thu, Mar 24, 2011 at 9:23 PM, Matt Aimonetti <mattaimonetti@gmail.com>wrote:
Out of curiosity, what's the correct way to mark a gem as MacRuby only so I can push it up to rubygems.org?
Currently, there isn't any because rubygems only has a concept of platform and not of Ruby engine :(
- Matt
On Thu, Mar 24, 2011 at 6:21 PM, dan sinclair <dj2@everburning.com> wrote:
For me, I've basically dropped HotCocoa. After doing a few apps with it I quickly came to realize that I liked IB and building apps that way. The thing that I've missed from HotCocoa is all the little Ruby-ish extensions that it added to various classes. As I've built other apps I've been collecting up a few of those and decided to stuff them into a gem.
You can see them at https://github.com/dj2/Bean if you're interested.
Out of curiosity, what's the correct way to mark a gem as MacRuby only so I can push it up to rubygems.org?
dan
On Mar 24, 2011, at 8:56 PM, Matt Aimonetti wrote:
Rich just sold his company to Living Social and I'm sure he's really busy ATM. If people are willing to hack on this project and maintain it (the core team won't), we probably should move it to its own repo and give commit rights to people.
Who's interested in created a HotCocoa team?
Thanks,
- Matt
On Thu, Mar 24, 2011 at 11:37 AM, Manfred Stienstra <manfred@gmail.com> wrote:
On Mar 24, 2011, at 6:57 PM, Perry E. Metzger wrote:
Would anyone who was previously involved in the maintenance of the project explain what would be involved in a new set of people maintaining the code base?
The blessed repository is on GitHub [1]. I'm sure Rich would love to accept patches for the from anyone who's interested in working on it.
Manfred
[1] https://github.com/richkilmer/hotcocoa _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
That's pretty cool :-). Although "def [](key)" in nsuserdefaults_additions.rb seems to be unnecessary, because macruby should already do that. It should automatically replace [] and []= calls to objectForKey: and setObject:forKey: (when necessary only, of course). I see you added deletion and sync on []=, which is why I didn't point it being unnecessary :-) -- Thibault Martin-Lagardette On Friday, March 25, 2011 at 02:21, dan sinclair wrote:
For me, I've basically dropped HotCocoa. After doing a few apps with it I quickly came to realize that I liked IB and building apps that way. The thing that I've missed from HotCocoa is all the little Ruby-ish extensions that it added to various classes. As I've built other apps I've been collecting up a few of those and decided to stuff them into a gem.
You can see them at https://github.com/dj2/Bean if you're interested.
Out of curiosity, what's the correct way to mark a gem as MacRuby only so I can push it up to rubygems.org?
dan
On Mar 24, 2011, at 8:56 PM, Matt Aimonetti wrote:
Rich just sold his company to Living Social and I'm sure he's really busy ATM. If people are willing to hack on this project and maintain it (the core team won't), we probably should move it to its own repo and give commit rights to people.
Who's interested in created a HotCocoa team?
Thanks,
- Matt
On Thu, Mar 24, 2011 at 11:37 AM, Manfred Stienstra <manfred@gmail.com> wrote:
On Mar 24, 2011, at 6:57 PM, Perry E. Metzger wrote:
Would anyone who was previously involved in the maintenance of the project explain what would be involved in a new set of people maintaining the code base?
The blessed repository is on GitHub [1]. I'm sure Rich would love to accept patches for the from anyone who's interested in working on it.
Manfred
[1] https://github.com/richkilmer/hotcocoa _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Sweet, didn't know about the automatic translation of objectForKey:. Will keep that in mind before wrapping it, heh. Are there any other methods to keep in mind that MacRuby automatically translates to a Ruby-ish version? Thanks, dan On 2011-03-25, at 3:14 AM, Thibault Martin-Lagardette wrote:
That's pretty cool :-).
Although "def [](key)" in nsuserdefaults_additions.rb seems to be unnecessary, because macruby should already do that. It should automatically replace [] and []= calls to objectForKey: and setObject:forKey: (when necessary only, of course). I see you added deletion and sync on []=, which is why I didn't point it being unnecessary :-)
-- Thibault Martin-Lagardette
On Friday, March 25, 2011 at 02:21, dan sinclair wrote:
For me, I've basically dropped HotCocoa. After doing a few apps with it I quickly came to realize that I liked IB and building apps that way. The thing that I've missed from HotCocoa is all the little Ruby-ish extensions that it added to various classes. As I've built other apps I've been collecting up a few of those and decided to stuff them into a gem.
You can see them at https://github.com/dj2/Bean if you're interested.
Out of curiosity, what's the correct way to mark a gem as MacRuby only so I can push it up to rubygems.org?
dan
On Mar 24, 2011, at 8:56 PM, Matt Aimonetti wrote:
Rich just sold his company to Living Social and I'm sure he's really busy ATM. If people are willing to hack on this project and maintain it (the core team won't), we probably should move it to its own repo and give commit rights to people.
Who's interested in created a HotCocoa team?
Thanks,
- Matt
On Thu, Mar 24, 2011 at 11:37 AM, Manfred Stienstra <manfred@gmail.com> wrote:
On Mar 24, 2011, at 6:57 PM, Perry E. Metzger wrote:
Would anyone who was previously involved in the maintenance of the project explain what would be involved in a new set of people maintaining the code base?
The blessed repository is on GitHub [1]. I'm sure Rich would love to accept patches for the from anyone who's interested in working on it.
Manfred
[1] https://github.com/richkilmer/hotcocoa _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
there you go: http://ofps.oreilly.com/titles/9781449380373/ch01.html#_syntactic_sugar - Matt On Fri, Mar 25, 2011 at 7:24 AM, dan sinclair <dj2@everburning.com> wrote:
Sweet, didn't know about the automatic translation of objectForKey:. Will keep that in mind before wrapping it, heh. Are there any other methods to keep in mind that MacRuby automatically translates to a Ruby-ish version?
Thanks, dan
On 2011-03-25, at 3:14 AM, Thibault Martin-Lagardette wrote:
That's pretty cool :-).
Although "def [](key)" in nsuserdefaults_additions.rb seems to be unnecessary, because macruby should already do that. It should automatically replace [] and []= calls to objectForKey: and setObject:forKey: (when necessary only, of course). I see you added deletion and sync on []=, which is why I didn't point it being unnecessary :-)
-- Thibault Martin-Lagardette
On Friday, March 25, 2011 at 02:21, dan sinclair wrote:
For me, I've basically dropped HotCocoa. After doing a few apps with it I quickly came to realize that I liked IB and building apps that way. The thing that I've missed from HotCocoa is all the little Ruby-ish extensions that it added to various classes. As I've built other apps I've been collecting up a few of those and decided to stuff them into a gem.
You can see them at https://github.com/dj2/Bean if you're interested.
Out of curiosity, what's the correct way to mark a gem as MacRuby only so I can push it up to rubygems.org?
dan
On Mar 24, 2011, at 8:56 PM, Matt Aimonetti wrote:
Rich just sold his company to Living Social and I'm sure he's really busy ATM. If people are willing to hack on this project and maintain it (the core team won't), we probably should move it to its own repo and give commit rights to people.
Who's interested in created a HotCocoa team?
Thanks,
- Matt
On Thu, Mar 24, 2011 at 11:37 AM, Manfred Stienstra <manfred@gmail.com> wrote:
On Mar 24, 2011, at 6:57 PM, Perry E. Metzger wrote:
Would anyone who was previously involved in the maintenance of the project explain what would be involved in a new set of people maintaining the code base?
The blessed repository is on GitHub [1]. I'm sure Rich would love to accept patches for the from anyone who's interested in working on it.
Manfred
[1] https://github.com/richkilmer/hotcocoa _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
On 25/03/2011, at 2:21 PM, dan sinclair wrote:
For me, I've basically dropped HotCocoa. After doing a few apps with it I quickly came to realize that I liked IB and building apps that way. The thing that I've missed from HotCocoa is all the little Ruby-ish extensions that it added to various classes. As I've built other apps I've been collecting up a few of those and decided to stuff them into a gem.
You can see them at https://github.com/dj2/Bean if you're interested.
This is very good. I can see them being very useful. Here's one I use a lot. Feel free to add it. class NSIndexSet include Enumerable def each i = self.firstIndex until i == NSNotFound yield i i = self.indexGreaterThanIndex(i) end end end Henry
Cool, added. If you have others, feel free to fork and send me a pull request. Thanks, dan On Mar 25, 2011, at 7:38 PM, Henry Maddocks wrote:
On 25/03/2011, at 2:21 PM, dan sinclair wrote:
For me, I've basically dropped HotCocoa. After doing a few apps with it I quickly came to realize that I liked IB and building apps that way. The thing that I've missed from HotCocoa is all the little Ruby-ish extensions that it added to various classes. As I've built other apps I've been collecting up a few of those and decided to stuff them into a gem.
You can see them at https://github.com/dj2/Bean if you're interested.
This is very good. I can see them being very useful.
Here's one I use a lot. Feel free to add it.
class NSIndexSet include Enumerable
def each i = self.firstIndex until i == NSNotFound yield i i = self.indexGreaterThanIndex(i) end end
end
Henry
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
On Mar 24, 2011, at 5:56 PM, Matt Aimonetti wrote:
Rich just sold his company to Living Social and I'm sure he's really busy ATM. If people are willing to hack on this project and maintain it (the core team won't), we probably should move it to its own repo and give commit rights to people.
Who's interested in created a HotCocoa team?
I thought the project's being on GitHub facilitated this already? You guys should be able to start forking away and coordinating your patches over email if there's any real interest in creating such a team! I think it would be interesting, myself, particularly if it led to the creation of something that could compare to Processing. :) - Jordan
Jordan, moving to GitHub helped but it also created fragmentation. Everyone is working on its own fork and there is nobody to centralize all the changes in a single repo. I agree that having a MacRuby based Processing like solution would be awesome. - Matt On Thu, Mar 24, 2011 at 7:35 PM, Jordan K. Hubbard <jkh@apple.com> wrote:
On Mar 24, 2011, at 5:56 PM, Matt Aimonetti wrote:
Rich just sold his company to Living Social and I'm sure he's really busy ATM. If people are willing to hack on this project and maintain it (the core team won't), we probably should move it to its own repo and give commit rights to people.
Who's interested in created a HotCocoa team?
I thought the project's being on GitHub facilitated this already? You guys should be able to start forking away and coordinating your patches over email if there's any real interest in creating such a team! I think it would be interesting, myself, particularly if it led to the creation of something that could compare to Processing. :)
- Jordan
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
I was trying to keep the various forks in line for a while before I stopped working on HotCocoa. If you look at the network graph, there is a fork off of mine which I think contains everything that has been worked on so far. Maybe a good place to start synchronizing from. dan On 2011-03-24, at 10:57 PM, Matt Aimonetti wrote:
Jordan, moving to GitHub helped but it also created fragmentation. Everyone is working on its own fork and there is nobody to centralize all the changes in a single repo. I agree that having a MacRuby based Processing like solution would be awesome.
- Matt
On Thu, Mar 24, 2011 at 7:35 PM, Jordan K. Hubbard <jkh@apple.com> wrote:
On Mar 24, 2011, at 5:56 PM, Matt Aimonetti wrote:
Rich just sold his company to Living Social and I'm sure he's really busy ATM. If people are willing to hack on this project and maintain it (the core team won't), we probably should move it to its own repo and give commit rights to people.
Who's interested in created a HotCocoa team?
I thought the project's being on GitHub facilitated this already? You guys should be able to start forking away and coordinating your patches over email if there's any real interest in creating such a team! I think it would be interesting, myself, particularly if it led to the creation of something that could compare to Processing. :)
- Jordan
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
I think that Dan just declared himself the new project lead! :-) Seriously, I understand Matt's point about fragmentation, but I honestly haven't seen enough action in this space to really merit that much concern about it. HotCocoa's problems are deeper than a small collection of one or two line patches, the bigger questions being: 1. What problem, or problems, is HotCocoa really trying to solve (and does it currently solve them)? 2. How far should HotCocoa go? Does it want to front-end every bit of complex Cocoa API or design pattern such that one can do, say, something meaningful with CoreData with just a few lines of code? If not, how much is considered reasonable and why? 3. How will the folks working on HotCocoa know when they're "finished"? (Related to both #1 and #2). 4. UIKit vs AppKit. Sure, right now only one of them are relevant to MacRuby, but should that change, how might this affect HotCocoa? I'm sure folks can come up with even more "pertinent questions", those are just some of the first ones to pop into my own head! - Jordan On Mar 25, 2011, at 7:25 AM, dan sinclair wrote:
I was trying to keep the various forks in line for a while before I stopped working on HotCocoa. If you look at the network graph, there is a fork off of mine which I think contains everything that has been worked on so far. Maybe a good place to start synchronizing from.
dan
On 2011-03-24, at 10:57 PM, Matt Aimonetti wrote:
Jordan, moving to GitHub helped but it also created fragmentation. Everyone is working on its own fork and there is nobody to centralize all the changes in a single repo. I agree that having a MacRuby based Processing like solution would be awesome.
- Matt
On Thu, Mar 24, 2011 at 7:35 PM, Jordan K. Hubbard <jkh@apple.com> wrote:
On Mar 24, 2011, at 5:56 PM, Matt Aimonetti wrote:
Rich just sold his company to Living Social and I'm sure he's really busy ATM. If people are willing to hack on this project and maintain it (the core team won't), we probably should move it to its own repo and give commit rights to people.
Who's interested in created a HotCocoa team?
I thought the project's being on GitHub facilitated this already? You guys should be able to start forking away and coordinating your patches over email if there's any real interest in creating such a team! I think it would be interesting, myself, particularly if it led to the creation of something that could compare to Processing. :)
- Jordan
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
On Mar 25, 2011, at 7:13 PM, "Jordan K. Hubbard" <jkh@apple.com> wrote:
[...]
4. UIKit vs AppKit. Sure, right now only one of them are relevant to MacRuby, but should that change, how might this affect HotCocoa?
See also: http://chameleonproject.org/ -- http://josephholsten.com
On Fri, 25 Mar 2011 17:13:04 -0700 "Jordan K. Hubbard" <jkh@apple.com> wrote:
1. What problem, or problems, is HotCocoa really trying to solve (and does it currently solve them)?
Quoting the web page: "The purpose of HotCocoa is to allow you to use the flexible syntax of Ruby and its dynamic nature to simplify programmatically constructing user interfaces on Mac OS X without an Interface Builder." That seems like a nice goal summary (and a nice goal...) Perry -- Perry E. Metzger perry@piermont.com
participants (10)
-
Buddy Lindsey, Jr.
-
dan sinclair
-
Henry Maddocks
-
Jordan K. Hubbard
-
Joseph Holsten
-
Manfred Stienstra
-
Matt Aimonetti
-
Michael Gehl
-
Perry E. Metzger
-
Thibault Martin-Lagardette