• 0 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle
    • Terrible format for archiving knowledge
    • Terrible tool for retrieving knowledge
    • Locks community access behind a corporate license agreement
    • Hands control of community-created content to a corporation
    • Prevents indexing by web search engines
    • Antithetical to interoperability
    • Privacy-hostile

    A web forum is far better in most cases. If you can’t manage to run your own, there are plenty of lemmy servers that will do it for you. Even an email list (with searchable archives) would be better than Discord.

    If you have collaborative documents that outgrow the forum format, use a wiki.

    If real-time chat is needed, irc or matrix.

    A project hosting its community on Discord is a project that won’t get my contributions.


  • That’s as I expected; Thanks for confirming.

    Unfortunately, that leaves out the kind of integration I was asking about (and the kind implied in this post), through existing Qt & KDE shared libraries and such.

    CopperSpice might still be interesting for stand-alone projects written in C++, though, and I appreciate that you’re here engaging with the community.


  • I think you’re talking about migration from Qt to CopperSpipce, though, yes? I’m talking about integration with existing desktop environments. Making use of the themes that are already installed. Communicating with existing libraries via the existing interfaces. Are there any hitches to be aware of on that front?

    And language bindings, for those of us who are trying to get away from writing in C++?




  • Qt is a wonderful GUI toolkit, but new language bindings are notoriously difficult, since it depends not only on C++ (which itself is tricky to bind into other languages) but also the Qt meta-object compiler. Even so, some interesting projects have emerged on that front. For example:

    Verdigris:

    This (header-only) library can be used to create an application using Qt, without the need of the moc (MetaObject Compiler). It uses a different set of macro than Qt and templated constexpr code to generate the QMetaObject at compile-time. It is entirely binary compatible with Qt.

    DQt:

    DQt contains experimental bindings for using a subset of Qt with the D Programming Language. Qt is a library for writing cross-platform graphical user interfaces. Currently bindings exist for the Qt modules core, gui, widgets and webenginewidgets.









  • If you don’t find software that works well, you might consider a keyboard with QMK or TMK firmware, or an older AT or PS/2 keyboard with a Soarer’s converter. (I think I’ve even seen some hobbyist Soarer’s converter variants that handle USB keyboards.)

    One advantage of these is that, since they operate at the hardware level, they work in all OS and application environments.


  • You could restructure your network, but it’s probably not necessary. My phone is always behind NAT on the secondary router’s wi-fi. I got it working by:

    • Reserving a static IP address for my phone in the secondary router’s DHCP server.
    • Forwarding that router’s incoming ports 1714-1764 to the phone’s IP address.
    • Allowing outgoing traffic from that router’s network to ports 1714-1764 on my workstation’s IP address (on the primary network).
    • Adding a device (my workstation) by IP address in my phone’s KDE Connect app.