pilot-db-list

Re: [pilot-db-list] editing on a PC

[Nathan K. <na...@ve...>]

> > > Should it? Is this a good way, considering no tool will follow closely
> > > enough the development of pilot-db? And, BTW, isn't something written in
> > > some higher-level language easier to write? E.g. things like
> > > datascript or DataWorkshop? I know this isn't pilot-db-related, but
> > > palm-db-tools seems dead to me.
> > 
> > We've had a bit of discussion this list about what needs to be done
> > about this, but no solution yet.  I wouldn't give up on the hope of
> 
> I will read the archives.

It was probably sometime in January, and it was only initial discussion.
I wasn't trying to imply that it should not be discussed further!

> > having a tool that would follow the development of pilot-db.  In fact,
> > I think that is just about the only hope.  
> 
> Generally speaking, I agree. But this wasn't my point. What I wanted to
> say is this: Even though there is currently no tool that knows about
> recent additions (global scripts, filters), there is still a way to
> edit the _data_ part without loosing all the metadata. Using only
> palm-db-tools, pdb2csv and csv2pdb, this isn't possible - on the first
> conversion you loose everything not supported by it. Using par, I keep
> all the metadata in binary form, as a single appinfo file, and edit the
> data with whatever I want.

Yes, certainly a tool that did not throw away all the information it
did not understand would be a useful improvement.  I must confess I
haven't actually tried using palm-db-tools in the last couple years. :(

> But when writing for a PC, we can use some higher level language. Either
> a general-purpose scripting language (such as perl or python),

Yes, definitely.  I think the best way to achieve this might be to
have a C language library that allows access to PDB files (ideally one
that actually shares most of its code with the Palm version), and then
write some interfaces to this from Perl, Python, etc.  But just doing
it directly in some other language would be fine too.

At this point, we could happily benefit from anything that works.

> is what I suggested, to use a tool that is specifically intended for such
> a thing - a tool in which you define your data in some language and can
> automatically edit or export/import it, without adding code in a lower
> level language.

Sadly, I fear what we really need is just a good definition of our
data format.  Currently, there does not seem to be one other than as
defined by the current C code.    

--nate

[pilot-db-list] a bug in recordview up/down arrows

[Yedidyah Bar-D. <di...@ta...>]

> > 7. There is a bug, that sometimes, when pressing the down-arrow or up-arrow
> > icons on the buttom-right, in the "record view" (is this the name?), it
> > crashes, requiring a soft reset. Pressing PgDn does work, so that's what
> > he does for now. I tried for some time to debug this with pose and gdb,
> > but did not really get anywhere. It says:
> > "DB (1.1.0) called SysFatalAlert with the message:
> > "leakdetect.c, Line:188, addr"."
> > and gives control to gdb, but I can't see too much - 'where' says
> > (gdb) where
> > #0  0x1001d8b2 in ErrDisplayFileLineMsg ()
> > #1  0x00091b88 in ?? ()
> > #2  0x0008955c in ?? ()
> > #3  0x0007b770 in ?? ()
> > #4  0x10066b08 in PrvSendEventToForm ()
> > #5  0x10069f2c in FrmDispatchEvent ()
> > #6  0x0006f670 in EventLoop () at main.c:201
> > #7  0x0006f8a6 in EditViewGetFieldHeight () at main.c:715
> > #8  0x0006f3e4 in CheckMinVersion () at crt0.c:69
> > which does not help much. I tried to also put a breakpoint in
> > leakdetect.c:188, but also didn't get much further. 
> 
> I fixed something similar in the CVS version (Danger! Don't go
> there!). 

Already done :-) but only on pose, it's not dangerous (except maybe
for my mental health?).

> If possible, it would be great to see if you can reproduce
> this bug with a stock binary release.  There are a number of

If you refer to db-1.2.0-alpha5.prc then it's mostly the same. It
crashes at the same point, but with a different message:

"DB (1.2.0m) called SysFatalAlert with the message:
"MemoryMgr.c, Line:4372, Non-word-aligned handle"."

> configuration oddities that might cause this (some codepaths seem not
> to have been used in years) and it that's causing this.
> 
> Submitting this as a bug would be good for record keeping:
>   http://sourceforge.net/tracker/?group_id=621&atid=100621

OK.

> 
> > How do I debug pilot-db? Is there some tutorial somewhere?
> 
> No, there is not much published information, but I'm eager and willing
> to help you figure it out, and if we do it on-list it will probably
> help people in the future.   
> 
> It looks like the problem you are hitting now is that pilot-db is a
> multi-segment application, and that the standard prc-tools kit
> (including m68k-palmos-gdb) does not really support multiple code
> segments.  But there are patches available to do so:
>   http://www.v-overbeek.nl/msectgdb/
> While it's possible to do the compile from scratch, it's a lengthy
> multi-step procedure.  I submitted Linux binaries to Ton, which should
> be now available on his site.  

I'll look there.
-- 
Didi

[pilot-db-list] speed of transferring

[Yedidyah Bar-D. <di...@ta...>]

> > 6. Not terribly important, but transferring it to/from the palm takes
> > quite a lot of time - around 45 seconds, for a 170KB file. For comparison,
> > db-iw.prc itself, which is larger, takes much less time (not sure, I think
> > around 13 seconds). Is this reasonable? Is it because of the many records?
> 
> I don't know, but that does sound odd.  I've done almost all my
> testing on Pose and I haven't run into this problem. 

It's very fast with pose, doing "Install DB". It's slow with the real
palm, and with pilot-xfer. I didn't look (yet?) and pose's emulation
of hotsync, to see if it's the same.
-- 
Didi

[pilot-db-list] editing on a PC

[Yedidyah Bar-D. <di...@ta...>]

