Hi guys, Things are shaping pretty nicely in trunk and we expect to release the second beta in a few days. We receive bug reports every day, it's great that people are testing it, and the final release will be awesome :-) If you are interested in contributing to the project and you do not have the time or expertise to learn the source code & contribute patches, there are still crucial things that you could do: 1) Test as many Ruby code (gems, libraries) as possible with MacRuby and report us feedback, if the code crashes, runs slowly or leaks all your memory. If you report a runtime crash, it would be even better if you could take the time to reduce the problem into a few lines of Ruby, this saves us (well, me :)) time. Things we don't run yet (but should): rspec, mocha, activesupport (that's a big one!), etc. 2) Write Cocoa samples! MacRuby ships with a few samples but we desperately need more & better ones. If you play with MacRuby to do Cocoa development and use a specific framework/feature, it would be awesome if you could contribute it back as a sample application. Things we do not cover in samples: core data, bindings, opengl, many Cocoa classes, etc. 3) Document your experience as part of a website tutorial or recipe. We are trying to build a "documentation center" for MacRuby resources at http://www.macruby.org/documentation.html and we desperately need more content. Contributing new or enhancing existing content would be greatly appreciated. Thanks! Laurent
I created a document on Hotcocoa and Core Data (http://everburning.com/news/hotcocoa-and-core-data/ ) a while ago when I was poking at it. There is a patch in Trac to have the .xcdatamodel files compiled automatically by Rake. Not sure if it ever got looked at. dan On Nov 1, 2009, at 3:36 PM, Laurent Sansonetti wrote:
Hi guys,
Things are shaping pretty nicely in trunk and we expect to release the second beta in a few days. We receive bug reports every day, it's great that people are testing it, and the final release will be awesome :-)
If you are interested in contributing to the project and you do not have the time or expertise to learn the source code & contribute patches, there are still crucial things that you could do:
1) Test as many Ruby code (gems, libraries) as possible with MacRuby and report us feedback, if the code crashes, runs slowly or leaks all your memory. If you report a runtime crash, it would be even better if you could take the time to reduce the problem into a few lines of Ruby, this saves us (well, me :)) time. Things we don't run yet (but should): rspec, mocha, activesupport (that's a big one!), etc.
2) Write Cocoa samples! MacRuby ships with a few samples but we desperately need more & better ones. If you play with MacRuby to do Cocoa development and use a specific framework/feature, it would be awesome if you could contribute it back as a sample application. Things we do not cover in samples: core data, bindings, opengl, many Cocoa classes, etc.
3) Document your experience as part of a website tutorial or recipe. We are trying to build a "documentation center" for MacRuby resources at http://www.macruby.org/documentation.html and we desperately need more content. Contributing new or enhancing existing content would be greatly appreciated.
Thanks!
Laurent _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Thanks for the remainder. HotCocoa is unfortunately not actively maintained anymore, but we will address that soon! Laurent On Nov 1, 2009, at 4:40 PM, dan sinclair wrote:
I created a document on Hotcocoa and Core Data (http://everburning.com/news/hotcocoa-and-core-data/ ) a while ago when I was poking at it. There is a patch in Trac to have the .xcdatamodel files compiled automatically by Rake. Not sure if it ever got looked at.
dan
On Nov 1, 2009, at 3:36 PM, Laurent Sansonetti wrote:
Hi guys,
Things are shaping pretty nicely in trunk and we expect to release the second beta in a few days. We receive bug reports every day, it's great that people are testing it, and the final release will be awesome :-)
If you are interested in contributing to the project and you do not have the time or expertise to learn the source code & contribute patches, there are still crucial things that you could do:
1) Test as many Ruby code (gems, libraries) as possible with MacRuby and report us feedback, if the code crashes, runs slowly or leaks all your memory. If you report a runtime crash, it would be even better if you could take the time to reduce the problem into a few lines of Ruby, this saves us (well, me :)) time. Things we don't run yet (but should): rspec, mocha, activesupport (that's a big one!), etc.
2) Write Cocoa samples! MacRuby ships with a few samples but we desperately need more & better ones. If you play with MacRuby to do Cocoa development and use a specific framework/feature, it would be awesome if you could contribute it back as a sample application. Things we do not cover in samples: core data, bindings, opengl, many Cocoa classes, etc.
3) Document your experience as part of a website tutorial or recipe. We are trying to build a "documentation center" for MacRuby resources at http://www.macruby.org/documentation.html and we desperately need more content. Contributing new or enhancing existing content would be greatly appreciated.
Thanks!
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
On Sun, Nov 1, 2009 at 12:36 PM, Laurent Sansonetti <lsansonetti@apple.com>wrote:
Hi guys,
Things are shaping pretty nicely in trunk and we expect to release the second beta in a few days. We receive bug reports every day, it's great that people are testing it, and the final release will be awesome :-)
If you are interested in contributing to the project and you do not have the time or expertise to learn the source code & contribute patches, there are still crucial things that you could do:
I have the following questions in regards to submitting code/patches: 1) Is there an Xcode project file for operating on the source? 2) How does properly create a patch file for submittal and should this be filed as a ticket?
1) Test as many Ruby code (gems, libraries) as possible with MacRuby and report us feedback, if the code crashes, runs slowly or leaks all your memory. If you report a runtime crash, it would be even better if you could take the time to reduce the problem into a few lines of Ruby, this saves us (well, me :)) time. Things we don't run yet (but should): rspec, mocha, activesupport (that's a big one!), etc.
Yes, activesupport is keeping from playing with activemodel at the moment. Also, RSpec, at the absolute minimum, would be a great addition to the MacRuby project. Is anyone working on activesupport at the moment?
2) Write Cocoa samples! MacRuby ships with a few samples but we desperately
need more & better ones. If you play with MacRuby to do Cocoa development and use a specific framework/feature, it would be awesome if you could contribute it back as a sample application. Things we do not cover in samples: core data, bindings, opengl, many Cocoa classes, etc.
3) Document your experience as part of a website tutorial or recipe. We are trying to build a "documentation center" for MacRuby resources at http://www.macruby.org/documentation.html and we desperately need more content. Contributing new or enhancing existing content would be greatly appreciated.
Thanks!
Laurent
Thanks in advance for any input in regards to the above. -Conrad
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Hi, On Nov 1, 2009, at 5:04 PM, Conrad Taylor wrote:
On Sun, Nov 1, 2009 at 12:36 PM, Laurent Sansonetti <lsansonetti@apple.com
wrote: Hi guys,
Things are shaping pretty nicely in trunk and we expect to release the second beta in a few days. We receive bug reports every day, it's great that people are testing it, and the final release will be awesome :-)
If you are interested in contributing to the project and you do not have the time or expertise to learn the source code & contribute patches, there are still crucial things that you could do:
I have the following questions in regards to submitting code/patches:
1) Is there an Xcode project file for operating on the source?
No, there isn't.
2) How does properly create a patch file for submittal and should this be filed as a ticket?
I recommend using the patch functionality of the SCM you're using. If you work with SVN, you can simply change files, then: $ svn diff > patch.diff And you can enclose the .diff file to a Trac ticket. .
1) Test as many Ruby code (gems, libraries) as possible with MacRuby and report us feedback, if the code crashes, runs slowly or leaks all your memory. If you report a runtime crash, it would be even better if you could take the time to reduce the problem into a few lines of Ruby, this saves us (well, me :)) time. Things we don't run yet (but should): rspec, mocha, activesupport (that's a big one!), etc.
Yes, activesupport is keeping from playing with activemodel at the moment. Also, RSpec, at the absolute minimum, would be a great addition to the MacRuby project. Is anyone working on activesupport at the moment?
I looked a few weeks ago and noted a few bugs, that have been fixed since. It's a perpetual approach, trying to run something, hitting a bug, reducing it, fixing it, etc. I would prefer to have rspec working first, though :-) AFAIK nobody is working on this yet. Laurent
On Sun, Nov 1, 2009 at 5:19 PM, Laurent Sansonetti <lsansonetti@apple.com>wrote:
Hi,
On Nov 1, 2009, at 5:04 PM, Conrad Taylor wrote:
On Sun, Nov 1, 2009 at 12:36 PM, Laurent Sansonetti <
lsansonetti@apple.com> wrote: Hi guys,
Things are shaping pretty nicely in trunk and we expect to release the second beta in a few days. We receive bug reports every day, it's great that people are testing it, and the final release will be awesome :-)
If you are interested in contributing to the project and you do not have the time or expertise to learn the source code & contribute patches, there are still crucial things that you could do:
I have the following questions in regards to submitting code/patches:
1) Is there an Xcode project file for operating on the source?
No, there isn't.
So, you tend to do something similar the following: 1) [ create and ] execute the appropriate spec 2) edit the code 3) rake 4) if spec_passes? go to (5). Otherwise go to (2) 5) move to the next issue
2) How does properly create a patch file for submittal and should this be
filed as a ticket?
I recommend using the patch functionality of the SCM you're using. If you work with SVN, you can simply change files, then:
$ svn diff > patch.diff
And you can enclose the .diff file to a Trac ticket.
.
1) Test as many Ruby code (gems, libraries) as possible with MacRuby and report us feedback, if the code crashes, runs slowly or leaks all your memory. If you report a runtime crash, it would be even better if you could take the time to reduce the problem into a few lines of Ruby, this saves us (well, me :)) time. Things we don't run yet (but should): rspec, mocha, activesupport (that's a big one!), etc.
Yes, activesupport is keeping from playing with activemodel at the moment. Also, RSpec, at the absolute minimum, would be a great addition to the MacRuby project. Is anyone working on activesupport at the moment?
I looked a few weeks ago and noted a few bugs, that have been fixed since. It's a perpetual approach, trying to run something, hitting a bug, reducing it, fixing it, etc.
I would prefer to have rspec working first, though :-)
Laurent, I will take a look at RSpec this week. -Conrad
AFAIK nobody is working on this yet.
Laurent
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
participants (3)
-
Conrad Taylor
-
dan sinclair
-
Laurent Sansonetti