On Tue, Feb 17, 2009 at 12:54 AM, Steve Borho <[email protected]> wrote:
> On Tue, 2009-02-17 at 00:42 +0000, TK Soh wrote:
>> On Tue, Feb 17, 2009 at 12:40 AM, TK Soh <[email protected]> wrote:
>> > On Tue, Feb 17, 2009 at 12:36 AM, Steve Borho <[email protected]> wrote:
>> >> On Tue, 2009-02-17 at 00:04 +0000, TK Soh wrote:
>> >>> [resending to cc dev list]
>> >>>
>> >>> On Mon, Feb 16, 2009 at 4:27 PM, Simon Heimberg <[email protected]> 
>> >>> wrote:
>> >>> > # HG changeset patch
>> >>> > # User Simon Heimberg <[email protected]>
>> >>> > # Date 1234800759 -3600
>> >>> > # Node ID 9521df28903da5391789bcbb2b341613c9e01a10
>> >>> > # Parent  a7d4a0c9e5e57b5be8c174e79ba22d4ac7621f7d
>> >>> > add separate module for menu creation
>> >>>
>> >>> Do we need this? IIRC, the menu creation is needed only for context
>> >>> menu. It may be 'cleaner' to have classes in different modules, but if
>> >>> we are not reusing the classes else where, it would just add
>> >>> unnecessary complexity to the code with not apparent benefit.
>> >>
>> >> The idea is to share it with Nautilus and other future shell
>> >> integrations.
>> >
>> > I see. But is the pywin32 portable to nautilus?
>>
>> I meant the pywin32 code.
>
> No, that will have to get cleaned before the module can be shared.
> But that doesn't seem like it will be too bad.  There doesn't appear
> to be anything windows specific in menuthg.py.

OK. I will try to take a look later when I have more time.

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Tortoisehg-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop

Reply via email to