cssed-devel — cssed development discussion

[cssed-devel] Changes in cvs

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

I've commited some changes on cvs, and current cvs could be not as
stable as it used to be.

I'm still working on those changes, but I updated to avoid big merges.


- Changed the Document list from the view menu - it clashed with the HIG
as it states this menu must be for changes in the view of the current
document. I moved it temporary to "tools" menu waiting for  a better
idea.

- Updated libcroco to 0.6.0 - this should end in more stable css parsing
routines.

- Changes in the "Digest" list - now when you scan a untitled document
have not the benefit of the caret moving to the location of the
selector, when clicking on the list, but you can scan various CSS files
- not just one - and if the files are closed they'll be opened and the
caret placed at the selector location.

- Changes in "validate and dump" - now the locations in the program
output are also clickable.

- Changes in the document list - now they're reoderable clicking in the
list headers.

... surely I'm missing something ...

Major changes will be arriving at cvs soon. At least I will go for the
expat to libxml port before the next release.
--=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

Re: [cssed-devel] Changed accelerator in Document

[<mic...@ea...>]

Le 19 f=E9vr. 2005, =E0 20:27, Iago Rubio a =E9crit :

> On Sat, 2005-02-19 at 20:03, Mich=E8le Garoche wrote:
>>>> That is correct, is not it?
>>>
>>> Yes, it's correct to start documenting the code, but will not help=20=

>>> with
>>> he plugin's doc - that's what I tried to tell you in the previous=20
>>> three
>>> messages :)
>> Oh, sorry, I did not want to touch src, hiding in the corner.
>
> Don't worry, no problem at all :)
>
>> It can be left as is for the future when doc will be done for =
sources.
>
> Yes, indeed will be left there, so I will continue documenting the =
code
> meanwhile I work in the current changes.
>
> It can even help to find possible changes.
There is a problem though, because the headers in include are wrong:=20
for example it lacks of some enums (Makefile , etc.)

Mich=E8le
<http://micmacfr.homeunix.org>

Re: [cssed-devel] Release delayed.

[<mic...@ea...>]

Le 19 f=E9vr. 2005, =E0 20:27, Iago Rubio a =E9crit :

> On Sat, 2005-02-19 at 20:07, Mich=E8le Garoche wrote:
>> I'm currently working on the doc, so I don't commit anything.
>
> Oh!, please check this http://cssed.sourceforge.net/cssed-doc.tgz

>
> It have some work in progress that - may be - can help you. The main
> work done, is to split the docs in chapters and to change it to book
> instead of article.
>
> If it's not useful simply discard it.
It's already done for a long time: book, chapter, section and so on.

I'll have a look at it though.

Mich=E8le
<http://micmacfr.homeunix.org>

Re: [cssed-devel] Changed accelerator in Document

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

On Sat, 2005-02-19 at 20:03, Mich=C3=A8le Garoche wrote:
> >> That is correct, is not it?
> >
> > Yes, it's correct to start documenting the code, but will not help with
> > he plugin's doc - that's what I tried to tell you in the previous three
> > messages :)
> Oh, sorry, I did not want to touch src, hiding in the corner.

Don't worry, no problem at all :)

> It can be left as is for the future when doc will be done for sources.

Yes, indeed will be left there, so I will continue documenting the code
meanwhile I work in the current changes.

It can even help to find possible changes.
--=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

Re: [cssed-devel] Release delayed.

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

On Sat, 2005-02-19 at 20:07, Mich=C3=A8le Garoche wrote:
> Le 19 f=C3=A9vr. 2005, =C3=A0 20:03, Iago Rubio a =C3=A9crit :
>=20
> > I've just updated the libcroco to the new version, and it adds a new
> > dependency to libxml2.
> >
> > As we're using expat as XML engine, I will go for a port to libxml2 in
> > all the code so cssed will depend only in one XML parsing engine, and
> > not in two as it would be with this new dependency.
> >
> > This will delay things a bit, but we'll end with less dependencies, and
> > I don't think it's ok to required two different XML parsers for a given
> > application.
> >
> > Does anyone have any problem with this ?
> > Is libxml2 ok in all platforms ? In win32, Linux, and BSD it works.
> >
> > Michelle, any problem with Mac?
> No, libxml2 is here.

Will go for it then.

> > NOTE: please wait a bit to commit to cssed/src and cssed/libcroco as
> > major changes are in progress. If there's a need on commiting anything,
> > please post it in the list so I can update the cvs to avoid clashes.
> I'm currently working on the doc, so I don't commit anything.

