I'm trying to not sound like a broken record but I still do not hear an
actual use cases that is unique to IndexedDB. I understand that you like
it, I do too, and the browsers will support it eventually in Cordova so
effort spent there is not really a demonstrable win (to me) unless I hear a
use ca
The key win I think is simply having a consistent implementation.
CanIUse reports that indexedDB is available on Android 4.4+ and every other
of our supported platforms, with a very notable exception of Mobile Safari.
Ultimately this is a plugin, and Parashuram is working on it, so I am sure
he wou
I've wanted to add Cordova plugin dependencies to the app's top-level
config.xml for a long time, but it's never reached the top of my
priorities. I think with that support, we can avoid checking in ./plugins/
and ./platforms altogether for 99% of app developers. If it doesn't solve
anyone's use ca
The unfortunate part is that Eclipse and Xcode are also (more or less) the
build systems for iOS and Android. You can build from CLI, and even deploy
from the CLI if the stars align and you have your ruby slippers on the
correct feet, but in practice most people are launching from IDEs. That
makes
I'm sorry, what problems do you really have with the CLI for
building/deploying? I have none nor see any issues that require slippers. ;)
When I train people about Cordova based dev I always teach them the CLI and
to use a text editor. Most are using Sublime (not Xcode) and many are
rolling into a
1) Wouldn't it make more sense to default to the root config.xml if both
are present? If you create a new project and import an old www project
using a new CLI (--source or --link), you would get both configuration
files (one at the root created by the template, and one inside your
imported www).
1) Good point. Makes sense to me.
2) I think this is a tougher call. In on context, it does make more sense
as "app.xml", since "config.xml" is the thing you're generating as an
output. OTOH, there are a lot of tutorials & blog posts that say "put FOO
in your config.xml", and so renaming it would
If we don't add a config.json by default, we need a new strategy for
looking up paths for the root.
I don't like naming the top-level config "config.xml", but after some
thoughts on it, I don't think we should rename it just right now. There
are a lot of changes that would need to go along with t
I'm glad to hear people are having success with IDE-less workflows. I'm a
vim guy through and through, and wish I didn't have to waste disk space or
memory on Xcode or Eclipse. I need them for native debugging, I suppose.
I have had a patchy history of trying to deploy to simulators and devices
us
ya agreed, we should aim to do something early Feb once everyone is back
into the the flow
On Mon, Jan 6, 2014 at 11:59 AM, Michal Mocny wrote:
> If we don't add a config.json by default, we need a new strategy for
> looking up paths for the root.
>
> I don't like naming the top-level config "c
We've quibbled over this before. Regardless of your preference or
philosophy, at least some users are choosing/expecting to use IDE's and
then complaining about it.
I'm all for removing the barriers to all-CLI all the time (I'm also a "vim
guy"), but these changes significantly appease confusion
After discussing this and reading the other thread (on config.json
movement), I agree this is not the time for the rename.
On Mon, Jan 6, 2014 at 2:58 PM, Andrew Grieve wrote:
> 1) Good point. Makes sense to me.
>
> 2) I think this is a tougher call. In on context, it does make more sense
> as
On Mon, Jan 6, 2014 at 12:03 PM, Braden Shepherdson wrote:
> I have had a patchy history of trying to deploy to simulators and devices
> using the CLI commands, but it may be something about my setup (eg. my HTC
> One frequently drops out of the ADB devices list even though it's still
> plugged in
(More OT: I've gone through my fourth damaged microUSB cable on this last
road trip. They bend so easily in the car.)
On Mon, Jan 6, 2014 at 3:17 PM, Joe Bowser wrote:
> On Mon, Jan 6, 2014 at 12:03 PM, Braden Shepherdson
> wrote:
> > I have had a patchy history of trying to deploy to simulat
Hello fellow Cordova Devs,
I have been using PhoneGap / Cordova for about the last few years and love
that the project is ever evolving. I would like to help contribute to the
Cordova project as well to help give back some of what was freely given to
myself.
Some of my hobbies include mobile deve
Welcome Josh!
On Mon, Jan 6, 2014 at 9:20 AM, Josh Bavari wrote:
> Hello fellow Cordova Devs,
>
> I have been using PhoneGap / Cordova for about the last few years and love
> that the project is ever evolving. I would like to help contribute to the
> Cordova project as well to help give back so
Right on, welcome to the fray Josh.
On Mon, Jan 6, 2014 at 3:31 PM, Anis KADRI wrote:
> Welcome Josh!
>
>
> On Mon, Jan 6, 2014 at 9:20 AM, Josh Bavari wrote:
>
> > Hello fellow Cordova Devs,
> >
> > I have been using PhoneGap / Cordova for about the last few years and
> love
> > that the proj
About plugin and platform version control.
I heard a lot about that, and confused why you think that everybody would
like to remove ./plugins and ./platforms folders from source control. I do
agree that this is most likely the case for the simple applications and for
the maybe 99% of current Cordov
Hi Andrey,
I have worked on two small, simple Cordova applications, but we still at times
had to modify platform specific code. Not much, but some (AppDelegate.m for
the iOS app, and the DroidGap subclass for Android--this is a 2.9.x project for
now).
Here's my solutions to your issues.
* if
Hi,
I'm hoping to get some help with the camera usage causing memory warnings
and an eventual crashing of the application.
I've filed a bug with details here:
https://issues.apache.org/jira/browse/CB-5732
Hey Andrey,
Much like you said 99% of the users will want to ignore platforms and
plugins from version control. Making this work properly would not stop
someone from including them if they wanted to. If your workflow is better
including those folders you would have no problem doing so.
Ideally th
Awesome! Welcome to the team!
On Mon, Jan 6, 2014 at 3:40 PM, Brian LeRoux wrote:
> Right on, welcome to the fray Josh.
>
>
> On Mon, Jan 6, 2014 at 3:31 PM, Anis KADRI wrote:
>
> > Welcome Josh!
> >
> >
> > On Mon, Jan 6, 2014 at 9:20 AM, Josh Bavari wrote:
> >
> > > Hello fellow Cordova Dev
22 matches
Mail list logo
