Try out Chainsaw - it's super useful once you get the model. Under help, there's info on the expression syntax, and the chainsaw-log tab (where chainsaw log messages route by default) can be a playground for working with the colorization/filtering/expressions.
Here's my general flow: 1. Filter at the logger level using the logger tree on the left. Right-click on the root or at a logger level to explicitly hide or unhide loggers and their children 2. Build a custom expression to ignore other cruft you don't want to look at. Click on the ellipses next to 'Ignore' below the logger tree to define a custom expression you can use to hide additional stuff. Now that you have your 'base' set of events you want to look at, you can use the 'Refine focus on' box to define an expression to match specific events you want to see. Try: msg ~= receiver Entering an expression in the 'Find' box will find matches, and you can move through those matches with F3/Shift-F3 Try: level >= warn Expressions can be &&'d and ||'d and paren'd, and you can use most of the fields like msg, level, logger, or 'exception exists' in java-land since we try to parse java exceptions into the 'throwable' field. One last thing: Event annotation. Click on the 'Marker' field and enter something. You can bounce between annotations with F2/Shift F2. You can bounce between any color rule (search, marker or custom color expression) using Cmd-N and Cmd-P (mac shortcut at least). Right click on a row in the table to get to the color expression screen, where you can order color matching expressions - first match wins. Hope that helps - love to hear feedback. Scott On 10/14/17, Matt Sicker <boa...@gmail.com> wrote: > On 14 October 2017 at 13:22, Ralph Goers <ralph.go...@dslextreme.com> > wrote: > >> I’ve worked with JavaFX. It is pretty easy. I have zero interest in >> working with Swing. >> > > Good to know! For Kotlin support, this project looks handy: < > https://github.com/edvin/tornadofx>. For Scala support, there's this: < > http://www.scalafx.org/>. The extent of my current JavaFX knowledge is > basically that I know there are some sort of psuedo-XML files to describe > the GUI (or you can use the API directly), and that it uses CSS to some > extent. > > >> I’d prefer to get away from WebStart. I think that may have been what >> hung >> up Scott in the first place as he needed a cert. Some of the other >> technologies for binary deployment make sense to me. >> > > Infra has an official way to sign things for this now, so it might not be > as bad as back when Scott was trying to get support for it in the first > place. With Java 9, I think it'll be easier to bundle up .exe/.app files > for Windows and macOS, and GNU/Linux still has a million ways to package > things, but there are some maven plugins out there to create some common > ones (rpm, deb, etc.). There's also Flatpak <http://flatpak.org/> for that > as well. Distributing them from dist.a.o works fine, though distributing in > app stores generally requires a signing key the same way that webstart > does. > > >> To be honest, I’ve never run Chainsaw or Lillith. I am not sure how they >> differ. I am not a big fan of having two projects that do exactly the >> same >> thing so I’d like some understanding of what they do and how they differ. >> > > Most of my log viewing happens either via console programs (tail, grep, > clog, tried out some others that I can't remember) or via shitty web GUIs > (Kibana, Graylog, Splunk, etc.). If I could find or help build a GUI that > works better for that, then that'd be great. I'm also not a fan of the > whole "embed Chrome and call it a native app" movement going on with > Electron; even Java is lightweight on the desktop in comparison! > > -- > Matt Sicker <boa...@gmail.com> >
