[cssed-devel] New release

[Iago R. <iag...@hi...>]

I'm moving towards a new minor release and most changes are in CVS right
now.

The main changes for this release (0.3.1) are focused in bug fixing and
multiple document's management.

I will not enumerate the bugs fixed but the new features added:

* Mark documents - there's a new entry on the Documents menu called
"Flag" that let's you change the document's tab colors to ease
recognition.=20

* Draggable documents - once opened documents can be reordered dragging
the document's button and dropping it on another document's button. The
dragged document will be moved to the drop position. This closes feature
request ID 1083073.
http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1083073&group_=
id=3D95078&atid=3D610119

* Document list - There's a new entry on the Document menu called
"Document list" that shows a dialog will the opened documents in a list.
This list can be saved and loaded to and from a file (in XML format).
You can also drag items from the file browser plugin - if loaded - on a
document list, or from other document lists as well.
You can open as many document lists as you want in a single session.
This closes feature request ID 961437
http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D961437&group_i=
d=3D95078&atid=3D610119

Those are the main additions, but there is some developer's work to be
done before the release:

- Update to the new libcroco library.
- Commit some fixes to the upstream scintilla.
- Fix a bug in the font dialog repoted by Clansco Falsetti.

On plugins, the file browser have some minimal but interesting changes.

It now remembers the drop down list of directories opened from one
session to other, and there's a new dialog to edit the drop down list.

It can also be edited, by hand as it's plain text will a directory path
per line at $HOME/.cssed/filebrowser.

On the ctags plugin have been no work, but the addition of css support
to ctags, so this modified ctags version can scan also CSS style sheets.

Unfortunately, the ctags project seems to be slowing down and there are
lots of requests for addition of new languages, that are being ignored
by the upstream developer - surely he have low spare time right now - so
I don't expect to see CSS support in the upstream exuberant-ctags.

It's a problem to be solved, and I don't know how. Shipping a self made
version of ctags, or putting the files and compile instructions on the
web site. I don't know yet how to handle this.

There's also some work on plugins to be done before the release as to
change all plugins to the gtk+-2.4 file chooser.

To fix the plugins interface on win32 will wait for the next major
release, as it will involve changes in the plugins' API and the rewrite
of most plugins.

There are some feature requests also pending for the next release:

- Gerard Gualberto http://www.tortus.com asked for gnome-vfs support if
the libraries are present, and it have been accepted.

- izzy  http://sourceforge.net/users/izzy/ asked for CSS preview and it
have been accepted, but it's pending for technical reasons.
=20
[x] Add here your feature requests.

The main changes planed for the next major release are:

- CssedFileType manager, is now merely an integer that identify the file
type. I will change to hold an object that will manage syntax
highlighting, auto completion, saving and such.

The idea behind this  is to let users to override parts or the whole
object, to add auto completion functions, styling functions or else, via
plugins.

This way you can code - as example - PHP auto completion or python
support, and ship it as a plugin for anyone interested, without bloating
cssed.

- Plugin interface extension: will be added some functions to the
plugin's interface, to better fit on Win32.

- UIModules: I'm planning a generic interface to allow to show/hide
parts of the user interface by the user. It will be possible to use it
from plugins.

- External command support: I'm also planning some short of external
command support to run programs, pipe documents through external
commands, or catch the output from a external command to a new or opened
document.

This is the actual report on how things are going. If anyone miss
anything, or don't like some of those ideas, please post it here.


Thanks in advance for your feedback.
--=20
Iago Rubio