You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
(50) |
Dec
(118) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(93) |
Feb
(17) |
Mar
(6) |
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(45) |
Dec
(17) |
| 2007 |
Jan
(23) |
Feb
(33) |
Mar
(4) |
Apr
(1) |
May
|
Jun
|
Jul
(2) |
Aug
(6) |
Sep
(1) |
Oct
|
Nov
(13) |
Dec
(20) |
| 2008 |
Jan
(26) |
Feb
(69) |
Mar
(72) |
Apr
(32) |
May
(35) |
Jun
(12) |
Jul
(99) |
Aug
(52) |
Sep
(15) |
Oct
(49) |
Nov
(12) |
Dec
(26) |
| 2009 |
Jan
(7) |
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Paolo C. <pao...@is...> - 2008-07-10 10:28:18
|
Francesco Tonarelli wrote: > Hi, Paolo > > I moved some functions to the vcg library how we had discussed yesterday. > 2 dubts came into my mind while doing it: > > 1: I've got to use Color4b as parameter type or a more generic color type? yes. I think Color4b it is a reasonable compromise between generality and practicality > 2: the parameter ProcessSelected allows the remotion of an if branch, > but...who calls the function > has to pass as parameter ProcessSelected=true if the mesh has > something selected, false otherwise... > so the branch comes out in the upper level...is it true? yes. in this way it is shorter and can be explicitly managed at a meshlab parameter level. > > I got still problems with gamma and levels...I'll goin' into deep next > days... > > cheers. > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > > ------------------------------------------------------------------------ > > _______________________________________________ > 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 |
|
From: Francesco T. <lit...@gm...> - 2008-07-09 22:38:02
|
Hi, Paolo I moved some functions to the vcg library how we had discussed yesterday. 2 dubts came into my mind while doing it: 1: I've got to use Color4b as parameter type or a more generic color type? 2: the parameter ProcessSelected allows the remotion of an if branch, but...who calls the function has to pass as parameter ProcessSelected=true if the mesh has something selected, false otherwise... so the branch comes out in the upper level...is it true? I got still problems with gamma and levels...I'll goin' into deep next days... cheers. |
|
From: Paolo C. <pao...@is...> - 2008-07-08 06:55:21
|
Francesco Tonarelli wrote: > Hi Paolo, > > I'll try to use the new feature but, in the meantime...my code doesn't > compile no more... > > You (or somebody else) have moved or deleted the originalVertexColor > (member of MeshModel) and the relative functions, > storeVertexColor/restoreVertexColor. > This member was the CORE of all my job, becouse filters always works > on the original color of the mesh that is dumped in > originalVertexColor just once, in the initParametersSet(). > > Now, I need that, or something like that to do my job, so: > > -Can you tell me if you have moved it somewhere? > -Can you tell me if you have replaced that with something I can use? > (may be vertColor ? I saw it, but...) > -Are you sure that what I use doesn't conflict with the 'work' of the > new dynamic parameter? > Hi Francesco, Look at the sample. samplefilterdyn.cpp I have commented it a bit more (and cleaned up a bit) From the sample code: // In this sample a couple of parameter are declared as dynamic. That means that the meshlab framework will automatically // manage the store and restore of the mesh state during the dynamic movement of the filter. // The plugin writer is no more burdened with the task of saving the state, but he has only to declare what the filter changes // (in this case just the vertex color). When a filter is dynamic (e.g. it has a dynamic float parameter) the meshlab // framework will automatically store that part of the state at the opening of the dialog. When the user drag the slider, // the framework will restore the state and then simply call the apply callback of the filter. // So from the point of view of the filter every time you have the freshly new mesh. // // when the user press apply the current stored state is updated. // when the user press close the mesh state is restored to the one before the startup of the filter. This should shorten a lot your code (probably it needs a bit of shortening) Cheers Paolo PS. A suggestion on coding: put in header files mostly templated code. > I leave my code unchanged by now: if I don't know where save original > colors I can't do nothing, so PLEASE reply me asap. > > cheers > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > > ------------------------------------------------------------------------ > > _______________________________________________ > 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 |
|
From: Francesco T. <lit...@gm...> - 2008-07-07 23:03:01
|
Hi Paolo, I'll try to use the new feature but, in the meantime...my code doesn't compile no more... You (or somebody else) have moved or deleted the originalVertexColor (member of MeshModel) and the relative functions, storeVertexColor/restoreVertexColor. This member was the CORE of all my job, becouse filters always works on the original color of the mesh that is dumped in originalVertexColor just once, in the initParametersSet(). Now, I need that, or something like that to do my job, so: -Can you tell me if you have moved it somewhere? -Can you tell me if you have replaced that with something I can use? (may be vertColor ? I saw it, but...) -Are you sure that what I use doesn't conflict with the 'work' of the new dynamic parameter? I leave my code unchanged by now: if I don't know where save original colors I can't do nothing, so PLEASE reply me asap. cheers |
|
From: Paolo C. <pao...@is...> - 2008-07-07 15:50:20
|
Dear developers I have just added the DynamicFloat type of parameter It is a floating point parameter that can be dynamically changed and that, hopefully, modify only partially the current mesh. You have to specify for that parameter the range of admitted values, and what the parameter changes on the mesh (e.g. the color, the vertex positions, the normals etc). For this parameter in the standard meshlab dialog for filter parameter you have a slider, when you drag the slider the mesh state is automatically restored to the initial state and after that the filter is applied. This allows the interactive exploration of some of the filter parameters. There is a new sample in the sampleplugins folder showing the intended use of this kind of parameter, it is called rather trivially samplefilterdyn @ Tonarelli The new color processing filters should use this kind of a approach. @Barney The same could hold also for the morphing plugins that could be refactored as filter instead of edit cheers Paolo (caveat: implementation is still partial, correctly works only for filters that dynamically change colors or positions of the mesh) -- Paolo Cignoni -- Senior Researcher Visual Computing Laboratory - ISTI - CNR http://vcg.isti.cnr.it/~cignoni ISTI - CNR Via Moruzzi 1, 56124 Pisa ITALY |
|
From: Francesco T. <lit...@gm...> - 2008-07-06 21:31:31
|
Hi Paolo, I commited a new version of my job. The filters that are in, are completed (just need some parameters tuning and descriptions) and seems to work fine. Of course the code needs refactoring and style changes...so don't worry about that! Please, get a look (you and/or Marco) and play with them, so you can decide if they like as they are, or if some changes are needed. I followed the algorithms in your link, but some effects in gimps works in a little different way. I wish ask you a meeting during this week, so I can explain better this, and I thing that we can fix a lot of other details. In the meantime I'll keep on working to other filters. cheers. |
|
From: Francesco T. <lit...@gm...> - 2008-07-04 13:17:37
|
Hi. >>read access is for everyone, but to commit stuff you need to be a >> meshlab developer >> make an account on sourceforge and then send me the id of that account. >> and I will add you to the list of developers I hope you refer to this... wiki account: username Little.tona ID 255 let me know when I can commit. >>And PLEASE read and follow carefully this page >> >> http://meshlab.sourceforge.net/wiki/index.php/Writing_Code ok. |
|
From: Paolo C. <pao...@is...> - 2008-07-04 11:17:12
|
Francesco Tonarelli wrote: > > Hi, Paolo > > thanks for your reply. A kept on working and have more questions. > > first of all, a problem. SVN asks me a password when I try to commit > my files. I get a look around in the wiki and didn't find a password > and I don't have used a password when checked out the repository, > almost this is wath I remember...something wrong in my settings? suggests? > read access is for everyone, but to commit stuff you need to be a meshlab developer make an account on sourceforge and then send me the id of that account. and I will add you to the list of developers And PLEASE read and follow carefully this page http://meshlab.sourceforge.net/wiki/index.php/Writing_Code > > 2: I have complete the brightness & contrast filter. I have > implemented this algorithm : > http://www.vbaccelerator.com/home/Vb/Code/vbMedia/Image_Processing/Brightness_and_Contrast/article.asp > > Brightness and Contrast are 2 differents algorithms; I understood > that you want these functionality in the same filter box, so I chained > the 2 filter one after the other: but the computations are not > 'commutative', so the order it's important. I suggest of implement 2 > stand alone filters. Let me know what you think about that. > As a suggestion, follow closely the behaviour of the GIMP brightness and contrast dialog. Look at how the histogram of the image is changed when the slider are moved and look at this description here http://pippin.gimp.org/image_processing/chap_point.html I hope that this week-end i will commit the required changes to the filterparameter and to the interfaces to allow dynamic sliders (so also morphing could be rewrote as a filter plugin instead of a edit one) Cheers p. -- Paolo Cignoni -- Senior Researcher Visual Computing Laboratory - ISTI - CNR http://vcg.isti.cnr.it/~cignoni ISTI - CNR Via Moruzzi 1, 56124 Pisa ITALY |
|
From: Francesco T. <lit...@gm...> - 2008-07-04 09:34:46
|
Hi, Paolo thanks for your reply. A kept on working and have more questions. first of all, a problem. SVN asks me a password when I try to commit my files. I get a look around in the wiki and didn't find a password and I don't have used a password when checked out the repository, almost this is wath I remember...something wrong in my settings? suggests? 2: I have complete the brightness & contrast filter. I have implemented this algorithm : http://www.vbaccelerator.com/home/Vb/Code/vbMedia/Image_Processing/Brightness_and_Contrast/article.asp Brightness and Contrast are 2 differents algorithms; I understood that you want these functionality in the same filter box, so I chained the 2 filter one after the other: but the computations are not 'commutative', so the order it's important. I suggest of implement 2 stand alone filters. Let me know what you think about that. thera are others bad things that derives from apply filters more times, but they a hard to explain now, by mail. I'll wait that you can try my work after I committed it. cheers. <https://lists.sourceforge.net/lists/listinfo/meshlab-devel> > > |
|
From: Paolo C. <pao...@is...> - 2008-07-04 00:24:09
|
Francesco Tonarelli wrote:
> Hi. I start to work to Color Processing filter and I yet finished the
> simplest one, i.e 'filling with a fixed color' (I don't have still
> commited it).
I hope that you gave a look at the file
vcg/complex/trimesh/update/colors.h...
>
> well, I've got some questions about filters organization.
>
> 1: all the filter types that I put in appears in the filters menu, but
> they are not grouped! How can I group them?
> I look at meshcolorize filters: the creation code is the same
> but filters appears grouped in the menu...
It depend on the "filter class"; from the interfaces.h
// The FilterClass describes in which generic class of filters it fits.
// This choice affect the submenu in which each filter will be placed
// For example filters that perform an action only on the selection
will be placed in the Selection Class Ôø?
virtual const FilterClass getClass(QAction *) { return
MeshFilterInterface::Generic; }
>
> 2: I need a place where I can put code of some action that always need
> to be performed at the launch of the filter (i.e to save a copy of the
> original colors per vertex).
> I do this in the initParameterSet() function. Is it right there
> or there is another initialization place where I can do it?
>
> just a note: in the standard dialog there is no way to undo and
> restore original settings. I understood that all my filters should use
> standard dialog, so I suppose that
> will discuss how to implement this feature in the next meeting...
>
True. I hope to succeed to start adding these functionalities to the
interfaces asap.
cheers
p.
> by, tanks.
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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
|
|
From: Francesco T. <lit...@gm...> - 2008-07-03 15:59:11
|
Hi. I start to work to Color Processing filter and I yet finished the
simplest one, i.e 'filling with a fixed color' (I don't have still commited
it).
well, I've got some questions about filters organization.
1: all the filter types that I put in appears in the filters menu, but they
are not grouped! How can I group them?
I look at meshcolorize filters: the creation code is the same but
filters appears grouped in the menu...
2: I need a place where I can put code of some action that always need to be
performed at the launch of the filter (i.e to save a copy of the original
colors per vertex).
I do this in the initParameterSet() function. Is it right there or
there is another initialization place where I can do it?
just a note: in the standard dialog there is no way to undo and restore
original settings. I understood that all my filters should use standard
dialog, so I suppose that
will discuss how to implement this feature in the next meeting...
by, tanks.
|
|
From: Paolo C. <pao...@is...> - 2008-07-02 21:39:47
|
Hi, have you look at the Compiling page? http://meshlab.sourceforge.net/wiki/index.php/Compiling It explains (among other things) how the additional libraries should be placed in the ''code' directories. We usually compile against qt 4.3.4 and various flavours of gcc (honestly most of them not as recent as yours) For other info about the linux compilation of meshlab you could find interesting this lengthy debian bug discussion http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426581 Assuming that you got both meshlab and vcglib freshly checkedout from svn, and looking at the error, it seems that there is a type clash that is not detected by our zoo of compilers... at line 419 typedef CurvatureDirType<float> CurvatureDirType; seems rather stupid. probably the struct above should have been called *CurvatureDirBaseType * instead of *CurvatureDirType *For me it still compile. Could you try to change it on your local copy and see if it compile? cheers and thanks for your bug submission Marco Paladini wrote: > Dear all, > I'm having errors compiling meshlab 1.1.1 release > and the same when compiling the svn version. > > In file included from ../../../sf/vcg/simplex/vertexplus/base.h:74, > from meshmodel.h:98, > from mainwindow.h:179, > from main.cpp:51: > ../../../sf/vcg/simplex/vertexplus/component.h:280: warning: type qualifiers ignored on function return type > ../../../sf/vcg/simplex/vertexplus/component.h:293: warning: type qualifiers ignored on function return type > ../../../sf/vcg/simplex/vertexplus/component.h:426: error: declaration of ‘typedef struct vcg::vert::CurvatureDirType<float> vcg::vert::EmptyCurvatureDir<TT>::CurvatureDirType’ > ../../../sf/vcg/simplex/vertexplus/component.h:416: error: changes meaning of ‘CurvatureDirType’ from ‘struct vcg::vert::CurvatureDirType<float>’ > > > Has this been fixed? how? > I'm using: > 2.6.25.6-55.fc9.i686 GNU/Linux > QMake version 2.01a > Using Qt version 4.4.0 in /usr/lib > g++ (GCC) 4.3.0 20080428 (Red Hat 4.3.0-8) > > > Also, I cannot find the svn version of the "code" directory.. > > > Thanks in advance > > > > Hai un indirizzo email difficile da ricordare? > Scegli quello che hai sempre desiderato su Yahoo! Mail > http://it.docs.yahoo.com/nuovo_indirizzo.html > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > 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 |
|
From: Marco P. <pal...@ya...> - 2008-07-02 17:18:07
|
Dear all,
I'm having errors compiling meshlab 1.1.1 release
and the same when compiling the svn version.
In file included from ../../../sf/vcg/simplex/vertexplus/base.h:74,
from meshmodel.h:98,
from mainwindow.h:179,
from main.cpp:51:
../../../sf/vcg/simplex/vertexplus/component.h:280: warning: type qualifiers ignored on function return type
../../../sf/vcg/simplex/vertexplus/component.h:293: warning: type qualifiers ignored on function return type
../../../sf/vcg/simplex/vertexplus/component.h:426: error: declaration of ‘typedef struct vcg::vert::CurvatureDirType<float> vcg::vert::EmptyCurvatureDir<TT>::CurvatureDirType’
../../../sf/vcg/simplex/vertexplus/component.h:416: error: changes meaning of ‘CurvatureDirType’ from ‘struct vcg::vert::CurvatureDirType<float>’
Has this been fixed? how?
I'm using:
2.6.25.6-55.fc9.i686 GNU/Linux
QMake version 2.01a
Using Qt version 4.4.0 in /usr/lib
g++ (GCC) 4.3.0 20080428 (Red Hat 4.3.0-8)
Also, I cannot find the svn version of the "code" directory..
Thanks in advance
Hai un indirizzo email difficile da ricordare?
Scegli quello che hai sempre desiderato su Yahoo! Mail
http://it.docs.yahoo.com/nuovo_indirizzo.html
|
|
From: Paolo C. <pao...@is...> - 2008-06-29 07:57:04
|
I have updated the pro of the collada io filter, again: there is no more anything like ../../sf/wrap/io_trimesh/import_dae.h vcg library when moved from cvs to svn is located in a vcglib based path so you shoud have writte ../../vcglib/wrap/io_trimesh/import_dae.h cheers p. PS - IMPORTANT! please update both meshlab and vcg library from the SVN (forget CVS) i have just committed some minimal changes in the collada stuff. skunkwerk wrote: > has anyone tried debugging meshlab on linux - i'm using gdb/ddd, but > am having trouble loading in the import_dae.h file, as ddd doesn't > recognize it as part of the program, ie. when I go to file -> open > source it's not listed as one of the files I can load. I used to be > able to get around this by simply loading mainwindow_RuntTime.cpp and > putting a breakpoint in the function that would eventually call the > file i was interested in, but that didn't work this time > > i didn't see any .h files specified in any of the .pro files in > meshlab, but when I added this to my /meshlab/src .pro file: > HEADERS = ../../sf/wrap/io_trimesh/import_dae.h > it still didn't detect any changes when I issued 'make all' > > any further suggestions? > > thanks, > imran > > On Fri, Jun 27, 2008 at 10:55 AM, Paolo Cignoni > <pao...@is... <mailto:pao...@is...>> wrote: > > skunkwerk wrote: >> thanks Paolo, >> >> 1) what do you mean by 'don't use the old sf path' - should the >> directory structure be different? > yes look at http://meshlab.sourceforge.net/wiki/index.php/Compiling > the standard path for the vcg lib stuff is no more something like > sf/wrap but vcglib/wrap >> 2) the file i'm changing is import_dae.h, for collada stuff > Great! i hoped that, >> 3) if you can give me a deadline of when the next release is >> planned for, I can try to commit the collada changes by then > I hope before mid july. I hope. > > cheers > p. > > >> >> i'll try adding it to the .pro file and try again >> >> yours, >> imran >> >> On Fri, Jun 27, 2008 at 1:59 AM, Paolo Cignoni >> <pao...@is... <mailto:pao...@is...>> wrote: >> >> Usually the stuff inside vcglib (do not use anymore the old >> "sf" path) should be reasonably static and it should not be >> changed very frequently. >> >> In the case you need to experiment on a particular file of >> the vcglib simply add that .h file of the vcglib that you are >> changing into the header section of your pro file (apropos >> use the standard way of making .pro files that uses a common >> .pri file with all the common stuff). >> >> by the way what file of the vcglib are you changing and why? >> >> >> Off topic: >> If i well remember, you had corrected some bugs of the >> collada importing library but i do not remember exactly if >> you committed all the changes that you have done. >> Could you check it? >> >> cheers >> >> P. >> >> >> >> >> skunkwerk wrote: >>> i'm still having trouble with the make system for meshlab - >>> whenever I make a change in /devel/sf/wrap/ somewhere and do >>> a 'make all' it doesn't detect any changes, so I have to do >>> a 'make clean' and then a 'make all' again which takes a >>> good 20 minutes. it would save me an invaluable amount of >>> time if someone could tell me how to fix this... or suggest >>> a workaround >>> >>> this is on linux >>> >>> thanks, >>> imran >>> ------------------------------------------------------------------------ >>> >>> ------------------------------------------------------------------------- >>> Check out the new SourceForge.net Marketplace. >>> It's the best place to buy or sell services for >>> just about anything Open Source. >>> http://sourceforge.net/services/buy/index.php >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Meshlab-devel mailing list >>> Mes...@li... <mailto: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 <http://vcg.isti.cnr.it/%7Ecignoni> >> >> ISTI - CNR >> Via Moruzzi 1, >> 56124 Pisa >> ITALY >> >> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://sourceforge.net/services/buy/index.php >> _______________________________________________ >> Meshlab-devel mailing list >> Mes...@li... >> <mailto:Mes...@li...> >> https://lists.sourceforge.net/lists/listinfo/meshlab-devel >> >> >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://sourceforge.net/services/buy/index.php >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Meshlab-devel mailing list >> Mes...@li... <mailto: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 <http://vcg.isti.cnr.it/%7Ecignoni> > > ISTI - CNR > Via Moruzzi 1, > 56124 Pisa > ITALY > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Meshlab-devel mailing list > Mes...@li... > <mailto:Mes...@li...> > https://lists.sourceforge.net/lists/listinfo/meshlab-devel > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > > ------------------------------------------------------------------------ > > _______________________________________________ > 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 |
|
From: skunkwerk <sku...@gm...> - 2008-06-29 03:46:52
|
has anyone tried debugging meshlab on linux - i'm using gdb/ddd, but am having trouble loading in the import_dae.h file, as ddd doesn't recognize it as part of the program, ie. when I go to file -> open source it's not listed as one of the files I can load. I used to be able to get around this by simply loading mainwindow_RuntTime.cpp and putting a breakpoint in the function that would eventually call the file i was interested in, but that didn't work this time i didn't see any .h files specified in any of the .pro files in meshlab, but when I added this to my /meshlab/src .pro file: HEADERS = ../../sf/wrap/io_trimesh/import_dae.h it still didn't detect any changes when I issued 'make all' any further suggestions? thanks, imran On Fri, Jun 27, 2008 at 10:55 AM, Paolo Cignoni <pao...@is...> wrote: > skunkwerk wrote: > > thanks Paolo, > > 1) what do you mean by 'don't use the old sf path' - should the directory > structure be different? > > yes look at http://meshlab.sourceforge.net/wiki/index.php/Compiling > the standard path for the vcg lib stuff is no more something like sf/wrap > but vcglib/wrap > > 2) the file i'm changing is import_dae.h, for collada stuff > > Great! i hoped that, > > 3) if you can give me a deadline of when the next release is planned for, > I can try to commit the collada changes by then > > I hope before mid july. I hope. > > cheers > p. > > > > i'll try adding it to the .pro file and try again > > yours, > imran > > On Fri, Jun 27, 2008 at 1:59 AM, Paolo Cignoni <pao...@is...> > wrote: > >> Usually the stuff inside vcglib (do not use anymore the old "sf" path) >> should be reasonably static and it should not be changed very frequently. >> >> In the case you need to experiment on a particular file of the vcglib >> simply add that .h file of the vcglib that you are changing into the header >> section of your pro file (apropos use the standard way of making .pro files >> that uses a common .pri file with all the common stuff). >> >> by the way what file of the vcglib are you changing and why? >> >> >> Off topic: >> If i well remember, you had corrected some bugs of the collada importing >> library but i do not remember exactly if you committed all the changes that >> you have done. >> Could you check it? >> >> cheers >> >> P. >> >> >> >> >> skunkwerk wrote: >> >> i'm still having trouble with the make system for meshlab - whenever I >> make a change in /devel/sf/wrap/ somewhere and do a 'make all' it doesn't >> detect any changes, so I have to do a 'make clean' and then a 'make all' >> again which takes a good 20 minutes. it would save me an invaluable amount >> of time if someone could tell me how to fix this... or suggest a workaround >> >> this is on linux >> >> thanks, >> imran >> >> ------------------------------ >> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source.http://sourceforge.net/services/buy/index.php >> >> ------------------------------ >> >> _______________________________________________ >> Meshlab-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/meshlab-devel >> >> >> >> -- >> Paolo Cignoni -- Senior Researcher >> Visual Computing Laboratory - ISTI - CNR http://vcg.isti.cnr.it/~cignoni <http://vcg.isti.cnr.it/%7Ecignoni> >> >> ISTI - CNR >> Via Moruzzi 1, >> 56124 Pisa >> ITALY >> >> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://sourceforge.net/services/buy/index.php >> _______________________________________________ >> Meshlab-devel mailing list >> Mes...@li... >> https://lists.sourceforge.net/lists/listinfo/meshlab-devel >> >> > ------------------------------ > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source.http://sourceforge.net/services/buy/index.php > > ------------------------------ > > _______________________________________________ > Meshlab-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/meshlab-devel > > > > -- > Paolo Cignoni -- Senior Researcher > Visual Computing Laboratory - ISTI - CNR http://vcg.isti.cnr.it/~cignoni <http://vcg.isti.cnr.it/%7Ecignoni> > > ISTI - CNR > Via Moruzzi 1, > 56124 Pisa > ITALY > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Meshlab-devel mailing list > Mes...@li... > https://lists.sourceforge.net/lists/listinfo/meshlab-devel > > |
|
From: Paolo C. <pao...@is...> - 2008-06-27 17:55:50
|
skunkwerk wrote: > thanks Paolo, > > 1) what do you mean by 'don't use the old sf path' - should the > directory structure be different? yes look at http://meshlab.sourceforge.net/wiki/index.php/Compiling the standard path for the vcg lib stuff is no more something like sf/wrap but vcglib/wrap > 2) the file i'm changing is import_dae.h, for collada stuff Great! i hoped that, > 3) if you can give me a deadline of when the next release is planned > for, I can try to commit the collada changes by then I hope before mid july. I hope. cheers p. > > i'll try adding it to the .pro file and try again > > yours, > imran > > On Fri, Jun 27, 2008 at 1:59 AM, Paolo Cignoni > <pao...@is... <mailto:pao...@is...>> wrote: > > Usually the stuff inside vcglib (do not use anymore the old "sf" > path) should be reasonably static and it should not be changed > very frequently. > > In the case you need to experiment on a particular file of the > vcglib simply add that .h file of the vcglib that you are changing > into the header section of your pro file (apropos use the standard > way of making .pro files that uses a common .pri file with all the > common stuff). > > by the way what file of the vcglib are you changing and why? > > > Off topic: > If i well remember, you had corrected some bugs of the collada > importing library but i do not remember exactly if you committed > all the changes that you have done. > Could you check it? > > cheers > > P. > > > > > skunkwerk wrote: >> i'm still having trouble with the make system for meshlab - >> whenever I make a change in /devel/sf/wrap/ somewhere and do a >> 'make all' it doesn't detect any changes, so I have to do a 'make >> clean' and then a 'make all' again which takes a good 20 >> minutes. it would save me an invaluable amount of time if >> someone could tell me how to fix this... or suggest a workaround >> >> this is on linux >> >> thanks, >> imran >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://sourceforge.net/services/buy/index.php >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Meshlab-devel mailing list >> Mes...@li... <mailto: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 <http://vcg.isti.cnr.it/%7Ecignoni> > > ISTI - CNR > Via Moruzzi 1, > 56124 Pisa > ITALY > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Meshlab-devel mailing list > Mes...@li... > <mailto:Mes...@li...> > https://lists.sourceforge.net/lists/listinfo/meshlab-devel > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > > ------------------------------------------------------------------------ > > _______________________________________________ > 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 |
|
From: skunkwerk <sku...@gm...> - 2008-06-27 16:00:22
|
thanks Paolo, 1) what do you mean by 'don't use the old sf path' - should the directory structure be different? 2) the file i'm changing is import_dae.h, for collada stuff 3) if you can give me a deadline of when the next release is planned for, I can try to commit the collada changes by then i'll try adding it to the .pro file and try again yours, imran On Fri, Jun 27, 2008 at 1:59 AM, Paolo Cignoni <pao...@is...> wrote: > Usually the stuff inside vcglib (do not use anymore the old "sf" path) > should be reasonably static and it should not be changed very frequently. > > In the case you need to experiment on a particular file of the vcglib > simply add that .h file of the vcglib that you are changing into the header > section of your pro file (apropos use the standard way of making .pro files > that uses a common .pri file with all the common stuff). > > by the way what file of the vcglib are you changing and why? > > > Off topic: > If i well remember, you had corrected some bugs of the collada importing > library but i do not remember exactly if you committed all the changes that > you have done. > Could you check it? > > cheers > > P. > > > > > skunkwerk wrote: > > i'm still having trouble with the make system for meshlab - whenever I make > a change in /devel/sf/wrap/ somewhere and do a 'make all' it doesn't detect > any changes, so I have to do a 'make clean' and then a 'make all' again > which takes a good 20 minutes. it would save me an invaluable amount of > time if someone could tell me how to fix this... or suggest a workaround > > this is on linux > > thanks, > imran > > ------------------------------ > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source.http://sourceforge.net/services/buy/index.php > > ------------------------------ > > _______________________________________________ > Meshlab-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/meshlab-devel > > > > -- > Paolo Cignoni -- Senior Researcher > Visual Computing Laboratory - ISTI - CNR http://vcg.isti.cnr.it/~cignoni <http://vcg.isti.cnr.it/%7Ecignoni> > > ISTI - CNR > Via Moruzzi 1, > 56124 Pisa > ITALY > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Meshlab-devel mailing list > Mes...@li... > https://lists.sourceforge.net/lists/listinfo/meshlab-devel > > |
|
From: Paolo C. <pao...@is...> - 2008-06-27 08:59:59
|
Usually the stuff inside vcglib (do not use anymore the old "sf" path) should be reasonably static and it should not be changed very frequently. In the case you need to experiment on a particular file of the vcglib simply add that .h file of the vcglib that you are changing into the header section of your pro file (apropos use the standard way of making .pro files that uses a common .pri file with all the common stuff). by the way what file of the vcglib are you changing and why? Off topic: If i well remember, you had corrected some bugs of the collada importing library but i do not remember exactly if you committed all the changes that you have done. Could you check it? cheers P. skunkwerk wrote: > i'm still having trouble with the make system for meshlab - whenever I > make a change in /devel/sf/wrap/ somewhere and do a 'make all' it > doesn't detect any changes, so I have to do a 'make clean' and then a > 'make all' again which takes a good 20 minutes. it would save me an > invaluable amount of time if someone could tell me how to fix this... > or suggest a workaround > > this is on linux > > thanks, > imran > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > > ------------------------------------------------------------------------ > > _______________________________________________ > 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 |
|
From: skunkwerk <sku...@gm...> - 2008-06-27 04:09:17
|
i'm still having trouble with the make system for meshlab - whenever I make a change in /devel/sf/wrap/ somewhere and do a 'make all' it doesn't detect any changes, so I have to do a 'make clean' and then a 'make all' again which takes a good 20 minutes. it would save me an invaluable amount of time if someone could tell me how to fix this... or suggest a workaround this is on linux thanks, imran |
|
From: Paolo C. <pao...@is...> - 2008-06-25 21:56:22
|
skunkwerk wrote: > hi Paolo, > i was looking at software that could do normal mapping and noticed > it was listed as one of the plugin projects in meshlab. > > is anyone working on it yet? anyone else interested in helping? > > I read your paper on normal mapping from a few years ago. Do I need > to get the texture atlas plugin fixed before starting on the detail > transfer? > yes complete the texture atlas first. about the redetailing stuff: it is almost in. If you look at the new filter_sampling tool you can find all the basic pieces: closest retrieval and texel sampling. I think that adding a attribute transfer is matter of a few lines of code. consider it already done. (yes i have to remove it from the projecgts :) ) p. > > imran > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > > ------------------------------------------------------------------------ > > _______________________________________________ > 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 |
|
From: skunkwerk <sku...@gm...> - 2008-06-25 20:02:42
|
hi Paolo,
i was looking at software that could do normal mapping and noticed it
was listed as one of the plugin projects in meshlab.
is anyone working on it yet? anyone else interested in helping?
I read your paper on normal mapping from a few years ago. Do I need to get
the texture atlas plugin fixed before starting on the detail transfer?
i couldn't find much information on the procedure online or in books - when
rendering, do you just do regular phong/gouraud shading, or is there
additional complexity involved?
imran
|
|
From: claudio i. <imb...@cl...> - 2008-06-25 08:54:36
|
> Of some other projects I have no update. Could the interested ones > report a bit on their status? > > MeshLab server (imbrenda) bit of report: still nothing done. As I already said (to prof. Cignoni, in private), I had too many things to do and unfortunately meshlabserver was one of the things I had to postpone. In the current situation I am not capable of completing meshlabserver in reasonable time. Feel free to reassign it to whoever can do it. I will take another task when I will have some more time. Cheers Claudio Imbrenda -- This space intentionally has nothing but text explaining why this space has nothing but text explaining that this space would otherwise have been left blank, and would otherwise have been left blank. . |
|
From: skunkwerk <sku...@gm...> - 2008-06-24 16:37:05
|
morning Paolo,
i haven't worked on the filter texture plugin since the last commit - as
it currently stands, it just needs to be debugged, as most of the
implementation is there. the code is commented, but i could write a wiki
page explaining the algorithm i was trying to implement. but i don't think
i'll be able to fix it right now...
thanks,
imran
On Mon, Jun 23, 2008 at 8:19 AM, Paolo Cignoni <pao...@is...>
wrote:
> Dear all
>
> I would like to know the current status and planned evolution on some
> plugins whose developement has started but not yet ended, just to have a
> forecast on when (and if) they will be ready for inclusion in the next
> release
>
> edit_quality
> filter_texture (the atlasing..)
>
> In the mean time the following plugins have reached a reasonable
> stability state so i encourage all the devs to try them and report news
> on the them here
>
> All of them have (or they should have) a page on the wiki so it should
> be reasonable to basically understand them
>
> # Texture Parametrization Tool. Tool to inspect and modify texture
> parametrizations
> # Straightener: a easy to use tool to interactively set reference frames
> (or in other words to straighten up a randomly oriented mesh).
> # mesh optimization filters; tools for optimizing the
> aspect-ratio/curvature
> # geometric erosion filter; a tool for aging a mesh, creating dents on it.
> # The new painting tool
>
> Any comments on these plugins is really welcome.
>
>
> Of some other projects I have no update. Could the interested ones
> report a bit on their status?
>
> MeshLab server (imbrenda)
> Generative mesh instancing filter (raglianti)
> Function Filter (alemanno)
> Improved Slicing Tool (pocci)
> Dirty maker filter (Bartoletti)
>
> Cheers
>
> P.
>
> --
> Paolo Cignoni -- Senior Researcher
> Visual Computing Laboratory - ISTI - CNR
> http://vcg.isti.cnr.it/~cignoni <http://vcg.isti.cnr.it/%7Ecignoni>
>
> ISTI - CNR
> Via Moruzzi 1,
> 56124 Pisa
> ITALY
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Meshlab-devel mailing list
> Mes...@li...
> https://lists.sourceforge.net/lists/listinfo/meshlab-devel
>
|
|
From: Paolo C. <pao...@is...> - 2008-06-23 15:20:55
|
Dear all I would like to know the current status and planned evolution on some plugins whose developement has started but not yet ended, just to have a forecast on when (and if) they will be ready for inclusion in the next release edit_quality filter_texture (the atlasing..) In the mean time the following plugins have reached a reasonable stability state so i encourage all the devs to try them and report news on the them here All of them have (or they should have) a page on the wiki so it should be reasonable to basically understand them # Texture Parametrization Tool. Tool to inspect and modify texture parametrizations # Straightener: a easy to use tool to interactively set reference frames (or in other words to straighten up a randomly oriented mesh). # mesh optimization filters; tools for optimizing the aspect-ratio/curvature # geometric erosion filter; a tool for aging a mesh, creating dents on it. # The new painting tool Any comments on these plugins is really welcome. Of some other projects I have no update. Could the interested ones report a bit on their status? MeshLab server (imbrenda) Generative mesh instancing filter (raglianti) Function Filter (alemanno) Improved Slicing Tool (pocci) Dirty maker filter (Bartoletti) Cheers P. -- Paolo Cignoni -- Senior Researcher Visual Computing Laboratory - ISTI - CNR http://vcg.isti.cnr.it/~cignoni ISTI - CNR Via Moruzzi 1, 56124 Pisa ITALY |
|
From: skunkwerk <sku...@gm...> - 2008-06-03 15:27:49
|
you may be wondering why i've been spending time working on meshlab... a friend and i started a 3d web service that relies heavily on meshlab on the backend: www.shadowpush.com you'll find meshlab mentioned on the 'open source' page suggestions and feedback welcome thanks to all for your help, imran |
