On Mon, Jan 11, 2010 at 12:00 PM, Yuki KODAMA <endflow....@gmail.com> wrote: > On Tue, Jan 12, 2010 at 01:20, Steve Borho <st...@borho.org> wrote: >> On Mon, Jan 11, 2010 at 10:15 AM, Yuki KODAMA <endflow....@gmail.com> wrote: >>> On Tue, Jan 12, 2010 at 00:30, Steve Borho <st...@borho.org> wrote: >>>> On Mon, Jan 11, 2010 at 2:42 AM, Yuki KODAMA <endflow....@gmail.com> wrote: >>>>> Hi all, >>>>> >>>>> Before feature freeze, I'd like to tweak Commit dialog. >>>>> Here is my plan: >>>> <snip> >>>> >>>> I'll also be hacking on the commit tool over the next couple of weeks, >>>> though mostly in status.py. I want to start whittling down these bugs >>>> and feature requests: >>>> >>>> #709 - commit preview not refreshed entirely on F5 >>>> #561 - merge diffs with renames >>>> #507, #338 - subrepo support >>>> #12 - show rename diffs, allow change selection >>> >>> I see. Probably I can finish my TODOs on Commit dialog in this week. >>> After it, I want to do these tasks as much as possible: >>> * improve column setting dialog of Repository Explorer to store widths >>> ** make it a component can be used for others (Datamine, MQ, ...) >>> * fix some layout issues >>> * refactoring statusbar.py >>> * put preview dialog for export/rebase/transplant commands >>> * update checker for TortoiseHg >> >> Sounds good. >> >> For my money, I would do the last first, but you are always free to do >> as you like. :) > > Thanks, I can't promise it now ;) > >> How did you intend for the update checker to operate? I thought about >> it a bit over the weekend, and thought that it would be best >> integrated into the about dialog. > > I think so. It's appropriate implementation. > However most users don't open About dialog frequently with the > exception of users who wanted to check TortoiseHg's update. > > So I have one idea: Update checker is launched when the user runs > any hgtk command at intervals of 1 week (configurable). > For the user feels it annoying, it should be have checkbox option > to disable update check feature. TortoiseHg setting dialog will have > the option to set the interval of update check. > > As far as the way to detect update, I have no good idea. > If we check the download page or RSS on Bitbucket, we need to ask > them whether it's possible. Because it causes the overload of web server.
Yes, it would definitely need to be on the static web site, something like http://tortoisehg.bitbucket.org/currentversion.html with perhaps just two lines: 0.9.2 http://bitbucket.org/tortoisehg/stable/downloads/tortoisehg-0.9.2-1-hg-1.4.2.exe and whatever HTML formatting we need to make it parse-able by Python's HTML code. I'll ask the Bitbucket folks about it, but the static HTML is heavily cached so they probably won't have any problems with it. -- Steve Borho ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Tortoisehg-discuss mailing list Tortoisehg-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
