Discussion:
Release plans for abook
(too old to reply)
Raphaël Droz
2013-06-13 21:07:09 UTC
Permalink
My name is Gaetan and I package abook for the Arch Linux distribution.
[...] Also I was wondering if you had any future release plans for abook.
[...] I have been using a git snapshot myself lately; that snapshot is
perfectly stable
[...]
Hi,

this is indeed a good idea, especially if we can expect that enough
testing of the git sources happened during the last months.

I'm currently in a kind of roaming-mode, ie: no guarantee before the end
of July, but that leaves time for last-minute regression reports to pop-up.


A couple of open notes:

* I would go for "0.6.3", what means no "officially" stable "0.6.2" will
ever exist

* I hope everyone will be happy with the assumption done for the mouse
support (scrolling and text-selection)

* I'm pretty sure the way I retrieve custom fields in [8fd8454] for the
allcsv output isn't adequate but haven't found a better way
(Jaakko, if you read me)
[ custom fields, if considered and correctly used in other functions,
could be even greater ]
Roger
2013-06-13 21:13:57 UTC
Permalink
Post by Raphaël Droz
* I hope everyone will be happy with the assumption done for the mouse
support (scrolling and text-selection)
I wouldn't worry about it too much as most have been stuck on abook-0.6.0_pre2
on Gentoo for sometime. If they don't like it, they can always remain at
version 0.6.0_pre2 and await for the next release to adjust it based on user
feedback.

You will likely see no user feedback until after a release is made. Shrugs.
People make mistakes. People are only able to shine, if they're able to adjust
through using user feedback. ;-)

(I might kill some time here and get the git version for kicks.)
--
Roger
http://rogerx.freeshell.org/
Roger
2013-06-14 07:03:21 UTC
Permalink
Post by Raphaël Droz
* I hope everyone will be happy with the assumption done for the mouse
support (scrolling and text-selection)
OK. I pulled git today and built.

Found the only mention of mouse support within the git abookrc.

Enabled it within $HOME/.abook/abookrc with "set use_mouse=true"

Still no mouse button or mouse scrolling within abook within the virtual
terminal or Xorg using GNU Screen. However, using a plain urxvt terminal
within Xorg, I was able to get mouse support.

A few issues:

1) No back out key except for 'q' when viewing a record, and no key apparently
escapes editing a field of a record.

Should use the 'ESC' key to both; back out of viewing a record and, escaping an
entry field being edited.

Quite possibly, use the 'Right Mouse Button' for backing out of a record and
into the list view. Also could use the 'Right Mouse Button' for escaping an
entry being edited. In other words, make 'ESC' = 'Right Mouse Button'.

2) Man for abookrc contains non-alphabetized options within the 'VARIABLES'
paragraph.
--
Roger
http://rogerx.freeshell.org/
Jostein Berntsen
2013-08-05 16:39:35 UTC
Permalink
Post by Roger
Post by Raphaël Droz
* I hope everyone will be happy with the assumption done for the mouse
support (scrolling and text-selection)
OK. I pulled git today and built.
Found the only mention of mouse support within the git abookrc.
Enabled it within $HOME/.abook/abookrc with "set use_mouse=true"
Still no mouse button or mouse scrolling within abook within the virtual
terminal or Xorg using GNU Screen. However, using a plain urxvt terminal
within Xorg, I was able to get mouse support.
1) No back out key except for 'q' when viewing a record, and no key apparently
escapes editing a field of a record.
Should use the 'ESC' key to both; back out of viewing a record and, escaping an
entry field being edited.
Quite possibly, use the 'Right Mouse Button' for backing out of a record and
into the list view. Also could use the 'Right Mouse Button' for escaping an
entry being edited. In other words, make 'ESC' = 'Right Mouse Button'.
2) Man for abookrc contains non-alphabetized options within the 'VARIABLES'
paragraph.
Any news on release plans for a new version?

Jostein
Raphaël
2013-11-27 17:07:12 UTC
Permalink
Post by Jostein Berntsen
Any news on release plans for a new version?
Following Roger's advise a live Gentoo ebuild for abook (git) is
provided here [1] so that gentoo'ist can test it further before tagging
and releasing.



