knokiisync-users — If you are an end user, this list is for you.

Re: [Knokiisync-users] KnokiiSync 0.3.0 on it's way...

[Dimitris S. <dim...@li...>]

> On Thursday 10 July 2003 16:22, Robert Maier wrote: >
> Hi Dimitris,
> >
> > For me the crash after I read the phone book from the mobile still
> > persists in the CVS version.
>

Hi, found and fixed in CVS. While SF CVS server synchronize, you can grab the 
CVS version as a tarball from:

http://knokiisync.sf.net/knokiisync-071003.tar.bz2

Dimitris

Re: [Knokiisync-users] KnokiiSync 0.3.0 on it's way...

[Dimitris S. <dim...@li...>]

On Thursday 10 July 2003 16:22, you wrote:
> Hi Dimitris,
>
> For me the crash after I read the phone book from the mobile still
> persists in the CVS version.
>
> Here is the latest dump:
> -----
> [New Thread 16384 (LWP 12634)]
> 0x41009387 in waitpid () from /lib/libpthread.so.0
> #0  0x41009387 in waitpid () from /lib/libpthread.so.0
> #1  0x4072bc89 in KCrash::defaultCrashHandler(int) ()
>    from /opt/kde3/lib/libkdecore.so.4
> #2  0x410081ec in __pthread_sighandler () from /lib/libpthread.so.0
> #3  <signal handler called>
> #4  0x400437e2 in KABC::Addressee::detach() () from
> /opt/kde3/lib/libkabc.so.1 #5  0x4004b8a8 in
> KABC::Addressee::insertCustom(QString const&, QString const&, QString
> const&) () from /opt/kde3/lib/libkabc.so.1

Hi Robert, from what I can see, this is for a completely different reason. 
I'll look into it and let you know.

Dimitris

-- 
For people who like peace and quiet: a phoneless cord.

Re: [Knokiisync-users] KnokiiSync 0.3.0 on it's way...

[Robert M. <Rob...@es...>]

Hi Dimitris,

For me the crash after I read the phone book from the mobile still persists in 
the CVS version.

Here is the latest dump:
-----
[New Thread 16384 (LWP 12634)]
0x41009387 in waitpid () from /lib/libpthread.so.0
#0  0x41009387 in waitpid () from /lib/libpthread.so.0
#1  0x4072bc89 in KCrash::defaultCrashHandler(int) ()
   from /opt/kde3/lib/libkdecore.so.4
#2  0x410081ec in __pthread_sighandler () from /lib/libpthread.so.0
#3  <signal handler called>
#4  0x400437e2 in KABC::Addressee::detach() () from /opt/kde3/lib/libkabc.so.1
#5  0x4004b8a8 in KABC::Addressee::insertCustom(QString const&, QString 
const&, QString const&) () from /opt/kde3/lib/libkabc.so.1
#6  0x0805a428 in SyncView::readMobPhBook() ()
#7  0x08063940 in SyncView::readMobClicked() ()
#8  0x080687ca in SyncView::qt_invoke(int, QUObject*) ()
#9  0x40b6d8e7 in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0x40b6d78f in QObject::activate_signal(int) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0x40e6b3ec in QButton::clicked() () from /usr/lib/qt3/lib/libqt-mt.so.3
#12 0x40bf5716 in QButton::mouseReleaseEvent(QMouseEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0x40ba3954 in QWidget::event(QEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0x40b0c5f8 in QApplication::internalNotify(QObject*, QEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0x40b0bd76 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0x406b8929 in KApplication::notify(QObject*, QEvent*) ()
   from /opt/kde3/lib/libkdecore.so.4
#17 0x40aad5c8 in QETWidget::translateMouseEvent(_XEvent const*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0x40aaae30 in QApplication::x11ProcessEvent(_XEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0x40ac04f2 in QEventLoop::processEvents(unsigned) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x40b20b83 in QEventLoop::enterLoop() ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0x40b20a76 in QEventLoop::exec() () from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0x40b0c87f in QApplication::exec() () from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0x08068409 in main ()
#24 0x41165857 in __libc_start_main () from /lib/libc.so.6
-----

Best regards,
Robert.

On Thursday 10 July 2003 13:35, Dimitris Stasinopoulos wrote:
> Hi everyone,
>
> I finally implemented multiple subentry types per contact (eg. 3 work
> phones, 2 emails, etc). The only limitation is with URL and Note, as
> KDE's address book doesn't allow more than entry of these types. The code
> is ready and waiting in CVS, however, I do want to test it a bit more
> before I tag it as 0.3.0. If any of the usual adventurers want to have a
> go at it, please do, and let me know of any issues you find.
>
> Dimitris

-- 
------------------------------------------------------------------------------
Robert Maier			
ESAT SCD/COSIC                     ______      _____ _____ ______
Kasteelpark Arenberg 10           / ____/___  / ___//_  _// ____/
3001 Heverlee                    / /   / __ \ \__ \  / / / /
BELGIUM                         / /___/ /_/ /___/ /_/ /_/ /___
Phone: +32-16-32.18.53          \____/\____//____//____/\____/
Fax:   +32-16-32.19.69	
------------------------------------------------------------------------------

