Hi Thomas,
On 28/07/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
-------- Original-Nachricht --------
Datum: Fri, 28 Jul 2006 21:00:08 +0200
Von: "Alexis Pigeon" <[EMAIL PROTECTED]>
> OOo
> codebase of each component has to be buildable for any platform OOo is
> released on.
This is the goal yes. but a first release for windows and linux woudl be a
start as stated, dont expect 100 percent from the first, here is the crux, all
want 100 percent and then say, we have no time for this lot of work,
And people are right when they ask for a 100% functionnal product. OOo
is more and more widely used not only by simple persons like you and
me, but by public administration and big corporations, and these users
are far more picky on quality and stability of the software they use.
I just want to get a small zipfel initially started and if after 3 years there
is no mac version, than we can remove the messenger still ou of the windows
version. but i guess sucess stories are not reversed!
3 years?!? You are kidding?
> Moreover, CSpace is coded in Python, and AFAIK, 90% (if
> not more) of OOo code is C++. A huge refactoring would be needed
> before even thinking of integrating CSpace as a component. Not even
> talking about GUI, look n feel, translations (of the GUI and
> documentation), etc... And then porting to Mac (X11 for Intel and PPC,
> and then for the upcoming Aqua native version), Solaris and *BSD
> platform has to be completed.
So again these both reasons, no Mac version and todo is a Gui logo insertation.
I say: adding a gui logo (logo as mailed in colour blue and yellow bubble) is
easy and for the first
release we can add MAc and Solaris later..
So the concerns are quite easy for me to capture, and i see it is not a lot of
work.
Not a lot of work? Refactoring the code, QA'ing it, porting it (i can
assure you there is no possibility for a component to be released if
not working on the main platforms), writing and translating all the
documentation and GUI, and after the release, maintaining the code
(please stop saying CSpace is bugfree, bugfree software DO NOT exist,
and I'm saying so as a developer), this is a HUGE workload, not only
adding an icon and an HTML page.
[Quoting another email of yours]
There are no plans to make a clone of open office or an own bundling, nor is
there a plan to
make cSpace compatible with Open Office from cspace side. CSpace has not the
manpower to
to this as well as CSpace has own development goals. The action has to come
from Open Office.
The existing version is perfect, bug free and is a good basis, the CSpace
development then can
be taken by Open office for free as well. So the basic release now is easy to
handle.
So now you propose a fork of the CSpace project? Well, if none of the
OOo core team is familiar with the source code of CSpace (ie, if none
of the current CSpace developers integrates the OOo team, or at least
is willing to provide fulltime feedback on the source code), I guess
it would be easier / more reliable to start an IM client from scratch.
> I find the
> idea of p2p-based IM quite interesting and innovative, and I could
> help for testing on Mac platform.
:-) So we agree.
Please don't misunderstand me. I find the core idea of CSpace quite
interesting, and do think an IM client is totally out of the scope of
OOo. And email client or a browser are out of scope too.
Gtreat thing. come join the CSpace development, keep yourself informed about
that.. and we will see...
Sorry, already having a fulltime job as a Java coder, and dedicating
part of my free time to OOo QA, I have no time to get involved in
another project. But as I said, I would be glad to test CSpace as soon
as a Mac port exists.
Regards,
alexis
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
