knows
>> of one.
>>
>> Sent from my BlackBerry 10 smartphone on the Rogers network.
>> From: Benn Mapes
>> Sent: Monday, August 26, 2013 5:53 PM
>> To: dev@cordova.apache.org
>> Reply To: dev@cordova.apache.org
>> Subject: Re: PROPOSAL: node.js all
gt; Sent from my BlackBerry 10 smartphone on the Rogers network.
> From: Benn Mapes
> Sent: Monday, August 26, 2013 5:53 PM
> To: dev@cordova.apache.org
> Reply To: dev@cordova.apache.org
> Subject: Re: PROPOSAL: node.js all the script things
>
>
> Ok, I'm pushing up these
v@cordova.apache.org
Reply To: dev@cordova.apache.org
Subject: Re: PROPOSAL: node.js all the script things
Ok, I'm pushing up these changes to the android master branch.
The only problem I see arising is the fact that you need a 'node' prefix
before any of the commands on windows.
Ok, I'm pushing up these changes to the android master branch.
The only problem I see arising is the fact that you need a 'node' prefix
before any of the commands on windows. This will break the CLI for android
on windows (maybe plugman too), unless we update the tooling to require the
node module
Ok, I've started with the node tooling for android and put it up on github.
https://github.com/bennmapes/cordova-android/tree/node-toolin
If someone can take a look at it and maybe add some suggestions that would
be awesome. I added a project.properties file to the root/bin folder so you
can `cd`
An unofficial tally of opinion so far:
Android only: Jesse, Anis, Andrew, Lorin
All: Fil, Frank Henning, Matt Lantz
Benn's vote counts as "do android now/soon, with all eventually".
So putting effort into this venture for Android seems to be supported for
now.
If anyone is interested in kicking
The question is not _are_ there benefit, but what value do that they bring,
versus the effort to do it?
In my opinion rewriting it presents a greater risk than (for example)
having a Log utility function duplicated across files, as it will _never_
change.
To me this is a case of knowing what and wh
One thing about the windows sets of scripts (Jscript-based) is that it is
a primitive scripting language. From what I can tell (please correct me if
I'm wrong) there's no concept of modules, so code re-use is a problem,
which leads us to roll with copy-paste jobs such as the Log function [1]
[2] [3
+1 to this thread.
I say we work on BB/Android first but it would be nice to have all the
tooling eventually in node (for consistency/maintainability). For the
windows tooling, it's mostly in JScript at the moment anyways so the code
could pretty much stay the same by just updating a few of the ba
this conversation has been continuing on and offline around the watercooler.
+1 for Jesse's concern.
There is absolutely no value in throwing out working bat scripts and
rewriting them in node. It's makework.
For BB10, the scripts were written in node in the first place, and bash/bat
scripts inv
No, I have not yet seen it, sounds sweet, and I applaud your commitment.
The comment was based on historical data; I am still optimistic for the
future.
You will of course need to upgrade/downgrade to Windows 8 to develop/test
for Windows 8, or Windows Phone 8.
@purplecabbage
risingj.com
On Wed,
I have seen it and I want the same one!
On Wed, Aug 7, 2013 at 12:14 PM, Filip Maj wrote:
> I resent that comment about lack of Windows testing! Have you seen my
> sweet swivel-monitor laptop that I have Windows 7 on?
>
> On 8/7/13 12:11 PM, "Jesse" wrote:
>
>>Well, given that only Benn, and mys
I resent that comment about lack of Windows testing! Have you seen my
sweet swivel-monitor laptop that I have Windows 7 on?
On 8/7/13 12:11 PM, "Jesse" wrote:
>Well, given that only Benn, and myself have contributed to the windows 8,
>and windows phone platform scripts, and no one else even seem
Well, given that only Benn, and myself have contributed to the windows 8,
and windows phone platform scripts, and no one else even seems willing to
test the windows phone platform, it seems unfair to suggest we throw away
working code, and rewrite it just for fun.
Having a dependency on node is no
To install any plugins you at least need plugman which requires node. Our
users are most likely going to have to install node as a dependency at some
point. I don't see why having it as a dependency for platform libraries is
such a big deal.
On Wed, Aug 7, 2013 at 11:34 AM, M. Lantz wrote:
> +1
+1
Agreed I pretty much only use Cordova cli at this stage to make apps and as
such don't have any issues keeping my node up to date or relying on is as a
dependency.
M. Lantz
On 2013-08-07, at 1:07 PM, Frank Hennig wrote:
> +1 for all platforms
>
> I think it's not really an completely ne
+1 for all platforms
I think it's not really an completely new dependency. Some components actually
depends on node.js like cordova-cli and plugman. Many developers of cordova
app's actually using grunt or bower and other node related stuff to lint or to
test their html and js code.
A consist
+1 for Android/BB
would be majorly helpful on those platforms
On Wed, Aug 7, 2013 at 9:15 AM, Filip Maj wrote:
> I agree with you, Andrew.
>
> Bryan, judging by this thread, it doesn't look like we'll be switching
> over to node.js for all platforms, just for android/bb.
>
> On 8/7/13 7:38 AM,
I agree with you, Andrew.
Bryan, judging by this thread, it doesn't look like we'll be switching
over to node.js for all platforms, just for android/bb.
On 8/7/13 7:38 AM, "Andrew Grieve" wrote:
>I should also add that when I installed node on windows XP, it had no
>other
>dependencies and was
I should also add that when I installed node on windows XP, it had no other
dependencies and was far easier to install than android's other
dependencies (android sdk, eclipse, JDK).
However, I did also find that at least one of node's apis (getline) didn't
work on windows. We'll have to still test
+1 for Android.
On Wed, Aug 7, 2013 at 10:00 AM, Bryan Higgins wrote:
> All BB scripts are already written in node, except for check_reqs. It's
> hard to check for the existence of node using node. :)
>
> If other platforms go that way, we should standardize the location of the
> scripts. I'd li
All BB scripts are already written in node, except for check_reqs. It's
hard to check for the existence of node using node. :)
If other platforms go that way, we should standardize the location of the
scripts. I'd like to see them directly invoked by CLI rather than going
through the shell.
On T
+1 if we can somehow automate a user-level node installation (or
package it somehow).
On Tue, Aug 6, 2013 at 3:28 PM, Filip Maj wrote:
> That's a fair answer! I concur. The main win for me is in android + BB
> land, for the reason you name, Jesse.
>
> On 8/6/13 3:24 PM, "Jesse" wrote:
>
>>I only
That's a fair answer! I concur. The main win for me is in android + BB
land, for the reason you name, Jesse.
On 8/6/13 3:24 PM, "Jesse" wrote:
>I only think this should be done for the multi-OS platforms.
>Elsewhere it is just a make work project IMHO.
>I have spent a lot of time ensuring that I
I only think this should be done for the multi-OS platforms.
Elsewhere it is just a make work project IMHO.
I have spent a lot of time ensuring that I was not introducing
dependencies, then we add node, and we get 600 deps.
@purplecabbage
risingj.com
On Tue, Aug 6, 2013 at 3:14 PM, Filip Maj wr
25 matches
Mail list logo