[Knokiisync-users] KnokiiSync 0.3.0 on it's way...

[Dimitris S. <dim...@li...>]

Hi everyone,

I finally implemented multiple subentry types per contact (eg. 3 work 
phones, 2 emails, etc). The only limitation is with URL and Note, as 
KDE's address book doesn't allow more than entry of these types. The code 
is ready and waiting in CVS, however, I do want to test it a bit more 
before I tag it as 0.3.0. If any of the usual adventurers want to have a 
go at it, please do, and let me know of any issues you find.

Dimitris

-- 
Klingon multitasking systems do not support "time-sharing". When a Klingon 
program wants to run, it challenges the scheduler in hand-to-hand combat 
and owns the machine.

Re: [Knokiisync-users] Bug?

[Dimitris S. <dim...@li...>]

On Friday 04 July 2003 12:21, Robert Maier wrote:

>
> Yes, the phone memory is totally empty, nothing in it. The error that I
> get is "Can't find a free slot on the phone. Doh: Invalid type of
> memory" And afterwards, when the application wants to refresh the
> contents of the phone book frame it says (correctly) that "The selected
> memory (Phone) is empty!" I also tried it with the other two types of
> memories (Phone+SIM and SIM) and I always get the first error message
> and the second is adapted to the type of memory that is selected.

Weird. This could be a gnokii problem, because the error message is given=20
to KnokiiSync from libgnokii. I will see if I can backup my phone and=20
erase it's memory.

>
> Now, if I create an entry on the phone, using the phone's interface,
> and then refresh the phonebook frame in the application by clicking
> "Read" I get an erroneous entry. Let me explain myself: I create an
> entry on the phone: name "A" and number: "1". When I click "Read" I get
> the Surname of the entry that WAS on the phone at that position (in
> this case, position 1) before erasing the memory. The number is ok. I
> also got such anomalies with respect to the Surname and Name when the
> memory was not empty, I just saw entries that had Surnames or Names
> belonging to old entries occupying the same position. After creating
> this entry I am able to transfer all entries from KAB to the phone
> without problems.

Wild guess:
The name "A" is not in a valid format. The previous name you had on the=20
phone in position 001 propably wasn't in a proper format either and you=20
propably double-clicked the entry and changed it to your likings.=20

So, KnokiiSync checks if there is a name "override" for entry 001 in the=20
configuration file, and found the previous one. It normally should=20
"understand" that the entry has changed, but I don't know why it didn't.

If I'm correct, open .knokiisyncrc. You should see a section:

[Entry_001_XXXXXXXXXXXX]

where XXXXXXXXXXXXXX is your phone's IMEI.
If there is an option "InPhone=3D", what is it?

>
> After that, if I erase the entry that I created manually (or any other
> entry on the phone) and I re-Read the contents of the memory I get an
> entry with "***" on the Position field, "Error in entry 1" on the
> Surname field and "The given location is empty" on the Name field.

This is expected behaviour. It simply says that entry 1 is empty. In=20
0.3.x, there will be an option to "hide" all these problematic entries=20
(those whose "position" is "***").

>
> Another matter is the fact that all entries transferred from the
> computer to the phone belong to the Family group, they should initially
> not belong to any group at all.

I know this too, I had problems getting the group type of entries. I will=20
speak about this with Pawel Kot, and see if we come up with anything.

>
> Yet another matter: I got two error messages about unhandled frames. I
> had two rather special phone numbers that encoded also the extension
> next to the number of the central and it seems that the application
> encounters the "/" in the numbers and chokes on them. Here is the
> listing from the errors: -----
> UNHANDLED FRAME RECEIVED
> request: 0x03 / 0x006e
> 00 01 00 0b 00 01 01 00 00 10 02 05 00 47 00 00 |              G
> 00 00 00 00 00 03 07 00 00 24 ff 1e 00 50 00 6f |          $=FF  P o
> 00 6c 00 69 00 74 00 69 00 65 00 5f 00 66 00 75 |  l i t i e _ f u
> 00 72 00 74 00 75 00 72 00 69 1e 00 00 08 ff 01 |  r t u r i    =FF
> 00 55 0b 00 00 2c ff 06 00 00 00 22 00 2b xx xx |  U   ,=FF    " + x
> xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx |  x x x x x x x x
> xx xx xx xx 00 2f 00 32 00 33 00 36 00 30       |  x x / 2 3 6 0
> reply: 0x03 / 0x000e
> 01 52 00 0c 00 01 0f 00 00 08 43 00 00 00       |  R        C
> Please read Docs/Bugs and send a bug report!
> -----

Please post this in the gnokii mailing list, it's a problem of libgnokii.

>
> BTW, you were right about the notification window, I just dismissed it
> in the beginning and cheked the "do not bother me again"-like checkbox,
> that's why I did not get those messages anymore even after
> reinstalling. Thanks!

