TweetFollow Us on Twitter

Extend OpenDoc with SOM

Volume Number: 13 (1997)
Issue Number: 4
Column Tag: Programming Techniques

Using SOM to Extend Your OpenDoc Parts

by Gerry Kenner, University of Utah, David Kenner, Phone Directories, Deborah Grits, Apple Computer

An introduction to SOM and OpenDoc extensions with an overview of Apple's ScriptRunner sample code

With the release of OpenDoc, version 1 (DR4) in January 1996, Apple provided the developer community with a powerful tool for creating interchangeable software modules. The good news is that component parts for use inside of applications such as Microsoft Excel and ClarisWorks can be produced quickly using the tools provided. Further, the OpenDoc Frameworks Library (ODF) is definitely a step in the right direction - providing tools to take care of routine graphic interfacing.

Unfortunately, OpenDoc parts are optimized for responding to menu and user events and cannot easily communicate with each other directly. The problem is summarized on p.69 of the OpenDoc Programmer's Guide. "The basic architecture of OpenDoc is primarily geared toward mediating the geometric interrelationships among parts, their sharing of user events, and their sharing of storage. Direct communications among parts for other purposes than frame negotiation is mostly beyond the basic intention of OpenDoc. If separate parts in a document (or across documents) need to share information, or if one part needs to manipulate the contents or behavior of another part, you need to extend the capabilities of OpenDoc in some way."

Translated, this says that you cannot conveniently pass parameters to and from a part without adding extension subclasses. To do this, you must write and compile SOM idl files. Fortunately writing, modifying and compiling idl files is not difficult as we will show in this article.

In this article we approach the subject of OpenDoc extensions in the following way.

1. Explain what extensions are.

2. Provide a glossary of some of the common terms we will be using in this article.

3. Show how extensions work by providing a detailed description of Apple's ScriptRunner demo. This will also show how to use lists, shared resources and shell plug-ins.

4. Outline and build a simple example which will show how to write the necessary code for implementing a minimal extension.

5. Provide instructions for compiling the files by executing the SOM compiler from within Apple's MPW Shell program or the ToolServer.

Extensions

What are these magic things called extensions? First, we consulted Chapter 10 of the OpenDoc Programmer's Guide and determined that OpenDoc uses the extension mechanism for the following:

• Expanding the object interface.

• Creating custom event types.

• Creating custom focus types.

• Supporting scripting.

• Customizing information returned by the Part Info dialog box.

Also, extensions can be used for graphical transformations, creating shell plug-ins and writing OpenDoc patches.

These things are possible because all subclasses of class ODObject can be extended using subclasses of the ODExtension class.

Extensions operate by providing an interface to a part which can be accessed by other parts. The extension has methods which when called will relay the call to the corresponding methods of the parent classes.

Figure 1 shows how this works for the ScriptRunner example.

Figure 1. The HandleMenuEvent method of the TextEditor object can access the Show method of the ScriptRunner object thru the PaletteExt object, which is a subclass of ODExtension.

Some OpenDoc Terminology

Here are some terms used in the material that follows:

Name space

Object (or list) which maps data types to values. If published, name spaces can be used globally.

Plug-in module

Shared libraries which must be installed when a document which has parts that use them is first opened. They modify or extend the functions of the document shell. They are not ODExtension subclasses.

Document shell or document shell program

Managing the environment of the parts in a document.

Extension

Mechanism for expanding the functionality of the OpenDoc classes.

Agent

Code for performing tasks such as instantiating an object.

ScriptRunner Project

Apple included a project in the version 1.0 release of OpenDoc (Developer Release 4) named ScriptRunner. The function of ScriptRunner was to demonstrate how to program and use extensions and plug-ins. ScriptRunner was designed to enhance the capabilities of another Apple Demo part, TextEdit, by adding a palette with scripting functions.

ScriptRunner has several components, an OSA plug-in, a data transfer extension, a scripting palette extension and the ScriptRunner part. The interrelationship between the components and the TextEdit part is shown in Figure 2.

Figure 2. Relationships of the various components of the ScriptRunner system. Modified from illustration in Apple's ScriptRunner Read Me document entitled "ScriptRunner Mechanics."

