Feature wishes: Option to load all images from rebrickable, custom fields, paypal for donation #146

New Issue

2026-04-14T15:38:54+02:00

derwohat commented

2026-04-14 15:38:54 +02:00

Hi Frederik,

I have some feature wishes:

It would be nice to have an option to load all available pictures from rebrickable per set and also to upload my own pictures. For example I think that it would look much nicer to have the boxed pictures of the sets on the dashboard rather then some built versions. And instead of the blurry picture as a background I would suggest to put the main picture on the left border and put the rest of the pictures as a preview grid on the right side.
Adding custom categories, fields and values would be nice
Please show the correct price-tags in the dashboard. Not the rounded numbers.
Mass-editing for tags (or other properties) could also be useful
Please provide a paypal adress for donation so I dont have to put in my credit card into that buy me a coffee thing ;)

Thank you so much for that app. I am curious for future updates!

Hi Frederik, I have some feature wishes: 1. It would be nice to have an option to load all available pictures from rebrickable per set and also to upload my own pictures. For example I think that it would look much nicer to have the boxed pictures of the sets on the dashboard rather then some built versions. And instead of the blurry picture as a background I would suggest to put the main picture on the left border and put the rest of the pictures as a preview grid on the right side. 2. Adding custom categories, fields and values would be nice 3. Please show the correct price-tags in the dashboard. Not the rounded numbers. 4. Mass-editing for tags (or other properties) could also be useful 5. Please provide a paypal adress for donation so I dont have to put in my credit card into that buy me a coffee thing ;) Thank you so much for that app. I am curious for future updates!

FrederikBaerentsen commented

2026-04-14 21:23:26 +02:00

Thanks for the detailed list!

Going through each point:

Load all images from Rebrickable / upload own images:

I get the idea, unfortunately the Rebrickable API only returns a single cover image per set. There's no endpoint to fetch multiple photos or select if it is a box-image or build-set-image that's returned. Custom image uploads could be interesting longer term but is a bigger feature to design properly. I've noted it for future consideration.

Custom categories, fields, and values:

Could you explain what you mean here? BrickTracker already supports custom tags and statuses which can be created and assigned to sets. If those don't cover your use case I would love to understand what you're trying to do. Could you provide some examples?

Price tags showing rounded numbers:

Good catch. This is a bug. Some of the price values on the Statistics page are formatted with %.0f (rounded to whole numbers) instead of %.2f. Will be fixed in the next release.

Mass-editing tags and other properties:

Noted, but this is a bigger feature that won't make it into the current release. Added to my backlog. It is a functionality I've wanted myself too, so it is definitely on my radar.

Donation / PayPal

The README on the release/1.4-branch has been updated with the relevant link. Thanks for asking!

Thanks for the detailed list! Going through each point: 1. Load all images from Rebrickable / upload own images: I get the idea, unfortunately the Rebrickable API only returns a single cover image per set. There's no endpoint to fetch multiple photos or select if it is a box-image or build-set-image that's returned. Custom image uploads could be interesting longer term but is a bigger feature to design properly. I've noted it for future consideration. 2. Custom categories, fields, and values: Could you explain what you mean here? BrickTracker already supports custom tags and statuses which can be created and assigned to sets. If those don't cover your use case I would love to understand what you're trying to do. Could you provide some examples? 3. Price tags showing rounded numbers: Good catch. This is a bug. Some of the price values on the Statistics page are formatted with %.0f (rounded to whole numbers) instead of %.2f. Will be fixed in the next release. 4. Mass-editing tags and other properties: Noted, but this is a bigger feature that won't make it into the current release. Added to my backlog. It is a functionality I've wanted myself too, so it is definitely on my radar. 5. Donation / PayPal The [README](https://gitea.baerentsen.space/FrederikBaerentsen/BrickTracker/src/branch/release/1.4#bricktracker) on the `release/1.4`-branch has been updated with the relevant link. Thanks for asking!

FrederikBaerentsen added the Kind/Bug Kind/Enhancement Kind/Feature labels 2026-04-14 21:23:37 +02:00

FrederikBaerentsen added this to the Version 1.4 milestone 2026-04-14 21:23:48 +02:00

derwohat commented

2026-04-15 11:57:51 +02:00

Hi,

Thanks for your reply.

Its a pity not to have all the pictures available. Perhaps it works with brickset api? At least it would be nice to upload the main image and some more by myself, if not automatically via one of the portals. Thanks for consideration.
For example if I sold a set, I would be nice to have that number too in the database. I know you dont want to go in that direction with your app, but I am not talking about some kind of automation for professional sellers on ebay. Just to have a field for custom information like notes or something, would be nice.
Thanks
Thanks again!
Perfect!

Hi, Thanks for your reply. 1. Its a pity not to have all the pictures available. Perhaps it works with brickset api? At least it would be nice to upload the main image and some more by myself, if not automatically via one of the portals. Thanks for consideration. 2. For example if I sold a set, I would be nice to have that number too in the database. I know you dont want to go in that direction with your app, but I am not talking about some kind of automation for professional sellers on ebay. Just to have a field for custom information like notes or something, would be nice. 3. Thanks 4. Thanks again! 5. Perfect!

FrederikBaerentsen commented

2026-04-15 15:06:25 +02:00

Thanks for the follow up!

I have previously looked at the BrickSet API. getAdditionalImages does support fetching additional images per set, but it requires both an API key, a user hash and a setID, which you get via getSets, as the setID isn't the same as the setNumer. The Brickset API key isn't as straightforward to obtain as a Rebrickable key. So I'd rather not add that dependency for now.
Instead, I'm going to go the custom upload route: users will be able to upload their own images to a set, select which one acts as the cover image, and browse them in a lightbox. I'll add this to the backlog for a future release. I really like the idea, as I also prefer the box image as the cover. I will also see if i can combine it with #37, and offer a sidecar container with custom sourced data, that BrickTracker can pull from. If i could source the links to the additional images all at once, we might not need every user to get them themselves.
Ah, I think I understand now. Not just tags, but fully user-defined key/value pairs. So instead of a predefined field like "Owner: UserX", you could define something like "Sold for: €45" where both the label and the value are up to you. That's a more flexible system than what's currently there. I'll look info the possibilities!

Thanks for the follow up! 1. I have previously looked at the BrickSet API. [getAdditionalImages](https://brickset.com/api/v3.asmx?op=getAdditionalImages) does support fetching additional images per set, but it requires both an API key, a user hash and a setID, which you get via [getSets](https://brickset.com/api/v3.asmx?op=getSets), as the setID isn't the same as the setNumer. The Brickset API key isn't as straightforward to obtain as a Rebrickable key. So I'd rather not add that dependency for now. Instead, I'm going to go the custom upload route: users will be able to upload their own images to a set, select which one acts as the cover image, and browse them in a lightbox. I'll add this to the backlog for a future release. I really like the idea, as I also prefer the box image as the cover. I will also see if i can combine it with #37, and offer a sidecar container with custom sourced data, that BrickTracker can pull from. If i could source the links to the additional images all at once, we might not need every user to get them themselves. 2. Ah, I think I understand now. Not just tags, but fully user-defined key/value pairs. So instead of a predefined field like "Owner: UserX", you could define something like "Sold for: €45" where both the label and the value are up to you. That's a more flexible system than what's currently there. I'll look info the possibilities!

derwohat commented

2026-04-15 17:47:48 +02:00

Perhaps you can make it a combined field. Either uploading the image from harddrive oder copy the link of an actual image i.e. from brickset so that the image will be downloaded directly from brickset to BrickTracker instead of having to safe the image to harddrive and then upload again. Could save some time.
Yes, exactly.
NEW: I just thougt of another little tweak. In the detail view of a set it would be nice to have the minifigs also inside of a foldable category. Or if it is too complicated, please put the management section up above the minifigs.

1. Perhaps you can make it a combined field. Either uploading the image from harddrive oder copy the link of an actual image i.e. from brickset so that the image will be downloaded directly from brickset to BrickTracker instead of having to safe the image to harddrive and then upload again. Could save some time. 2. Yes, exactly. 3. NEW: I just thougt of another little tweak. In the detail view of a set it would be nice to have the minifigs also inside of a foldable category. Or if it is too complicated, please put the management section up above the minifigs.

FrederikBaerentsen commented

2026-04-18 20:21:32 +02:00

Rounding error: Fixed in the upcoming 1.4.1 release. All price values on the Statistics page should now use %.2f. You can test it now with the pre-1.4.1 Docker tag.

Rounding error: Fixed in the upcoming 1.4.1 release. All price values on the Statistics page should now use %.2f. You can test it now with the `pre-1.4.1` Docker tag.

FrederikBaerentsen referenced this issue from a commit

2026-04-30 20:12:21 +02:00

fix(statistics): show price values with 2 decimal places instead of rounding to whole numbers (see #146)

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: FrederikBaerentsen/BrickTracker#146