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

List:       kwrite-devel
Subject:    Re: TODO for 3.2
From:       Joseph Wenninger <jowenn () jowenn ! at>
Date:       2002-11-24 13:26:04
[Download RAW message or body]

Hi

Am Sam, 2002-11-23 um 22.35 schrieb Anders Lund:
> On Saturday 23 November 2002 19:23, Christoph Cullmann wrote:
> > Hi,
> > just wanted to start the official:
> > "What we want/need/must/should/could do for KDE 3.2"
> > discussion on the list.
> 
> :-)
> 
> > Here my points, what we "should do", if possible:
> >
> > - BiDi support, as that is the only REAL thing that is missing now after
> >   dynamic word wrap is delivered
> 
> Maybe we ought to advertise for help on this one somehow? Last time we 
> discussed it, none of us had the sufficient knowledge.
> 
> > - write some design documents about the kate part and app (and their
> >   interfaces), for example update the plugin howto, ...
> 
> I'll take on the plugin howto for a start
> 

I think we really should start looking over our code and document it in
the cpp files too, not just in the headers. For me that is even more
important than plugin howtos, because without good documentation we most
probably will break the external interfaces, when we change internals.
IMPORTANT: Usefull documentation, NOT  i++; //increments i by one

> > - Try to implement the most common wishes on bugs.kde.org ;)
> >
> > - Some keywords:
> >    Scripting, Embed different Highlightings at once, ...

I've some very experimental code for including highlighting files into
others on my harddisc. I'll merge it into HEAD after the release

> >
> > - And last but not least:
> >     A) MILLIONS OF BUGFIXES ;P:
> 
> We can't fix bugs we don't know. Currently we have 36 bugs in bugs.kde.org 
> that are not fixed or wishes.
> 
> >          atm not aware of really critical bugs like crashs (at least I had
> > no kate crash since weeks beside those we allready have fixed for release
> > now;)
> >
> >     B) Optimizations for the code (there is still some room for
> > improvements, good examples: search & replace (can made much faster),
> > folding, text buffer, ...
> >
> > This list is open for discussion, if we have agreed on a set of
> > features/fixes, I will put them up on kate.kde.org for common access.
> 
> We should create a list of wanted plugins, preferable with some kind of spec 
> for each. Some idears:
> * File templates
> 	This will allow to load file content into a new file. I want to 
> 	provide some sort of hierachy of predefined templates as well.
> 	(I'll take on that, I wrote the code once, so i can reconstruct it)
> * Clip library
> 	This will allow insertion of predefined strings/variables, which 
> 	could be made available based on mime type and URL matching
> 
> 	I once wrote a spec for a "template language" which would allow
> 	for collection of user input for combination with templates and 
> 	clips, I still have it and I will post it on the web again
> 	for reference and discussion.
> 	(I'd like to take on that as well. jowenn?)
> * Version control
> 	Seperate plugins for CVS, RSC, SVN etc, each of which could provide
> 	basic commands on a pr file bases. For example a CVS support could
> 	include "Update...", Commit...", "Add...", "Diff..." etc, based on 
> 	the presence of a CVS directory in the files immediate location.
> 	I don't know if cervisia is providing a library, but some dialogs
> 	and facilities are quite general.
> * All kinds of programming tools - class parsers/viewers etc...
> 
> A general thought: We usually use a very simple table for these lists. I 
> wonder if it would be worth adding priority/asignee/status columns? And as I 
> said, I think writing specs is a good idear. It improves our options to 
> discuss the design of features.
> 
> Some of my own plans/itches:
> * make kate use the new loading scheme when restoring split frames on startup
> * move HTML export to a plugin, make it produce real HTML/CSS, add features
> 	similar to printing (linenumbers, selection, syntax guide) + some
> 	more (like export to clipboard)
> * sort/tree options for the file list
> 	Add directory tree as an option
> 	Add sort by path | name | opening order
> 	Add bookmarks tree as an option
> * get the filter plugin to save a history, possibly (?) a list of saved
> 	filters and handle errors with slightly more grace
> * get the HTML tools plugin to agree with the XML plugin who provides what
> 	(the XML one does if loaded and has the feature)
> * add a document structure sidebar for HTML (in the HTML tools plugin)
> * projects ... yes, some time. I'll try write a spec for that.
> * perl tool kit (partly done)
> 
> -anders
> 

Does the hosting server have a database ? than we could add a simple
TODO list (like on sf and other sites) with login for changing
assignees, setting priorities, adding new items, adding comments, ....


Kind regards
Joseph Wenninger

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