The San Jose Symphony Orchestra has announced it will declare bankruptcy and fold, leaving San Jose the largest city in the United States without it’s own orchestra.
June 4, 2002
by Joe
Comments Off
June 3, 2002
by Joe
Comments Off
°i£±£±£±£±
£?o –thojhm m 8ol mnjjjjjjjjjjjjjjjjjmgy,mjj888888888888888888888888 594////////////740=7 8nj nhnnnnnnnnnnnt ll t frrrrrrrrrrr]hyyyyyyyyyzyhddd2a h
June 2, 2002
by Joe
Comments Off
A better browser – The Chimera Project
Chimera is a small Mozilla offshoot project that is rapidly gaining momentum in the open source community. This project is intended to deliver the best possible web browser for the Mac OS X platform.
After using this browser for a few nights, I am gradually finding myself getting more and more addicted to it. It has many performace and UI benefits that put it past MSIE and Mozilla/Fizzilla/Netscape. Chimera uses a Unix backend and a Cocoa front end, instead of MSIE and Fizzilla’s use of the Carbon environment, making it overall a much faster browser. Using Cocoa means that the application behaves like a true Mac OS X application, from the Cocoa GUI elements, smoother native performance, right on down to the Quartz text rendering.
What’s more, the Chimera project has opted to do away with the bloatware and just focus on the browser. So no bundled Mail and Composer apps to suck up your disk space and RAM, and no unused clutter in your user interface. Crisp and clean!
I think that it would be nice to see a Mail client written along these guidelines: Unix/Cocoa, lean, focused application, and possibly even a Composer-like HTML browser one day. All as seperate apps, seperate downloads, seperate preference files.
Chimera, like Mozilla, is an open-source browser, and as such is distributed for free. If you find this interesting and would like to explore Chimera or even possibly contribute, then check out the Chimera web site to get started. I for one have taken a strong interest in this project and am submitting bugs when I find ‘em. You can too.
As of this writing, the Chimera browser is at only version 0.2.8. Still, at this early stage, it is quite a good quality browser that supports most of the things we need and does a fairly good job – bugs notwithstanding. By version 1.0, this should be quite a piece of work.
May 28, 2002
by Joe
Comments Off
Sharing Adobe InDesign 2.0 files between Mac and Windows
Adobe InDesign 2.0 files are compatible between Macintosh and Windows. Often Windows users receive InDesign 2.0 files that originated on the Mac, and complain that they cannot open the files.
To open a Mac InDesign 2.0 file on Windows, simply be sure to add the “.indd” suffix to the file name.
Mac users should get in the habit of adding “.indd” to their InDesign 2.0 file names. I’m amazed that Adobe didn’t build this in to the Save dialog box, as they did with Illustrator and Photoshop.
Now, adding .indd to the end of the file won’t solve your problems when the design firm you’re sending the files to has an old, outdated copy of InDesign, you’re on 2.0, and they don’t tell you that they haven’t upgraded yet…
May 27, 2002
by Joe
Comments Off
How to set file behavior in Dreamweaver MX for custom file types
Dreamweaver MX can support just about any file type if you tell it to. Dreamweaver looks at a filename’s suffix to know how it should be treated, and this behavior can be customized rather easily. Natively, it supports all the standard server types such as .jsp, .php, .xml, .html, .cfm, and – god forbid – .asp, as well as a host of others.
But lets say your site use some lesser known application server, or you’ve edited your httpd.conf file to trick Apache into using your company’s ticker symbol as the default file extension. Or for whatever reason, you have pages that don’t have any of the common and traditional file name extensions and when you try to open the file in Dreamweaver MX, the thing appears as code, or worse, opens up in another application.
It doesn’t have to be this way.
To add your custom extensions, and to have Dreamweaver treat it the way you want, you need to edit a configuration file.
The file in question is “MMDocumentTypes.xml”. This file can be found in your Macromedia Dreamweaver MX application directory, under the sub-directories Configuration and DocumentTypes. On Mac OS X, the root path is /Applications/Macromedia Dreamweaver MX/Configuration/DocumentTypes/MMDocumentTypes.xml
Open this file in a text editor such as BBEdit, or Dreamweaver MX’s code view. In there you simply need to type in the file extension you wish in the appropriate section. So for instance, I wanted to use “.inc” for all my server side include files, and have them render in Dreamweaver MX as standard HTML. So I added the “inc” value to the first line to the winfileextension and macfileextension properties, where it reads ‘documenttype id=”HTML”‘. However, if you want your custom extension to act like JSP or PHP, you could change the file appropriately. Save the file and restart Dreamweaver, and you should be ready to go.
If your custom file extension now opens in Dreamweaver MX, but only in code view, then there is one more step. Open Dreamweaver MX’s Preferences panel and click on File Types / Editors. In the top field where it is labeled “Open in Code View”, locate and delete your custom file extension.
That should do it.