Today I wrote a little bookmark roaming script and added it to mozilla_tools. Nothing fancy, and it requires you to have ssh / scp and an account where you can ssh to. If you don't know what that is, don't try it. If you do know what it is, it's pretty easy to use.
I was looking through nsCSSFrameConstructor some more today for the refactoring of geometricParent crap and found out that for XHTML, any content that tries to be the root content will not get framed--except tables. God knows why; the spec happily tells us that must be the root element, and with good reason--if anything else is the root, positioning and stuff totally bombs (though we don't crash anymore for whatever reason--bug 178885 was the fix, taking it out has no effect). The relevant code is if (docElemIsTable) in ConstructDocElementFrame. Perhaps someone will tell me why in Thor's name we want to allow this. xhtml isn't really out there yet, for goodness' sakes, we shouldn't let people do stupid stuff already.
Posted by jkeiser at January 27, 2003 2:54 AMI made a small change to your scripts.
-if ($os eq "CYGWIN_NT-5.1") {
+if ($os =~ /CYGWIN_NT/) {
Thanks. I've made another change, myself (it's on the server), and I'll incorporate that change in a bit. I wanted to be paranoid about the OS type so as to not overwrite things on alternate OS's.
Posted by: John at January 31, 2003 1:56 AMHelp! Did you include help tags in your applications? (I'd be lost without them.) Also, be sure to take extra time to develop your other help files. The Apple Help Viewer supports HTML, QuickTime, and also AppleScript. Take advantage of it! There isn't anything I hate more than going to the Help menu and finding there isn't any help.
Posted by: John at January 26, 2004 12:44 AMWhether native or not, this is obviously one of the first steps on your way to OS X. Keep in mind that often, the functionality of your code has a lot to do with how your interface is designed. How many developers have come up with great functional ideas from working with their interface or looking at their competitors'? Start working on your Aqua compliance from day one. Don't wait until the last minute.
Posted by: Sybil at January 26, 2004 12:44 AMDue to the positioning of the Dock, remember that when you build an application, you have to be sure that new document window sizes and positions do not violate the Dock's space. Dock is temperamental and Dock loves his space. If you default to a window size that expands behind the dock, users will have a difficult time reaching the navigation and resize areas at the bottom of the screen. I can personally say that more than once I have been rather peeved that I couldn't get to an area of the window to resize because the default window settings always pop up behind the Dock. In addition, the new Dock in 10.1 will allow users to position their Dock location on either side of the screen as well.
Posted by: Adrian at January 26, 2004 12:44 AMOther examples of these animations might be to show the status of an FTP transfer, the progress of media being digitized, or an updated time signature. And don't forget that users may want to have some control over this, so give them plenty of options, including the ability to turn these functions off.
Posted by: James at January 26, 2004 12:44 AMWhether native or not, this is obviously one of the first steps on your way to OS X. Keep in mind that often, the functionality of your code has a lot to do with how your interface is designed. How many developers have come up with great functional ideas from working with their interface or looking at their competitors'? Start working on your Aqua compliance from day one. Don't wait until the last minute.
Posted by: Arnold at January 26, 2004 12:44 AMIn building your amazing Aqua application, one of the most important things to consider is the Dock. There are three things your app needs to be "Dock Compliant." Now, I write this knowing that the Dock will be going through some major changes soon, but for the most part, these should still hold true.
Posted by: Tabitha at January 26, 2004 12:44 AMThe simple fact is that, when all other factors are equal, where will consumers spend their money? I believe that in the long run, the best looking, easiest-to-use applications will also be the most successful. I think that's why Apple encourages developers to write programs that are 100 percent Aqua-compliant.
Posted by: Francis at January 26, 2004 12:44 AMDrawers. Similar to Sheets, this is a "child" window that gives users access to items that do not always need to be present. But when do you use a drawer and when do you use a palette?
Posted by: Justinian at January 26, 2004 12:44 AMDrawers. Similar to Sheets, this is a "child" window that gives users access to items that do not always need to be present. But when do you use a drawer and when do you use a palette?
Posted by: Randall at January 26, 2004 12:44 AMDue to the positioning of the Dock, remember that when you build an application, you have to be sure that new document window sizes and positions do not violate the Dock's space. Dock is temperamental and Dock loves his space. If you default to a window size that expands behind the dock, users will have a difficult time reaching the navigation and resize areas at the bottom of the screen. I can personally say that more than once I have been rather peeved that I couldn't get to an area of the window to resize because the default window settings always pop up behind the Dock. In addition, the new Dock in 10.1 will allow users to position their Dock location on either side of the screen as well.
Posted by: Christiana at January 26, 2004 12:44 AM