Oh!, please check this http://cssed.sourceforge.net/cssed-doc.tgz

It have some work in progress that - may be - can help you. The main
work done, is to split the docs in chapters and to change it to book
instead of article.

If it's not useful simply discard it.
--=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

Re: [cssed-devel] Changed accelerator in Document

[<mic...@ea...>]

Corrected now with the right headers.

>> <http://micmacfr.homeunix.org/cssed/html/index.html>
>

Mich=E8le
<http://micmacfr.homeunix.org>

Re: [cssed-devel] Release delayed.

[<mic...@ea...>]

Le 19 f=E9vr. 2005, =E0 20:03, Iago Rubio a =E9crit :

> I've just updated the libcroco to the new version, and it adds a new
> dependency to libxml2.
>
> As we're using expat as XML engine, I will go for a port to libxml2 in
> all the code so cssed will depend only in one XML parsing engine, and
> not in two as it would be with this new dependency.
>
> This will delay things a bit, but we'll end with less dependencies, =
and
> I don't think it's ok to required two different XML parsers for a =
given
> application.
>
> Does anyone have any problem with this ?
> Is libxml2 ok in all platforms ? In win32, Linux, and BSD it works.
>
> Michelle, any problem with Mac?
No, libxml2 is here.


> NOTE: please wait a bit to commit to cssed/src and cssed/libcroco as
> major changes are in progress. If there's a need on commiting =
anything,
> please post it in the list so I can update the cvs to avoid clashes.
I'm currently working on the doc, so I don't commit anything.

Mich=E8le
<http://micmacfr.homeunix.org>

Re: [cssed-devel] Changed accelerator in Document

[<mic...@ea...>]

Le 19 f=E9vr. 2005, =E0 19:53, Iago Rubio a =E9crit :

> On Sat, 2005-02-19 at 18:50, Mich=E8le Garoche wrote:
>> Le 19 f=E9vr. 2005, =E0 18:33, Iago Rubio a =E9crit :
>>
>>> On Sat, 2005-02-19 at 12:49, Mich=E8le Garoche wrote:
>>>> The doxygen file hides those internal functions, so that should be=20=

>>>> not
>>>> a problem, or maybe I don't understand exactly what you mean.
>>>
>>> It's not a problem Michelle, not at all.
>>>
>>> What I meant was, some publicly exposed functions in some of the
>>> headers
>>> located in src, are not meant to be plugin functions, so we cannot
>>> generate the documentation with the cssed headers - those located in
>>> "cssed/src" -
>>>  but with the plugin's headers - those located in
>>> "include".
>> Sure, I have not put all the headers in cssed/src; just the ones used
>> in plugins, that is:
>> cssdialogs-class.h
>> cssedwindow.h
>> document.h
>> plugin.h
>> SciLexer.h
>> Scintilla.h
>> ScintillaWidget.h
>>
>> That is correct, is not it?
>
> Yes, it's correct to start documenting the code, but will not help =
with
> he plugin's doc - that's what I tried to tell you in the previous =
three
> messages :)
Oh, sorry, I did not want to touch src, hiding in the corner.

It can be left as is for the future when doc will be done for sources.

Mich=E8le
<http://micmacfr.homeunix.org>

[cssed-devel] Release delayed.

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

I've just updated the libcroco to the new version, and it adds a new
dependency to libxml2.

As we're using expat as XML engine, I will go for a port to libxml2 in
all the code so cssed will depend only in one XML parsing engine, and
not in two as it would be with this new dependency.

This will delay things a bit, but we'll end with less dependencies, and
I don't think it's ok to required two different XML parsers for a given
application.

Does anyone have any problem with this ?
Is libxml2 ok in all platforms ? In win32, Linux, and BSD it works.

Michelle, any problem with Mac?

NOTE: please wait a bit to commit to cssed/src and cssed/libcroco as
major changes are in progress. If there's a need on commiting anything,
please post it in the list so I can update the cvs to avoid clashes.
--=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

Re: [cssed-devel] Changed accelerator in Document

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

On Sat, 2005-02-19 at 18:50, Mich=C3=A8le Garoche wrote:
> Le 19 f=C3=A9vr. 2005, =C3=A0 18:33, Iago Rubio a =C3=A9crit :
>=20
> > On Sat, 2005-02-19 at 12:49, Mich=C3=A8le Garoche wrote:
> >> The doxygen file hides those internal functions, so that should be not
> >> a problem, or maybe I don't understand exactly what you mean.
> >
> > It's not a problem Michelle, not at all.
> >
> > What I meant was, some publicly exposed functions in some of the=20
> > headers
> > located in src, are not meant to be plugin functions, so we cannot
> > generate the documentation with the cssed headers - those located in
> > "cssed/src" -
> >  but with the plugin's headers - those located in
> > "include".
> Sure, I have not put all the headers in cssed/src; just the ones used=20
> in plugins, that is:
> cssdialogs-class.h
> cssedwindow.h
> document.h
> plugin.h
> SciLexer.h
> Scintilla.h
> ScintillaWidget.h
>=20
> That is correct, is not it?

Yes, it's correct to start documenting the code, but will not help with
he plugin's doc - that's what I tried to tell you in the previous three
messages :)

> Then the SciLexer and Scintilla headers do not need documentation at=20
> all.

Only one function needed to manage scintilla scintilla_send_message()

> There are only some functions in the other headers which are not=20
> commented.
>=20
> > That's why I did not documented all the functions on the headers at
> > "cssed/src" but those at "cssed/include".
> I spoke about those of course, sorry for the misunderstanding.
>=20
> You can see what it becomes here - a work in progress (I've slightly=20
> changed the doxyfile to show all functions, even if not documented).
> <http://micmacfr.homeunix.org/cssed/html/index.html>

It's a nice start point for the main code documentation, but the code is
still a bit messy to be documented.=20

I'm also going for major changes ...
--=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

Re: [cssed-devel] Changed accelerator in Document

[<mic...@ea...>]

Le 19 f=E9vr. 2005, =E0 18:33, Iago Rubio a =E9crit :

> On Sat, 2005-02-19 at 12:49, Mich=E8le Garoche wrote:
>> The doxygen file hides those internal functions, so that should be =
not
>> a problem, or maybe I don't understand exactly what you mean.
>
> It's not a problem Michelle, not at all.
>
> What I meant was, some publicly exposed functions in some of the=20
> headers
> located in src, are not meant to be plugin functions, so we cannot
> generate the documentation with the cssed headers - those located in
> "cssed/src" -
>  but with the plugin's headers - those located in
> "include".
Sure, I have not put all the headers in cssed/src; just the ones used=20
in plugins, that is:
cssdialogs-class.h
cssedwindow.h
document.h
plugin.h
SciLexer.h
Scintilla.h
ScintillaWidget.h

That is correct, is not it?

Then the SciLexer and Scintilla headers do not need documentation at=20
all.
There are only some functions in the other headers which are not=20
commented.

> That's why I did not documented all the functions on the headers at
> "cssed/src" but those at "cssed/include".
I spoke about those of course, sorry for the misunderstanding.

You can see what it becomes here - a work in progress (I've slightly=20
changed the doxyfile to show all functions, even if not documented).
<http://micmacfr.homeunix.org/cssed/html/index.html>

Mich=E8le
<http://micmacfr.homeunix.org>

Re: [cssed-devel] Changed accelerator in Document

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

On Sat, 2005-02-19 at 12:49, Mich=C3=A8le Garoche wrote:
> The doxygen file hides those internal functions, so that should be not=20
> a problem, or maybe I don't understand exactly what you mean.

It's not a problem Michelle, not at all.

What I meant was, some publicly exposed functions in some of the headers
located in src, are not meant to be plugin functions, so we cannot
generate the documentation with the cssed headers - those located in
"cssed/src" - but with the plugin's headers - those located in
"include".

If we generate the plugins docs with the cssed headers some public=20
functions - that I don't want to expose to plugins - will be shown so
used.

That's why I did not documented all the functions on the headers at
"cssed/src" but those at "cssed/include".

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

Re: [cssed-devel] Changed accelerator in Document

[<mic...@ea...>]

Le 19 f=E9vr. 2005, =E0 12:45, Iago Rubio a =E9crit :

> On Fri, 2005-02-18 at 18:41, Mich=E8le Garoche wrote:
>> I've also integrated comments in header for plugindoc, to avoid
>> reinvent the wheel.
>
> I didn't do it because the plugin's headers are not meant to be =
exactly
> the same as the application headers.
>
> Some functions are taken out for convenience, because are not ready to
> be public, and expose internall functions not needed for plugin's
> development.
>
> That's why there's a separated set of headers distributed in the=20
> include
> directory for external developers. Are not exactly the same - or=20
> better,
> are not meant to be the same - as the internally used ones.
>
> Of course the functions that appears in the plugin's headers are=20
> exactly
> the same on the application's headers.
The doxygen file hides those internal functions, so that should be not=20=

