KitwarePublic - Recent changes [en]

IGSTK/Git/Develop

2012-05-18T17:55:47Z

← Older revision		Revision as of 17:55, 18 May 2012
Line 42:		Line 42:
	[http://progit.org/book/ch1-5.html Pro Git: Setup]		[http://progit.org/book/ch1-5.html Pro Git: Setup]
	\|}		\|}
		+
		+	==Add Testing Data==

	==Workflow==		==Workflow==

VTK/Examples/Cxx/Meshes/Subdivision

2012-05-18T14:19:49Z

← Older revision		Revision as of 14:19, 18 May 2012
Line 77:		Line 77:
	for(unsigned i = 0; i < numberOfViewports; i++)		for(unsigned i = 0; i < numberOfViewports; i++)
	{		{
		+	// Note: Here we create a superclass pointer (vtkPolyDataAlgorithm) so that we can easily instantiate different
		+	// types of subdivision filters. Typically you would not want to do this, but rather create the pointer to be the type
		+	// filter you will actually use, e.g.
		+	// vtkSmartPointer<vtkLinearSubdivisionFilter> subdivisionFilter = vtkSmartPointer<vtkLinearSubdivisionFilter>::New();
	vtkSmartPointer<vtkPolyDataAlgorithm> subdivisionFilter;		vtkSmartPointer<vtkPolyDataAlgorithm> subdivisionFilter;
	switch(i)		switch(i)

CMake:CPackNSISAdvancedTips

2012-05-17T20:45:07Z

Newly Created

New page

=CPack NSIS Advanced Tips=
Those who are comfortable with both CMake/CPack and NSIS may wish to customize their own NSIS scripts to pass through CPack.

==NSIS script file creation==
When CPack uses the NSIS generator, it reads the following files from the modules path:
NSIS.template.in
NSIS.InstallOptions.ini.in

CPack fills in the variables and outputs it to this directory:
${CMAKE_BINARY_DIR}\_CPack_Packages\${CPACK_TOPLEVEL_TAG}\${CPACK_GENERATOR}\

Both files get their name changed to
Project.nsi
NSIS.InstallOptions.ini

To start work on a custom NSIS script, simply create a file (or copy) into your module path (e.g. CPACK_MODULE_PATH) called NSIS.template.in. CPack will automatically use your path over the default one.

'''NOTE:''' It may be tempting to create custom Install options using NSIS.InstallOptions.ini.in, but it is '''NOT''' recommended. CPack uses this file to provide the option of modifying the PATH environment variable. Modifying this file or the references to it within NSIS.template.in may render this option useless. If custom InstallOptions files are desired, read the next section.

==Integrating Custom InstallOptions files ==
At first glance, integrating a custom option file appears to be difficult, since CPack copies 2 specific files to a separate generated directory. However, integration is really quite simple.

With the NSIS.template.in, look for the Function .onInit Within this function insert the following line:
!insertmacro INSTALLOPTIONS_EXTRACT_AS "@MY_PATH_TO_FILE@\@MY_FILENAME@" "@MY_FILENAME@"

Next, look for a section that says ReserveFile. Again, just add the line:
ReserveFile "@MY_PATH_TO_FILE@\@MY_FILENAME@"

Don't forget to define MY_PATH_TO_FILE and MY_FILENAME in either your CPackConfig file or your CMakeLists.txt

Now, @MY_FILENAME@ can be referenced directly anywhere in the script.

CMake:CPackPackageGenerators

2012-05-17T20:44:44Z

NSIS: Added a link to the newly created CPackNSISAdvancedTips page.

← Older revision		Revision as of 20:44, 17 May 2012
Line 50:		Line 50:
	==NSIS==		==NSIS==

-	Nullsoft Installer. Requires [http://nsis.sourceforge.net/ NSIS] for creating the package.	+	Nullsoft Installer. Requires [http://nsis.sourceforge.net/ NSIS] for creating the package. See the [[CMake:CPackNSISAdvancedTips\|Advanced Tips]] for details on customizing an NSIS script through CPack.

	=== NSIS Generator Specifics settings ===		=== NSIS Generator Specifics settings ===

VTK/Image Rendering Classes

2012-05-17T18:19:15Z

← Older revision		Revision as of 18:19, 17 May 2012
Line 5:		Line 5:

	These classes were merged into VTK on March 15, 2011. Major updates were added on June 26, 2011.		These classes were merged into VTK on March 15, 2011. Major updates were added on June 26, 2011.
		+
		+	These classes are part of VTK 5.10 and later releases of VTK.

	== Proposal ==		== Proposal ==

IGSTK/Git/Download

2012-05-17T14:40:23Z

Clone:

← Older revision		Revision as of 14:40, 17 May 2012
(One intermediate revision not shown)
Line 20:		Line 20:
	\|-		\|-
	\|		\|
-	If you want to run tests, get the <code>Testing/Data</code> submodule:	+	If you want to run tests, get the <code>Testing/Data</code> submodule. First, change directory to the location where the source code is installed and then issue the git command:
	\|-		\|-
	\|		\|

CMake/CPack/Examples/Linux/DEB

2012-05-16T21:22:42Z

← Older revision		Revision as of 21:22, 16 May 2012
Line 1:		Line 1:
		+	Note that this VTK example is simply a filler so we can do VTK packaging in the CMake (below).
		+
	==DistanceBetweenPoints.cxx==		==DistanceBetweenPoints.cxx==
	<source lang="cpp">		<source lang="cpp">

VTK XML Formats

2012-05-16T19:20:56Z

Compressed Data:

← Older revision		Revision as of 19:20, 16 May 2012
(6 intermediate revisions not shown)
Line 5:		Line 5:
	The top-level document element of any VTK XML file is called "VTKFile":		The top-level document element of any VTK XML file is called "VTKFile":

-	<VTKFile type="..." byte_order="<i>byte-order</i>">	+	<VTKFile type="..." version="<i>version</i>" byte_order="<i>byte-order</i>" ...>
	<i>...rest of file...</i>		<i>...rest of file...</i>
	</VTKFile>		</VTKFile>

-	The byte order specified may be either "LittleEndian" or "BigEndian" and indicates the byte order used for any binary data in the file.	+	The <code><i>version</i></code> number is specific to each type of data set represented in the file.
		+	For normal (non-composite) data set types possible version numbers are:
		+	* <code>0.1</code>: Readable by VTK >= 4
		+	* <code>1.0</code>: Readable by VTK >= 6
		+
		+	The <code><i>byte-order</i></code> specified may be either "<code>LittleEndian</code>" or "<code>BigEndian</code>" and indicates the byte order used for any binary data in the file.
		+
		+	File format version 1.0 supports an additional <code>VTKFile</code> attribute:
		+
		+	<VTKFile ... version="1.0" ... header_type="<i>header-type</i>">
		+
		+	The <code><i>header-type</i></code> specified may be either "<code>UInt32</code>" or "<code>UInt64</code>" and indicates the integer type used in binary data headers (see below).
		+	If no such attribute is specified (as in version 0.1) the header type is <code>UInt32</code>.

	=Appended Data Section=		=Appended Data Section=
Line 34:		Line 46:
	A block representing a data array without compression has this format:		A block representing a data array without compression has this format:

-	~~NNNN~~<i>[DATA]</i>	+	[#bytes]<i>[DATA]</i>

-	where "~~NNNN~~" is ~~a 32-bit unsigned~~ integer value specifying the number of <b>bytes</b> in the block of data following it. The rest of the data immediately follow it. The byte count and all data are in the byte order specified by the "byte_order" attribute at the top of the file. In general a raw, uncompressed AppendedData element has the form	+	where "[#bytes]" is an integer value specifying the number of <b>bytes</b> in the block of data following it.
		+	The rest of the data immediately follow it.
		+	The byte count integer type is specified by the "<code>header_type</code>" attribute at the top of the file (<code>UInt32</code> if no type specified).
		+	The byte count and all data are in the byte order specified by the "<code>byte_order</code>" attribute at the top of the file.
		+	In general a raw, uncompressed AppendedData element has the form

	<AppendedData encoding="raw">		<AppendedData encoding="raw">
Line 42:		Line 58:
	</AppendedData>		</AppendedData>

-	where the "<n1>"-style tokens indicate 32-~~bit unsigned~~ integer byte counts and "<data1>"-style tokens indicate the corresponding blocks of binary data.	+	where the "<n1>"-style tokens indicate <code>header_type</code>-d integer byte counts and "<data1>"-style tokens indicate the corresponding blocks of binary data.

	==Compressed Data==		==Compressed Data==
Line 54:		Line 70:
	[#blocks][#u-size][#p-size][#c-size-1][#c-size-2]...[#c-size-#blocks]<i>[DATA]</i>		[#blocks][#u-size][#p-size][#c-size-1][#c-size-2]...[#c-size-#blocks]<i>[DATA]</i>

-	Each token is ~~a 32-bit unsigned~~ integer value. The token meanings are:	+	Each token is an integer value whose type is specified by "<code>header_type</code>" at the top of the file (<code>UInt32</code> if no type specified).
		+	The token meanings are:

	[#blocks] = Number of blocks		[#blocks] = Number of blocks

VTK/Remove BTX ETX

2012-05-16T16:39:50Z

The solution: How to completely remove BTX/ETX:

← Older revision		Revision as of 16:39, 16 May 2012
Line 32:		Line 32:

	# All .h files included by the wrapped header file must be parsed and their contents temporarily stored by the wrapper tools. Note that these included headers will only be parsed, not wrapped.		# All .h files included by the wrapped header file must be parsed and their contents temporarily stored by the wrapper tools. Note that these included headers will only be parsed, not wrapped.
-
	# A search routine must be added to allow the wrappers to search through the parsed data for all the included files for any types that are encountered in any wrapped class methods.		# A search routine must be added to allow the wrappers to search through the parsed data for all the included files for any types that are encountered in any wrapped class methods.
-
	# If the search for an encountered type fails, but a forward declaration for that type exists, then the wrappers must attempt to load the header file for that type. For example, if the type vtkLookupTable is encountered then vtkLookupTable.h will be loaded if it exists.		# If the search for an encountered type fails, but a forward declaration for that type exists, then the wrappers must attempt to load the header file for that type. For example, if the type vtkLookupTable is encountered then vtkLookupTable.h will be loaded if it exists.

User talk:Shayashi

2012-05-16T16:36:25Z

Welcome!

New page

'''Welcome to ''KitwarePublic''!'''
We hope you will contribute much and well.
You will probably want to read the [[Help:Contents|help pages]].
Again, welcome and have fun! [[User:Matthew.bowman|Matthew.bowman]] 12:36, 16 May 2012 (EDT)

User:Shayashi

2012-05-16T16:36:23Z

Creating user page with biography of new user.

New page

I've been an electrical and computer engineer for about 10 years and am presently working on a project that uses both CMake and CPack.

User:Shayashi

2012-05-16T16:36:23Z

created new account User:Shayashi

ITK Release 4/SimpleITK/Tcon 2012 16 02

2012-05-16T13:30:33Z

New Issues:

New page

= Tcon Information =
Please join the following teleconference line:
Toll-Free #: 1-888-677-0429
Participant Code: 96280

Wednesday, May 16nd, 9:30am Eastern Time

= Attendees =

* Bradley Lowekamp
* Dan Blezek

=Links=

*HOME PAGE: http://simpleitk.org
*CDASH: http://www.cdash.org/CDash/index.php?project=simpleITK
** C# is not working!
*COVERAGE: http://open.cdash.org/viewCoverage.php?buildid=2242884
*VALGRIND: http://open.cdash.org/viewDynamicAnalysis.php?buildid=2243279
*GIT: http://itk.org/gitweb?p=SimpleITK.git;a=log
*GITHUB-MIRROR:https://github.com/SimpleITK/SimpleITK/network
*DOXYGEN: http://www.itk.org/SimpleITKDoxygen/html/
*JIRA: https://itk.icts.uiowa.edu/jira/browse/SIMPLEITK

= Daily Details=
* The Stage Repository

SIMPLEITK-224_AddVectorSupportGetBuffer | master=0 next=0
SIMPLEITK-74_AutomaticallyComputeTimeStep | master=0 next=1
SIMPLEITK-1_AddImageRegistration | master=0 next=0
SIMPLEITK-292_AddImageSources | master=0 next=1
UpdateData | master=0 next=1
SIMPLEITK-226_Multiple_Image_Input | master=0 next=0
SIMPLEITK-AddNumpySupportForVectorImages | master=0 next=0
SIMPLEITK-226_Multiple_Image_Inputs | master=0 next=1
SIMPLEITK-292_AddBinaryReconstruction | master=0 next=1
SIMPLEITK-279_AddComposeImageFilter | master=0 next=1
SIMPLEITK-264_AddTransformations | master=0 next=0
SIMPLEITK-211_AddingWatershedFilters | master=0 next=0

= New Issues =

== Working on Multi-Input Filters ==
* Completed and in next

==Update On Transformations for Registration ==

* Dan?

== Gradient ImageFilter ==
* I have a modified ITK, which enable GradientImageFilter to work with VectorImages
* Getting GradientRecursiveGaussian working is going to be more complicated

== PyBuffer Issues ==
* Support for old python buffer interface?
** With numpy 1.5 it appears that we are unable to get a PEP 3118 Buffer interface

==Dashboard==

=== Valgrind failures ===

* Both Valgrind and VS10 debug are reporting failures on the same test.
* Real bug here must be addressed.

=== Shared libraries on Windows ===

* Need to add the ITK library directory to the PATH environmental variable to correctly load dlls.

== User Requested Features ==

* A couple of post on the users list related to better support for VectorImages or 4D images. Reading, accessing buffer and pixel and converting to numpy.

* A users wanting to use the edge potential image filter, there is not way to create gradient image. Nor compose scalar images into a vector image.

= Priorities for next release =

* Registration
* <strike>C++ installation</strike>
* Splitting Wrapping directory into languages
* <strike>Splitting BasicFilters Library</strike>
* improved vector image support

= Schedule =

* Discuss long term goals and milestones.
* Documentations
* Registration is very important

ITK/Release 4/SimpleITK

2012-05-16T13:27:45Z

TCons:

← Older revision		Revision as of 13:27, 16 May 2012
Line 100:		Line 100:

	= TCons =		= TCons =
		+
		+	* [[ITK_Release_4/SimpleITK/Tcon 2012 16 02\|5/16/2012]]

	* [[ITK_Release_4/SimpleITK/Tcon 2012 9 02\|5/09/2012]]		* [[ITK_Release_4/SimpleITK/Tcon 2012 9 02\|5/09/2012]]

VTK Related Job Opportunities

2012-05-15T15:32:29Z

← Older revision		Revision as of 15:32, 15 May 2012
Line 1:		Line 1:
		+	Please feel free to post announcements for jobs and positions that are related to VTK and applicants with VTK experience. Once the position has been fulfilled, please update the entry accordingly.
		+
		+	<br>
		+
		+
	-----------------		-----------------

-	Software Engineer(s)-Electrical Geodesics, Inc.	+
		+
		+	== '''Software Developer - University of Utah''' ==
		+
		+	Posted May 15, 2012
		+
		+	The [http://www.carmacenter.org CARMA Center] is seeking a full-time C++ software developer. The position involves working with a large, interdisciplinary team of scientists and clinicians to implement and evaluate new image-based computational algorithms and software for the treatment of cardiac disease and the study of its underlying causes.
		+
		+	The CARMA Center is looking for an individual who is available for a full-time commitment and has completed a Bachelor’s degree in Computer Science, Computer Engineering, or a related field with similar mathematical and computational experience.
		+
		+	Applicants must demonstrate strong C++ programming skills, be self-motivated, and possess good organizational and communication skills. Image processing experience and familiarity with the ITK and VTK toolkits are especially desirable, but not required, provided the applicant has sufficient technical background and interest to learn.
		+
		+	Web site: http://www.healthsciences.utah.edu/carma/jobs_volunteer.html
		+
		+
		+	==Software Engineer(s)-Electrical Geodesics, Inc.==

	EGI, an international medical device company in the neurology/neuroscience field is seeking to add "three", Software Engineers to it's "Software Engineering Team"		EGI, an international medical device company in the neurology/neuroscience field is seeking to add "three", Software Engineers to it's "Software Engineering Team"
Line 35:		Line 55:
	• Strong profiency in database engineering, and demonstrable knowledge of SQL.		• Strong profiency in database engineering, and demonstrable knowledge of SQL.
	• Experience with Netbeans or Eclipse (and comfortable to use either).		• Experience with Netbeans or Eclipse (and comfortable to use either).
-
-
-	~~-----------------~~

ITK/Job Opportunities

2012-05-15T15:29:40Z

← Older revision		Revision as of 15:29, 15 May 2012
Line 5:		Line 5:

	-----------------		-----------------
		+
		+	== '''Software Developer - University of Utah''' ==
		+
		+	Posted May 15, 2012
		+
		+	The [http://www.carmacenter.org CARMA Center] is seeking a full-time C++ software developer. The position involves working with a large, interdisciplinary team of scientists and clinicians to implement and evaluate new image-based computational algorithms and software for the treatment of cardiac disease and the study of its underlying causes.
		+
		+	The CARMA Center is looking for an individual who is available for a full-time commitment and has completed a Bachelor’s degree in Computer Science, Computer Engineering, or a related field with similar mathematical and computational experience.
		+
		+	Applicants must demonstrate strong C++ programming skills, be self-motivated, and possess good organizational and communication skills. Image processing experience and familiarity with the ITK and VTK toolkits are especially desirable, but not required, provided the applicant has sufficient technical background and interest to learn.
		+
		+	Web site: http://www.healthsciences.utah.edu/carma/jobs_volunteer.html

	== '''ITK-SNAP Software Developer - University of Pennsylvania''' ==		== '''ITK-SNAP Software Developer - University of Pennsylvania''' ==

User talk:Amorris

2012-05-15T14:51:12Z

Welcome!

New page

User:Amorris

2012-05-15T14:51:11Z

Creating user page with biography of new user.

New page

Software developer at the CARMA Center (www.carmacenter.org)

User:Amorris

2012-05-15T14:51:11Z

created new account User:Amorris

VTK/Examples/C

2012-05-15T14:47:46Z

Created page with "It is possible to wrap some VTK functionality to be used by a C program."

New page

It is possible to wrap some VTK functionality to be used by a C program.

VTK/Examples

2012-05-15T14:47:20Z

Examples are available for the following programming languages::

← Older revision		Revision as of 14:47, 15 May 2012
Line 18:		Line 18:
	* [[VTK/Examples/Tcl \|Tcl]]		* [[VTK/Examples/Tcl \|Tcl]]
	* [[VTK/Examples/CSharp \|C#]]		* [[VTK/Examples/CSharp \|C#]]
		+	* [[VTK/Examples/C \|C]]

	The above examples demonstrate how to ''use'' VTK functionalities. There are also examples specifically to demonstrate how to write code as a VTK filter using VTK techniques. This is helpful so that your custom code can be called in a fashion that other people are already familiar with. It is also necessary if you plan to contribute your classes to VTK.		The above examples demonstrate how to ''use'' VTK functionalities. There are also examples specifically to demonstrate how to write code as a VTK filter using VTK techniques. This is helpful so that your custom code can be called in a fashion that other people are already familiar with. It is also necessary if you plan to contribute your classes to VTK.

File:VTK Examples Baseline Texture TestTexturedSphere.png

2012-05-15T00:25:44Z

uploaded a new version of "[[File:VTK Examples Baseline Texture TestTexturedSphere.png]]" Baseline changed

VTK/VTK6/Migration/DoublePrecisionPi

2012-05-14T18:49:58Z

Analyze:

New page

VTK6 represents a major upgrade to VTK. The upgrade presents an opportunity to provide consistent representation and usage of Pi and TwoPi.

This experiment uses the [http://en.wikipedia.org/wiki/DMAIC#DMAIC '''DMAIC'''] methodology of the [http://en.wikipedia.org/wiki/Six_Sigma ''Six Sigma management process''] to ''"Define"'', ''"Measure"'', ''"Analyze"'', ''"Improve"'' and ''"Control"'' valgrind defects in VTK.

The basic methodology (from Wikipedia) consists of the following five steps:
*'''''D'''efine'' process goals that are consistent with customer demands and VTK's strategy.
*'''''M'''easure'' key aspects of the current process and collect relevant data.
*'''''A'''nalyze'' the data to verify cause-and-effect relationships. Determine what the relationships are, and attempt to ensure that all factors have been considered.
*'''''I'''mprove'' or optimize the process.
*'''''C'''ontrol'' to ensure that any deviations from target are corrected before they result in defects. Set up pilot runs to establish software quality, move on to production, set up control mechanisms and continuously monitor the process.

==Define==
Provide a consistent use if Pi and TwoPi throughout the toolkit. Currently Pi is used in the following manner:
# vtkMath::Pi() returns a single precision representation of Pi.
# vtkMath::DoublePi() returns a double precision representation of Pi.
# Explict forms like 3.1415927
## 3.141593
## 3.1415926
## 3.141592653589
## 3.141592654
## 3.14159265358979
## 3.141592653589793
## 3.14159265358979323846

Similar uses exist for TwoPi, DoubleTwoPi and 6.28...

==Measure==
Pi usage was measured using the unix grep command on just .cxx files.
# vtkMath::Pi() - 64 files
# vtkMath::DoublePi() - 13 files
# Explicit Pi - 19 files
# vtkMath::TwoPi - 0 files
# vtkMath::DoubleTwoPi() - 4 files
# Explicit 2Pi - 5 files

==Analyze==
Sometime around vtk4.4, most floating point calculations were converted from single precision to double precision. Apparently at that time, the vtkMath::Pi() was not converted to double. Rather, vtkMath::DoublePi() was introduced. Also, throughout the toolkit, some developers chose to use explicit representations of Pi. These varied in precision.

==Improve==

==Control==
Gerrit reviewers should watch for the introduction of explicit representation of Pi and 2Pi

VTK/Futures/Math Library

2012-05-14T17:29:52Z

Motivation:

← Older revision		Revision as of 17:29, 14 May 2012
Line 1:		Line 1:
	==Motivation==		==Motivation==
-	A [http://~~old~~.~~nabble~~.~~com~~/~~Scope~~-of-~~VTK-and-it%27s-potential-as-a-common-research-language-td27105322~~.html recent discussion on the vtk-developers] mailing list described the need for a standard maths/vectors package for VTK.	+	A [http://www.vtk.org/pipermail/vtk-developers/2010-January/006953.html recent discussion on the vtk-developers] mailing list (continued [http://www.vtk.org/pipermail/vtk-developers/2010-January/007196.html here]) described the need for a standard maths/vectors package for VTK.

	This page captures the motivation, requirements and evaluation of candidates.		This page captures the motivation, requirements and evaluation of candidates.
-

	==Requirements==		==Requirements==

File:VTK Examples Baseline Texture TestTexturedSphere.png

2012-05-14T15:57:47Z

uploaded "[[File:VTK Examples Baseline Texture TestTexturedSphere.png]]"

VTK/Examples/Cxx/Texture/TexturedSphere

2012-05-14T15:57:09Z

New example

New page

<div class="floatcenter">[[File:VTK_Examples_Baseline_Texture_TestTexturedSphere.png]]</div>
==TexturedSphere.cxx==
<source lang="cpp">
#include <vtkSmartPointer.h>

#include <vtkRenderWindowInteractor.h>
#include <vtkRenderWindow.h>
#include <vtkRenderer.h>
#include <vtkActor.h>
#include <vtkPolyDataMapper.h>
#include <vtkTransformTextureCoords.h>
#include <vtkTexture.h>
#include <vtkTextureMapToSphere.h>
#include <vtkImageReader2Factory.h>
#include <vtkImageReader.h>
#include <vtkTexturedSphereSource.h>

int main (int argc, char *argv[])
{
if (argc < 2)
{
std::cout << "Usage: " << argv[0]
<< " texture(.png)"
<< " [translate]" <<std::endl;
return EXIT_FAILURE;
}
double translate[3];
if (argc > 2)
{
translate[0] = atof(argv[2]);
}
else
{
translate[0] = 0.0;
}
translate[1] = 0.0;
translate[2] = 0.0;
std::cout << translate[0] << ", "
<< translate[1] << ", "
<< translate[2] << "\n";
// Create a sphere with texture coordinates
vtkSmartPointer<vtkTexturedSphereSource> source =
vtkSmartPointer<vtkTexturedSphereSource>::New();

// Read texture file
vtkSmartPointer<vtkImageReader2Factory> readerFactory =
vtkSmartPointer<vtkImageReader2Factory>::New();
vtkSmartPointer<vtkImageReader2> imageReader =
readerFactory->CreateImageReader2(argv[1]);
imageReader->SetFileName(argv[1]);

// Create texture
vtkSmartPointer<vtkTexture> texture =
vtkSmartPointer<vtkTexture>::New();
texture->SetInputConnection(imageReader->GetOutputPort());

vtkSmartPointer<vtkTransformTextureCoords> transformTexture =
vtkSmartPointer<vtkTransformTextureCoords>::New();
transformTexture->SetInputConnection(source->GetOutputPort());
transformTexture->SetPosition(translate);

vtkSmartPointer<vtkPolyDataMapper> mapper =
vtkSmartPointer<vtkPolyDataMapper>::New();
mapper->SetInputConnection(transformTexture->GetOutputPort());

vtkSmartPointer<vtkActor> actor =
vtkSmartPointer<vtkActor>::New();
actor->SetMapper( mapper );
actor->SetTexture( texture );

vtkSmartPointer<vtkRenderer> renderer =
vtkSmartPointer<vtkRenderer>::New();
renderer->AddActor(actor);
renderer->SetBackground(.1, .2, .3);

vtkSmartPointer<vtkRenderWindow> renderWindow =
vtkSmartPointer<vtkRenderWindow>::New();
renderWindow->AddRenderer( renderer );

vtkSmartPointer<vtkRenderWindowInteractor> renWinInteractor =
vtkSmartPointer<vtkRenderWindowInteractor>::New();
renWinInteractor->SetRenderWindow( renderWindow );

renderWindow->Render();
renWinInteractor->Start();

return EXIT_SUCCESS;
}
</source>

{{VTKCMakeLists|TexturedSphere}}

VTK/Examples/Cxx/Utilities/OffScreenRendering

2012-05-12T20:48:30Z

The imaging and graphics factories have been removed in VTK6.

← Older revision		Revision as of 20:48, 12 May 2012
(One intermediate revision not shown)
Line 3:		Line 3:
	==OffScreenRendering.cxx==		==OffScreenRendering.cxx==
	<source lang="cpp">		<source lang="cpp">
		+	#include <vtkVersion.h>
		+	#if VTK_MAJOR_VERSION == 6
		+	int main(int, char *argv[])
		+	{
		+	std::cout << argv[0] << " requires VTK 5.10 or earlier. This VTK version is " << vtkVersion::GetVTKVersion() << std::endl;
		+	return EXIT_SUCCESS;
		+	}
		+	#else
	#include <vtkPolyDataMapper.h>		#include <vtkPolyDataMapper.h>
	#include <vtkActor.h>		#include <vtkActor.h>
Line 67:		Line 75:
	return EXIT_SUCCESS;		return EXIT_SUCCESS;
	}		}
		+	#endif
	</source>		</source>

-	~~==CMakeLists.txt==~~	+	{{VTKCMakeLists\|OffScreenRendering}}
-	~~<source lang="cmake">~~	+
-	~~cmake_minimum_required(VERSION 2.6)~~	+
-		+
-	~~PROJECT(~~OffScreenRendering)	+
-		+
-	~~FIND_PACKAGE(VTK REQUIRED)~~	+
-	~~INCLUDE(${VTK_USE_FILE~~})	+
-		+
-	~~ADD_EXECUTABLE(OffScreenRendering OffScreenRendering.cxx)~~	+
-	~~TARGET_LINK_LIBRARIES(OffScreenRendering vtkHybrid)~~	+
-		+
-	~~</source>~~	+
-		+
-	~~[[Category:VTKNoVizRequired]]~~	+

VTK/Wrappers

2012-05-11T19:16:10Z

Command-line arguments are not python-specific

← Older revision		Revision as of 19:16, 11 May 2012
Line 19:		Line 19:
	[[VTK/Remove BTX ETX \| BTX/ETX]]		[[VTK/Remove BTX ETX \| BTX/ETX]]

-	~~= vtkWrapPython =~~	+	[[VTK/Wrappers/Command Line Arguments \| Command Line Arguments]]
-	* [[VTK/Wrappers/Command Line Arguments \| Command Line Arguments]]	+
		+	= vtkWrapPython =
	* [[VTK/Python Wrapper Enhancement \| Python Wrapper Enhancement]]		* [[VTK/Python Wrapper Enhancement \| Python Wrapper Enhancement]]

VTK/Wrappers

2012-05-11T19:09:04Z

← Older revision		Revision as of 19:09, 11 May 2012
(One intermediate revision not shown)
Line 19:		Line 19:
	[[VTK/Remove BTX ETX \| BTX/ETX]]		[[VTK/Remove BTX ETX \| BTX/ETX]]

-	[[VTK/Wrappers/Command Line Arguments \| Command Line Arguments]]	+	= vtkWrapPython =
-		+	* [[VTK/Wrappers/Command Line Arguments \| Command Line Arguments]]
-	[[VTK/Python Wrapper Enhancement \| Python Wrapper Enhancement]]	+	* [[VTK/Python Wrapper Enhancement \| Python Wrapper Enhancement]]

VTK

2012-05-11T18:36:39Z

Wrapping:

← Older revision		Revision as of 18:36, 11 May 2012
Line 133:		Line 133:

	== Wrapping ==		== Wrapping ==
-		+
		+	* [[VTK/Wrappers \| Wrapping Tools]]
		+
	* [[VTK/Java Wrapping\|Java]]		* [[VTK/Java Wrapping\|Java]]
	** [[VTK/Java Code Samples\|Java code samples]]		** [[VTK/Java Code Samples\|Java code samples]]

VTK/Wrappers

2012-05-11T18:35:34Z

Wrapping Tools:

New page

== Wrapping Tools ==

The wrapping tools that come with VTK are:

* [[VTK/Python Wrapping FAQ | vtkWrapPython]]
* vtkWrapTcl
* vtkWrapJava/vtkParseJava
* vtkWrapJavaBeans <font color='green'>(obsolete)</font>
* [[VTK/WrapHierarchy | vtkWrapHierarchy]]
* vtkHTML <font color='green'>(obsoleted in favor of Doxygen)</font>
* vtkPrint <font color='green'>(obsolete)</font>

[[VTK/Wrapper Update 2010 | Wrapper Changes for VTK 5.8]]

[[VTK/Wrapping Special Types | Wrapping Special Types]]

[[VTK/WrapHierarchy | WrapHierarchy and Hierarchy Files]]

[[VTK/Remove BTX ETX | BTX/ETX]]

[[VTK/Wrappers/Command Line Arguments | Command Line Arguments]]

[[VTK/Python Wrapper Enhancement | Python Wrapper Enhancement]]

VTK/Wrappers/Command Line Arguments

2012-05-11T18:10:49Z

← Older revision		Revision as of 18:10, 11 May 2012
Line 12:		Line 12:
	\|-		\|-
	\| -o <file>		\| -o <file>
-	\| the output file	+	\| the output file <font color='green'>(proposed for VTK 6.0)</font>
	\|-		\|-
	\| -I <dir>		\| -I <dir>
-	\| add an include directory	+	\| add an include directory <font color='green'>(new for VTK 5.8)</font>
	\|-		\|-
	\| -D <macro[=definition]>		\| -D <macro[=definition]>
-	\| define a macro (the definition is optional)	+	\| define a macro (the definition is optional) <font color='green'>(new for VTK 5.8)</font>
	\|-		\|-
	\| -U <macro>		\| -U <macro>
-	\| undefine a macro	+	\| undefine a macro <font color='green'>(new for VTK 5.8)</font>
	\|-		\|-
	\| @<file>		\| @<file>
-	\| read command-line arguments from the specified file	+	\| read command-line arguments from the specified file <font color='green'>(proposed for VTK 6.0)</font>
	\|-		\|-
	\| --hints <file>		\| --hints <file>
-	\| hints file, usually called "hints"	+	\| hints file, usually called "hints" <font color='green'>(new for VTK 5.8)</font>
	\|-		\|-
	\| --types <file>		\| --types <file>
-	\| type hierarchy file, usually ends in "Hierarchy.txt"	+	\| type hierarchy file, usually ends in "Hierarchy.txt" <font color='green'>(new for VTK 5.8)</font>
	\|-		\|-
	\| --version		\| --version
-	\| print the VTK version number of the tool	+	\| print the VTK version number of the tool <font color='green'>(new for VTK 5.10)</font>
	\|-		\|-
	\| --help		\| --help
-	\| print a short help message	+	\| print a short help message <font color='green'>(new for VTK 5.10)</font>
	\|-		\|-
	\| --concrete		\| --concrete
-	\| force the wrappers to wrap the input as a concrete class	+	\| force the wrappers to wrap the input as a concrete class <font color='green'>(new for VTK 5.8)</font>
	\|-		\|-
	\| --abstract		\| --abstract
-	\| force the wrappers to wrap the input as an abstract class	+	\| force the wrappers to wrap the input as an abstract class <font color='green'>(new for VTK 5.8)</font>
	\|-		\|-
	\| --vtkobject		\| --vtkobject
-	\| inform the wrappers that the class is derived from vtkObjectBase	+	\| inform the wrappers that the class is derived from vtkObjectBase <font color='green'>(new for VTK 5.8)</font>
	\|-		\|-
	\| --special		\| --special
-	\| inform the wrappers that the class is not derived from vtkObjectBase	+	\| inform the wrappers that the class is not derived from vtkObjectBase <font color='green'>(new for VTK 5.8)</font>
	\|-		\|-
	\|}		\|}

	The "@file" option allows one or more of the command-line arguments to be stored in a file. If the file that appears after the "@" does not exist, then "@file" will, itself, be treated as a command-line argument. This behavior was chosen for consistency with gcc, which also supports "@" files.		The "@file" option allows one or more of the command-line arguments to be stored in a file. If the file that appears after the "@" does not exist, then "@file" will, itself, be treated as a command-line argument. This behavior was chosen for consistency with gcc, which also supports "@" files.

User talk:DenisKrivosheev

2012-05-11T16:09:33Z

Welcome!

New page

User:DenisKrivosheev

2012-05-11T16:09:32Z

Creating user page with biography of new user.

New page

Programmer