14 messages in org.kde.quanta-develRe: Quanta 3.3 plans
FromSent OnAttachments
Eric LaffoonJan 21, 2004 12:52 am.kno
Chris HornbakerJan 21, 2004 4:37 am 
Bill ChmuraJan 21, 2004 7:17 am 
Andras MantiaJan 21, 2004 7:43 am 
Andras MantiaJan 21, 2004 7:56 am 
Linus McCabeJan 21, 2004 8:25 am 
Andras MantiaJan 21, 2004 8:42 am 
Chris HornbakerJan 21, 2004 9:29 am 
Eric LaffoonJan 21, 2004 12:12 pm 
Eric LaffoonJan 21, 2004 1:14 pm 
Melvyn SopacuaJan 21, 2004 2:30 pm 
Eric LaffoonJan 21, 2004 11:53 pm 
Nicolas DeschildreJan 22, 2004 5:00 am 
Andras MantiaJan 22, 2004 6:36 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Quanta 3.3 plansActions...
From:Andras Mantia (aman@virtualartisans.com)
Date:Jan 21, 2004 7:56:59 am
List:org.kde.quanta-devel

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Wednesday 21 January 2004 10:52, Eric Laffoon wrote:

Hi all, I was inspired to take a break from work an do this. I'm doing good in 2004. I got over the ear infection and now have a painful stiff and swollen right knee. I guess I'm on my last legs. ;-)

I thought I'd get the discussion going here on what to do with Quanta. I have mixed feelings. Over all I'm happy it's so well received and has made such great strides... I'm also really frustrated that so much more I wanted to do didn't make it into 3.2. That's okay. Heres what we will want to do.

That always happens. Look at the amount of items that were shifted from the KDE 3.2 feature plan to 3.3.... But what is true is that we didn't had a strict plan. Many ideas came up, but sometimes the priorities were others, and we couldn't implement or complete them.

1) Look at a good time to introduce decent feature enhancements for a BE release for 3.2 and KDE 3.1 users. My guess is we may want to do this by early Feb but the first thing is to see

KDE is scheduled to appear on 5th of Feb., so at least we should wait a week after that release.

1A) what we really feel we need to change after release that can be done quickly

OK, you'll hate this, but there is still one issue with PHP parsing.

1B) what new features are coming along that might be released like debugging or VPL updates

I'd like to see the debugging features in. That would be a real difference and would motivate users to download and donate. ;-)

1C) a generally desirable release situation

2) We need to look at releasing a 3.3 release prior to KDE 3.3. This means we need to determine the feature set we consider worth a full release and the date as well as supplemental issues like if we branch CVS to keep it clean and how long we test. My inclination is some time between April and August.

See my other mail.

3) We need to begin planning for our next official release with KDE.

The attached Knowit file is not meant to be complete but a start and everyone is invited to edit and resubmit it.

Idea one: put it to the CVS, so we can update/modify it easily.

And now comments about the plan: 1. What does "Actions should get new triggers." mean? 2.The two DCOP features are the same. Selectors are DTEP groups. Should be easy to implement. 3. KHTML: someone who knows a little shell scripting, XSLT and such may come up with an example how to turn an XML to HTML and view it in Konqueror. After that it's easy to integrate that in Quanta. Chris? 4. Toolbars: - cleaning up is required and the same is true for DTEPs. Chris offered some help here. - the "add this tag to a toolbar" is a nice idea - "Make toolbars abide by tag relationships like auto complete": I don't understand this. - Phase 2/2 sounds a little complicated to me and I'm also not sure that I understood it completely. 5. Templates: - as I already said, we need real templates - directory templates (includes the .tgz functionality) is on the feature plan already

About the rest, later .

Andras

- -- Quanta Plus developer - http://quanta.sourceforge.net K Desktop Environment - http://www.kde.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQFADqFhTQdfac6L/08RAtOEAKCbjPyJdmpASGQijHRtlPnAhZqhkACgoJFy p+54XnvNmorZWRLcZocXmk4= =kuTx -----END PGP SIGNATURE-----