> > 5. I spent some time on editing the DB on a PC. I mostly want to do this
> > on linux, so dbeditor isn't my first choice. I tried to hack palm-db-tools
> > into exporting and importing filters (and eventually hoped for all other
> > data), but after spending on this around 10 hours, not getting it working
> > and deciding it's too hard to debug, I decided to quit. Instead, I searched
> > and found a small tool called par (7th google hit searching for 'par'),
> > which lets you extract the appinfo to a file, each record to a file, and
> > create a pdb from such files. So I intend to write a script that will
> > do this:
> > export and keep the appinfo
> > pdb2csv to file.csv
> > edit the file.csv (with openoffice, or maybe mysql+some web UI?)
> > csv2pdb
> > export all the records from the new pdb
> > create a pdb from the records and the saved appinfo
> > 
> > I verified that this theoretically works, but did not make thorough tests.
> > Should it? Is this a good way, considering no tool will follow closely
> > enough the development of pilot-db? And, BTW, isn't something written in
> > some higher-level language easier to write? E.g. things like
> > datascript or DataWorkshop? I know this isn't pilot-db-related, but
> > palm-db-tools seems dead to me.
> 
> We've had a bit of discussion this list about what needs to be done
> about this, but no solution yet.  I wouldn't give up on the hope of

I will read the archives.

> having a tool that would follow the development of pilot-db.  In fact,
> I think that is just about the only hope.  

Generally speaking, I agree. But this wasn't my point. What I wanted to
say is this: Even though there is currently no tool that knows about
recent additions (global scripts, filters), there is still a way to
edit the _data_ part without loosing all the metadata. Using only
palm-db-tools, pdb2csv and csv2pdb, this isn't possible - on the first
conversion you loose everything not supported by it. Using par, I keep
all the metadata in binary form, as a single appinfo file, and edit the
data with whatever I want.

Now, even without reading the archives (and hoping this doesn't sound
too rude): Suppose I agree there is a need for a tool that will fully
support all the metadata. When writing for palmos, it's pretty clear
why you (we?) write in C - we want it as fast and small as possible.
But when writing for a PC, we can use some higher level language. Either
a general-purpose scripting language (such as perl or python), or, which
is what I suggested, to use a tool that is specifically intended for such
a thing - a tool in which you define your data in some language and can
automatically edit or export/import it, without adding code in a lower
level language. The two examples I gave are datascript and DataWorkshop.
I have no experience with neither, I only found them now, but they do
look to me like the Right Thing (even if the implementation isn't, yet?).

What do you think?
-- 
Didi

[pilot-db-list] record plugins in listview

[Yedidyah Bar-D. <di...@ta...>]

> > 4. Since it's too slow for daily work, he uses the memoexport plugin
> > for the daily tasks, and uses that, using pilot-db only for longer-term
> > planning. Is there an easy way to export at once all the records displayed
> > by a specific view/filter? I guess no. It sounds to me as something that's
> > generally-useful - to make all the one-record plugins also available from
> > the listview, making them operate on all the records. Does this make sense?
> > Or is the right thing writing another plugin that will be specific to this
> > (which he will probably need anyway, since he wants it to set also the
> > category etc.)?
> 
> I'd guess it is not possible either, but yes, it does sound useful.

I don't have anything to add, just adding a separate note. I might look
into this sometime.
-- 
Didi

[pilot-db-list] Searching Hebrew

[Yedidyah Bar-D. <di...@ta...>]

> 
> > 3. Searching for Hebrew phrases is a bit weird. When using one kit of
> > Hebrew support, the one he got with the palm (HarelHeb 3.5, IIRC), it
> > only finds things if they are at the end of a field. When using another
> > support kit (a 2-week temporary license from www.kalanit.co.il for
> > what seems like a newer version of the same HarelHeb, but not sure),
> > it works just fine. Is this reasonable? Is there anything pilot-db can
> > do about it, or is this only the foreign-language support's job? I
> > did grep the source and found it's MatchString, which calls
> > *Glue* functions. Are these part of the foreign-lang support?
> 
> I don't know---I haven't dealt much with the foreign language support,
> and not at all with the non-latin-alphabet languages.  Submitting it
> as a bug report would be useful to create a permanent record, but my
> offhand guess is that if we are calling the *Glue* functions
> correctly, there is not much else to be done on the pilot-db end.
> But it is certainly worth checking if we are calling them correctly...
> 

For now I only _read_ the relevant code, and it seemed ok to me, how
much this worth isn't clear. The fact that it does work with one kit
(the newer) suggests that it is indeed a bug in the older kit, not
pilot-db. I hoped there is someone on the list who does have some
experience with this, who would be able to tell if this analysis is
reasonable (in which case, the only thing left to do is to purchase
the newer version. BTW - do other languages support kits cost money,
in other countries? It's not cheap either - around $30-$40, for a
machine that cost him $150).
-- 
Didi

[pilot-db-list] large DB support

[Yedidyah Bar-D. <di...@ta...>]

> > 2. The "large DB support" didn't work very well for him, so for now
> > I disabled it (compiled with '--with-vldb=0'). IIRC, it also wasn't
> > that much faster - and it _is_ an issue for him, having a 1000+
> > records DB with around 20 fields (still to change, but num of records
> > will not get smaller - it's his todo list). How experimental is this?
> > Is it going to become stable soon? Should I help debug this? Can I?
> 
> You compiled it!  Congratulations!  As best as I can tell, there are
> very few people on this list who have done so.  Be warned that many of
> the code paths seem to be unused in recent years, and that by
> including (or omitting) configuration flags you might soon find
> yourself in uncharted waters.

(repeating myself:)
I did
./configure --enable-standard --enable-debug --enable-sony=no --enable-handera=no --enable-fiveways=no --enable-make_plugins
With and without --with-vldb=0. Well, not the CVS one - only 1.1.0.
CVS I compiled only without it (that is, _with_ vldb support).
It wasn't that hard. Where is the catch?

> 
> Yes, it is probably going to become stable in the next release by
> simple method of removing all reference to the word "experimental".
> As far as I know (based on my recollection of submitted bug reports)
> it does not seem to add additional bugs.  I don't know about it's
> performance, but I think it purpose was simply to allow very large
> databases, not to necessarily make them work faster. (?)

Well, the 'configure --help' says:
"optimize for very large databases, and set the size of such a database".
Can you tell me what you think is the maximum of pilot-db without
this support, if it's not only optimization? It does work on a 1000+
record DB.

I did not yet try to reproduce the bug on the cvs - on 1.1.0 it sometimes
did not refresh the screen on Up/Down arrows. Since The User (my brother-
in-law) uses it daily, and is not friendly with computers, I chose for
him the slower but safer version. But it _is_ an issue.

> 
> Yes, you should help debug this! :) Submitting the slowness as a bug
> report to the SourceForge website, and then giving a sample database
> with some sample times would be good too.  I haven't yet tried much

I'll try to prepare something.
Maybe there is simply nothing to do? It is indeed a slow machine, and
a complex program. Are there profiling tools for this? prc does not
have gprof.

> profiling under POSE, but it does appear to be possible.  I'd guess
> (without having looked closely at the code) that there is lots of room
> for simple optimization.  If you can do it, wonderful, otherwise (like
> everything else) I'll try to get to it once we have a stable release.

OK.
-- 
Didi

[pilot-db-list] Hebrew support

[Yedidyah Bar-D. <di...@ta...>]

Sorry for the last message - I accidentally hit 'send' before changing
the subject ...

OK, I will make it a separate message for each issue.
I also subscribed to the list. Still, there are a few things I won't
repeat in each message: I use Debian sid, with the following versions:
prc-tools 2.2.90.cvs20030306-4 (has gcc 2.95.3, gdb 5.3)
pose 3.5-6 (the first version working for me - for a few months I
was pretty sure I'll have to use the simulator on Windows, which isn't
as simple for me) with the ROM of a Palm m130 (PalmOS 4.1)
palmos sdk 5r3

I tried and worked with pilot-db 1.1.0, 1.2.0 alpha 5 (the compiled
prc from sf.net), and the CVS version of today. Earlier versions needed
minor tweaks to compile against sdk-5r3, the CVS compiled cleanly.

I used the following to compile:
./configure --enable-standard --enable-debug --enable-sony=no --enable-handera=no --enable-fiveways=no --enable-make_plugins
without '--enable-sony=no --enable-handera=no --enable-fiveways=no', I
had some compilation problems, I guess because you need a different sdk
for this, didn't check.
As I said, in some cases I added '--with-vldb=0', more about that in
a different message.

On Mon, Apr 26, 2004 at 09:26:47AM -0600, Nathan Kurz wrote:
> Hello --
> 
> Thanks for your interest and time spent!
> 
> > 1. I translated the UI to Hebrew. You can get the file at
> > <http://www.cs.tau.ac.il/~didi/iw.rcp> (I did not know if it's
> > considered polite sending here attachments, so I put it there).
> > I did not translate everything, mostly the commonly-used things as
> > well as the ones easy to translate :-). If there is interest I do not
> > mind spending a few more hours on polishing this, but I think it's
> > already good enough for inclusion in a next version.
> 
> I'm probably the person who would include this, but I'm a new
> maintainer for this and I haven't yet dealt with adding languages.
> But if you can leave it up for a while (currently unspecified) I'll
> add it as a language once we get a release candidate mostly working.

