my goal is to see how far I can get with that repo without having to open a text editor
so far I created the README and got the Gitter badge in there strictly through the web interface
good call, i use that web interface a lot actually
Forrest L Norvell
that's a start
retweeted from like all my accounts :)
Forrest L Norvell
so my pocket tells me ;)
at some point you should send something to the mailing list about it
This message was deleted
@othiym23 I'd love to pitch in with help @mikeal I've commented on the issue about maths.
@kenperkins I'm guessing PayPal is using Breeze for their ML stuff
@rvagg I'm updating the Node Forward website with more calls to action and I want to put some stuff in there asking people to contribute to nan, is there a good starting point for that, or an Issue about the changes you want to make for the next big release?
@mikeal issues list is where all of it done, one of the main contributors only exists on github in fact e.g. next release has been outlined here: rvagg/nan#205 - will be released at the end of this week. I've just made this issue for v2 discussions: rvagg/nan#208 - so far there's only one small breaking change that's slated for it (I just can't recall exactly what it is right now!) but I'm opening up discussion to more severe breakages.
Hello guys. I have had a thought about node and I feel a little like "node" is missing a user interface. And wondered if that is worth a discussion.
If by "user interface" you mean a GUI, there are projects such as node-webkit and atom-shell which allow you to write HTML5 desktop apps that directly interface with node.js application code, or tint2, which is more of an extension of node.js which bridges with native desktop APIs.
yeah, and existing browser engine is amuh better GUI than we’d be able to just implement.
is there a discussion/place to discuss build targets for node?
yeah, there is a /build repo :)
that's where the people who are building and managing the new build system are
@rvagg is driving it
@quarterto No I don't mean node-webkit. I mean an access to node without the shell. I know that this thought is sort of heretic but having settings for npm, managing global packages or projects could perhaps use a user interface.
@martinheidegger I'm having trouble wrapping my head around what you are asking for. I read this as GIU configuration tool for package.json files? I've seen something like this for rails apps once: https://github.com/RailsApps/rails-composer
@evantahler Well: If you install nodejs on a mac these days all you "get" is a command line tool. Don't get me wrong: its cool. But for beginners it is sort of a black box. I think a UI could do following. 1) Offer a tutorial to get started with the first nodejs code 2) Offer a tool / display to set the global npm settings (and show them): npm set / npm get etc. 3) Offer a tool that lists the npm packages (particularly the ones that are often installed with -g) to install them globally (i.e.: coffeescript) 4) Offer a tool where you can add folders as "projects". Every project added has automatic (visual!) checks for the validity of the package.json (Eventually outdated dependency checks) buttons for all the enabled scripts (run/publish/etc.)
So, am I getting this right: node-forward="Community effort to strengthen node and its ecosystem by providing a source for knowledge directly from the horses mouth" io.js="Community effort to bring node forward with help from node-forward" ?