date:20090529

Re: [MacRuby-devel] Experimental branch status

2009-05-29 Thread Eloy Duran


Hi, another not-Laurent here,

On the topic of the RubySpec, which Jordan mentions as RSpecs; I have  
written a README on how to help out with the specs:

http://github.com/alloy/mr-experimental/blob/master/spec/README.rdoc

Cheers,
Eloy

On 29 mei 2009, at 06:35, Jordan K. Hubbard wrote:



On May 28, 2009, at 8:15 PM, Giampiero De Ciantis wrote:

Btw, if you were to pick one thing that you would say "I wish  
someone in the community would do " what would  
that item be? I have been trying to see where I can contribute, but  
I haven't participated in an open source project before and I don't  
want to waste other people's and my own time doing something of low  
value.



I'm not Laurent, but I do have a list of such things:

1. Volunteers to help maintain the web site and handle "PR" when the  
project's primary developers are busy doing other things (like  
hacking on code).  Sometimes that might involve collating/reporting  
on MacRuby-related developments in the MacRuby blog, since what's a  
blog without regular entries, and other times that might involving  
sending folks like Laurent and/or Rich messages on a semi-regular  
basis, encouraging them to provide a quick list of status bullets  
which the volunteers can then format and edit appropriately for the  
web site, again sparing the primary developers some of the admin  
work (and serving as their alarm clock to provide information to the  
masses :).


2. Writing tutorials / sample code for MacRuby, since anyone who's  
new to the project needs a place to start.


3. Writing RSpecs for MacRuby.

4. Reporting bugs, writing docs, providing words of encouragement,  
etc. :)


- Jordan

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Experimental branch status

2009-05-29 Thread Chuck Remes

How is progress on support FFI? That seems to be the new ruby-way for  
interfacing to native code supported by JRuby, Rubinius and to some  
extent the 1.9.x codeline. With FFI built in, as gems are updated to  
support the other ruby interpreters and/or compilers then MacRuby  
would be supported for "free" through those efforts.


cr

On May 28, 2009, at 11:42 PM, Matt Aimonetti wrote:

The other thing that needs to be done is to port/fix the popular  
Ruby gems which don't work on MacRuby yet. Also, writing wrappers  
for common obj-c libraries/frameworks would be very useful.


If you are interested in writing tutorials/articles, feel free to  
contact me offline so I can show you how to use our blog engine  
tool. (I think Rich is planning on releasing a tutorial on how to do  
that, but that might not happen right away)


- Matt

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Experimental branch status: C-lib wrappers

2009-05-29 Thread Charles Turner


On May 29, 2009, at 12:42 AM, Matt Aimonetti wrote:

Also, writing wrappers for common obj-c libraries/frameworks would  
be very useful.


I could contribute a few of these, but as I'm new to Cocoa (and only  
less so Ruby) I'm still casting around for manuals and examples to RTFM.


Somewhat worse, I have a few C-libs working with FFI in the 1.9.1  
release, so that's actually hindering my progress with MacRuby. (Path  
of least resistance, ya know.)


My newbiness also has me thinking about very thin wrappings. Just  
enough to get the C functions working.


So if anyone has pointer to info and source examples, I'd be grateful.

Thanks!

Charles

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Experimental branch status

2009-05-29 Thread Eloy Duran

I haven't actively spoken about this with Laurent over the last week,  
but afaik not much changed since last time, which means that the  
support is not nearly far enough to start using it. We decided that we  
want the FFI specs in the repo in order to finish this work  
appropriately, which would need work to be converted from RSpec to  
MSpec.


Luckily Brian Ford (from the rubyspec project) was already planning on  
incorporating them. I haven't had time to check if they're in yet. So  
this is another area where people could help out. By porting the ruby- 
ffi specs to mspec and integrating them into the rubyspec.


Cheers,
Eloy

On May 29, 2009, at 1:28 PM, Chuck Remes wrote:

How is progress on support FFI? That seems to be the new ruby-way  
for interfacing to native code supported by JRuby, Rubinius and to  
some extent the 1.9.x codeline. With FFI built in, as gems are  
updated to support the other ruby interpreters and/or compilers then  
MacRuby would be supported for "free" through those efforts.


cr

On May 28, 2009, at 11:42 PM, Matt Aimonetti wrote:

The other thing that needs to be done is to port/fix the popular  
Ruby gems which don't work on MacRuby yet. Also, writing wrappers  
for common obj-c libraries/frameworks would be very useful.


If you are interested in writing tutorials/articles, feel free to  
contact me offline so I can show you how to use our blog engine  
tool. (I think Rich is planning on releasing a tutorial on how to  
do that, but that might not happen right away)


- Matt

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] [MacRuby] #269: Calling a method on a pointer passed to a KVC validation method fails

2009-05-29 Thread MacRuby

#269: Calling a method on a pointer passed to a KVC validation method fails
+---
 Reporter:  mik...@…|   Owner:  lsansone...@…
 Type:  defect  |  Status:  new  
 Priority:  major   |   Milestone:   
