Seeing as porting something like TomCat to android seems a little
insane, is there any way to use the DataAPI directly from a local
android/iphone client application without needing a server?
I asked this earlier but intended to make it public.
I suspect the answer is no (else there would be
What about a HTML5 based mobile client? Newer browsers should also support
offline-storage (in theory)...
- Reply message -
De : Thomas Wrobel darkfl...@gmail.com
Date : sam., avr. 16, 2011 12:50
Objet : Starting project: Mobile client
Pour : Yuri Z vega...@gmail.com, wave-dev
Il giorno 05/apr/2011, alle ore 14.37, Thomas Wrobel ha scritto:
Offtopic indeed :)
Its more an issue of what Giacomo wants to do though.
Yes... :)
So... finally, none is working at the development of an iPhone client, so, does
someone have some idea on which is the best way?
Using HTTP
I'm working on a mobile android wave client,
Do you think we can share the same software requirements document?
Id happy to share resources, but we haven't got anything so organised as that.
We started with a couple of simple use cases and built the code around them.
We have been mostly
On 4 April 2011 21:56, Giacomo Piva p...@innovativa.it wrote:
snip
The main problem with iPhone development is the closure to third-part
frameworks and library also (for what I can understand at the moment) the
only way to develop an iPhone native client application is using HTTP
Protocol
It think that native clients for IPhone/Android are great ideas and the more
the merrier, however it seems to me that it would be a lot easier to make Data
API based clients first.
Sent from my iPhone
On 5 באפר 2011, at 12:02, Thomas Wrobel darkfl...@gmail.com wrote:
I'm working on a mobile
On 5 Apr 2011, at 10:11, Yuri Z. wrote:
It think that native clients for IPhone/Android are great ideas and the more
the merrier, however it seems to me that it would be a lot easier to make
Data API based clients first.
Or indeed just mobile web applications using JQMobile etc
Sent
On 5 Apr 2011, at 10:11, Yuri Z. wrote:
It think that native clients for IPhone/Android are great ideas and the more
the merrier, however it seems to me that it would be a lot easier to make
Data API based clients first.
Or indeed just mobile web applications using JQMobile etc
Ok, You mean porting client API to C language? this is a good starting point,
if someone have some experience and want spend some emails to show me how to do
it I would
Giacomo
Il giorno 05/apr/2011, alle ore 11.05, Chris Mear ha scritto:
On 4 April 2011 21:56, Giacomo Piva
While web clients and data API clients would obviously be easier to write, I
think it would be difficult to get people to adopt the wave protocol and
WIAB unless native clients with full real-time editing are available.
That said, I would love to see _any_ Android client, and I am glad there is
Its certainly possible to write a native client in android using
websockets or socketIO - however the tricky bit is what your sending
via them and processing the response's.
My own application demands a native client, as I'm dealing with 3d and
camera manipulation, however wouldn't even a simple
On 5 Apr 2011, at 12:02, Thomas Wrobel wrote:
Its certainly possible to write a native client in android using
websockets or socketIO - however the tricky bit is what your sending
via them and processing the response's.
My own application demands a native client, as I'm dealing with 3d and
On 5 April 2011 13:10, Scott Wilson scott.bradley.wil...@gmail.com wrote:
On 5 Apr 2011, at 12:02, Thomas Wrobel wrote:
Its certainly possible to write a native client in android using
websockets or socketIO - however the tricky bit is what your sending
via them and processing the
Offtopic indeed :)
Its more an issue of what Giacomo wants to do though.
I know my application wouldn't be possible on a web app for awhile,
but maybe Giacomos would.
I'll look into Obigo/WARP/W3C widget solutions anyway though as I dont
know much about them.
I'm not sure Id want any special
I try to reply to all ...
In terms of a mobile client, what sort of functionality would you like to
see or have you envisioned for it?
I think that the mobile client should permit the basic operations (create,
edit, invite ...) and should also permit to store and handle a multiple
connection
uhm... are you sure? why? I think that a mobile client shall require a
connection to work, like a browser...
Mobile connection is by its nature unreliable. I find it best to code with
the assumption that the network may not be available. Hence the need for
some sort of offline storage.
--
I'm working on a mobile android wave client, only with a different
goal (geolocating information and sharing it rather then a normal
text client).So different GUI, but same comms needed. I had a working
connection way back with FedOne but since then things have changed and
I've been struggling to
17 matches
Mail list logo