ScriptRunner operates as follows. The TextEdit part is opened and the user either types or pastes an Apple script into the active text window. The menu item "Show ScriptRunner" of the Tools menu is then selected (Figure 3). The ScriptRunner part is instantiated and the ScriptRunner palette appears in the document window. Selection of the Run item of the palette results in execution of the script contained in the text window. At the end of execution, a dialog box appears with the results returned by the AppleScript. It will read "No results" if nothing is returned. As of DR4, the record function had not been implemented.

Figure 3. Window of TextEditor at the completion of an execution cycle of the Run command of ScriptRunner.

Now that the reader understands how ScriptRunner is called and what it does, we will show the details of the operation. For clarity, we will present this in several segments.

OSA Plug-in

Plug-ins are shared libraries which are called by the document shell when a document is created. When a document is opened, the document shell is launched by OpenDoc. The document shell sets up the document after which it calls the install methods of associated plug-ins. Once this is done, the shell finishes setting up the document by opening its window.

Each shell plug-in has a single exported entry point, its install function. The OSA plug-in's install function is named ODShellPlugInInstall. This function creates a name space for storing an object reference to an object of the class ScriptRunnerAgent. It then instantiates the object and puts its address in the name space (Figure 4).

Figure 4. Creation of name space and ScriptRunnerAgent objects, followed by storage of an object reference to the ScriptRunnerAgent object in the name space object.

Accessing ScriptRunnerAgent by TextEdit

ScriptRunner is accessed by selecting the "Run ScriptRunner" item from the Tools menu. The first time this occurs, the program checks to see if ScriptRunner is available and then installs it (Figure 5). This is done by retrieving the reference to the ScriptRunnerAgent from the name space and using its methods to instantiate the ScriptRunner part.

Figure 5. Sequence of events following selection of "Open ScriptRunner" item of tools menu.

Accessing the palette extension

For a client part to use another part's extension, it calls the method AcquireExtension to get a reference to it. AcquireExtension will create a new extension object if one does not already exist

Using the palette extension

At this point, the palette menu is showing. Selection of the Run item results in the sequence of events shown in Figure 6.

Figure 6. Program flow when the Run item of the Palette is selected.

Extension Project

Planning Stage

We are going to design a simple project to demonstrate how to write an extension which has minimal functionality.

Business Sublevel

Our starting point is the Image project that was described in the February, 1996 issue of MacTech Magazine. This project involved the creation of objects of two parts named ImagePart and SelectPart. Following instantiation, the ImagePart object displayed a read only text screen and had a menu option for selecting the name of a text file. Selection of the menu option resulted in the instantiation of the SelectPart object which automatically displayed an SFGetFile dialog box that asked for a file name. The SelectPart object then placed the name in global storage from which it was retrieved by the ImagePart object. The name was then displayed in the read-only window.

Solution Sublevel

ImagePart will be simplified by having it call the MyOpenPict method from its InitializeFromStorage method thus bypassing the menu operations. This is bad practice but it does enable getting a program running quickly. The MyOpenPict method will instantiate a SelectPart object and call one its methods which was added via the extension mechanism.

The ODExtension subclass GetNameExt will add a method named GetName to SelectPart. The extension will be accessed by ImagePart which will then call the method. The method GetName will display a dialog box asking for the name of a file. This is to provide visual evidence that calling the method was successful.

To simplify our demo, we are not going to pass or return any parameters. Adding this functionality is moderately complicated and will make a good subject for a future article.

Prototyping Level

Figures 7 and 8 give the general layout for running the modified image program. After instantiating SelectPart, ImagePart will interrogate it to determine if it has the desired extension for getting a file name. If it is available, a call will be made to obtain the file name. The SelectPart object will then be disposed of and the ImagePart object will be displayed (Figure 7).

Figure 7. Outline of activities of the ImagePart part.

An overall outline of the operations of the SelectPart object is shown in Figure 8.

Figure 8. Outline of operations of SelectPart.

Flow Diagramming Level

Figure 9 shows the flow of the MyOpenPict method. The SelectPart part is instantiated followed by the acquisition of a pointer to the GetNameExt extension (AcquireExtension method). A call is then made to the GetName method of the extension. Figure 10 shows the details of how the GetName method of the SelectPart part is called from the GetName method of the extension.

Figure 9. Program flow of ImagePart/SelectPart interaction.

