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

help-circle



  • ono@lemmy.catoProgrammer Humor@programming.devFLOSS communities right now
    link
    fedilink
    English
    arrow-up
    303
    arrow-down
    3
    ·
    edit-2
    5 months ago
    • 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.




  • Your current approach of talking raw SMTP is likely to be more hassle than is worthwhile, and since the days of permissive SMTP servers are long gone, might not work at all.

    Since you appear to be using an Debian-based Linux distro, I suggest this approach:

    • If you don’t specifically need exim, consider replacing it with the lightweight dma package (DragonFly Mail Agent): apt install dma
    • Configure dma (or exim) to use your ISP’s SMTP server as a smart host. (Or the Gmail SMTP server if your ISP doesn’t provide one.)
    • Use the /usr/sbin/sendmail command (which comes with dma or exim) to send messages from your scripting language of choice.

    If you prefer to receive messages as SMS, note that most major mobile carriers maintain an email-to-sms gateway for this purpose. Some web searches will probably lead you to the one for your carrier. They usually accept email at an address like 123456789@sms-gateway.example.com







  • Be the change, homie.

    When someone claims two obviously different things are exactly the same, pointing out that the comparison is idiotic is not combative, homie.

    Edit: More to the point, defending one’s community by pointing out the idiocy of an attack is not combative.

    You might not be paying for software in money but you’re going to pay for it, one way or another.

    Indeed. As I hinted in my comment, and stated more clearly in another one.



  • The difference here is mountains vs. molehills.

    And in most cases, they obviously do have sufficient ability to learn how, because they were able to learn the commercial software they’re currently using.

    As for time, yes, learning always takes time. (Thus my comparison to learning a new commute.) But suggesting that someone learn something new is not stupid or unreasonable, especially if the thing they currently use is not serving them well.

    • In response to that paragraph you added after I replied:

    I don’t know why you would think that cherry-picked and extremely specific scenario is somehow representative of the general subject we’re discussing. Of course situations exist where learning alternative software isn’t the best answer. That doesn’t make it wrong for people to suggest the alternatives. Quite often, they’re perfectly viable, and it’s perfectly reasonable to try to help by making someone aware of them.