BeeRef 0.3.4?

Can someone please release the stable version of 0.3.4?

I notice that the development version fixed the cropping crash, and added a prompt to prevent exiting the app without saving. The last update to the development version was in June 2024, and the latest stable release was released in May 2024 (over a year ago).

I tried to create an AppImage of the development version, but I admittedly have no idea what I'm doing, and flubbed it. If someone with programming skills and time on their hands could do this, I (and many other users of BeeRef) would greatly appreciate it.

Thank you!

[g-rix]

Hi, I'm not sure what has happened to the project, but I have forked it and built 0.3.4-dev. (Plus added some stuff that I needed unfortunately I don't have the time to fully support the project.) (Go take a look here : https://github.com/g-rix/beeref/releases). The windows-11 and ubuntu(20.04) releases have been tested. A previous test release of mine has been tested on MacOS.

@g-rix Thank you so, so much!

I understand that you don't have time to fully support the project, but would it be possible to allows users to report issues on your repo?

I already ran into a bug, unfortunately: The prompt of asking a user to save a project before exiting does not appear if you exit the app with the X on the menu bar (The prompt only appears if you use File > ... ).

Nonetheless, thank you so much for building the 0.3.4 version, and even adding some features!

[Yasumora]

yup I agree, I also mentioned in another issue that allowing us to open issues would be ideal.

[g-rix]

Hi @cs50ad and @Yasumora I've updated my repo to Beeref-0.3.4-dev-RC1, this should fix your @cs50ad issue as noted above. It was fixed before but I had not published it.

I'm still deciding on how to to support this project, I've never used Python or Qt or the combo before never mind github with it's build-runners etc so the learning curve is really steep. I really don't want to give users' the impression that they can request features or report bugs, which will they ultimately hope will be implemented/fixed at some point. I really don't have a good insight into how the internal graphic aspects of Beeref work or the way it stores all the pieces that you add to your mood board never mind the language/toolkit aspects.

I've been really lucky that the features that I wanted were quite easy to implement, these were around 'editing-out' parts of a really big mood board. Chuck all the images into a huge one and then arrange/group into pages/categories, export the pieces to create smaller mood boards (and/or .svg images) and/or actually extract those images to be used in some other application.
Hence the Export/Save_as/Show-filename features that I've added.

PS: I'm a photographer that is using Beeref to filter/group/collate images for zine(s) / photobook(s) and "it's perfect by the way".

I really wish that rbreu/Rebecca Breu was around to give us some guidance

[Yasumora]

hey! @g-rix I understand your situation, I am also quite new to python and programming in general so I can see how this is a bit overwhelming since it is for me too lol. Completely unrelated to the message, but I think it'd be great if instead of shipping the .zip for the appimage, you'd just upload the unzipped AppImage (Tools like GearLever and AppImageLauncher update from repo url automatically) and remove "ubuntu" from the name as AppImage is a universal package type.