ADC Home > Reference Library > Technical Notes > Legacy Documents > Carbon >

Legacy Documentclose button

Important: This document is part of the Legacy section of the ADC Reference Library. This information should not be used for new development.

Current information on this Reference Library topic can be found here:

Collaborative Computing Q&As

CONTENTS

This Technical Note contains a collection of archived Q&As relating to a specific topic--questions sent the Developer Support Center (DSC) along with answers from the DSC engineers. Current Q&As can be found on the Macintosh Technical Q&As web site.

[Mar 01 1993]






Two Macintosh systems showing same application screen

Date Written: 11/5/92

Last reviewed: 3/1/93

How can I get the same information to appear on the screens of two different Macintosh systems?

___

If you want the second screen (the one on the other machine) to show exactly what's on the first machine--including up-to-date user actions such as the mouse position--you'll be faced with a difficult task. Here, you might find it best to look into a third-party application, such as Farallon System's "Timbuktu."

If you want the second screen to show the same display as the first, but aren't concerned about mouse clicks or other user-interaction issues, you might consider writing your application so that it uses Apple events (or some other network protocol) to send screen changes to the display application.

In the second case, we recommend that you use a "factored" (client-server) application design with independent human-interface and display modules. In this design,

  • All user actions (menu choices, data entry, etc.) are packaged into Apple event messages; they aren't acted on immediately.
  • To run on one system, send the Apple event to yourself.
  • To run on two systems, create two Apple events (with the two destinations) that have the same content and send to both systems.
  • On each system, your application's event loop will receive Apple events as part of its normal operation. It should then extract the content and update the display.

Note that the second computer doesn't know (or care) that it received its window-change request from the first computer. Also, this application design makes it simple to record actions to a file, so you can make your application scriptable, or drive it from a script using AppleScript or some suitable third-party application, such as UserLand Frontier.

This design is also much easier to debug, as you can do all the work on one machine.

There's a nice article on this technique in issue #10 of develop called "Apple Event Objects and You," as well as a course from Apple Developer University.

(When the Developer Support Center mentions a third-party product by name, it's meant to be a possible solution for you to investigate, not a recommendation. The DSC doesn't evaluate third-party tools, nor does the DSC maintain complete lists of possible third-party solutions. Consult resources such as the Macintosh Products Guide, Macintosh Development Tools & Languages, the Redgate Buyer's Guide, your dealer, electronic bulletin boards, and reviews in technical magazines to find a product that will fit your needs.)

Back to top

Macintosh XTND translators and graphic type registry

Date Written: 10/9/92

Last reviewed: 11/24/92

I need to translate TIFF, PhotoShop, Targa, PICT, EPSF and other file types that are going to be 24-bit depth and beyond. The last Developer CD Series disc has XTND 1.3.5, which I'm studying. Does Apple have other XTND files available? Do you have a registry of graphic file types with information about them that can be used to write XTND translators? I want to avoid having to license or request the file structures from companies.

___

All that Apple has on developing translators is the XTND Developers Kit, which can be found on the Developer CD Series; it is also the most current version.

Apple doesn't maintain a registry of graphic file types (nor any other type of file type). You have two avenues to pursue to meet your development needs. The first, you already stated you wanted to avoid: contacting the companies individually and requesting the formats/translators directly. The second might be less painful from an effort point of view--purchasing prewritten translators from a company that specializes in them. Dataviz and at least one other third-party developer write and sell a varied set of translators. You can check the Redgate Buyers Guide or Macintosh periodicals such as MacWorld and MacUser for more information on what they offer and how to contact them.

Back to top

Downloadables

Acrobat gif

Acrobat version of this Note (32K)

Download


Back to top


Did this document help you?
Yes: Tell us what works for you.
It’s good, but: Report typos, inaccuracies, and so forth.
It wasn’t helpful: Tell us what would have helped.