I mean, it’s dumb but I know what it is. It’s the painter for the internal frame’s title pane maximize button, which is in the internal frames title, which is in the internal frame.
It’s essentially a dumb way of writing: InternalFrame.Title.MaximizeButton.Painter
It’s java. Extremely drawn out method names is it’s calling card.
And slow startup times.
One might even say it’s an ExtremelyDrawnOutMethodNamesFactoryImpl
… BeanAbstractBeanFactory
Java isn’t as verbose as Appkit/UIKit, I think. Take a look: https://developer.apple.com/documentation/uikit/nstextselectiondatasource https://developer.apple.com/documentation/appkit/nstextinputclient
Lol. Two things can both be bad.
I’m unfamiliar with Mac programming but that looks normal. Do those function calls become absurdly long when used?
Here’s one I found on Google from the jdk:
InternalFrameInternalFrameTitlePaneInternalFrameTitlePaneMaximizeButtonPainter
Yes that’s not a typo, internalframe is repeated.
I mean, it’s dumb but I know what it is. It’s the painter for the internal frame’s title pane maximize button, which is in the internal frames title, which is in the internal frame.
It’s essentially a dumb way of writing: InternalFrame.Title.MaximizeButton.Painter