2. Summary
  3. Files
  4. Support
  5. Report Spam
  6. Create account
  7. Log in
 
Idea sandbox Idea sandbox
Popular ideas Popular ideas
Ideas in development Ideas in development
Implemented ideas Implemented ideas

Popular ideas Here are the latest ideas about GIMIAS that have been approved.

Visual properties are not easy to access  
Written by xplanes the 16 Dec 11 at 16:59. Global category: End-User. New
To change common visual properties like volume rendering or opacity of a mesh there are too much clicks
0
votes
up equal down
Solution #1: Simplify access to visual properties
Written by xplanes the 16 Dec 11 at 16:59.
Add a toolbar for changing visual properties
Divide properties controls into more commonly used and advanced
Add a snapshot to select volume rendering transfer function

Add a comment or propose a solution >>

When user selects a plugin, there's no information  
Written by xplanes the 16 Dec 11 at 16:14. Global category: End-User. New
There's no information about what the plugin does and the current version.
0
votes
up equal down
Solution #1: Add more information
Written by xplanes the 16 Dec 11 at 16:14.
Use an icon and the information that is in the web site for each plugin. Use Automatic Update to check for updates about a plugin.

Add a comment or propose a solution >>

Automatic updates is not usable  
Written by xplanes the 16 Dec 11 at 16:09. Global category: Developer. New
There are too many controls in automatic updates without icons.
0
votes
up equal down
Solution #1: Improve GUI
Written by xplanes the 16 Dec 11 at 16:09.
It will be nice to have an icon for each package like in Android-Market and more information about each package. Hide all controls and divide the window in two parts: select package and downloading/installing packages.

Add a comment or propose a solution >>

There are too many toolbars by default  
Written by xplanes the 16 Dec 11 at 16:05. Global category: End-User. New
The user has too many options by default. Usually it only uses a few of them.
0
votes
up equal down
Solution #1: Use more advanced toolbars that can hide the options
Written by xplanes the 16 Dec 11 at 16:05.
Try toolbars that can show the options when are clicked or ribbons like Microsoft Office

Add a comment or propose a solution >>

Configuration of custom working area is not easy  
Written by xplanes the 16 Dec 11 at 16:03. Global category: End-User. New
Configuration window that allows to customize the working area is not easy to use.
0
votes
up equal down
Solution #1: Toolbar + type
Written by xplanes the 16 Dec 11 at 16:03.
User should be able to create a custom working area using a toolbar with a grid defining the number of windows. Later, user should be able to configure the type of each window.

Add a comment or propose a solution >>

Define a plug-in error system to avoid exception to cross DLL boundaries  
Written by yakumoklesk the 26 Jan 11 at 08:57. Global category: Developer. New
Gimias is a great framework, but it deals with many DLLs, and it is used by many developers, using diferent operating systems, and even compiler versions on the same operating system, different libraries versions, etc.

Actually, when a error is produced in a plug-in DLL, the normal behaviour is throwing a exception that is catched in gimias, thus crossing the DLL boundary. As the exception thrown is an object created in the DLL, it may use a heap allocated in a different processing space that gimias, also with a different malloc version, etc. Moreover, the exception object could be different version in gimias core that in DLL. This can cause some obscure problems very difficult to debug, so it is nice to avoid this kind of design.

0
votes
up equal down
Solution #1: Provide error handling for comunicate between plug-in and gimias
Written by yakumoklesk the 26 Jan 11 at 08:57.
The solution is designing an error system to inform about errors to gimias, but keep all exceptions inside the DLL.

As this would need a very amount of work, is understandable that this idea will be hard to implement in a near future, but is useful to have it at hand.

Add a comment or propose a solution >>

Selection toolbox: continuos selection  
Written by carlosmarcos the 20 Jan 11 at 10:11. Global category: End-User. New
While selecting a region, you must hold CTRL key and CLICK each triangle or area (if you are using "brush" selection) in order to select it. This is pretty uncomfortable if you must select or de-select a big area
0
votes
up equal down
Solution #1: Enable continous selection
Written by carlosmarcos the 20 Jan 11 at 10:11.
Enable a checkbox in Selection Toolbox that allows a continous selection, that is: while the checkbox is selected, you only have to move the mouse (while CTRL already holded) around to select/deselect an area, instead of having to click each individual triangle or "brush area"

