November 2011 - MacRuby-devel - lists.macosforge.org

Re: [MacRuby-devel] Scripting Bridge
by Matt Aimonetti 07 Nov '11

07 Nov '11

I talked with Laurent and it said that the fact that the object type is SBObject is probably done on purpose by the inDesign API. - Matt On Tue, Nov 1, 2011 at 12:12 PM, Matt Aimonetti <mattaimonetti(a)gmail.com>wrote: > I generated the header file and looked at the description and I think that > the issue us that the returned value isn't cast: > > @property (copy) id appliedFont; // The font applied to the find glyph > preference, specified as either a font object or the name of font family. > Can return: font, string or nothing. > > "id" in Objective-C means refers to an object that isn't typed (could be > anything). That might be the reason why you get an object that isn't cast. > There is a workaround and it's to use the properties hash: > > framework 'Foundation' > framework 'ScriptingBridge' > > app = SBApplication.applicationWithBundleIdentifier('com.adobe.indesign') > load_bridge_support_file 'inDesign.bridgesupport' > doc = app.activeDocument > doc.allParagraphStyles.each do |style| > puts style.name > puts style.properties["appliedFont"].name > puts "~~~~~~~~~~~~~~" > end > > In my case it returns the following: > > [No Paragraph Style] > Minion Pro Regular > ~~~~~~~~~~~~~~ > [Basic Paragraph] > Minion Pro Regular > ~~~~~~~~~~~~~~ > > The available properties are: > OTFContextualAlternate > OTFDiscretionaryLigature > OTFFigureStyle > OTFFraction > OTFHVKana > OTFHistorical > OTFJustificationAlternate > OTFLocale > OTFMark > OTFOrdinal > OTFOverlapSwash > OTFProportionalMetrics > OTFRomanItalics > OTFSlashedZero > OTFStretchedAlternate > OTFStylisticAlternate > OTFStylisticSets > OTFSwash > OTFTitling > alignToBaseline > allowArbitraryHyphenation > appliedFont > appliedLanguage > appliedNumberingList > autoLeading > autoTcy > autoTcyIncludeRoman > balanceRaggedLines > basedOn > baselineShift > bulletChar > bulletsAlignment > bulletsAndNumberingListType > bulletsCharacterStyle > bulletsTextAfter > bunriKinshi > capitalization > characterAlignment > characterDirection > characterRotation > cjkGridTracking > composer > desiredGlyphScaling > desiredLetterSpacing > desiredWordSpacing > diacriticPosition > digitsType > dropCapCharacters > dropCapLines > dropCapStyle > dropcapDetail > endJoin > fillColor > fillTint > firstLineIndent > fontStyle > glyphForm > gradientFillAngle > gradientFillLength > gradientFillStart > gradientStrokeAngle > gradientStrokeLength > gradientStrokeStart > gridAlignFirstLineOnly > gridAlignment > gridGyoudori > horizontalScale > hyphenWeight > hyphenateAcrossColumns > hyphenateAfterFirst > hyphenateBeforeLast > hyphenateCapitalizedWords > hyphenateLadderLimit > hyphenateLastWord > hyphenateWordsLongerThan > hyphenation > hyphenationZone > id > ignoreEdgeAlignment > imported > index > jidori > justification > kashidas > keepAllLinesTogether > keepFirstLines > keepLastLines > keepLinesTogether > keepRuleAboveInFrame > keepWithNext > keepWithPrevious > kentenAlignment > kentenCharacterSet > kentenCustomCharacter > kentenFillColor > kentenFont > kentenFontSize > kentenFontStyle > kentenKind > kentenOverprintFill > kentenOverprintStroke > kentenPlacement > kentenPosition > kentenStrokeColor > kentenStrokeTint > kentenTint > kentenWeight > kentenXScale > kentenYScale > kerningMethod > keyboardDirection > kinsokuHangType > kinsokuSet > kinsokuType > label > lastLineIndent > leading > leadingAki > leadingModel > leftIndent > ligatures > maximumGlyphScaling > maximumLetterSpacing > maximumWordSpacing > minimumGlyphScaling > minimumLetterSpacing > minimumWordSpacing > miterLimit > mojikumi > name > nextStyle > noBreak > numberingAlignment > numberingApplyRestartPolicy > numberingCharacterStyle > numberingContinue > numberingExpression > numberingFormat > numberingLevel > numberingRestartPolicies > numberingStartAt > objectReference > overprintFill > overprintStroke > paragraphDirection > paragraphGyoudori > paragraphJustification > parent > pointSize > position > positionalForm > previewColor > rensuuji > rightIndent > rotateSingleByteCharacters > rubyAlignment > rubyAutoAlign > rubyAutoScaling > rubyAutoTcyAutoScale > rubyAutoTcyDigits > rubyAutoTcyIncludeRoman > rubyFill > rubyFont > rubyFontSize > rubyFontStyle > rubyOpenTypePro > rubyOverhang > rubyOverprintFill > rubyOverprintStroke > rubyParentOverhangAmount > rubyParentScalingPercent > rubyParentSpacing > rubyPosition > rubyStroke > rubyStrokeTint > rubyTint > rubyType > rubyWeight > rubyXOffset > rubyXScale > rubyYOffset > rubyYScale > ruleAbove > ruleAboveColor > ruleAboveGapColor > ruleAboveGapOverprint > ruleAboveGapTint > ruleAboveLeftIndent > ruleAboveLineWeight > ruleAboveOffset > ruleAboveOverprint > ruleAboveRightIndent > ruleAboveTint > ruleAboveType > ruleAboveWidth > ruleBelow > ruleBelowColor > ruleBelowGapColor > ruleBelowGapOverprint > ruleBelowGapTint > ruleBelowLeftIndent > ruleBelowLineWeight > ruleBelowOffset > ruleBelowOverprint > ruleBelowRightIndent > ruleBelowTint > ruleBelowType > ruleBelowWidth > scaleAffectsLineHeight > shataiAdjustRotation > shataiAdjustTsume > shataiDegreeAngle > shataiMagnification > singleWordJustification > skew > spaceAfter > spaceBefore > spanColumnMinSpaceAfter > spanColumnMinSpaceBefore > spanColumnType > spanSplitColumnCount > splitColumnInsideGutter > splitColumnOutsideGutter > startParagraph > strikeThroughColor > strikeThroughGapColor > strikeThroughGapOverprint > strikeThroughGapTint > strikeThroughOffset > strikeThroughOverprint > strikeThroughTint > strikeThroughType > strikeThroughWeight > strikeThru > strokeAlignment > strokeColor > strokeTint > strokeWeight > tabList > tatechuyoko > tatechuyokoXOffset > tatechuyokoYOffset > tracking > trailingAki > treatIdeographicSpaceAsSpace > tsume > underline > underlineColor > underlineGapColor > underlineGapOverprint > underlineGapTint > underlineOffset > underlineOverprint > underlineTint > underlineType > underlineWeight > verticalScale > warichu > warichuAlignment > warichuCharsAfterBreak > warichuCharsBeforeBreak > warichuLineSpacing > warichuLines > warichuSize > xOffsetDiacritic > yOffsetDiacritic > > That's probably enough info for you to use ;) > > " My current project requires a JPEG >> export and an IDML (InDesign's package XML for 3rd parties) export and I >> cannot get the Dictionary standard "exports" to work." > > > Can you explain a bit more about what you call the standard exports to > work? I *might* be able to help. > > I had started writing a very simple parser for the sdef header file, but I > never finished the project nor released my code since nobody seemed to need > it. > It would certainly be nice to have the equivalent of AppleScript Editor's > dictionary viewer but with the MacRuby method names. It shouldn't be hard > to do, but I really don't have much time to work on it at the moment. If > anyone is interested, please let me know, I can assist you. > > - Matt > > p.s: To generate the bridgesupport file I run the following commands: > $ sdef /Applications/Adobe\ InDesign\ CS5.5/Adobe\ InDesign\ CS5.5.app/ | > sdp -fh --basename inDesign > $ gen_bridge_metadata -c '-I.' inDesign.h > inDesign.bridgesupport > > > > On Tue, Nov 1, 2011 at 9:42 AM, Spencer Rose <dspencerr(a)gmail.com> wrote: > >> >> >> Hey Matt, >> >> Thanks for the response. I had already read and done the tutorial there. >> It was very helpful. >> >> The problem is not so much the weakness of Scripting Bridge, it is the >> difficulty in knowing all of the method calls and their syntax available >> from InDesign. >> >> Following an earlier thread in here i used "myIndesign.methods(true,true)" >> and now have a list of methods, but that list is completely devoid of >> really >> import actions like "open" & "export" and the documentation in the >> Scripting >> Dictionary for InDesign which I have been using for Javascript & Apple >> Script >> does not translate straight across. The code I used to start >> experimenting >> with speaking directly to the InDesign DOM and getting its info was as >> follows: >> @id = >> SBApplication.applicationWithBundleIdentifier('com.adobe.indesign') >> doc = @id.activeDocument >> >> pgph = doc.allParagraphStyles >> >> pgph.each do |style| >> puts "#{style.name}" >> puts style.appliedFont >> end >> >> I get the name of the Paragraph Style, but the appliedFont just prints an >> SBObject. >> >> This is a really small example, but is the basis for my work because I >> will need >> to get font names, styles, kerning, margins, the text of stories and >> coordinates >> of text boxes and a lot more information. My current project requires a >> JPEG >> export and an IDML (InDesign's package XML for 3rd parties) export and I >> cannot get the Dictionary standard "exports" to work. I really like >> macRuby and >> have totally jumped on it. Your book is awesome and has helped a ton. >> But I worry that it is not sufficiently evolved for me to use it >> on a project needing this level of control and access to InDesign >> >> Thanks in advance, Spencer >> >> _______________________________________________ >> MacRuby-devel mailing list >> MacRuby-devel(a)lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >> > >