Well, it's pretty simple, and documented in docs/translating.txt. I had
to add the file to rcp/langs/, and add the line 'include(iw.rcp)' to
rcp/db.rcp (or rather, to db.rcp.in, before running configure). Then,
'make db-iw.rcp' worked. No need to change the Makefile, as written there.
It's probably possible to even make the change to db.rcp automatic too,
but I didn't look at this.

But I do not mind that you'll wait with this - as I said, the translation
does need some more work, and I did not even start with the help file.
-- 
Didi

Re: [pilot-db-list] few things

[Yedidyah Bar-D. <di...@ta...>]

OK, I will make it a separate message for each issue.
I also subscribed to the list. Still, there are a few things I won't
repeat in each message: I use Debian sid, with the following versions:
prc-tools 2.2.90.cvs20030306-4 (has gcc 2.95.3, gdb 5.3)
pose 3.5-6 (the first version working for me - for a few months I
was pretty sure I'll have to use the simulator on Windows, which isn't
as simple for me) with the ROM of a Palm m130 (PalmOS 4.1)
palmos sdk 5r3

I tried and worked with pilot-db 1.1.0, 1.2.0 alpha 5 (the compiled
prc from sf.net), and the CVS version of today. Earlier versions needed
minor tweaks to compile against sdk-5r3, the CVS compiled cleanly.

I used the following to compile:
./configure --enable-standard --enable-debug --enable-sony=no --enable-handera=no --enable-fiveways=no --enable-make_plugins
without '--enable-sony=no --enable-handera=no --enable-fiveways=no', I
had some compilation problems, I guess because you need a different sdk
for this, didn't check.
As I said, in some cases I added '--with-vldb=0', more about that in
a different message.

On Mon, Apr 26, 2004 at 09:26:47AM -0600, Nathan Kurz wrote:
> Hello --
> 
> Thanks for your interest and time spent!
> 
> > 1. I translated the UI to Hebrew. You can get the file at
> > <http://www.cs.tau.ac.il/~didi/iw.rcp> (I did not know if it's
> > considered polite sending here attachments, so I put it there).
> > I did not translate everything, mostly the commonly-used things as
> > well as the ones easy to translate :-). If there is interest I do not
> > mind spending a few more hours on polishing this, but I think it's
> > already good enough for inclusion in a next version.
> 
> I'm probably the person who would include this, but I'm a new
> maintainer for this and I haven't yet dealt with adding languages.
> But if you can leave it up for a while (currently unspecified) I'll
> add it as a language once we get a release candidate mostly working.

Well, it's pretty simple, and documented in docs/translating.txt. I had
to add the file to rcp/langs/, and add the line 'include(iw.rcp)' to
rcp/db.rcp (or rather, to db.rcp.in, before running configure). Then,
'make db-iw.rcp' worked. No need to change the Makefile, as written there.
It's probably possible to even make the change to db.rcp automatic too,
but I didn't look at this.

But I do not mind that you'll wait with this - as I said, the translation
does need some more work, and I did not even start with the help file.
-- 
Didi

Re: [pilot-db-list] few things

[Nathan K. <na...@ve...>]

Hello --

Thanks for your interest and time spent!

> 1. I translated the UI to Hebrew. You can get the file at
> <http://www.cs.tau.ac.il/~didi/iw.rcp> (I did not know if it's
> considered polite sending here attachments, so I put it there).
> I did not translate everything, mostly the commonly-used things as
> well as the ones easy to translate :-). If there is interest I do not
> mind spending a few more hours on polishing this, but I think it's
> already good enough for inclusion in a next version.

I'm probably the person who would include this, but I'm a new
maintainer for this and I haven't yet dealt with adding languages.
But if you can leave it up for a while (currently unspecified) I'll
add it as a language once we get a release candidate mostly working.

