CTK-Hackfest-September-2010: Difference between revisions
| Line 58: | Line 58: | ||
* Review status of Qt-based CTK widget developments | * Review status of Qt-based CTK widget developments | ||
** Slicer4, DTK, GoFigure (others?) | ** Slicer4, DTK, GoFigure (others?) | ||
=== Plugins, Modules === | === Plugins, Modules === | ||
| Line 64: | Line 63: | ||
* Plugins: not-application dependent (like a java plugin that runs in firefox or internet explorer) | * Plugins: not-application dependent (like a java plugin that runs in firefox or internet explorer) | ||
* Modules: rely on some of the API of the host application (like a loadable module that creates a custom GUI using a Qt API so it may work in more than one Qt-based application) | * Modules: rely on some of the API of the host application (like a loadable module that creates a custom GUI using a Qt API so it may work in more than one Qt-based application) | ||
=== Interoperability === | === Interoperability === | ||
( | (gluing toolkits together) | ||
* VTK/OpenInventor shared OpenGL rendering context | |||
=== Events and Communications === | === Events and Communications === | ||
(run-time messaging within and among applications) | (run-time messaging within and among applications) | ||
=== Integration === | |||
(using CTK code in different applications) | |||
== Travel & Hotel == | == Travel & Hotel == | ||
Revision as of 10:33, 14 July 2010
Home < CTK-Hackfest-September-2010Event pictures
| This is a working meeting - the goal is to start writing code! The event will look something like these pictures from the May 2010 meeting in Washington. |
Introduction
Date: September 13-17
Location: TBD
Goal: A follow on to the wildly successful March 2010 pre-hackfest and May 2010 hackfest .
Requirements: attendees must be enthusiastic about CTK and willing to spend their time with the details of dicom, git, cmake, c++, Qt, vtk, itk, openinventor, and related technologies. People who do not feel qualified for this are politely not invited :)
Group size: maximum 20 participants so we can have a manageable working meeting. The organizing committee will invite and select participants based on input from TheTeam.
Organizers: Ivo Wolf, Steve Pieper, Stephen Aylward
Site Hosts: TBD
Attendees: (due to limited space, please contact the organizers to attend)
- Steve Pieper, Isomics, Inc., USA
- Ivo Wolf, Hochschule Mannheim and DKFZ, Germany
- Marco Nolden, DKFZ, Germany
- Sascha Zelzer, DKFZ, Germany
- others...
Future Events: The organizing committee invited a group of developers to get the CTK project started and we've believe we've reached capacity for this event. Future hackfests will be announced in advance and we hope lots of people will be interested in participating. The venue and activities at future hackfests will be determined based on the number of active participants in the project.
Preparation
Developers should bring a laptop with the current CTK source code downloaded and built.
Use the CTK developers mailing list to discuss build issues and topics for ongoing work.
Topics and Projects
Pick up threads of discussion and activity from Pre-Hackfest and May 2010 Hackfest
General set of topics (attendees, please flesh this out with your own ideas!)
Organization and Workflow
- First day will be dedicated to code organization and policies for git-based workflow.
- expected result will be a set of procedures for dissemination to the ctk community for comment and adoption.
DICOM
- Review of ITKv4 DICOM Plans and discussion of DCMTK and GDCM.
Widgets
- Review status of Qt-based CTK widget developments
- Slicer4, DTK, GoFigure (others?)
Plugins, Modules
(utilities for discovering and invoking code blocks)
- Plugins: not-application dependent (like a java plugin that runs in firefox or internet explorer)
- Modules: rely on some of the API of the host application (like a loadable module that creates a custom GUI using a Qt API so it may work in more than one Qt-based application)
Interoperability
(gluing toolkits together)
- VTK/OpenInventor shared OpenGL rendering context
Events and Communications
(run-time messaging within and among applications)
Integration
(using CTK code in different applications)
Travel & Hotel
Travel: TBD
Hotel TBD
Connectivity
- We will provide both wired and wireless connection
