May 2012 - MacRuby-devel - lists.macosforge.org

MacRuby, ApplesScript and Skype?
by Mike Gleeson 30 May '12

30 May '12

I'm looking to do some scripted control of Skype, and not able to get too far with MacRuby. Please let me know if this is not the proper forum to ask, thanks. I can find the app: >> skype = SBApplication.applicationWithBundleIdentifier("com.skype.skype") And I see in the Applescript editor that there is a single command called "send" that matches the Skype documentation. I can't seem to invoke it, asking for suggestions. The list of available functions shows a few relevant details: >> skype.methods(true,true) - Object.methods(true,true) (This is trimmed): :classesForScriptingNames, :classNamesForCodes, :"sendCommand:scriptName:", :classForScriptingClass, :setDelegate, :delegate, and then a handful of init methods. It looks like ':"sendCommand:scriptName:"' is that doorway into AppleScript, but I'm not sure what to do with it. I don't see "send" anywhere, and I don't know if that's an issue as it is also a standard Ruby method. Ideas anyone? Thanks, - Mike G

4 3

Re: [MacRuby-devel] Appstore rules on symlinks Macruby framework changed ?
by Rob Ista 29 May '12

29 May '12

Yes, i have seen that .. i will do some tests to see if i can get a working app with a symlink although a manual change did not succeed thus far .. either it cannot find macgems (if i hack the binary with "A") or it just crashes because it can not find "Current" through the simlink any more and yes, it seems that apple is really stretching their rules to the limits .. i sensed some disturbance in the python community as well with similar issues the last few days … the response from the review team was : - - - - - Dear developer, We have discovered one or more issues with your recent delivery for "SubtitleReSync". To process your delivery, the following issues must be corrected: Malformed Framework - The framework bundle MacRuby (SubtitleReSync.app/Contents/Frameworks/MacRuby.framework) 'Versions' directory must contain a symbolic link 'Current' resolving to a specific version directory. Refer to the Anatomy of Framework Bundles for more information. - - - - - The funny thing is that i have another framework but didn't bother to create a "cute" one so i just dumped the .dylib into Frameworks. That seems to be allowed and ok :) I will file a bug report as well cheers, Rob > > macruby_deploy fiddles with the version symlinks on purpose. We changed it in the past for app store guidelines at some point; you should be able to see it in the history of macruby_deploy. > > It would be fastest to just revert that change and see if that fixes things. Though if Apple really wants the version to be A then we will need to do a bit more work. > > macruby_deploy is fairly straightforward, so it is easy to go through and find what needs to be changed. > > > Sent from my iDevice > > On 2012-05-07, at 9:38, Joshua Ballanco <jballanc(a)gmail.com> wrote: > >> Hi Rob, >> >> I haven't had time to look into it, but hopefully Apple is not looking to restrict versions within framework bundles to "A", "B", "C", etc. As for "Current" not being a symlink, that does seem like a bug. Would you mind filing it as such so that we don't loose track of it? >> >> - Josh >> On Saturday, May 5, 2012 at 8:27 PM, Rob Ista wrote: >> >>> 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 >>> _______________________________________________ >>>

5 8

Compile command line app
by Enrico Pilotto 29 May '12

29 May '12

Hi, there is a way to create a command line tool with XCode using macruby? I've a little program that run with 'macruby main.rb', but now i want create an executable file... There is a way to compile the macruby source? Thanks, Enrico.

3 3

Github Issues: Now open for your MacRuby bugs!
by Joshua Ballanco 16 May '12

16 May '12

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

1 0

Double module included
by Dave Lee 10 May '12

10 May '12

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

2 1

RubyMotion: Ruby for iOS
by bugpowder 08 May '12

08 May '12

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

2 1

Appstore rules on symlinks Macruby framework changed ?
by Rob Ista 07 May '12

07 May '12

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

3 2

RubyMotion: Ruby for iOS
by Laurent Sansonetti 04 May '12

04 May '12

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 @RubyMotion on Twitter. http://twitter.com/RubyMotion Enjoy! Laurent

13 20

Re: [MacRuby-devel] RubyMotion: Ruby for iOS
by Jean-Denis MUYS 04 May '12

04 May '12

One solution would be some provision with an escrow, with the commitment that should Laurent's company go out of business (for business reasons or bus-hit reasons), then the full source code would reverse to be open-source under such and such license. But clearly, adopting RubyMotion for a professional product is a significant business risk (even if shared by other similar products), and that should be addressed somehow. Saying that whatever you purchase will continue to work "as is" is not enough. As a simple example, RubyMotion's "GC" doesn't handle retain cycles yet. I suppose it will, sooner than later, but for the time being, the product is not complete. That's fine for exploring and developing. It's not for releasing. In the meantime, many (most?) of us will purchase RubyMotion, if only for the pleasure of hacking with Ruby on iOS :-) Jean-Denis

1 0

Re: [MacRuby-devel] RubyMotion: Ruby for iOS
by Dan Farrand 03 May '12

03 May '12

I like the idea that somebody is invested in Ruby for IOS to make money. Open Source is great for projects that become very popular. Projects related to Apple like MacRuby are inherently risky since Apple will be indifferent at best to weather it does something to break MacRuby, especially as they see it being a competitor for their preferred mindset. If a company can make money ensuring that MacRuby for Mac and IOS continue to survive Apple's passive aggressive ways, then it gives me greater incentive to invest my time using MacRuby. On the other hand we have to serious consider Apple's commitment to computing at all. As Apple ignores the computer market, the point will come where none of the rest of it maters. If the next computer I buy is not an Apple product, the likely hood grows that the next phone or tablet I buy will not be a MAC OS/iOS product. As someone who makes a living from computing, it is the computer that leads not the other gadgets.

1 0