Tuesday, March 18, 2003|
From the Quick-Links Dept:
Another feature of my Post-All-Open-OmniWeb-Documents script.. the ability to do "QuickLinks". Really should find the time to generalize and publish it... maybe have it interact with NetNewsWire somehow. |
|
From the Wishing Dept: Can I have a system service that saves work-state? Like say I'm working on a website. I've got BBEdit, all my browsers, Terminal, probably GraphicsConverter, all open. Plus some Finder windows that I would really like to come back to. Tomorrow I'll be working in CodeWarrior. I'll have CodeWarrior up, BBEdit up, and probably a few (very different) Finder windows open. I would like to be able to save all those Open things into a state. Come back to that state when I come back to the project. It would have to be an OS level service, to remember the apps, Finder windows, open documents, everything I had open. On that Mac, I'm betting that some sort of standard AppleEvent (kCoreSuite, kAllOpenDocuments) would work. Make it simple so that developers will implement it. Simple in this case probably means staying away from the AppleEvents Object Model. Straight AppleEvents are simple - Object Model AppleEvents take much more setup work. In the past I've implemented something like this by putting a bunch of aliases into a folder, then running an AppleScript that opens everything in that folder. It worked nicely, but it was very hack0rish. I'm wondering if the next breakthrough in GUI design will not be hierarchical, but project based. Maybe even to the point of projects going into an Archive folder after X days. Of course, there would need to be some sort of automatic backup going on as well. Yes, I can implement this sort of thing for my main applications (BBEdit, Finder) with a script. But an OS level functionality of this kind would be a major step in GUI design - one that's stayed basically the same for the last 20 years. |
