No, it's not. I just didn't know you had already created one. I closed the
issue.
On Wed, Oct 17, 2012 at 5:23 PM, Andrew Grieve wrote:
> :) I guess my suggestion to move further discussion to
> https://issues.apache.org/jira/browse/CB-1668 is a no. Anis - is the bug
> you created any different?
:) I guess my suggestion to move further discussion to
https://issues.apache.org/jira/browse/CB-1668 is a no. Anis - is the bug
you created any different? Do you want to make it about deprecating the old
scripts?
On Wed, Oct 17, 2012 at 7:50 PM, Filip Maj wrote:
> Totally in favor of these chan
Totally in favor of these changes!
How would we go about documenting these changes? Just drop them in for
2.3? Blog post? Thoughts?
On 10/17/12 3:14 PM, "Anis KADRI" wrote:
>On Wed, Oct 17, 2012 at 10:37 AM, Andrew Grieve
>wrote:
>
>> I don't think we should change them for 2.2, and instead tak
On Wed, Oct 17, 2012 at 10:37 AM, Andrew Grieve wrote:
> I don't think we should change them for 2.2, and instead take some time for
> 2.3 to get them exactly how we want them, and consist across platforms.
>
Agreed
>
> I think keeping the existing scrips as-is for a deprecation period would
>
I don't think we should change them for 2.2, and instead take some time for
2.3 to get them exactly how we want them, and consist across platforms.
I think keeping the existing scrips as-is for a deprecation period would
cause more confusion than good.
On Wed, Oct 17, 2012 at 12:01 PM, Anis KADR
Yes, I think so.
On Tue, Oct 16, 2012 at 7:20 PM, Filip Maj wrote:
> Dully noted for the cli :)
>
> I'll have the cli reflect the command changes as well.
>
> Should there be any level of "deprecation" for this? I.e. Keep the old
> scripts around for 2.2 and then remove/rename as necessary compl
Dully noted for the cli :)
I'll have the cli reflect the command changes as well.
Should there be any level of "deprecation" for this? I.e. Keep the old
scripts around for 2.2 and then remove/rename as necessary completely for
2.3?
On 10/16/12 11:39 AM, "Brian LeRoux" wrote:
>ya 2.3 for sure -
ya 2.3 for sure --- I imagine this will bust up cordova-cli a little
On Tue, Oct 16, 2012 at 11:19 AM, Anis KADRI wrote:
> Yes I like that much better. Should we target those changes for 2.2 or 2.3
> ? I am thinking 2.3. It will give us sometime to update the docs etc…
>
> On Tue, Oct 16, 2012 at
Yes I like that much better. Should we target those changes for 2.2 or 2.3
? I am thinking 2.3. It will give us sometime to update the docs etc…
On Tue, Oct 16, 2012 at 10:32 AM, Brian LeRoux wrote:
> > ./cordova/BOOM is what you want. Why is it called like that and why there
> > is no such thin
> ./cordova/BOOM is what you want. Why is it called like that and why there
> is no such thing on iOS ? I don't know…
Heh. I did that as a joke for my 'Steve Jobs' demo. BOOM there's your app.
> I am not a fan of "debug" to run on a device though. Can there be a better
> word ?
cordova/deploy?
On Mon, Oct 15, 2012 at 5:43 PM, Andrew Grieve wrote:
>
> on Android - why not build from emulate? Is there a way to launch the app
> via adb (probably there is).
>
./cordova/BOOM is what you want. Why is it called like that and why there
is no such thing on iOS ? I don't know…
> on both platfo
I agree with Brian and Patrick suggestions, it make sense and makes things
less confusing.
On 10/16/12 10:06 AM, "Patrick Mueller" wrote:
>Perhaps
>the job of a "clean" script, or something.
+1
On 10/16/12 3:11 AM, "Brian LeRoux" wrote:
>The orig scripts did have some symmetry. Change happe
Ya, I have SO many problems with Xcode, I tend to live in a "recompile the
universe" world, when I'm "scripting" builds, just to be safe. The extra
compile time is slightly painful, not enough for me to expend extra effort
to alleviate the pain tho. The most recent Xcode's do seem to be better
ab
> on iOS - why do a clean build instead of a regular build?
This was because in some cases an updated file was not copied over, or
a built app still had an older file that was removed from the project.
An edge case to be sure, but if there was a script that referred to
the old file still, it might
The orig scripts did have some symmetry. Change happens. =)
My ideal for each mobile os platforms:
- cordova/build: just compiles the app
- cordova/log: attached a logger to stdout for console.log messages
- corodova/emulate: compiles, then launches in platform emulator (and
attaches logger)
- co
Many questions around what these are supposed to do.
The current state:
iOS:
cordova/debug: Does a clean build in debug mode
cordova/emulate: Does a build if the app does not exist, but doesn't
attempt to build if it's there but stale. Runs the app in the simulator via
ios-sim
Android:
cordova/de
16 matches
Mail list logo
