Thread: [cssed-devel] New release
Brought to you by:
iagorubio
From: Iago R. <iag...@hi...> - 2005-02-06 10:58:11
|
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 |
From: <mic...@ea...> - 2005-02-09 07:47:51
Attachments:
PGP.sig
|
Le 6 f=E9vr. 2005, =E0 11:57, Iago Rubio a =E9crit : > * Document list - There's a new entry on the Document menu called > "Document list" that shows a dialog will the opened documents in a=20 > list. > This list can be saved and loaded to and from a file (in XML format). Impossible to save the list, as the dialog which opens does not create=20= a file but ask to choose an existing file. Severe problems when a document is not utf-8 encoded. Mich=E8le <http://micmacfr.homeunix.org> |
From: Iago R. <iag...@hi...> - 2005-02-09 11:14:59
|
On Wed, 2005-02-09 at 08:47, Mich=C3=A8le Garoche wrote: > Le 6 f=C3=A9vr. 2005, =C3=A0 11:57, Iago Rubio a =C3=A9crit : >=20 > > * Document list - There's a new entry on the Document menu called > > "Document list" that shows a dialog will the opened documents in a=20 > > list. > > This list can be saved and loaded to and from a file (in XML format). > Impossible to save the list, as the dialog which opens does not create=20 > a file but ask to choose an existing file. Yes it's not very user friendly as I first coded the document list itself, then the document list save dialog. To save a doclist start with the current one, modify it as needed and use the save or save as buttons. I have just added to CVS a "New document list" option, as it will be more user friendly. > Severe problems when a document is not utf-8 encoded. I hope it's fixed in CVS, now all file names are converted to UTF-8 before writting. You should take care yourself in saving as UTF-8 if you write the document list file by hand. Just curious, what those severe problems was ? parser errors or messed file names ... or ??=20 --=20 Iago Rubio =20 - Home page * http://www.iagorubio.com=20 - Last project * http://cssed.sourceforge.net =20 - GPG Keyserv * pgp.rediris.es id=3D0x909BD4DD |
From: <mic...@ea...> - 2005-02-09 11:27:09
Attachments:
PGP.sig
|
Le 9 f=E9vr. 2005, =E0 12:14, Iago Rubio a =E9crit : > On Wed, 2005-02-09 at 08:47, Mich=E8le Garoche wrote: >> Le 6 f=E9vr. 2005, =E0 11:57, Iago Rubio a =E9crit : >> >>> * 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). >> Impossible to save the list, as the dialog which opens does not = create >> a file but ask to choose an existing file. > > Yes it's not very user friendly as I first coded the document list > itself, then the document list save dialog. > > To save a doclist start with the current one, modify it as needed and > use the save or save as buttons. That's precisely what I cannot do as there is no current one=20 (apparently). >> >> Severe problems when a document is not utf-8 encoded. > > I hope it's fixed in CVS, now all file names are converted to UTF-8 > before writting. I'll see this later. But the problem was not with the file name, but=20 with the contents and I don't speak of document list, but mere=20 document. Mich=E8le <http://micmacfr.homeunix.org> |
From: Iago R. <iag...@hi...> - 2005-02-09 16:42:05
|
On Wed, 2005-02-09 at 12:26, Mich=C3=A8le Garoche wrote: > Le 9 f=C3=A9vr. 2005, =C3=A0 12:14, Iago Rubio a =C3=A9crit : >=20 > > On Wed, 2005-02-09 at 08:47, Mich=C3=A8le Garoche wrote: > >> Le 6 f=C3=A9vr. 2005, =C3=A0 11:57, Iago Rubio a =C3=A9crit : > >> > >>> * 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). > >> Impossible to save the list, as the dialog which opens does not create > >> a file but ask to choose an existing file. > > > > Yes it's not very user friendly as I first coded the document list > > itself, then the document list save dialog. > > > > To save a doclist start with the current one, modify it as needed and > > use the save or save as buttons. > That's precisely what I cannot do as there is no current one=20 > (apparently). It's now fixed in CVS. > >> Severe problems when a document is not utf-8 encoded. > > > > I hope it's fixed in CVS, now all file names are converted to UTF-8 > > before writting. > I'll see this later. But the problem was not with the file name, but=20 > with the contents and I don't speak of document list, but mere=20 > document. Could you please elaborate it a little and/or send me the file ? The UTF conversion/detection code have not changed from last release. Regards. --=20 Iago Rubio =20 - Home page * http://www.iagorubio.com=20 - Last project * http://cssed.sourceforge.net =20 - GPG Keyserv * pgp.rediris.es id=3D0x909BD4DD |
From: <mic...@ea...> - 2005-02-09 16:51:29
Attachments:
PGP.sig
micmaciso.css
|
Le 9 févr. 2005, à 17:41, Iago Rubio a écrit : >>>> Severe problems when a document is not utf-8 encoded. > Could you please elaborate it a little and/or send me the file ? > > The UTF conversion/detection code have not changed from last release. Maybe not the detection, but the handling probably since I've never seen this behaviour before. It's hard to explain because I should make a movie to explain what happens: This message repeats constantly in console= ** (cssed:19170): WARNING **: Invalid UTF8 string passed to pango_layout_set_text() The line is cut and cssed tries constantly to redraw it. If I move the cursor, some characters of the line are inserted in a new line below the given line, or removed, well cssed is kind of movie player. Here's the file: |
From: Iago R. <iag...@hi...> - 2005-02-09 17:23:17
|
On Wed, 2005-02-09 at 17:51, Mich=C3=A8le Garoche wrote: > Le 9 f=C3=A9vr. 2005, =C3=A0 17:41, Iago Rubio a =C3=A9crit : >=20 > >>>> Severe problems when a document is not utf-8 encoded. > > Could you please elaborate it a little and/or send me the file ? > > > > The UTF conversion/detection code have not changed from last release. > Maybe not the detection, but the handling probably since I've never=20 > seen this behaviour before. I was not even touched a single line of code. > It's hard to explain because I should make a movie to explain what=20 > happens: >=20 > This message repeats constantly in console=3D > ** (cssed:19170): WARNING **: Invalid UTF8 string passed to=20 > pango_layout_set_text() > The line is cut and cssed tries constantly to redraw it. > If I move the cursor, some characters of the line are inserted in a new=20 > line below the given line, or removed, well cssed is kind of movie=20 > player. I've seen this in some bogus files with characters that did not match any encoding but never in "normal" files. With normal I mean, written with a keyboard, as the weird behaviour on the files I mentioned, was caused by characters completly out of keyboard's range. Have you tried to forze other encoding ? > Here's the file: Will take a look at this, but at first sight it seems ISO-8859, if it's not well rendered with "Default" encoding, then we've got a problem. ITOH it's passes g_utf8_validate checks, not being utf8. --=20 Iago Rubio =20 - Home page * http://www.iagorubio.com=20 - Last project * http://cssed.sourceforge.net =20 - GPG Keyserv * pgp.rediris.es id=3D0x909BD4DD |
From: <mic...@ea...> - 2005-02-09 17:30:26
Attachments:
PGP.sig
|
Le 9 f=E9vr. 2005, =E0 18:23, Iago Rubio a =E9crit : > On Wed, 2005-02-09 at 17:51, Mich=E8le Garoche wrote: >> Le 9 f=E9vr. 2005, =E0 17:41, Iago Rubio a =E9crit : > I've seen this in some bogus files with characters that did not match > any encoding but never in "normal" files. That was my normal file. Maybe it's BBEdit which makes weird things,=20 strange though, because it works in 0.3.0. > > With normal I mean, written with a keyboard, as the weird behaviour on > the files I mentioned, was caused by characters completly out of > keyboard's range. I promise it was written with a keyboard :-) > Have you tried to forze other encoding ? Yes, I've used bluefish to encode it in utf-8 under a new name, then it=20= passes correctly through cssed. > >> Here's the file: > > Will take a look at this, but at first sight it seems ISO-8859, if = it's > not well rendered with "Default" encoding, then we've got a problem. Normally, it's ISO-8859-15. Mich=E8le <http://micmacfr.homeunix.org> |
From: Iago R. <iag...@hi...> - 2005-02-09 17:37:36
|
On Wed, 2005-02-09 at 17:51, Mich=C3=A8le Garoche wrote: > Le 9 f=C3=A9vr. 2005, =C3=A0 17:41, Iago Rubio a =C3=A9crit : >=20 > >>>> Severe problems when a document is not utf-8 encoded. > > Could you please elaborate it a little and/or send me the file ? > > > > The UTF conversion/detection code have not changed from last release. > Maybe not the detection, but the handling probably since I've never=20 > seen this behaviour before. > It's hard to explain because I should make a movie to explain what=20 > happens: I see the problem. May be it's fixed in CVS. Could you please take a test ? Thanks in advance. --=20 Iago Rubio =20 - Home page * http://www.iagorubio.com=20 - Last project * http://cssed.sourceforge.net =20 - GPG Keyserv * pgp.rediris.es id=3D0x909BD4DD |
From: <mic...@ea...> - 2005-02-09 19:31:26
Attachments:
PGP.sig
|
Le 9 f=E9vr. 2005, =E0 18:37, Iago Rubio a =E9crit : > On Wed, 2005-02-09 at 17:51, Mich=E8le Garoche wrote: >> Le 9 f=E9vr. 2005, =E0 17:41, Iago Rubio a =E9crit : >> >>>>>> Severe problems when a document is not utf-8 encoded. >>> Could you please elaborate it a little and/or send me the file ? >>> >>> The UTF conversion/detection code have not changed from last = release. >> Maybe not the detection, but the handling probably since I've never >> seen this behaviour before. >> It's hard to explain because I should make a movie to explain what >> happens: > > I see the problem. May be it's fixed in CVS. > > Could you please take a test ? Works fine now. Perfect. Mich=E8le <http://micmacfr.homeunix.org> |
From: Iago R. <iag...@hi...> - 2005-02-09 16:40:20
|
On Wed, 2005-02-09 at 08:47, Mich=C3=A8le Garoche wrote: > Le 6 f=C3=A9vr. 2005, =C3=A0 11:57, Iago Rubio a =C3=A9crit : >=20 > > * Document list - There's a new entry on the Document menu called > > "Document list" that shows a dialog will the opened documents in a=20 > > list. > > This list can be saved and loaded to and from a file (in XML format). > Impossible to save the list, as the dialog which opens does not create=20 > a file but ask to choose an existing file. Ah! Now I see. The gtk-2.4 file chooser don't let you select a file name to save but a existing file, isn't it ? Fixed in CVS. --=20 Iago Rubio =20 - Home page * http://www.iagorubio.com=20 - Last project * http://cssed.sourceforge.net =20 - GPG Keyserv * pgp.rediris.es id=3D0x909BD4DD |
From: <mic...@ea...> - 2005-02-09 08:20:15
Attachments:
PGP.sig
|
Le 6 f=E9vr. 2005, =E0 11:57, Iago Rubio a =E9crit : > * 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. The red flag makes the file name almost unreadable on Mac, as the=20 default foreground color is slight gray. And the more I think of it, the more I find it very inconvenient, since=20= it overrides the colour sets by gtk theme (especially customized one),=20= if any. Or the user should have the choice (via a color well, in order not to=20 reduce the choice) of overriding also the foreground color and applies=20= the combination with fits him best. Mich=E8le <http://micmacfr.homeunix.org> |
From: Iago R. <iag...@hi...> - 2005-02-09 11:13:22
|
On Wed, 2005-02-09 at 09:20, Mich=C3=A8le Garoche wrote: > Le 6 f=C3=A9vr. 2005, =C3=A0 11:57, Iago Rubio a =C3=A9crit : >=20 > > * 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. > The red flag makes the file name almost unreadable on Mac, as the=20 > default foreground color is slight gray. Yes, I noticed something like that in my laptop were color a bit fuzzy. > And the more I think of it, the more I find it very inconvenient, since=20 > it overrides the colour sets by gtk theme (especially customized one),=20 > if any. It will always happen :) The gtk-theme have support only to defaults and have no choice options were the user could set a list of choices for colouring the same or similar widgets. > Or the user should have the choice (via a color well, in order not to=20 > reduce the choice) of overriding also the foreground color and applies=20 > the combination with fits him best. I will go for it, but with named colours. There're a pletora of them to select so I think it will not cut drasticaly users' choice. Or may be I could try a colour wheel as it was done on the preferences dialog's highlighting tab. One or another, Is the overall idea ok ? It seems useful to me when working in a big bunch of files. Have anyone a better idea on how to mark a set of documents ? Regards. --=20 Iago Rubio =20 - Home page * http://www.iagorubio.com=20 - Last project * http://cssed.sourceforge.net =20 - GPG Keyserv * pgp.rediris.es id=3D0x909BD4DD |
From: <mic...@ea...> - 2005-02-09 11:23:42
Attachments:
PGP.sig
|
Le 9 f=E9vr. 2005, =E0 12:12, Iago Rubio a =E9crit : > On Wed, 2005-02-09 at 09:20, Mich=E8le Garoche wrote: >> Le 6 f=E9vr. 2005, =E0 11:57, Iago Rubio a =E9crit : >> >>> * 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. >> The red flag makes the file name almost unreadable on Mac, as the >> default foreground color is slight gray. > > Yes, I noticed something like that in my laptop were color a bit = fuzzy. I've already inserted a flag for Mac (not commited yet). > The gtk-theme have support only to defaults and have no choice options > were the user could set a list of choices for colouring the same or > similar widgets. Not a list of choice, but you can customize ~/gtk-2.0.rc file? I've=20 customized mine with the plain #xxyyzz colors. Hence it may happen that=20= it chocks with fixed colors authorized within cssed. > Or may be I could try a colour wheel as it was done on the preferences > dialog's highlighting tab. Or if you are speedy for release, we could stick temporarily with as=20 is, just I've inserted the flag for Mac. > > One or another, Is the overall idea ok ? It seems useful to me when > working in a big bunch of files. Yes, why not, it is not my way of practice, but it may be convenient=20 for users. Anyway, that's a choice, so, it won't hurt. > Have anyone a better idea on how to mark a set of documents ? I don't know if it is possible, but I would have done a super tab, to=20 group together given documents. But not sure it is better as idea. Colors seems to me possible, but provided that the user could override=20= both background and foreground colors, as you'll never know what colors=20= the user has. Mich=E8le <http://micmacfr.homeunix.org> |
From: <mic...@ea...> - 2005-02-09 09:07:52
Attachments:
PGP.sig
|
Le 6 f=E9vr. 2005, =E0 11:57, Iago Rubio a =E9crit : > * 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. Instead of "Flag" in menu, which has no trivial sense for the user,=20 woud not "Change tab color" be better (no need for Document, since it=20 is already in the Document menu)? Mich=E8le <http://micmacfr.homeunix.org> |