Sebastian Herholz wrote:
> Hello Paolo,
>
> We met recently with our most experienced 3D software user, who will now
> start using meshlab for some parts of his work, to go over Meshlab and
> its plugins. He liked Meshlab very much and had a few suggestions to
> make it even better. We also have a couple things to discuss about how
> edit plugins work. We would be happy to do the work for these changes
> but want to get your opinion about our ideas. We know that there are a
> lot of things here so if you prefer a conference call please feel free
> to let us know.
>
> 1. Currently to rotate the mesh when using an edit plugin you have to
> push escape or the toggle button to exit edit mode each time. In order
> to be more like other 3D software packages alt+middle mouse button
> should also be able to rotate the model. In edit mode MeshLab already
> supports mouse wheel to zoom and middle mouse button click to drag the
> mesh just like 3DS Max so we think adding the 3rd type of motion to the
> middle mouse button makes sense.
>
true. It was something i planned to do sometimes ago but i forgot...
go for it.
> 2. We would like a Save function that saves the mesh to the file it was
> opened from without explicitly asking for a name and path.
>
agree. feel free to add it.
> 3. After saving a mesh with "Save As" we would like the mesh to now be
> linked to the file you just saved instead of the file that was
> originally loaded (like most all other applications do). Right now, for
> example, if you "Save As" mesh.obj as mesh2.obj you are still working on
> mesh.obj instead on mesh2.obj. Isn't it a better idea to to use
> mesh2.obj instead?
>
>
yes. patch it.
> 4. When an edit plugin has a Dialog which has a close button (x),
> 5. The current design for the MeshEditInterface does not have any
>
> 6. Edit plugins do very crazy things when you try to open meshes in
>
>
I sincerely think that the whole edit mechanism, glarea abstraction,
documnet managaing of meshlab are really not well designed.
I really would like to start a BIG refactor of the basic structure of
meshlab, but i think that it will postponed to the 1.2 release.
So for now i leave it as is trying to make most things more or less working.
I have just started a page on the wiki
http://meshlab.sourceforge.net/wiki/index.php/MeshLab_Architecture
devoted to the design of the next release of the meshlab framework.
Lets try to use it and post here in the mailing list when someone update
it to request for comment.
For now i have just copyedited your insightfull comments there.
> 7. When you start meshlab in linux with metacity there is this empty
> meshlabStdDialog showing which is later populated with the filter ui
> when you chose a filter from the list. Could a new dialog window be
> created each time a filter is run instead of opening and hiding this
> one? As it is now linux with metacity users have to try to drag this
> window from the corner of the screen to uncover the file and edit menu.
>
>
Even if i think that this is a problem of QT/metacity compatibility,
I think that creating/destroying instead of hiding/showing would not be
a big change and it should not affect anything.
You can go for it.
> We know that this is a lot of stuff but we hope to here from you soon.
>
> Thanks,
>
Thanks again to you for your help, efforts and competence.
Cheers
P.
> Oscar and Sebastian
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Meshlab-devel mailing list
> Mes...@li...
> https://lists.sourceforge.net/lists/listinfo/meshlab-devel
>
>
--
Paolo Cignoni -- Senior Researcher
Visual Computing Laboratory - ISTI - CNR
http://vcg.isti.cnr.it/~cignoni
ISTI - CNR
Via Moruzzi 1,
56124 Pisa
ITALY
|