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);
    with device do
 MoveTo(10, 30);
 DrawString('This is a test DA');
 end;{ of with }
 end;{ of UpdateSelf }

 procedure Open (var device : deviceControlRec;
                                           var block : ParamBlockRec);
  R : Rect;
  wP : windowPeek;
     with device do
      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);
     with device do
      dctlWindow := nil;
  end;{ of with }
 end;{ of close }

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

 procedure Ctl (var device : deviceControlRec;
                                      var block : ParamBlockRec);
  poi : point;
     with block do
      case csCode of
  64 :        { accEvent }
      Event(device, block);
     {        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

    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;

  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;

  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;

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;
    NewWindow := pointer(LinlineF($A913, @GlobalWindow,
                                 @boundsRect, @title, visible, procID,
   behind, goAwayFlag, refcon));
 procedure BeginUpdate (TheWindow : WindowPtr);
      inlineP($A922, TheWindow);
 procedure EndUpdate (TheWindow : WindowPtr);
      inlineP($A923, TheWindow);
 procedure DisposeWindow (TheWindow : WindowPtr);
      inlineP($A914, TheWindow);

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;

{ 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'));
   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 }
   quit := false;

   repeat { until quit }
 repeat { accRun and accCursor until an event occurs  }
            { 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 }
 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 }
  poi := SysEv.where;
  fnd := winlineF($A92C, poi, @wPeek);
  { Findwindow( poi, wPeek) }
  if fnd > 0 then { if not on desktop }
 if fnd > 1 then
      inlineP($A91F, wPeek);{ SelectWindow }
 case fnd of
     1 :      {  mouse down is in MenuBar }
  lll := LinlineF($A93D, poi);
 {  lll:=MenuSelect(poi) }
  if hiword(lll) = device.dctlMenu then
 { if dctlMenu selected then make accMenu call }
  block.csCode := 67;
                { 67 is accMenu }
                  @Block.csParam[0], 4);
  Ctl(device, block);
  if Hiword(lll) = 13 then
 { Applications Edit menu? }
          {  if mouse down in app.'s Edit}
          { then make accUndo..accClear} 
          { call }
              Block.csCode := 
 loword(lll) + 67;
  Ctl(device, block);
        inlineP($A938, 0);{ HiliteMenu(0 }
     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 }

   setrect(r, -999, -999, 999, 999);
   inlineP($A925, wPeek, poi, r);
 { DragWindow }
     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 }
 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);
           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!


Community Search:
MacTech Search:

Software Updates via MacUpdate

