at 11:41 AM, Brian LeRoux b...@brian.io
wrote:
Sounds good. FTR we did it for issue tracking not
arbitrarily.
Having
a stamp at the top of the file fulfills the same end.
On Tue, Apr 30, 2013 at 11:31 AM, Filip Maj f...@adobe.com
wrote:
If I recall correctly the original reason was because
Ultimately its up to us how we want to run with it. Far prefer lazy
consensus to voting.
On Wed, May 1, 2013 at 3:15 PM, Andrew Grieve agri...@chromium.org wrote:
Even in the pre-updated release steps, it explicitly says we need a vote
and refers to this apache way doc:
to change the release process to include an
official vote, Andrew, then we should start a vote on the private list,
I.e. Vote-to-change-the-process kind of vote.
On 5/1/13 3:37 PM, Brian LeRoux b...@brian.io wrote:
Ultimately its up to us how we want to run with it. Far prefer lazy
consensus
Sounds good. FTR we did it for issue tracking not arbitrarily. Having
a stamp at the top of the file fulfills the same end.
On Tue, Apr 30, 2013 at 11:31 AM, Filip Maj f...@adobe.com wrote:
If I recall correctly the original reason was because putting the version
in after the lib name in the JS
Main reason was to vendor in the scripts with the version of the src
they would operate on.
On Mon, Apr 29, 2013 at 11:31 AM, Shazron shaz...@gmail.com wrote:
*over-write
(oops on the oop)
On Mon, Apr 29, 2013 at 11:15 AM, Shazron shaz...@gmail.com wrote:
I think the main purpose of the
YES
On Thu, Apr 25, 2013 at 2:05 PM, Joe Bowser bows...@gmail.com wrote:
Should we fire up the script and create the tickets for tagging today?
On Thu, Apr 25, 2013 at 12:01 PM, Jesse purplecabb...@gmail.com wrote:
How about we let it sit, and plan for 2.7.0 release on Monday?
Added myself. Could be promising.
On Wed, Apr 24, 2013 at 7:35 AM, Andrew Grieve agri...@chromium.org wrote:
https://issues.apache.org/jira/browse/INFRA-5889
We have cordova repos for cordova-a* - cordova-ios
This includes cordova-app-harness, cordova-android, cordova-cli,
cordova-ios.
I plan to be there!
On Wed, Apr 24, 2013 at 8:37 AM, Ken Wallis kwal...@blackberry.com wrote:
Thanks very much for this Paul, I will be attending. Any other Cordova
people going, perhaps an informal gathering can be arranged?
--
Ken Wallis
Product Manager – WebWorks
BlackBerry
There is a very good reason that we want the plugins to be discreet,
atomic, almost userspace, artifacts vs the core cordova distribution
which should just be bridge and supporting code.
On Mon, Apr 22, 2013 at 7:50 AM, Anis KADRI anis.ka...@gmail.com wrote:
I can only see one. Does the apache
The first step will be to lazy load the locked in version.
Ok. So we are version locked. But MINOR has different meaning from a
native project to the CLI tools.
The much longer goal would be to discuss and architect the grunt inspired
approach. However, with how the CLI is structured, it
+major.minor.patch
Example:
1.0.12+2.7.0 === npm module 1.0.12 and Cordova framework 2.7.0
On Fri, Apr 19, 2013 at 3:47 PM, Brian LeRoux b...@brian.io wrote:
Cordova CLI has a version that is independent of the Cordova releases.
(Once we decouple the creating of projects from version
I don't get it. Why not independently version?
(I recognize we version lock currently.)
On Fri, Apr 19, 2013 at 2:19 PM, Filip Maj f...@adobe.com wrote:
Rockin, love it
On 4/19/13 2:17 PM, Michael Brooks mich...@michaelbrooks.ca wrote:
Hey all,
I'm planning to change the way we version the
and as a consumable npm module.
On Fri, Apr 19, 2013 at 3:28 PM, Brian LeRoux b...@brian.io wrote:
I don't get it. Why not independently version?
(I recognize we version lock currently.)
On Fri, Apr 19, 2013 at 2:19 PM, Filip Maj f...@adobe.com wrote:
Rockin, love it
On 4/19/13 2:17 PM, Michael
Congratulations Ian!
On Thu, Apr 18, 2013 at 10:02 AM, Filip Maj f...@adobe.com wrote:
Welcome and looking forward to working with you!
On 4/18/13 7:43 AM, James Jong wjamesj...@gmail.com wrote:
Welcome Ian!
-James Jong
On Apr 18, 2013, at 10:20 AM, Andrew Grieve agri...@chromium.org
Agree on 2.7 and love the idea for a regression label. Would be a good
'first bug' for folks new to the project to help cut support releases.
Here's a battery of queries, how do we decide we need a MINOR point
release? can it be just one issue cherry picked? does it need to be fully
packaged or
I really like this spec but suspect we want to hold off until post 3.x
to be safe.
On Thu, Apr 18, 2013 at 2:20 PM, Filip Maj f...@adobe.com wrote:
TL;DR this is a way to solve the how to reference in-app package contents
in a platform-agnostic fashion
Relevant to us because it would solve a
Braden: you thinking that the config is canonical and then prepare quietly
does the right thing based on that?
(Agree less steps is exactly what we're going for here.)
On Wed, Apr 17, 2013 at 10:16 AM, Braden Shepherdson bra...@chromium.orgwrote:
Re: --install calling --prepare: no. It could,
This is a good point. Might be better to warn about unused permissions.
(And offer an audit command for cleanup/release purposes.)
On Wed, Apr 17, 2013 at 3:13 PM, Jesse purplecabb...@gmail.com wrote:
I think we do have consensus on permission, you can ignore the entire
discussion of
It would be ideal to see 2.7 ship before the month is out for sure.
On Tue, Apr 16, 2013 at 7:41 AM, Joe Bowser bows...@gmail.com wrote:
I think that this would be a good thing. It'd be nice to get a
released lined up for Conf-Month! (Adobe Max, Google IO, JSConf, etc).
On Tue, Apr 16,
On Mon, Apr 15, 2013 at 1:10 PM, Brian LeRoux b...@brian.io wrote:
My only feedback would be to see if you can get it working w/ Plugman!
[1]
(And if not lets file issues [2] to ensure it can.)
[1] https://github.com/apache/cordova-plugman
[2] http://issues.cordova.io
On Mon
sgtm
On Tue, Apr 16, 2013 at 10:58 AM, Michal Mocny mmo...@google.com wrote:
I think we plan to default to ARC support for iOS projects post 3.0.
As a first transition I'm hoping to add a --arc option to the create script
to use optionally starting today, since its necessary for bleeding
ok, cool
On Tue, Apr 16, 2013 at 1:42 AM, Jukka Zitting jukka.zitt...@gmail.comwrote:
Hi,
On Tue, Apr 16, 2013 at 12:51 AM, Brian LeRoux b...@brian.io wrote:
Not totally sure why but I'm getting a message that we have a report for
April (even though I don't think we do b/c we should
, 2013, at 2:06 PM, Brian LeRoux b...@brian.io wrote:
sgtm
On Tue, Apr 16, 2013 at 10:58 AM, Michal Mocny mmo...@google.com
wrote:
I think we plan to default to ARC support for iOS projects post 3.0.
As a first transition I'm hoping to add a --arc option to the create
script
to use
I'm down for this. (Given no plugins really work w/ it yet anyhow.)
On Tue, Apr 16, 2013 at 11:28 AM, Michal Mocny mmo...@chromium.org wrote:
Should I also change cordova-cli in future to enable by default?
On Tue, Apr 16, 2013 at 2:23 PM, Brian LeRoux b...@brian.io wrote:
plugin compat
brianleroux
On Tue, Apr 16, 2013 at 2:42 PM, Filip Maj f...@adobe.com wrote:
Yep works! Thanks shaz
also: no more super annoying what city was apache con 2004 held in?
questions. Double-win.
On 4/16/13 2:39 PM, Shazron shaz...@gmail.com wrote:
Ok, I've added
- FilMaj
- AndrewGrieve
-
ya no kidding
On Tue, Apr 16, 2013 at 2:46 PM, Anis KADRI anis.ka...@gmail.com wrote:
That's cool! I was getting tired of googling every apache conference since
1970.
On Tue, Apr 16, 2013 at 2:42 PM, Filip Maj f...@adobe.com wrote:
Yep works! Thanks shaz
also: no more super annoying
Yep. Could be as simple as a hard reset to the latest SHA from GitHub if
the above is fulfilled. (Maybe start it in a new branch on Apache Git for
us to review in the meantime.)
On Mon, Apr 15, 2013 at 10:04 AM, Filip Maj f...@adobe.com wrote:
WRT to BlackBerry since node is already required,
Not totally sure why but I'm getting a message that we have a report for
April (even though I don't think we do b/c we should be quarterly.)
Anyhow. Doesn't matter. I've been tracking stuff here. [1]
Let me know if there's anything of note to add.
[1]
I'd rather we did not go ahead w/ the new directory structure. It offers no
functional benefit, and comes at an upgrade cost for ppl using the CLI
tools today.
On Mon, Apr 15, 2013 at 12:46 PM, Andrew Grieve agri...@chromium.orgwrote:
Just catching up on the past week of emails and it's not
Lets give this a few days to make sure we're not about hurt anyone.
(I'm in favor of removing support.)
On Wed, Apr 10, 2013 at 12:03 PM, Michael Wolf michael.w...@cynergy.comwrote:
Fwiw I wasn't saying 2.3, but 2.2. The consideration of supporting 2.3
goes based on who your consumer base
I'd rather we saved this for a future refactoring. Bigger fish to fry.
On Wed, Apr 10, 2013 at 12:22 PM, Anis KADRI anis.ka...@gmail.com wrote:
I feel like I am going to be alone on this one again but as far as I am
concerned I don't like the idea of introducing a dependency.
I think too
We recently moved to * by default to ease common userland woe. I'd be in
favor of removal of whitelisting but I'm fairly certain that would be
a controversial position!
On Wed, Apr 10, 2013 at 11:38 AM, Kevin Hawkins
kevin.hawkins.cord...@gmail.com wrote:
Hey all,
Those of us who have been
:(
We never had full consensus to do this Braden.
On Tuesday, April 9, 2013, Filip Maj wrote:
For a couple months now the npm package has had about 1000 downloads per
month [1].
We do have upgrade guides in our docs for each version for each platform.
Maybe we could add a CLI section? Then
to do releases? E.g.
2.7 is missing two plugins since they were moved into different repos.
On Fri, Apr 5, 2013 at 4:20 PM, Brian LeRoux b...@brian.io wrote:
That synopsis on the wiki was super helpful Joe. I think we should stop
thinking we have to do EVERYTHING ALL AT ONCE. We do not need
Right on! Welcome Luke and Erik, great to have more firepower on Cordova. =)
On Fri, Apr 5, 2013 at 1:12 PM, James Jong wjamesj...@gmail.com wrote:
Great to have you onboard Luke and Erik. Welcome!
-James Jong
On Apr 5, 2013, at 4:08 PM, Ken Wallis kwal...@blackberry.com wrote:
Great
Agree w/ Anis. Just move what can be moved and file up tickets for
that which cannot be done in the immediate term / that is in the
'official' list of plugins.
On Wed, Apr 3, 2013 at 11:27 AM, Anis KADRI anis.ka...@gmail.com wrote:
I think a good first pass is to plugin-ize what is plugin-izable
:56 PM, Brian LeRoux b...@brian.io wrote:
cordova-app sounds good to me
On Thu, Mar 28, 2013 at 2:45 PM, Andrew Grieve agri...@chromium.org
wrote:
I don't think we need to decide on an App Store name yet. Repo name
sounds
good though.
On Thu, Mar 28, 2013 at 4:40 PM, Michael
Thanks so much and don't be stranger Markus! Let us know if ever you
need our help.
On Thu, Mar 28, 2013 at 8:38 AM, Lorin Beer lorin.beer@gmail.com wrote:
thanks for your hard work, and good luck in your future endeavours!
On Thu, Mar 28, 2013 at 7:30 AM, Anis KADRI anis.ka...@gmail.com
So, what would be better?
On Tuesday, March 26, 2013, Giorgio Natili wrote:
The naming convention seems confusing also to me especially on big
projects.
On 3/25/13 10:46 PM, Brian LeRoux b...@brian.io javascript:; wrote:
I'm apprehensive about returning to a naming convention. In a larger
working.
On Tue, Mar 26, 2013 at 12:18 AM, Brian LeRoux b...@brian.io wrote:
Hate to 'make work' but we might want to drop a README in them
explaining what is supposed to go there (maybe a link to plugman) and
the mailing list before we open those up to speculation.
On Mon, Mar 25, 2013
Jesse, while I respect our mutual disdain for the Bruins fan that is Mapes,
it would be more helpful for all of us to know those implications so we can
help while you're out!
On Tue, Mar 26, 2013 at 8:34 AM, Shirley Adams shirleya.fu...@gmail.comwrote:
[?]
On Tue, Mar 26, 2013 at 11:29 AM,
Looks great Andrew. I'd add Ripple and device mirroring as part of
this. (More than one device navigates in concert.)
What is this thing going to be called? cordova-app-harness sounds kinky.
On Mon, Mar 25, 2013 at 5:59 PM, Andrew Grieve agri...@chromium.org wrote:
Hey Michael (and anyone else
Unfortunate as we thought 2.6 was realistic a few weeks ago but I echo
the sentiment. Too soon! Going to kick up a fresh thread on JS.
On Mon, Mar 25, 2013 at 4:05 PM, Shazron shaz...@gmail.com wrote:
I don't think it should go in for 2.6.0 as well, for the already mentioned
reasons.
On Mon,
Steve has plugman working with devicemotion plugin. Happy days! Its
time he ripped the JS out of cordova-js and put it in the plugin. But
does plugman support js installation? What needs happening to make it
so?
, then we can advertise them and ask for help. The
folks skilled at doing the initial extraction are already here on the dev
mailing list.
So defer advertising the empty plugin repos until they aren't empty.
-- Marcel
On Mar 26, 2013, at 11:54 AM, Brian LeRoux b...@brian.io wrote:
I'm
\o/
On Tue, Mar 26, 2013 at 9:08 AM, Filip Maj f...@adobe.com wrote:
Just wanted to send out a quick congratulatory note to the public dev
list. We've voted in four new committers in the past week or two, I'm very
excited about this!
Don Coleman, Max Woghiren, James Jong, and Tommy
the Cordova framework
(which
they sort of are), then call it Cordova DX (DX is developer experience).
Michael
On Tue, Mar 26, 2013 at 9:06 AM, Brian LeRoux b...@brian.io wrote:
Looks great Andrew. I'd add Ripple and device mirroring as part of
this. (More than one device navigates in concert
...@adobe.com wrote:
Use the future branch of plugman. That's where braden is putting the
symbol mapping work into.
On 3/26/13 9:09 AM, Brian LeRoux b...@brian.io wrote:
Steve has plugman working with devicemotion plugin. Happy days! Its
time he ripped the JS out of cordova-js and put
cordova-kink
PROS:
would probably get lots of downloads in the app store
CONS:
would probably not get accepted into the app store
On Tue, Mar 26, 2013 at 10:03 AM, Michal Mocny mmo...@chromium.org wrote:
I like the kinky version.
On Tue, Mar 26, 2013 at 12:52 PM, Brian LeRoux b...@brian.io
.
Braden
On Mon, Mar 25, 2013 at 2:17 PM, Brian LeRoux b...@brian.io wrote:
While this might be our goal it is in no way true that ./platforms
ia
build artifact today or anytime soon.
On Mon, Mar 25, 2013 at 10:55 AM, Braden Shepherdson
bra...@chromium.org wrote
it could work and
have the global only responsible for creating dirs and setting up
package.json stuff etc...
+1 for looking into this.
On 23/03/2013, at 4:53, Brian LeRoux b...@brian.io wrote:
Right now the global executable is version locked to a Cordova
release. If you have
that today, but we decided not to try to
cherry-pick that change into 2.6.x.
It's harmless for the main function of cordova-js, but it means that the
future branch of the CLI tools won't work with the released 2.6.
Braden
On Tue, Mar 26, 2013 at 12:57 PM, Brian LeRoux b...@brian.io wrote
On Tue, Mar 26, 2013 at 12:31 PM, Braden Shepherdson
bra...@chromium.org
wrote:
Congratulations!
On Tue, Mar 26, 2013 at 12:27 PM, Brian LeRoux b...@brian.io wrote:
\o/
On Tue, Mar 26, 2013 at 9:08 AM, Filip Maj f...@adobe.com
wrote:
Just wanted
omg. yes!
cordova-webkeg
I can see the Yohei style app icon already..
On Tue, Mar 26, 2013 at 12:14 PM, Douglas Campos q...@qmx.me wrote:
On 26/03/2013, at 16:13, Filip Maj f...@adobe.com wrote:
My vote is for WebKeg
THIS
--
qmx
app distribution (such that say cordova create
path-to-app), we would need to support importing from an app folder (for
the two folder merges and www reason alone). Yet we currently plan to
unpack that app folder inside the workspace.
-Michal
On Sun, Mar 24, 2013 at 5:22 PM, Brian LeRoux b
(Btw this isn't a vote thread guys.)
On Mon, Mar 25, 2013 at 9:37 AM, Brian LeRoux b...@brian.io wrote:
So, what if you want to version the ./platorms folder? I don't like
it, but ppl will do.
On Mon, Mar 25, 2013 at 9:10 AM, James Jong wjamesj...@gmail.com wrote:
+1 for app folder
I think its useful for us to have the conversation, but lets not
forget that we're going to be moving to this plugin reality so what
gets supported and doesn't isn't as big of a deal.
On Mon, Mar 25, 2013 at 9:53 AM, Lorin Beer lorin.beer@gmail.com wrote:
hrm, that makes things trickier. Our
work fine.
Braden
On Mon, Mar 25, 2013 at 12:37 PM, Brian LeRoux b...@brian.io wrote:
(Btw this isn't a vote thread guys.)
On Mon, Mar 25, 2013 at 9:37 AM, Brian LeRoux b...@brian.io wrote:
So, what if you want to version the ./platorms folder? I don't like
it, but ppl will do
wanted to separate the permissions so that Cordova apps don't
ask for everything all the time, but only what they actually need.
-1 to installing all the core plugins by default, and to lockstep
versioning them to the tools.
On Fri, Mar 22, 2013 at 6:08 PM, Brian LeRoux b...@brian.io wrote
miscellany in the git repo won't be part of
the app.
On Mon, Mar 25, 2013 at 1:19 PM, Brian LeRoux b...@brian.io wrote:
Ok, let me try again. What is precisely problem we are solving by
changing the structure? To be clear, I'm not really against or for it.
I just don't understand why
of extra build
artifact cruft in your git repo, or your devs just have to know that
platforms/ and plugins/ are in .gitignore.
Braden
On Mon, Mar 25, 2013 at 1:45 PM, Brian LeRoux b...@brian.io wrote:
But, if you go up one level, the same is true w/ the current
structure. Its just
I'm going to guess 'too soon' given there are no platform scripts as
of yet but leave that to Herm to qualify.
On Mon, Mar 25, 2013 at 11:30 AM, Filip Maj f...@adobe.com wrote:
Where does firefox os fit in in here?
On 3/24/13 8:21 PM, Brian LeRoux b...@brian.io wrote:
Thanks Steve!
On Sunday
plugins separated.
I know PhoneGap Day is in July, and I agree 3.0 for PGD is a great goal,
but a major version number bump shouldn't indicate that time has elapsed.
There should be some excitement behind it! :)
On Mon, Mar 25, 2013 at 1:54 PM, Brian LeRoux b...@brian.io wrote:
No no. You must
Check out the other platforms. Things have standardized on
./bin/create and in a generated project ./cordova/*.
On Mon, Mar 25, 2013 at 1:38 PM, Benn Mapes benn.ma...@gmail.com wrote:
Right now most of the scripts for windows phone except create are in
/tooling/scripts/
and there are duplicate
I'm apprehensive about returning to a naming convention. In a larger
app this would lead to a very cluttered dir.
The other consideration for ./merges are other assets: icons, and
splashscreens. (Which would then require 2x or something for
retina/hdpi situations.)
On Mon, Mar 25, 2013 at 2:34
Hate to 'make work' but we might want to drop a README in them
explaining what is supposed to go there (maybe a link to plugman) and
the mailing list before we open those up to speculation.
On Mon, Mar 25, 2013 at 7:21 PM, Michael Brooks
mich...@michaelbrooks.ca wrote:
Would it make sense to
for it to be
in the www folder so that the www folder can go straight to
build.phonegap.com.
On 23/03/2013, at 9:15 AM, Brian LeRoux b...@brian.io wrote:
I'm ok with ./merges at the same level as ./www but the config.xml
inside of ./www bugs me too. I think having a root level ./www just
\o/
On Fri, Mar 22, 2013 at 8:12 PM, Anis KADRI anis.ka...@gmail.com wrote:
Cool! Now we need to populate them at least as fast as it took to get them
created :-)
On Fri, Mar 22, 2013 at 5:54 PM, Andrew Grieve agri...@google.com wrote:
https://issues.apache.org/jira/browse/INFRA-5839
, Mar 22, 2013 at 10:33 AM, Jeffrey Heifetz
jheif...@blackberry.comwrote:
+1
On 13-03-22 1:32 PM, Anis KADRI anis.ka...@gmail.com wrote:
+1
On Fri, Mar 22, 2013 at 10:29 AM, Brian LeRoux b...@brian.io wrote:
Propose we add ./bin/check_requirements to each platforms in 2.7
Thanks Steve!
On Sunday, March 24, 2013, Steven Gill wrote:
Yup
On Sun, Mar 24, 2013 at 2:23 PM, Brian LeRoux b...@brian.io wrote:
Good enough for me. Steve you got that?
On Sat, Mar 23, 2013 at 9:54 PM, Jesse MacFadyen
purplecabb...@gmail.com wrote:
+1 for windows 8
Propose we add ./bin/check_requirements to each platforms in 2.7
timeframe so as to remove that logic from the cordova-cli tool.
Right now the cordova-cli has a lot of logic looking at parsing the
config.xml and some stuff is existing in the platforms. This is more
of a discussion thread for that. I don't have any concrete to talk
about here but Fil can elaborate.
Right now we put the release of Cordova into the npm package for
cordova-cli and we version lock the two. (Codova/CLI 2.5.x ===
Cordova/Platform 2.5.latest).
We did this because:
- has to work offline
- cannot have a Git dep to do development
- issue tracking locked to the real version of
Right now the global executable is version locked to a Cordova
release. If you have a project running 2.5 you are required to have
Cordova/CLI 2.5. If you need to then work in Cordova 2.4 you need to
downgrade (not really but you would to be safe).
In Grunt .4 the global executable is dumb. It
I think this bleeds back into other discussions. It was mentioned in
the call earlier. I think some tacit agreement that ./serve goes away
and Ripple is the default ./emulate command. But lets discuss. (Just
this. Lets keep thread focused.)
...
Thoughts? I'm down. But maybe post 3.x since neither is a real issue atm.
None have support currently in the CLI tools.
- Herm is pursuing platform level scripts so support for FxOS can happen.
- Mapes is doing the same in Windows land.
Both cases we could use some help. If any on this list care about
those platforms and would like to pitch in this is the thread to
I am sure we all agree to this. Want to get a sense of how it will
happen. Anis you mentioned you need Braden to commit the JS stuff
first?
A plugin should specify the Cordova versions it supports too.
On Fri, Mar 22, 2013 at 10:59 AM, Brian LeRoux b...@brian.io wrote:
I am sure we all agree to this. Want to get a sense of how it will
happen. Anis you mentioned you need Braden to commit the JS stuff
first?
Would have the benefit of enabling a plugin, and plugin-test existence
in a single repo. Consolidates a lot of tooling. Lets discuss more
herein
22, 2013 at 1:56 PM, Brian LeRoux b...@brian.io wrote:
...
propose a flag like cordova platform add android
--target=../../cordova-android where that local directory can have
whatever locally patched code I want.
Braden
On Fri, Mar 22, 2013 at 1:37 PM, Brian LeRoux b...@brian.io wrote:
Right now we put the release of Cordova into the npm package
if we don't have the build dependencies.
Emulate would just default to ripple so is still usable if we can't
build/deploy
Sent from my iPhone
On 2013-03-22, at 1:55 PM, Brian LeRoux b...@brian.io wrote:
I think this bleeds back into other discussions. It was mentioned in
the call earlier
I'm into it.
On Fri, Mar 22, 2013 at 11:11 AM, Max Woghiren m...@chromium.org wrote:
The main technical ask here is the ability to specify a plugin as { git
repo, commit hash, subdirectory } instead of just { git repo, commit hash }.
On Fri, Mar 22, 2013 at 2:05 PM, Brian LeRoux b...@brian.io
that we also include some set of plugins inside of cordova-cli?
On Fri, Mar 22, 2013 at 2:13 PM, Brian LeRoux b...@brian.io wrote:
It big. Certainly would be more efficient to lazy load, and cache so
offline works.
On Fri, Mar 22, 2013 at 11:04 AM, Gord Tanner gtan...@gmail.com wrote
on every prepare. That's not currently
true
for native code, but it is for the rest.
Since we're doing that, we need the full content of the plugins to stick
around. Is there a problem with keeping this around?
Braden
On Fri, Mar 22, 2013 at 2:12 PM, Brian LeRoux b...@brian.io wrote:
Cool
a
list of compatible cordova versions, right?
Then the universe can manage a reverse mapping if it wants fast access.
-Michal
On Fri, Mar 22, 2013 at 2:00 PM, Brian LeRoux b...@brian.io wrote:
A plugin should specify the Cordova versions it supports too.
On Fri, Mar 22, 2013 at 10:59 AM
Currently a release consists of some boilerplate:
DISCLAIMER
LICENSE
NOTICE
README.md
changelog
And the guts:
cordova-android.zip
cordova-app-hello-world.zip
cordova-bada-wac.zip
cordova-bada.zip
cordova-blackberry.zip
cordova-cli.zip
cordova-docs.zip
cordova-ios.zip
cordova-js.zip
at 2:15 PM, Brian LeRoux b...@brian.io wrote:
omg I just realized this would fulfill offline use case vs lazy
load
vendoring
caching could be a future thing
might be a really nice path
On Fri, Mar 22, 2013 at 11:06 AM, Gord Tanner gtan...@gmail.com
wrote
one (5 to 10 seconds) if multiple
emulators are running.
* Start emulator. If you have multiple ones set up (Android's case),
prompt, timeout and launch first one (5 to 10 seconds).
Yes/no/discuss. Let's try to get to a consensus :)
On 3/21/13 5:29 PM, Brian LeRoux b...@brian.io wrote:
I
Given that plugins will be independently versioned once they break off
I think it will be a whole new world for where we focus our efforts
next year. I suspect most of what you propose will be without
contention.
On Fri, Mar 22, 2013 at 2:54 PM, Joe Bowser bows...@gmail.com wrote:
Hey
I'm
?)
-Michal
On Fri, Mar 22, 2013 at 4:01 PM, Brian LeRoux b...@brian.io wrote:
Good question.
My intuition is saying for as long as 3.x is around we preload w/ core
plugins. We'll do as such w/ the PhoneGap distribution to minimize
pain. Once ppl are used to the tools they'll be asking
I'm ok with ./merges at the same level as ./www but the config.xml
inside of ./www bugs me too. I think having a root level ./www just
works well mentally in that its obvious whats there, what it does, and
who it effects. The ./merges folder is really just stuff that gets
added to ./www in the
will create issues for coho in regards to this.
-Steve
On Fri, Mar 22, 2013 at 2:35 PM, Filip Maj
f...@adobe.comjavascript:;
wrote:
+1
On 3/22/13 2:26 PM, Brian LeRoux b...@brian.io javascript:;
wrote:
Currently a release consists of some boilerplate
/cordova-docs/pull/24
https://github.com/apache/cordova-js/pull/21
https://github.com/apache/cordova-ios/pull/35
https://github.com/apache/cordova-android/pull/35
https://github.com/apache/cordova-mobile-spec/pull/13
-James Jong
On Mar 19, 2013, at 6:46 PM, Brian LeRoux b...@brian.io wrote:
Ya
like the idea of putting this doc into the docs.cordova.io docs?
Or do we prefer to keep contributor-related things in the wiki? If the
latter, it can wait, but if the former then I should probably commit it
very soon.
Braden
On Thu, Mar 21, 2013 at 1:58 PM, Brian LeRoux b...@brian.io wrote
Ya tend to agree w/ the workflows you describe Jesse. Not at the
exlusion of discreet scripts however. We probably should have small
focused scripts and then compose the workflow scripts from them.
(Making it easier to test and compose new scripts and tooling.)
On Thu, Mar 21, 2013 at 12:07 AM,
I think we can have our cake and eat it too. We should have four high
level commands. Those commands can shell to lower level discreetly
testable commands. The end user will never know the difference. The
developers win the tight abstraction we seek.
Make sense?
On Thu, Mar 21, 2013 at 2:55 PM,
stewarded?
Sent from my iPhone
On 2013-03-21, at 6:00 PM, Filip Maj f...@adobe.com wrote:
+1
On 3/21/13 2:12 PM, Shazron shaz...@gmail.com wrote:
+1
On Thu, Mar 21, 2013 at 1:46 PM, Michal Mocny mmo...@chromium.org wrote:
+1
On Thu, Mar 21, 2013 at 4:38 PM, Brian LeRoux b...@brian.io
801 - 900 of 1061 matches
Mail list logo
