gmane.comp.lang.ruby.macintosh.devel

Github Issues: Now open for your MacRuby bugs!

Joshua Ballanco — 2012-05-16T00:17:59

Hello all, 

Quick summary: go to https://github.com/MacRuby/MacRuby/issues to file all your MacRuby bugs from now on.

As had been previously discussed, today we've gone ahead and opened Github issues for the MacRuby project. At the same time, we've frozen the old Trac reporting tool and will no longer be accepting new bug reports there (though existing reports can still be viewed/searched until we manage to move them all over).

One side-effect of this change is that new bug reports (filed with Github Issues) will no longer be reported to the MacRuby-tickets mailing list. We are currently investigating ways that we can bring this back, though I feel like not many people outside of the core team were subscribed to this list in the first place. (If you were and will miss it horribly, please let us know.)

This is just one of the changes coming over the next few days, so be sure to keep an eye on the list!

Cheers,

Josh 

_______________________________________________
MacRuby-devel mailing list
MacRuby-devel-qhrM8SXbD5KlRa4neek8BWD2FQJk+8+b< at >public.gmane.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Double module included

Dave Lee — 2012-05-10T21:09:25

Hi,

Can anyone tell me, is this a MacRuby bug?

module A; end
module B; include A; end
class C; include B; end
p C.ancestors

in Ruby 1.9.3 the results are:

[C, B, A, Object, Kernel, BasicObject]

and in MacRuby 0.11 the results are:

[C, B, A, A, NSObject, Kernel]

Why is the A module included twice?

thanks,
Dave
_______________________________________________
MacRuby-devel mailing list
MacRuby-devel-qhrM8SXbD5KlRa4neek8BWD2FQJk+8+b< at >public.gmane.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Appstore rules on symlinks Macruby frameworkchanged ?

Rob Ista — 2012-05-05T17:27:21

Hi all, 
it seems that the Appstore validation has sharpened its control (again) … submitting an app now is rejected because the Macruby framework does not comply to the official Anatomy of Framework Bundles … There should be a symbolic "Current" resolving to "A" ... in the Macruby Framework this is now a fixed "Current" .. does anyone have seen this before and is there a workaround  for the time being ? 

Secondly, the code signing of the bundle contents is still a bit shaky although it seems to work on Lion .. on SL the .rb files create an "argument list too long" message (see below) .. commenting out the .rb files in macruby_deploy for codesigning makes the deploy come to a proper end but of course now the .rb are not signed. Daniel has done some great work on this already but are there any other ideas?  

rgrds, Rob 

/Users/robista/Library/Developer/Xcode/DerivedData/SubtitleReSyncBasic-ayrbtqtujxpvspgaanykiwlaojxy/ArchiveIntermediates/Deployment/BuildProductsPath/Release/SubtitleReSyncBasic.app/Contents/Frameworks/MacRuby.framework/Versions/Current/usr/lib/ruby/1.9.2/abbrev.rb: Argument list too long

RubyMotion: Ruby for iOS

bugpowder — 2012-05-05T12:52:49

Hello, new list member here, through I follow through the web for a long
time.

Just a quick question regarding RubyMotion:

In all reviews/mentions I've read, they say that you need to build your UI
programmatically.

I understand that there is no XCode IDE integration, but is there something
specific preventing an XCode user from creating his UI in XCode/IB and then
instantiating the .xib files with RubyMotion?

If so, would that perhaps be possible in the future, or is there something
inherent in RubyMotion/MacRuby that prevents it?

Thanks
_______________________________________________
MacRuby-devel mailing list
MacRuby-devel-qhrM8SXbD5KlRa4neek8BWD2FQJk+8+b< at >public.gmane.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

RubyMotion: Ruby for iOS

Laurent Sansonetti — 2012-05-03T17:02:20

Hi guys,

I am extremely excited to announce the immediate availability of
RubyMotion, a revolutionary toolchain for iOS development in Ruby.

(RubyMotion is what I have been working on these last 6 months. :))

RubyMotion is a commercial flavor of MacRuby for iOS that includes an
optimized runtime, a brand-new static compiler and memory model, and a
command-line interface.

If you are familiar with MacRuby you should be all set to develop iOS
apps right away.

You can find more information about RubyMotion on its website.

  http://www.rubymotion.com

For a limited time only, RubyMotion can be purchased at a 25% discounted rate.

The developer center features guides, articles and a pointer to the
sample code repository.

  http://www.rubymotion.com/developer-center

Also, the awesome folks at The Pragmatic Studio released an amazing
50-minute screencast on the product. Check it out, it's free!

  http://pragmaticstudio.com/screencasts/rubymotion

