Well in that case I would recommend just calling the tool with the
specifications that you want. That way you would get the desired behavior.
The WARNING message gives you all the flags you didn't specify so if it's
not doing what you want, just run it again and specify what you want.
For new user
On Tue, Apr 9, 2013 at 2:44 PM, Benn Mapes wrote:
> It wouldn't be hard to error out instead of giving a warning message about
> what the tool is doing BUT I think it would be less frustrating for users
> of the tool if it just did what they were trying to do and used defaults
> for the things th
For windows phone I just have a deploy.js (jscript) that handles all of the
run and install commands.
Usage: [ --device | --emulator | --target= ] [ --debug | --release |
--nobuild ]
In the case that just `run` is called, the script will follow the `run`
specification as documented in the wiki (ex
Filed the INFRA issue: https://issues.apache.org/jira/browse/INFRA-6131
On Tue, Apr 9, 2013 at 10:58 AM, Shazron wrote:
> Thanks Jukka,
> I can file the issue, following the template. I suppose I can request to
> set myself as the initial admin as well.
>
>
> On Tue, Apr 9, 2013 at 1:37 AM, Juk
If there is any chance of mutual exclusivity, an error should be raised.
Otherwise the user has no idea which one happened. For building, I could see
doing both the debug and release version. But for deploying/running, I would
argue the intent is for only one at a time? (At least to me.)
_
I can't say I have strong feelings one way or the other.
I will say that having config.xml inside www *does* feel odd. So I'd be all for
moving it to the project's root directory (but that breaks spec. Is that good?
Bad?). Which is a breaking change, and so we'd still have to deal with older
p
+1 to the sanity plea of devgeek Tommy
Also, if it didn't happen on this list,
'Consensus' should always be tracked back to a thread here, regardless of
meetings, hangouts, irc, bbs, ...
@purplecabbage
risingj.com
On Tue, Apr 9, 2013 at 1:48 PM, tommy-carlos Williams wrote:
> Sorry, bu
Sorry, but as someone that helps users everyday, the almost "it's alpha, they
shoulda seen it coming" tone of this is a bit upsetting.
It reminds me of before the deprecation policy, etc when PhoneGap would
completely break everything whenever a new version came out.
I feel like we have come
Or it can just fail and ask users to build with the appropriate flag first.
I mean that is if we're following the 'one script does only one thing' idea.
On Tue, Apr 9, 2013 at 12:54 PM, Michael Brooks wrote:
> >
> > Augh! This actually made it past the mailing list. :(
>
> ...
>
> > +1 for the
I did think about this in the back of my mind when moving the config.xml. I
don't think bending this spec and letting the paths in config.xml continue
to be relative to www/ is that terrible. We break the Widget spec in a
quite a number of other ways anyway.
It would be a tiny change to put it bac
I'm still not sold on the new directory structure, but I would need to
review the previous thread on why we are interested in adopting it.
A minor concern on my part is the placement of `config.xml`.
The path to `index.html` must be referenced relative to `config.xml` [1].
Since `config.xml` is o
>
> Augh! This actually made it past the mailing list. :(
...
> +1 for the dislike :P but users will tell us if they like having 12 scripts
> laying around.
They are only assigned issues. If you guys have concerns, bring them up.
There is little point in committing to work if it isn't valuable
That's now how I recalled the discussion. It certainly wasn't clear-cut,
but I thought the conclusion was that this was fine.
Well, then this is now a discussion thread. What are the counterarguments?
Braden
On Tue, Apr 9, 2013 at 2:49 PM, Brian LeRoux wrote:
> :(
>
> We never had full consen
:(
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?
+1 for the dislike :P but users will tell us if they like having 12 scripts
laying around.
On Tue, Apr 9, 2013 at 11:38 AM, Joe Bowser wrote:
> Augh! This actually made it past the mailing list. :(
>
> I hate this idea for the emulators and devices, because this is a set
> of extremely complex
Augh! This actually made it past the mailing list. :(
I hate this idea for the emulators and devices, because this is a set
of extremely complex script that has next to zero payoff for our
users. I really wish I paid more attention to this thread earlier on,
because I really don't like these scri
Sounds good to me.
The lack of dots in the js-module name is a new restriction you'll have to
write code to defend against, but I would be surprised to see any existing
plugins violate it.
Braden
On Tue, Apr 9, 2013 at 2:07 PM, Jeffrey Heifetz wrote:
> I know at some point we spoke about modif
I know at some point we spoke about modifying require to allow relative paths
within a module and I'm wondering if this is still something we're interested
in doing and if so what a reasonable spec for doing so would be.
In the current plugin spec [1], under the JS module tag, we define a module
Thanks Jukka,
I can file the issue, following the template. I suppose I can request to
set myself as the initial admin as well.
On Tue, Apr 9, 2013 at 1:37 AM, Jukka Zitting wrote:
> Hi,
>
> On Mon, Apr 8, 2013 at 6:18 PM, Shazron wrote:
> > +1 I love this - how do we get it set up?
>
> See htt
We have raw sockets support implemented in the Chrome Apps layer[1], for
the chrome.socket API[2]. It should be relatively easy to allow both APIs
to call the same native code.
Braden
[1]
https://github.com/MobileChromeApps/chrome-cordova/tree/master/plugins/socket
[2] http://developer.chrome.com
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 we can reference those guides in
the CLI's readme? Just thinking out loud.
[1] http://npmjs.org/pack
This mailing list post is, or will shortly be, indexed by Google and
others. Any newcomers will see the new docs and create new projects.
As I mentioned on IRC, existing users are either accepting or ignoring the
"alpha" warnings that this software is new and under heavy development, and
if they
Day one of three days of meetings. I'll summarize what was discussed and
how Cordova fits in. As always if anyone here has anything they would like
me to raise specifically with the group let me know.
For reference the agenda is here:
http://www.w3.org/wiki/System_Applications:_1st_F2F_Meeting_Age
How will we communicate this change to our existing users?
On 4/9/13 5:22 PM, "Braden Shepherdson" wrote:
>I've just pushed a change to the future branch that changes the directory
>structure to:
>
>app/
>merges/
>android/
>ios/
>www/
>config.xml
>
>As was discussed a
I've just pushed a change to the future branch that changes the directory
structure to:
app/
merges/
android/
ios/
www/
config.xml
As was discussed at our video conference meeting a couple of weeks ago,
this has a number of advantages:
- config.xml is no longer in the
Maybe eventually the ci dashboard? But one thing at a time ;)
On 4/9/13 5:04 PM, "Don Coleman" wrote:
>Is there someone specific in INFRA to contact or just email
>infrastructure@apache?
>
>Do we have other stuff to run on this VM or just the server for
>file-transfer tests?
>
>
>On Tue, Apr 9,
Is there someone specific in INFRA to contact or just email
infrastructure@apache?
Do we have other stuff to run on this VM or just the server for
file-transfer tests?
On Tue, Apr 9, 2013 at 4:32 AM, Filip Maj wrote:
> Anyone wanna volunteer to talk to INFRA about setting up a VM for our
> tes
FYI issues for all of these scripts have been filed.
On 3/28/13 1:31 PM, "Michael Brooks" wrote:
>Fil, great work on the wiki document. Below are some feedback points.
>
>
>> `build`
>
>...
>
>What happens when a user specifies both --debug and --release?
>
>
>I'm happy as long as we decide on w
Hey Gorkem,
There is a bunch of housework to do around merging the PR. Thank you for
providing two implementations, but we have to be sure that all other
platforms at least have issues filed for following support.
I am currently attending a W3C meeting and don't have much time this week,
but I ha
Hi,
On Mon, Apr 8, 2013 at 6:18 PM, Shazron wrote:
> +1 I love this - how do we get it set up?
See https://issues.apache.org/jira/browse/INFRA-4742 for an example of
how we did this for Jackrabbit.
BR,
Jukka Zitting
Anyone wanna volunteer to talk to INFRA about setting up a VM for our
testing purposes? This way we can have this server running on apache infra
that all of our committers can access and tweak and fix etc.
http://apache.org/dev/freebsd-jails
On 4/8/13 8:54 PM, "Don Coleman" wrote:
>I restarted
Definitely, I am tired of the spam! +1
On 4/8/13 7:15 PM, "Jesse MacFadyen" wrote:
>+1, great idea.
>
>Cheers,
> Jesse
>
>Sent from my iPhone5
>
>On 2013-04-08, at 8:19 AM, Shazron wrote:
>
>+1 I love this - how do we get it set up?
>
>
>On Mon, Apr 8, 2013 at 5:03 AM, Simon MacDonald
>wrote:
32 matches
Mail list logo
