On 1 May 2008, at 10:19 AM, Claus Atzenbeck wrote: > > Subject: Re: [Skim-app-users] Open Skim-enhanced PDFs (feature > proposal) > In-Reply-To: <[EMAIL PROTECTED]> > Message-ID: <[EMAIL PROTECTED]> > References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED] > > > User-Agent: Alpine 1.10 (OSX 962 2008-03-14) > MIME-Version: 1.0 > Content-Type: MULTIPART/MIXED; BOUNDARY="0-100545559-1209629949=:255" > > This message is in MIME format. The first part should be readable > text, > while the remaining parts are likely unreadable without MIME-aware > tools. > > --0-100545559-1209629949=:255 > Content-Type: TEXT/PLAIN; charset=ISO-8859-15; format=flowed > Content-Transfer-Encoding: 8BIT > > On Thu, 1 May 2008, Christiaan Hofman wrote: > >>> 1. Add to the preferences something like "Open .skim file >>> additionally >>> opens PDF" and "Open .skim file exclusively opens PDF" (the latter >>> would >>> close the .skim file and the PDF would be the only remaining >>> window). >>> >> >> That would mean you can't open .skim files by itself. Moreover it >> would be messing with the standard document architecture, and >> fighting >> against the frameworks always leads to a lot of pain, even if it >> seems >> simple at first sight. > > What I meant would not fight against frameworks. It simply would call > the associated PDF when a .skim file is opened. In other words: when > opening the .skim file, the same function would be called as if the > user > would manually click on the "Open PDF" button on the .skim file > window. >
You mean opening *both*? Many users would object to that, as it is totally unexpected behavior. My other objections still stand. >>> 2. Option + double click in Finder opens a file, but closes the >>> Finder >>> window. It would be good to have a similar behavior for the "Open >>> PDF" >>> button at the .skim file window: Option + click opens the PDF and >>> closes >>> the .skim file window. >>> >> >> Skim doesn't know *how* you opened the file, only that it should open >> a file. So even if I would think it a good idea it would not be >> possible. > > There is a misunderstanding: I proposed a variant of opening PDFs from > within the associated .skim file window: Each .skim file window has a > button "Open PDF". Clicking on this button opens the associated PDF, > but > leaves the .skim file window open. Similar what the Finder does for > files, I would like to have the feature of Option+click for the "Open > PDF" button on the .skim file window. This would close the .skim file > window additionally to opening the PDF. (This has nothing to do with > the > Finder, I just used to Finder as a reference to similar behavior.) > Same withv a button. A button has a click action. Not an option-click action or something. Moreover it would be too much hidden, it's not intuitive at all. Finder is a completely custom view, so no standard behavior and standard expectations. Also this feature in Finder is totally hidden (I didn't even know about it). So it's not a good example, unless as an example why not to do it. Christiaan > Currently, I have to click "Open PDF", then use e.g. Exposé to get > back > to the .skim file window in order to close it. Using Option+click on > the > "Open PDF" button would make things more efficient. > >> There's a hidden pref to set the creator code for files with Skim >> notes, see the Wiki for details. It won't be in the pref window. > > Thanks. I'll take a look at that. > > Cheers, > Claus > --0-100545559-1209629949=:255-- ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Skim-app-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/skim-app-users
