TweetFollow Us on Twitter

DA Prototype
Volume Number:2
Issue Number:1
Column Tag:Pascal Procedures

Prototyping Desk Accessories

By Alan Wootton, President, Top-Notch Productions, MacTutor Contributing Editor

This month I will try to provide an interesting explanation of how to program Desk Accessories. Rather than simply attempting to explain the purpose and function of each of the three main procedures used by DA's (which has, after all, been done), we will try an entirely different approach. We will start with a simple DA, and take for granted the fact that it works. We will then type this DA's code into MacPascal and attempt to get it to run. In the process we will learn a lot about DA's, and when it is all done we will have a useful tool for prototyping Desk Accessories.

Perhaps at this point you are wondering "What do you mean, type it in and get it to run?" We can't make the system call a MacPascal procedure the same way it calls compiled 68000 procedures, so we will write a program that attempts to duplicate the actions of the system and its relationship with DA's. [ A desk accessory simulator! -Ed.]

To start with let's take a look at the DA we will be using as a subject. Its' code is listed below. Look at it briefly and then continue reading the text that follows.

The Simple DA We Will Be Using

 procedure UpdateSelf (var device : deviceControlRec);
 begin
    with device do
 begin
     SetPort(dctlWindow);
     BeginUpdate(dctlWindow);
 
 MoveTo(10, 30);
 DrawString('This is a test DA');
 
     EndUpdate(dctlWindow);
 end;{ of with }
 end;{ of UpdateSelf }

 procedure Open (var device : deviceControlRec;
                                           var block : ParamBlockRec);
     var
  R : Rect;
  wP : windowPeek;
 begin
     with device do
  begin
      setrect(R, 128, 128, 256, 256);
      dctlWindow := 
                  NewWindow(nil, R, 'Test DA', true, 0, nil, true, 0);
      wP := pointer(ord(dctlWindow));
      wP^.windowKind := dctlRefNum;
  end;{ of with }
 end;{ of open }

procedure  Close (var device : deviceControlRec;
                                            var block : ParamBlockRec);
 begin
     with device do
  begin
      DisposeWindow(dctlWindow);
      dctlWindow := nil;
  end;{ of with }
 end;{ of close }

 procedure Event (var device : deviceControlRec;
                                        var block : ParamBlockRec);
     var
         EventP : ^EventRecord;
 begin
    {  csParam holds a pointer to the event record }
    {  copy it to EventP }
     BlockMove(@block.csParam[0], @EventP, 4);
     with EventP^ do{ eventRecord    }
  begin
      case what of
  1 :           { mdown event }
      SysBeep(1);
  6 :            { update event }
      UpdateSelf(device);
  otherwise
      ;       { ignore all other events }
      end;{ case of what }
  end;{ with }
 end;{ procedure event }

 procedure Ctl (var device : deviceControlRec;
                                      var block : ParamBlockRec);
     var
  poi : point;
 begin
     setport(device.dctlWindow);
     with block do
  begin
      case csCode of
  64 :        { accEvent }
      Event(device, block);
  otherwise
      ;
     {        other codes (accRun, accCursor, accMenu,  
                          accCut, etc.) }
     {        are not used by this DA          }
      end;{ case of code }
  end;{ of with block }
 end;{ of Ctl  }

The first thing to notice about this DA is that it does practically nothing. The Open procedure creates a window, the Ctl procedure only handles calls of type accEvent (which are passed to the procedure event). The only events handled are Update, which draws a string, and MouseDown which merely beeps. Finally, the Close procedure Disposes the window. That's all it does. The next thing to notice is that there are some data types referenced that MacPascal does not recognize. Scanning through the code we encounter a DeviceControlRec, and then the ParamBlockRec. Further examination reveals the type WindowPeek which is used once in the Open procedure. We will deal with these three types in a moment. The final thing is the toolbox calls used by the DA. We will declare equivalent procedures to these and use "inline" to make the actual calls. It will be very straightforward with one minor twist.

