![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Has anyone done work with DesignBais on PDAs using Pocket Internet Explorer? I see on the DesignBais website that it doesn't handle multivalue inputs (I guess they mean in a grid setting) on PDAs. How do you get around this limitation? Any other issues with DesignBais & PocketIE? |
#3
| |||
| |||
|
|
I have not so much done an app to work in a pda, but have done a few w3c status screens so i can monitor the system from my phone when out and about. There is a good white paper on the different mode differences at http://designbais.bais.com.au/dbinst...in%20Modes.pdf rgds Symeon. sh wrote: Has anyone done work with DesignBais on PDAs using Pocket Internet Explorer? I see on the DesignBais website that it doesn't handle multivalue inputs (I guess they mean in a grid setting) on PDAs. How do you get around this limitation? Any other issues with DesignBais & PocketIE? |
#4
| |||
| |||
|
|
That was the document I was refering to. Seems like it really has problems working on PDAs. Symeon wrote: I have not so much done an app to work in a pda, but have done a few w3c status screens so i can monitor the system from my phone when out and about. There is a good white paper on the different mode differences at http://designbais.bais.com.au/dbinst...in%20Modes.pdf rgds Symeon. sh wrote: Has anyone done work with DesignBais on PDAs using Pocket Internet Explorer? I see on the DesignBais website that it doesn't handle multivalue inputs (I guess they mean in a grid setting) on PDAs. How do you get around this limitation? Any other issues with DesignBais & PocketIE? |
#5
| |||
| |||
|
#6
| |||
| |||
|
|
Sh, Yes, Db works very well on PDAs. I have it running on my Dell Axim for demos. The thing you need to remember is that a PDA is a special case of W3C and is has its own standards (and you probably want to use smaller fonts). So a form written for a W3C mode will not be displayed properly in PDA mode. You will need to specifically tag the form for PDA mode. We are doing some work on W3C mode and I believe that On-Form Reports will be able supported in W3C mode in our upcoming 4.1 release due out the end of this month. Rick |
#7
| |||
| |||
|
|
Sh, Yes, Db works very well on PDAs. I have it running on my Dell Axim for demos. The thing you need to remember is that a PDA is a special case of W3C and is has its own standards (and you probably want to use smaller fonts). So a form written for a W3C mode will not be displayed properly in PDA mode. You will need to specifically tag the form for PDA mode. We are doing some work on W3C mode and I believe that On-Form Reports will be able supported in W3C mode in our upcoming 4.1 release due out the end of this month. Rick |
#8
| |||
| |||
|
|
Rick Weiser wrote: Sh, Yes, Db works very well on PDAs. I have it running on my Dell Axim for demos. The thing you need to remember is that a PDA is a special case of W3C and is has its own standards (and you probably want to use smaller fonts). So a form written for a W3C mode will not be displayed properly in PDA mode. You will need to specifically tag the form for PDA mode. We are doing some work on W3C mode and I believe that On-Form Reports will be able supported in W3C mode in our upcoming 4.1 release due out the end of this month. Rick Rick I quite understand that screens must be fashioned specifically for a PDA. That stands to reason, given it's smaller real estate and more limited functionality. My question is, according to the document on your web-site, it won't deal with multivalue input or output. Is that true? If so, how does one get around that limitation? And doesn't that defeat it's whole purpose (or at leat a sizeable portion of it)? Sholom |
#9
| |||
| |||
|
|
sh wrote: Rick Weiser wrote: Sh, Yes, Db works very well on PDAs. I have it running on my Dell Axim for demos. The thing you need to remember is that a PDA is a special case of W3C and is has its own standards (and you probably want to use smaller fonts). So a form written for a W3C mode will not be displayed properly in PDA mode. You will need to specifically tag the form for PDA mode. We are doing some work on W3C mode and I believe that On-Form Reports will be able supported in W3C mode in our upcoming 4.1 release due out the end of this month. Rick Rick I quite understand that screens must be fashioned specifically for a PDA. That stands to reason, given it's smaller real estate and more limited functionality. My question is, according to the document on your web-site, it won't deal with multivalue input or output. Is that true? If so, how does one get around that limitation? And doesn't that defeat it's whole purpose (or at leat a sizeable portion of it)? Sholom I'll request and recommend that you allow a couple of weeks for a response, as the answer you get about MV Input controls might change by then. If v4.1 does support on-form reports then this is one solution to the problem of maintaining dependencies in a grid on a PDA. You can simulate the MV Input control with an on-form report (grid), allowing insert, change, and delete of line items. Since a grid is built with a dynamic array, your BASIC code can easily manage the update operations using standard methods: info = delete(info,selectedrow) or info = insert(info,selectedrow;line) If this is the way we'll need to do things, I'll do a blog entry to explain how it works. See other recent updates: http:// removethisNebula-RnD.com/blog/category/tech/mv/designbais/ Whether or not on-form reports are supported for PDA in v4.1, there are different ways to skin this cat. The MV Input control is certainly a convenient way to maintain correlated MV data, but it's not the only way. ad Of course I'll offer development and consultation services. /ad HTH T |
#10
| |||
| |||
|
|
I'll request and recommend that you allow a couple of weeks for a response, as the answer you get about MV Input controls might change by then. If v4.1 does support on-form reports then this is one solution to the problem of maintaining dependencies in a grid on a PDA. You can simulate the MV Input control with an on-form report (grid), allowing insert, change, and delete of line items. Since a grid is built with a dynamic array, your BASIC code can easily manage the update operations using standard methods: info = delete(info,selectedrow) or info = insert(info,selectedrow;line) If this is the way we'll need to do things, I'll do a blog entry to explain how it works. See other recent updates: http:// removethisNebula-RnD.com/blog/category/tech/mv/designbais/ Whether or not on-form reports are supported for PDA in v4.1, there are different ways to skin this cat. The MV Input control is certainly a convenient way to maintain correlated MV data, but it's not the only way. ad Of course I'll offer development and consultation services. /ad HTH T |
![]() |
| Thread Tools | |
| Display Modes | |
| |