If you want to stay connected, make sure to follow < at >RubyMotion on Twitter.

  http://twitter.com/RubyMotion

Enjoy!

Laurent

Failing installers

stephen horne — 2012-05-02T16:42:34

It's been a while since I installed a nightly build because I get a error in the installer ("Installation failed", and "An error occurred while running scripts from the package “macruby_nightly-2012-05-02.pkg”"), and I haven't had the time to look into it.

I've just given it another go, and, to my eyes, it seems to have installed everything it should have:


/Library/Frameworks/MacRuby.framework

/usr/local/bin/macgem
/usr/local/bin/macirb
/usr/local/bin/macrake
/usr/local/bin/macrdoc
/usr/local/bin/macri
/usr/local/bin/macruby
/usr/local/bin/macruby_deploy
/usr/local/bin/macruby_select
/usr/local/bin/macrubyc
/usr/local/bin/macrubyd


Does anyone know if that is everything? Can I just ignore the installer error if the above is in place?

Cheers
--
Fb

_______________________________________________
MacRuby-devel mailing list
MacRuby-devel-qhrM8SXbD5KlRa4neek8BWD2FQJk+8+b< at >public.gmane.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Multiple enumerations

Josh Voigts — 2012-05-01T20:57:08

Is there a way to get multiple enumerations to work, like in the
following example. I know I could be doing this with cocoa, but it's a
small scripting project. (Also I didn't feel like loading a bridge
support file, would that help in this case?)


framework 'ScriptingBridge'

sys = SBApplication.applicationWithBundleIdentifier("com.apple.systemevents")

COMMAND_KEY = 1264807268
OPTION_KEY = 1265594484

sys.keystroke("u", using: COMMAND_KEY|OPTION_KEY)



It seems to only recognize the first enum... I'm probably missing
something logically here...

migrating tickets to GitHub

Matt Aimonetti — 2012-04-27T08:58:30

So it looks like we are waiting for the tracker tickets to be migrated from
MacOS Forge to GitHub to also do the website update and the release.
Who's working on that, what's the status of the migration?

Thanks,

- Matt
_______________________________________________
MacRuby-devel mailing list
MacRuby-devel-qhrM8SXbD5KlRa4neek8BWD2FQJk+8+b< at >public.gmane.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

mruby + mobiRuby ...

Kevin Poorman — 2012-04-20T11:17:51

Looks like matz's is ahead of the game with an iOS compatible version of ruby …

http://mobiruby.org/_______________________________________________
MacRuby-devel mailing list
MacRuby-devel-qhrM8SXbD5KlRa4neek8BWD2FQJk+8+b< at >public.gmane.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

StringScanner Performance

Sylvester Keil — 2012-04-19T13:19:05

Dear all,

while debugging performance issues for a gem (bibtex-ruby) I noticed that MacRuby's StringScanner implementation creates new Regular Expression objects every time #scan is called; as I am dealing with a lexical analyzer based on StringScanner the #scan method is quite crucial and the current implementation performs so slowly that it is basically unusable on MacRuby.

This is the problematic method in MacRuby:

https://github.com/MacRuby/MacRuby/blob/master/lib/strscan.rb#L638

Both MRI and Rubinius work around this by using a feature of Oniguruma patterns to match the pattern at the beginning of a string only. Here are the corresponding sections:

https://github.com/ruby/ruby/blob/trunk/ext/strscan/strscan.c#L437
https://github.com/rubinius/rubinius/blob/master/lib/strscan.rb#L264

Do regular expressions in MacRuby expose similar functionality to either Ruby or C extensions? I'd be happy to help resolving this issue, but have no experience with MacRuby so any pointers on how to best approach this are much appreciated.

Thanks,

Sylvester

Elegant initialization

Josh Voigts — 2012-04-19T03:44:49

Hey, first post to the list, woot!

I've run into a little bit of a snag. Is there an elegant way of
building an initializer similar to this one in macruby? (assuming I'm
subclassing an NSView object)


- (id)initWithFrame:(NSRect)frame controller:(AppController *)ctrlr
{
    if (self = [super initWithFrame:frame]) {
        controller = ctrlr; // deliberately weak reference.
    }

    return self;
}
_______________________________________________
MacRuby-devel mailing list
MacRuby-devel< at >lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Help with class files

Robert Rice — 2012-04-18T17:37:06

Help,

I have a recurring problem with corrupted class files created by Xcode 3.2.4 and I don't know much about class files.

