You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Tomoko Uchida (Jira)" <ji...@apache.org> on 2021/12/15 08:44:00 UTC
[jira] [Comment Edited] (LUCENE-10313) Remove log4j from dependencies and switch to java logging (in luke)
[ https://issues.apache.org/jira/browse/LUCENE-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459721#comment-17459721 ]
Tomoko Uchida edited comment on LUCENE-10313 at 12/15/21, 8:43 AM:
-------------------------------------------------------------------
{quote}I think this should only update itself when it's actually displayed but it's been years since I wrote any swing code and I forgot what the listener was to actually determine whether a tabbed pane is visible or not.
{quote}
Unfortunately, I do not think Luke well supports such a fine-grained event-driven model. It expects all components in tabs to be ready beforehand and when a user switches to TabB from TabA, it just shows the already rendered contents; this simplest static model was easy to handle for me. If a more dynamic (or event-driven) model is needed, let me take a look.
I think TabbledPaneProvider.Tab enum may need a method to re-render the component (JPanel) that is tied to the indexed tab so that TabbledPaneProvider can re-render its child components by "switchTab" event trigger. I think such tab-related event handling is not done at Swing level but application level; Swing does not have a high-level abstraction for tabs as far as I know.
was (Author: tomoko uchida):
{quote}I think this should only update itself when it's actually displayed but it's been years since I wrote any swing code and I forgot what the listener was to actually determine whether a tabbed pane is visible or not.
{quote}
Unfortunately, I do not think Luke well supports such a fine-grained event-driven model. It expects all components in tabs to be ready beforehand and when a user switches to TabB from TabA, it just shows the already rendered contents; this simplest static model was easy to handle for me. If a more dynamic (or event-driven) model is needed, let me take a look.
> Remove log4j from dependencies and switch to java logging (in luke)
> -------------------------------------------------------------------
>
> Key: LUCENE-10313
> URL: https://issues.apache.org/jira/browse/LUCENE-10313
> Project: Lucene - Core
> Issue Type: Task
> Components: luke
> Reporter: Tomoko Uchida
> Priority: Major
>
> This seems to be a simpler solution at this moment
> https://issues.apache.org/jira/browse/LUCENE-10303
> https://issues.apache.org/jira/browse/LUCENE-10308
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org