On Fri, Jan 9, 2009 at 6:42 AM, Steve Borho <[email protected]> wrote: > On Fri, Jan 9, 2009 at 12:39 AM, TK Soh <[email protected]> wrote: >> >> On Thu, Jan 8, 2009 at 4:02 PM, Steve Borho <[email protected]> wrote: >> > On Thu, Jan 8, 2009 at 9:40 AM, Peter Ruibal <[email protected]> wrote: >> >> >> >> Of the above, built-in hgshelve/record support in hggtk.commit would be >> >> my >> >> most wanted :) >> >> >> >> I'd really like to eventually get the following in crew (in addition to >> >> the above): >> >> >> >> 1) Run native hgtk in native python on windows (inclusion of an >> >> hgtk.bat >> >> in contrib/win32, like Mercurial) >> >> 2) Able to install from source from setup.py on non-win32 systems >> >> (...so >> >> python can import hggtk on linux) >> >> 3) Build windows installer from setup.py >> > >> > I agree with all that. If we did get a decent shelve implementation, I >> > think we could unbundle Qct and have people install it separately if >> > they >> > still wanted to use it. This would roughly halve the size of the THG >> > installer. >> >> Is the 'halve the size' contributed by Qt? If so, isnt' hgconf still >> depend on Qt? > > I don't see any reason to keep those dialogs once Qct is removed. Nearly > everything they provide is covered better by thgconfig, except for the > username one, and that has a GTK version we could keep.
Naturally, having just on config dialog will take away some confusion. So the commit hook can be converted easily to call thgconfig for user to input ui.username? ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
