Comments on: PDA GUI for MV http://nebula-rnd.com/blog/tech/mv/2008/12/mvpda01.html Welcome to the Nebula Fri, 06 Jan 2012 09:44:06 +0000 hourly 1 http://wordpress.org/?v=3.1 By: Tony Gravagno http://nebula-rnd.com/blog/tech/mv/2008/12/mvpda01.html/comment-page-1#comment-305 Tony Gravagno Wed, 31 Dec 2008 07:42:08 +0000 http://Nebula-RnD.com/blog/tech/mv/2008/12/mvpda01.html#comment-305 <p>You've hit on many key topics, Peter. Thanks for your comments.</p> <p>QMPDA doesn't have a telnet server and no QMClient. There isn't any "remote" way to connect into it. So you can't browse into it or use Winnix. I need to write this bit of connectivity myself.</p> <p>My current approach, as you suggest, is to use a command-line like:<br /><strong>qmpda -quiet -aPDA.ACCT</strong></p> <p>From there I can push/pull data with a custom API as described in recent CDP threads and blog entries. (You see, there are practical applications for all of this rhetoric...)</p> <p>Due to limitations in the feature set of the PDA, this isn't as easy as with a full version of Windows. I need to manually work out issues interacting with a command-line process - things that are handled automatically in a PC. I'll discuss this with Martin over the next couple weeks. I'm only about 50% confident in my ability to do this part alone.</p> <p>It's possible that a more modern PDA would not have the limitations, I need to research that. I could also commission someone to finish that specific connectivity segment for the older devices. But with no funding whatsoever, this is all way on the bottom of the priority list, and I'm not inclined to pay someone to do development unless someone tells me they have end-users waiting to pay for the results.</p> <p>So we're very close to seeing all of this work in harmony - nevertheless it may still not get done. As we've discussed in CDP, business requirements need to drive the technical decisions.</p> You’ve hit on many key topics, Peter. Thanks for your comments.

QMPDA doesn’t have a telnet server and no QMClient. There isn’t any "remote" way to connect into it. So you can’t browse into it or use Winnix. I need to write this bit of connectivity myself.

My current approach, as you suggest, is to use a command-line like:
qmpda -quiet -aPDA.ACCT

From there I can push/pull data with a custom API as described in recent CDP threads and blog entries. (You see, there are practical applications for all of this rhetoric…)

Due to limitations in the feature set of the PDA, this isn’t as easy as with a full version of Windows. I need to manually work out issues interacting with a command-line process – things that are handled automatically in a PC. I’ll discuss this with Martin over the next couple weeks. I’m only about 50% confident in my ability to do this part alone.

It’s possible that a more modern PDA would not have the limitations, I need to research that. I could also commission someone to finish that specific connectivity segment for the older devices. But with no funding whatsoever, this is all way on the bottom of the priority list, and I’m not inclined to pay someone to do development unless someone tells me they have end-users waiting to pay for the results.

So we’re very close to seeing all of this work in harmony – nevertheless it may still not get done. As we’ve discussed in CDP, business requirements need to drive the technical decisions.

]]> By: excalibur21 http://nebula-rnd.com/blog/tech/mv/2008/12/mvpda01.html/comment-page-1#comment-304 excalibur21 Tue, 30 Dec 2008 22:46:48 +0000 http://Nebula-RnD.com/blog/tech/mv/2008/12/mvpda01.html#comment-304 Hi I am keen on seeing the QM PDA development unfortunately the first couple of clients I have in mind only need a couple of licences so I alone cannot justify Martin's efforts. Firstly any PDA development has to be able to stand alone even in Sydney there are significant areas without wifi coverage and the forests of Tasmania are definitely off the wifi map.  Both of these places are areas where the simple invoice recording systems I plan are needed, and the business rules being contained in the PDA are essential. The connection method is of particular interest.  My initial thought was why not use the existing browser technology as this fits in with larger developments and there are mini PDA web servers available. MY next step was Windows forms using Visual Studio 2008 and the wifi developer.  In this case the use of the QM EXECUTE command is not an issue as there is only one user. Then Winnix announced that the terminal emulator works on QM PDA and whilst this is not a GUI it does bridge a gap nicely to get the product out there.  However I see in the blog that Telnet is not available so how does Winnix connect?  This may clarify some of my other issues on CDP. Thanks Peter McMurray   Hi
I am keen on seeing the QM PDA development unfortunately the first couple of clients I have in mind only need a couple of licences so I alone cannot justify Martin’s efforts.
Firstly any PDA development has to be able to stand alone even in Sydney there are significant areas without wifi coverage and the forests of Tasmania are definitely off the wifi map.  Both of these places are areas where the simple invoice recording systems I plan are needed, and the business rules being contained in the PDA are essential.
The connection method is of particular interest.  My initial thought was why not use the existing browser technology as this fits in with larger developments and there are mini PDA web servers available.
MY next step was Windows forms using Visual Studio 2008 and the wifi developer.  In this case the use of the QM EXECUTE command is not an issue as there is only one user.
Then Winnix announced that the terminal emulator works on QM PDA and whilst this is not a GUI it does bridge a gap nicely to get the product out there.  However I see in the blog that Telnet is not available so how does Winnix connect?  This may clarify some of my other issues on CDP.
Thanks
Peter McMurray
 

]]>