Neither HTML or C/C++, I looked at the assembled 68K code resource in
ePQA.PRC.
I wouldn't hold my breath on the Clipper source ever being available - I
suspect that you will see a next generation first.
As for opensource/free software... We'll, I'm kind of a fan of
intellectual property rights and commercial software, being as that is
how I make my living. That's not to say that I don't believe in sharing
information. If I had worked this out using only your requirements, I'd
be glad to 'share'. The problem is that I simply snooped at someone
else's work. I don't feel that it is my place to 'liberate' someone's
work for them.
Perhaps you should take up your enhancement ideas with Steven's Creek.
Some things, like 'validate' would be more useful if they could be part
of the 'submit' process (complete with locally generated clipper result
pages).
I'm not sure I like the idea of a hidden PRC generating cookies. I'm
still figuring out how to clear the clipper cache... ;>
Good Luck,
-jjf
-----Original Message-----
From: Michael C. Neel [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 07, 2000 2:11 PM
To: Palm Developer Forum
Subject: Re: palmcall and the clipper
> So, going back to your first question - you seem to be asking, how
does
> ePQA find the fields to insert the text?
In a nutshell, yes. Where is that magic ptr to the data in the fields?
> Ugh, I don't feel right answering that one directly. I've now looked
at
> ePQA.PRC (it's only about 8k of code). The method seems pretty
straight
> forward, but it is not really my 'hack' to reveal, since I just had to
> look at the working code.
Do you mean the html source or the c/c++ source? I didn't find any
c/c++
source for the prc on his site (or anywhere for that matter).
> Is there a reason that you don't want to just use ePQA? It seems to
be
> intended as a tool for developers (as opposed to an end user
> application).
Believer in opensource/free software (esp. development tools), and I
have
other ideas this could be used in, such as sudo-cookies: Instead of a
real
submit button, the submit is a palmcall which stores the cookie info in
it's
database, then forwards on the request (using INet or maybe a gotoURL
w/clipper) after doing some data validation.
On ThinAirMail, when you want to see your settings, it makes a wireless
connection. If there was a sudo-cookie with your settings stored, it
would
only need to make a connection if you changed your settings, saving you
a
few bytes to read mail with.
BTW, I really appreciate you taking the time to help me on this. Being
relatively new to palm os programming (but not to programming in
general) I
sometime overlook the obvious. Like the formspy.pl script that comes
with
Poser. Knowing about that a few days ago would have saved me quite a
few
hours of C coding...
Mike
<hint to palm> of course if palm just made the source to clipper
available,
all of this would be mute </hint to palm> ;)
--
For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palm.com/devzone/mailinglists.html
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
