Hi there,
Developing Hybrid Applications using Cordova/PhoneGap is very popular
today, but for Automation Testing, it is very hard for these Hybrid
Applications.
Selenium is a very popular tool on automation testing. So far there are
Selenium web drivers for Android, iOS and other mobile
Cordova for (Open) webOS is playing an important role, for still available
hardware (TouchPad and Phones) and new hardware (there are Open webOS Ports for
the Galaxy Nexus and Nexus 7 for example).
Also see
Jesse ,
yup , I saw that just after sending the mail!
I wont register yet as Tizen is not yet in PhoneGap...
And for now I am involved only in Tizen Port
thanks,
Paul
On Mon, Mar 18, 2013 at 10:45 AM, Jesse MacFadyen
purplecabb...@gmail.comwrote:
Hi Paul,
Anyone who wants to be listed at
Thanks for the highlights Fil. Makes for easier reading!
On Mon, Mar 18, 2013 at 5:21 PM, Filip Maj f...@adobe.com wrote:
Highlights w.r.t. Cordova:
1. Application manifest JSON (yay!) [1]:
2. There is an Application interface now in charge of handling:
- pause/resume/launch/terminate
Excellent Suggestion. Plugin management is a huge focus for the next few
months and likely the major change for cordova 3.0. Expect improvements.
I'll let others speak to the specifics of the current plugin versioning
plan, but its great to have outside feedback on what we should focus on.
Yes, the plan is to have plugins versionned and backwards compatible with
previous versions of Cordova. Depending on what cordova version you have
installed there will/should be a specific version of that plugin that works
with it. I will kick off a thread about this.
On Tue, Mar 19, 2013 at
Hey all,
Plugins need to be versioned to be backward compatible with previous
versions of Cordova. I had a discussion with the PhoneGap:Build team
yesterday and they need to be backward compatible. Ally Ogilvie also
mentioned in separate thread that game developers would also need something
like
Nothing much out there for automation of hybrid apps, I have been working
on a project called medic [1] that hooks into a hybrid app using
javascript within the hybrid app package. Medic is the project that powers
Cordova's rudimentary CI setup [2]. It's designed to compile and deploy
our test
Selenium for iOS and Android must use WebViews, no? It would probably be
possible to write a Cordova plugin to add selenium to a project for testing.
On Tue, Mar 19, 2013 at 1:39 PM, Filip Maj f...@adobe.com wrote:
Nothing much out there for automation of hybrid apps, I have been working
on a
That sounds reasonable to me.
How would this be maintained? Would there be some automated process that
keeps that mapping up-to-date?
On Tue, Mar 19, 2013 at 10:59 AM, Anis KADRI anis.ka...@gmail.com wrote:
Hey all,
Plugins need to be versioned to be backward compatible with previous
Hey Ally, good to hear from you and awesome feedback!
Your thread came at a good time because Anis and Braden are starting to
tackle these issues in a sane way.
As Anis mentioned, a discussion thread should be jumping up today. You can
also track the plugin progress through the plugman code (no
+1
However, I think we may need a better property/value pair name than
just cordova_version:
plugin_versions. This is because I feel like there is a implicit idea that
this particular plugin will work on a specific version of Cordova, but for
all platforms. Whereas in reality, most of the plugins
I personally dislike Selenium because it's next to impossible to set
up and write tests for, and it's extremely large and full of cruft.
After many months trying to get Selenium working on Cordova-Android, I
gave up on it and wrote the Purity Class, which basically just
simulates touch events on
However, It's expensive to clone down the
repository just to check if the plugin works or not.
Good point Anis, it would be expensive to clone down a plugin simply to disc
I believe we should store some sort of mapping on our discovery server.
Such as:
{
cordova_version:
For those unaware, cordova-plugman [1] is a tool under active development
that will be responsible for all the plugin things.
Braden, Anis and I are actively working on getting this tool to a working
state, after which we will more completely integrate with cordova-cli.
Braden is currently
Bringing this up once more, hopefully the last time :)
TL;DR: the behavior and naming of the platform-level scripts are still not
100% lined up. I'd like to fix this and agree with you all on some of the
finer points surrounding this issue.
Benn Mapes, an intern at Adobe, has been working on
Ya braden put that huge thread on the list w/ the docs..
On Tue, Mar 19, 2013 at 3:22 PM, Filip Maj f...@adobe.com wrote:
Haha have we even brought back the new method to the list since the F2F?
On 3/19/13 3:21 PM, Brian LeRoux b...@brian.io wrote:
Yes, lets give this new method a go.
On
I'm a little confused. Would we not specify the plugin version in the
config.xml?? Plugins that get published most certainly need to be
versioned on the discovery server side too of course..
On Tue, Mar 19, 2013 at 1:03 PM, Filip Maj f...@adobe.com wrote:
What Michael says seems to make the most
I just restarted it.
I will post the creds to the private list in case this happens in the
future. We also have the option of having a VM hosted on apache infra that
we can set up a similar server for. It's still on my todo list but it's
dropped down in priority a lot, in case someone else wants
Thanks Fil.
Now getting mobile-spec filetransfer errors when there were none before (at
2.5.0 release). Wondering if anything changed on the scripts? I'll login
and see if nodejitsu has logs...
On Tue, Mar 19, 2013 at 3:59 PM, Filip Maj f...@adobe.com wrote:
I just restarted it.
I will post
I would like to see Ripple support completely replace the cordova server
command - they both do the same thing but Ripple is better tailored at
doing the server+emulation job.
On 3/9/13 12:08 PM, Brian LeRoux b...@brian.io wrote:
Yes, this is awesome, think a Ripple command is good while we suss
That code has been crashing on nodejitsu, not sure why. I think I might
need to upgrade node to 0.6.
It's also deployed to http://cordova-filetransfer.herokuapp.com/ as an
alternate.
On Tue, Mar 19, 2013 at 7:09 PM, Shazron shaz...@gmail.com wrote:
Thanks Fil.
Now getting mobile-spec
Errors in the upload script, no tmpDir:
-
info Tue, 19 Mar 2013 23:08:36 GMT 10.112.36.46 GET /favicon.ico 404
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.22 (KHTML,
like Gecko) Chrome/25.0.1364.172 Safari/537.22
info Tue, 19 Mar 2013 23:08:36 GMT 10.112.36.46 GET /upload
We should move the file transfer server code over to a branch on labs for
now, so we can all fix stuff easily.
On 3/19/13 4:15 PM, Don Coleman don.cole...@gmail.com wrote:
That code has been crashing on nodejitsu, not sure why. I think I might
need to upgrade node to 0.6.
It's also deployed to
I'll add a pull request, and see if I can fix Shaz's error.
On Tue, Mar 19, 2013 at 7:22 PM, Filip Maj f...@adobe.com wrote:
We should move the file transfer server code over to a branch on labs for
now, so we can all fix stuff easily.
On 3/19/13 4:15 PM, Don Coleman don.cole...@gmail.com
I agree with your easy wins.
As for the 'emulate' command I don't think it should exist and should be
replaced with 'run'. I thought we agreed on it in a previous thread. I
believe the way Android does it is the way to go.
The issue is to get it to work on iOS with Fruitstrap. Obviously we can't
I would also like to see iOS's release script changed.
Currently (as Fil said below) it compiles with the profile set to Release.
However, since it is still building targeting x86 (i.e.: the iOS Sim, not a
device) it is inconsistent with say the Android release script that actually
gets you a
The easy thing to do is download fruitstrap at runtime in the iOS
implementation, just like android + blackberry do for commons-codec and
any other required libs that we can't ship with cordova.
I still see value in having an emulate command that will RUN an emulator.
I would like to hear more
+1
Ripple is all I use `cordova serve` for anyway :)
On 20/03/2013, at 10:14 AM, Filip Maj f...@adobe.com wrote:
I would like to see Ripple support completely replace the cordova server
command - they both do the same thing but Ripple is better tailored at
doing the server+emulation job.
I agree with Anis, and your easy wins Fil!
emulate is confusing, unless emulate is 'ripple only!'
I think run should take a parameter which specifies where it should run,
defaulting to an attached device perhaps.
The cordova-deploy tool for Windows Phone 8 and Windows Phone 7 ( same API,
I agree with the BlackBerry scripts must do. Most of the BlackBerry stuff
should be pretty simple. If you took all the existing ant commands and
what's in the cordova scripts already, you're most of the way there.
However, I'm not sure what log would look like. I think there's a way to
ssh your
We will try to provide relevant stats on platform adoption as we are able. I am
anxiously awaiting that information myself. ;)
While lacking this information, I still feel that BBOS will be with us for a
deal of time, particularly in the enterprise where we are seeing a significant
trend
Shazron,
I updated the code and redeployed to nodejitsu
Fil,
I added the code to a fork. https://github.com/don/cordova-labs
Should I issue the pull request against master or should someone create a
'cordova-filetransfer' branch first?
On Tue, Mar 19, 2013 at 7:23 PM, Don Coleman
Thanks Don! I'll re-test tomorrow.
I might want to add scripts to test basic-auth later...
On Tue, Mar 19, 2013 at 8:03 PM, Don Coleman don.cole...@gmail.com wrote:
Shazron,
I updated the code and redeployed to nodejitsu
Fil,
I added the code to a fork.
Hi,
I could offer to start helping on the Windows Phone side of things.
P.S: This is my first email to the group, and I think I should introduce myself
- I am Parashuram, working for Microsoft Open Technologies Inc.
-Original Message-
From: Filip Maj [mailto:f...@adobe.com]
Sent:
35 matches
Mail list logo
