On 2009 Feb 5, at 10:19 AM, Steve Borho wrote: > On Thu, Feb 05, 2009 at 08:22:29AM +0000, TK Soh wrote: >> On Wed, Feb 4, 2009 at 5:16 AM, Steve Borho <[email protected]> wrote: >>> On Wed, 2009-02-04 at 04:58 +0000, TK Soh wrote: >>>> I just pull from you repo, but got a ImportError when trying to >>>> run commit.py: >>>> >>>> ImportError: cannot import name ParseError >>> >>> My bad, I thought this exception was moved from cmdutil.py. It >>> actually >>> came from dispatch.py. I've pushed a fix. >> >> Here's some of my observation: >> >> Before anything further, I just want to state that I understand how >> difficult it is to design a decent interface for this and that Steve >> has put in a lot of good work into implementing this. So everything I >> have to say is strictly my personal view being a user (vs. being a >> developer). > > This is the kind of feedback I'm looking for.
I can't wait until the regular automated installer builder is working to be able to try these new versions out too. "On Paper" lots of things sound promising, but it isn't until the mouse clicks hit the screen that you can really know... :) > Still, I would like to get a vote on what people think would be more > clear to first-time users: > > a) having separate dialogs for commit and shelve This makes some amount of sense to me, since one of the use cases my work group has is to suspend working on some changes, pull and update to a different changeset, make some changes there, commit (or maybe shelve and later-rinse-repeat). Often, then, shelve is a precursor to a pull/update and new work as much as to commit. > b) making shelve operate on selected hunks, while commit operates on > non-rejected hunks (keeping both functions in one tool) This one I would have to see and use, it sounds good in theory... > It's been my intention to expand on the shelve functionality to > support multiple named shelves. Part of that will be the ability to > browse the shelves and pick those to be re-applied to the working > directory. I've always figured this would be a separate tool from the > commit tool. I agree. But then I also thought having so many tools was confusing. Consider that the log viewer can start a merge, but a completely different dialogue is needed for committing the merge. Very tedious. I was very hopeful about the Google SoC project that would have unified all these different dialogues (if I remember (or have dreamt) correctly). --Doug ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Tortoisehg-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