Component:  MacRuby |Keywords:  kvc pointer crash
+---
 If I define a -validate:error: method in the class used as an
 NSArrayController's class, any method call on any parameter causes a
 crash.

 == Steps to reproduce: ==

 Create a new MacRuby project.
 Place a table view and a button in the main window.
 Instantiate a new NSArrayController.
 Set the class of the array controller to SomeModel, with the key someKey.
 Bind the table view's single column's value to the array controller's
 arrangedObject.someKey key path, and check Validates Immediately.
 Set the button's target to be the array controller, action add:.

 Create a new Ruby file in the project. Here's the code:

 {{{
 #encoding: utf-8
 class SomeModel
   attr_accessor :someKey

   def validateSomeKey someKeyPointer, error: errorPointer
 NSLog "Validating someKey."
 someKeyPointer.nil? # This is where the program crashes.
 return true
   end
 end
 }}}

 Launch the application, add a new row, try to change its someKey. When you
 press enter, it crashes.

 Attached is the backtrace I get from GDB.

-- 
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] experimental branch: status update

2009-05-29 Thread Laurent Sansonetti


Hi all,

The last status was sent the 4th May, so this one is a bit lengthy. I  
am sorry about that and I will try to do status updates more often.


Before listing the changes, 2 important things happened since and I  
think they need to be mentioned!


- The very first RubyOnOSX conference was held in Amsterdam,  
Netherlands. I had the pleasure to attend it and it was awesome. There  
were about 7 presentations on Ruby on Mac OS X, most of them related  
to MacRuby, and I think that all of them were filmed. Hat tips to  
Fingertips (Eloy, Manfred and Thijs) for the organization. I heard  
they are processing the videos right now, if you are using Twitter you  
can follow http://twitter.com/fngtps for more info.


- Patrick Thompson, our intern, started working full-time from the  
Cupertino offices for 3 months! He will certainly be able to push more  
excellent work during this period.


And now the list of changes.

- The format string APIs were re-implemented on top of a LLVM ->  
CFStringCreateWithFormat() stub.


- libffi was removed from the project build, because it's not used  
anymore!


- Implemented assignment to global values in a multiple assignment  
expression.


- The MacRuby Objective-C class was re-implemented.

- Finished the save of locals when a block transformed into a Proc  
leaves the scope of the function where it was created.


- Implemented assignment to constants in a multiple assignment  
expression.


- A HACKING file was added, for those interested into hacking MacRuby.  
(It's still very preliminary).


- Implemented yield of splat arguments.

- Some work for 10.6 support. 10.6 support is almost as stable as  
10.5, but it has a few caveats and it's still not ready for everyone.


- Re-implemented the way we push blocks in the VM so that it works  
with some strange Ruby behavior (such as `def foo(p=Proc.new); p.call;  
end; foo {}`) and also fixed numerous blocks-related bugs.


- Make sure primitive classes can be subclassed again, fixed  
immutability check.


- Improved String#<< and str_modifiable() check.

- Fixed a bug when using negative indexes to Array#[] (in the  
optimized primitive).


- Implemented $! as well as the way we save current exceptions in the  
VM. Also fixed a few exceptions-related bugs.


- Fixed bugs in the Method class (principally making sure it's  
statically linked to the method implementation) and also implemented  
Method#to_proc.


- Fixed Hash.new with a block.

- IO work: some ARGF functionality, Kernel#readlines, Kernel#readline,  
IO#pos, IO#read (bugfix), IO#pipe, IO#foreach, IO#sysopen, IO#bytes,  
IO#lines, IO#chars, IO#stat, IO#write (bugfix), Kernel#syscall,


- Implemented a very basic AOT compiler, which is available via the -- 
compile command-line option of the miniruby/macruby executable. It  
compiles the given Ruby expression or file into a binary, by  
translating the LLVM IR into machine code, statically. The resulted  
binary does not parse/compile anything anymore. This is a proof of  
concept and it only supports a limited set of the Ruby language for  
now, but it will be extended later.


- The big roxor.cpp source file (> 11K lines) was split into several  
small files: vm.{cpp|h}, compiler.{cpp|h}, bridgesupport.{cpp|h}. The  
codebase is now easier to maintain and also faster to build during  
development.


- Added support for calling pure Ruby method starting with a regular  
argument then an optional Hash argument.


- Fixed the internal str_new() function to not create unnecessary  
Bytestring objects.


- Fixed a lazy JIT bug when dealing with modules included in modules  
then included in classes.


- Fixed a bug when copying Objective-C methods upon module inclusion  
that have not been resolved (non-JIT'ed) yet into subclasses.


- Fixed the overwriting of Objective-C methods accepting an argument  
whose size is larger than 128-bit (ABI conformance).


- Implemented informal protocol method definition.

- Fixed several misc bugs in the compiler when compiling Objective-C  
stubs.


- Ported the math.c and random.c files to the new runtime APIs.

- Ruby exceptions can now be caught by Objective-C (64-bit only).

- Define -allocWithZone: and not -alloc on every new NSObject pure  
Ruby subclass (IB/nib support).


- Allow true/false to be passed as numeric C types.

As you can see lots of things changed since the last status update,  
and the more relevant thing is that the project is now installable  
again. You can do rake and rake install. We passed several "internal"  
milestones in order to reach this point.


Also, some Cocoa support work was done and several sample code  
applications work again. Some don't, but we are working on that.


The experimental branch is not ready yet to replace trunk, but I think  
we are progressing well, slowly but surely.


If you are interested into installing the experimental branch, keep in  
mind that:


1) It's not as stable as trunk yet, and the installation