Figure 10. Execution of the GetName method.

SOM Interface

To get the advantages of a cross-platform development system, it is necessary to isolate the program code from the interface code. This is done in OpenDoc by writing SOM interface code using the IDL (Interface Definition Language) programming language. The interface code bridges the gap between SOM and high level programming languages such as C++ which are used to write the program proper.

SOM has several components, the most important of which are the SOM kernel, the SOM class libraries and the SOM compiler. The kernel implements the basic runtime behavior while the class libraries augment the runtime environment. The compiler translates the IDL code into a target language such as C++.

The first step towards creating a part is to write a definition file using IDL. The file will be identified with an .IDL suffix. The format of a typical class definition taken from Apple's SamplePart project is as follows:

module SampleCode
{
 interface som_SamplePart : ODPart
 {
 majorversion = 1; minorversion = 0;
 functionprefix = som_SamplePart__;
 override:
 somInit,
 somUninit,
 AcquireExtension,
 HasExtension,
 Purge,
 ReleaseExtension,
 etc.

#ifdef __PRIVATE__
 passthru C_xih = "class SamplePart;";

 SamplePart *fPart;
#endif //__PRIVATE__
};
...More stuff that is not used on the Macintosh.

When the .IDL file is compiled, three new files are created. These are a usage binding, an implementation and an implementation template file with extensions .xh, .xih and .cpp respectively. The usage binding file corresponds to a C++ header file. The implementation file is private to the SOM class and contains macros and other information needed for the class to have access to its instance variables and superclass methods. The implementation template file corresponds to a regular C++ implementation file. Basically, it contains stub method definitions which must be filled in by the programmer.

Programming Level

The following code was tested using OpenDoc release DR5, CodeWarrior, version 9 and System 7.5.2. Create two new OpenDoc part projects using PartMaker Pro. Configure them as follows.

ImagePart

The ImagePart part is created using Apple's SamplePart template. Use the names ImagePart and KSS for class and module identifiers respectively. The following method is added to the ImagePart class and called by adding a line of code to the end of the InitializePartFromStorage (or InitPart) method.

void ImagePart::MyOpenPict(Environment *ev)
{
 ODPart *selectFile;
 ODStorageUnit *su;
 ODBooleanhasExt;
 KSS_GetNameExt  *extension;

 su = fSelf->GetStorageUnit(ev);
 selectFile = 0L;
 selectFile = su->GetDraft(ev)
 ->CreatePart(ev, kSelectPart, kODNULL);
 hasExt = selectFile->HasExtension(ev, kGetNameExtension);
 if (hasExt)
 {
 extension = (KSS_GetNameExt*)selectFile
 ->AcquireExtension(ev, kGetNameExtension);
 extension->GetName(ev);
 extension->ReleaseExtension(ev); // Not tested.
 }
}

This #include statement is put at the top of the ImagePart.cpp file:

#include "GetNameExt.xh" // This can go anywhere.

Add these lines to the ImagePart.h file.

//-*** Programmer added material ***
public:
 void MyOpenPict(Environment *ev);

The indicated changes are made to the ImagePartDef.h file.

// SelectPart items
#define kSelectPartKind   "Apple:Kind:SelectPart"
#define kGetNameExtension \
 "Apple Computer:Extension:ScriptGetName"

At this point, set aside the ImagePart project until the SelectPart project has been compiled and the SelectPart.stub and GetNameExt.h files have been created.

SelectPart

The next step is to get our ducks in line on the receiving end. Create the SelectPart project using Apple's ScriptRunner template. Use SelectPart and KSS for class and module identifiers respectively. Locate the following lines of code in the SelectPart.idl file, which are located immediately after the following line.

interface som_SelectPart : ODPart

{
 void   ShowPalette();
 void   HidePalette();
 ODBooleanIsPaletteVisible();
 ODBooleanMovePalette(in ODPoint point);
 ODPoint* GetPaletteLocation();
 void   SetClient(in ODPart client);
 void   HandleRecordingEvent(in AEDesc script);

and replace them with

 void GetName();

Now, locate the following lines immediately after releaseorder.

 CreatePalette,
 ShowPalette,
 HidePalette,
 IsPaletteVisible,
 MovePalette,
 GetPaletteLocation,
 SetClient,
 HandleRecordingEvent,

and replace ShowPalette to HandleRecordingEvent with