No problem, like I said, it happens to me all the time :-)

>
> Cheers,
> Robert.
> PS. I am now using 0.2.3, so all the "bug-reports" are about this
> version, since I can not yet use the CVS version.

OK, thanks for the trouble :-)

Dimitris

=2D-=20
Backup not found: (A)bort (R)etry (P)anic?

Re: [Knokiisync-users] Bug?

[Robert M. <Rob...@es...>]

On Friday 04 July 2003 07:21, Dimitris Stasinopoulos wrote:
> On Friday 04 July 2003 00:56, Robert Maier wrote:
> > Hi again,
> >
> > Before I forget: if you try to transfer a contact information into an
> > empty phone address book, you will get an error. I could only transfer
> > data into an empty memory on the phone after I manually created an
> > entry using the phone's interface.
> >
> > Cheers,
> > Robert.
>
> Hi Robert,
>
> what exactly do you mean "an empty phone address book"? Empty as in
> _totally_ empty, no other contacts on the phone? What is the error
> message you get? I can't replicate it because I dare not empty my phone's
> address book :-)

Hi Dimitris,

Yes, the phone memory is totally empty, nothing in it. The error that I get is 
"Can't find a free slot on the phone. Doh: Invalid type of memory" And 
afterwards, when the application wants to refresh the contents of the phone 
book frame it says (correctly) that "The selected memory (Phone) is empty!"
I also tried it with the other two types of memories (Phone+SIM and SIM) and I 
always get the first error message and the second is adapted to the type of 
memory that is selected.

Now, if I create an entry on the phone, using the phone's interface, and then 
refresh the phonebook frame in the application by clicking "Read" I get an 
erroneous entry. Let me explain myself: I create an entry on the phone: name 
"A" and number: "1". When I click "Read" I get the Surname of the entry that 
WAS on the phone at that position (in this case, position 1) before erasing 
the memory. The number is ok. I also got such anomalies with respect to the 
Surname and Name when the memory was not empty, I just saw entries that had 
Surnames or Names belonging to old entries occupying the same position.
After creating this entry I am able to transfer all entries from KAB to the 
phone without problems.

After that, if I erase the entry that I created manually (or any other entry 
on the phone) and I re-Read the contents of the memory I get an entry with 
"***" on the Position field, "Error in entry 1" on the Surname field and "The 
given location is empty" on the Name field.

Another matter is the fact that all entries transferred from the computer to 
the phone belong to the Family group, they should initially not belong to any 
group at all.

Yet another matter: I got two error messages about unhandled frames. I had two 
rather special phone numbers that encoded also the extension next to the 
number of the central and it seems that the application encounters the "/" in 
the numbers and chokes on them. Here is the listing from the errors:
-----
UNHANDLED FRAME RECEIVED
request: 0x03 / 0x006e
00 01 00 0b 00 01 01 00 00 10 02 05 00 47 00 00 |              G
00 00 00 00 00 03 07 00 00 24 ff 1e 00 50 00 6f |          $ÿ  P o
00 6c 00 69 00 74 00 69 00 65 00 5f 00 66 00 75 |  l i t i e _ f u
00 72 00 74 00 75 00 72 00 69 1e 00 00 08 ff 01 |  r t u r i    ÿ
00 55 0b 00 00 2c ff 06 00 00 00 22 00 2b xx xx |  U   ,ÿ    " + x
xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx |  x x x x x x x x
xx xx xx xx 00 2f 00 32 00 33 00 36 00 30       |  x x / 2 3 6 0
reply: 0x03 / 0x000e
01 52 00 0c 00 01 0f 00 00 08 43 00 00 00       |  R        C
Please read Docs/Bugs and send a bug report!
-----

BTW, you were right about the notification window, I just dismissed it in the 
beginning and cheked the "do not bother me again"-like checkbox, that's why I 
did not get those messages anymore even after reinstalling. Thanks!

Cheers,
Robert.
PS. I am now using 0.2.3, so all the "bug-reports" are about this version, 
since I can not yet use the CVS version.

-- 
------------------------------------------------------------------------------
Robert Maier			
ESAT SCD/COSIC                     ______      _____ _____ ______
Kasteelpark Arenberg 10           / ____/___  / ___//_  _// ____/
3001 Heverlee                    / /   / __ \ \__ \  / / / /
BELGIUM                         / /___/ /_/ /___/ /_/ /_/ /___
Phone: +32-16-32.18.53          \____/\____//____//____/\____/
Fax:   +32-16-32.19.69	
------------------------------------------------------------------------------

Re: [Knokiisync-users] Bug?

[Dimitris S. <dim...@li...>]

On Friday 04 July 2003 00:56, Robert Maier wrote:
> Hi again,
>
> Before I forget: if you try to transfer a contact information into an
> empty phone address book, you will get an error. I could only transfer
> data into an empty memory on the phone after I manually created an
> entry using the phone's interface.
>
> Cheers,
> Robert.

