Older blog entries for iagorubio (starting at number 3)

As SCO's is running the Sex Pistols' way of try a gain, I finally decided to involve personally, and put my 2 cents against this company.

I know that as an individual, I can do almost nothing to fight SCO.

So, what have I done ?

First of all I drop support for all SCO distros on my project, so bugs from any of the Caldera/SCO distros will be simply ignored by me.

I know that's almost nothing as a little CSS editor is not supposed to be in a SCO Unix server system, but Fyodor have drop Nmap support to those distros and, I'm sure, if more developers do the same, it will hurt.

If all Open Source community drop support for UnixWare and family, SCO user's will have less resources so SCO's distros will be - even - less attractive.

Then I think, how can a company consider a License void and illegal, but accept it's terms ?

GPL's point five states :

Are public challeges considering it "void" and "illegal" enough to prove non acceptance of a License's terms ?

I think that yes, it's enough, so I added a legal notice to the cssed project's site.

If you ask me if I can defend it in court, I will answer that no, it's sure I can not spend the funds required, but I fell much better since I wrote this down ;)

Preparing cssed for a new release, I was wondering about memory management.

I checked - not one but twice - all buffers allocated by cssed were released, but the doubt was in the air.

I didn't like very much memprof, so I decided to try valgrin.

The results of the tests where doubly satisfactory: I didn't find memory leaks in cssed's code, and I find a great tool for memory checking.

valgrid did a great job, checking the program for memory problems.

I build some test apps, to check results, and it found every memory leak and race condition, pointing to source file and line number.

I'm sure it's in my tool box to stay ;)

You've got it here http://valgrind.kde.org/

Chris Hornbaker (Quanta+) have started a discussion about the creation of an XML based function reference format, common to all Linux web editors.

Olivier Sessink (Bluefish) and Dodji Seketeli (MLView and libcroco) have just joined the list.

I think it's a great idea to try to build standards between open source applications. This will help users to choose in freedom as they'll know their reference files will work in all web editors.

As I know both Dodji and Olivier ( well I mailed Dodji a couple of times, and I help Olivier in the Bluefish project actively) I'm sure I will join the list, to put my 2 cents on the project.

That's something closed source developers can't even dream about ;)

The list is here: https://sourceforge.net/mail/?group_id=50363 </b></b>

Well, finally I decided to put something here.

I didn't put anything in this diary, because my english is really poor, but - may be - it's a good moment to try to learn it, and the only way to learn anything, is using it.

Other thing that get me far from diaries, weblogs and stuff like that, is I'm not a *guru* or *influent* man, that should spread my word around the world, telling people how they must think, or what they must do.

The net is plenty of such kinds of blogs where not important people, say not important stupid things, in the hope that, someday anyone stop at his blog, and read it.

That's what I will not post here anything about me, my boring life or my personal ideas.

There's only one thing I will speak about here, my current programming project cssed [home page].

If you're looking for any kind of "illumination", a personal guru or a political counsel, it's not a place for you.

Once said that, I will put some words about cssed.

cssed is a small CSS editor for web developers, written in C with GTK2. It uses as editor component the scintilla editor.

Lot of people asked me about why I choose scintilla. Well, the true is I've used scintilla some years ago, and It's full featured, open source and low memory consuming, so my question is: Why I must not use it ?

It works much better that GtkTextView and GtkSourceView. May be when GtkSourceView get a couple of years of development I will switch to it, but right now I recommend everyone to use scintilla.

many people was confused about scintilla itself, there where opinios of all flavors:

• It's propietary
• It's not portable
• It's C++ so you must use C++

But all of them was really confused:

• Scintilla is open source
• Scintilla was done with portability in mind
• Scintilla is a library that can be linked with C code with no problem.

It's other example about the fact that human stupidness is infinite.

It's open source, so wtf you care about it was done for Windows? Is not enought that scintilla's author made it with portability in mind and build a Gtk1 and Gtk2 versions?

Once explained that - cssed use scintilla because I think it's the best editor control for programers build with Gtk - just some words avbout the state of the project, and I'm sure it's enough for my first diary entry.

cssed is right now running for the beta. That means it's still in Alpha but sounds much better ;)

I'm right now changing the API of some dialogs to run them as independent ones -connected to some callbacks - or with gtk_dialog_run and use a function call to get the dialog results. All this dialogs simply returns a string with a CSS declaration.

That's the main and boring task that gets me working hard.

I will start to describe my advances from this point.

But not today ....