 GetName,

The finished .idl file will be as follows:

module KSS
{
 interface som_SelectPart : ODPart

{

 void GetName();
#ifdef __SOMIDL__
 implementation
 .
 .
 .
 WritePartInfo;
 
 releaseorder:
 CreatePalette,
 GetName,

#ifdef __PRIVATE__
 passthru C_xih =
 "class SelectPart;";

Compile the file using the instructions given in the next section.

When completed, you will have three output files entitled SelectPart.cpp, SelectPart.xh and SelectPart.xih. Replace the .xh and .xih files in the SelectPart project source folder with the new ones.

Do not replace the .cpp but rather open the original one found in the source folder and delete the methods ShowPalette, HidePalette, IsPaletteVisible, MovePalette, GetPaletteLocation, SetClient and HandleRecordingEvent. Comment out the command somSelf->HidePalette(ev) and associated code in the HandleEventWindow method. Open CScripter.cpp and comment out the call to HandleRecordingEvent in the method, RecordEventHandler. Open the new .cpp file and locate the GetName method. Use this code as a model for adding a GetName method to the original SelectPart.cpp file. The resulting addition should be as follows.

SOM_Scope void SOMLINK SelectPart__GetName(KSS_SelectPart *somSelf,
 Environment *ev)
{
 Point  where;
 SFTypeList typeList;
 SFReplyreply;

 KSS_SelectPartMethodDebug("SelectPart","GetName");

 where.h = 40;
 where.v = 40;
 {
 ODSLong rfRef;
 rfRef = BeginUsingLibraryResources();
 {
 ::SetCursor(&ODQDGlobals.arrow);
 ::SFGetFile(where, 0L, 0L, -1, typeList, 0L, 
 &reply);
 }
 EndUsingLibraryResources(rfRef);
 }
}

Put #include "StandardFile.h" somewhere so that SFGetFile will work.

GetNameExt

Locate the files PaletteExt.idl, PaletteExt.cpp, PaletteExt.xh, PaletteExt.xih and paletteExt.exp and change their names to GetNameExt.idl, GetNameExt.cpp, etc. Do a global search in the text of these files with an editor such as BBEdit and replace all instances of PaletteExt and Samples with GetNameExt and KSS respectively. Similarly locate and replace any instances of kPaletteExtension found in the SelectPart project (all the files in the source folder) with kGetNameExtension. We are now ready to modify and compile the GetNameExt.idl file.

Locate the following lines in the GetNameExt.idl file:

 void   Show();
 void   Hide();
 ODBooleanIsPaletteVisible();
 ODBooleanMove(in ODPoint topleft);
 ODPoint* GetLocation();
 void   SetClient(in ODPart client); 



Replace them with:

 void   GetName();

Also locate:

 
 releaseorder:
 Show,
 Hide,
 IsPaletteVisible,
 Move,
 GetLocation,
 SetClient;

and replace them with:

 releaseorder:
 GetName;

Following SOM compilation, go back to the source folder of the SelectPart project and replace GetNameExt.xh and GetNameExt.xih with the newly generated files. Open the SelectPart project and replace PaletteExt.cpp and Palette.exp with GetNameExt.cpp and GetName.exp. Open the original GetNameExt.cpp file and remove the code for the Show, Hide, IsPaletteVisible, Move, GetLocation and SetClient methods. Next open the new GetNameExt.cpp file and copy the code over for the GetName method to the original GetNameExt.cpp file. This code should be as follows.

SOM_Scope void
SOMLINK GetNameExt__GetName(Samples_GetNameExt *somSelf, Environment 
*ev)
{
 Samples_GetNameExtData *somThis = 
 Samples_GetNameExtGetData(somSelf);
 Samples_GetNameExtMethodDebug("Samples_GetNameExt",
 "Get NameExt__GetName");
 
 SOM_TRY
 _fOwner->GetName(ev);
 SOM_CATCH_ALL
 SOM_ENDTRY
}

Compile the SelectPart project.

SelectPart.stub

Create a file named SelectPart.stub as follows.

1. Make a copy of the SelectPart library and name it SelectPart.stub.

2. Open SelectPart.stub using ResEdit. Open the ‘cfrg' resource.

3. Change the member count of the ‘cfrg' resource to 1.

4. Delete the second member of the ‘cfrg' resource.

5. Save the resource.

Move the SelectPart.stub file to the Objects folder of the ImagePart project folder. Make a copy of the GetNameExt.xh file and move it to the source folder of the ImagePart project folder. Open the ImagePart project, create a category named SelectPart Library and add SelectPart.stub to the project. Compile the ImagePart project.

Create stationary files from the ImagePart and SelectPart libraries. Go to the stationary folder and execute the ImagePart stationary. It will bring up a dialog box asking for a file name.

At this point, you are ready to start creating your own parts which use customized extensions.

SOM Compilation

Once the requested changes have been made, the .idl files are compiled with MPW Shell or ToolServer. The major problem is that these programs do not keep track of header files. This means that the programmer must know what and where everything is in his OpenDoc project. This requirement usually overwhelms anyone using these programs for the first time (or the second, or the third).

We have found that the easiest (not best) work-around for the directory problem, is to put everything into the main MPW directory. The equivalent operation with ToolServer is probably to place the project folder in the directory containing ToolServer. The best method, of course, is to become proficient with MPW Shell and/or ToolServer. Instructions and scripts on how to use ToolServer can be obtained from Symantec and Metrowerks. In addition, there are two articles dealing with this subject in recent issues of Develop. (See further reading.)

We used the following script based on the Internet tech note by Jeremy Roschelle to compile our .idl files. (See further reading.)

set SOMOUT ‘ PowerBook1:MPW:OpenDoc Projects:SOM Support'
set ODIDL ‘ PowerBook1:MPW:OpenDoc Projects:Interfaces:IDL'
set ODDIRS "-i ‘{ODIDL}'"
set TARGET ‘ PowerBook1:MPW:OpenDoc Projects:IDL'
somc {ODDIRS} -p -e xih,xc,xh -o "{SOMOUT}" " PowerBook1:MPW:OpenDoc 
Projects:IDL:som_SamplePart.idl"

SOMOUT is the path to where we want our output files to be placed. ODDIRS is the location of the OpenDoc .idl files. If you don't know where to find them, search for the file arbitrat.idl on the OpenDoc and compiler disks and copy them to the above directory. TARGET was included for completeness. It is the pathway to your .idl source file. MPW Shell has a bug which prevented its use so we addressed the location of the file with its full path name (end of somc command line). SamplePartVers.h must be placed in this folder also.

Conclusion

And there it is. You can add an extension to your part by making minor changes to two .idl files. You then make further minor changes to the original .cpp and .h files. The resulting code will be stable and eventually you will be able to port across platforms.

Acknowledgments

We wish to thank the folks at Metrowerks, Mainstay and Bare Bones for CodeWarrior, MacFlow and BBEdit respectively. Without these programs, life would be much harder.

Further Reading

Recent articles that are relevant to this article.

Apple Computer, "OpenDoc Cookbook for the Macintosh", Addison-Wesley: Menlo Park, CA, (1996). (Also OpenDoc Developer CD #4 and Apple Developer CDs.)

Apple Computer, "OpenDoc Programmer's Guide for the Apple OS", Addison-Wesley: Menlo Park, CA, (1996). (Also OpenDoc Developer CD #4 and Apple Developer CDs.)

Kenner, G., and D. Kenner, "Using OpenDoc with Object Flow System (OFS)," MacTech Magazine, 12:2(1996) 40-46.

Kenner, G., and D. Kenner, Object Flow System (OFS) for Visual C++, unpublished manuscript, 1995. (Request via email.)

Maroney, T., ToolServer Caveats and Carping, Develop, 24 (1995) 69-71.

 

Community Search:
MacTech Search:

Software Updates via MacUpdate

A Better Finder Rename 9.52 - File, phot...
A Better Finder Rename is the most complete renaming solution available on the market today. That's why, since 1996, tens of thousands of hobbyists, professionals and businesses depend on A Better... Read more
OmniFocus 2.2.3 - GTD task manager with...
OmniFocus helps you manage your tasks the way that you want, freeing you to focus your attention on the things that matter to you most. Capturing tasks and ideas is always a keyboard shortcut away in... Read more
TinkerTool 5.4 - Expanded preference set...
TinkerTool is an application that gives you access to additional preference settings Apple has built into Mac OS X. This allows to activate hidden features in the operating system and in some of the... Read more
Tinderbox 6.3.1 - Store and organize you...
Tinderbox is a personal content management assistant. It stores your notes, ideas, and plans. It can help you organize and understand them. And Tinderbox helps you share ideas through Web journals... Read more
Parallels Desktop 10.2.2 - Run Windows a...
Parallels Desktop is simply the world's bestselling, top-rated, and most trusted solution for running Windows applications on your Mac. With Parallels Desktop for Mac, you can seamlessly run both... Read more
Adobe Premiere Pro CC 2015 9.0.1 - Digit...
Premiere Pro CC 2015 is available as part of Adobe Creative Cloud for as little as $19.99/month (or $9.99/month if you're a previous Premiere Pro customer). Premiere Pro CS6 is still available for... Read more
Adobe After Effects CC 2015 13.5.1 - Cre...
After Effects CC 2015 is available as part of Adobe Creative Cloud for as little as $19.99/month (or $9.99/month if you're a previous After Effects customer). After Effects CS6 is still available... Read more
Adobe Creative Cloud 2.2.0.129 - Access...
Adobe Creative Cloud costs $49.99/month (or less if you're a previous Creative Suite customer). Creative Suite 6 is still available for purchase (without a monthly plan) if you prefer. Introducing... Read more
Tower 2.2.3 - Version control with Git m...
Tower is a powerful Git client for OS X that makes using Git easy and more efficient. Users benefit from its elegant and comprehensive interface and a feature set that lets them enjoy the full power... Read more
Apple Java 2015-001 - For OS X 10.7, 10....
Apple Java for OS X 2015-001 installs the legacy Java 6 runtime for OS X 10.11 El Capitan, OS X 10.10 Yosemite, OS X 10.9 Mavericks, OS X 10.8 Mountain Lion, and OS X 10.7 Lion. This package is... Read more

Domino Drop (Games)
Domino Drop 1.0 Device: iOS Universal Category: Games Price: $1.99, Version: 1.0 (iTunes) Description: Domino Drop is a delightful new puzzle game with dominos and gravity!Learn how to play it in a minute, master it day by day.Your... | Read more »
OPERATION DRACULA (Games)
OPERATION DRACULA 1.0.1 Device: iOS Universal Category: Games Price: $5.99, Version: 1.0.1 (iTunes) Description: 25% off launch sale!!! 'Could prove to be one of the most accurate representations of the Japanese bullet hell shmup... | Read more »
Race The Sun (Games)
Race The Sun 1.01 Device: iOS iPhone Category: Games Price: $4.99, Version: 1.01 (iTunes) Description: You are a solar craft. The sun is your death timer. Hurtle towards the sunset at breakneck speed in a futile race against time.... | Read more »
Tap Delay (Music)
Tap Delay 1.0.0 Device: iOS Universal Category: Music Price: $4.99, Version: 1.0.0 (iTunes) Description: Back in the “old days”, producers and engineers created delay and echo effects using tape machines. Tap Delay combines the warm... | Read more »
This Week at 148Apps: July 20-24, 2015
July is Heating Up With 148Apps How do you know what apps are worth your time and money? Just look to the review team at 148Apps. We sort through the chaos and find the apps you're looking for. The ones we love become Editor’s Choice, standing out... | Read more »
Red Game Without A Great Name (Games)
Red Game Without A Great Name 1.0.3 Device: iOS Universal Category: Games Price: $2.99, Version: 1.0.3 (iTunes) Description: The mechanical bird is flying through an unfriendly, Steampunk world. Help it avoid obstacles and deadly... | Read more »
Warhammer: Arcane Magic (Games)
Warhammer: Arcane Magic 1.0.2 Device: iOS Universal Category: Games Price: $9.99, Version: 1.0.2 (iTunes) Description: Engage in epic battles and tactical gameplay that challenge both novice and veteran in Warhammer: Arcane Magic, a... | Read more »
Mazes of Karradash (Games)
Mazes of Karradash 1.0 Device: iOS Universal Category: Games Price: $1.99, Version: 1.0 (iTunes) Description: The city of Karradash is under attack: the monsters of the Shadow Realms are emerging from the depths.No adventurer is... | Read more »
Battle Golf is the Newest Game from the...
Wrassling was a pretty weird - and equally great - little wressling game. Now the developers, Folmer Kelly and Colin Lane, have turned their attention to a different sport: golfing. This is gonna be weird. [Read more] | Read more »
Qbert Rebooted has the App Store Going...
The weird little orange... whatever... is back, mostly thanks to that movie which shall remain nameless (you know the one). But anyway it's been "rebooted" and now you can play the fancy-looking Qbert Rebooted on iOS devices. [Read more] | Read more »

Price Scanner via MacPrices.net

2015 13-inch 2.7GHz Retina MacBook Pro on sal...
B&H Photo has the new 2015 13″ 2.7GHz/128GB Retina MacBook Pro on sale today for $1199 including free shipping plus NY sales tax only. Their price is $100 off MSRP. Read more
2.8GHz Mac mini available for $988, includes...
Adorama has the 2.8GHz Mac mini available for $988, $11 off MSRP, including a free copy of Apple’s 3-Year AppleCare Protection Plan. Shipping is free, and Adorama charges sales tax in NY & NJ... Read more
Updated Mac Price Trackers
We’ve updated our Mac Price Trackers with the latest information on prices, bundles, and availability on systems from Apple’s authorized internet/catalog resellers: - 15″ MacBook Pros - 13″ MacBook... Read more
High-Precision Battery Fuel Gauge IC Extends...
Renesas Electronics Corporation has announced its new lithium-ion (Li-ion) battery fuel gauge IC, the RAJ240500, designed to extend battery life for connected mobile devices such as tablets, notebook... Read more
27-inch 3.3GHz 5K iMac on sale for $1799, $20...
B&H Photo has the 27″ 3.3GHz 5K iMac on sale for $1799 including free shipping plus NY tax only. Their price is $200 off MSRP, and it’s the lowest price available for this model from any Apple... Read more
Twelve South Free Dual Screen Backgrounds Co...
Twelve South has posted a second collection of travel Desktop photos, noting: For the Twelve South team, a vacation is never just a vacation. It’s a time to try out new prototypes on the road, visit... Read more
Apple Refurbished iMacs available for up to $...
The Apple Store has Apple Certified Refurbished iMacs available for up to $380 off the cost of new models. Apple’s one-year warranty is standard, and shipping is free: - 27″ 3.5GHz 5K iMac – $1949 $... Read more
Tablets: Why Microsoft’s Surface Is Soaring W...
In contrast to Apple’s record fiscal third quarter reported this week, Microsoft had a miserable latest quarter with its revenues falling by 5.1 percent, hammered by ongoing weak PC demand, and... Read more
Sale! 13″ 1.6GHz/256GB MacBook Air for $1099,...
B&H Photo has the 13″ 1.6GHz/256GB MacBook Air on sale for $1099 including free shipping plus NY tax only. Their price is $100 off MSRP, and it’s the lowest price available for this model. Read more
iPad mini 4 To Be Upgraded To iPad Air 2 Spec...
There’s a certain inevitability about making Apple product predictions this time of year. Come September, we can pretty reliably count on the release of refreshed iPhones, along with the iOS 9... Read more

Jobs Board

*Apple* Retail - Multiple Positions (US) - A...
Job Description: Sales Specialist - Retail Customer Service and Sales Transform Apple Store visitors into loyal Apple customers. When customers enter the store, Read more
*Apple* Retail - Multiple Positions (US) - A...
Job Description: Sales. Specialist - Retail Customer Service and Sales. Transform Apple Store visitors into loyal Apple customers. When customers enter the store, Read more
*Apple* Customer Experience (ACE) Leader - A...
…management to deliver on business objectives Training partner store staff on Apple products, services, and merchandising guidelines Coaching partner store staff on Read more
Project Manager - *Apple* Pay Security - Ap...
**Job Summary** The Apple Pay Security team is seeking a highly organized, results-driven Project Manager to drive the development of Apple Pay Security. If you are Read more
*Apple* TV Product Design Internship (Spring...
…the mechanical design effort associated with creating world-class products with the Apple TV PD Group. Responsibilities will include working closely with manufacturing, Read more
All contents are Copyright 1984-2011 by Xplain Corporation. All rights reserved. Theme designed by Icreon.