Changes between Version 10 and Version 11 of FeatureRequests

Timestamp:

Oct 2, 2006, 10:05:12 PM (18 years ago)

Author:

anonymous

Comment:

--

FeatureRequests

@@ -75 +75 @@
 === ''CMT team's answer'' ===
 
- * See ticket #28 for extending project syntax
-
+ * See ticket #29
 
 == 4. Support for <project> placeholder for patterns (DavidQ) ==
@@ -99 +98 @@
 is present, and otherwise use the symlinked version from the  
 InstallArea.
+
+=== ''CMT team's answer'' ===
+
+ * See ticket #30
+
 
 == 5. Simplification of the -I<paths> (DavidQ) ==
@@ -144 +148 @@
 cmt co Reconstruction/RecExample/RecExCommon-01-02-03
 
+=== ''CMT team's answer'' ===
+
+Yes, this is clearly not vital and more straight forward to do with Svn as backend than CVS.
 
 == 9. Make CMT a library rather than a static executable (SébastienB) ==
@@ -149 +156 @@
 This surely is a long-term item but I think it would ease the work of people 
 writting scripts (see b.) or building plugins for CMT.
+
+=== ''CMT team's answer'' ===
+
+It supposes to wrap cmt with another libraries as Boost/swig/etc and allow interrogating directly in python the data structures. In the short term, the solution in 10. is more evident.
 
 == 10. Have python bindings for CMT (SébastienB) ==
@@ -155 +166 @@
 official python bindings for CMT. Just have a look at how many python 
 wrappers have been written for CMT in the Atlas CVS repository.
+
+=== ''CMT team's answer'' ===
+
+Actually a non-official python wrapper exists, we will distribute it (follow ticket )
+
 
 == 11. Introduce the concept of a Release (or some equivalent 'meta-data') (SébastienB) ==
@@ -171 +187 @@
 command.
 
+=== ''CMT team's answer'' ===
+
+
 == 12. Separate the 'build' environment from the 'user' environment (SébastienB) ==