[MacRuby-devel] [ANN] RailsMailPreview released

2011-09-29 Thread Fernando Barajas
Hi I just finished RailsMailPreview is now available on github Feel free to check out.. https://github.com/fernyb/RailsMailPreview Thanks - Fernando ___ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/lis

Re: [MacRuby-devel] [ANN] AXElements: UI Automation with MacRuby

2011-09-29 Thread Mark Rada
I missed your question earlier. There is a very easy way to find out what all the descriptions of all the menu extras are: ui = Accessibility.application_with_bundle_identifier 'com.apple.systemuiserver' ui.menu_extras.map(&:description) That is all. There is also an arguably e

Re: [MacRuby-devel] [ANN] AXElements: UI Automation with MacRuby

2011-09-29 Thread Mark Rada
Hmm, that bug sounds like it could be the culprit, but I haven't checked. I'm busy tonight, but I'll have time tomorrow to look into it; I should make a note in the AXElements documentation about NSStatusBar things. On 2011-09-29, at 8:46 PM, Brice Ruth wrote: > I followed the steps in the ra

Re: [MacRuby-devel] [ANN] AXElements: UI Automation with MacRuby

2011-09-29 Thread Brice Ruth
I followed the steps in the radar below to activate VO and had the same results as described. Interesting to see which of my non-Apple menu items are using the private API ;-) SwitchResX MenuMeters And those that are using the public API Quicksilver pyTivoX Jumpcut gfxCardStatus vmware dropbox (

Re: [MacRuby-devel] [ANN] AXElements: UI Automation with MacRuby

2011-09-29 Thread Brice Ruth
It appears that there's a known bug in the public NSStatusBar / NSStatusItem API that prevents these from being selected by the Accessibility API. At least that's what I'm assuming - see here: http://openradar.appspot.com/6832098 Granted, this is from 2009, but I'm actually unable to access my ap

Re: [MacRuby-devel] [ANN] AXElements: UI Automation with MacRuby

2011-09-29 Thread Brice Ruth
Awesome, thanks! On Sep 29, 2011, at 11:47 AM, Mark Rada wrote: Whether or not an app is supported depends on if it implements the accessibility protocol. All Cocoa applications, including NSStatusBar apps, do implement this by default. However, sometimes the default implementation is not suffi

Re: [MacRuby-devel] [ANN] AXElements: UI Automation with MacRuby

2011-09-29 Thread Mark Rada
Whether or not an app is supported depends on if it implements the accessibility protocol. All Cocoa applications, including NSStatusBar apps, do implement this by default. However, sometimes the default implementation is not sufficient or is just buggy. So far, the only places I have had issue

Re: [MacRuby-devel] Invoking an obj-c method requiring a block

2011-09-29 Thread Andy Park
Laurent Sansonetti writes: > > Hi Andy, > > Blocks should work. Perhaps there is a problem with this very specific > API. Could you file a ticket? We will investigate. > > Thanks > Laurent > Hi Laurent, Thanks for your feedback. I am now seeing the issue only intermittently; I repo rted it

Re: [MacRuby-devel] [ANN] AXElements: UI Automation with MacRuby

2011-09-29 Thread Brice Ruth
This looks very useful. I skimmed through the documentation and didn't see anything for accessing NSStatusBar applications. Is this possible? Or would I need to add some hooks in my application to allow the test to open the windows when launched versus via clicking a menuitem from the NSStatusBar m

[MacRuby-devel] [ANN] AXElements: UI Automation with MacRuby

2011-09-29 Thread Mark Rada
Hey all, On behalf of Marketcircle Inc., I am open sourcing a library that I have been working on for a while now. AXElements is an alternative to using Auotmator or the ScriptingBridge frameworks. AXElements provides more generic actions than it's alternatives and should work with almost any C