[Contents] [TitleIndex] [WordIndex

This report is part of Contributor - Scilab backend to Cantor project.

Scilab backend to Cantor report - 15 August 2011


This is a last report about this project. I will follow the recommendations given by Sylvestre Ledru by e-mail and separate the threads on issues that evaluators want to see.

A full documentation of the final project from the user perspective:

How to build it ?

For build Scilab backend to Cantor, is necessary learn how build a KDE application to compile and install Cantor software and build Scilab master branch.

These links above teach how compile these softwares.

Where is it available ?

This project have code in two different repositories. Scilab backend to Cantor is in scilab-backend branch in Cantor repository, and the Scilab version supported by this project is in Scilab master branch in Scilab repository.

Which version of Scilab is necessary ?

Currently, only the master branch version. But, in the next major realease of Scilab, will be supported.

How it can be used ?

Simply, run Cantor and select Scilab. Cantor load Scilab backend and becomes an Scilab IDE.

When possible, we have to find documentations into the Scilab help system

This project is a Scilab IDE in Cantor. Exist a button with a link to Scilab web documentation. I will write a documentation about how use Cantor IDE to develop code in Scilab programming language.

A technical documentation

The stuff you think we should know

What are the known bugs ?

What should be done next ?

Correct, some bugs in chart load in Cantor workspace and develop unit tests for this backend.

To you, is it a version 0.1 or 1.0 ?

I think this is a "0.9" version. :-) Missing unitary tests and I think that will be interesting more tests. But the main features are implemented and working.

Did you published a tagged tarballs ? Where ?

The KDE project webpage of Cantor provides tarballs for the project. Check in this link.

Did you tried to port your work on an other architecture ?

Currently, I tested it in Linux 64 and 32bits. To test in Windows or OS X, is necessary that KDE port the actual version of Cantor to these operational systems.

How many unitary tests ? Where are they ?

Currently, they are missing.

Are you planning to implement what is missing ?

Sure, I want implement unitary tests, correct the problem of caching images and look for more bugs too. I want this backend to be an interesting alternative IDE for Scilab.

Are you planning to maintain it in the future ?

Sure! I want maintain this backend updated with each version of Scilab and Qt/kdelibs that will be release.

Anything you think is relevant

I can only thank the help of the developers of Scilab and Cantor, for this project, while a multi-community project, I had to deal with two communities, two development methodologies and two completely different technologies. However, whenever needed, the two communities helped me with my specific questions. Thank you!

You and the GSoC

Which part took you the longest ?

Work in graphic part. It's very hard and, too, because my video card no have a good supported in Linux.

What do you think we should improve for next year ?

I think that Google could available a value (maybe, 2 thousand dollar) to student travel to country of his mentor and and be there in person some days.

How hard did you consider your subject ?

In the general, no very hard, but some parts was, yes, very hard (for example, Scilab graphic part). My project too was different because it is a "multi-community" project - I sent more code to Cantor, a software that no have relation with Scilab. But I think it very exciting, and in Scilab community and KDE community I found help at times when needed, in their specific technologies.

And of course, what did you do since the last report ?

Now, syntax highlight of pre-defined variables in Scilab is working. Scilab backend load Scilab export charts in Cantor workspace now, but is necessary some work to correct some bugs, yet.

2022-09-08 09:26