Hi Robert,

what exactly do you mean "an empty phone address book"? Empty as in 
_totally_ empty, no other contacts on the phone? What is the error 
message you get? I can't replicate it because I dare not empty my phone's 
address book :-)

Dimitris

-- 
Sometimes, even the salamander burns.

[Knokiisync-users] Bug?

[Robert M. <Rob...@es...>]

Hi again,

Before I forget: if you try to transfer a contact information into an empty 
phone address book, you will get an error. I could only transfer data into an 
empty memory on the phone after I manually created an entry using the phone's 
interface.

Cheers,
Robert.
-- 
------------------------------------------------------------------------------
Robert Maier			
ESAT SCD/COSIC                     ______      _____ _____ ______
Kasteelpark Arenberg 10           / ____/___  / ___//_  _// ____/
3001 Heverlee                    / /   / __ \ \__ \  / / / /
BELGIUM                         / /___/ /_/ /___/ /_/ /_/ /___
Phone: +32-16-32.18.53          \____/\____//____//____/\____/
Fax:   +32-16-32.19.69	
------------------------------------------------------------------------------

Re: [Knokiisync-users] Crash trace and two other matters

[Dimitris S. <dim...@li...>]

On Thursday 03 July 2003 12:51, Robert Maier wrote:
> Hi Dimitris,
>
> Here is the crash trace from the CVS version. It crashed after reading all
> contacts from the phone addressbook. I wanted to go back to the CVS version
> since I need the functionality that you are implementing now (more phone
> numbers of the same type per contact).

Btw, the current CVS code only READS the entries from the phone, it cannot 
transfer the _extra_ phones to the address book yet, nor does it read 
multiple entries per phone type from the KAB! Do not try this, or there could 
be problems!

Dimitris

Re: [Knokiisync-users] Crash trace and two other matters

[Dimitris S. <dim...@li...>]

On Thursday 03 July 2003 12:51, Robert Maier wrote:
> Hi Dimitris,
>
> Here is the crash trace from the CVS version. It crashed after reading all
> contacts from the phone addressbook. I wanted to go back to the CVS version
> since I need the functionality that you are implementing now (more phone
> numbers of the same type per contact).
> ---
> [New Thread 16384 (LWP 12105)]
> 0x41008387 in waitpid () from /lib/libpthread.so.0
> #0  0x41008387 in waitpid () from /lib/libpthread.so.0
> #1  0x4072ac89 in KCrash::defaultCrashHandler(int) ()
>    from /opt/kde3/lib/libkdecore.so.4
> #2  0x410071ec in __pthread_sighandler () from /lib/libpthread.so.0
> #3  <signal handler called>
> #4  0x40043dc2 in KABC::Addressee::setUid(QString const&) ()
>    from /opt/kde3/lib/libkabc.so.1
> #5  0x0805ac33 in SyncView::readMobPhBook() ()

OK, I can see where the problem is, I will have a look at it.

>
> On another matter, the dialog box that we were talking about yesterday (the
> one that informs you to restart the application for the new preferences to
> take effect) is there in the code, but I do not see it displayed even if I
> change something in the preferences.

Go to the configuration file ($HOME/.kde/share/config/.knokiisyncrc), and 
where it says:

[Notification Messages]
ConfChangeRestart=...

First of all, is it set to true or false?
If false, then you've propably "silently" acknowledged it - it happens to me 
all the time :-)

>
> And yet on another matter, in 0.2.3 whenever I want to transfer an entry
> that has no phone numbers (only names and E-mail address, for instance),
> the application responds with Write failed: incorrect data format.

Will look into it, I think I know where the problem is.

>
> Any timelines on the release of the new functionality (more of the same
> phone number type per user)?
>
> Thanks!
> Robert.

If I get some time in the weekend, propably by then, else within the coming 
week.

Dimitris

[Knokiisync-users] Crash trace and two other matters

[Robert M. <Rob...@es...>]

Hi Dimitris,

Here is the crash trace from the CVS version. It crashed after reading all 
contacts from the phone addressbook. I wanted to go back to the CVS version 
since I need the functionality that you are implementing now (more phone 
numbers of the same type per contact).
---
[New Thread 16384 (LWP 12105)]
0x41008387 in waitpid () from /lib/libpthread.so.0
#0  0x41008387 in waitpid () from /lib/libpthread.so.0
#1  0x4072ac89 in KCrash::defaultCrashHandler(int) ()
   from /opt/kde3/lib/libkdecore.so.4
#2  0x410071ec in __pthread_sighandler () from /lib/libpthread.so.0
#3  <signal handler called>
#4  0x40043dc2 in KABC::Addressee::setUid(QString const&) ()
   from /opt/kde3/lib/libkabc.so.1
#5  0x0805ac33 in SyncView::readMobPhBook() ()
#6  0x08065834 in SyncView::qt_invoke(int, QUObject*) ()
#7  0x40b6c8e7 in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#8  0x40b6c78f in QObject::activate_signal(int) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#9  0x40e6a3ec in QButton::clicked() () from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0x40bf4716 in QButton::mouseReleaseEvent(QMouseEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0x40ba2954 in QWidget::event(QEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#12 0x40b0b5f8 in QApplication::internalNotify(QObject*, QEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0x40b0ad76 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0x406b7929 in KApplication::notify(QObject*, QEvent*) ()
   from /opt/kde3/lib/libkdecore.so.4
#15 0x40aac5c8 in QETWidget::translateMouseEvent(_XEvent const*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0x40aa9e30 in QApplication::x11ProcessEvent(_XEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0x40abf4f2 in QEventLoop::processEvents(unsigned) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0x40b1fb83 in QEventLoop::enterLoop() ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0x40b1fa76 in QEventLoop::exec() () from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x40b0b87f in QApplication::exec() () from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0x080654c9 in main ()
#22 0x41164857 in __libc_start_main () from /lib/libc.so.6
---

On another matter, the dialog box that we were talking about yesterday (the 
one that informs you to restart the application for the new preferences to 
take effect) is there in the code, but I do not see it displayed even if I 
change something in the preferences.

And yet on another matter, in 0.2.3 whenever I want to transfer an entry that 
has no phone numbers (only names and E-mail address, for instance), the 
application responds with Write failed: incorrect data format.

Any timelines on the release of the new functionality (more of the same phone 
number type per user)?

Thanks!
Robert.


-- 
------------------------------------------------------------------------------
Robert Maier			
ESAT SCD/COSIC                     ______      _____ _____ ______
Kasteelpark Arenberg 10           / ____/___  / ___//_  _// ____/
3001 Heverlee                    / /   / __ \ \__ \  / / / /
BELGIUM                         / /___/ /_/ /___/ /_/ /_/ /___
Phone: +32-16-32.18.53          \____/\____//____//____/\____/
Fax:   +32-16-32.19.69	
------------------------------------------------------------------------------

Re: [Knokiisync-users] Regarding the only "registered" bug of knokiisync

[Dimitris S. <dim...@li...>]

On Wednesday 02 July 2003 20:59, you wrote:
> Hi Dimitris,
>
> Thanks for the prompt reply.
>

You are welcome :-)

> >
> > Please copy/paste the crash trace when the crash dialog appears. Also, I
> > would recommend that you use version 0.2.3, as the current CVS version is
> > a leap from 0.2.x to 0.3. Currently, I'm in the middle of implementing
> > multiple same phone types (eg. 2 mobiles, 3 work, 2 emails) for a given
> > contact. This is still experimental, where 0.2.3 is known to work OK.
>
> Got it, I switched back to 0.2.3 and guess what? The problem is solved!
> Initially in 0.2.3 it used to crash as soon as I tried to read the phone
> addressbook, that's why I went on to the CVS version. That was helpfull
> because it was there that I found out about the encoding thing, but never
> tried it back in 0.2.3. I tried it now and it works (though not extensively
> tested yet).

Great :-)

> [ As another comment, I think you should include a dialog (or any kind of
> message) that warns the user about having to restart the application so
> that the preferences changes should take effect ]

It does actually! Have a look at line 163 of conf_dialog.ui.h. It also has a 
checkbox, so that you can disable it (so that it won't show up again in the 
future).

>
> > I haven't had this problem, no. Let's start with the crash first.
> > Also, please report your phone model, your connection type as well as how
> > many contacts you have on your phone.
>
> For the record, I am using a Nokia 6310i, connected via Bluetooth and I
> have around 126 contacts on the phone and around 15 on the SIM. I should
> also mention that the contacts are quite complex (one of the reasons why I
> want them sync'ed), namely one contact has several phone numbers (home,
> cellular, fax, work etc.).

That's ok, I have tested KnokiiSync with MANY phones per contact, including 
URL, email, postal addresses, etc., and it works pretty well ;-)

> >
> > Thanks Robert, I'll be more than happy to deliver. Now that I (finally)
> > got bluetooth working on my laptop (so far, it only worked on my
> > workstation at home), I'll propably be a bit more concentrated on the
> > project.
>
> Let me know if I can help you in any way (especially testing, although
> don't rule out programming :)). I really like this project and I think it
> has a future.
>
> Robert.

Again, thanks. I can use a dedicated tester or two, and definately someone to 
"push" (=motivate) me a bit when my mood gets lazy :-))

Dimitris

--
Q: What is the difference between a terrorist and an object methodologist?
A: You can negotiate with the terrorist.

Re: [Knokiisync-users] Regarding the only "registered" bug of knokiisync

[Robert M. <Rob...@es...>]

Hi Dimitris,

Thanks for the prompt reply.

