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

Combine Options into a single tabbed dialog #62

Open
ctrueden opened this Issue May 1, 2014 · 2 comments

Comments

Projects
None yet
2 participants
@ctrueden
Copy link
Member

ctrueden commented May 1, 2014

Currently there are many Edit > Options plugin dialogs. It would be better to combine them into a single tabbed dialog.

Migrated-From: http://trac.imagej.net/ticket/366

@ctrueden ctrueden added this to the 3.0.0 milestone May 1, 2014

@tnargsirrah

This comment has been minimized.

Copy link
Member

tnargsirrah commented May 1, 2014

Curtis --
  I concur!
  How are you?  Are Kevin and Johannes coming out here for AQLM?

    -- 

    Grant
  On 5/1/2014 6:25 AM, Curtis Rueden wrote:

  Currently there are many Edit > Options plugin dialogs,
    corresponding to the IJ1 dialogs. It would be better to combine
    them into a single tabbed dialog. To accomplish this, the IJ2
    plugin framework needs a new Parameter attribute specifying
    which on which tab of the input dialog a particular input field
    belongs.
  Migrated-From: http://trac.imagej.net/ticket/366
  —
    Reply to this email directly or view it on
      GitHub.
@ctrueden

This comment has been minimized.

Copy link
Member Author

ctrueden commented May 1, 2014

Yep, @dscho and Kevin will both be there this year, I think!

As for this issue: it is left intentionally vague, but there are really two separate challenges:

  1. Make the modern Swing UI combine the options into a single dialog.
  2. Make the legacy ImageJ1 UI do so.

Achieving (1) is what the Trac ticket was originally about. But since we are sticking with the ImageJ 1.x UI for at least a couple more years, there is now a question of whether we should enhance it in this fashion. I would lean toward not, and still focus on improving the Swing UI. But as far as improvements go, there are many (many, many, many......) bigger fish to fry. We decided to evolve the new Swing UI away from the ImageJ1 UI design, since doing so will only benefit users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.