Re: [MacRuby-devel] [YARD] Troubles with YARD on MacRuby 0.6

2010-10-03 Thread Laurent Sansonetti
I believe this bug has been fixed in trunk a couple weeks ago.

$ ./miniruby -e 'p "%-8s" % [:symbol]'
"symbol  "

Laurent

On Oct 2, 2010, at 10:31 PM, Rich Morin wrote:

> I happen to be on both lists, so I saw this:
> 
> At 1:24 AM -0400 10/3/10, Loren Segal wrote:
>>  Just to clarify, the offending line seems to be:
>> 
>> 
>> http://github.com/lsegal/yard/blob/master/lib/yard/cli/command_parser.rb#L82
>> 
>> MacRuby doesn't seem to be able to do:
>> 
>> "%-8s" % [:symbol]
>> 
>> Or:
>> 
>> sprintf("%-8s", :symbol)
>> 
>> Note that it's fine with "%s", but any form of width formatting screws
>> it up. This works fine in all other Rubies, so it's definitely a MacRuby
>> specific problem with the stdlib implementation. You should report this
>> with them.
> -- 
> http://www.cfcl.com/rdmRich Morin
> http://www.cfcl.com/rdm/resume r...@cfcl.com
> http://www.cfcl.com/rdm/weblog +1 650-873-7841
> 
> Technical editing and writing, programming, system design
> ___
> 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


Re: [MacRuby-devel] Hotcocoa documentation

2010-10-03 Thread Felix Holmgren
In my understanding, HotCocoa is not only useful for UI programming,
although it's true that those classes often need a lot of
configuration and so benefit a lot from a wrapper. I think possible
problems inherent in the approach might be a certain arbitrariness
when defining defaults, and the continual effort to track changes in
the Cocoa APIs themselves. Also, if one is likely to move to using the
Cocoa classes directly sooner or later, it might not be worth the
effort to first use HotCocoa, even if it makes it easy to get started
on a project.

/Felix

2010/10/2 Jordan K. Hubbard :
> I think the issue wasn't that HotCocoa was "dropped" so much as people, 
> including its primary author, seemed to simply lose interest in updating it.  
> That is why the project was moved to github, in hopes that someone else would 
> fork it and start doing interesting things with the project again.
>
> Bigger picture, I think the lack of interest also stems from the fact that 
> it's generally a lot easier to do User Interface programming in Interface 
> Builder, and a set of what are in effect UI element macros can only go so far 
> in papering over the more intricate details of implementing a Cocoa app.  
> From an evolutionary standpoint, it's hard to argue that HotCocoa isn't 
> something of a dead-end, though that's also describing HotCocoa in its 
> *current* form.  The success of high-level development toolkits like 
> Processing (in Java) suggests that there is a place for very high-level, 
> concise ways of making pretty graphics on the screen or interesting sounds 
> come out the speakers, and with a fair bit more work it's possible that 
> HotCocoa could become that.  But not without volunteers to work on it. :-)
>
> - Jordan
>
> On Oct 1, 2010, at 10:34 PM, Felix Holmgren wrote:
>
>> Is there some information somewhere about why Hotcocoa was dropped? If
>> not, a few words of explanation here would be appreciated! Hotcocoa
>> does stand out as a pretty nifty gadget, although I can imagine it's a
>> lot of work to maintain it.
>>
>> /Felix
>>
>> 2010/10/2 Laurent Sansonetti :
>>> Hi Michael,
>>>
>>> On Oct 1, 2010, at 7:07 PM, Michael Sokol wrote:
>>>
 Hello

 I just discovered Macruby and Hotcocoa, and I must say that I'm very 
 excited about it. Hotcocoa is nothing short of amazing and I love the ease 
 with which you can build a Mac application using Ruby.

 The only problem I have though, is that I didn't find a real documentation 
 showing hotcocoa API. I'm using the examples, but it's very limited. I was 
 wondering if any API documentation exists, and if not, what is the best 
 way to know each methods available and their parameters?
>>>
>>> I am afraid HotCocoa is no longer actively developed neither maintained (I 
>>> recommend to avoid using it). The project lives on github now and people 
>>> willing to help should do it there.
>>>
>>> http://github.com/richkilmer/hotcocoa
>>>
>>> Laurent
>> ___
>> 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] RoxorThreadRaisException with Ruby Thread

2010-10-03 Thread Shaun August
*Hi There,*

*
*

*I am using a number of ruby threads in an application and I am getting a
random error of RoxorThreadRaisException. I have read through some of the
bugs and I am wondering if I should switch over to NSThread? Is the ruby
thread stable?*

*
*

**
*

Thanks,


Shaun
*

*
*

*
*

*
*
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


Re: [MacRuby-devel] RoxorThreadRaisException with Ruby Thread

2010-10-03 Thread Laurent Sansonetti
Hi Shaun,

Yes, Ruby threads should be stable. Could you verify if you reproduce the 
problem with a nightly build? http://www.macruby.org/files/nightlies/

If yes, please file a ticket with a backtrace, and if possible, a reduction.

Thanks,
Laurent

On Oct 3, 2010, at 4:38 PM, Shaun August wrote:

> Hi There,
> 
> I am using a number of ruby threads in an application and I am getting a 
> random error of RoxorThreadRaisException. I have read through some of the 
> bugs and I am wondering if I should switch over to NSThread? Is the ruby 
> thread stable?
> 
> Thanks,
> 
> Shaun
> 
> 
> 
> 
> ___
> 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] MacRuby Document-based Application template seems a bit broken

2010-10-03 Thread Caio Chassot
I had to make the following changes to make it work:

- Change File's Owner class to MyDocument
- Connect File's Owner window to Window
- Connect Window's deletage to File's Owner

Makes sense?


I'd submit a patch but OMG so much ugly XML. Is this the right way to do it? 
Edit it in Interface Builder and commit all that junk it changes?

___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel