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

Support for List as an input type #118

Open
hinerm opened this Issue Aug 29, 2014 · 5 comments

Comments

Projects
None yet
2 participants
@hinerm
Copy link
Member

commented Aug 29, 2014

It would be great if an input could be a List of a supported sub-type. The List widget would render plus and minus buttons to add or remove widgets of the sub-type.

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

@hinerm hinerm added the enhancement label Aug 29, 2014

@hinerm

This comment has been minimized.

Copy link
Member Author

commented Aug 29, 2014

I think there should also be a toggle to decide if the list is row or column major.

For the actual numeric notation, I propose moving Range to SJC and genericizing it. Then we can accept String notation for each row/column.

@ctrueden

This comment has been minimized.

Copy link
Member

commented Aug 29, 2014

What are the rows and columns here...? Isn't that only applicable to 2D data structures like tables?

@hinerm

This comment has been minimized.

Copy link
Member Author

commented Aug 29, 2014

Sorry, I was conflating things.

I don't think List alone provides a nice way to enter tables so it doesn't really solve the my use case.. I was imagining entering a list of 1D Ranges to build tables.. but maybe that's a bad idea and/or not really necessary right now

@ctrueden

This comment has been minimized.

Copy link
Member

commented Aug 29, 2014

Right, support for Range inputs is one thing. Support for List that has + and - buttons is something else.

The reason I drew your attention to this List thing was not to suggest that it would solve your use case, but rather to point out that it is a potentially conflicting use case. If we interpret List and array inputs to mean "variable number of the constituent type's widgets" that is somewhat incompatible with treating a particular array as a single input with its own widget type.

Further thought and discussion required probably!

@ctrueden

This comment has been minimized.

Copy link
Member

commented Sep 27, 2017

@tibuch started work on a general-purpose Swing list widget here. Further effort needed to polish this up. (The widget itself belongs in scijava-ui-swing, but it is highly relevant to this issue.)

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.