On Wednesday 02 July 2003 22:30, Dimitris Stasinopoulos wrote:
> this is a tricky question, but the answer is rather surprising:
> "Experiment". In the CVS code, I switched from having Latin1 as the default
> encoding, to ISO8859-1, which is much less crash prone. If you are using
> your phone in Belgium (which means French names, etc), ISO8859-1 should be
> the right option.
Thanks, I'll do the experiment completely then and try all the possibilities. 
I am indeed using my phone in Belgium, but the phone was bought in Germany 
and I am not using any special characters (only latin characters).
>
> > Moreover, I tried reading the phone address book with different encoding
> > settings and for some (ISO 8859-1 for ex.) KnokiiSync displayed the
> > progress dialog, went from 0 to 100% (so it read all the addresses in the
> > address book) and only then crashed.
>
> Please copy/paste the crash trace when the crash dialog appears. Also, I
> would recommend that you use version 0.2.3, as the current CVS version is a
> leap from 0.2.x to 0.3. Currently, I'm in the middle of implementing
> multiple same phone types (eg. 2 mobiles, 3 work, 2 emails) for a given
> contact. This is still experimental, where 0.2.3 is known to work OK.
Got it, I switched back to 0.2.3 and guess what? The problem is solved! 
Initially in 0.2.3 it used to crash as soon as I tried to read the phone 
addressbook, that's why I went on to the CVS version. That was helpfull 
because it was there that I found out about the encoding thing, but never 
tried it back in 0.2.3. I tried it now and it works (though not extensively 
tested yet).
[ As another comment, I think you should include a dialog (or any kind of 
message) that warns the user about having to restart the application so that 
the preferences changes should take effect ]
> I haven't had this problem, no. Let's start with the crash first.
> Also, please report your phone model, your connection type as well as how
> many contacts you have on your phone.
For the record, I am using a Nokia 6310i, connected via Bluetooth and I have 
around 126 contacts on the phone and around 15 on the SIM. I should also 
mention that the contacts are quite complex (one of the reasons why I want 
them sync'ed), namely one contact has several phone numbers (home, cellular, 
fax, work etc.).
>
> > BTW, Dimitri, let me congratulate you on the initiation and the current
> > status of this project. When I'll have it working I think it will be very
> > nice and very useful to me. Keep up the good work!
>
> Thanks Robert, I'll be more than happy to deliver. Now that I (finally) got
> bluetooth working on my laptop (so far, it only worked on my workstation at
> home), I'll propably be a bit more concentrated on the project.
Let me know if I can help you in any way (especially testing, although don't 
rule out programming :)). I really like this project and I think it has a 
future.

Robert.

-- 
------------------------------------------------------------------------------
Robert Maier			
ESAT SCD/COSIC                     ______      _____ _____ ______
Kasteelpark Arenberg 10           / ____/___  / ___//_  _// ____/
3001 Heverlee                    / /   / __ \ \__ \  / / / /
BELGIUM                         / /___/ /_/ /___/ /_/ /_/ /___
Phone: +32-16-32.18.53          \____/\____//____//____/\____/
Fax:   +32-16-32.19.69	
------------------------------------------------------------------------------

Re: [Knokiisync-users] Regarding the only "registered" bug of knokiisync

[Dimitris S. <dim...@li...>]

On Wednesday 02 July 2003 14:46, Robert Maier wrote:
> Hi,
>
> I have some comments on the bug that makes knokiiSync crash when reading
> the phone address book. It is the only bug that is submitted on the
> project's sourceforge homepage. I have posted a small comment there as
> well.
>
> The workaround for this bug seems to be setting the phone encoding properly
> (this appears also in red letters on KnokiiSync's GUI the latest CVS
> version). Now my question: how do I know what encoding does my phone use?
> Is there a way to find this out?
>

Hello Robert,

this is a tricky question, but the answer is rather surprising: "Experiment".
In the CVS code, I switched from having Latin1 as the default encoding, to 
ISO8859-1, which is much less crash prone. If you are using your phone in 
Belgium (which means French names, etc), ISO8859-1 should be the right 
option. 

> Moreover, I tried reading the phone address book with different encoding
> settings and for some (ISO 8859-1 for ex.) KnokiiSync displayed the
> progress dialog, went from 0 to 100% (so it read all the addresses in the
> address book) and only then crashed.

Please copy/paste the crash trace when the crash dialog appears. Also, I would 
recommend that you use version 0.2.3, as the current CVS version is a leap 
from 0.2.x to 0.3. Currently, I'm in the middle of implementing multiple same 
phone types (eg. 2 mobiles, 3 work, 2 emails) for a given contact. This is 
still experimental, where 0.2.3 is known to work OK.

> With other encoding settings it eats
> up my resources and the only way to get out of it is reboot my computer
> (or, if fast enough, maybe kill KnokiiSync). Did anyone experience this
> behaviour too? Does anyone (Dimitri maybe?) have any solution to these
> problems?

I haven't had this problem, no. Let's start with the crash first.
Also, please report your phone model, your connection type as well as how many
contacts you have on your phone.

>
> BTW, Dimitri, let me congratulate you on the initiation and the current
> status of this project. When I'll have it working I think it will be very
> nice and very useful to me. Keep up the good work!
>
> Robert.