I start having this problem whenever my application become large and I try to change the inheritance of some MacRuby files. Occasionally, the change will cause Interface Builder to crash immediately without an error message but usually the problem manifests itself by not updating the class inheritance information in IB. Even after selecting "Reload All Class Files", IB will show the old inheritance. Deleting my file from Xcode and adding it back in still does not fix the problem.

The only way I know to fix the problem is to copy all of my source file into a new project but this is getting to be more than annoying. Is there a way that I can force Xcode to rebuild all class files for my project?

Thanks,
Bob Rice

Appscript and pathname translation

Robert Schaaf — 2012-04-18T11:48:05

Hello again, Macruby community!

I'm trying to rewrite a program that drives Excel with appscript, and running into the problem of translating back and forth between HFS and POSIX pathnames.  The old Appscript module included a MacTypes module, and these two translations were provided.

1. to go from POSIX to HFS:  

hfs_pathname  = MacTypes::FileURL.path(posix_pathname).hfs_path

2. to make the round trip back to POSIX:  

posix_pathname  = DefaultCodecs.unpack(DefaultCodecs.pack(hfs_pathname).coerce(KAE::TypeFileURL)).path

Do I need to go to the scripting bridge for this?  This is Core Foundation stuff, and I'm totally at sea.  

Any help would be greatly appreciated.

Bob Schaaf


_______________________________________________
MacRuby-devel mailing list
MacRuby-devel-qhrM8SXbD5KlRa4neek8BWD2FQJk+8+b< at >public.gmane.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Compile error

Robert Rice — 2012-04-16T22:52:31

Hi,

I have a project nearing release and I'm trying to compile it but I get the following error in my Build Results:

*** Deployment started
*** Compiling files
ld: library not found for -lbundle1.o
collect2: ld returned 1 exit status
Can't compile "/Users/robertrice/Desktop/RiceCNC/build/Release/RiceCNC.app/Contents/Resources/Analog_Setup_Controller.rb"
Command /bin/sh failed with exit code 1

Any suggestions?

Thanks,
Bob Rice


_______________________________________________
MacRuby-devel mailing list
MacRuby-devel-qhrM8SXbD5KlRa4neek8BWD2FQJk+8+b< at >public.gmane.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Installer Fails

Robert Rice — 2012-04-16T17:12:30

Hi MacRubyists,

It's been a long time since I posted on this forum. I've been doing well with MacRuby. But I ran into a problem trying to bring my installation up-to-date. updated I found that I could only update to the 2/21/2012 nightly build. After that the installer gives me a message "Installation Failed" with nothing descriptive of the problem. Anyone know what changed?

Thanks,
Bob Rice

Update

Laurent Sansonetti — 2012-04-10T23:46:03

Hi guys,

So we had a team chat, and we agreed on the following.

First, we will release master as 0.12 (and just forget about 0.11). It
is important since master has changes for the latest Xcode that have
never been snipped yet. I will work on this. In the meantime, if you
can, please do install one of the latest nightly builds and let us
know of any regression. It is likely that 0.12 will be one of the last
releases before 1.0.

Second, we will prepare a new landing page for the project, which will
be hosted on GitHub. The page will be very minimal, as we intend to
use the wiki for the real content. Josh volunteered to work on this,
he does not need more help. Watson has been working on the necessary
Wiki pages, but we might need more. If you're interested, the Wiki is
open to anyone, you can create new pages or edit existing ones:
https://github.com/macruby/macruby/wiki

Third, we will migrate the tickets from trac to GitHub. Jake Smith and
Dan Sinclair volunteered to work on this. We will coordinate so that
the process will be as smooth as possible. No more help is required
here.

Fourth, we will move the nightly build system to a new infrastructure.
I will provide a Mac Mini that will do the builds and push them on
Amazon S3 (costs will be covered by my company). This will not happen
right now, but somewhere in the future.

We will probably do the first 3 items at once :)

Laurent

Future of MacRuby

Laurent Sansonetti — 2012-04-06T11:20:35

Hi guys,

Yes, I'm still alive :) As you may have noticed, I have been absent
here for a few months. Last year we got a baby, then we moved back to
Europe. I decided to leave Apple a few months ago to achieve one of my
dreams: work on a startup, in part so that I would be flexible in my
time and be able to keep hacking on MacRuby.

Believe it or not, in the near future I should have less pressure on
myself and therefore I should have the time to hack on MacRuby again.
I will happily resume maintaining MacRuby, like I did for the last 5
years. MacRuby is quite stable right now so the maintenance burden is
less significant than before.