Re: [MacRuby-devel] experimental branch: status update

2009-05-29 Thread Rich Morin

As of revision 1634, my PPC build is still failing in spots.
See http://cfcl.com/rdm/macruby/2009.0529.0500 for details.

-r


...
You appear to be using a PowerPC machine. MacRuby's primary
  architectures are Intel 32-bit and 64-bit (i386 and x86_64).
  Consequently, PowerPC support may be lacking some features.
./mspec/bin/mspec ci -B ./spec/macruby.mspec ...
(in .../2009.0529.0500/macruby-experimental)
MacRuby version 0.5 (ruby 1.9.0) [universal-darwin9.0, ppc]
2009-05-29 05:07:12.116 miniruby[50581:717]
  *** Terminating app due to uncaught exception 'RuntimeError',
  reason: 'can't modify frozen/immutable array'
2009-05-29 05:07:12.304 miniruby[50581:717] Stack: (
2478378432,
2426381548,
1325972,
207312,
201556,
11728,
24660,
...

...
6000 ensure w/o exception   0.54   0.00   0.54 (  0.608066)
5 raise   2009-05-29 05:08:34.144 miniruby[50633:10b]
  *** Terminating app due to uncaught exception 'RuntimeError', reason: ''
2009-05-29 05:08:34.200 miniruby[50633:10b] Stack: (
2478378432,
2426381548,
1325972,
214128,
...
)
rake aborted!
Command failed with status (): [./miniruby -I./lib bench.rb...]
...

-- 
http://www.cfcl.com/rdmRich Morin
http://www.cfcl.com/rdm/resume [email protected]
http://www.cfcl.com/rdm/weblog +1 650-873-7841

Technical editing and writing, programming, and web development
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] Tim added you as a friend on MyLife!

2009-05-29 Thread Tim Rand

Tim Rand added you as a friend on MyLife(TM).
Please confirm you know Tim so we can connect you.

Do You Know Tim?

YES - Connect with Tim, and see who's searching for you

http://smtp26.mail.reunion.com:80/track?type=click&mailingid=68900&messageid=9300&databaseid=1238061926&serial=1228209694&emailid=macruby-de...@lists.macosforge.org&userid=251423&extra=&&&2002&&&http://www.mylife.com/showInviteRegistration.do?uid=357900586&invitee=macruby-de...@lists.macosforge.org

NO - I don't know Tim 
http://smtp26.mail.reunion.com:80/track?type=click&mailingid=68900&messageid=9300&databaseid=1238061926&serial=1228209694&emailid=macruby-de...@lists.macosforge.org&userid=251423&extra=&&&2000&&&http://www.mylife.com/showInviteRegistration.do?unsub=true&invitee=macruby-de...@lists.macosforge.org&uid=357900586

~~

MyLife - Find everyone. All in one place.(TM) 

You have received this email because a MyLife member sent an 
invitation to
this email address. For assistance, please refer to our FAQ or 
Contact Us:

http://smtp26.mail.reunion.com:80/track?type=click&mailingid=68900&messageid=9300&databaseid=1238061926&serial=1228209694&emailid=macruby-de...@lists.macosforge.org&userid=251423&extra=&&&2001&&&http://help.mylife.com/

Our Address: 2118 Wilshire Blvd., Box 1008, Santa Monica, CA 
90403-5784

Copyright (c) 2009 MyLife.com, Inc. All Rights Reserved.
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] experimental branch: status update

2009-05-29 Thread Laurent Sansonetti


Hi Rich,

I forgot to mention that 32-bit support is a bit b0rked for now, which  
is probably what's problematic in your case.


Laurent

On May 29, 2009, at 1:59 PM, Rich Morin wrote:


As of revision 1634, my PPC build is still failing in spots.
See http://cfcl.com/rdm/macruby/2009.0529.0500 for details.

-r


...
You appear to be using a PowerPC machine. MacRuby's primary
 architectures are Intel 32-bit and 64-bit (i386 and x86_64).
 Consequently, PowerPC support may be lacking some features.
./mspec/bin/mspec ci -B ./spec/macruby.mspec ...
(in .../2009.0529.0500/macruby-experimental)
MacRuby version 0.5 (ruby 1.9.0) [universal-darwin9.0, ppc]
2009-05-29 05:07:12.116 miniruby[50581:717]
 *** Terminating app due to uncaught exception 'RuntimeError',
 reason: 'can't modify frozen/immutable array'
