ACDSee 1.6 for Mac: OS X software for digital picture viewing on Macintosh.: "ACDSee 1.6 for Mac is a fast image viewing and management tool compatible with Mac OS X software. It lets you view, browse and organize your digital pictures and multimedia files extremely fast and comes with TWAIN image acquisition support for scanners."
Sports Illustrated's favorite image viewer. I'll try it out.
Saturday, March 20, 2004
Friday, March 19, 2004
Free & Impressive Fnord (Kakadu) Photoshop JPEG 2000 (jp2) plug-in
j2k
I tried the LEAP plug-in, I couldn't read the JPEG 2000 files on my Mac. Fnord software in San Francisco puts out this free Photoshop plug-in for Mac and PC. Last updated 1/03. Written by Brendan Bolles.
The Fnord plug-in uses Kakadu 3.2. QuickTime/Mac and Yahoo Messenger use the same development kit, created by Dr. David Taubman at the University of New South Wales. The common SDK source for this plug-in and QuickTime may be responsible for the Mac compatibility.
I used it with Photoshop Elements 2.0/PC to compress a 10MB PNG map scan to a very readable 200K JP2 file. Unlike the LEAP plug-in the Fnord file was readable by Quicktime/Mac. In both cases I included the Adobe sRGB ICC file, but Quicktime choked on the LEAP generated jp2 file.
I tried the LEAP plug-in, I couldn't read the JPEG 2000 files on my Mac. Fnord software in San Francisco puts out this free Photoshop plug-in for Mac and PC. Last updated 1/03. Written by Brendan Bolles
The Fnord plug-in uses Kakadu 3.2. QuickTime/Mac and Yahoo Messenger use the same development kit, created by Dr. David Taubman at the University of New South Wales. The common SDK source for this plug-in and QuickTime may be responsible for the Mac compatibility.
I used it with Photoshop Elements 2.0/PC to compress a 10MB PNG map scan to a very readable 200K JP2 file. Unlike the LEAP plug-in the Fnord file was readable by Quicktime/Mac. In both cases I included the Adobe sRGB ICC file, but Quicktime choked on the LEAP generated jp2 file.
USB Active Extension Cable by A-TEN
USB Active Extension Cable by A-TEN
Looks good. Be nice to have a wireless bridge solution to extend a USB cable. Don't know of one.
USB Active Extension Cable by A-TEN
Part NO: UAE-16
Features : The USB Active Extension Cable is not a passive cable. It has a patent pending ASIC chip inside that buffers the ingoing and outgoing USB signals. Passive cables have the risk of data loss because they cannot pass the signals efficiently. The Active Extension Cable acts as a single port hub, which means that multiple cables can be cascaded (up to 5) to increase the distance between your computer and USB devices. The cable meets USB specifications and works with low-speed and high-speed devices
Extends the distance of a USB Device by 16 feet (5 m).
Can be cascaded, up to 5 cables to greater extend the distance to up to 80 feet (25 m). Complies with USB Electrical and Timing Specs for a USB Hub.
Looks good. Be nice to have a wireless bridge solution to extend a USB cable. Don't know of one.
Fix for installation of Palm Desktop in OS X 10.3
palmOne - Support - palmOne Permission Fixer
"The palmOne Permission Fixer application resolves a known issue with the Palm Desktop installer and Macintosh OS X when iSync 1.2 has been installed.
You may receive the following error during installation or re-installation of Palm Desktop if you have installed the iSync 1.2 Palm Conduit for Mac OS X: "Sorry, the operation could not be completed due to a System error. (Access Denied.)"
"The palmOne Permission Fixer application resolves a known issue with the Palm Desktop installer and Macintosh OS X when iSync 1.2 has been installed.
You may receive the following error during installation or re-installation of Palm Desktop if you have installed the iSync 1.2 Palm Conduit for Mac OS X: "Sorry, the operation could not be completed due to a System error. (Access Denied.)"
Wednesday, March 17, 2004
Apple Reference Library Makeover
Reference Library
Apple's redone their reference library. Very nice!
Apple's redone their reference library. Very nice!
MacDevCenter.com: Are You Talking to Me? Speech on Mac OS X [Mar. 17, 2004]
MacDevCenter.com: Are You Talking to Me? Speech on Mac OS X [Mar. 17, 2004]
Everything you want to know about speech on the Mac. I've wondered about using some of these capabilities in reading education software.
Everything you want to know about speech on the Mac. I've wondered about using some of these capabilities in reading education software.
FileMaker 7: separating data and code (Tidbits review)
TidBITS#721/15-Mar-04: "In FileMaker Pro 7, it's possible to put the data in one file, and all the programming resources - layouts, scripts, value lists, summaries - into a separate file. Separating data (and the data structure) from the stuff you do to analyze and display the data brings an enhanced clarity to the development process. It's also a huge boon for any client whose developer is working remotely. When it's time to update that solution with 6 million records, the IT guy takes the solution off line, throws out the old front-end file, puts the new front-end file in its place, and places the solution back online. Downtime: five minutes, tops.
FileMaker developers have been talking about 'The Separation Model' for years, but it was more of a dream than a reality, due to the limitations on the ways in which one file could access, manipulate, and display another file's data. Line-item reports can't be printed effectively from portals, so you usually had to jump to a data file to print line items (like invoices or class rosters). And that usually meant you had to include scripts in the data file to sort the records and display them on a report layout.
But in FileMaker Pro 7, since one file can logically incorporate all the tables in another file and make use of them as if they were stored internally, these impediments to true separation no longer exist. The main remaining obstacles to The Separation Model are the need to deal with unanticipated fields and user modifications to accounts and passwords, but a lot of smart developers are working on these problems. I have a solution on my PowerBook right now that implements The Separation Model completely. It's somewhat modest, but it works.
The Separation Model won't be adopted by every developer. Many developers will be so thrilled to be able to put everything in a single file that they won't want to think about the alternative, at least not for a while. Even those who embrace it may not use it in every solution, in part because it may unnecessarily increase the amount of data that needs to be backed up regularly. But the sky's the limit now as far as file size goes. FileMaker Pro database files can balloon to 8 terabytes (if you have an Xserve RAID to store it on). As FileMaker Pro databases grow ever larger, the advantages of The Separation Model may become more obvious and more compelling."
FileMaker developers have been talking about 'The Separation Model' for years, but it was more of a dream than a reality, due to the limitations on the ways in which one file could access, manipulate, and display another file's data. Line-item reports can't be printed effectively from portals, so you usually had to jump to a data file to print line items (like invoices or class rosters). And that usually meant you had to include scripts in the data file to sort the records and display them on a report layout.
But in FileMaker Pro 7, since one file can logically incorporate all the tables in another file and make use of them as if they were stored internally, these impediments to true separation no longer exist. The main remaining obstacles to The Separation Model are the need to deal with unanticipated fields and user modifications to accounts and passwords, but a lot of smart developers are working on these problems. I have a solution on my PowerBook right now that implements The Separation Model completely. It's somewhat modest, but it works.
The Separation Model won't be adopted by every developer. Many developers will be so thrilled to be able to put everything in a single file that they won't want to think about the alternative, at least not for a while. Even those who embrace it may not use it in every solution, in part because it may unnecessarily increase the amount of data that needs to be backed up regularly. But the sky's the limit now as far as file size goes. FileMaker Pro database files can balloon to 8 terabytes (if you have an Xserve RAID to store it on). As FileMaker Pro databases grow ever larger, the advantages of The Separation Model may become more obvious and more compelling."
Subscribe to:
Posts (Atom)