From: Roger <tk...@12...> - 2006-10-11 13:42:50
|
Hi,everyone I use vtk for 3d rendering. I want to know how to save the vtk window as a image in vtk. Thanks Roger |
From: Jim G. <jgreen@RobotVision.com> - 2006-10-12 16:30:18
|
Again, I'm very new to vxl. As vxl uses cvs, I want to use that too to be compatible with what everyone else does. I've never used cvs before and have a few simple questions about using cvs with vxl (in particular WinCVS and cvsnt). I've been reading the cvsnt documentation, but there are some things that aren't clear, at least as it applies to vxl. Comments or answers will be greatly appreciated. I (apparently) successfully downloaded a working copy of vxl from the repository at sourceforge.net using WinCVS. It (apparently) built OK and runs OK, at least the parts I have tried so far. (Thanks to several of you for your suggestions and help in getting this working.) 1) I assume that the vxl "repository" (the term used in the cvsnt documentation) is at soruceforge,net? 2) I assume that my vxl "working copy" (the term used in the cvsnt documentation) is where I downloaded the source tree from sourceforge.net, that is, D:\cvsroot\vxl on my disk? If these two statements are not correct, then I don't understand what I've read in the cvsnt documentation. Otherwise: 3) The documentation suggests that when I downloaded vxl from sourceforge.net to D:\cvsroot\vxl on my disk, it was "checked out" from sourceforge,net, and I don't need to "check out" files any further from my D:\cvsroot\vxl? The statement in (3) may not be correct and may be causing me confusion because: 4) If I don't need to "check out" files any further from my local "working copy", how do I "check in" changes I make to my local "working copy" at D:\cvsroot\vxl (I'm NOT talking about checking in to the sourceforge.net "repository")? That is, what I want to do is use cvs to track local changes and additions I make to my local working copy here, but not try to check them in to the sourceforge,net repository, at least not for now. Or do I need to do another checkout to a private working copy on my disk and then check changes back in to the working copy at D:\cvsroot\vxl? Thanks for you help, Jim Green ------------------------------------------------ |
From: Peter V. <pet...@ya...> - 2006-10-13 06:04:44
|
--- Jim Green <jgreen@RobotVision.com> skrev: > 1) I assume that the vxl "repository" is at sourceforge.net? Yes. That's the cvs term used in general. > 2) I assume that my vxl "working copy" is D:\cvsroot\vxl on my disk? Yes. > 3) I don't need to "check out" files any further from my D:\cvsroot\vxl? Right. > 4) how do I "check in" changes I make to my local "working copy" at D:\cvsroot\vxl The term "check in" is only used to submit changes to the repository. To do what you want, just change the files in D:\cvsroot\vxl. If you want to see later on which are the changes between your file(s) and the repository version you started from, just say "cvs diff". If you want to incorporate any further changes on the repository without loosing your own changes, just say "cvs update". -- Peter. |
From: Ian S. <ian...@st...> - 2006-10-12 16:50:10
|
Jim Green wrote: > Again, I'm very new to vxl. As vxl uses cvs, I want to use that too > to be compatible with what everyone else does. I've never used cvs > before and have a few simple questions about using cvs with vxl (in > particular WinCVS and cvsnt). I've been reading the cvsnt > documentation, but there are some things that aren't clear, at least > as it applies to vxl. Comments or answers will be greatly appreciated. > > I (apparently) successfully downloaded a working copy of vxl from the > repository at sourceforge.net using WinCVS. It (apparently) built OK > and runs OK, at least the parts I have tried so far. (Thanks to > several of you for your suggestions and help in getting this working.) > > 1) I assume that the vxl "repository" (the term used in the cvsnt > documentation) is at soruceforge,net? Correct. > 2) I assume that my vxl "working copy" (the term used in the cvsnt > documentation) is where I downloaded the source tree from > sourceforge.net, that is, D:\cvsroot\vxl on my disk? Correct. > If these two statements are not correct, then I don't understand what > I've read in the cvsnt documentation. Otherwise: > > 3) The documentation suggests that when I downloaded vxl from > sourceforge.net to D:\cvsroot\vxl on my disk, it was "checked out" > from sourceforge,net, and I don't need to "check out" files any > further from my D:\cvsroot\vxl? Correct. Checked out, merely means that you have downloaded it from the repository to your working copy. > The statement in (3) may not be correct and may be causing me > confusion because: > > 4) If I don't need to "check out" files any further from my local > "working copy", how do I "check in" changes I make to my local > "working copy" at D:\cvsroot\vxl (I'm NOT talking about checking in > to the sourceforge.net "repository")? You don't check-in changes to your local working copy. You just make changes in your local working copy using a text editor. > That is, what I want to do is use cvs to track local changes and > additions I make to my local working copy here, but not try to check > them in to the sourceforge,net repository, at least not for now. Or > do I need to do another checkout to a private working copy on my disk > and then check changes back in to the working copy at D:\cvsroot\vxl? Any cvs client will help you keep track of the differences between your copy and the particular version you originally downloaded from the repository. It can also help you merge new changes in the repository into your locally modified working copy. Keeping track of individual changes locally on your workstation would mean that you have to run your own repository. Not particularly difficult at first, though synchronising such a repository with the official one at SF is definitely non-trivial. I guess most GUI clients support local repositories (all command-line clients certainly do), but you might need to run a few command line tools in order to set up the repository in the first place. That said, I don't imagine that any of the vxl-maintainers would recommend running your own parallel repository. Such a repository appears to make sense when amortised over a larger team, but people who have tried it in the past have abandoned it sooner or later. FYI, When I asked around our office, TortoiseCVS is far and away the most highly recommended GUI CVS client for windows. Ian. |
From: Jim G. <jgreen@RobotVision.com> - 2006-10-12 17:14:44
|
Ian, Thanks again for you very clear comments/answers. It seems that I am doing almost the right thing. If I download and isntall TortoiseCVS, should I delete the local working copy vxl tree that I downloaded with WinCVS and re-download a new working copy with TortoiseCVS from sourceforge.net? Thanks for your help, Jim Green ------------------------------------------ At 12:49 PM 10/12/2006, Ian Scott wrote: >Jim Green wrote: >>Again, I'm very new to vxl. As vxl uses cvs, I want to use that >>too to be compatible with what everyone else does. I've never used >>cvs before and have a few simple questions about using cvs with vxl >>(in particular WinCVS and cvsnt). I've been reading the cvsnt >>documentation, but there are some things that aren't clear, at >>least as it applies to vxl. Comments or answers will be greatly appreciated. >>I (apparently) successfully downloaded a working copy of vxl from >>the repository at sourceforge.net using WinCVS. It (apparently) >>built OK and runs OK, at least the parts I have tried so >>far. (Thanks to several of you for your suggestions and help in >>getting this working.) >>1) I assume that the vxl "repository" (the term used in the cvsnt >>documentation) is at soruceforge,net? > >Correct. > >>2) I assume that my vxl "working copy" (the term used in the cvsnt >>documentation) is where I downloaded the source tree from >>sourceforge.net, that is, D:\cvsroot\vxl on my disk? > >Correct. > >>If these two statements are not correct, then I don't understand >>what I've read in the cvsnt documentation. Otherwise: >> >>3) The documentation suggests that when I downloaded vxl from >>sourceforge.net to D:\cvsroot\vxl on my disk, it was "checked out" >>from sourceforge,net, and I don't need to "check out" files any >>further from my D:\cvsroot\vxl? > >Correct. Checked out, merely means that you have downloaded it from >the repository to your working copy. > >>The statement in (3) may not be correct and may be causing me >>confusion because: >>4) If I don't need to "check out" files any further from my local >>"working copy", how do I "check in" changes I make to my local >>"working copy" at D:\cvsroot\vxl (I'm NOT talking about checking in >>to the sourceforge.net "repository")? > >You don't check-in changes to your local working copy. You just make >changes in your local working copy using a text editor. > >>That is, what I want to do is use cvs to track local changes and >>additions I make to my local working copy here, but not try to >>check them in to the sourceforge,net repository, at least not for >>now. Or do I need to do another checkout to a private working copy >>on my disk and then check changes back in to the working copy at >>D:\cvsroot\vxl? > >Any cvs client will help you keep track of the differences between >your copy and the particular version you originally downloaded from >the repository. It can also help you merge new changes in the >repository into your locally modified working copy. > >Keeping track of individual changes locally on your workstation >would mean that you have to run your own repository. Not >particularly difficult at first, though synchronising such a >repository with the official one at SF is definitely non-trivial. I >guess most GUI clients support local repositories (all command-line >clients certainly do), but you might need to run a few command line >tools in order to set up the repository in the first place. > >That said, I don't imagine that any of the vxl-maintainers would >recommend running your own parallel repository. Such a repository >appears to make sense when amortised over a larger team, but people >who have tried it in the past have abandoned it sooner or later. > >FYI, When I asked around our office, TortoiseCVS is far and away the >most highly recommended GUI CVS client for windows. > >Ian. |
From: Ian S. <ian...@st...> - 2006-10-12 17:22:35
|
Jim Green wrote: > Ian, > > Thanks again for you very clear comments/answers. It seems that I am > doing almost the right thing. If I download and isntall TortoiseCVS, > should I delete the local working copy vxl tree that I downloaded with > WinCVS and re-download a new working copy with TortoiseCVS from > sourceforge.net? I'm afraid I don't know much about CvsNT. IIRC tortoiseCVS working copy structure is the same as standard command line cvs. If each directory in your current working copy has a CVS sub-directory containing files called Entries Repository and Root, then there is a good chance it will work. Ian. |