You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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
workspace
The text was updated successfully, but these errors were encountered: