Hi John,
I would like to see if I can get my fork of JPEGView into the official PortableApps repositories. I'm the current maintainer of the active JPEGView fork. The original JPEGView hasn't been updated since 2018. I've updated some libraries, and starting to get some activity moving along with community contributions.
App page as it is now, 1.0.37.0 was the last version. https://portableapps.com/apps/graphics_pictures/jpegview_portable
My semi-official fork 1.0.39.1 currently latest: https://github.com/sylikc/jpegview/releases
Thanks
/Kevin M (sylikc)
Good idea. I just posted a dev test here: https://portableapps.com/node/65918
Sometimes, the impossible can become possible, if you're awesome!
Thanks a lot John!
I haven't changed the code too much. More features are in the pipeline as some PRs are out, but as of right now it works exactly the same as it did in v1.0.37. I'm going to be putting in some work to make the keymap.txt and JPEGView.ini work portably.
Right now it loads the second JPEGView.ini from the APPDATA directory. I just tested the portableapps installer... I see the ini save there too.
I think I might be able to add an environment variable or switch which could redirect it to the PortableApps settings directory for KEYMAP.TXT (and have it work well with the launcher). I'll put that on the TODO :).
It's been a long time since I've been active with PaPPs. I'm happy to see you're still the maintainer!
Thanks!
/Kevin (sylikc)
The launcher works the same between the original and the fork, so any bugs from there will still be there. Is the second INI always used from APPDATA? If so, I can backup/restore that during run.
Still maintaining, yeah It's odd to think I released the first modern portable app 18 years ago.
Sometimes, the impossible can become possible, if you're awesome!
I'm still familiarizing myself with the JPEGView code. I'll be taking a look in the future regarding how it's handling the "user" INI file. There's an open issue right now from a community member regarding just this, so I have to dive into the mechanism soon enough.
I'll let you know when I figure it out, and since I also worked with PortableApps installers in the past, I'll look at that code too to see how it interacts with JPEGView.
It's been a long time... I still remember the beta days, or at least the way long ago versions, before Freeware hit the scene! Ah, the nostalgia!
You can drop a note to the developers email on the contact page and I'll get it.
The PA.c Launcher (JPEGViewPortable.exe) moves JPEGView.ini and ParamDB.db back and forth to the App\JPEGView directory from Data\settings. You can see the configuration in the JPEGViewPortable.ini file within JPEGViewPortable\App\AppInfo\Launcher.
Yeah, it's been a while. Still working on a new hosting solution for freeware so it isn't quite so expensive.
Sometimes, the impossible can become possible, if you're awesome!
I tested it a bit more and all seems well, so I went ahead and released the new package I did of this as official.
Sometimes, the impossible can become possible, if you're awesome!
I appreciate it! Some translations and stuff updates will be coming...
So, what's the process of getting updated releases in? Do I post on the forum here when a new version is out or something?
Can you do me a favor and change the name on Publisher? "Kevin M (sylikc)" is what I've been going with these days (still not yet comfortable putting my last name in anywhere)... feel free to leave on David Kleiner https://sourceforge.net/u/dkleiner/ if it's common to attribute his past work.
Updated. We usually link to the fork as long as they link to the previous maintainers, which you do.
Sometimes, the impossible can become possible, if you're awesome!