New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OS X version #37

Open
maksis opened this Issue Jan 16, 2016 · 7 comments

Comments

Projects
None yet
4 participants
@maksis
Collaborator

maksis commented Jan 16, 2016

The application compiles on OS X already and code-level compatibility is being actively tested with Travis. The make install phase is not supported yet.

Implementing a graphical config tool for the web server might be useful before actually shipping anything.

@maksis maksis added the help wanted label Jan 16, 2016

@knoopx

This comment has been minimized.

Show comment
Hide comment
@knoopx

knoopx Jul 25, 2017

I started writing a homebrew formula here. However it produces broken binaries:

/usr/local/Cellar/airdcpp-webclient/2.1.0/AirDC++;Web;Client.app/Contents/ (2 files)
/usr/local/Cellar/airdcpp-webclient/2.1.0/airdcppd.app/Contents/ (2 files)
/usr/local/Cellar/airdcpp-webclient/2.1.0/share/airdcpp/ (111 files)

knoopx commented Jul 25, 2017

I started writing a homebrew formula here. However it produces broken binaries:

/usr/local/Cellar/airdcpp-webclient/2.1.0/AirDC++;Web;Client.app/Contents/ (2 files)
/usr/local/Cellar/airdcpp-webclient/2.1.0/airdcppd.app/Contents/ (2 files)
/usr/local/Cellar/airdcpp-webclient/2.1.0/share/airdcpp/ (111 files)
@maksis

This comment has been minimized.

Show comment
Hide comment
@maksis

maksis Aug 5, 2017

Collaborator

@knoopx do you have any idea that how it can be fixed? Note that the cmake scripts haven't been fully implemented for MacOS.

Collaborator

maksis commented Aug 5, 2017

@knoopx do you have any idea that how it can be fixed? Note that the cmake scripts haven't been fully implemented for MacOS.

@knoopx

This comment has been minimized.

Show comment
Hide comment
@knoopx

knoopx Aug 5, 2017

No idea, make systems always looked like alien language to me. 🤣

knoopx commented Aug 5, 2017

No idea, make systems always looked like alien language to me. 🤣

@doobnet

This comment has been minimized.

Show comment
Hide comment
@doobnet

doobnet Nov 20, 2017

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, .dmg, is created containing the application for final distribution.

Thoughts?

doobnet commented Nov 20, 2017

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, .dmg, is created containing the application for final distribution.

Thoughts?

@maksis

This comment has been minimized.

Show comment
Hide comment
@maksis

maksis Nov 20, 2017

Collaborator

@doobnet Yeah, such approach sounds good to me. At a later stage, certain Web UI navigation menus could possibly be replaced with native UI elements to get some kind of native feeling in it (similar to Spotify app).

Collaborator

maksis commented Nov 20, 2017

@doobnet Yeah, such approach sounds good to me. At a later stage, certain Web UI navigation menus could possibly be replaced with native UI elements to get some kind of native feeling in it (similar to Spotify app).

@KiPa187

This comment has been minimized.

Show comment
Hide comment
@KiPa187

KiPa187 Feb 9, 2018

any news? :)

KiPa187 commented Feb 9, 2018

any news? :)

@doobnet

This comment has been minimized.

Show comment
Hide comment
@doobnet

doobnet Feb 9, 2018

No, sorry. I haven't had time to work on this yet.

doobnet commented Feb 9, 2018

No, sorry. I haven't had time to work on this yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment