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

Workspaces #256

Open
rladstaetter opened this issue Aug 12, 2024 · 2 comments
Open

Workspaces #256

rladstaetter opened this issue Aug 12, 2024 · 2 comments

Comments

@rladstaetter
Copy link
Owner

Motivation

Currently, LogoRRR opens a file via dragn' drop or via file menu and populates the filter bar with default values, which correspond to java.util.logging conventions and are primarily chosen because of my usage of the application.

However, for other (most?) users, the choice of the defaults are other ones, not really foreseeable if you think of it.

What is missing is a possibility to persist filters of your choice as defaults. Maybe depending on the usecase or log file - or application? - you want to have always the same settings for the log viewer, such that you can observe different aspects of the log file.

Implementation / Feature ideas / Brainstorming

  • create an option to persist the current filter configuration, give them a name - this concept will be called workspace
  • on opening new files, provide the possibility to quickly select or switch those named `workspaces´ and apply the filters accordingly
  • workspaces are independent of individual log files and live as their own concept (as opposed to the current situation)
  • optional: workspaces may also comprise of other settings for logorrr as well, like the position/height/size of the application window
  • it should be easy to use in any case, just with the mouse ideally (except naming of such a workspace?)
  • thought: maybe it suffices to just use different configuration files?
@rladstaetter
Copy link
Owner Author

tagging @eitch - maybe you have some thoughts on this.

@eitch
Copy link

eitch commented Aug 15, 2024

This sounds quite good. Maybe just have a drop down for the workspace, and this stores all the modified configuration in that workspace. A new workspace copies the previously selected workspace.

A file should be able to override the workspace's configuration, so maybe a dialog for the workspace's configuration still makes sense?

I'm thinking of: When i use log4j, then i want to use it's INFO/WARN, etc. filters. But a file might require additional filtering for a special class, which should be highlighted as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants