Re: Triggering the save command

[Jim Correia]

On May 11, 2007, at 6:38 PM, [EMAIL PROTECTED] wrote:


On May 10, 2007, at 12:51pm, Steve Kalkwarf wrote:

To be specific, Yojimbo doesn't edit "documents" and as such,  
doesn't have any sort of notion of an unsaved document.


if that's the case, then why does yojimbo have a "save" command at  
all?  :-)


It is possible to work with separate editor windows in manual save  
mode. The main window always autosaves.


while i understand, semantically, what you're saying, i think the  
bottom line is consistency in the user experience. when i create a  
note in yojimbo, i'm creating a document, whether yojimbo "thinks"  
it's a document or not. the fact that yojimbo auto-saves is  
fantastic! but if i create a note (document) and start typing,  
until yojimbo auto-saves, that document has not been saved.


Consider iCal as an example. When you create a new calendar/ 
appointment/to do in iCal, it doesn't mark the main window as edited  
until such time as iCal commits the edits to disk.


Yojimbo manages the details for you.

Jim

--
--
This message is sent to you because you are subscribed to
 the mailing list .
To unsubscribe, send mail to: <[EMAIL PROTECTED]>
List archives:  
Have a feature request, or not sure if the software's working 
correctly? Please send mail to: <[EMAIL PROTECTED]>

Re: Triggering the save command

[soundsgoodtome]

On May 10, 2007, at 12:51pm, Steve Kalkwarf wrote:

To be specific, Yojimbo doesn't edit "documents" and as such,  
doesn't have any sort of notion of an unsaved document.



if that's the case, then why does yojimbo have a "save" command at  
all?  :-)


while i understand, semantically, what you're saying, i think the  
bottom line is consistency in the user experience. when i create a  
note in yojimbo, i'm creating a document, whether yojimbo "thinks"  
it's a document or not. the fact that yojimbo auto-saves is  
fantastic! but if i create a note (document) and start typing, until  
yojimbo auto-saves, that document has not been saved.


so i still maintain that the dot should appear until either (a) the  
user saves or (b) yojimbo auto-saves. the dot is simply a visual aid  
for the user, and with all due respect, your rationale does not  
explain why the dot should *not* appear.  :-)  then again, i may have  
missed (or misunderstood) something


-merv

--
--
This message is sent to you because you are subscribed to
 the mailing list .
To unsubscribe, send mail to: <[EMAIL PROTECTED]>
List archives:  
Have a feature request, or not sure if the software's working 
correctly? Please send mail to: <[EMAIL PROTECTED]>

Re: Triggering the save command

[Steve Kalkwarf]

last night, while working in a small note window (one of my 
favorite features; thanks!), i discovered that modifying it 
does not trigger the standard, OS X, red-dot indicator for a 
modified document.


A couple weeks ago, somebody asked a similar question. Here's 
part of my previous answer:



We auto-save when Yojimbo is idle, if you switch to another application, if you 
quit Yojimbo, and at several other times.

The Save menu item will be enabled for the brief period of time your changes 
are not saved, so you can feel free to type Command-S at any time.

You can see this by making a new note, quickly popping open the File menu, 
waiting a moment, and looking again.


To be specific, Yojimbo doesn't edit "documents" and as such, 
doesn't have any sort of notion of an unsaved document.


--
Steve Kalkwarf
<[EMAIL PROTECTED]>


--
--
This message is sent to you because you are subscribed to
 the mailing list .
To unsubscribe, send mail to: <[EMAIL PROTECTED]>
List archives:  
Have a feature request, or not sure if the software's working
correctly? Please send mail to: <[EMAIL PROTECTED]>