Promoting the use of Mercurial; was: Re: gnome dvcs survey results
Bill Barry
after.fallout at gmail.com
Thu Jan 8 14:02:40 UTC 2009
Steve Borho wrote:
>
>
> * tortoisehg shipping on the same day as hg (possibly even
> dropping the tortoise brand, just pushed as "hg for windows")
>
>
> I agree this is a goal, but it will take a bit more infrastructure
> before this is feasible. Building a THG installer these days is a
> long, complicated (and thus error prone) process.
>
> There have been many posts on this thread that list THG as a definite
> plus for Mercurial compared to other DVCS. I would like to take this
> opportunity to announce: "Help, please". We need more contributors.
> You don't need to use Windows to develop on THG; clone the repository
> and use hgtk.
I'd love to help, but there are 3 problems:
1. I really don't have time to donate (yet; hopefully this will change soon)
2. I don't feel that confident working in python yet
3. I have no idea how to even start working on thg
I do have a couple of ideas of things I would like to see happen:
* CI environment building the tip of various repositories
(thg-hg-crew-tip, tortoisehg-crew and tortoisehg at the least)
* console command that opens the "View Changelog" dialog (at the root
level unless provided a subdirectory/file)
* ability to move commands up or down a level in the menu
* do not display password part of url in the synchronize dialog
* ability to turn on separated pull and push (ie not needing to use the
synchronize dialog)
* potentially, auto-pull and auto-push when there is incoming and
outgoing changesets (it would have to be an option to turn on or off and
I haven't really thought about how desirable it actually is)
* context menu accesskeys
* olive clone
* context menu for mq integration
* more system integrated ui (no quit button in the corner; combo keys;
menues [hidden on vista until you press alt]; smaller button areas
[icons should be 16, 24, 32 or 48 px and buttons should be 18, 28, 36 or
52 px respectively and text should be beside not underneath the button])
>
> Depends on what you mean by extension. THG can use any Mercurial
> extension under the covers, just ask on the mailing list for that
> extension to be included. To add new dialogs, you mainly pick an
> existing one under hggtk/ and copy-paste-hack. PyGtk is pretty
> straight-forward to learn.
I mean like how can I set it up to run the shelve extension? Is there
some special directory to put the python file in? Do I need to do some
sort of precompilation step (where are the python files for thg
anyways)? Would it require me to make my own build of THG?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20090108/9ee5cce4/attachment-0001.html>
More information about the Mercurial
mailing list