[1] https://bugs.gentoo.org/show_bug.cgi?id=462338
Roger
2013-11-28 00:14:23 UTC
Permalink
Post by Raphaël
Any news on release plans for a new version?=20
Following Roger's advise a live Gentoo ebuild for abook (git) is
provided here [1] so that gentoo'ist can test it further before tagg=
ing
Post by Raphaël
and releasing.
[1] https://bugs.gentoo.org/show_bug.cgi?id=3D462338
I personally don't mind Live EBuilds or EBuild files containing CVS/S=
VN/GIT=20
repositories as long as they're properly masked from common users acc=
identally=20
pulling them into their system. The reason I enjoy the live ebuilds,=
I can=20
very easily build and test recent code from projects I have not impor=
ted using
CVS/SNV/GIT, nor desire spending the time setting up the development=
=20
environment for compiling and installing the application. Live EBuil=
ds also=20
seem to exploit the Gentoo platform for what it was likely initially =
engineered=20
to do to begin with. (ie. Meet the recent library depends more easil=
y, depends=20
required by developers when coding their program or application.) In=
stead,=20
Gentoo only makes meeting depends more easily, while not encouraging =
Live=20
EBuilds which further exploits this feature.

However I need to mention, many of the Gentoo EBuild repository devel=
opers=20
frown upon CVS/SVN/GIT builds as they're afraid of admitting unstable=
code, or=20
encouraging packages to release stable snapshots. (The later already=
has=20
plenty of influence from other more popular binary distros. And furt=
her=20
masking the Live EBuild already encourages stable packages.) I stron=
gly feel=20
the some of the Gentoo maintainers or volunteers discouraging live EB=
uilds, are=20
cutting themselves short by omitting one of Gentoo's strong features.

Gentoo Live EBuilds (ie. EBuilds built using CVS/SVN/GIT repositories=
) promote=20
the following:

1) Target a larger audience for testing code. (Albeit, only some tes=
ters=20
submit bug reports, but a larger audience should exponentially increa=
se=20
possible bug reports, encouraging more stable code. ;-)

2) Easier compiling and installing of CVS/SVN/GIT repositories.

3) Gentoo now has several more FEATURES for debugging nowadays, then =
in the=20
past years. (ie. 'splitdebug' - along side keeping source code after=
=20
installing, along side 'noclean' or 'installsources' for keeping the =
source=20
code after install.) A lot of these features can be enabled only for=
certain=20
EBuilds by using the now standard "/etc/portage/package.env" &=20
"/etc/portage/env/" files/folders!


The one area where they may have some reasonable excuse, having a low=
er-level=20
package for which is heavily depended on by the system being a develo=
pment=20
version, which would cause higher-level packages depending on it prob=
lems. (ie. =20
Causing users to unknowingly submit bugs to bugs.gentoo.org instead o=
f=20
upstream.) However, the majority of Live EBuilds refused are higher-=
level=20
entry-level applications not having any code depend on it and are alr=
eady=20
appropriately masked.

So in short, don't be surprised if they mark the Live EBuild as close=
d. What=20
happens when you admit Debian-minded folks into a feature rich Distro=
. ;-)

=2E.. or you might get lucky, as the Mutt EMail client is heavily use=
d by smarter=20
folks! (Sorry for the extended EMail, but wanted to clarify this as =
I guess I=20
gave advice on using Live EBuilds somewhere previously!)


--=20
Roger
http://rogerx.freeshell.org/

Raphaël
2013-11-27 14:09:45 UTC
Permalink
Hi,
Post by Roger
Found the only mention of mouse support within the git abookrc.
The changelog is also helpful, but indeed mouse support wasn't advertised
in abook(1). As most changes are "optional" the implicit rule was used:
- new command-lines switches => abook(1)
- new abookrc options affecting the interactive mode => abookrc(5)
It's kind of "arbitrary", but any nicer solution welcomed.
Post by Roger
1) No back out key except for 'q' when viewing a record, and no key apparently
escapes editing a field of a record.
Should use the 'ESC' key to both; back out of viewing a record and, escaping an
entry field being edited.
?
doesn't ^G (CTRL-G) cancels editing, as it always did ?
Post by Roger
Quite possibly, use the 'Right Mouse Button' for backing out of a record and
into the list view. Also could use the 'Right Mouse Button' for escaping an
entry being edited. In other words, make 'ESC' = 'Right Mouse Button'.
I myself don't use mouse support a lot, has Thorsten any opinion about this ?
Post by Roger
2) Man for abookrc contains non-alphabetized options within the 'VARIABLES'
paragraph.
I don't understand. Is it about formatting ? which ones are a concern ?
Do you mean that all option's value should be underlined, or something
else ?


