ok, I'll try to help with what were possible to me. ;-)
what do you think will be need first for this task ? remove the
dependencies of equinox ?
there is a bug created for this ?
Cristiano
On 12/06/12 17:08, Scott Lewis wrote:
Hi Cristiano,
Yes, our existing ECF releng is currently done with
Buckminster+Maven+PDE+Hudson...but what we're talking about here
(Android libs from ECF codebase) is mostly what I would consider
in the category of 'new' packaging and releng...and so doesn't
require/imply any particular technology (IMHO). Sure...there
could be some integration with what's there...but that's usually
the case for releng...is my observation.
Scott
On 6/12/2012 12:27 PM, Cristiano Gavião wrote:
Scott,
Perhaps I didn't understand well your wish and/or perhaps don't
understand what you mean about releng... But if were about to do
something related to ECF's Buckminster, honestly is out of my
knowledge...
Cristiano
On 12/06/12 16:10, Scott Lewis wrote:
Hi Christiano,
I'm not sure if knowing Maven and Tycho really limits you
(there's no particular requirement on what build tech is
required/necessary to do this)...but ok.
Scott
On 6/12/2012 12:05 PM, Cristiano Gavião wrote:
Well,
Unfortunately I will not be able to help you with this
releng task because the unique build tool that I'm know well
is Maven and in the last couple years, Tycho.
cheers,
Cristiano
On 12/06/12 15:47, Scott Lewis wrote:
Christiano,
Regrettably, I haven't been able to keep these
example/test apps maintained as ECF has moved forward.
My intention/desire these days is to work on the releng
such that new versions of ECF could be automatically
packaged for Android usage (for client and/or server for
some protocols)...but like many other things, it remains a
little out of reach (for resources/time)...at the moment.
Scott
On 6/12/2012 11:41 AM, Cristiano Gavião wrote:
Hi Scott,
I've tried to get it work today, but I couldn't because
there were some API changes in latest ECF and I couldn't
resolve in my short study time...
But I'll try again tomorrow...
thanks,
Cristiano
On 12/06/12 15:00, Scott Lewis wrote:
Hi Christiano,
Those are some of my early experiments. The goals
were to make some simple/test android clients...that
use ECF for communication.
Scott
On 6/12/2012 8:36 AM, Cristiano Gavião wrote:
Hi,
I've found this project on github:
https://github.com/ECF/Android
Could someone explain me what it is and the goals of
this project?
thanks,
Cristiano
On 11/06/12 13:57, Scott Lewis wrote:
Christiano,
On 6/11/2012 8:51 AM, Cristiano Gavião wrote:
Hi guys,
I was reading this article: http://eclipse.dzone.com/articles/eclipse-indigo-highlights-ecf
and there is a nice video of one android app
using ECF and Google Wave.
Google wave was discontinued, so what is the
alternative in actual days for this kind of
mobile applications ?
So...this effort (by Mustafa Isik and Sebastian
Schmidt) used some of the ECF core classes...and,
in fact whole plugins/jars...to support the Wave
provider work [1]. These plugins/classes...and
their runtime class dependencies...were added to
the Android projects as library jars (I
think)...and so were loaded/used at runtime
without actually running a complete OSGi
framework.
Running outside of OSGi is something that can be
done with much...although not all...of ECF. I do
this myself with other parts of ECF (e.g. the
shared object API)...in order to make it simple to
create Android-based clients that can easily and
extensibly communicate/message with ECF
servers/services (that happen to run under a full
OSGi framework).
There is some work (as yet undone) to do the
releng associated with using the relevant parts of
ECF in a non-OSGi environment. For example, the
creation of the non-bundle jars and the
elimination of the unneeded classes from ECF,
OSGi, and Equinox would be very desirable for this
usage...along with creating a single
distribution-ready Android library...rather than
several jars. Doing these things would make it
much easier for people to consume/use ECF in
Android environments.
One other point...although Google wave was
discontinued as an application, I suspect Google
would like to continue to use (and have others
use) the wave protocol...i.e. [2]. This was the
work upon which [1] is based, so I don't think
this is completely out of the technical picture
(although the Wave application is indeed
discontinued). But I'm not directly connected
with the Wave protocol work these days...so I
could be wrong on this.
Scott
[1] https://github.com/ECF/Wave
[2] http://www.waveprotocol.org/
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
|