2 10

How to Configure Xcode to Run Test in MacRuby Project?
by techzen 05 Nov '11

05 Nov '11

Okay, I'm sure I'm just missing something simple but I can't figure out how to include test in a MacRuby Xcode project. I've been using MacBacon to learn MacRuby in TextMate but I don't see how to do so in Xcode. My google-fu has failed me as well because all the example are how to include MacRuby test in an Objective-C project and the build settings don't seem to translate to a pure MacRuby project. It looks to me like I would have to build a custom testing bundle from scratch for each project but that can't be correct. Any pointers would be appreciated. I don't know much ruby so I'm sure I'm missing something. TechZen

2 2

Re: [MacRuby-devel] MacRuby: The Definitive Guide
by Jean-Denis MUYS 03 Nov '11

03 Nov '11

On 3 nov. 2011, at 13:28, Matt Aimonetti <mattaimonetti(a)gmail.com<mailto:mattaimonetti@gmail.com>> wrote: Date: Wed, 2 Nov 2011 19:46:42 -0700 From: Matt Aimonetti <mattaimonetti(a)gmail.com<mailto:mattaimonetti@gmail.com>> To: "MacRuby development discussions." <macruby-devel(a)lists.macosforge.org<mailto:macruby-devel@lists.macosforge.org>> Subject: [MacRuby-devel] MacRuby: The Definitive Guide Message-ID: <CAFGi+5eZNN=ks7q8oPSSNe2Pc0SDTY+2G_PdFL5VwM9SUAaQDw(a)mail.gmail.com<mailto:CAFGi+5eZNN=ks7q8oPSSNe2Pc0SDTY+2G_PdFL5VwM9SUAaQDw@mail.gmail.com>> Content-Type: text/plain; charset="utf-8" Hey guys, if you pre ordered the hard copy of my book, it should arrive in a few days (just got mine). Otherwise you can buy from O'Reilly: http://shop.oreilly.com/product/0636920000723.do or Amazon: http://amzn.to/tVx4ng (cheaper) Digital versions are available on the iBooks and Kindle marketplaces and available in a all included format package on the O'Reilly website. I would sincerely appreciate if some of you could leave reviews on Amazon or O'Reilly, especially if my writing managed to help you out in the past. </infomercial> Thanks, - Matt I just posted the following review to the Amazon page: If you are: - a Ruby developer who would like to learn Cocoa and program for the Mac or - a Cocoa Mac developer who would like to learn programming with Ruby then you could do a lot worse than reading Matt Aimonetti's book. It gets exactly what's useful by focusing on programming for Mac, on the Mac, using MacRuby. So it doesn't want to teach you Ruby or Cocoa. There are other books for that. Instead it focuses on the specific stuff: - What's different when programming in Ruby from programming in Objective-C - How to use Mac tools, e.g. Xcode, to develop in Ruby for the Mac - How the MacRuby runtime is using and integrates with the Objective-C runtime - How to call Ruby code from Objective-C and back - How to benefit from the interpreted nature of Ruby within a Cocoa app and so on. A very interesting look into what the future of Mac programming (and hopefully iOS). It helped me get up to speed very quickly with MacRuby (now included with OS X Lion) and saved me a *lot* of time, probably weeks. I am an inexperienced Ruby programmer, but a seasoned Cocoa programmer. I think that it would be equally useful to an experienced Ruby programmer getting started with Mac development. Highly recommended

2 1

Scripting Bridge
by Spencer Rose 01 Nov '11

01 Nov '11

Hey everyone, any help would be incredible. I am consolidating a workflow with scripts into an actual desktop application. When a search down to base "leaf" node such as "AppliedFont" from a paragraph style in InDesign, all I get is a SBObject. I need the name of the font. I am struggling to figure out how to introspect that object. Tried casting it, to inspect as a Cocoa object. Did not go well. Anyways, any ideas on how to get the property names and not these SBObjects would be helpful.

2 3