thank you!
Thorsten Wißmann
2013-11-27 18:06:13 UTC
Permalink
Post by Raphaël
Post by Roger
Quite possibly, use the 'Right Mouse Button' for backing out of a record and
into the list view. Also could use the 'Right Mouse Button' for escaping an
entry being edited. In other words, make 'ESC' = 'Right Mouse Button'.
I myself don't use mouse support a lot, has Thorsten any opinion about this ?
To be as close as possible to the behaviour of ordinary GUI Applications
abook should cancel editing if the user clicks anywhere outside the text
box (in particular when right-clicking somehwere).

By the way I used the title "abook-currentversion" on the top left as
the escape button (but not yet when editing some entry). And it's also
not mentioned in the man page. I can write patches for all three issues
later, if it's OK for you.

Regards,
Thorsten
Thorsten Wißmann
2013-11-27 22:12:36 UTC
Permalink
Post by Thorsten Wißmann
Post by Raphaël
Post by Roger
Quite possibly, use the 'Right Mouse Button' for backing out of a record and
into the list view. Also could use the 'Right Mouse Button' for escaping an
entry being edited. In other words, make 'ESC' = 'Right Mouse Button'.
I myself don't use mouse support a lot, has Thorsten any opinion about this ?
To be as close as possible to the behaviour of ordinary GUI Applications
abook should cancel editing if the user clicks anywhere outside the text
box (in particular when right-clicking somehwere).
It turned out to be much more difficult than expected, because the
prompt in the bottom line directly is readline. And I can't access the
main loop of readline(). (I think that it is not worth rewriting it)
Post by Thorsten Wißmann
By the way I used the title "abook-currentversion" on the top left as
the escape button (but not yet when editing some entry). And it's also
not mentioned in the man page. I can write patches for all three issues
later, if it's OK for you.
I described the First-Row-Behaviour in the attached
0001-Describe-first-row-clicking-in-abookrc.5.patch -- please merge or
improve it :)

Regarding the Right-Clicking: When binding the right mouse button, then
it is not possible to access the right-click menu of your terminal
emulator. Having the first-row-trick, the right-click-escape feature
is not very intuitive and annoying for the context-menu-users, IMO. If
you want to play with it anyway, just try the attached patch
0002-Let-mouse-right-click-behave-like-the-escape-key.patch but I don't
think it should be merged. Maybe making it configurable solves these
problems. Opions?

Regards,
Thorsten
Roger
2013-11-27 23:43:18 UTC
Permalink
Hi,=20
Post by Roger
Found the only mention of mouse support within the git abookrc.
The changelog is also helpful, but indeed mouse support wasn't adver=
tised
in abook(1). As most changes are "optional" the implicit rule was us=
- new command-lines switches =3D> abook(1)
- new abookrc options affecting the interactive mode =3D> abookrc(5)
It's kind of "arbitrary", but any nicer solution welcomed.
Post by Roger
1) No back out key except for 'q' when viewing a record, and no ke=
y apparently=20
Post by Roger
escapes editing a field of a record.
Should use the 'ESC' key to both; back out of viewing a record and=
, escaping an=20
Post by Roger
entry field being edited.
?
doesn't ^G (CTRL-G) cancels editing, as it always did ?
Eh. Now I know how to escape when typing the email address into the =
"TO:"=20
field! (I've always just used ESC, albeit a major sin when typing as=
my=20
fingers are leaving the keyboard.)
Post by Roger
Quite possibly, use the 'Right Mouse Button' for backing out of a =
record and=20
Post by Roger
into the list view. Also could use the 'Right Mouse Button' for e=
scaping an=20
Post by Roger
entry being edited. In other words, make 'ESC' =3D 'Right Mouse Bu=
tton'.
I myself don't use mouse support a lot, has Thorsten any opinion abo=
ut this ?

Can't remember typing this, or if it was my idea or somebody else's m=
erged into=20
a reply. (Maybe something I witnessed while testing mouse support wi=
thin the=20
terminal during this time period?)
Post by Roger
2) Man for abookrc contains non-alphabetized options within the 'V=
ARIABLES'=20
Post by Roger
paragraph.
I don't understand. Is it about formatting ? which ones are a concer=
n ?
Do you mean that all option's value should be underlined, or somethi=
ng
else ?
I think as I was reading the abookrc manual page, I found a listing o=
f=20
non-alphabetized variables. Think it's preferable to alphabetize or =
order=20
things when possible? (The comment was likely non-related to mouse s=
upport,=20
and more general in nature.)


--=20
Roger
http://rogerx.freeshell.org/
Loading...