> 2. The "large DB support" didn't work very well for him, so for now
> I disabled it (compiled with '--with-vldb=0'). IIRC, it also wasn't
> that much faster - and it _is_ an issue for him, having a 1000+
> records DB with around 20 fields (still to change, but num of records
> will not get smaller - it's his todo list). How experimental is this?
> Is it going to become stable soon? Should I help debug this? Can I?

You compiled it!  Congratulations!  As best as I can tell, there are
very few people on this list who have done so.  Be warned that many of
the code paths seem to be unused in recent years, and that by
including (or omitting) configuration flags you might soon find
yourself in uncharted waters.

Yes, it is probably going to become stable in the next release by
simple method of removing all reference to the word "experimental".
As far as I know (based on my recollection of submitted bug reports)
it does not seem to add additional bugs.  I don't know about it's
performance, but I think it purpose was simply to allow very large
databases, not to necessarily make them work faster. (?)

Yes, you should help debug this! :) Submitting the slowness as a bug
report to the SourceForge website, and then giving a sample database
with some sample times would be good too.  I haven't yet tried much
profiling under POSE, but it does appear to be possible.  I'd guess
(without having looked closely at the code) that there is lots of room
for simple optimization.  If you can do it, wonderful, otherwise (like
everything else) I'll try to get to it once we have a stable release.

> 3. Searching for Hebrew phrases is a bit weird. When using one kit of
> Hebrew support, the one he got with the palm (HarelHeb 3.5, IIRC), it
> only finds things if they are at the end of a field. When using another
> support kit (a 2-week temporary license from www.kalanit.co.il for
> what seems like a newer version of the same HarelHeb, but not sure),
> it works just fine. Is this reasonable? Is there anything pilot-db can
> do about it, or is this only the foreign-language support's job? I
> did grep the source and found it's MatchString, which calls
> *Glue* functions. Are these part of the foreign-lang support?

I don't know---I haven't dealt much with the foreign language support,
and not at all with the non-latin-alphabet languages.  Submitting it
as a bug report would be useful to create a permanent record, but my
offhand guess is that if we are calling the *Glue* functions
correctly, there is not much else to be done on the pilot-db end.
But it is certainly worth checking if we are calling them correctly...

> 4. Since it's too slow for daily work, he uses the memoexport plugin
> for the daily tasks, and uses that, using pilot-db only for longer-term
> planning. Is there an easy way to export at once all the records displayed
> by a specific view/filter? I guess no. It sounds to me as something that's
> generally-useful - to make all the one-record plugins also available from
> the listview, making them operate on all the records. Does this make sense?
> Or is the right thing writing another plugin that will be specific to this
> (which he will probably need anyway, since he wants it to set also the
> category etc.)?

I'd guess it is not possible either, but yes, it does sound useful.

> 5. I spent some time on editing the DB on a PC. I mostly want to do this
> on linux, so dbeditor isn't my first choice. I tried to hack palm-db-tools
> into exporting and importing filters (and eventually hoped for all other
> data), but after spending on this around 10 hours, not getting it working
> and deciding it's too hard to debug, I decided to quit. Instead, I searched
> and found a small tool called par (7th google hit searching for 'par'),
> which lets you extract the appinfo to a file, each record to a file, and
> create a pdb from such files. So I intend to write a script that will
> do this:
> export and keep the appinfo
> pdb2csv to file.csv
> edit the file.csv (with openoffice, or maybe mysql+some web UI?)
> csv2pdb
> export all the records from the new pdb
> create a pdb from the records and the saved appinfo
> 
> I verified that this theoretically works, but did not make thorough tests.
> Should it? Is this a good way, considering no tool will follow closely
> enough the development of pilot-db? And, BTW, isn't something written in
> some higher-level language easier to write? E.g. things like
> datascript or DataWorkshop? I know this isn't pilot-db-related, but
> palm-db-tools seems dead to me.

We've had a bit of discussion this list about what needs to be done
about this, but no solution yet.  I wouldn't give up on the hope of
having a tool that would follow the development of pilot-db.  In fact,
I think that is just about the only hope.  

> 6. Not terribly important, but transferring it to/from the palm takes
> quite a lot of time - around 45 seconds, for a 170KB file. For comparison,
> db-iw.prc itself, which is larger, takes much less time (not sure, I think
> around 13 seconds). Is this reasonable? Is it because of the many records?

I don't know, but that does sound odd.  I've done almost all my
testing on Pose and I haven't run into this problem. 

> 7. There is a bug, that sometimes, when pressing the down-arrow or up-arrow
> icons on the buttom-right, in the "record view" (is this the name?), it
> crashes, requiring a soft reset. Pressing PgDn does work, so that's what
> he does for now. I tried for some time to debug this with pose and gdb,
> but did not really get anywhere. It says:
> "DB (1.1.0) called SysFatalAlert with the message:
> "leakdetect.c, Line:188, addr"."
> and gives control to gdb, but I can't see too much - 'where' says
> (gdb) where
> #0  0x1001d8b2 in ErrDisplayFileLineMsg ()
> #1  0x00091b88 in ?? ()
> #2  0x0008955c in ?? ()
> #3  0x0007b770 in ?? ()
> #4  0x10066b08 in PrvSendEventToForm ()
> #5  0x10069f2c in FrmDispatchEvent ()
> #6  0x0006f670 in EventLoop () at main.c:201
> #7  0x0006f8a6 in EditViewGetFieldHeight () at main.c:715
> #8  0x0006f3e4 in CheckMinVersion () at crt0.c:69
> which does not help much. I tried to also put a breakpoint in
> leakdetect.c:188, but also didn't get much further. 

I fixed something similar in the CVS version (Danger! Don't go
there!).  If possible, it would be great to see if you can reproduce
this bug with a stock binary release.  There are a number of
configuration oddities that might cause this (some codepaths seem not
to have been used in years) and it that's causing this.

Submitting this as a bug would be good for record keeping:
  http://sourceforge.net/tracker/?group_id=621&atid=100621

> How do I debug pilot-db? Is there some tutorial somewhere?

No, there is not much published information, but I'm eager and willing
to help you figure it out, and if we do it on-list it will probably
help people in the future.   

It looks like the problem you are hitting now is that pilot-db is a
multi-segment application, and that the standard prc-tools kit
(including m68k-palmos-gdb) does not really support multiple code
segments.  But there are patches available to do so:
  http://www.v-overbeek.nl/msectgdb/
