[prev in list] [next in list] [prev in thread] [next in thread] 

List:       quanta-devel
Subject:    Re: [quanta-devel] Annotation support
From:       Jens Herden <jens () kdewebdev ! org>
Date:       2005-04-27 13:31:47
Message-ID: 200504272031.47546.jens () kdewebdev ! org
[Download RAW message or body]

Hi Andras,

>  I'm not Eric, but this was public. :-)

Of course, that is why I send it to the list.

> > 1. transition to KDevelop is my top priority. I will not work on the
> > "old" Quanta anymore because I really believe that KDevelop framework is
> > the future. In the moment I read and hear everything about Quanta with
> > the idea
> > of how can this be integrated in KDevelop and how would it be usefull for
> > other languages there.
>
> I don't have anything against your priorities. :-) But as hopefully the
> KDevelop transition will happen here, until you come here we should not
> stop the development, so don't worry if new features are added.

I have no intention to stop people working on whatever they want and I do not 
worry. I just wanted to explain why I am not working on features, except of 
complaining if I think things go wrong.


> > 2. I will not work on team development if the groundwork is not done.
> > That means implementing some features that are missing, like integrated
> > link check, KWallet, Config XT, KHotNewStuff etc.
>
> From the above:
> - integrated link check: absolutely needed, you're right.
> - KWallet: yes, needed as well.
> - Config XT: I'm not *sure* this is mandatory. Many application still miss
> it, including KDevelop!

Yes this is debateable, but to not have it because other don't have it is a 
pure argument. 

> - KHotNewStuff: what is the problem here?? I no only that we need to do
> the server side...

Exactly! This renders the whole feature useless. How long do we have this in 
the code? Why do the users have to wait so long? I really don't get this. 

> > This does also mean a clear
> > concept about what do we want to achieve with team development.
>
> Sometimes it's not clear also for me, but this is why the list exists (see
> below).
>
> > Quanta
> > misses
> > basic thinks like how to protect files from concurrent access.
>
> Is it really a problem with Quanta? If it's about concurent access inside
> a team, one should use a versioning system.

Agreed but I still don't see how the team features cooperate with CVS. You 
probably don't want to make a CVS update to get the latest message from you 
colleagues. I am missing the concept here. 

> > 3. I am not interested in reinventing the wheel. Creating our own
> > solutions
> > for messages or to-do lists is a no-go for me. Integration into the KDE
> > desktop is the way to go. Why should I want to have messages in KMail and
> > Quanta, why should I want to have to-do lists in KOrganizer and Quanta?
> > So we
> > could think about a bridge between KMail and Quanta and KOrganizer and
> > Quanta. I would think about how to display a folder from KMail in Quanta
> > but
> > never how to create my own messaging system.
>
> Sure, we don't need to invent anything. But if something that is not
> present anywhere, we must do it. :-)

Agreed.

> > I am not against support for team development. But actually everything
> > happens
> > in your mind and at private contacts with Andras so that I feel outside
> > of this development. I am confident that your ideas and mine will coexist
> > when
> > we can use the KDevelop plugin system.
>
> No, not everything, and I think this was the only case when we taked
> through phone about Quanta. :-) I agree it's better to discuss such things
> on the list, and next time if it happens outside, I will write a summary
> here. But I don't remember when was last time (aside of this call) when we
> discussed in private about Quanta's new features.

Oh, so the absence of discussion on the list did mislead me to the idea that 
the discussion does happen somewhere else. Sorry for the wrong assumption. I 
am happy if the list gets more discussion in the future.

Jens
_______________________________________________
quanta-devel mailing list
quanta-devel@kde.org
https://mail.kde.org/mailman/listinfo/quanta-devel
[prev in list] [next in list] [prev in thread] [next in thread]