Now let's get back to the type declarations. DeviceControlRec is not found anywhere in Inside Macintosh! As it turns out, if you read the portion of the Desk Manager on "writing your own Desk Accessories" it will mention the three driver routines used and then refer you to the Device Manager for further details. In the Device Manager chapter they mention that all driver routines recieve a pointer to the calls parameter block in A0 (there's the ParamBlockRec), and a pointer to the "Device Control Entry" in A1. On page 21, titled "A Device Control Entry" we find the description of what must be the DeviceControlRec. The description is not a Pascal type declaration but we can easily convert it into one. The only fields accessed by the simple DA are the dctlRefNum, and dctlWindow. DctlRefNum is the reference number of the driver (related to the number of the DA), and dctlWindow is a place to put a pointer to the window the DA uses. Once you become familiar with DA's the use of the other fields is easily found.

The declaration of a ParamBlockRec is found in that same chapter. If we read the DA carefully we see that csCode and csParam are the only parts referenced, so we won't type all four of the variant parts, only what is needed. CsParam is declared as array[0..0] of Byte which seems real stupid and dangerous to me so I changed it to array[0..3] of Byte. In the DA csParam is used only as a pointer to an event record. It would be convenient to change the definition of csParam to ^EventRecord, but let's stay with the standard form. IM assumes that all DA's (and all drivers) are written in assembly language. In assembly you can use csParam any way you wish. In Pascal the type checking gets in the way, so I have adopted the habit of useing BlockMove to copy things into an out of csParam.

To find the definition of WindowPeek we look, naturally, in the Window Manager chapter of IM. To use this definition we must also provide declarations for a Handle, and for a StringHandle. As I mentioned in previous articles, MacPascal allocates 2 bytes for boolean types while Lisa Pascal allocates 1 byte (1 is correct). We take this into account in the declaration.

We are now ready to do the Type declarations, so here they are:

