Does anyone know if the Pick .Net API will work on a handheld device
running the .Net Compact Framework?

Who at Tiger Logic would know the answer to this question?

Sholom

On Dec 2, 3:46*am, sh <sham... (AT) prupipe (DOT) com> wrote:
Ummmm .... why not just call TL & find out? Looking at the support
forums, and who is responsible for the MVSP forum, I'd suggest a good
place to start would be Mark Locke, D3 Windows Support Manager,
TigerLogic Corporation

Ross Ferris wrote:

Yeah, why is this a "who would know" question? Just contact Support
through your normal channels and anyone there who works with MVSP will
get back to you. It's just like any other product.

Software needs to be built with CF or it simply won't work with CF.
So unless TL advertises CF somewhere, your chances are VERY slim that
it's supported for MVSP (.NET or Java). Given the lack of interest
demonstrated in this market for mobile computing, I'd doubt that it's
even on the list of short-term development projects.

I recommended this in the U2 forum a few days ago and I believe this
applies to MVSP, QMClient, and other interfaces: Rather than trying to
go direct from mobile<>MV, it's SO much easier to go
mobile<>webservice<>MV. The technology is stable, well documented,
and easy to implement.

I'm working on extensions for MVSP to provide additional functionality
which will almost certainly never be built-in. A proxy for mobile
could work its way into those extensions if there is adequate demand.

Regards,
T

On Dec 2, 5:21*am, Tony Gravagno <nos... (AT) nospam (DOT) invalid> wrote:
I can not comment on TL products. However, if this type of
connectivity is important for your product you might consider
InterSystems Cache. We do support a Compact Framework version of our
managed provider (api). Along with many other connectivity options.

Let me know if you need more information or have any questions


Richard S Taylor
Sales Engineer
InterSystems Corporation
Office: 443-340-8614
email: Rich.Taylor (AT) Intersystems (DOT) com

On 12/2/2010 5:21 AM, Tony Gravagno wrote:

I don't have normal channels. They are all abnormal!

That's how I do it now - via webservice. But while it might be easy for
me to implement, it's not easy for the end-user to experience a whole
day long, day-in day-out. It's a multi-step procedure (and don't forget
the return trip) mobile->webservice->MV->webservice->mobile. There can
(and is) a noticeable time lag going through webservices. I don't see
why it's so terrible to experiment on a direct connection to MV and see
the time differential. Have you done so?

Sholom

Sholom wrote:

Is someone really using a mobile device to connect to your data That
much? Mobile users are used to some delay, even on "3g/4g", as are
browser users. We pay for the convenience of getting data Where we
want with a small price penalty on When we want the data - and it's
only an extra second or two, hardly unreasonable.

Not to quibble but notice that I used <> rather than ->, acknowledging
traffic in both directions.

That's unfortunate and I won't argue with your experience. It's a
problem that needs to be fixed. So maybe another pipe Is required, or
more efficient use of web services.

No, I have not done so, only because MV providers don't have CF
libraries. Correction: I Thought that was the case for all providers
but I found out last week that there is a UO/CF package, and as Rich
told us today, Caché has one. But for all others that I work with
I've done a generic CF<>WS<>MV connection, which means the client is
completely agnostic of the database, which at the extreme is a nice
separation of UI from rules anyway.

I don't think there's anything wrong with using a MV-specific library
in your mobile apps if you can find one, and I'd be tickled to get
that functionality. As a v1.0 release for a mobile app however, I'd do
it the easy way. Apparently you've already done this. There's
nothing wrong with looking for a better solution, as long as you've
really exhausted the capabilities of the existing one.

For reference, I have not touched Windows Phone 7 development yet. I
haven't done anything with mobile since my PDA effort with QM early
last year (see blog). As much as I'd like to I just don't see the
market yet, here or elsewhere. (Being "tickled" isn't a pragmatic
reason for me to write code unfortunately.) If someone else sees a
market for WP7, or even Android, I'd enjoy working on a MV-related
project. My most recent efforts are for voice/SMS/Fax/PBX integration
with MV - I'm having great success with all of that.

Tony Gravagno
Nebula Research and Development
TG@ remove.pleaseNebula-RnD.com
Nebula R&D sells mv.NET worldwide
and provides related development services
remove.pleaseNebula-RnD.com/blog
Visit PickWiki.com! Contribute!
http://Twitter.com/TonyGravagno