Announcement

Collapse
No announcement yet.

Rapid Photo Downloader For Linux Switches From GTK To Qt

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Razmattaz
    replied
    Originally posted by Degra View Post
    With all the Qt/GTK discussion going on,
    what's also cross-platform are web frameworks ported to a desktop app. i.e. Electron.
    Sure, Angular isn't native to both GTK as well as QT based DEs, but it can look really shiny and is super easy to port. On top of that Typescript is a much more convenient language than both C and C++.
    I am so totally in agreement with you. That is exactly the kind of Linux desktop environment needs to take off properly, I believe. Of course Electron is still a bit slow and has substantial overhead, but I think in time they will overcome some of the current performance issues or someone can always port electron to a leaner embedded browser with a more limited feature set. Using typescript for your desktop universal apps would be super awesome. Also I believe if much of the services and engines are available through micro-services, you can have a nice separation between your model/service and your front-end app (view), similar to the separation of content and presentation of HTML and CSS.

    Leave a comment:


  • doom_Oo7
    replied
    Originally posted by oleid View Post
    Actually, I prefer writing GTK+ programs over writing Qt; Qt feels like a Java-like library grafted onto C++98/C++03, and forces you to do stuff in a pre-C++11 way.
    How so ? Qt fully embraces C++11 (it is built with -std=c++1z and requires at minimum c++11 nowadays)... connect supports lambdas, containers have rvalue reference overloads, etc... You can put all your objects on automatic storage and pass pointers if you wish to get rid of `new QSomething` but now you have to take care of ownership though.

    Leave a comment:


  • darkbasic
    replied
    Unfortunately the Arch package hasn't been updated still.

    Leave a comment:


  • bug77
    replied
    Originally posted by dkasak View Post
    Ah, the QT trolls are covering themselves in their own seminal deposits today. Yawn. Still writing gtk+3 apps, still loving it. I'm guessing those who find it an 'abomination' are either just trolls or javascript kiddies.
    Now who wouldn't want to work with a little ray of sunshine like yourself?

    Leave a comment:


  • boudewijnrempt
    replied
    Originally posted by -MacNuke- View Post
    Many applications still depend on Qt4... Moving between major versions of Qt is not easier.
    From Qt4 to Qt5 was actually quite easy -- for a Qt-only application. Big applications like Qt Creator were for a long time buildable with either Qt4 or Qt5 without needing a lot of #ifdefs. Porting a kdelibs4/Qt4 application to Qt5/KDE Frameworks was a lot more work and took me months of full-time work for Calligra and Krita.

    Leave a comment:


  • dkasak
    replied
    Ah, the QT trolls are covering themselves in their own seminal deposits today. Yawn. Still writing gtk+3 apps, still loving it. I'm guessing those who find it an 'abomination' are either just trolls or javascript kiddies.

    Leave a comment:


  • Luke_Wolf
    replied
    Originally posted by Degra View Post
    With all the Qt/GTK discussion going on,
    what's also cross-platform are web frameworks ported to a desktop app. i.e. Electron.
    Sure, Angular isn't native to both GTK as well as QT based DEs, but it can look really shiny and is super easy to port. On top of that Typescript is a much more convenient language than both C and C++.
    How about... no. Keep your faux-native crap that always flips out after a few hours of being open off my desktop.

    Leave a comment:


  • eduperez
    replied
    Originally posted by microcode View Post

    This program literally seems to be DCIM -> Select All -> Drag to sync folder -> No to all (replace file prompts).

    And sure, a script is better, but there's a certain kind of person who uses a GUI program to move files between two filesystems, and for them I honestly don't see the point.
    My workflow with Rapid Photo Downloader is as follows:
    1. Plug card into card reader.
    2. Rapid Photo Downloader appears and displays a thumbnail of all images in the card.
    3. All files are selected by default, I could deselect some of them, but I rarely do that.
    4. I press "Download" and the following happens:
      1. Pictures are downloaded into separate folders, with one folder per day (using EXIF date).
      2. Pictures are renamed to include date, time, camera, and sequence.
      3. All pictures are also downloaded to a backup folder, in a separate drive.
    5. Rapid Photo Downloader disappears

    If you have an alternative capable of doing exactly that with one click or less, please tell us.

    Leave a comment:


  • microcode
    replied
    Originally posted by starshipeleven View Post
    Ummm..... no. It's like saying "there is already a wooden piece of furniture that does everything a sofa does, without all the crap, it's called tripod stool"

    Seriously, even a naked bash script is better than a file manager (and an operator) at doing what that program does.
    This program literally seems to be DCIM -> Select All -> Drag to sync folder -> No to all (replace file prompts).

    And sure, a script is better, but there's a certain kind of person who uses a GUI program to move files between two filesystems, and for them I honestly don't see the point.

    Leave a comment:


  • cipri
    replied
    Originally posted by oleid View Post
    Actually, I prefer writing GTK+ programs over writing Qt; Qt feels like a Java-like library grafted onto C++98/C++03, and forces you to do stuff in a pre-C++11 way. GTKmm is much nicer. I realize, though, that Qt is easier usable in non-Unix environments. I'd love to see more Windows and MacOS work for GTK+.
    Exactly !!!!
    When I was talking to a qt dev (qt3d developer), I asked him why also this new module , (i.e. qt3d) has the old-c++-style api.... and his answer was: to be consistent. This horrible api is not going to improve anytime soon that much. Bad documentation, old stype api which encourages you to writing bugs........
    I'm very sad to admit that i see no great future to qt. New features and modules are coming.. mostly experimental with a lot of bugs... and with old style api........

    Leave a comment:

Working...
X