While it's possible to do the compile from scratch, it's a lengthy
multi-step procedure.  I submitted Linux binaries to Ton, which should
be now available on his site.  

> I hope this isn't too long! 

On-topic length is no problem.

> If you want further discussion to be in single-issue-threads, fine
> with me.

Probably better.  Let's put the followup posts into separate threads.

> If I am supposed to subscribe before sending, fine - but I can't
> promise I will spend much time on "real" work.

Subscribing would be useful, as otherwise I have to manually approve
each post you make.  

> Thanks a lot anyway,

And thank you!


Nathan Kurz
na...@ve...

[pilot-db-list] few things

[Yedidyah Bar-D. <di...@ta...>]

Hello all,

First I'd like to say thanks to everyone working on pilot-db. I think
it's a great piece of software.

I installed it on my brother-in-law's m103, as well as on pose on linux
with his rom. It mostly works well. I do have a few issues/questions.
I did not search the archives before sending this, only skimmed through
the first 20 messages (two months) to get the feeling of the list, so
feel free to ignore already-discussed issues.

1. I translated the UI to Hebrew. You can get the file at
<http://www.cs.tau.ac.il/~didi/iw.rcp> (I did not know if it's
considered polite sending here attachments, so I put it there).
I did not translate everything, mostly the commonly-used things as
well as the ones easy to translate :-). If there is interest I do not
mind spending a few more hours on polishing this, but I think it's
already good enough for inclusion in a next version.