Also, during my absence, Watson did a great job of smashing all sorts
of incoming bugs, if he keeps up he will likely become the #1
committer of the project :). Mark Rada spent a lot of time triaging
bugs and writing patches. And Josh Ballanco kept the IRC channel in
activity. It's like the project never slept.

BTW, the 0.11 release actually does exist, you can find it on the
GitHub page. The release notes are still missing, but I will take care
of this (we need to automate the whole process).

One thing that people are worried about is that the Objective-C GC is
being deprecated in Mountain Lion. That's not a surprise given that
the emphasis is on ARC now. As Apple generally (but not always)
removes deprecated APIs in the next release cycle, MacRuby needs to be
changed this year to not depend on the GC anymore.

I have been experimenting with different alternate memory models for
MacRuby on my spare time, and one of them seems to work well, modulo a
few leaks. It's similar to ARC in design (but it has a different
implementation). I have been working on a MacRuby app with friends
using the new code, so far so good. I will merge my branch with GitHub
as soon as it's stable, with a few other improvements. That should
happen before Mountain Lion ships, so no worries, we should be fine.

What can you do to help? Well, keep using MacRuby :) Report bugs.
Write cool samples and submit them on GitHub. Write tutorials covering
a feature of OSX that was challenging to program in MacRuby. For the
more technically-inclined, you can check the tickets, try creating
patches, etc.

Laurent

Re The Future of MacRuby

Tim Rand — 2012-04-06T06:21:43

I am surprised to hear Laurent has left Apple. I don't know what motivated
the change, but I am sure that he is working on something great. Good luck
Laurent!!!

While I have a lot of faith in the open source community and think growing
a larger pool of contributors is critical for the long-term viability of
macruby, the libauto issue is a simple example of how internal decisions at
Apple can have profound effects on macruby's future. That worries me.
Without anyone promoting macruby from inside Apple, they can shut
compatibility with x-code off with an update, add months of work to remove
libauto-dependency because they decide to deprecate GC or otherwise alter
the programming universe in some unforeseen way. Since Apple is an
unapologetic, iron-curtain of secrecy, with a propensity to stop short and
change direction (remember when it seemed like macruby would be on iOS?), I
can only imagine how many hacker years the macruby community will burn
while trying to hit an ever-moving target.

Apple, think different--don't be evil!
--Tim



On Thu, Apr 5, 2012 at 9:02 PM,
<macruby-devel-request-qhrM8SXbD5KlRa4neek8BWD2FQJk+8+b< at >public.gmane.org>wrote:

_______________________________________________
MacRuby-devel mailing list
MacRuby-devel-qhrM8SXbD5KlRa4neek8BWD2FQJk+8+b< at >public.gmane.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re The Future of MacRuby

Dan Farrand — 2012-04-05T22:34:56

I am not a a contributor to MacRuby, but I have been interested in using it. Without Apple sponsorship, I have very little interest in MacRuby.  Without commitment and support from Apple, it will be a never ending scramble to just keep up with niggling changes to xcode, cocoa and the build process.  Every new release of anything by Apple will break stuff.  By offering no comment and no hook into the apple labyrinth the message from Apple is that, "it is not strategic to us".  

The broader message may also be that computing in general is less and less strategic to Apple.  

So sad to say,  I think it is goodby MacRuby.  Very sad, because if Apple does care about the computing side of the business, they are going to need to provide an alternative to ObjectiveC and the aging development approach they have been living off of for the last 10 years.    I had hopped that MacRuby might have pointed the way, but apparently not.

danf

The future of MacRuby

Matt Aimonetti — 2012-04-05T22:06:27

*Many of you have been wondering what is going on with the MacRuby project
given the lack of up-to-date releases and overall communication.
I feel we owe you some explanation.

As a lot of you have noticed, our de-facto project leader Laurent
Sansonetti has been M.I.A since October 2011, his last post to this mailing
list being
http://lists.macosforge.org/pipermail/macruby-devel/2011-October/008168.htmlannouncing
MacRuby 0.11 really soon.
His last commit was a change of license back in October:
https://github.com/MacRuby/MacRuby/commit/ac2a7a8e678d19e44d3c64a9508a8370d082dca2
<https://github.com/MacRuby/MacRuby/commit/ac2a7a8e678d19e44d3c64a9508a8370d082dca2>
Laurent is fine. As described on his twitter http://twitter.com/lrz and
LinkedIn http://www.linkedin.com/in/sansonetti accounts, Laurent is no
longer with Apple and is clearly also no longer directly involved with the
MacRuby project on a day-to-day basis.
Laurent is currently busy with another project and and hopes to someday be
able to contribute to the MacRuby project again.