a problem, or maybe I don't understand exactly what you mean.

Mich=E8le
<http://micmacfr.homeunix.org>

Re: [cssed-devel] Changed accelerator in Document

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

On Fri, 2005-02-18 at 18:41, Mich=C3=A8le Garoche wrote:
> I've changed accelerator in Document/highlighting for Plain text to=20
> avoid chocking with C/CPP accelerator.

Ok, thanks.

> I've also integrated comments in header for plugindoc, to avoid=20
> reinvent the wheel.=20

I didn't do it because the plugin's headers are not meant to be exactly
the same as the application headers.

Some functions are taken out for convenience, because are not ready to
be public, and expose internall functions not needed for plugin's
development.

That's why there's a separated set of headers distributed in the include
directory for external developers. Are not exactly the same - or better,
are not meant to be the same - as the internally used ones.

Of course the functions that appears in the plugin's headers are exactly
the same on the application's headers.

> Some functions are not documented at the time

Yes, because I did not documented the code.=20

May be I should start to do it, but right now functions that are not
"public" are not documented.=20

The documentation is for the plugins, not for the applications
developer's docs - that does not exists at the moment.

I was waiting to a have a cleaner code to document it.=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

[cssed-devel] Changed accelerator in Document

[<mic...@ea...>]

I've changed accelerator in Document/highlighting for Plain text to 
avoid chocking with C/CPP accelerator.
I've also integrated comments in header for plugindoc, to avoid 
reinvent the wheel. Some functions are not documented at the time 
being.

Committed.

Re: [cssed-devel] Added accelerators to Convert EOLs

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

On Fri, 2005-02-18 at 10:15, Mich=C3=A8le Garoche wrote:
> To avoid chocking with items in the main submenu. Committed.

Updated thanks.
--=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

[cssed-devel] Added accelerators to Convert EOLs

[<mic...@ea...>]

To avoid chocking with items in the main submenu. Committed.

Re: [cssed-devel] Format of documentation

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

On Fri, 2005-02-11 at 20:40, Mich=C3=A8le Garoche wrote:
> Le 11 f=C3=A9vr. 2005, =C3=A0 20:21, Iago Rubio a =C3=A9crit :
>=20
> > On Fri, 2005-02-11 at 20:02, Mich=C3=A8le Garoche wrote:
> >> Le 11 f=C3=A9vr. 2005, =C3=A0 19:54, Iago Rubio a =C3=A9crit :
> >>
> >>> On Fri, 2005-02-11 at 17:52, Mich=C3=A8le Garoche wrote:
> >>>> Le 11 f=C3=A9vr. 2005, =C3=A0 17:48, Iago Rubio a =C3=A9crit :
> >>>>
> >>>>> On Fri, 2005-02-11 at 11:22, Mich=C3=A8le Garoche wrote:
> >>>>>> Le 11 f=C3=A9vr. 2005, =C3=A0 11:17, Iago Rubio a =C3=A9crit :
> >>>>>>
> >>>>>>> On Fri, 2005-02-11 at 06:19, Mich=C3=A8le Garoche wrote:
> >>> [snip]
> >>>>> Saxon have not even packages for Linux but a zip, and is not in the
> >>>>> most
> >>>>> common distros.
> >>>> Java is free, Saxon is free.
> >> Unless I've missed something, Sun as released Java as free open source
> >> package last year.
> >
> > Where is such distribution ?
> > http://java.com/en/download/license.jsp

I'm sure you got confused with the Solaris OS that was opened by Sun
last year. But they retained licensing on Java.

> You need no more than the virtual machine, it is integrated in any=20
> system, no?

That's the problem.

As it's a non free package most Linux distributions don't ship it - well
no Linux distribution but Novell's one.

As it's not shipped by distributions, it does not fit in the system
update tools, and have no automatic updates.

Users should go to the Java.com page and accept a license to get the
software but it's not integrated in the software management system tools
at all.

> Oh, well, I don't discuss anymore on this. It leads to nowhere. Every=20
> system has a part which is not open source, be it hardware, middleware=20
> or software, hence with your logic, you cannot deliver anything.

That's what should be changed. Computing is not bounded to closed
licenses, and a completely open system is nearest today than ever.

There's an open hardware movement, and an open bios project working
right now.=20

Open source software is a success and I'd like to continue contributing
to it. To use or require closed source tools, is not the way to achieve
the goal of completely free systems, but the way to spread dependencies
on closed systems.