2009-05-29 05:07:12.304 miniruby[50581:717] Stack: (
   2478378432,
   2426381548,
   1325972,
   207312,
   201556,
   11728,
   24660,
...

...
6000 ensure w/o exception   0.54   0.00   0.54  
(  0.608066)
5 raise   2009-05-29 05:08:34.144  
miniruby[50633:10b]
 *** Terminating app due to uncaught exception 'RuntimeError',  
reason: ''

2009-05-29 05:08:34.200 miniruby[50633:10b] Stack: (
   2478378432,
   2426381548,
   1325972,
   214128,
   ...
)
rake aborted!
Command failed with status (): [./miniruby -I./lib bench.rb...]
...

--
http://www.cfcl.com/rdmRich Morin
http://www.cfcl.com/rdm/resume [email protected]
http://www.cfcl.com/rdm/weblog +1 650-873-7841

Technical editing and writing, programming, and web development
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Tim added you as a friend on MyLife!

2009-05-29 Thread Rich Morin

At 14:01 -0700 5/29/09, Tim Rand wrote:
>
> Tim Rand added you as a friend on MyLife.
> Please confirm you know Tim so we can connect you.
> Do you know Tim?

Sorry, Tim, MacRuby likes you, but is too busy right now
(what with all the surgery, etc.) for social networking.

-r
-- 
http://www.cfcl.com/rdmRich Morin
http://www.cfcl.com/rdm/resume [email protected]
http://www.cfcl.com/rdm/weblog +1 650-873-7841

Technical editing and writing, programming, and web development
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] [MacRuby] #257: Conversion to JSON works , But JSON parsing fails in MacRuby 0.4

2009-05-29 Thread MacRuby

#257: Conversion to JSON works , But JSON parsing fails in MacRuby 0.4
---+
 Reporter:  nex...@…   |Owner:  lsansone...@…
 Type:  defect |   Status:  closed   
 Priority:  blocker|Milestone:  MacRuby 0.5  
Component:  MacRuby|   Resolution:  fixed
 Keywords:  json   |  
---+
Changes (by lsansone...@…):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 Merged to both trunk and experimental. Thanks for the patch Dan!

-- 
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Tim added you as a friend on MyLife!

2009-05-29 Thread Eloy Duran


Spot on :)

On 29 mei 2009, at 23:10, Rich Morin wrote:


At 14:01 -0700 5/29/09, Tim Rand wrote:


Tim Rand added you as a friend on MyLife™.
Please confirm you know Tim so we can connect you.
Do you know Tim?


Sorry, Tim, MacRuby likes you, but is too busy right now
(what with all the surgery, etc.) for social networking.

-r
--
http://www.cfcl.com/rdmRich Morin
http://www.cfcl.com/rdm/resume [email protected]
http://www.cfcl.com/rdm/weblog +1 650-873-7841

Technical editing and writing, programming, and web development
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] Contributions (Was: Experimental branch status)

2009-05-29 Thread Laurent Sansonetti


So, to recap, I think the following contributions will be welcome:

- Maintaining the website (blog, content, etc.) and writing tutorials.  
There are lots of very interesting blog posts around that could I  
think be transformed into a tutorial or into a recipe (shorter  
tutorial). I think we need more recipes, for instance how to embed  
MacRuby in your app, how to use a specific and complex Cocoa class  
(NSOutlineView/NSTableView/etc.) in Ruby, etc.


- Writing / translating sample code for MacRuby. We will bundle it in  
the MacRuby distribution. If you wrote anything interesting in MacRuby  
that could be used as a sample code, let us now. Creating new sample  
code is cool, but porting an existing Objective-C sample code is good  
too.


- Specs: working on the 1.8 -> 1.9 rubyspec transition (see Eloy's  
message above). Eloy is currently doing all the specs maintenance as  
well and I think he will not be against help :) Also, we recently  
started writing MacRuby-specific specs, they need to be extended.  
Finally, we need to start working on passing the core specs (we only  
did language so far).


- Porting C extensions to the Ruby FFI API. We started working on a  
compatible Ruby FFI API, we still have a plan to support C extensions  
but not in the very near future and the performance will not be great,  
FFI will be faster. Also if most of the well-known C extensions have  
been ported, we might simply decide to not support C extensions, which  
is one less thing to do. Also, working on Ruby FFI-compatible  
libraries will make JRuby / Rubinius / etc. users happy :)


- HotCocoa: I will leave this part to Rich and Matt, but I think they  
will be mostly interested in mappings. Try to create a HotCocoa app,  
then contribute mappings for things that do not exist (or improve the  
existing ones by contributing custom methods, etc.).


- Core: there are lots of things to do, if you feel hacking on the low- 
level bits. We maintain a TODO file which contains a few things that  
still need to be done. At this point, the JIT compiler is almost  
finished (AOT is maybe finished at 10%, though) and the VM is still  
under development. A good way to start hacking is to run the  
test_vm.rb test suite, pick a failing test and try to fix it.  
Contributing new failing tests is also highly welcome, you can simply  
use the miniruby executable and try to make it crash (it's not hard,  
you will see).


- ... anything more? :)

Laurent

On May 29, 2009, at 6:57 AM, Eloy Duran wrote:

I haven't actively spoken about this with Laurent over the last  
week, but afaik not much changed since last time, which means that  
the support is not nearly far enough to start using it. We decided  
that we want the FFI specs in the repo in order to finish this work  
appropriately, which would need work to be converted from RSpec to  
MSpec.


Luckily Brian Ford (from the rubyspec project) was already planning  
on incorporating them. I haven't had time to check if they're in  
yet. So this is another area where people could help out. By porting  
the ruby-ffi specs to mspec and integrating them into the rubyspec.


Cheers,
Eloy

On May 29, 2009, at 1:28 PM, Chuck Remes wrote:

How is progress on support FFI? That seems to be the new ruby-way  
for interfacing to native code supported by JRuby, Rubinius and to  
some extent the 1.9.x codeline. With FFI built in, as gems are  
updated to support the other ruby interpreters and/or compilers  
then MacRuby would be supported for "free" through those efforts.


cr

On May 28, 2009, at 11:42 PM, Matt Aimonetti wrote:

The other thing that needs to be done is to port/fix the popular  
Ruby gems which don't work on MacRuby yet. Also, writing wrappers  
for common obj-c libraries/frameworks would be very useful.


If you are interested in writing tutorials/articles, feel free to  
contact me offline so I can show you how to use our blog engine  
tool. (I think Rich is planning on releasing a tutorial on how to  
do that, but that might not happen right away)


- Matt

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Contributions (Was: Experimental branch status)

2009-05-29 Thread dan sinclair

Is the goal to keep all of the tutorials on the main macruby site? I  
enjoy writing them but prefer to post them to everburning to keep them  
with the rest of my stuff.  If the goal is to have them on the website  
I can port the 3 HotCocoa bits I've written over to whatever it is the  
website uses.


Along with that, there is no good way to get to the trac to view  
tickets on the website. The only link, that I've found, is to use the  
file a ticket section of the contact page and navigate out from there.  
Might be a good idea to make it easier for people to submit bugs/find  
bugs to work on.


dan



On May 29, 2009, at 6:31 PM, Laurent Sansonetti wrote:


So, to recap, I think the following contributions will be welcome:

- Maintaining the website (blog, content, etc.) and writing  
tutorials. There are lots of very interesting blog posts around that  
could I think be transformed into a tutorial or into a recipe  
(shorter tutorial). I think we need more recipes, for instance how  
to embed MacRuby in your app, how to use a specific and complex  
Cocoa class (NSOutlineView/NSTableView/etc.) in Ruby, etc.


- Writing / translating sample code for MacRuby. We will bundle it  
in the MacRuby distribution. If you wrote anything interesting in  
MacRuby that could be used as a sample code, let us now. Creating  
new sample code is cool, but porting an existing Objective-C sample  
code is good too.


- Specs: working on the 1.8 -> 1.9 rubyspec transition (see Eloy's  
message above). Eloy is currently doing all the specs maintenance as  
well and I think he will not be against help :) Also, we recently  
started writing MacRuby-specific specs, they need to be extended.  
Finally, we need to start working on passing the core specs (we only  
did language so far).


- Porting C extensions to the Ruby FFI API. We started working on a  
compatible Ruby FFI API, we still have a plan to support C  
extensions but not in the very near future and the performance will  
not be great, FFI will be faster. Also if most of the well-known C  
extensions have been ported, we might simply decide to not support C  
extensions, which is one less thing to do. Also, working on Ruby FFI- 
compatible libraries will make JRuby / Rubinius / etc. users happy :)


- HotCocoa: I will leave this part to Rich and Matt, but I think  
they will be mostly interested in mappings. Try to create a HotCocoa  
app, then contribute mappings for things that do not exist (or  
improve the existing ones by contributing custom methods, etc.).


- Core: there are lots of things to do, if you feel hacking on the  
low-level bits. We maintain a TODO file which contains a few things  
that still need to be done. At this point, the JIT compiler is  
almost finished (AOT is maybe finished at 10%, though) and the VM is  
still under development. A good way to start hacking is to run the  
test_vm.rb test suite, pick a failing test and try to fix it.  
Contributing new failing tests is also highly welcome, you can  
simply use the miniruby executable and try to make it crash (it's  
not hard, you will see).


- ... anything more? :)

Laurent

On May 29, 2009, at 6:57 AM, Eloy Duran wrote:

I haven't actively spoken about this with Laurent over the last  
week, but afaik not much changed since last time, which means that  
the support is not nearly far enough to start using it. We decided  
that we want the FFI specs in the repo in order to finish this work  
appropriately, which would need work to be converted from RSpec to  
MSpec.


Luckily Brian Ford (from the rubyspec project) was already planning  
on incorporating them. I haven't had time to check if they're in  
yet. So this is another area where people could help out. By  
porting the ruby-ffi specs to mspec and integrating them into the  
rubyspec.


Cheers,
Eloy

On May 29, 2009, at 1:28 PM, Chuck Remes wrote:

How is progress on support FFI? That seems to be the new ruby-way  
for interfacing to native code supported by JRuby, Rubinius and to  
some extent the 1.9.x codeline. With FFI built in, as gems are  
updated to support the other ruby interpreters and/or compilers  
then MacRuby would be supported for "free" through those efforts.


cr

On May 28, 2009, at 11:42 PM, Matt Aimonetti wrote:

The other thing that needs to be done is to port/fix the popular  
Ruby gems which don't work on MacRuby yet. Also, writing wrappers  
for common obj-c libraries/frameworks would be very useful.


If you are interested in writing tutorials/articles, feel free to  
contact me offline so I can show you how to use our blog engine  
tool. (I think Rich is planning on releasing a tutorial on how to  
do that, but that might not happen right away)


- Matt

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
M

Re: [MacRuby-devel] Contributions (Was: Experimental branch status)

2009-05-29 Thread Matt Aimonetti

Dan, if you were able to port your tutorials to the website's format, that
would be very helpful. We are using webby and if you are interested, I can
contact you off list and show you how to generate articles/tutorials.

A tutorial on how to report a bug/submit a fix would also be greatly
appreciated.

- Matt

On Fri, May 29, 2009 at 4:14 PM, dan sinclair  wrote:

> Is the goal to keep all of the tutorials on the main macruby site? I enjoy
> writing them but prefer to post them to everburning to keep them with the
> rest of my stuff.  If the goal is to have them on the website I can port the
> 3 HotCocoa bits I've written over to whatever it is the website uses.
>
> Along with that, there is no good way to get to the trac to view tickets on
> the website. The only link, that I've found, is to use the file a ticket
> section of the contact page and navigate out from there. Might be a good
> idea to make it easier for people to submit bugs/find bugs to work on.
>
> dan
>
>
>
>
> On May 29, 2009, at 6:31 PM, Laurent Sansonetti wrote:
>
>  So, to recap, I think the following contributions will be welcome:
>>
>> - Maintaining the website (blog, content, etc.) and writing tutorials.
>> There are lots of very interesting blog posts around that could I think be
>> transformed into a tutorial or into a recipe (shorter tutorial). I think we
>> need more recipes, for instance how to embed MacRuby in your app, how to use
>> a specific and complex Cocoa class (NSOutlineView/NSTableView/etc.) in Ruby,
>> etc.
>>
>> - Writing / translating sample code for MacRuby. We will bundle it in the
>> MacRuby distribution. If you wrote anything interesting in MacRuby that
>> could be used as a sample code, let us now. Creating new sample code is
>> cool, but porting an existing Objective-C sample code is good too.
>>
>> - Specs: working on the 1.8 -> 1.9 rubyspec transition (see Eloy's message
>> above). Eloy is currently doing all the specs maintenance as well and I
>> think he will not be against help :) Also, we recently started writing
>> MacRuby-specific specs, they need to be extended. Finally, we need to start
>> working on passing the core specs (we only did language so far).
>>
>> - Porting C extensions to the Ruby FFI API. We started working on a
>> compatible Ruby FFI API, we still have a plan to support C extensions but
>> not in the very near future and the performance will not be great, FFI will
>> be faster. Also if most of the well-known C extensions have been ported, we
>> might simply decide to not support C extensions, which is one less thing to
>> do. Also, working on Ruby FFI-compatible libraries will make JRuby /
>> Rubinius / etc. users happy :)
>>
>> - HotCocoa: I will leave this part to Rich and Matt, but I think they will
>> be mostly interested in mappings. Try to create a HotCocoa app, then
>> contribute mappings for things that do not exist (or improve the existing
>> ones by contributing custom methods, etc.).
>>
>> - Core: there are lots of things to do, if you feel hacking on the
>> low-level bits. We maintain a TODO file which contains a few things that
>> still need to be done. At this point, the JIT compiler is almost finished
>> (AOT is maybe finished at 10%, though) and the VM is still under
>> development. A good way to start hacking is to run the test_vm.rb test
>> suite, pick a failing test and try to fix it. Contributing new failing tests
>> is also highly welcome, you can simply use the miniruby executable and try
>> to make it crash (it's not hard, you will see).
>>
>> - ... anything more? :)
>>
>> Laurent
>>
>> On May 29, 2009, at 6:57 AM, Eloy Duran wrote:
>>
>>  I haven't actively spoken about this with Laurent over the last week, but
>>> afaik not much changed since last time, which means that the support is not
>>> nearly far enough to start using it. We decided that we want the FFI specs
>>> in the repo in order to finish this work appropriately, which would need
>>> work to be converted from RSpec to MSpec.
>>>
>>> Luckily Brian Ford (from the rubyspec project) was already planning on
>>> incorporating them. I haven't had time to check if they're in yet. So this
>>> is another area where people could help out. By porting the ruby-ffi specs
>>> to mspec and integrating them into the rubyspec.
>>>
>>> Cheers,
>>> Eloy
>>>
>>> On May 29, 2009, at 1:28 PM, Chuck Remes wrote:
>>>
>>>  How is progress on support FFI? That seems to be the new ruby-way for
 interfacing to native code supported by JRuby, Rubinius and to some extent
 the 1.9.x codeline. With FFI built in, as gems are updated to support the
 other ruby interpreters and/or compilers then MacRuby would be supported 
 for
 "free" through those efforts.

 cr

 On May 28, 2009, at 11:42 PM, Matt Aimonetti wrote:

  The other thing that needs to be done is to port/fix the popular Ruby
