Thrust v0.7

[spolu]

ExoBrowser will undego a major overhaul to reach version v0.7. The changes include:

TODOS

• move exo_browser to brightray [@spolu]
• remove nodeJS event loop and expose API over unix domain sockets [@spolu]
• move to <webview> support instead of ExoFrames [@spolu]
• Mac OS X version (fix build errors)
• Windows version (fix build errors & add code needed)
• Add Menu Items API Expose Menu / Menu Item API #157
  • OSX
  • Aura
• Add support for webkit draggable and frameless
• Add support for TopBar Status Icon
• Update UI to Aura Port ExoBrowser to Aura #142

[spolu]

The following branch is tracking the changes: https://github.com/breach/exo_browser/tree/wip-0.7

[miketheprogrammer]

@spolu I am seeing some great code :). I however need to get a linux development environment set up. The build currently does not work on Mac, and my linux VM has too many errors trying to open the browser. (mostly due to lack of opengl support).

Gonna try to get my exo building on my Kali Linux box later. Its a very crappy machine that could not handle the full chromium build, but should def be able to handle the new brightray build.

[spolu]

Awesome! I'll try make it work on OSX before the end of the week! :)

[nearsyh]

There is no DEPS in this branch. So we use the latest chromium or the version in the master branch? Or we use brightray instead of chromium now?

[spolu]

See scripts/bootstrap.py it uses libchromiumcontent. No more long builds ;-)

[nearsyh]

Great! So how to build it now on mac?

[spolu]

First run the boostrap script:

./scripts/bootstrap.py 

Then generate build files with:

GYP_GENERATORS=ninja gyp --depth . exo_shell.gyp

Finally run ninja:

ninja -C out/Debug exo_shell

[spolu]

There are still some build errors on OSX. I'll try to fix them today

[spolu]

@nearsyh should build now. Still some errors when running... Some .gyp file tweaking is still required (frameworks and resources are not properly found by the app at runtime)

[nearsyh]

When I run on mac with the following command

open ExoShell.app

it outputs

LSOpenURLsWithRole() failed with error -10810

.

And -10810 is referenced as unknown error in Apple's document. Does anyone have any idea about how to fix this?
Also, if I run the executable in the app directory directly, it will print this :

[0808/203848:FATAL:content_main_runner.cc(751)] Check failed: base::i18n::InitializeICU().

[spolu]

The later error needs to be addressed first. It is related to the fact that the executable can't find icutl.dat in its resources... Probably due to some erroneous build config ATM since the file is in the Resources directory of the bundle.

[spolu]

Anybody willibg to take a stab at it (I'm on holidays and I only have a machine on Linux with me)

[deepak1556]

@spolu was able to build this branch successfully on linux, but have to run exo_shell with --disable-setuid-sanbox ATM . any idea how atom-shell is able to run without this problem ?

[morganrallen]

Sorry if this is a terrible question.. but did you try running exo_shell --disable-setuid-sandbox? I also have a shared library path problem so my full command line is

LD_LIBRARY_PATH=out/Debug/ ./out/Debug/exo_shell --disable-setuid-sandbox

[deepak1556]

@morganrallen i just run exo_shell from /out/Debug with that flag

[morganrallen]

Get any output?

[morganrallen]

Another thought. If it appears to be running but doing nothing. From another tab or shell run node test.js

[morganrallen]

test.js will be in the root project directory

[spolu]

Well exoshell will be used as a library in other projects

[deepak1556]

@morganrallen 👍

[miketheprogrammer]

Latest version of wip0.7 finally builds and runs for me on OSX.

[miketheprogrammer]

@spolu I know we have alot of work to do but have you given any thought to security. Exposing ExoBrowser over rpc, with a simple JSON protocol that is open source breaks opens Exo up to a variety of attacks.

I examined a bunch of different ideas however none really seem to pan out from a useability perspective.

Let me know if you feel this is a concern for the short term, or if this is more of a concern for the long term. Security for an Alpha version, developer oriented browser, that will probably not be useable by the general public for at least another year, seems a waste of time, but I feel at least thought should be put in to understanding how we will and can secure it.

[spolu]

Which kind of attacks do you have in mind? Listening on a local socket with the proper rights set should be rather secure, no?

[miketheprogrammer]

I am no security expert. I assume you are correct, if we lock it down to local unix sockets, with proper rights then yes, we have delegated the problem to the user. I simply was considering the case that the User downloads some software, that software happens to have a detection for whether or not the user has exobrowser installed. Iterates of each of the available sockets and tries to execute an exobrowser command against it.

[spolu]

Well in that case, the program can also erase the entire user home directory :)

[miketheprogrammer]

@spolu :) yea true.

[nearsyh]

I tried to build the new version of Mac and found two kinds of errors.

One is "content/public/content/web_contents_view.h" is not found. This error can be fixed after removing related include statements. Will this header be used later?

The other one is caused by '-Werror' and some unused variable warnings. I cannot find where the flag is introduced, but removing this flag from out/Debug/obj/exo_shell_lib.ninja works.

[spolu]

Hey, working on it as we speak!

[miketheprogrammer]

Sounds good. I will get back on to menus asap however I think having your
core code done first will be essential.
On Oct 7, 2014 12:22 PM, "Stanislas Polu" notifications@github.com wrote:

Hey, working on it as we speak!

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

[spolu]

WiP implementation of Menus available here: https://github.com/breach/exo_shell/tree/wip-0.7
(cc @miketheprogrammer)

[spolu]

Renaming issue as "Thrust v0.7"
Will probably merge v0.7 branch before this issue is entirely resolved

[ken-okabe]

Currently, the project name confusion occurs, so please allow me to confirm.

This repo is breach.thrust and the README.md titles ExoShell now.

I tried breach.core today, and found exo-browser side by side.

Did you change the project name

ExoBrowser -> ExoShell -> thrust ??

Thanks.

[spolu]

As mentioned above. All work related to v0.7 now renamed thrust is happening here: https://github.com/breach/thrust/tree/wip-0.7

[spolu]

Yes. The project name went from ExoBrowser to ExoShell to Thrust.

[ken-okabe]

Thanks spolu, now everything is clear to me.

[spolu]

No problem! happy to help you @kenokabe. I know that things are a little unclear now with names, etc... It will eventually get better :)

[spolu]

wip-0.7 was merged with updated README.md and overall renaming to make things clearer.

[spolu]

Intial windows support! Yay! 👍

[miketheprogrammer]

Yayyyyy
On Oct 21, 2014 10:43 AM, "Stanislas Polu" notifications@github.com wrote:

Intial windows support! Yay! [image: 👍]
[image: screenshot from 2014-10-21 07 42 44]
https://cloud.githubusercontent.com/assets/15067/4720366/9e04c118-5930-11e4-98b8-af34c567533e.png

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

[spolu]

All remaining items have been added to the Roadmap (https://github.com/breach/thrust#roadmap)
Issues will be created if not already existing