Thanks Robert, I'll be more than happy to deliver. Now that I (finally) got 
bluetooth working on my laptop (so far, it only worked on my workstation at 
home), I'll propably be a bit more concentrated on the project.

Dimitris

--
Our software does not have bugs. Only random features.

[Knokiisync-users] Regarding the only "registered" bug of knokiisync

[Robert M. <Rob...@es...>]

Hi,

I have some comments on the bug that makes knokiiSync crash when reading the 
phone address book. It is the only bug that is submitted on the project's 
sourceforge homepage. I have posted a small comment there as well.

The workaround for this bug seems to be setting the phone encoding properly 
(this appears also in red letters on KnokiiSync's GUI the latest CVS 
version). Now my question: how do I know what encoding does my phone use? Is 
there a way to find this out?

Moreover, I tried reading the phone address book with different encoding 
settings and for some (ISO 8859-1 for ex.) KnokiiSync displayed the progress 
dialog, went from 0 to 100% (so it read all the addresses in the address 
book) and only then crashed. With other encoding settings it eats up my 
resources and the only way to get out of it is reboot my computer (or, if 
fast enough, maybe kill KnokiiSync). Did anyone experience this behaviour 
too? Does anyone (Dimitri maybe?) have any solution to these problems?

BTW, Dimitri, let me congratulate you on the initiation and the current status 
of this project. When I'll have it working I think it will be very nice and 
very useful to me. Keep up the good work!

Robert.
-- 
------------------------------------------------------------------------------
Robert Maier			
ESAT SCD/COSIC                     ______      _____ _____ ______
Kasteelpark Arenberg 10           / ____/___  / ___//_  _// ____/
3001 Heverlee                    / /   / __ \ \__ \  / / / /
BELGIUM                         / /___/ /_/ /___/ /_/ /_/ /___
Phone: +32-16-32.18.53          \____/\____//____//____/\____/
Fax:   +32-16-32.19.69	
------------------------------------------------------------------------------

[Knokiisync-users] KnokiiSync 0.2.3

[Dimitris S. <dim...@li...>]

Hi everyone,

this is to announce the release of KnokiiSync V. 0.2.3. While not a major 
release, it does include some tweaks that will affect (help) those who are a 
bit more "sloppy" on their naming schemes. This release will give you a bit 
more control over the names. Specifically:

- Names that do not match the format given in the configuration dialog are 
flagged. You can choose if you want to be notified immediately (during the 
phonebook read) and still read the problematic entry or ignore the entry.

- Other "problematic" entries (like empty ones) are also flagged.

- In some cases, if the format didn't match, the transfer would end, but the 
transfer dialog would still remain there. Fixed.

- Minor code cleanup.

Downloads as usual at http://www.sf.net/projects/knokiisync

Download, compile, test and report problems :-)
Oh, and for those who like to walk on the bleeding edge:
KnokiiSync is in the CVS repository. If you want to download the latest 
release:

cvs -d:pserver:ano...@cv...:/cvsroot/knokiisync login
(Press enter for no password)
cvs -z3 -d:pserver:ano...@cv...:/cvsroot/knokiisync checkout 
KnokiiSync

And you (propably) have the latest stuff.  After that, issue:

cvs -z3 -d:pserver:ano...@cv...:/cvsroot/knokiisync update 
KnokiiSync

to keep your local copy updated, everytime you feel like it. Please note that 
SourceForge has a 24hr gap between the syncs of the developer and the end 
user (anonymous) CVS server, so you might be getting "last night's" stuff. 

Enjoy,
Dimitris

--
"The end of time is reached around the year 8000, by which time we expect Qt 
to be obsolete."

- QT Documention, qdate.html#details

[Knokiisync-users] KnokiiSync 0.2.2

[Dimitris S. <dim...@li...>]

Hi everyone, this is to announce the release of KnokiiSync 0.2.2

Changes:

* Seperate tarballs are no longer required to build with bluetooth 
support. Thanks to Pawel Kot for the hint. Note that this means that you 
will need pkg-config for this magic to work. See 
http://www.freedesktop.org.

* Better name handling. KnokiiSync can now distinguish between Surname 
("Family Name") and Name ("Given Name"), and will ask you what to do if 
something isn't right. You can then tweak these, right in the program, by 
double-clicking the surname and name in the Mobile (right hand side) 
panel.

* Progress dialogs when reading both the KAB, as well as the phone memory.

* Memory selection option. You can now choose "Phone", "SIM", "Phone+SIM".

* Bugfixes here and there. 

* Some minor stuff, like error reporting instead of silent drops, and 
more.

Download, test, report problems, and as usual, have fun!

Dimitris

-- 
Our network is object-oriented;
Everytime I change something, the users object.

[Knokiisync-users] Re: [Knokiisync-developers] KnokiiSync 0.2.3 around the corner

[Dimitris S. <dim...@li...>]