I know it's a kind of zealotry, but well ... the only way to go for it
is being a bit zealot.

> And by the way, it is not mandatory to deliver the sources, just the=20
> output, which can be done in a4 and us formats if needed.

I know that, but I want to post the sources so anyone willing to help
could be able to contribute to the documentation.

If anyone offers help with the docs, I don't want to tell him he should
accept a closed license, and install closed source packages.

Take into account that downloading Java, you're accepting - among other
things - to pay even attorney fees if anyone hungry enough sues Sun for
something you made related with Java.

That's too much for lots of people.

With this I don't say I don't use Java. You can even download some Open
Source Java applications written by me long time ago.=20

But what I don't want to do is to make mandatory to install Java to
build the docs.

I could be all right if there are makefiles to use with saxon to get=20
better looking docs, but only if there are makefiles to use with open
source tools to achieve a ugliest - but usable - result.=20

Unfortunately, to maintain those dual build scripts will be a burden,
and lots of compatibility issues will arise sooner or later.

Is possible to build only the PDFs with saxon and the HTML with open
source tools ?

I suppose xsltproc can make the transformation from XML/XSLT to HTML.

Am I right ?
--=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

Re: [cssed-devel] Format of documentation

[<mic...@ea...>]

Le 11 f=E9vr. 2005, =E0 20:21, Iago Rubio a =E9crit :

> On Fri, 2005-02-11 at 20:02, Mich=E8le Garoche wrote:
>> Le 11 f=E9vr. 2005, =E0 19:54, Iago Rubio a =E9crit :
>>
>>> On Fri, 2005-02-11 at 17:52, Mich=E8le Garoche wrote:
>>>> Le 11 f=E9vr. 2005, =E0 17:48, Iago Rubio a =E9crit :
>>>>
>>>>> On Fri, 2005-02-11 at 11:22, Mich=E8le Garoche wrote:
>>>>>> Le 11 f=E9vr. 2005, =E0 11:17, Iago Rubio a =E9crit :
>>>>>>
>>>>>>> On Fri, 2005-02-11 at 06:19, Mich=E8le Garoche wrote:
>>> [snip]
>>>>> Saxon have not even packages for Linux but a zip, and is not in =
the
>>>>> most
>>>>> common distros.
>>>> Java is free, Saxon is free.
>> Unless I've missed something, Sun as released Java as free open =
source
>> package last year.
>
> Where is such distribution ?
> http://java.com/en/download/license.jsp
You need no more than the virtual machine, it is integrated in any=20
system, no?

Oh, well, I don't discuss anymore on this. It leads to nowhere. Every=20
system has a part which is not open source, be it hardware, middleware=20=

or software, hence with your logic, you cannot deliver anything.

And by the way, it is not mandatory to deliver the sources, just the=20
output, which can be done in a4 and us formats if needed.

Mich=E8le
<http://micmacfr.homeunix.org>

Re: [cssed-devel] Format of documentation

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

On Fri, 2005-02-11 at 20:02, Mich=C3=A8le Garoche wrote:
> Le 11 f=C3=A9vr. 2005, =C3=A0 19:54, Iago Rubio a =C3=A9crit :
>=20
> > On Fri, 2005-02-11 at 17:52, Mich=C3=A8le Garoche wrote:
> >> Le 11 f=C3=A9vr. 2005, =C3=A0 17:48, Iago Rubio a =C3=A9crit :
> >>
> >>> On Fri, 2005-02-11 at 11:22, Mich=C3=A8le Garoche wrote:
> >>>> Le 11 f=C3=A9vr. 2005, =C3=A0 11:17, Iago Rubio a =C3=A9crit :
> >>>>
> >>>>> On Fri, 2005-02-11 at 06:19, Mich=C3=A8le Garoche wrote:
> > [snip]
> >>> Saxon have not even packages for Linux but a zip, and is not in the
> >>> most
> >>> common distros.
> >> Java is free, Saxon is free.
> Unless I've missed something, Sun as released Java as free open source=20
> package last year.

Where is such distribution ?
http://java.com/en/download/license.jsp

--=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

Re: [cssed-devel] Format of documentation

[<mic...@ea...>]

Le 11 f=E9vr. 2005, =E0 19:54, Iago Rubio a =E9crit :