Tidy Up 5.3.7 - Find duplicate files and...
Tidy Up is a full-featured duplicate finder and disk-tidiness utility. Features: Supports Lightroom: it is now possible to search and collect duplicates directly in the Lightroom library. Multiple... Read more
Pinegrow 5.97 - Mockup and design web pa...
Pinegrow (was Pinegrow Web Designer) is desktop app that lets you mockup and design webpages faster with multi-page editing, CSS and LESS styling, and smart components for Bootstrap, Foundation,... Read more
BlueStacks 4.210.0 - Run Android applica...
BlueStacks App Player lets you run your Android apps fast and fullscreen on your Mac. Feature comparison chart How to install Bluestacks on your Mac Go to MacUpdate and click the green "Download"... Read more
WhatsApp 2.2027.10 - Desktop client for...
WhatsApp is the desktop client for WhatsApp Messenger, a cross-platform mobile messaging app which allows you to exchange messages without having to pay for SMS. WhatsApp Messenger is available for... Read more
Art Text 4.0.1 - $29.99
Art Text is graphic design software specifically tuned for lettering, typography, text mockups and various artistic text effects. Supplied with a great variety of ready to use styles and materials,... Read more
Adobe Dreamweaver CC 2020 20.2 - Build w...
Dreamweaver CC 2020 is available as part of Adobe Creative Cloud for as little as $20.99/month (or $9.99/month if you're a previous Dreamweaver customer). Adobe Dreamweaver CC 2020 allows you to... Read more
Adobe Acrobat DC 20.009.20074 - Powerful...
Acrobat DC is available only as a part of Adobe Creative Cloud, and can only be installed and/or updated through Adobe's Creative Cloud app. Adobe Acrobat DC with Adobe Document Cloud services is... Read more
beaTunes 5.2.10 - Organize your music co...
beaTunes is a full-featured music player and organizational tool for music collections. How well organized is your music library? Are your artists always spelled the same way? Any R.E.M. vs REM?... Read more
DiskCatalogMaker 8.1.5 - Catalog your di...
DiskCatalogMaker is a simple disk management tool which catalogs disks. Simple, light-weight, and fast Finder-like intuitive look and feel Super-fast search algorithm Can compress catalog data for... Read more
Meteorologist 3.4.1 - Popular weather ap...
Meteorologist is a simple interface to weather provided by It provides the ability to show the weather in the main menu bar, displaying more detail in a pop-up menu, whose contents are... Read more

Latest Forum Discussions

See All

Steam Link Spotlight - Disco Elysium
Steam Link Spotlight is a feature where we look at PC games that play exceptionally well using the Steam Link app. Our last entry was Signs of the Sojourner Read about how it plays using Steam Link over here. | Read more »
Distract Yourself With These Great Mobil...
There’s a lot going on right now, and I don’t really feel like trying to write some kind of pithy intro for it. All I’ll say is lots of people have been coming together and helping each other in small ways, and I’m choosing to focus on that as I... | Read more »
Pokemon Go's July Community Day wil...
Pokemon Go developers have announced the details concerning the upcoming Gastly Community Day. This particular event was selected by the players of the game after the Gas Pokemon came in second place after a poll that decided which Pokemon would... | Read more »
Clash Royale: The Road to Legendary Aren...
Supercell recently celebrated its 10th anniversary and their best title, Clash Royale, is as good as it's ever been. Even for lapsed players, returning to the game is as easy as can be. If you want to join us in picking the game back up, we've put... | Read more »
Detective Di is a point-and-click murder...
Detective Di is a point-and-click murder mystery set in Tang Dynasty-era China. You'll take on the role of China's best-known investigator, Di Renjie, as he solves a series of grisly murders that will ultimately lead him on a collision course with... | Read more »
Dissidia Final Fantasy Opera Omnia is se...
Dissidia Final Fantasy Opera Omnia, one of Square Enix's many popular mobile RPGs, has announced a plethora of in-game events that are set to take place over the summer. This will include several rewards, Free Multi Draws and more. [Read more] | Read more »
Sphaze is a neat-looking puzzler where y...
Sphaze is a neat-looking puzzler where you'll work to guide robots through increasingly elaborate mazes. It's set in a visually distinct world that's equal parts fantasy and sci-fi, and it's finally launched today for iOS and Android devices. [... | Read more »
Apple Arcade is in trouble
Yesterday, Bloomberg reported that Apple is disappointed in the performance of Apple Arcade and will be shifting their approach to the service by focusing on games that can retain subscribers and canceling other upcoming releases that don't fit... | Read more »
Pixel Petz, an inventive platform for de...
Pixel Petz has built up a sizeable player base thanks to its layered, easy-to-understand creative tools and friendly social experience. It revolves around designing, trading, and playing with a unique collection of pixel art pets, and it's out now... | Read more »
The King of Fighters Allstar's late...
The King of Fighters ALLSTAR, Netmarble's popular action RPG, has once again been updated with a plethora of new content. This includes battle cards, events and 21 new fighters, which increases the already sizeable roster even more. [Read more] | Read more »

Price Scanner via

$219 Apple AirPods Pro are back at Verizon, s...
Verizon has Apple AirPods Pro on sale again for a limited time for $219.99 on their online store. Their price is $30 off Apple’s MSRP, and it’s the lowest price we’ve seen for AirPods Pro. Available... Read more
Apple’s $779 13″ MacBook Air deal returns to...
Apple has clearance, Certified Refurbished, 2019 13″ MacBook Airs available again starting at $779. Each MacBook features a new outer case, comes with a standard Apple one-year warranty, and is... Read more
$200 13″ MacBook Pro discounts are back at Am...
Amazon has 2020 13″ 2.0GHz MacBook Pros on sale again today for $150-$200 off Apple’s MSRP. Shipping is free. Be sure to purchase the MacBook Pro from Amazon, rather than a third-party seller, and... Read more
Deal Alert! Apple AirPods with Wireless Charg...
Sams Club has Apple AirPods with Wireless Charging Case on sale on their online store for only $149.98 from July 6, 2020 to July 9, 2020. Their price is $50 off Apple’s MSRP, and it’s the lowest... Read more
Xfinity Mobile promo: Apple iPhone XS models...
Take $300 off the purchase of any Apple iPhone XS model at Xfinity Mobile while supplies last. Service plan required: – 64GB iPhone XS: $599.99 save $300 – 256GB iPhone XS: $749.99 save $300 – 512GB... Read more
New July 2020 promo at US Cellular: Switch an...
US Cellular has introduced a new July 2020 deal offering free 64GB Apple iPhone 11 smartphones to customers opening a new line of service. No trade-in required, and discounts are applied via monthly... Read more
Apple offers up to $400 Education discount on...
Apple has launched their Back to School promotion for 2020. They will include one free pair Apple AirPods (with charging case) with the purchase of a MacBook Air, MacBook Pro, iMac, or iMac Pro (Mac... Read more
July 4th Sale: Woot offers wide range of Macs...
Amazon-owned Woot is blowing out a wide range of Apple Macs and iPads for July 4th staring at $279 and ranging up to just over $1000. Models vary from older iPads and 11″ MacBook Airs to some newer... Read more
Apple Pro Display XDR with Nano-Texture Glass...
Abt Electronics has Apple’s new 32″ Pro Display XDR model with the nano-texture glass in stock and on sale today for up to $144 off MSRP. Shipping is free: – Pro Display XDR (nano-texture glass): $... Read more
New 2020 Mac mini on sale for up to $100 off...
Amazon has Apple’s new 2020 Mac minis on sale today for $40-$100 off MSRP with prices starting at $759. Shipping is free: – 2020 4-Core Mac mini: $759 $40 off MSRP – 2020 6-Core Mac mini: $998.99 $... Read more

Jobs Board

Physical Therapist Assistant - *Apple* Hill...
Physical Therapist Assistant - Apple Hill Rehab - Full Time Tracking Code 62519 Job Description General Summary: Under the direct supervision of a licensed Physical Read more
Operating Room Assistant, *Apple* Hill Surg...
Operating Room Assistant, Apple Hill Surgical Center - Full Time, Day Shift, Monday - Saturday availability required Tracking Code 62363 Job Description Operating Read more
Perioperative RN - ( *Apple* Hill Surgical C...
Perioperative RN - ( Apple Hill Surgical Center) Tracking Code 60593 Job Description Monday - Friday - Full Time Days Possible Saturdays General Summary: Under the Read more
Product Manager, *Apple* Commercial Sales -...
Product Manager, Apple Commercial Sales Austin, TX, US Requisition Number:77652 As an Apple Product Manager for the Commercial Sales team at Insight, you Read more
*Apple* Mac Product Engineer - Barclays (Uni...
Apple Mac EngineerWhippany, NJ Support the development and delivery of solutions, products, and capabilities into the Barclays environment working across technical Read more
All contents are Copyright 1984-2011 by Xplain Corporation. All rights reserved. Theme designed by Icreon.