On Wednesday 11 June 2003 12:40, Pawel Kot wrote:
> On Wed, 11 Jun 2003, Stasinopoulos Dimitris wrote:
>
> Hi Dimitris,
>
> [I'm not sure to which list should I write, so feel free to truncate
> the Cc list. Also not setting reply-to policy at sf is imho quite
> annoying...]
>

Hello Pawel.
Yes, you are right. I'll fix this.

> As the side note. Did you think about integration with MultiSync?
> (http://multisync.sf.net/)
>

No, mainly because I'm a KDE person :)
But my final goal will be to offer full synchronization, including todo's, 
memo's, appointments, etc.

> As the other kind of functionality I'd like to see is the daemon
> watching the possible connections and enabling the 'Synchronize' window
> when any of the connections is available.
>

I understand what you want, but I can't see how this will be done (the 
detection of the phone) without writing a new deamon, specifically 
scanning serial and IR ports, as well as bluetooth channels. This can be 
a bit tricky, and at the moment is not in my priorities (stability, core 
functionality, compatibility, in that order)

> And a small bug report: when 'Name' field in the phone is just one
> word, knokiisync didn't save the entry correctly into the KDE
> addressbook: an extra space at the beginning and no number.
>

You are right. KnokiiSync should prompt the user with a question on what 
to do in that case. Also see the name format setting in the configuration 
dialog. The same applies for the postal address.

> And a hint. When creating Makefile you need to determine what flags you
> should use (ie. your special case for the bluetooth). Gnokii does
> provide pc file, which allows you to use:
>
> $ pkg-config --libs gnokii
> and
> $ pkg-config --cflags gnokii
>
> which should help in determining the correct compilation/linking flags.
>

Nice - thanks for the info. That should put an end to the distribution of 
two different tarballs, and the mess that brings. :-)

> pkot

Dimitris

-- 
Copywight 1994 Elmer Fudd. All wights wesewved.

[Knokiisync-users] Re: [Knokiisync-developers] KnokiiSync 0.2.3 around the corner

[Pawel K. <pk...@li...>]

On Wed, 11 Jun 2003, Stasinopoulos Dimitris wrote:

Hi Dimitris,

[I'm not sure to which list should I write, so feel free to truncate the
Cc list. Also not setting reply-to policy at sf is imho quite annoying...]

> Hi everyone. I will be releasing version 0.2.3 of KnokiiSync shortly (as
> early as within the day, as late as until Friday).
> So, this is an encouragment for everyone to post any ideas, bugs,
> contributions, etc. as soon as possible, so that I can
> have a look and possibly implement in this release, which I hope to be
> the last for the 0.2.x series. Roadmap for the
> next versions coming soon.

As the side note. Did you think about integration with MultiSync?
(http://multisync.sf.net/)

As the other kind of functionality I'd like to see is the daemon watching
the possible connections and enabling the 'Synchronize' window when any of
the connections is available.

And a small bug report: when 'Name' field in the phone is just one word,
knokiisync didn't save the entry correctly into the KDE addressbook: an
extra space at the beginning and no number.

And a hint. When creating Makefile you need to determine what flags you
should use (ie. your special case for the bluetooth). Gnokii does provide
pc file, which allows you to use:

$ pkg-config --libs gnokii
and
$ pkg-config --cflags gnokii

which should help in determining the correct compilation/linking flags.

pkot
-- 
mailto:pk...@li... :: mailto:pk...@sl...
http://kt.linuxnews.pl/ :: Kernel Traffic po polsku

[Knokiisync-users] KnokiiSync 0.2.3 around the corner

[Stasinopoulos D. <dim...@li...>]

Hi everyone. I will be releasing version 0.2.3 of KnokiiSync shortly (as
early as within the day, as late as until Friday).
So, this is an encouragment for everyone to post any ideas, bugs,
contributions, etc. as soon as possible, so that I can
have a look and possibly implement in this release, which I hope to be
the last for the 0.2.x series. Roadmap for the
next versions coming soon.
 
Dimitris
 
--
Mental Floss prevents Moral Decay

Re: [Knokiisync-users] French po file for knokii 0.2.1 ready

[Dimitris S. <dim...@li...>]

On Wednesday 04 June 2003 14:22, Olivier Kaloudoff wrote:
> Hi,
>
> 	I just translated knokii to French,
> who should I send the .po file to so that it will
> be included in next release ?
>
> Best Regards,
>
> Olivier Kaloudoff
> LUG Linux Azur

Hi Olivier, please send them to me. I will see to it that they get included. 
Thanks for all the trouble. :-)

Dimitris

--
"The end of time is reached around the year 8000, by which time we expect Qt 
to be obsolete."

- QT Documention, qdate.html#details

[Knokiisync-users] French po file for knokii 0.2.1 ready

[Olivier K. <ka...@ka...>]

Hi,

	I just translated knokii to French,
who should I send the .po file to so that it will
be included in next release ?


Best Regards,


Olivier Kaloudoff
LUG Linux Azur