Re: Re: CvsAlert changes

Jens,

>Hmmh, I still see the "Move to trash" as a reversible operation
>(at least on the Mac) and it's not different than switching to Finder
>(the Mac "Explorer") and moving the file to trash from there (as a
>matter of fact, the original implementation of move to trash actually
>just sent a message to the Finder to have it move the files to the trash).

We are also using the shell functions to perform that, but it's uncertain
what exaclty will happen because it depends on the personal settings. It's
possible that the file will be lost without the backup. That makes the erase
operation extremely dangerous. IMHO it's better to play safe and risk a
little annyance to the user than to destroy some potentially valuable file.

>And I don't see why it's not intended to be a routine task - it's
>very convenient and avoids having to switch to an other app, go
>hunting for the file, etc.

It's not a routine task because it's not a CVS task. Some few years back the
erase command was a neccesity because it was the only way to abandon the
changes made to the file and start a new. You would have to remove the file
and then do "cvs update" to get the unchanges file from the repository.
However CVS is now providing the -C option to the update command which makes
the erase obsolete. In fact the "update -C" is much safer than simple
removal of the file because it will make the backup if the file was
modified.

The erase may be used to clean up a non-CVS files eventually, but then again
we have the set of macros to do that task.

>But we can still have different default buttons on each platform
>based on whether move to trash is easily reversible or not.

OK, I will just have to accept the fact that Mac users like to live
dangerously so the Mac will have default button set to OK for files erase
while Windows will stick to Cancel. I have gCvs using the Cancel as well
which Kalle can review and change if necessary ;)

>BTW: Did you take a look at the PromptMessage function?
>I've implemented this for the Mac using CvsAlert and I think
>we could remove all platform conditional stuff in there and use
>CvsAlert for all platforms...

Yes, PromptMessage is waiting for it's turn ;)

>(The PromptEditMessage probably has to remain as it is, since
>it requires an additional edit field. I don't think we should extend
>CvsAlert to also provide an edit field - that's just too special to put
>into the CvsAlert API)...

I have not yet decided what to do with that one. I will probably move the
whole thing to another file - I want to get rid of AskYesNo.cpp/h files
after the AskYesNo function is gone and create a new one with a more
suitable name.

I will let you guys know how it develops...

Best Regards,
Jerzy

------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark
Printer at MyInks.com. Free s/h on orders $50 or more to the US & Canada.
http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/NhFolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
[email protected]

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/