4 ms·

Yes, that's a good suggestion. The readme is due for a rewrite so I'll make sure to mention that somewhere up top! EDIT: the parent post was edited, and this c

Yes, that's a good suggestion. The readme is due for a rewrite so I'll make sure to mention that somewhere up top! EDIT: the parent post was edited, and this comment was written for the original post.

cm3 10y ago
There's a linux directory, what's that for?
- viktorelofsson 10y ago
  I've split the project in two parts, PicoTorrent and PicoTorrentCore. PicoTorrentCore is cross-platform and builds on GCC4.8. The linux directory contains build scripts to build on Linux, which is used for the TravisCI builds.
  - cm3 10y ago
    And there's no UI yet, right? If you plan to write one, I'd suggest Qt, since you use C++ extensively already.
    - serbrech 10y ago
      Why not using electron on top of the api? it's not overly complicated UI anyway, and it will build on an api that other can use.
    - tgpc 10y ago
      I hear qt is excellent, but would encourage you to do distinct ui code for each platform, in that platform's native ui libs. You'll look like a fish out of water otherwise.
      - viktorelofsson 10y ago
        Yeah, that's what I'm planning in order to keep it small and tidy.
        skrowl 10y ago
        You might want to start with a web UI then (like SyncThing). This provides you with a simple way to display your data and you get Mac / Linux / etc support for "Free" while also allowing your Windows users to have simple network access. No extra dependencies, no UI toolkits!
        viktorelofsson 10y ago
        Yes, and then you have Hadouken (https://github.com/hadouken/hadouken https://github.com/hadouken/hadouken), another BitTorrent client of mine (though server oriented) :)
      - cm3 10y ago
        To be clear, Qt is as native as you can get on X11 and Wayland. There is no vendor-controlled UI toolkit as on Windows or OS X or Android or ...
deleted 10y ago
[deleted]
cm3 10y ago
Sorry about that, I posted too fast and after seeing the linux directory reformulated it. Basically I was suggesting to more prominently mention it's Windows-only and not just in the list of features.

cm3 10y ago

There's a linux directory, what's that for?

viktorelofsson 10y ago
I've split the project in two parts, PicoTorrent and PicoTorrentCore. PicoTorrentCore is cross-platform and builds on GCC4.8. The linux directory contains build scripts to build on Linux, which is used for the TravisCI builds.
- cm3 10y ago
  And there's no UI yet, right? If you plan to write one, I'd suggest Qt, since you use C++ extensively already.
  - serbrech 10y ago
    Why not using electron on top of the api? it's not overly complicated UI anyway, and it will build on an api that other can use.
  - tgpc 10y ago
    I hear qt is excellent, but would encourage you to do distinct ui code for each platform, in that platform's native ui libs. You'll look like a fish out of water otherwise.
    - viktorelofsson 10y ago
      Yeah, that's what I'm planning in order to keep it small and tidy.
      - skrowl 10y ago
        You might want to start with a web UI then (like SyncThing). This provides you with a simple way to display your data and you get Mac / Linux / etc support for "Free" while also allowing your Windows users to have simple network access. No extra dependencies, no UI toolkits!
        viktorelofsson 10y ago
        Yes, and then you have Hadouken (https://github.com/hadouken/hadouken https://github.com/hadouken/hadouken), another BitTorrent client of mine (though server oriented) :)
    - cm3 10y ago
      To be clear, Qt is as native as you can get on X11 and Wayland. There is no vendor-controlled UI toolkit as on Windows or OS X or Android or ...

deleted 10y ago

[deleted]

cm3 10y ago

Sorry about that, I posted too fast and after seeing the linux directory reformulated it. Basically I was suggesting to more prominently mention it's Windows-only and not just in the list of features.