Let's build a beta

[piranna]

Now that almost all the tasks for the alpha are complete, I think it's time to start thinking and discussing where to work now:

• showstopper Update version of Node.js (fix v8 issue)
• UIs
  • blessed correctly working by default
    • NodeOS font
  • HTML renderer (Chromium Embedded Framework)
• OS flavours
  • mainframe
  • workstation
• alternative kernels
  • FreeBSD
  • NetBSD
  • runtime.js
• alternative platforms
  • ARM (raspberry pi)
  • MIPS
  • PowerPC
• splitted modules for each layer
• tests for all packages
• containers for each user
• network reverse proxy (only http/ws?)
• dhcp client written in Node.js (including ability to set ip/rotue/netmask)
• npkg update Intended to use ndm
• EFI support

Any other idea? :-)

[formula1]

That looks like the important stuff, If I wasn't so swamped I wouldn't mind getting involved with fbdev.

Btw, I found you again. http://stackoverflow.com/questions/12746053/pass-large-amounts-of-data-between-web-worker-and-main-thread

[piranna]

fbdev is "almost" working, we have it enabled but no way to use it :-P I have been working to be able to run node-canvas on NodeOS (there's a fork with fbdev support) and after fixing some issues with the libraries and dependencies to make the build process standalone, there are some linking problems because GCC guys think it's not a valid use case to have a shared library that it's itself statically compiled ¬¬ There's a workaround hack regarding rename the library files that I need to test, but don't know if it would lead to bigger problems in the future... :-/

Btw, I found you again. http://stackoverflow.com/questions/12746053/pass-large-amounts-of-data-between-web-worker-and-main-thread

Yeah, that one was regarded to my previous project ShareIt! :-P

Hmm, is there a reason why you want to statically build everything?

[piranna]

The recomended way to generate node.js compiled modules is as statically linked shared libraries, so this way they don't depend on external libraries and can be easily installable. Regarding node-canvas this is somewhat more important, since it link against Cairo graphics, that's a huge and complicated one...

[mitsukaki]

network reverse proxy (only http/ws?)

We can check that one off! 😄

[piranna]

Not fully, it keeps to find a way so users can register their own web
servers and allow virtual hosts, and write a module that wraps 'http'
module to doing so transparent...
El 25/11/2015 03:31, "Lite McFish" notifications@github.com escribió:

network reverse proxy (only http/ws?)

We can check that one off! [image: 😄]

—
Reply to this email directly or view it on GitHub
#146 (comment).

[mitsukaki]

Not fully, it keeps to find a way so users can register their own web
servers and allow virtual hosts, and write a module that wraps 'http'
module to doing so transparent...

Darn. We're getting there!

[DeanHristov]

Hi, everyone. When I run the command "install" in the stdout on my shell throw error? See the image below

Any ideas?

[mitsukaki]

@piranna ^ I had the same issue.

[piranna]

I honestly don't know what's the error here, could you describe it better? Are you talking about that stat lines? Seems the layers are not being correctly build... Are you using npm3? NodeOS build only works with npm2 by the moment (and the change to npm3 will be difficult... :-( ).