> The core functionality is about 500 lines of C-like code that I'd be > interested in porting to a BBEDIT text handler if there's a reasonable > learning curve for doing so. Can anyone advise me with a sample of what a > text-handler or other kind of BBEDIT extension looks like?
How do you envision people using your tool? For getting the output text generated, the easy solution, which you may already have, is compiling your C code as a stdio unix tool. However, I think the bigger problem is getting input to the tool, as there is no built in GUI for building extensions. Depending on your areas of comfort, I would suggest a small Cocoa application, whose window displays at NSStatusWindowLevel (which would have the appearance of being in BBEdit's display layers). When the app is finished running, there are a few ways to get the result back to the current document, the easiest being an AppleEvent (which can be expressed as an AppleScript). Which brings me to the next option, which is an AppleScript Studio application (or whatever Apple calls them these days). I guess it really depends on your goal. Steve -- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at <http://groups.google.com/group/bbedit?hl=en> If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
