[qbzr] QBzr 0.16 released
Gary van der Merwe
with new features - QBzr 0.16 codenamed "Acacia".
This release add lots of new features for working with your working
tree. I've bloged about these (with screen shots) here:
http://bazaarvcs.wordpress.com/2009/11/08/new-working-tree-features-in-qbzr/
What's new in this release:
* qswitch:
* Added support for --create-branch option to "bzr switch". (A. S. Budden)
* SubprocessUIFactory and QUIFactory now both support get_username, and
get_boolean. (Bug #421851, Gary van der Merwe)
* Save the size of Dialogs when the user press Esc. (Bug #417809,
Gary van der Merwe)
* qlog:
* Get the max main_line digets in a different way so that we don't break
--no-graph. (Bug #455867, Gary van der Merwe)
* Corrected the margin for the revision number column. (Gary van der Merwe)
* When loading the file list delta, only lock the repositories that are
being used. If the 2 trees are from the same repositories, load them
together. (Gary van der Merwe)
* When viewing a svn repo, only show the file list if 1 revision is selected,
and if so, use a optimized method to do so. (Bug #450225,
Gary van der Merwe)
* Show a throbber above the file list while a delta is being loaded.
(Gary van der Merwe)
* Fix a bug when refreshing a branch with revisions that have been removed.
(Bug #435486, Gary van der Merwe)
* qlog/qannotate:
* Preserve leading whitespace in the lines of the log message.
(Max Bowsher)
* qadd:
* Don't show unchanged directories that contain ignored files.
(Bug #462435, Gary van der Merwe)
* qcommit, qadd, qrevert:
* Directoies with 4 or more sub items are grouped in the tree view.
(Bug #456198, Gary van der Merwe)
* Correct the old path shown for renamed files. (Bug #432572,
Gary van der Merwe)
* Passing a directory via the command line now correctly checks the
directory. (Bug #435034, Gary van der Merwe)
* For qcommit, It is now possible to select unversioned file and directories
via the command line. (Gary van der Merwe)
* Automaticly expand to the check items on load. (Gary van der Merwe)
* Fix View for unversoined files when run from a sub directory of the
working tree. (Gary van der Merwe)
* qcommit/qbrowse:
* Conflicts are shown in the status column. External merge applications
can be launched to resolve these conflicts, and the conflicts can be
marked as merged. (Bug #174509, Gary van der Merwe)
* Improved the usibility of the context menu add, and revert actions.
These now directly use the api, rather than via subprocess. There is
now no prompt for add. With large trees, there is less flicker when the
tree is refreshed, and the scroll position is remembered.
(Gary van der Merwe)
* It is now possible to rename and move files or directories, and to mark
files or directories that have allready been renamed or moved as such.
(Gary van der Merwe)
* It is now possible to remove files from the branch. (Gary van der Merwe)
* Show blank icon for missing files. (Bug #418471, Gary van der Merwe)
* qcommit/uncommit:
* Catch AttributeError in save of commit_data during qcommit and/or uncommit
in lightweight checkout from branch accessed via smart-server
(lp:, bzr+ssh://, bzr:// etc).
(Bug #434034 Bug #430382 Bug #463296, Alexander Belchenko)
* qsubprocess:
* Show actual command-line to user when we invoke action via qsubprocess.
(Bug #476025, Alexander Belchenko)
* qcommit:
* Don't run `bzr add --no-recurse` before commit if there is nothing to add.
(Alexander Belchenko)
* qplugins:
* Format plugin version nicely even if it does not follow bzr standards on
version_info tuple. (Bug #475286, Alexander Belchenko)
Download
--------
Source code:
http://launchpad.net/qbzr/trunk/0.16/+download/qbzr-setup-0.16.exe
Universal windows installer:
http://launchpad.net/qbzr/trunk/0.16/+download/qbzr-setup-0.16.exe
Release page:
https://launchpad.net/qbzr/trunk/0.16
QBzr at Launchpad (Code, Bugs, Translations, Answers):
https://launchpad.net/qbzr
Gary
Algis Kabaila
I realise that QBzr is MS Win oriented and the power be with you. I use
ubuntu and want to run 0.16 QBzr as well as QBzr head (which, I gather, has at
this time unresolved conflicts).
For version 0.16:
1. If the tar ball is expanded in directory ~/xyz and I place a symbolic link
QBzr -> ~/xyz
then to run the QBzr CLI would require entry
bzr QBzr
Is that correct?
2. How can I access several translations of QBzr? I want to see it in a
working GUI, not just in a file. My location is Australia and the default
language is English. However, I am interested in different translations. I
found it very interesting to diff the some translations in files in "po"
subdirectory, viz. "ru" against "uk". To change the location just for that is
so inconvenient that it is not a practical proposition.
3. How can I run "head" of QBzr? It is very easy to change the sym links, but
that seems to leave some "unhappiness" in some __init__ methods. Is it enough
to delete __init__.pyc and let it be regenerated from __init__.py?
TIA,
OldAl.
--
Algis Kabaila, MEngSc, PhD(Eng)
http://akabaila.pcug.org.au/StructuralAnalysis.pdf
Alexander Belchenko
> On Monday 09 November 2009 10:33:35 Gary van der Merwe wrote:
>> On behalf of QBzr development team I'd like to announce a release brim
>> with new features - QBzr 0.16 codenamed "Acacia".
>>
>> This release add lots of new features for working with your working
>> tree. I've bloged about these (with screen shots) here:
>> http://bazaarvcs.wordpress.com/2009/11/08/new-working-tree-features-in-qbzr
>> /
>>
> Gary,
>
> I realise that QBzr is MS Win oriented and the power be with you.
This is too far from true. QBzr is cross-platform tool. It's just happen to be main GUI library for
TortoiseBzr which is Windows-only tool. AFAIK QBzr runs on all 3 major platforms.
So your statement is clearly false.
Alexander Belchenko
> On behalf of QBzr development team I'd like to announce a release brim
> with new features - QBzr 0.16 codenamed "Acacia".
>
> This release add lots of new features for working with your working
> tree. I've bloged about these (with screen shots) here:
> http://bazaarvcs.wordpress.com/2009/11/08/new-working-tree-features-in-qbzr/
> Download
> --------
> Source code:
> http://launchpad.net/qbzr/trunk/0.16/+download/qbzr-setup-0.16.exe
Gary, there is copy-paste error. It should be:
Source code:
http://launchpad.net/qbzr/trunk/0.16/+download/qbzr-0.16.tar.gz
Alexander Belchenko
Congratulations on new shiny release!
QBzr rocks!
Martin Pool
> I realise that QBzr is MS Win oriented and the power be with you. I use
> ubuntu and want to run 0.16 QBzr as well as QBzr head (which, I gather, has at
> this time unresolved conflicts).
>
> For version 0.16:
> 1. If the tar ball is expanded in directory ~/xyz and I place a symbolic link
> QBzr -> ~/xyz
> then to run the QBzr CLI would require entry
> bzr QBzr
> Is that correct?
No, it would still be qbzr. However to install it, it needs to be in
~/.bazaar/plugins/qbzr
> 2. How can I access several translations of QBzr? I want to see it in a
> working GUI, not just in a file. My location is Australia and the default
> language is English. However, I am interested in different translations. I
> found it very interesting to diff the some translations in files in "po"
> subdirectory, viz. "ru" against "uk". To change the location just for that is
> so inconvenient that it is not a practical proposition.
I don't really understand. If you want to run QBzr in a different
language, use something like
LANG=ru_RU.UTF-8 bzr qbzr
> 3. How can I run "head" of QBzr? It is very easy to change the sym links, but
> that seems to leave some "unhappiness" in some __init__ methods. Is it enough
> to delete __init__.pyc and let it be regenerated from __init__.py?
I don't know what this is about. You don't need to delete the pyc
files. Just run "bzr branch lp:qbzr ~/.bazaar/plugins/qbzr" and it
should be ok.
--
Martin <http://launchpad.net/~mbp/>
Martin Pool
> Actually I am really interested to see Lithuanin translations in action. No
> such luck, as there are no lt translation in the po directory of qbzr :)
>
> However, there is a "lt" (Lithuanian) translation package, in bzr-explorer's
> po files, but I was unable to invoke it. I also tried some widely used
> languages, viz. French, German. Again I did not succeeed to run the bzr-
> explorer in one of those languages.
>
> In a few days time, I will ask Ian C. But let him first recover from his
> illness. I believe it is all my own fault - missing language package or
> something of that sort. Happy to note that the "qlog" works fine in de, fr,
> ru, uk.
I think you need to rebuild the translation files, which you can do with
./setup.py build
then this worked for me
LANG=lt_LT.UTF-8 bzr explorer
I see these translations are mostly yours.
<https://translations.edge.launchpad.net/bzr-explorer/trunk/+pots/explorer/lt/+translate>
Thanks for translating it!
--
Martin <http://launchpad.net/~mbp/>
Algis Kabaila
On Tuesday 10 November 2009 10:35:04 Martin Pool wrote:
> 2009/11/9 Algis Kabaila <akab...@pcug.org.au>:
> > I realise that QBzr is MS Win oriented and the power be with you. I use
> > ubuntu and want to run 0.16 QBzr as well as QBzr head (which, I gather,
> > has at this time unresolved conflicts).
> >
true that many/most developers use posix OS and that makes the MS Win users,
prepared to test, even more precious. The above was meant as a compliment.
> > For version 0.16:
> > 1. If the tar ball is expanded in directory ~/xyz and I place a symbolic
> > link QBzr -> ~/xyz
> > then to run the QBzr CLI would require entry
> > bzr QBzr
> > Is that correct?
>
> No, it would still be qbzr. However to install it, it needs to be in
> ~/.bazaar/plugins/qbzr
Yes. Actually it was installed in a separate directory and a symbolic link
qbzr in .bazaar/plugins/ points to it. The bzr q<command> works fine in
several languages.
>
> > 2. How can I access several translations of QBzr? I want to see it in a
> > working GUI, not just in a file. My location is Australia and the
> > default language is English. However, I am interested in different
> > translations. I found it very interesting to diff the some translations
> > in files in "po" subdirectory, viz. "ru" against "uk". To change the
> > location just for that is so inconvenient that it is not a practical
> > proposition.
>
> I don't really understand. If you want to run QBzr in a different
> language, use something like
>
> LANG=ru_RU.UTF-8 bzr qbzr
Yes, I do, want to run some programs in several different languages, because I
ammultilingual and I have tried to help with some translations and would like
to continue to do so.
@Alexander - As you suggested,
LANG=ru bzr qlog <a directory with a branch> works fine.
Actually I am really interested to see Lithuanin translations in action. No
such luck, as there are no lt translation in the po directory of qbzr :)
However, there is a "lt" (Lithuanian) translation package, in bzr-explorer's
po files, but I was unable to invoke it. I also tried some widely used
languages, viz. French, German. Again I did not succeeed to run the bzr-
explorer in one of those languages.
In a few days time, I will ask Ian C. But let him first recover from his
illness. I believe it is all my own fault - missing language package or
something of that sort. Happy to note that the "qlog" works fine in de, fr,
ru, uk.
>
> I don't know what this is about. You don't need to delete the pyc
> files. Just run "bzr branch lp:qbzr ~/.bazaar/plugins/qbzr" and it
> should be ok.
Sorry about the above para. - I was just blundering about. I should return to
my own program writing where the problems are created solely by me (at least
at present).
Martin, I fail to understand how you find the time to answer such a volume of
mail - a big *thanks* to you!
Alexander - I do appreciate you going to the trouble to answer my questions.
Algis Kabaila
> 2009/11/10 Algis Kabaila <akab...@pcug.org.au>:
>
> I think you need to rebuild the translation files, which you can do with
>
> ./setup.py build
>
> then this worked for me
>
> LANG=lt_LT.UTF-8 bzr explorer
>
LANG=lt bzr explorer
works also, but bzr gives a bunch of warnings (I think the user well deserves
to get those).
> I see these translations are mostly yours.
> <https://translations.edge.launchpad.net/bzr-explorer/trunk/+pots/explorer/
>lt/+translate> Thanks for translating it!
Thanks for putting up with an old fellow. The software translation has a steep
learning curve, but I think I am getting there. As a consequence my chess
playing and my own textbook/programs are being neglected. No great loss :).
Martin, thank you again. I am in the process of translating the bzr-
migration-docs. Managed to twig how to use make to create html output in
_build subdirectory. It would be nice to look at the output, but so far only
managed to display the menu page. I probably should engage a 7 year old to
figure it out, but my youngest grandchild is 20 and not in Canberra...