> On Fri, 2005-02-11 at 17:52, Mich=E8le Garoche wrote:
>> Le 11 f=E9vr. 2005, =E0 17:48, Iago Rubio a =E9crit :
>>
>>> On Fri, 2005-02-11 at 11:22, Mich=E8le Garoche wrote:
>>>> Le 11 f=E9vr. 2005, =E0 11:17, Iago Rubio a =E9crit :
>>>>
>>>>> On Fri, 2005-02-11 at 06:19, Mich=E8le Garoche wrote:
> [snip]
>>> Saxon have not even packages for Linux but a zip, and is not in the
>>> most
>>> common distros.
>> Java is free, Saxon is free.
Unless I've missed something, Sun as released Java as free open source=20=

package last year.

Mich=E8le
<http://micmacfr.homeunix.org>

Re: [cssed-devel] Format of documentation

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

On Fri, 2005-02-11 at 17:52, Mich=C3=A8le Garoche wrote:
> Le 11 f=C3=A9vr. 2005, =C3=A0 17:48, Iago Rubio a =C3=A9crit :
>=20
> > On Fri, 2005-02-11 at 11:22, Mich=C3=A8le Garoche wrote:
> >> Le 11 f=C3=A9vr. 2005, =C3=A0 11:17, Iago Rubio a =C3=A9crit :
> >>
> >>> On Fri, 2005-02-11 at 06:19, Mich=C3=A8le Garoche wrote:
[snip]
> > Saxon have not even packages for Linux but a zip, and is not in the=20
> > most
> > common distros.
> Java is free, Saxon is free.

Java is free as beer, but not as speech. Saxon depends on Java :)

> > Are there other free software options avaiable ?
> For pdf output, no.

We should stuck in the old format then.

I will not ask to install a non open source package, for building docs.

All should be free - as speech - from the ground up.

At least upstream build scripts should depend only on open source
packages.

If it exists the posibility of improve something with non open source
tools, great. But I will not distribute packages with such dependencies.

At least not in the cssed project's page. May be I could do it in my
personal page, but only as an alternative.

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

Re: [cssed-devel] Draggable documents not working

[<mic...@ea...>]

Le 11 f=E9vr. 2005, =E0 19:26, Iago Rubio a =E9crit :
> I'm planning to change it as it fails on Windows. I'd try to use the
> document's label, instead of the button to track d'n'd actions.
Yes, it will be more intuitive and give more space to make the drop.

Mich=E8le
<http://micmacfr.homeunix.org>

Re: [cssed-devel] Draggable documents not working

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

On Thu, 2005-02-10 at 21:48, Mich=C3=A8le Garoche wrote:
> Le 10 f=C3=A9vr. 2005, =C3=A0 21:15, Iago Rubio a =C3=A9crit :
>=20
> > On Thu, 2005-02-10 at 11:29, Mich=C3=A8le Garoche wrote:
> >> I cannot get this behaviour working.
> >
> > I've seen in Gtk-2.4 for window this failing also, but working on
> > gtk-2.2.
> >
> > What are the symptoms in your system ?
> >
> > Does the document get closed when you click it and drag out without
> > releaseing the button ?
> >
> > It'd be nice if you could elaborate it a little.
> No, nothing happens, so that I cannot elaborate.
>=20
> Sorry it works, but I did not know you have to click on the cross, then=20
> I have to wait a very long time to get the drag, and I should put it on=20
> the other cross, otherwise it does not work.

I'm planning to change it as it fails on Windows. I'd try to use the
document's label, instead of the button to track d'n'd actions.

--=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

Re: [cssed-devel] Problems in starting win-version...

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

On Fri, 2005-02-11 at 17:55, Xenofon Grigoriadis wrote:
> Iago Rubio wrote:
>=20
> >Could you please search your registry for the key
> >HKLM\Software\GTK\2.0\Path ?
> >
> >Is it present ?
> > =20
> >
> yap. Here is the value of the key: "C:\Programme\Common Files\GTK\2.0"
> So I don't think this could so wrong... And by the way the version=20
> string found in the same path of the registry is "2.4.7.0" and Revision=20
> is "a".

It's fine.

> >The pre-release package is at
> >http://iagorubio.com/gtk/cssed-pre-0.3.1-gtk2.4.exe
> >
> >Please uninstall the previous package to avoid clashes, even while it's
> >not mandatory.=20
> > =20
> I just tried that one too, but I get the same message.=20

I'm sorry.

> Sorry, really, I=20
> don't mean spoiling your weekend.

Your whish then, but I'll spoil most of the weekend with cssed one way
or another.

If you'd like to take another try, just post it here.

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