<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
naming issues aside, I tend to agree with Julien here.<br>
<br>
Generally, I am of course in favor of extending CTK with useful
functionality. However, here is a short anecdote: Ivo and I recently
got a request from German group if we think their project would be a
good fit for CTK. Although it looked very promising, well
engineered, and was in the scope of CTK, we expressed our concerns
because the project was not Qt-ified at all and would somehow break
the consistent code style we have now in CTK. I see the same issue
with the current MIDAS code. In the past, I would have voted for
including MIDAScpp as an external project, as we did with all
existing projects we wanted to use but did not comply with the CTK
style.<br>
<br>
I do not want to slow people down or to damp their enthusiasm. I am
just concerned that CTK becomes a Zoo of libraries with inconsistent
"Look and Feel".<br>
<br>
Maybe an open discussion about integrating larger pieces of software
*in advance* of starting the effort would be helpful in the future.<br>
<br>
I am still thinking about your naming suggestions... ;-)<br>
<br>
Best,<br>
Sascha<br>
<br>
On 06/07/2011 03:25 PM, Julien Finet wrote:
<blockquote
cite="mid:BANLkTi=y8YTiFmXMXUuutEC7VzNS-XpFcA@mail.gmail.com"
type="cite">
<div>For the naming convention, is "MIDAScpp" mandatory? couldn't
it be just MIDAS (and be externally refered as CTK MIDAS).</div>
<div>By having MIDAS into CTK, we infer it is C++ and Qt based.</div>
<div>My 2 cts,</div>
<div>Julien.</div>
<br>
<div class="gmail_quote">On Tue, Jun 7, 2011 at 9:19 AM,
Jean-Christophe Fillion-Robin <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:jchris.fillionr@kitware.com">jchris.fillionr@kitware.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">Hi Sasha, <br>
<br>
You bring a very good point ! <br>
<br>
The work related to these projects has just been published and
is open to review.<br>
See <a moz-do-not-send="true"
href="https://github.com/zachmullen/CTK/commit/1051813f5046bb08835b73a12138a672c9c48c82"
target="_blank">https://github.com/zachmullen/CTK/commit/1051813f5046bb08835b73a12138a672c9c48c82</a><br>
<br>
Expat, KWSys, Sqlite and libcurl were initially shipped with
MIDAScpp library ... I advocates to externalize and CMake-ifie
properly these libraries as a first step. That way the code
checked in CTK would "really" corresponds to the library
itself.<br>
<br>
Having an other perspective is always fruitful :) You are
right, since MIDAScpp would be part of CTK, it makes sens to
not depend on these external project and rely on Qt directly.
Qt is a mandatory dependency after all.<br>
<br>
I am cc'ing Zach in the email and I am sure I will be able to
provide more comments. <br>
<br>
Zach> Instead of using expat, libcurl, sqlite and kwsys,
would it make sens to depends on Qt ? <br>
<br>
In the mean time, I have the following questions:<br>
<br>
- Currently the library is named "CTKMIDAScppCore" and
CTKMIDAScppWidgets", I was thinking we could have something
like CTKDataManagementMIDAScppCore and
CTKDataManagementMIDAScppWidgets.<br>
What do you think ? Doing so would leave room to library like
"CTKDataManagementHadoopCore" ... <br>
<br>
- Does introducing a "DataManagement" hierachy of libraries
make sens ? As far as I am concerned, I think it's important
to provide both functionality to process, store and retrieve
the data.<br>
<br>
Thanks<br>
Jc
<div>
<div class="h5"><br>
<br>
<br>
<div class="gmail_quote">On Tue, Jun 7, 2011 at 1:48 AM,
Sascha Zelzer <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:s.zelzer@dkfz-heidelberg.de"
target="_blank">s.zelzer@dkfz-heidelberg.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt
0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
Hi guys,<br>
<br>
Recently, I observed an explosion in the number of
repositories containing external repositories in the
CommonTK organization of github. Could we discuss the
need of some of them, and maybe have these discussions
in the future in advance of pushing those projects?<br>
<br>
I am looking especially at the projects below, where
Qt might already offer enough functionality. Of course
I could be wrong, so thank you for your feedback!<br>
<br>
- sqlite (why not use the Qt sqlite wrapper?)<br>
- KWSys (where is it needed? I did not find any
reference to it in CTK)<br>
- libexpat (Qt also provides a streaming XML API, also
not used anywhere)<br>
- libcurl (there is also no reference to libcurl in
CTK)<br>
<br>
<br>
Thanks,<br>
<br>
Sascha<br>
_______________________________________________<br>
Ctk-developers mailing list<br>
<a moz-do-not-send="true"
href="mailto:Ctk-developers@commontk.org"
target="_blank">Ctk-developers@commontk.org</a><br>
<a moz-do-not-send="true"
href="http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers"
target="_blank">http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
</div>
</div>
<font color="#888888">-- <br>
<a moz-do-not-send="true" href="tel:%2B1%20919%20869%208849"
value="+19198698849" target="_blank">+1 919 869 8849</a><br>
<br>
</font><br>
_______________________________________________<br>
Ctk-developers mailing list<br>
<a moz-do-not-send="true"
href="mailto:Ctk-developers@commontk.org">Ctk-developers@commontk.org</a><br>
<a moz-do-not-send="true"
href="http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers"
target="_blank">http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers</a><br>
<br>
</blockquote>
</div>
<br>
</blockquote>
<br>
</body>
</html>