Type Declarations for the Sample DA

 type
    Lptr = ^longint;
    ptr = ^integer;
    Handle = ^ptr;
    Byte = 0..255;
    str255P = ^str255;
    stringHandle = ^str255;

  ParamBlockRec = record
      qLink : Ptr;
      qType : integer;
      ioTrap : integer;
      ioCmdAddr : ptr;
      ioCompletion : ptr;
      ioResult : integer;
      ioNamePtr : ^str255;
      ioVrefNum : integer;
      { Usually there are three variant parts here also. }
      { DA's use only csCode and csParam. }
      csCode : integer;
      csParam : array[0..3] of Byte;
   end;

  ParamBlkPtr = ^ParamBlockRec;

  WindowPtr = GrafPtr;
  WindowPeek = ^WindowRecord;

  WindowRecord = record
       port : GrafPort;
       windowKind : Integer;
       visible : Boolean;
       {hilited : Boolean; }
       goAwayFlag : Boolean;
       {spareFlag : Boolean; }
       strucRgn : RgnHandle;
       contRgn : RgnHandle;
       updateRgn : RgnHandle;
       windowDefProc : Handle;
       dataHandle : Handle;
       titleHandle : StringHandle;
       titleWidth : Integer;
       ControlList : Handle;
       nextWindow : WindowPeek;
       windowPic : PicHandle;
       refCon : LongInt;
   end;

  DeviceControlRec = record
       dCltDriver : Handle;
       DcltFlags : integer;
       dctlQueue : integer;
       DctlQHead : Lptr;
       DctlQtail : Lptr;
       DctlPosition : longint;
       DctlStorage : Handle;
       dCtlRefNum : integer;
       dCtlCurTicks : longint;
       dCtlWindow : GrafPtr;
       dCtlDelay : integer;
       dCtlEmask : integer;
       dCtlMenu : integer;
   end;

Now let's attack the issue of the toolbox calls. We will make procedure declarations for the needed routines, and use inline in those declarations. This method is clearer than using inline directly in the code. In the main procedure we will use inline directly (for brevity). The NewWindow function is going to allocate a window record on the heap, and MacPascal reacts very poorly to this (you get an out of memory error). To alleviate this problem we pass a pointer to a window record to NewWindow. We must remember later, when we are constructing the main procedure of our program, to declare a variable named GlobalWindow as a WindowRecord. The ToolBox interface is therefore:

ToolBox Interface routines

{--- Toolbox routines used by  DA -----------------------}
{ NewWindow used by Open. }
{ Uses GlobalWindow variable for WindowRecord instead of  }
{ letting the system allocate the memory automatically. }

 function NewWindow (wStorage : ptr;
       boundsRect : Rect;
                        title : str255;
      visible : boolean;
                  procID : integer;
      behind : windowPtr;
       goAwayFlag : boolean;
                   refcon : longint) : WindowPtr;
 begin
    NewWindow := pointer(LinlineF($A913, @GlobalWindow,
                                 @boundsRect, @title, visible, procID,
   behind, goAwayFlag, refcon));
 end;
 procedure BeginUpdate (TheWindow : WindowPtr);
 begin
      inlineP($A922, TheWindow);
 end;
 procedure EndUpdate (TheWindow : WindowPtr);
 begin
      inlineP($A923, TheWindow);
 end;
 procedure DisposeWindow (TheWindow : WindowPtr);
 begin
      inlineP($A914, TheWindow);
 end;
{---------------------------------------------------------------------}

At this point all we have is enough declarations to survive a command-K check without getting a bug box. We still don't have the DA doing anything. The routines to operate the DA will all be contained in the main procedure, and all their variables will be declared as global. You will find the program at the end of this article. Now we will step-step through the system simulation that will run the sample DA.

If you follow along in the code you'll see that the first command is to remove the menu hilite created by the Go command. We then set the dctlRefNum as if the system were opening the DA and that were its driver reference number. What the DA will do is set the WindowKind field of the DA's window to this number. Actually, if the WindowKind of any window is negative the Window Manager will not treat it normally. It therefore becomes necessary to cheat a little and use a positive number for dctlRefNum. Note that the same applies to the Menu Manager. Our sample DA does not use a menu, but if it did we would have to make that menu's id number positive or it would not be treated normally (Normally for an application menu that is. In a real DA we want the system to treat the menu differently.)

We then call Open, passing along the two records. Block is still not set to any values, but Open does not look for any so it doesn't matter. Open sets dctlWindow to the WindowPtr of the newly created window. Note that Open makes the new window in the back, and that immediately after the Open call the system calls SelectWindow and then ShowWindow. I know this is right because I have traced the code of the trap _OpenDeskAcc.

Now that the DA is Open, it can respond to Ctl (control) calls. When the system actually makes these calls they are of the form err:=PBControl(@Block,false), in other words, a normal device manager driver call. In a Pascal DA there is a header that converts the register based call into a procedure call. We will simply call Ctl directly. One type of control call that all DA's should respond to is those to cut and paste. Our sample DA doesn't, but we will include this in the simulation. To do this we will need a menu, like the Edit menu in an application, to generate the cut and paste commands. This is the purpose of the NewMenu call after Open.

At this point we enter an event loop. The variable "quit" is set to false and we will loop until it is true. The first thing the larger event loop does is enter a smaller loop that waits for an event to occur. There are two types of control call that DA's can receive that are not connected with an event. These are to set the cursor and perform a periodic action. We will not concern ourselves with the timing of the periodic action, or when the DA should set the cursor. Instead we will just make Ctl calls of these two types until an event occurs. Seehow easy it is to make a Ctl call: simply set the csCode and call Ctl.

Once an event occurs it is the system's job to decide if the event should go to a DA or somewhere else. We will go ahead and set up Block for an accEvent call and change it later if needed. In general a DA receives only update events unless it is the front window, in which case it gets almost all of the events. Rather than checking that now, we'll case out the event and check each event on an indivual basis to see which window should receive it. A good example is the first case, KeyDown. If the DA is in front then we make a Ctl call (already set up as type accEvent). Otherwise we do nothing, as the dormant MacPascal windows won't receive events.

The next case is that of a MouseDown. For a mouse click we'll need another case statement to handle the various places the click could have landed. FindWindow will return a code that indicates where, and in which windoow, the click occured. No matter where the click was, if it was in a window, then that window should be in front. So, we call SelectWindow. The variable "fnd'' is an integer that holds the code returned by FindWindow. We will handle the possibilities one at a time, and in numerical order. To understand the action of FindWindow better, consult the Window Manager chapter of Inside Mac.

If the MouseDown was in the menu bar then we should call the Menu Manager function MenuSelect to find which menu item the user wants to choose. MenuSelect returns a Longint with different information in the upper and lower words. If the HiWord is equal to dctlMenu then the user has chosen the DA's menu; csCode is set to accMenu, and csParam is set to the MenuSelect result. Note that the application handles the menu events, not the DA. By the time the DA finds out about it the menu has already been clicked, dragged, and released (MenuSelect does this). The DA uses the Longint MenuSelect result to determine what happened. If the HiWord from MenuSelect is not dctlMenu then it could be the Edit menu (a DA is not concerned with the others). I have arranged the menu put up earlier so that if we add 67 to the number of the menu item chosen it conveniently becomes the correct csCode for editing. We make a Ctl call accordingly.

If the MouseDown was not in the menu bar, but was in a window, then several possibilities remain. If the click was in the content portion of the window then it is that window's responsibility to handle it. Normally these clicks are returned to the application. But, if the WindowKind is negative, then the Window Manager will assume that that window belongs to a DA and make a control call. We do similarly. I found out about this the hard way. If the DA forgets to set WindowKind in Open then the window shows up but is strangely dead - this is most perplexing until you figure it out.

If the click is in the drag bar of a DA window the system will drag the window. The DA never even knows what has happened. Also, if the click is in the close box then the system calls TrackGoAway and then Close. The DA finds out this has happened whne it gets a Close call, it must then close itself. In the simulation we set "quit" and then call Close after exiting the main event loop.

We are done covering the MouseDown possibilities. All that remains are the rest of the event cases. For Update and Activate events a pointer to the window involved is in the message field of the event record. We check it, and make a Ctl call, if necessary. I am not sure how the system handles all the other event possibilities, so I pass them to the DA just in case.

This covers all the functions of the DA Prototyping Program. I have used this program, or one of its cousins, to develop several different DA's, including the one presented in this column in November '85. I think that it is a very useful tool, and I hope you find it useful, too.

DA Prototyping Program
program Run_A_DA;
    uses
      quickdraw2;

{ Put type declarations here }

 var { Variables for main simulation of system. }
     {  NOT for use by the DA }
     device : DeviceControlRec;{ passed to DA }
     block : ParamBlockRec;{ passed to DA }
     sysEv : eventRecord;
     sysMenu : MenuHandle;
     poi : point;
     wPeek : WindowPeek;
     r : rect;
     fnd : integer;
     quit : boolean;
     lll : longint;
     GlobalWindow : WindowRecord;
   
{ Put ToolBox interface routines here }

{ Put sample DA code here }

{*******************************************************}
{** Everything below this line is the simulation of the ****}
{** system running the DA and should not be changed **}
{*******************************************************}
begin { of main simulation of system handling desk acc. }
  { Desk Accessory simulation by Alan Wootton 11/11/85 }
  
   inlineP($A938, 0);{ HiliteMenu(0); remove Run hilite }
  
   device.dctlRefNum := -1 * (16 + 1);{ make this DA #16  }
  { Actually there is a problem with using negative numbers }
  { like a real DA would, so we change it to a positive number. }
   device.dctlRefNum := -device.dctlRefNum;
  { If the DA has owned Resources it may have trouble finding
     them. }
   Open(device, block);{ Open the DA }
  
   inlineP($A91F, device.dctlWindow);{ SelectWindow }
   inlineP($A915, device.dctlWindow);{ ShowWindow }
  
  { Make a menu to simulate the applications Edit menu. }
   sysMenu := Pointer(LinlineF($A931, 13, 'sysEDIT'));
          {NewMenu(13,'sysEdit'}
   inlineP($A933, sysMenu, 'undo');{AppendMenu}
   inlineP($A933, sysMenu, '??');{AppendMenu}
   inlineP($A933, sysMenu, 'cut');{AppendMenu}
   inlineP($A933, sysMenu, 'copy');{AppendMenu}
   inlineP($A933, sysMenu, 'paste');{AppendMenu}
   inlineP($A933, sysMenu, 'clear');{AppendMenu}
   inlineP($A935, sysMenu, 0);{ InsertMenu }
   inlineP($A937);{DrawMenuBar}
  
   quit := false;

   repeat { until quit }
       begin
     
 repeat { accRun and accCursor until an event occurs  }
     begin
            { actually these shouldn't happen all the time like 
                         they do here }
 block.cscode := 65; { accRun }
 Ctl(device, block);{ Device Manager Control call }
 block.cscode := 66; { accCursor }
 Ctl(device, block);{ Device Manager Control call }
     end
 until getnextevent(-1, SysEv);
     
     { set up block to make a control call of type accEvent }
 block.cscode := 64;
 lll := ord(@SysEv);
 BlockMove(@lll, @Block.csParam[0], 4);
     
 case SysEv.what of
     3, 5 :       {  key, or key repeat event  }
           if (LinlineF($A924)=ord(device.dctlWindow)) then
         {   if  FrontWindow = device.dctlWindow then }
      Ctl(device, block);
     1 :      { if mousedown event }
      begin
  poi := SysEv.where;
  fnd := winlineF($A92C, poi, @wPeek);
  { Findwindow( poi, wPeek) }
  if fnd > 0 then { if not on desktop }
      begin
 if fnd > 1 then
      inlineP($A91F, wPeek);{ SelectWindow }
 case fnd of
     1 :      {  mouse down is in MenuBar }
      begin
  lll := LinlineF($A93D, poi);
 {  lll:=MenuSelect(poi) }
  if hiword(lll) = device.dctlMenu then
      begin 
 { if dctlMenu selected then make accMenu call }
  block.csCode := 67;
                { 67 is accMenu }
  BlockMove(@lll, 
                  @Block.csParam[0], 4);
  Ctl(device, block);
      end
  else
      begin
  if Hiword(lll) = 13 then
 { Applications Edit menu? }
      begin
          {  if mouse down in app.'s Edit}
          { then make accUndo..accClear} 
          { call }
              Block.csCode := 
 loword(lll) + 67;
  Ctl(device, block);
      end;
        inlineP($A938, 0);{ HiliteMenu(0 }
   end;
              end;
     3, 5 : { if in content or grow part of window}
 if (wPeek^.windowKind = 
 device.dctlRefNum) then
       Ctl(device, block);
     4 :{ if in drag bar then drag window, }
          { no control call }

      begin
   setrect(r, -999, -999, 999, 999);
   inlineP($A925, wPeek, poi, r);
 { DragWindow }
      end;
     6 :  
 { if in GoAway box of DA window then make close call }

        if winlineF($A91E, wPeek, poi) > 0 then 
 { if TrackGoAway  then }
    if (wPeek^.windowKind = 
           device.dctlRefNum) then
        quit := true;
    { make close call later and end simulation }
     otherwise
        ;
 end{ case of  fnd }
     end;{ of if fnd>0 }
      end;{ case  mousedown }
     6, 8 :    {  if  update, or activate event then make      accEvent 
control call  }
  if sysev.message = 
                         ord(device.dctlWindow) then
       Ctl(device, block);
     otherwise
           Ctl(device, block);{ send other events to acc ??? }
    end;{ of case of event.what }
       end{ of repeat }
   until quit;
  
   Close(device, block);
    { Application ( or system ) calls CloseDeskAcc }
  
end.{  of program, and of article, see 'ya next month}

Only MacTutor brings you quality programming information month after month. Subscribe now!

 
AAPL
$95.60
Apple Inc.
-2.55
MSFT
$43.16
Microsoft Corpora
-0.42
GOOG
$571.60
Google Inc.
-15.82

MacTech Search:
Community Search:

Software Updates via MacUpdate

OneNote 15.2 - Free digital notebook fro...
OneNote is your very own digital notebook. With OneNote, you can capture that flash of genius, that moment of inspiration, or that list of errands that’s too important to forget. Whether you’re at... Read more
iStat Menus 4.22 - Monitor your system r...
iStat Menus lets you monitor your system right from the menubar. Included are 8 menu extras that let you monitor every aspect of your system. Some features: CPU -- Monitor cpu usage. 7 display... Read more
Ember 1.8 - Versatile digital scrapbook....
Ember (formerly LittleSnapper) is your digital scrapbook of things that inspire you: websites, photos, apps or other things. Just drag in images that you want to keep, organize them into relevant... Read more
OmniPlan 2.3.6 - Robust project manageme...
With OmniPlan, you can create logical, manageable project plans with Gantt charts, schedules, summaries, milestones, and critical paths. Break down the tasks needed to make your project a success,... Read more
Command-C 1.1.1 - Clipboard sharing tool...
Command-C is a revolutionary app which makes easy to share your clipboard between iOS and OS X using your local WiFi network, even if the app is not currently opened. Copy anything (text, pictures,... Read more
Knock 1.1.7 - Unlock your Mac by knockin...
Knock is a faster, safer way to sign in. You keep your iPhone with you all the time. Now you can use it as a password. You never have to open the app -- just knock on your phone twice, even when it's... Read more
Mellel 3.3.6 - Powerful word processor w...
Mellel is the leading word processor for OS X and has been widely considered the industry standard since its inception. Mellel focuses on writers and scholars for technical writing and multilingual... Read more
LibreOffice 4.3.0.4 - Free Open Source o...
LibreOffice is an office suite (word processor, spreadsheet, presentations, drawing tool) compatible with other major office suites. The Document Foundation is coordinating development and... Read more
Freeway Pro 7.0 - Drag-and-drop Web desi...
Freeway Pro lets you build websites with speed and precision... without writing a line of code! With it's user-oriented drag-and-drop interface, Freeway Pro helps you piece together the website of... Read more
Drive Genius 3.2.4 - Powerful system uti...
Drive Genius is an OS X utility designed to provide unsurpassed storage management. Featuring an easy-to-use interface, Drive Genius is packed with powerful tools such as a drive optimizer, a... Read more

Latest Forum Discussions

See All

Dawn of the Immortals Review
Dawn of the Immortals Review By Jennifer Allen on July 31st, 2014 Our Rating: :: RESPECTABLE EXPLORATIONUniversal App - Designed for iPhone and iPad Dawn of the Immortals might not re-invent the wheel, but it does tweak it a little... | Read more »
80 Days Review
80 Days Review By Jennifer Allen on July 31st, 2014 Our Rating: :: EPIC ADVENTUREUniversal App - Designed for iPhone and iPad A fantastic and fascinating re-envisioning of the classic novel by Jules Verne, 80 Days is a delightful... | Read more »
Battleheart Legacy Guide
The world of Battleheart Legacy is fun and deep; full of wizards, warriors, and witches. Here are some tips and tactics to help you get the most enjoyment out of this great game. | Read more »
Puzzle Roo Review
Puzzle Roo Review By Jennifer Allen on July 31st, 2014 Our Rating: :: PUZZLE-BASED TWISTUniversal App - Designed for iPhone and iPad A different take on the usual block dropping puzzle game, Puzzle Roo is quite pleasant.   | Read more »
Super Crossfire Re-Release Super Crossfi...
Super Crossfire Re-Release Super Crossfighter Coming Soon, Other Radiangames Titles Go 50% Off Posted by Ellis Spice on July 31st, 2014 [ | Read more »
Hexiled Review
Hexiled Review By Rob Thomas on July 31st, 2014 Our Rating: :: HEX SELLSUniversal App - Designed for iPhone and iPad In space, no one can hear you… spell? Hexiled is a neat concept for a word scramble puzzle, but it doesn’t go too... | Read more »
Summoners War: Sky Arena Passes 10 Milli...
Summoners War: Sky Arena Passes 10 Million Installs! Posted by Jessica Fisher on July 31st, 2014 [ permalink ] Universal App - Designed for iPhone and iPad | Read more »
Deep Loot Review
Deep Loot Review By Jennifer Allen on July 31st, 2014 Our Rating: :: DIVE DEEPUniversal App - Designed for iPhone and iPad Dive deep in this fun explore-em-up that’s a little grind heavy but ultimately quite entertaining.   | Read more »
Despicable Me: Minion Rush is One Year O...
Despicable Me: Minion Rush is One Year Old, Gets its Biggest Update Yet Posted by Jennifer Allen on July 31st, 2014 [ permalink ] Universal App - Designed for iPhone and iPad | Read more »
Fish & Shark Review
Fish & Shark Review By Jordan Minor on July 31st, 2014 Our Rating: :: FLAPPY FISHUniversal App - Designed for iPhone and iPad Fish & Shark’s beauty is only scale deep.   | Read more »

Price Scanner via MacPrices.net

Save up to $130 on an iPad mini with Apple re...
The Apple Store has Certified Refurbished 2nd generation iPad minis with Retina Displays available for up to $130 off the cost of new models, starting at $339. Apple’s one-year warranty is included... Read more
iPad Cannibalization Threat “Overblown”
Seeking Alpha’s Kevin Greenhalgh observes that while many commentators think Apple’s forthcoming 5.5-inch panel iPhone 6 will cannibalize iPad sales, in his estimation, these concerns are being... Read more
Primate Labs Releases July 2014 MacBook Pro P...
Primate Labs’ John Poole has posted Geekbench 3 results for most of the new MacBook Pro models that Apple released on Tuesday. Poole observes that overall performance improvements for the new MacBook... Read more
Apple Re-Releases Bugfixed MacBook Air EFI Fi...
Apple has posted a bugfixed version EFI Firmware Update 2.9 a for MacBook Air (Mid 2011) models. The update addresses an issue where systems may take longer to wake from sleep than expected, and... Read more
Save $50 on the 2.5GHz Mac mini, plus free sh...
B&H Photo has the 2.5GHz Mac mini on sale for $549.99 including free shipping. That’s $50 off MSRP, and B&H will also include a free copy of Parallels Desktop software. NY sales tax only. Read more
Save up to $140 on an iPad Air with Apple ref...
Apple is offering Certified Refurbished iPad Airs for up to $140 off MSRP. Apple’s one-year warranty is included with each model, and shipping is free. Stock tends to come and go with some of these... Read more
$250 price drop on leftover 15-inch Retina Ma...
B&H Photo has dropped prices on 2013 15″ Retina MacBook Pros by $250 off original MSRP. Shipping is free, and B&H charges NY sales tax only: - 15″ 2.3GHz Retina MacBook Pro: $2249, $250 off... Read more
More iPad Upgrade Musings – The ‘Book Mystiqu...
Much discussed recently, what with Apple reporting iPad sales shrinkage over two consecutive quarters, is that it had apparently been widely assumed that tablet users would follow a two-year hardware... Read more
13-inch 2.5GHz MacBook Pro on sale for $999,...
Best Buy has the 13″ 2.5GHz MacBook Pro available for $999.99 on their online store. Choose free shipping or free instant local store pickup (if available). Their price is $100 off MSRP. Price is... Read more
Save up to $300 on an iMac with Apple refurbi...
The Apple Store has Apple Certified Refurbished iMacs available for up to $300 off the cost of new models. Apple’s one-year warranty is standard, and shipping is free. These are the best prices on... Read more

Jobs Board

*Apple* Retail - Multiple Positions (US) - A...
Sales Specialist - Retail Customer Service and Sales Transform Apple Store visitors into loyal Apple customers. When customers enter the store, you're also the Read more
Sr. Product Leader, *Apple* Store Apps - Ap...
**Job Summary** Imagine what you could do here. At Apple , great ideas have a way of becoming great products, services, and customer experiences very quickly. Bring Read more
Sr Software Lead Engineer, *Apple* Online S...
Sr Software Lead Engineer, Apple Online Store Publishing Systems Keywords: Company: Apple Job Code: E3PCAK8MgYYkw Location (City or ZIP): Santa Clara Status: Full Read more
Sr Software Lead Engineer, *Apple* Online S...
Sr Software Lead Engineer, Apple Online Store Publishing Systems Keywords: Company: Apple Job Code: E3PCAK8MgYYkw Location (City or ZIP): Santa Clara Status: Full Read more
*Apple* Solutions Consultant (ASC) - Apple (...
**Job Summary** The ASC is an Apple employee who serves as an Apple brand ambassador and influencer in a Reseller's store. The ASC's role is to grow Apple Read more
All contents are Copyright 1984-2011 by Xplain Corporation. All rights reserved. Theme designed by Icreon.