Future of nomacs and call for help/volunteers about nomacs HOT 30 OPEN

@CSA-IT-Team Thank you.

The builds for Windows are created automatically almost after each commit on AppVeyor. Also when someone make a pull request with new features, there is a build on AppVeyor. The builds are available publicly 1 month. I'll notify you when I need to test some changes.

from nomacs.

I may be littering the thread for which I apologize, but I would just like to say that I have tested several different photo viewers and this one seems the best to me because it works. Every format launches without a problem. Thank you very much for the work you put into this project.

If I detect any errors I will certainly report them.

from nomacs.

@novomesk Hello, thanks for keeping this project alive! Nomacs has been my favorite image viewer, and I would love to help with its maintenance. Here's where I think I can help:

• Start triaging the issues. Add tags to help categorize them better, and close duplicates or non-reproducible ones. I would probably need privileges to modify the issues though.
• I know C++ though I am not very fluent. I can help fix some simpler bugs (slowly).
• I work on web development in my day job. I'm probably more backend-oriented but could do basic HTML and CSS, so might be able to help resurrect the Nomacs website.

from nomacs.

@leejuyuu I managed to fix the CI/CD and it now works. A minimal website for the test is up. I think from this point on wards it would be straightforward to contribute to the website like any other Github repo.

from nomacs.

@leejuyuu you can add the tags you need.

from nomacs.

@Coldtrain320

My suggestion is updating the latest bit of the code to qt6 since a lot of people use qt6 now a days. Sorry if you all hate my suggestion.

The suggestion to port code to Qt6 is good. We know that KDE is moving to Qt6 too and Qt5 is becoming obsolete.

We just need people who would turn that suggestion into reality - developers and testers.

If you are on Windows, you can help us by testing latest development build https://ci.appveyor.com/project/diemmarkus/nomacs/builds/49142263/artifacts and to check if there are not regressions compared to previous releases.

Preparations for Qt6 already started. However recent changes has to be tested/verified by experienced users. Sometimes it happens that new changes create new bugs.

from nomacs.

The suggestion to port code to Qt6 is good. We know that KDE is moving to Qt6 too and Qt5 is becoming obsolete.
We just need people who would turn that suggestion into reality - developers and testers.

Preparations for Qt6 already started. However recent changes has to be tested/verified by experienced users.

I'll make a nix package nomacs-qt6, which will enable nix users to easily run e.g. master builds in production to make real-life testing easier.

The prerequisite for this is that a qt6-based development build from a current branch can be built in the "usual" way and works generally.

from nomacs.

Anyway to add .dds format viewing on the windows application ?

The question is not related with subject of this thread.

If you want, build this plug-in and add your qdds.dll to enable viewing of the DDS files.

Here is the info why the plug-in is not built by default: qt/qtimageformats@06ee5a2

from nomacs.

@leejuyuu In my opinion we should consider two points:

1. They were not previously separated either, so same practice as before with the exception that there is a better link between the website and the code repo
2. We should consider the audience. Which layout/platform would they feel more comfortable with when reading documentation. Github or website.

imho the very technical documentations can live in the main repo (and perhaps mirrored on the website), and the general documentation live on the website. Then the only issue left would be how to define what is technical and what is general.

from nomacs.

I would be happy to be a Windows tester however at present I would need the builds to be created so I can install them. I can offer testing in a desktop and RDP environment (Windows Server 2022).

from nomacs.

The main advantage of Nomacs is that it is fast. But there are also shortcomings that make work difficult. In fact, I know of two similar image viewing applications: Nomacs and ImageGlass. Other applications are not suitable at all.

p.s. It would be good to think about changing the name to something more intelligible.

from nomacs.

I've been using Nomacs for the last year and really love it. I have a Windows 11 laptop, and would be happy to help with testing! If I knew how to code I'd love to help develop, but I have no experience 😅

from nomacs.

So, what is next?

from nomacs.

@leejuyuu Your willingness to help is welcomed.

Regarding the work on website, please contact @mmahmoudian who has access to the domain/website.

from nomacs.

@leejuyuu @novomesk the issue I have been facing at the moment is making the Github Action to work:

https://github.com/nomacs/nomacs.github.io/blob/main/.github/workflows/build.yml

from nomacs.

@novomesk Thanks for the reply!
@mmahmoudian Could you provide some details? I see that the build and deployment were successful.

from nomacs.

@novomesk Is it possible to add more tags? I would like to have "docs" and "translation" as well so that it can be easier for contributors to find.

from nomacs.

@leejuyuu I managed to fix the CI/CD and it now works. A minimal website for the test is up. I think from this point on wards it would be straightforward to contribute to the website like any other Github repo.

Now we need more people to know about this new repository for Nomacs.

from nomacs.

@novomesk Thanks!

from nomacs.

Another question, do you think discussions about documentation belong in this repo or the nomacs.github.io repo? Managing them in one place might make them easier to find, but now that the codes are separated.

from nomacs.

I probably should phrase it like this:
Should the issues about the user-facing documentation live in the main repo or the website repo?

It seems more likely that users report things in the main repo and we probably should keep it that way. Then the problem is whether to move the issues. I'm currently thinking that it might not be necessary, as long as they can be referenced from another repo.

from nomacs.

How would a regular user like me go about making a suggestion on the software for performance and security to keep up with times using Nomacs? My suggestion is updating the latest bit of the code to qt6 since a lot of people use qt6 now a days. Sorry if you all hate my suggestion.

from nomacs.

I probably should phrase it like this: Should the issues about the user-facing documentation live in the main repo or the website repo?

It seems more likely that users report things in the main repo and we probably should keep it that way. Then the problem is whether to move the issues. I'm currently thinking that it might not be necessary, as long as they can be referenced from another repo.

Also if your talking about moving the issues from the main repo you could do it like my favorite adblocker UblockOrgin and look at their repo for an example on how they did it @leejuyuu

from nomacs.

I probably should phrase it like this: Should the issues about the user-facing documentation live in the main repo or the website repo?

It seems more likely that users report things in the main repo and we probably should keep it that way. Then the problem is whether to move the issues. I'm currently thinking that it might not be necessary, as long as they can be referenced from another repo.

Also if your talking about moving the issues from the main repo you could do it like my favorite adblocker UblockOrgin and look at their repo for an example on how they did it @leejuyuu

Thanks for the suggestion, but my question is about whether to move, not how to move.

from nomacs.

I'll test it but I wouldn't know what I am looking for as bugs and how to report it on github on this version on Windows.

from nomacs.

Anyway to add .dds format viewing on the windows application ?

from nomacs.

Well that is sad then and no I don't trust my self making builds of any software

from nomacs.

@novomesk I have ~3 years of professional C++ experience, but I've never worked with QT or on a cross-platform application (only developed for Linux).

Nomacs is one of my favorite image viewers, and it'd be great to see it back in my distro's repos one day. I'm interested in contributing as a developer (feature implementation/bug fixes), but am wondering what kind of commitment would be expected - I've never contributed to open source before.

from nomacs.

@raxleys You yourself decide how many hours per month you want to dedicate to the project. There are many things to do, there are unfixed bugs, feature requests, etc. Choose anythings and discuss in the Matrix chat room what you would like to do next.

from nomacs.

@novomesk thanks, I'll start by looking through the issues then

from nomacs.