Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge bigdataviewer-vistools into bigdataviewer-core #180

Merged
merged 6 commits into from
Jun 12, 2024

Conversation

tpietzsch
Copy link
Member

This addresses #172.

There was a split package (bdv.util) between bigdataviewer-core and bigdataviewer-vistools.
The least intrusive way (for dependent projects) is to just merge the two repositories.

I tried to clean out the bdv.util package in core by moving hopefully-unused classes elsewhere.
So bdv.util is mostly just vistools now.

Also update README and added @axtimwalde`s new logo :-)

These are classes that are hopefully not used anywhere else.
(This is to prepare for the merging of bigdataviewer-core and -vistools.)
Somehow this caused OutOfMemoryException immediately now. After decreasing
the memory allocated added in each iteration the Paintable is now
garbage-collected as expected.
@tpietzsch tpietzsch force-pushed the jpms-compatibility branch 2 times, most recently from 39f292e to eb1625c Compare June 12, 2024 14:47
@tpietzsch tpietzsch merged commit ee8fc98 into master Jun 12, 2024
1 check passed
@tpietzsch tpietzsch deleted the jpms-compatibility branch June 12, 2024 14:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant