Re: Launch* functions moved

> I have two ideas:
> 1. We can create a sub-menu for all shell actions (like Shell Action) and
> that should indicate the difference from "cvs edit" command

Sounds good to me.


> 2. We could rename the new item to "Edit selection with editor". Maybe we
> should move the Open commands to the top so we would have:
>  - Open
>  - Open with...
>  - Edit with editor
>  - Edit with <Notepad>

Also OK... not sure which one I'd prefer really...


> This is one of the reasons to move the Open to the top actually - it would
> be more clear that "Edit with" options are in addition to the Open which
> will most probably be used.

But you still agree that the Edit item should be the new double-click
action? I don't see much of potential confusion when invoking this from a
menu as it will be absolutely clear from the captions. The significant
change that we must take precautions against is that of the double-click
behaviour which has no label and will thus be unexpected...


> But one-off dialog box with explanations sounds
> like a good idea, plus we should add that to the "Tip of the day" dialog.

Yep.


> >I was even already thinking whether it might not be a good idea to
> >even offer a simple one-step configuration UI for this as doing this
> >via the OS dialogs could be quite awkward at times.
>
> I think it 's a good idea actually. I wonder if there are any API for
> creating "edit" associations...

I have already spent most of today researching this. There appears to be no
API for creating or even easily querying associations (except for "open").
All the docs just create the registry keys manually. I think I saw mention
of an API for opening up the association dialog though...

I have however already written a draft macro now which will query the
relevant values for the file type of the current selection, present the old
value (if one exists, otherwise I propose the current "open" or default
command if available) and allow the user to change it or enter a new one.
(btw: the macro will require either Mark Hammond's Win32 extensions or
ActivePython (which already comes bundled with them) - otherwise it will
simply not be registered on the menu at all)
Of course this would be a whole lot more useful with a macro-accessible
browse-for-file dialog... looking into that next once I've got the thing
cleaned up a bit for posting... ;)

P.S.: I saw that you kept and even adjusted the LaunchEditor and
LaunchViewer functions even though they are really obsolete now. As I
mentioned before the only reason I did not remove them from my patch already
was not to invalidate all of Jens' work... they have no more purpose at all
as all calls to them have been replaced with appropriately parameterized
calls to LaunchHandler instead now....

Cheers,

Oliver
----  ------------------
JID:  [email protected]
ICQ:  18777742     (http://wwp.icq.com/18777742)


 

Yahoo! Groups Links

To visit your group on the web, go to:
 http://groups.yahoo.com/group/cvsgui-dev/

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/