2. The "large DB support" didn't work very well for him, so for now
I disabled it (compiled with '--with-vldb=0'). IIRC, it also wasn't
that much faster - and it _is_ an issue for him, having a 1000+
records DB with around 20 fields (still to change, but num of records
will not get smaller - it's his todo list). How experimental is this?
Is it going to become stable soon? Should I help debug this? Can I?

3. Searching for Hebrew phrases is a bit weird. When using one kit of
Hebrew support, the one he got with the palm (HarelHeb 3.5, IIRC), it
only finds things if they are at the end of a field. When using another
support kit (a 2-week temporary license from www.kalanit.co.il for
what seems like a newer version of the same HarelHeb, but not sure),
it works just fine. Is this reasonable? Is there anything pilot-db can
do about it, or is this only the foreign-language support's job? I
did grep the source and found it's MatchString, which calls
*Glue* functions. Are these part of the foreign-lang support?

4. Since it's too slow for daily work, he uses the memoexport plugin
for the daily tasks, and uses that, using pilot-db only for longer-term
planning. Is there an easy way to export at once all the records displayed
by a specific view/filter? I guess no. It sounds to me as something that's
generally-useful - to make all the one-record plugins also available from
the listview, making them operate on all the records. Does this make sense?
Or is the right thing writing another plugin that will be specific to this
(which he will probably need anyway, since he wants it to set also the
category etc.)?

5. I spent some time on editing the DB on a PC. I mostly want to do this
on linux, so dbeditor isn't my first choice. I tried to hack palm-db-tools
into exporting and importing filters (and eventually hoped for all other
data), but after spending on this around 10 hours, not getting it working
and deciding it's too hard to debug, I decided to quit. Instead, I searched
and found a small tool called par (7th google hit searching for 'par'),
which lets you extract the appinfo to a file, each record to a file, and
create a pdb from such files. So I intend to write a script that will
do this:
export and keep the appinfo
pdb2csv to file.csv
edit the file.csv (with openoffice, or maybe mysql+some web UI?)
csv2pdb
export all the records from the new pdb
create a pdb from the records and the saved appinfo

I verified that this theoretically works, but did not make thorough tests.
Should it? Is this a good way, considering no tool will follow closely
enough the development of pilot-db? And, BTW, isn't something written in
some higher-level language easier to write? E.g. things like
datascript or DataWorkshop? I know this isn't pilot-db-related, but
palm-db-tools seems dead to me.

6. Not terribly important, but transferring it to/from the palm takes
quite a lot of time - around 45 seconds, for a 170KB file. For comparison,
db-iw.prc itself, which is larger, takes much less time (not sure, I think
around 13 seconds). Is this reasonable? Is it because of the many records?

7. There is a bug, that sometimes, when pressing the down-arrow or up-arrow
icons on the buttom-right, in the "record view" (is this the name?), it
crashes, requiring a soft reset. Pressing PgDn does work, so that's what
he does for now. I tried for some time to debug this with pose and gdb,
but did not really get anywhere. It says:
"DB (1.1.0) called SysFatalAlert with the message:
"leakdetect.c, Line:188, addr"."
and gives control to gdb, but I can't see too much - 'where' says
(gdb) where
#0  0x1001d8b2 in ErrDisplayFileLineMsg ()
#1  0x00091b88 in ?? ()
#2  0x0008955c in ?? ()
#3  0x0007b770 in ?? ()
#4  0x10066b08 in PrvSendEventToForm ()
#5  0x10069f2c in FrmDispatchEvent ()
#6  0x0006f670 in EventLoop () at main.c:201
#7  0x0006f8a6 in EditViewGetFieldHeight () at main.c:715
#8  0x0006f3e4 in CheckMinVersion () at crt0.c:69
which does not help much. I tried to also put a breakpoint in
leakdetect.c:188, but also didn't get much further. How do I debug
pilot-db? Is there some tutorial somewhere?

I hope this isn't too long! If you want further discussion to be in
single-issue-threads, fine with me. If I am supposed to subscribe before
sending, fine - but I can't promise I will spend much time on "real"
work.

Thanks a lot anyway,
-- 
Didi

[pilot-db-list] large database

[Les N. <le...@th...>]

I am using pilot-db 1.1 with a large database and it works great, but =
how can I get rid of the=20
message "Experimental Very Large Database Support"

Thanks
-------------------------------
Praise the Lord!
Les Neely  <((((<
www.theneelys.info
www.bmoz.org
Phone 260 1 284886
For my Father's will is that everyone who looks to the Son and believes =
in him shall have eternal life, and I will raise him up at the last =
day."

P.O. Box 50599, RW Lusaka Zambia
----------------------------------------------------------------

[pilot-db-list] Problem with Boolean fields and filter.

[Ship M <sh...@ho...>]

Hi

Thanks for a great program, and for making I free, I deeply appreciate it.

And now the question I have. I have some “problems” working with Boolean 
fields and filter.

Background - I have made at Pilot-DB over Hugo and Nebula award winners, 
here I use Boolean fields to mark if the book have won the Hugo award, the 
Nebula award and if I have the book.

If I want to find the books I don’t have, and use the icon (Finds String) - 
entering 0 at the string and chose “Have the Book” Field in Search, it works 
fine, I get a list of the books I don’t have.

When I make a filter to do the same, using the following script (and %7 0) 
it returns an empty list why???? What am I missing her???.

If I change the script to (and %7 1) it works fine, it returns a list of the 
books I have.

I have found out that using the script (! %7 1) works? This returns a list 
of the books I don’t have. What value dose a Boolean field have when it is 
off.

Here is some Systeminfo if you need it:

Pilot-DB version 1.1.0 (14 Nov 2003)
Running on a Palm Vx
With Palm OS 3.5.3
And 6392K Free Memory

Fields in the database:
Author, last name (string)
Author, first name (string)
Title (string)
Publishing year (Integer)
# Book in series (Integer)
Hugo winner (Boolean)
Nebula winner (Boolean)
Have the book (Boolean)

Once again thanks for great program.

In advance thank you and Have a nice day :-)

Ship Moller
Copenhagen, Denmark

_________________________________________________________________
Få alle de nye og sjove ikoner på Ilovemessenger 
http://ilovemessenger.msn.com

Re: [pilot-db-list] Re:New db version 1.1

[marc\.chalain\@laposte\.net <mar...@la...>]

I never used CVS on sourceforge (my modem and my wallet didn't
accept to=
 use it) then it's normal that you didn't find a good
version. I'm knowi=
ng that Scott used it more, but that all. I
don't know the current versi=
on on CVS.

The last source code is the source code that every body can=

download from the website. On my computer i have another
version which=
 contains some corrections (i forget which ones),
but i didn't change a =
lot things.

But i want to keep your attention that the users are very=0D
=
strict on the stability of the software. You HAVE to be the
more careful=
l on the version that you release.

An other thing that i will inform y=
ou, it's the distribution.
You must survey which files that you distribu=
te and test each
one (the applications first: main application + the plu=
gins),
but the text files too ( the help files should contain the
good =
informations...).

For the end, i will tell you that to develop pilot-d=
b is one
thing and it's the less difficult, after you must:
 - make the=
 distribution.
 - inform the web world (palmgear, handango, other palm w=
ebsite).
 - coordinate the work of the others peoples, when you receive=0D
=
a translation file, you must build the overlay, when you
receive a patch=
, you must test it, when a beta-tester send a
bug trace, you must look f=
or the correction.
 - answer to the questions and the features requests.=

At the end you will spend a lot of time on your mailbox.

I don't wan=
t to afraid you, but there is just a lot of work
for one people and to f=
ind motivated peoples, it's not easy,
and to keep them, it's more diffic=
ult.

I will release a last 1.1.1 version, but you can begin with
the =
current version. There will not be a lot of modifications.

Salut,
Mar=
c.

> On Mon, Apr 19, 2004 at 02:09:26PM +0200, marc.chalain wrote:
> =
> I will try to release a last pilot-db 1.1 version soon, with
> > some =
corrections. After that i will stop pilot-db development
> > totally.=0D
=
> 
> Hello Marc ---
> 
> You mentioned a while ago that you had a more=
 current
version on your
> hard drive somewhere that you would send to =
me if you found
it.  If
> you could, that would be great.  If you want =
to go further
and release
> one last version, that would be even better=
.
> 
> I'm very frustrated with the version that was left in CVS. 
It =
has
> lots of bugs and problems with it, some obvious and some
only bei=
ng
> found as I fix the obvious layer.  I'm considering giving up
on th=
e
> CVS version, making it an experimental branch, and rolling
back to =
the
> last available 1.1 code, which appears to be in much better
shape=
.
> 
> I got started with this project because I thought it would
be u=
seful
> to me if it had better linked field support, but as it is
I've =
spent
> all my time just trying to get the thing to work as well as the=0D
=
> previous release.  If you have better or more current 1.1
code, I'd=0D
=
> certainly rather start with it than with that available on
the web
> =
site.  So if you have a better version, I'd love to have
access to it!=0D
=
> 
> Thanks!
> 
> Nathan Kurz
> na...@ve...
> 
> 
> -----------=
--------------------------------------------
> This SF.Net email is spon=
sored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel =
Robbins, President
and CEO of
> GenToo technologies. Learn everything f=
rom fundamentals to
system
>
administration.http://ads.osdn.com/?ad_id=
=3D1470&alloc_id=3D3638&op=3Dclick
> ___________________________________=
____________
> Pilot-db-list mailing list
> Pil...@li...urcef=
orge.net
> https://lists.sourceforge.net/lists/listinfo/pilot-db-list=0D
=
> =0A=0AAcc=E9dez au courrier =E9lectronique de La Poste : www.laposte.ne=
t ; =0A3615 LAPOSTENET (0,34=80/mn) ; t=E9l : 08 92 68 13 50 (0,34=80/mn)=
=0A=0A

[pilot-db-list] Problem with Boolean field.

[Ship M <sh...@ho...>]

<html><div style='background-color:'><DIV class=RTE>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">Hi<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">&nbsp;<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">Thanks for a great program, and for making I free, I deeply appreciate it.<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">&nbsp;<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">And now the question I have. I have some “problems” working with Boolean fields and filter.<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">&nbsp;<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><FONT size=3><FONT face="Times New Roman"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'">Background - I have made at </SPAN><SPAN lang=EN-GB style="mso-ansi-language: EN-GB">Pilot-DB</SPAN><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"> over Hugo and Nebula award winners, here I use Boolean fields to mark if the book have won the Hugo award, the Nebula award and if I have the book.<o:p></o:p></SPAN></FONT></FONT></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">&nbsp;<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">If I want to find the books I don’t have and use the icon (Finds String) - entering 0 at the string and chose “Have the Book” Field in Search, it works fine, I get a list of the books I don’t have.<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">&nbsp;<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">When I make a filter to do the same using the following script (and %7 0) it returns an empty list why???? What am I missing her???.<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">&nbsp;<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">If I change the script to (and %7 1) it works fine, it returns a list of the books I have.<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">&nbsp;<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">I have found out that using the script (! %7 1) works? This returns a list of the books I don’t have. What value dose a Boolean field have when it is off.<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">&nbsp;<o:p></o:p></FONT></FONT></SPAN></P><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'">Here is some Systeminfo if you need it:<o:p></o:p></SPAN></P><o:p></o:p></FONT></FONT></SPAN>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">&nbsp;<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB"><FONT size=3><FONT face="Times New Roman">Pilot-DB version 1.1.0 (14 Nov 2003)<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">Running on a Palm Vx<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">With Palm OS 3.5.3<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">And 6392K Free Memory<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB"><FONT size=3><FONT face="Times New Roman">&nbsp;<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">Fields in the database:<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">Author, last name (string)<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">Author, first name (string)<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">Title (string)<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">Publishing year (Integer)<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman"># Book in series (Integer)<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">Hugo winner (Boolean)<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">Nebula winner (Boolean)<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">Have the book (Boolean)<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">&nbsp;<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">Once again thanks for great program.<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">&nbsp;<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">In advance thank you and Have a nice day :-)<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">&nbsp;<o:p></o:p></FONT></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=DE style="mso-ansi-language: DE; mso-fareast-font-family: 'MS Mincho'"><FONT size=3><FONT face="Times New Roman">Ship Moller<o:p></o:p></FONT></FONT></SPAN></P><SPAN lang=DE style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-ansi-language: DE; mso-fareast-font-family: 'MS Mincho'; mso-fareast-language: DA; mso-bidi-language: AR-SA">Copenhagen, Denmark</SPAN></DIV></div><br clear=all><hr>Find din nye bolig med  <a href="http://g.msn.com/8HMADADK/2743??PS=">MSN Bolig</a>  </html>

Re: [pilot-db-list] Re:New db version 1.1

[Nathan K. <na...@ve...>]

On Mon, Apr 19, 2004 at 02:09:26PM +0200, marc.chalain wrote:
> I will try to release a last pilot-db 1.1 version soon, with
> some corrections. After that i will stop pilot-db development
> totally.

Hello Marc ---

You mentioned a while ago that you had a more current version on your
hard drive somewhere that you would send to me if you found it.  If
you could, that would be great.  If you want to go further and release
one last version, that would be even better.

I'm very frustrated with the version that was left in CVS.  It has
lots of bugs and problems with it, some obvious and some only being
found as I fix the obvious layer.  I'm considering giving up on the
CVS version, making it an experimental branch, and rolling back to the
last available 1.1 code, which appears to be in much better shape.

I got started with this project because I thought it would be useful
to me if it had better linked field support, but as it is I've spent
all my time just trying to get the thing to work as well as the
previous release.  If you have better or more current 1.1 code, I'd
certainly rather start with it than with that available on the web
site.  So if you have a better version, I'd love to have access to it!

Thanks!

Nathan Kurz
na...@ve...

[pilot-db-list] Re:New db version 1.1 - Wonderfull !

[marc\.chalain <mar...@la...>]

If i forget catalan support i'm very sorry.
If it's just an installation=
 problem, i will be looking for
the solution.

In the both case i will=
 try to correct that.

As old pilot-db users have seen, Nathan took the=
 leadership on
the development. I'm tired of the Pilot-DB development, i=
 work
on other subjects (Karate and Linux kernel), then i can spend
mor=
e time.
I will try to release a last pilot-db 1.1 version soon, with
so=
me corrections. After that i will stop pilot-db development
totally.
=0D
=
Good Luck to Nathan and the team.

>         You may have answereed to =
that message, but we do
not find it in our
> files.
> 
>         Than=
ks in advance.
> 
>         Paco Rivi=E8re
> 
> Original message send=
ed 24-1-2004 follows: ---------------
>         Hello Marc,
> 
>      =
   I have installed the new 1.1 db high resolution
version on my T3 and=0D
=
> its wonderfull !
> 
>         The only thin is the setup does not ins=
tall the
ca-overlay on the palm.
> This is not a problem for me at all.=
 It just installed
afterwards and it works
> wonderfully in catalan wit=
h all the latest corrections. But
it can be a very
> important problem =
for new users. And we have a lot of them.
In fact if you see
> our stat=
s at http://baixar.palmcat.org db is our star
application with the
> hi=
ghest user download quote !
> 
>         Could anything be done for thi=
s to be solved?
> 
>         Due to the success of the catalan version =
of DB we
have decided to
> translate the help and the script tutorial a=
n the next
months. Could you then
> compile for me the help-ca.prc or i=
f this is not possible
send me instructions
> for I can find anybody fo=
r doing it for me? Would it be any
problem to include
> any other trans=
lated file in next releases as for example
the script-tutorial?
> 
>=0D
=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
> Salut
> Paco Rivi=E8re
> Coordinador de PalmCAT
> Palm=
 Powered Expert Guide
>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> fri...@pa...
> http:/=
/www.palmcat.org
> 
> 8 llibres, 9 articles, 6 bases de dades i 17 prog=
rames
lliures a la vostra
> disposici=F3, i en catal=E0!
> 
>        =
 Mireu la p=E0gina de baixada http://baixar.palmcat.org
> =0A=0AAcc=E9de=
z au courrier =E9lectronique de La Poste : www.laposte.net ; =0A3615 LAPO=
STENET (0,34=80/mn) ; t=E9l : 08 92 68 13 50 (0,34=80/mn)=0A=0A

[pilot-db-list] install problem

[<tnj...@ju...>]

Hello,
I received a Visor Deluxe as a gift and am new to PDAs. I downloaded the
program from pdbtools.exe  into my Handspring, add-on folder. After
unzipping it I had the application available but there was no install
file to get it into my PDA. It works well on my desktop computer and
would like to try it with the PDA. Can you help me?
                                thanking you in advance,    -Tony L-

Re: [pilot-db-list] Pilot-DB - font size on Sony Clie

[Mark W. <mar...@fr...>]

Try Global Preferences > Display and remove tick from Enable High 
Resolution.  I use an SJ33 and the tiny hi-res text was one of my 
reasons for converting from Smartlist, but everyone has different views 
(excuse the pun).

Best wishes.

Mark Walker
On 15 Apr 2004, at 17:25, Simon McCarthy wrote:

> I just started using Pilot DB and I really like it...
>
> ...except that the text is tiny (and almost unreadable) on my Sony 
> Clie PEG-SJ22/E.
>
> The online manual says that there should be a question on first 
> starting DB-Pilot asking whether you want tiny or normal text, but I 
> was never asked the question and I can't see how to change the text 
> size.
>
> I have also tried uninstalling and reinstalling, but it doesn't seem 
> to make any difference.
>
> I am using version v 1.1.0.
>
> Regards,
>
> Simon McCarthy

[pilot-db-list] Pilot-DB - font size on Sony Clie

[Simon M. <Sim...@Si...>]

I just started using Pilot DB and I really like it...

...except that the text is tiny (and almost unreadable) on my Sony Clie
PEG-SJ22/E.

The online manual says that there should be a question on first starting
DB-Pilot asking whether you want tiny or normal text, but I was never
asked the question and I can't see how to change the text size.

I have also tried uninstalling and reinstalling, but it doesn't seem to
make any difference.

I am using version v 1.1.0.

Regards,

Simon McCarthy

[pilot-db-list] Databases templates and db-JFile3 plugin.

[<vi...@gm...>]

Hi all,

I'm new in this list. I'm using Pilot-DB some months in my Tungsten E and I=
=20
have to thank the developer for such a fantastic piece of software.

And now, some questions:

=2D Is there any "central" place where I can find examples or templates of =
free=20
Pilot-DB databases?=20
=2D I've installed in the Palm memory a JFile database (found at PalmGear) =
and=20
the db-JFile3 plugin (version 1.1.0). Despite I start the plugin corretly,=
=20
I'm unable of accessing this db. I get no error, indeed, I get nothing.=20

Thanks a lot in advance. Regards,

=2D-=20
Res publica non dominetur.

 V=EDctor Peinado || vitojph gmx net || http://vitojph.yoll.net
 Fingerprint: C0D5 22EA 607C 47F9 28D7 3FFB 1CE0 342F 1285 66CA
 JID: vitojph jabber dk || <vitojph />

[pilot-db-list] anomalie avec pilot-db v1.1.0

[jean-pierre d. <jpd...@wa...>]

Hello
J'ai install=E9 pilot-db v1.1.0 sur mon Cli=E9 PEG-675C.
J'ai cr=E9=E9 une base comportant (entre autres) un champ 'Note'.
J'ai observ=E9 que ce dernier ne dispose pas des fonctions Copier/Couper/Co=
ller. Est-ce une anomalie ou des fonctions absentes de cette version.
Je travaillerai bien sur ce projet, au moins pour la partie documentation; =
est-ce possible de me joindre =E0 l'=E9quipe ?
Bon courage

Re: [pilot-db-list] RE: testing AddressDB and Plucker

[Nathan K. <na...@ve...>]

On Sat, Apr 10, 2004 at 12:21:59PM -0500, Kyle davis wrote:
> 	I'll give release 5 alpha a try and let you know about the AddressDB
> plugin situation on my m130... 

I'd appreciate if you (and perhaps others) could test this.  It works
for me on a simulator, but there may be other issues with a real device.

<http://sourceforge.net/tracker/?group_id=621&atid=100621>

If you are ambitious, going through the first 20 or so bugs listed here
and reporting your results would help too.  I think some of them have
been solved, but for some I don't have the ability to actually test things.

> 	What are your thoughts about also hooking it up to Plucker somehow,
> or having a picture datatype?

Haven't thought about it, but it seems like a reasonable (long-term)
idea:  more likely hooking it up then having a picture type.  I
haven't actually used Plucker, but whenever I've been having Palm
programming issues, it seems like their list archives have someone who
has hit the same issues a few years ago.  Which makes me think they
might be a bit ahead of us...

--nate

[pilot-db-list] RE: Pilot-db-list digest, Vol 1 #877 - 1 msg

[Kyle d. <dav...@ya...>]

Nate,

	I'll give release 5 alpha a try and let you know about the AddressDB
plugin situation on my m130... 

	What are your thoughts about also hooking it up to Plucker somehow,
or having a picture datatype?

Kyle

-----Original Message-----
From: pil...@li...
[mailto:pil...@li...] On Behalf Of
pil...@li...
Sent: Wednesday, April 07, 2004 10:19 PM
To: pil...@li...
Subject: Pilot-db-list digest, Vol 1 #877 - 1 msg

Send Pilot-db-list mailing list submissions to

	pil...@li...



To subscribe or unsubscribe via the World Wide Web, visit

	https://lists.sourceforge.net/lists/listinfo/pilot-db-list

or, via email, send a message with subject or body 'help' to

	pil...@li...



You can reach the person managing the list at

	pil...@li...



When replying, please edit your Subject line so it is more specific

than "Re: Contents of Pilot-db-list digest..."





Today's Topics:



   1. still another alpha release to try (Nathan Kurz)



--__--__--



Message: 1

Date: Wed, 7 Apr 2004 03:02:33 -0600

From: Nathan Kurz <na...@ve...>

To: pil...@li...

Subject: [pilot-db-list] still another alpha release to try



Gradually things are getting there.  Here's another alpha to try.



1.2.0 alpha 5:

- changed bogus config.h.in that ignored certain configuration variables

- fixed "Scrolling with the 5-way no longer works" (917590)



Periodically, (OK, every time I touch the code) I'm unsure whether a

general rollback would be a better choice.  The current CVS code has

some parts that are in really bad shape, whereas the 1.1.0 seems a

little more readable.  But I don't want to throw away any improvements

that Scott might have made (of which I presume there must be some).



But for now at least I'll proceed with the straight ahead charge...



--nate







--__--__--



_______________________________________________

Pilot-db-list mailing list

Pil...@li...

https://lists.sourceforge.net/lists/listinfo/pilot-db-list





End of Pilot-db-list Digest

[pilot-db-list] still another alpha release to try

[Nathan K. <na...@ve...>]

Gradually things are getting there.  Here's another alpha to try.

1.2.0 alpha 5:
- changed bogus config.h.in that ignored certain configuration variables
- fixed "Scrolling with the 5-way no longer works" (917590)

Periodically, (OK, every time I touch the code) I'm unsure whether a
general rollback would be a better choice.  The current CVS code has
some parts that are in really bad shape, whereas the 1.1.0 seems a
little more readable.  But I don't want to throw away any improvements
that Scott might have made (of which I presume there must be some).

But for now at least I'll proceed with the straight ahead charge...

--nate