OS X version

[maksis]

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.

[knoopx]

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]

@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]

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

[doobnet]

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]

@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]

any news? :)

[doobnet]

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

[TheElectrocat]

hi have a emulated clients in whinebottler mac osx high sierra, in yosemite no have problem. but have some error whit the file list big, maybe we cant solutions this. thanks.

[TheElectrocat]

[TheElectrocat]

this problem is in emulated dc++, airdc, and apexdc.

[TheElectrocat]

https://www.4shared.com/s/f_MXExGClee

[doobnet]

hi have a emulated clients in whinebottler mac osx high sierra, in yosemite no have problem. but have some error whit the file list big, maybe we cant solutions this. thanks.

Are you running the AirDC++ Windows GUI client in Wine? I would recommend using the web client instead. The web client consists of a background daemon that is available on Linux and can be easily run from within Docker. The web frontend can be used from any platform, including macOS. I think the daemon can be compiled for macOS as well, perhaps with some minor modifications.

[doobnet]

I have started to work on a native GUI for macOS, which connects to the web client daemon. It's a very slow process and is going to take quite a while.

[TheElectrocat]

i emulated whit winebottler and the program run ok (dc++ and air dc) but the problem is (could not open targef file, general failure.) this problem is for the big file list of users, in some user all its ok and the client run very good. thanks for your time and please work in native air dc client or emulated :) y paste the client working ok now greylink https://www.4shared.com/s/f_MXExGClee