I've created a mock-up of what IGB might look like with updated toolbar icons. I've included images on this ticket of the main view as well as several of the drop-down menus with these updated icons included.

If you'd like to view my changes, here is my branch: https://bitbucket.org/pkulzer-lorainelab/integrated-genome-browser/branch/IGBF-4351

For review, let me know your thoughts on these design changes. Also, if there are any icons that do not align with the action they are representing, I will need to know so that I can change those.

Would you be able to build installers for your branch so that I can install the version on my computer to try it out?

I'm not sure if it's possible anymore to do that, however.

I can build installers within the "lorainelab" (workspace) repositories, but I'm not sure if regular users can do it.

Re-assigning to Paige Kulzer to take a look.

Ann Loraine, I am currently unable to build installers. I followed the instructions on Canvas for setting up BitBucket pipelines (https://canvas.instructure.com/courses/1164217/pages/set-up-bitbucket-pipelines?module_item_id=14594728) and I'm able to run the actual pipelines, but nothing is being output to my Downloads folder.

BitBucket recently decided to forego App Passwords in favor of API Tokens, so I wonder if that has something to do with the issue. Dr. Freese and I were troubleshooting yesterday with API Tokens but they are causing the pipeline to fail. We've tried saving the value of the BB_AUTH_STRING variable as the token, our username and the token, our email and the token, and the token name and the token (all colon-separated). We've also used API Tokens with all scopes enabled, so that's not contributing to the issue.

Here's the error I'm getting when the pipeline fails: [ERROR] Failed to execute goal org.sonatype.install4j:install4j-maven-plugin:1.1.1:compile (compile-installers) on project main: null returned: 1 -> [Help 1]

Thanks for identify and investigating the Bitbucket pipeline issue in the preceding comment Paige Kulzer.

The bitbucket pipeline service is basically a container-running service. When a developer runs an IGB pipeline, the bitbucket infrastructure creates a new container from a docker image we create. If developers can no longer easily run this "build pipeline" using their bitbucket accounts, we should develop a workflow that "core team" developers can do on their own machine to build installers.

In the meantime, can you provide a link to the IGB executable from the branch? I think the file name is igb_exe.jar or something similar. You could stash it on google drive and provide a link here. You might be able manually upload it to the Downloads section in your bitbucket account. There are a probably a lot of options. Don't attach here because - too big.

Here's a link to the IGB executable from this branch: https://drive.google.com/file/d/1mRLixs_WJU7CeRxqdHNMQV1ePmwm8YkE/view?usp=drive_link

I downloaded the jar file and ran it, but the version that ran did not seem to match your branch.

Info from the "About IGB" screen:

The current Branch Name : main
The build date/time : 07-18-2025 14:55:48
The latest commit id : 272d79449b978f8ded69e40d0fc2aa572f7df0e4

To test / review using igb_exe.jar, here's what I did:

Changed into my local IGB clone - the top level directory.
Ran "mvn clean" to remove any older class files and compiled jar files.
Copied the downloaded jar file to the current location.
Ran shell script ./run_igb.sh.
This should have ran the the newly downloaded jarfile.

Tested locally on Mac using Paige's branch.

Able to see the new icons. No errors in logs. Note that the icons have a transparent background so could be useful for a future light/dark mode.

I have changed the scope of the ticket such that the purpose of this ticket was to explore using updated transparent icons. As this has been completed I am closing the ticket.