> gems which don't work on MacRuby yet. Also, writing wrappers for common
> obj-c libraries/frame

Re: [MacRuby-devel] Contributions (Was: Experimental branch status)

2009-05-29 Thread Laurent Sansonetti

I don't think we need to convert every blog post on the main website,  
but for consistency and maintenance sake I think it's good to have a  
set of interesting tutorials there. Users would have a one-stop-shop  
for documentation and it would be easier for us to update them. The 3  
articles that Dan wrote are a great way to get started with HotCocoa,  
I think. I wonder if we shouldn't simply transform them into the  
"official" HotCocoa tutorial, if Dan agrees of course. We have an  
article regarding HotCocoa mappings that Rich wrote, but I don't think  
we have some introductory documentation yet.


Thoughts?

Laurent

On May 29, 2009, at 4:24 PM, Matt Aimonetti wrote:

Dan, if you were able to port your tutorials to the website's  
format, that would be very helpful. We are using webby and if you  
are interested, I can contact you off list and show you how to  
generate articles/tutorials.


A tutorial on how to report a bug/submit a fix would also be greatly  
appreciated.


- Matt

On Fri, May 29, 2009 at 4:14 PM, dan sinclair   
wrote:
Is the goal to keep all of the tutorials on the main macruby site? I  
enjoy writing them but prefer to post them to everburning to keep  
them with the rest of my stuff.  If the goal is to have them on the  
website I can port the 3 HotCocoa bits I've written over to whatever  
it is the website uses.


Along with that, there is no good way to get to the trac to view  
tickets on the website. The only link, that I've found, is to use  
the file a ticket section of the contact page and navigate out from  
there. Might be a good idea to make it easier for people to submit  
bugs/find bugs to work on.


dan




On May 29, 2009, at 6:31 PM, Laurent Sansonetti wrote:

So, to recap, I think the following contributions will be welcome:

- Maintaining the website (blog, content, etc.) and writing  
tutorials. There are lots of very interesting blog posts around that  
could I think be transformed into a tutorial or into a recipe  
(shorter tutorial). I think we need more recipes, for instance how  
to embed MacRuby in your app, how to use a specific and complex  
Cocoa class (NSOutlineView/NSTableView/etc.) in Ruby, etc.


- Writing / translating sample code for MacRuby. We will bundle it  
in the MacRuby distribution. If you wrote anything interesting in  
MacRuby that could be used as a sample code, let us now. Creating  
new sample code is cool, but porting an existing Objective-C sample  
code is good too.


- Specs: working on the 1.8 -> 1.9 rubyspec transition (see Eloy's  
message above). Eloy is currently doing all the specs maintenance as  
well and I think he will not be against help :) Also, we recently  
started writing MacRuby-specific specs, they need to be extended.  
Finally, we need to start working on passing the core specs (we only  
did language so far).


- Porting C extensions to the Ruby FFI API. We started working on a  
compatible Ruby FFI API, we still have a plan to support C  
extensions but not in the very near future and the performance will  
not be great, FFI will be faster. Also if most of the well-known C  
extensions have been ported, we might simply decide to not support C  
extensions, which is one less thing to do. Also, working on Ruby FFI- 
compatible libraries will make JRuby / Rubinius / etc. users happy :)


- HotCocoa: I will leave this part to Rich and Matt, but I think  
they will be mostly interested in mappings. Try to create a HotCocoa  
app, then contribute mappings for things that do not exist (or  
improve the existing ones by contributing custom methods, etc.).


- Core: there are lots of things to do, if you feel hacking on the  
low-level bits. We maintain a TODO file which contains a few things  
that still need to be done. At this point, the JIT compiler is  
almost finished (AOT is maybe finished at 10%, though) and the VM is  
still under development. A good way to start hacking is to run the  
test_vm.rb test suite, pick a failing test and try to fix it.  
Contributing new failing tests is also highly welcome, you can  
simply use the miniruby executable and try to make it crash (it's  
not hard, you will see).


- ... anything more? :)

Laurent

On May 29, 2009, at 6:57 AM, Eloy Duran wrote:

I haven't actively spoken about this with Laurent over the last  
week, but afaik not much changed since last time, which means that  
the support is not nearly far enough to start using it. We decided  
that we want the FFI specs in the repo in order to finish this work  
appropriately, which would need work to be converted from RSpec to  
MSpec.


Luckily Brian Ford (from the rubyspec project) was already planning  
on incorporating them. I haven't had time to check if they're in  
yet. So this is another area where people could help out. By porting  
the ruby-ffi specs to mspec and integrating them into the rubyspec.


Cheers,
Eloy

On May 29, 2009, at 1:28 PM, Chuck Remes wrote:

How is progress on support FFI? That se

[MacRuby-devel] [MacRuby] #270: [Website] Minor changes

2009-05-29 Thread MacRuby

#270: [Website] Minor changes
-+--
 Reporter:  d...@…|   Owner:  lsansone...@…
 Type:  enhancement  |  Status:  new  
 Priority:  trivial  |   Milestone:   
Component:  MacRuby  |Keywords:  website  
-+--
 Attached is a patch that makes a few minor changes to the website. Adds a
 few extra links, and makes, I think, some of the text a bit better.

-- 
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] [MacRuby] #271: [website] hotcocoa mappings tutorial paragraph wrapping

2009-05-29 Thread MacRuby

#271: [website] hotcocoa mappings tutorial paragraph wrapping
-+--
 Reporter:  d...@…|   Owner:  lsansone...@…
 Type:  enhancement  |  Status:  new  
 Priority:  trivial  |   Milestone:   
Component:  MacRuby  |Keywords:  website  
-+--
 Attached patch fixes the strange paragraph wrapping in parts of the
 HotCocoa mappings tutorial.

-- 
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] [MacRuby] #270: [Website] Minor changes

2009-05-29 Thread MacRuby

#270: [Website] Minor changes
-+--
 Reporter:  d...@…|Owner:  lsansone...@…
 Type:  enhancement  |   Status:  closed   
 Priority:  trivial  |Milestone:   
Component:  MacRuby  |   Resolution:  fixed
 Keywords:  website  |  
-+--
Changes (by mattaimone...@…):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 applied thanks!

-- 
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] [MacRuby] #271: [website] hotcocoa mappings tutorial paragraph wrapping

2009-05-29 Thread MacRuby

#271: [website] hotcocoa mappings tutorial paragraph wrapping
-+--
 Reporter:  d...@…|Owner:  lsansone...@…
 Type:  enhancement  |   Status:  closed   
 Priority:  trivial  |Milestone:   
Component:  MacRuby  |   Resolution:  fixed
 Keywords:  website  |  
-+--
Changes (by mattaimone...@…):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 applied, thanks.

-- 
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] The state of HotCocoa

2009-05-29 Thread Alex Vollmer


Hey folks,

Can anybody speak with some authority on the current state of  
HotCocoa? I seem to recall reading an email on the list that Rich and  
Matt were hacking on some new MVC hotness. Is that intended to replace  
HotCocoa, or just be an alternative?


Cheers,

Alex V.


Musings & Notes — http://alexvollmer.com
Track what you lend and borrow — http://moochbot.com





___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] The state of HotCocoa

2009-05-29 Thread Matt Aimonetti

I wrote a quick summary a couple of days ago:
http://lists.macosforge.org/pipermail/macruby-devel/2009-May/001825.html

Let me know if you have any questions.

- Matt

On Fri, May 29, 2009 at 10:19 PM, Alex Vollmer wrote:

> Hey folks,
>
> Can anybody speak with some authority on the current state of HotCocoa? I
> seem to recall reading an email on the list that Rich and Matt were hacking
> on some new MVC hotness. Is that intended to replace HotCocoa, or just be an
> alternative?
> Cheers,
>
> Alex V.
>
> 
> Musings & Notes — http://alexvollmer.com
> Track what you lend and borrow — http://moochbot.com
>
>
>
>
>
>
> ___
> MacRuby-devel mailing list
> [email protected]
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Experimental branch status

Re: [MacRuby-devel] Experimental branch status

Re: [MacRuby-devel] Experimental branch status: C-lib wrappers

Re: [MacRuby-devel] Experimental branch status

[MacRuby-devel] [MacRuby] #269: Calling a method on a pointer passed to a KVC validation method fails

[MacRuby-devel] experimental branch: status update

Re: [MacRuby-devel] experimental branch: status update

[MacRuby-devel] Tim added you as a friend on MyLife!

Re: [MacRuby-devel] experimental branch: status update

Re: [MacRuby-devel] Tim added you as a friend on MyLife!

Re: [MacRuby-devel] [MacRuby] #257: Conversion to JSON works , But JSON parsing fails in MacRuby 0.4

Re: [MacRuby-devel] Tim added you as a friend on MyLife!

[MacRuby-devel] Contributions (Was: Experimental branch status)

Re: [MacRuby-devel] Contributions (Was: Experimental branch status)

Re: [MacRuby-devel] Contributions (Was: Experimental branch status)

Re: [MacRuby-devel] Contributions (Was: Experimental branch status)

[MacRuby-devel] [MacRuby] #270: [Website] Minor changes

[MacRuby-devel] [MacRuby] #271: [website] hotcocoa mappings tutorial paragraph wrapping

Re: [MacRuby-devel] [MacRuby] #270: [Website] Minor changes

Re: [MacRuby-devel] [MacRuby] #271: [website] hotcocoa mappings tutorial paragraph wrapping

[MacRuby-devel] The state of HotCocoa

Re: [MacRuby-devel] The state of HotCocoa

22 matches

Site Navigation

Mail list logo

Footer information