[MacRuby-devel] HotCocoa futures
mrada at marketcircle.com
Fri Dec 23 20:01:37 PST 2011
I think Isaac already answered things fairly well, but I still thought I would throw in my two cents. HotCocoa will be done when Cocoa is dead. Even then, I'm sure there will still be things to do.
The "goal" of HotCocoa, as I see it, is to make Cocoa apps easier to develop and maintain using MacRuby. The problem here is that that is an extremely broad goal. Everything that Isaac listed is currently aided by HotCocoa by using different components of the project.
Some of the components, like the mappings and delegate builder, were designed together and work together nicely; while components like the application builder are completely separate and could become a separate project under the HotCocoa banner in the future. Similarly, the fork of macruby_graphics that exists in the HotCocoa (as `hotcocoa/graphics`) should also become a subproject of HotCocoa in a different repository and released as its own gem.
"Do we want to front end all the AppKit classes?" No, not unless it can be justified, and I don't think it can. Also, while AppKit may have been the original motivation for mappings, any class in any framework can have a mapping added. Mappings are justified if they make using the class flow more nicely/succinctly with the rest of the code you write, or if it advantageous to get a feature like block based delegation. Even if a mapping would not be useful in general, you can still write it and load mappings yourself.
"...provide convenience functions if and only when a certain conciseness (as expressed in percentage of code saved) is achievable?" This is similar to what I said above, except it gives a specific heuristic, percentage of code saved, which I think is not quite accurate. It is about making things easier to code/understand/maintain, which isn't always the smallest amount of code. For instance, masking in HotCocoa is just an array of symbols which I think is a bit more verbose looking than a chain of XOR'd constants; though since the symbols don't include the Cocoa prefix (i.e. NSAnnoyingPrefix) it ends up looking shorter than the equivalent Objective-C code.
However, HotCocoa can't do everything for everyone with the amount of resources it has now. Personally I will be focusing on updating and strengthening the existing components. I haven't been able to give HotCocoa the love it deserves in the last few months as I was busy with school. That being said, I'm not the only person working on HotCocoa, and the project has been moving ahead thanks to other contributors. I won't be in school for the next few months, so I'll have more time for HotCocoa again.
We have plans to improve documentation and promote the project in the next year, and hopefully that will help answer these questions in better detail.
On 2011-12-23, at 4:21 PM, isaac kearse wrote:
> Hi Rich,
> Thanks for starting a new thread - I was just getting ready to pollute
> the future of MacRuby thread with some more HotCocoa talk :)
> "The goal of the project is to simplify the process of creating and
> configuring Cocoa objects used when building native Mac apps"
> We should probably do a better job of explaining what this means in
> more detail - I have opened an issue for this here:
> Writing more concise code is great, but I wouldn't say it is my
> primary motivation, here are some other reasons why I use HotCocoa:
> * It helps you to write clearer and more idiomatic MacRuby code
> * Express your UI in code rather than IB
> * Makes it easier to use Xcode alternatives like TextMate
> * Helps you to package your code
> * Provides a basic structure for your project
> On Sat, Dec 24, 2011 at 9:25 AM, Rich Morin <rdm at cfcl.com> wrote:
>> At 7:29 PM +0100 12/23/11, Jordan K. Hubbard wrote:
>>> On Dec 23, 2011, at 2:47 AM, isaac kearse wrote:
>>> Are you aware that HotCocoa is being actively developed again?
>>> That's good to know. It would also be good to know, if and
>>> when the subject ever comes up, what its mission statement
>>> currently is. Front-end all of AppKit? All of AppKit AND
>>> Foundation? Neither of those, but provide convenience
>>> functions if and only when a certain conciseness (as
>>> expressed in percentage of code saved) is achievable? This
>>> is something I have been wondering ever since Rich started
>>> the project, since it definitely achieves an admirable degree
>>> of brevity over the equivalent ObjC code, but where do you
>>> stop? How will we know when HotCocoa is "done"? :-)
>> I'm not all that worried about whether HotCocoa is ever "done",
>> but I do think there are some interesting questions about how
>> additions should be managed. As Jordan suggests, there could
>> be rules for accepting additions, eg:
>> ... if and only when a certain conciseness (as expressed in
>> percentage of code saved) is achievable ...
>> Details aside, it can be good to know what kinds of things are
>> likely to be accepted (or rejected) without much discussion.
>> That said, I would like HotCocoa to be a continuing dialogue
>> for ways to make MacRuby code clearer and more idiomatic.
>> I think that "code forums" such as GitHub are extremely well
>> suited to this sort of dialogue. If I want to try out a new
>> idiom or feature, I can simply fork the project and hack. If
>> my work shows promise, I can push it back to GitHub and make
>> an announcement.
>> The trickier question is how to get reliable infrastructure
>> out of such a dialogue. The traditional approach involves a
>> cabal of "core committers", but Git and GitHub projects are
>> not required to be organized in this fashion.
>> In any case, I'm not particularly worried. If we have robust
>> participation in HotCocoa use and development, the details
>> can and will be worked out.
>> http://www.cfcl.com/rdm Rich Morin
>> http://www.cfcl.com/rdm/resume rdm at cfcl.com
>> http://www.cfcl.com/rdm/weblog +1 650-873-7841
>> Software system design, development, and documentation
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
More information about the MacRuby-devel