This is a fantastic product. I would absolutely love to have the standalone exe creator without the webkit add-on. It would make it worlds easier for node apps to be distributed (especially in commercial settings even though I understand the risks of not requiring an up-to-date, separate node VM). Is it feasible that the embedding logic (which I assume also adds hooks for the fs module) be separate from node-webkit? Is there a method for me to use this now in a headless form (i.e. no index.html) for just my standalone apps (I understand the executable will be bloated w/ Chromium embedded)? Or is there another framework that allows packaging of single, redistributable exe's using node? (I haven't found any).
On Thursday, August 9, 2012 1:09:50 AM UTC-5, Zhao Cheng wrote:
> Hello everyone,
> I'm glad to announce a new release of node-webkit, node-webkit is a > standalone runtime that run apps written in HTML and node.js.
> It has been a long time since release, this time we come back with > following features:
> * Write apps in modern HTML, CSS, JS and WebGL > * Strong network and native APIs from node.js > * Support modules written in JS and C++ > * Easy to package and distribute apps
> Here is a quick hello world:
> <html> > <head> > <title>Hello World!</title> > </head> > <body> > <h1>Hello World!</h1> > We are using node.js <script>document.write(process.version)</script> > </body> > </html>
On Sat, Aug 18, 2012 at 3:52 AM, Chad Retz <chad.r...@gmail.com> wrote:
> This is a fantastic product. I would absolutely love to have the standalone
> exe creator without the webkit add-on. It would make it worlds easier for
> node apps to be distributed (especially in commercial settings even though I
> understand the risks of not requiring an up-to-date, separate node VM). Is
> it feasible that the embedding logic (which I assume also adds hooks for the
> fs module) be separate from node-webkit? Is there a method for me to use
> this now in a headless form (i.e. no index.html) for just my standalone apps
> (I understand the executable will be bloated w/ Chromium embedded)? Or is
> there another framework that allows packaging of single, redistributable
> exe's using node? (I haven't found any).
You can do it yourself by adding logics in 'src/node.js', it's very easy.
I have downloaded the nw_release_win32 and then I have downloaded a zip of
https://github.com/zcbenz/nw-file-explorer and extracted to a subdirectory called "file-explorer" under nw_release_win32. I then open a console and run nw.exe file-explorer it opens a window and shows on the left hand side links to Home, Documents, Pictures and then About. When I click these nothing happens. I am guessing it should show me the contents of those folders?
Is there anyway to debug the application to find out what is wrong?
On Saturday, 11 August 2012 18:05:27 UTC+2, Zhao Cheng wrote:
> On Fri, Aug 10, 2012 at 8:00 PM, José F. Romaniello > <jfroma...@gmail.com <javascript:>> wrote: > > Hi Zhao, what are the steps to run the file explorer example?
On Mon, Aug 20, 2012 at 11:19 PM, sihorton <sihor...@gmail.com> wrote:
> This looks like a great project.
> I have downloaded the nw_release_win32 and then I have downloaded a zip of
> https://github.com/zcbenz/nw-file-explorer and extracted to a subdirectory
> called "file-explorer" under nw_release_win32. I then open a console and run
> nw.exe file-explorer it opens a window and shows on the left hand side links
> to Home, Documents, Pictures and then About. When I click these nothing
> happens. I am guessing it should show me the contents of those folders?
> Is there anyway to debug the application to find out what is wrong?
Currently released binaries have some bugs that make nw-file-explorer
only able to run on Linux, you have to wait our next release :(
Core
* Dependency of CEF is discarded, node-webkit is now based on Content Shell
* Store apps' data separately
* Make DevTools work
* Local information is provided through window.navigator.language
* timers and console related functions are tweaked to minimize conflicts
Windows
* Module finding paths is fixed so `require` would work for third party modules
* Windows version is compiled with openssl now
* Some fixs on the toolbar
Mac
* Binary size is reduced to normal size
* Fix issues on message loop
> Core
> * Dependency of CEF is discarded, node-webkit is now based on Content Shell
> * Store apps' data separately
> * Make DevTools work
> * Local information is provided through window.navigator.language
> * timers and console related functions are tweaked to minimize conflicts
> Windows
> * Module finding paths is fixed so `require` would work for third party modules
> * Windows version is compiled with openssl now
> * Some fixs on the toolbar
> Mac
> * Binary size is reduced to normal size
> * Fix issues on message loop
> And many other minor changes on stability.
> --
> Cheng
> Intel Open Source Technology Center
After this new release... now on OS X no log out put shows in
terminal... and still cant seem to get my request() example working...
(even more lost now since I cant even see any debug output)
On Thu, Aug 23, 2012 at 11:59 AM, Zhao Cheng <zcb...@gmail.com> wrote:
> On Thu, Aug 23, 2012 at 4:23 PM, Aldis Andrejevs <andrej...@gmail.com> wrote:
>> Hi, nice work..
>> but are you thinking about:
>> 1) hiding the source code
>> 2) and distributing it as one launch file
> Hiding source code is impossible now, what you can do is only
> Obfuscation [1], this is a problem faced by all web apps.
> As for distribution in one file, did you mean this [2] ?
On Thu, Aug 23, 2012 at 5:01 PM, Karl Tiedt <kti...@gmail.com> wrote:
> After this new release... now on OS X no log out put shows in
> terminal... and still cant seem to get my request() example working...
> (even more lost now since I cant even see any debug output)
Your request() example works, if the zip file didn't work that's
because it's not a valid package.
The console didn't work on Mac now, there will be a quick bug fix release soon.
