![]() ![]() Second: Define the driving application to be bundled with CTK (that demonstrates the utility of CTK).Future challenges to be addressed include methods for software testing, event handling, and more. We are currently focusing simplifying the challenging tasks of (1) integrating DICOM Q&R functionality into applications (i.e., thereby enabling the integration of applications into the data workflow of a clinical environment) and (2) providing clean and effective user interfaces that are appropriate for use in a clinical environment (e.g., intuitive user-interface widgets for window and level selection). Specifically, its parts are intended to be easily integrated into current software systems and help them address software engineering challenges that impede their clinical use. Candidate: CTK is meant to span the boundaries of current toolkits and applications.Pick a time and place for a talkfest in the US (perhaps at Washington University in St.General set of topics (attendees, please flesh this out with your own ideas!) Pick up threads of discussion and activity from Pre-Hackfest and May 2010 Hackfest afternoon summary of progress and discussion of ongoing work, future fests.afternoon status update from everyone, review to-do items for the rest of the week.Demos/Presentation: CreatTools, DTK/MedInria, MAF Scripts.Questions for packaging CTK in debian: 1) what to enable as 'standard ctk' 2) package name: commontk or ctk? 3) build against VTK trunk or release version? Same question for DCMTK, Qt, etc. ![]() Options for C++ DICOM Application Hosting implementation in CTK (Sascha and other) Presentation.Review of git methodologies (Jc, Benoit, Sascha and all).Also state if you would like to present on a topic and lead a discussion so these can be added to the agenda. Everyone should say a few words of what they want to accomplish during the week.Unless otherwise allocated, it is expected that the time will be spent hacking, with ad hoc discussions and debugging sessions as needed. Anyone who has prepared material they would like to present can suggest a time slot so a detailed agenda for the rest of the week can be prepared. Monday will start with a review of the topics. Nominally 9am to 5pm each day Monday through Friday. Be prepared to discuss projects so we can make the most effective use of the face-to-face hackfest time. We plan to hold weekly phone conferences during the month leading up to the actual hackfest. Use the CTK developers mailing list to discuss build issues and topics for ongoing work. The venue and activities at future hackfests will be determined based on the number of active participants in the project.ĭevelopers should bring a laptop with the current CTK source code downloaded and built. Future hackfests will be announced in advance and we hope lots of people will be interested in participating. Virtual Attendees (by email or phone): Lawrence Tarbox, Michael Onken, Stephen Aylwardįuture 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. Jean-Christophe Fillion-Robin Kitware, USA.Ivo Wolf, Hochschule Mannheim and DKFZ, Germany.Organizers: Ivo Wolf, Steve Pieper, Stephen AylwardĪttendees: (due to limited space, please contact the organizers to attend) The organizing committee will invite and select participants based on input from TheTeam. Group size: maximum 20 participants so we can have a manageable working meeting. People who do not feel qualified for this are politely not invited :) 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. Goal: A follow on to the wildly successful March 2010 pre-hackfest and May 2010 hackfest.
0 Comments
Leave a Reply. |