While no one on this list can speak for Apple, and Apple as a company does
not tend to comment on its future plans or intentions, I think it's
reasonable to imagine that Apple would be more than happy to have the
MacRuby project decide for itself what its destiny is and how to achieve
it.  If they did not want the community to be involved or drive such a
process, they would not have released MacRuby as open source or created the
project infrastructure to facilitate it.   It is time for us to stop
looking to Apple to provide guidance, leadership and coding for the
project, in other words, and take on those challenges for ourselves!
  MacRuby is already very powerful and comparatively stable as a
development platform, now it's time for us to take things to the next level.

I personally think it will finally allow us to communicate and collaborate
on the actual process of development as it occurs, rather than the previous
practice of simply seeing code appear from some hidden, internal branch
which was driven almost exclusively by a single person

Doing all of this in the open should lead to far more people being
interested in the project, not just as users but as developers and leaders.
 No one rushes to fill a position that is occupied by someone else, but now
we have a vacuum to fill, and that can be a good thing in terms of
encouraging more people to step forward.

Here is how I see things and I would love to hear more about what you guys
think.
MacRuby is a great project, but:

   - the target audience & projects aren't clear
   - the target platform (OS X) isn't the one we all really want to target
   (iOS)
   - Cocoa's API is awesome but not user friendly/easy to grasp


What I'd like to suggest is the following:

1. Define clear goals for MacRuby that we can easily evaluate:

   - Focus primarily on making MacRuby the tool to use for quickly
   prototyping OS X and iOS applications.
   - Remove dependency on libauto so MacRuby can run post Mountain Lion and
   on iOS.

2. Increase the number of contributors:

   - Define areas of contribution:
      - implementation itself (mainly requires C, C++ knowledge)
      - prototyping focus (templates, wrapper APIs, modules, tools: a full
      ecosystem aimed at being more productive)
      - documentation (getting started, guides, FAQs, wiki, demos, hacker
      guides)
      - support


   - empower contributors:
      - move the website to github for easier contribution
      - better release process and roadmap
      - better process to review pull requests & give commit rights

3. Improve communication:

   - start an active and official chat room (IRC, campfire like or
   something else)
   - open discussions about plans for the project and progress made
   - better collaboration with other Ruby implementation teams (Rubinius,
   JRuby, MagLev and of course Matz/C Ruby)


Let's not forget that MacRuby is and will remain a free Open Source project
and that means we need your help and support.
Without you, this project doesn't mean much so please voice your opinion
and if you decide to do so, become an active participant to MacRuby's
success.

I would like to thank Apple for their historical support and Laurent for
starting this project and all his work so far. Without those contributions,
MacRuby would never have existed and the project will more than welcome any
future participation by either Apple or Laurent.
At the same time, I don't think the future of this project can or should
rest on the shoulders of a single corporate entity, or that of a single
individual.  That does not encourage the kind of broad participation, or
the kind of overall longevity (in the form of future generations of
contributors) that Open Source projects really need to survive over the
long term.
Finally, I'd like to make clear that I see myself more in a role of a
facilitator than a technical leader on the order of what Laurent was. This
role has been left vacant for more than 6 months now and needs to be filled
by a group of people with greater technical skills than mine. Additional
contributors are therefore more than welcome to join the team, and their
support will be as much appreciated as it is needed.

Finally, in addition to the already numerous great MacRuby contributors and
soon to become contributors, Evan Phoenix (Rubinius) agreed to act as an
advisor for the project.

So, MacRuby community what do you think?*
*
*
*- Matt*
_______________________________________________
MacRuby-devel mailing list
MacRuby-devel-qhrM8SXbD5KlRa4neek8BWD2FQJk+8+b< at >public.gmane.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Rails.app done by the MacRuby community

Matt Aimonetti — 2012-03-29T04:44:24

Today a mini drama was started after Yehuda Katz announced his kickstarter project to build a ".app" for Rails. He's trying to raise $25k to work on the project, see more there:
http://news.ycombinator.com/item?id=3768339

Putting the money raising question aside, I think this is a good project but I think that as a community we can do it together, learn a lot in the process and create an awesome product helping the community.

My suggestion is that people interested get together and hack together in an open and public way. Yehuda might get funded and decide to contribute or do his own thing in JS, that's totally besides the point since our motivations  would be different so we shouldn't worry about that.

So, what do you say?

- Matt

P.S: Two years ago, I ported couchdbx to MacRuby and extracted some code you can see here: https://github.com/mattetti/mrstuff
The couchdbx app is also available in my github repo.


-m
Sent from my iPhone