Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
OS X version #37
The application compiles on OS X already and code-level compatibility is being actively tested with Travis. The
Implementing a graphical config tool for the web server might be useful before actually shipping anything.
I started writing a homebrew formula here. However it produces broken binaries:
I've given this issue some thought recently. One idea would be to create a native application, with a window containing a WebKit view, i.e. an embedded browser. Inside the native application the actual client is bundled. The application starts the client as a separate process and shuts it down when the application is terminated. A preference pane is provided to choose if the browsers should connect to a remote client or the local embedded client. Some code is also added to the application to forward the notifications in the browser to native notifications.
As a second iteration there could be an option that keeps the client running although the application is terminated. When the application is started again it connects to the client.
As for the build process, I'm thinking an Xcode project that builds the application. As a post-build step it can invoke the existing build process and set the installation target to inside the application bundle. Finally a disk image,