Add a comment or propose a solution >>

Sometimes the mouse Interaction with the render window is not intuitive  
Written by xplanes the 22 Oct 10 at 13:57. Global category: End-User. New
Sometimes it's not easy to remember what key needs to be pressed to perform an interaction like adding a landmark (Shift + left mouse click) or delete a region in manual segmentation (Ctrl + left click)
0
votes
up equal down
Solution #1: Use only mouse
Written by xplanes the 22 Oct 10 at 13:57.
For example some general description could be:
- Left mouse button: select and change
- Middle button: special functions.
- Rigth button: context dependent functions and informations.
- Double clicks: ????
All interactions be possible with the mouse alone. Keys only as a shortcut.

I like the think, that when you are in the capture range of the ‘cross’, a little icon appears close to the mouse pointer,
showing the interaction that can be done.
For all interaction on the viewing system ( scrolling through planes, zooming, rotating, and moving the viewport ) the
“hand” symbol can be shown, for interaction with the image, mesh or other objects the “arrow” is shown.

Add a comment or propose a solution >>

Execution of just one plugin  
Written by carlosmarcos the 26 May 10 at 12:06. Global category: Developer. New
Maybe in the future we discover that some Gimias plugins are executed always with the same parameters and, maybe only one is going to be executed, for example, to test if the algorithm implemented within the processor is correct: this kind of test usually involves dozens of test cases applied with slightly different input data. Doing these with actual Gimias can be a very repetitive and arduous task
0
votes
up equal down
Solution #1: Command line execution
Written by carlosmarcos the 26 May 10 at 12:06.
The simplest solution would be invoke Gimias from command line, passing as parameters the input file and, for instance, a file with the processor parameters. These way, the test cases scenario can be solved programming the invocation to Gimias. Even, this call ca be made late at night, if it's a heavy task, simplifying very much tasks whose entries are previously known and whose execution doesn't need human interaction
1
votes
up equal down
Solution #2: Add scripting capabilities
Written by xplanes the 26 May 10 at 13:13.
Add Scripting capabilities using for example Python. This will allow to execute a single processor and a single algorithm with different input data, or a loop interation, changing the parameters, or a set of processors.

Add a comment or propose a solution >>

Use DICOM tag as default value to render images  
Written by xplanes the 11 May 10 at 13:49. Global category: End-User. New
Use a tag that provides information about brightness and contrast
1
votes
up equal down
Solution #1: Add the TAG in DICOM plugin reader and DataEntity
Written by xplanes the 11 May 10 at 13:49.
Store the tag in DataEntity and use it to render the image

Add a comment or propose a solution >>

Too much clicks when adding landmarks  
Written by xplanes the 11 May 10 at 13:46. Global category: End-User. New
I need to click a button every time I need to add landmarks
0
votes
up equal down
Solution #1: Automatically start landmarks selection
Written by xplanes the 11 May 10 at 13:46.
Automatically start landmarks interactor when is needed and don't force the user to press a button

Add a comment or propose a solution >>

Scripting  
Written by xplanes the 11 May 10 at 13:13. Global category: End-User. New
Functionality for scripting, macros and video generation. Be able to save steps and reproduce it to reach a certain point in a workflow.
1
votes
up equal down
Solution #1: Use SWIG and PYTHON scripting language
Written by xplanes the 11 May 10 at 13:13.
Use Phyton as scripting language and SWIG as interface for C++

Add a comment or propose a solution >>

I need to undo the previous operation  
Written by xplanes the 11 May 10 at 13:08. Global category: End-User. New
It's usually needed in mesh editing operations
4
votes
up equal down
Solution #1: Add Undo/Redo as a GIMIAS framework functionality
Written by xplanes the 11 May 10 at 13:08.
Add a stack of operations and data objects, and menu options to undo/redo

Add a comment or propose a solution >>

I need a mesh editing tools to manipulate meshes from segmentation output  
Written by xplanes the 11 May 10 at 10:50. Global category: End-User. New
I need a mesh editing tools to manipulate meshes from segmentation output
3
votes
up equal down
Solution #1: Add local mesh manipulation interaction and global transformations
Written by xplanes the 11 May 10 at 10:50.
Add local mesh manipulation interaction and global transformations

Add a comment or propose a solution >>

Syndicate content

© 2012 Geeknet, Inc.   Terms of Use - Privacy Policy