I encountered same issue, the methods:
- (NSInteger)sourceList:(PXSourceList*)aSourceList badgeValueForItem:(id)item
- (NSUInteger)sourceList:(PXSourceList*)sourceList
numberOfChildrenOfItem:(id)item
is where the BAD_ACCESS happens.
If i implement those methods in Obj-C, subclass it in ruby and
Hi Robert,
Thank you for bring up this.
Would you give your insight on a similar issue?
I have uploaded a demo project: https://github.com/siuying/MacRubyPXListView
The core is RBListDelegate
(https://github.com/siuying/MacRubyPXListView/blob/3ba0f925c2ef535a95fd5858f7e8fa476ca9e0e8/MacRuby
sinatra-recipes (https://github.com/sinatra/sinatra-recipes) work really good.
I can help to bootstrap a page like that!
Jordan K. Hubbard 於 2012年2月12日 上午6:04 寫道：
>
> On Feb 11, 2012, at 1:55 PM, Kevin Poorman wrote:
>
>> All joking aside, I believe you're 100% right. That said, if the communi
tried to use rocco to generate documents with the source, with minimal changes,
the site look like this:
http://macruby-recipes.heroku.com/
sources:
https://github.com/siuying/macruby-recipes
Jordan K. Hubbard 於 2012年2月12日 上午6:04 寫道：
>
> On Feb 11, 2012, at 1:55 PM, Kevin Poorman wrote:
Nope, ARC work on compiler level. MacRuby runtime have nothing to do with it.
Currently the GC do these retain and release for us, if they are to be removed
in future release of OS X, we have to build our own GC for MacRuby. It would be
great because we are no longer limit by Apple to bring Mac
Thank you for your update. It's sad that Apple seems abandon the MacRuby
project, but this is also a chance to bring MacRuby closer to what we (as
developers and users) need instead of what Apple want.
I certainly agree that removing libauto is a primary goal, as OSX and iOS are
both going to
