From BlanchardJ at ieee.org Thu Jun 2 15:45:11 2011 From: BlanchardJ at ieee.org (Jonathan Blanchard) Date: Thu, 2 Jun 2011 10:45:11 -0300 Subject: First release of MPScilab Message-ID: Hi everyone, After more than two years in development the first release of MPScilab finally happened last week with the availability of version 0.1 both in source form and binary distribution for Linux and Windows. MPScilab saw its initial development sponsored as a Google Summer of Code project in 2009 with Matthew Arsenault as the student. MPScilab can be obtained from its ATOMS module page : http://atoms.scilab.org/toolboxes/MPScilab Feedback, bug reports and feature requests are welcome! Cheers, Jonathan Blanchard From clement.david at scilab.org Fri Jun 10 17:02:34 2011 From: clement.david at scilab.org (=?ISO-8859-1?Q?Cl=E9ment?= David) Date: Fri, 10 Jun 2011 17:02:34 +0200 Subject: Git pre-commit indentation hook Message-ID: <1307718154.28602.4.camel@pinarellu.inria.fr> Hi all, I just want to share my pre-commit hook which indent C/C++ files with 'indent` and XML/Xcos files with 'xmllint` just before the commit message edition. I hope it will help you. PS: I love criticism, do not hesitate :) -- Cl?ment David -------------- next part -------------- A non-text attachment was scrubbed... Name: pre-commit Type: application/x-shellscript Size: 1754 bytes Desc: not available URL: From xwang1976 at email.it Sat Jun 11 12:01:02 2011 From: xwang1976 at email.it (xwang1976 at email.it) Date: Sat, 11 Jun 2011 12:01:02 +0200 Subject: Idea for XCOS improvement Message-ID: <4DF33CDE.8040003@email.it> Hi to all, I'm a Simulink/Matlab user and I would like to use XCOS as an open source alternative. The most important thing that keep me from using it is the lack of the possibility to name superblocks inputs and outputs port as it is possible to do in Simulink and Matrixx. This feature is very useful IMHO when the simulated model begins to grow because it clarifies the IO interfaces of the blocks which constitute the model and permit to use a top-down approach with nested superblocks. Is there any plan to implements such a feature? Thank you, Xwang From sylvestre.ledru at scilab.org Sun Jun 12 01:49:44 2011 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Sun, 12 Jun 2011 01:49:44 +0200 Subject: [Scilab-Dev] Git pre-commit indentation hook In-Reply-To: <1307718154.28602.4.camel@pinarellu.inria.fr> References: <1307718154.28602.4.camel@pinarellu.inria.fr> Message-ID: <1307836185.25878.22.camel@losinj.inria.fr> Le vendredi 10 juin 2011 ? 17:02 +0200, Cl?ment David a ?crit : > Hi all, > > I just want to share my pre-commit hook which indent C/C++ files with > 'indent` and XML/Xcos files with 'xmllint` just before the commit > message edition. > > I hope it will help you. > > PS: I love criticism, do not hesitate :) Thanks. I don't criticize (for once) but propose that we add them into the repository to share it. CF this commit: http://codereview.scilab.org/#change,4200 which can be enabled by: cd .git/ mv hooks /tmp/ ln -s ../git_hooks/ hooks (I used the latest version of commit-msg from gerrit) It would be nice to add an equivalent of indent for Java. Sylvestre From clement.david at scilab.org Tue Jun 14 10:12:49 2011 From: clement.david at scilab.org (=?ISO-8859-1?Q?Cl=E9ment?= David) Date: Tue, 14 Jun 2011 10:12:49 +0200 Subject: [Scilab-Dev] Idea for XCOS improvement In-Reply-To: <4DF33CDE.8040003@email.it> References: <4DF33CDE.8040003@email.it> Message-ID: <1308039170.2249.6.camel@pinarellu.inria.fr> Hi, Thanks for the suggestion but it's available. On a SuperBlock diagram, the labels of I/O blocks (with Format->Edit...->Text) are translated to ports on the corresponding SuperBlock. -- Cl?ment Le samedi 11 juin 2011 ? 12:01 +0200, xwang1976 at email.it a ?crit : > Hi to all, > I'm a Simulink/Matlab user and I would like to use XCOS as an open > source alternative. > The most important thing that keep me from using it is the lack of the > possibility to name superblocks inputs and outputs port as it is > possible to do in Simulink and Matrixx. > This feature is very useful IMHO when the simulated model begins to grow > because it clarifies the IO interfaces of the blocks which constitute > the model and permit to use a top-down approach with nested superblocks. > Is there any plan to implements such a feature? > Thank you, > Xwang -- Cl?ment David From fedebergero at gmail.com Tue Jun 14 15:14:49 2011 From: fedebergero at gmail.com (Federico Bergero) Date: Tue, 14 Jun 2011 10:14:49 -0300 Subject: Deploying a Scilab module Message-ID: Hi, I wrote a atoms module (http://forge.scilab.org/index.php/p/BackDoor/) . How can I distribute it through different machines/OS??? Should I distribute it as a source and have a script to compile it and install it? If I distribute binary version, will this work with different OS? For example if I compile it on an amd_64 machine, will it work on i386? Thanks Fede -- I find television very educational. Every time someone switches it on, I go into another room and read a good book. From allan.cornet at scilab.org Tue Jun 14 15:48:46 2011 From: allan.cornet at scilab.org (Allan CORNET) Date: Tue, 14 Jun 2011 15:48:46 +0200 Subject: [Scilab-Dev] Deploying a Scilab module In-Reply-To: References: Message-ID: <007001cc2a99$c84db340$58e919c0$@scilab.org> Hi, You created a ATOMS web page http://atoms.scilab.org/toolboxes/BackDoor and upload sources (it seems to be only a template in current state) We build for supported architectures for you and you will receive a build log for each platform. And you we will do in scilab: atomsSystemUpdate() atomsInstall("BackDoor") Currently, C source in BackDoor-0.1-1-src.zip will not build on Windows since your template is empty for windows part Allan -----Message d'origine----- De?: Federico Bergero [mailto:fedebergero at gmail.com] Envoy??: mardi 14 juin 2011 15:15 ??: dev Objet?: [Scilab-Dev] Deploying a Scilab module Hi, I wrote a atoms module (http://forge.scilab.org/index.php/p/BackDoor/) . How can I distribute it through different machines/OS??? Should I distribute it as a source and have a script to compile it and install it? If I distribute binary version, will this work with different OS? For example if I compile it on an amd_64 machine, will it work on i386? Thanks Fede -- I find television very educational. Every time someone switches it on, I go into another room and read a good book. From paul.cazottes at gadz.org Tue Jun 14 20:02:19 2011 From: paul.cazottes at gadz.org (Paul Cazottes) Date: Tue, 14 Jun 2011 20:02:19 +0200 Subject: Fwd: Allan variance Message-ID: <201106142002.20310.paul.cazottes@gadz.org> Hello, I would like to make a Allan varian script. This tool was first designed for time reference, and is becoming a de-facto standard to show the performance of inertial sensors (accelerometers and gyrometers). We now can find scripts for Matlab as contribution, but I was not able to find it for scilab. I made one and would like to bring it to scilab, with full help etc etc. Is it possible for scilab devs to explain me: - how to make an optionnal argument in the syntax? Presently I would like to have a syntax as AllanM(X,st,Npoints) where Npoints is optionnal and defaults to 100. - write a help file? I didn't find an official tutorial in scilab.org - parallelize? The for loop is fully parallelizable. The Allan variance is simple to calculate yet CPU intensive on large sets. Maybe parrallelization is more for Scilab 6? I would greatly appreciate helt on these points. Thanks for scilab devs to bring this product to everybody! Paul Cazottes - paul.cazottes at gadz.org -------------- next part -------------- A non-text attachment was scrubbed... Name: Moulinette_Variance_d_Allan-module.sci Type: text/x-csrc Size: 4328 bytes Desc: not available URL: From sylvestre.ledru at scilab.org Tue Jun 21 18:11:34 2011 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Tue, 21 Jun 2011 18:11:34 +0200 Subject: [Scilab-Dev] Fwd: Allan variance In-Reply-To: <201106142002.20310.paul.cazottes@gadz.org> References: <201106142002.20310.paul.cazottes@gadz.org> Message-ID: <1308672694.10944.59.camel@losinj.inria.fr> Le mardi 14 juin 2011 ? 20:02 +0200, Paul Cazottes a ?crit : > Hello, > > I would like to make a Allan varian script. This tool was first designed for > time reference, and is becoming a de-facto standard to show the performance of > inertial sensors (accelerometers and gyrometers). > > We now can find scripts for Matlab as contribution, but I was not able to find > it for scilab. I made one and would like to bring it to scilab, with full help > etc etc. Thanks! > Is it possible for scilab devs to explain me: > - how to make an optionnal argument in the syntax? Presently I would like to > have a syntax as AllanM(X,st,Npoints) where Npoints is optionnal and defaults > to 100. See argn: http://help.scilab.org/docs/5.3.2/en_US/argn.html Example: function AllanM(X,st,Npoints) if argn(2) == 2 then Npoints = 2 end endfunction > - write a help file? I didn't find an official tutorial in scilab.org We are using docbook for the help. You will find a module example in contrib/toolbox_skeleton you will find some help page examples in it. > - parallelize? The for loop is fully parallelizable. The Allan variance is > simple to calculate yet CPU intensive on large sets. Maybe parrallelization is > more for Scilab 6? See parallel_run http://help.scilab.org/docs/5.3.2/en_US/parallel_run.html but it does not work under Windows. > I would greatly appreciate helt on these points. Thanks for scilab devs to > bring this product to everybody! Thanks! Sylvestre From sylvestre.ledru at scilab.org Tue Jun 21 18:12:53 2011 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Tue, 21 Jun 2011 18:12:53 +0200 Subject: [Scilab-Dev] SciLab 5.3.2 / XCOS In-Reply-To: References: Message-ID: <1308672773.10944.60.camel@losinj.inria.fr> Hello, Le vendredi 20 mai 2011 ? 10:27 +0200, Bernhard Kunkel a ?crit : > Hello developers of this wonderful software, > > working with XCOS ThermoHydraulics it would be nice to have a > "Flowmeter" like in ScicosLab 4.4.1. > > Is that possible or planed in future ? > I don't know if it is planned but could you report a bug with a severity as "wishlist" ? http://bugzilla.scilab.org/ Thanks, Sylvestre From fedebergero at gmail.com Tue Jun 21 20:07:25 2011 From: fedebergero at gmail.com (Federico Bergero) Date: Tue, 21 Jun 2011 15:07:25 -0300 Subject: [Scilab-Dev] Deploying a Scilab module In-Reply-To: <007001cc2a99$c84db340$58e919c0$@scilab.org> References: <007001cc2a99$c84db340$58e919c0$@scilab.org> Message-ID: That's true. I tried to compile it on Windows but Scilab ask for MSVC. I don't have Visual Studio, can I use MINGW? Thanks Fede 2011/6/14 Allan CORNET : > Hi, > > You created a ATOMS web page http://atoms.scilab.org/toolboxes/BackDoor and > upload sources (it seems to be only a template in current state) > > We build for supported architectures for you and you will receive a build > log for each platform. > > And you we will do in scilab: > > atomsSystemUpdate() > atomsInstall("BackDoor") > > Currently, C source in BackDoor-0.1-1-src.zip ?will not build on Windows > since your template is empty for windows part > > Allan > > -----Message d'origine----- > De?: Federico Bergero [mailto:fedebergero at gmail.com] > Envoy??: mardi 14 juin 2011 15:15 > ??: dev > Objet?: [Scilab-Dev] Deploying a Scilab module > > Hi, I wrote a atoms module (http://forge.scilab.org/index.php/p/BackDoor/) . > How can I distribute it through different machines/OS??? > Should I distribute it as a source and have a script to compile it and > install it? > If I distribute binary version, will this work with different OS? For > example if I compile it on an amd_64 machine, will it work on i386? > > Thanks > Fede > > -- > I find television very educational. Every time someone switches it on, I go > into another room and read a good book. > > -- I find television very educational. Every time someone switches it on, I go into another room and read a good book. From allan.cornet at scilab.org Tue Jun 21 20:14:36 2011 From: allan.cornet at scilab.org (allan.cornet at scilab.org) Date: Tue, 21 Jun 2011 20:14:36 +0200 Subject: [Scilab-Dev] Deploying a Scilab module In-Reply-To: References: <007001cc2a99$c84db340$58e919c0$@scilab.org> Message-ID: Hi, If you want to be packaged in ATOMS on Windows, your code must be compatible with MSVC compiler To check you can use Visual studio 2010 C++ express http://www.microsoft.com/visualstudio/en-us/products/2010-editions/visual-cpp-express Allan On Tue, 21 Jun 2011 15:07:25 -0300, Federico Bergero wrote: > That's true. > I tried to compile it on Windows but Scilab ask for MSVC. > I don't have Visual Studio, can I use MINGW? > Thanks > Fede > > 2011/6/14 Allan CORNET : >> Hi, >> >> You created a ATOMS web page >> http://atoms.scilab.org/toolboxes/BackDoor and >> upload sources (it seems to be only a template in current state) >> >> We build for supported architectures for you and you will receive a >> build >> log for each platform. >> >> And you we will do in scilab: >> >> atomsSystemUpdate() >> atomsInstall("BackDoor") >> >> Currently, C source in BackDoor-0.1-1-src.zip ?will not build on >> Windows >> since your template is empty for windows part >> >> Allan >> >> -----Message d'origine----- >> De?: Federico Bergero [mailto:fedebergero at gmail.com] >> Envoy??: mardi 14 juin 2011 15:15 >> ??: dev >> Objet?: [Scilab-Dev] Deploying a Scilab module >> >> Hi, I wrote a atoms module >> (http://forge.scilab.org/index.php/p/BackDoor/) . >> How can I distribute it through different machines/OS??? >> Should I distribute it as a source and have a script to compile it >> and >> install it? >> If I distribute binary version, will this work with different OS? >> For >> example if I compile it on an amd_64 machine, will it work on i386? >> >> Thanks >> Fede >> >> -- >> I find television very educational. Every time someone switches it >> on, I go >> into another room and read a good book. >> >> From fedebergero at gmail.com Tue Jun 21 20:17:00 2011 From: fedebergero at gmail.com (Federico Bergero) Date: Tue, 21 Jun 2011 15:17:00 -0300 Subject: [Scilab-Dev] Deploying a Scilab module In-Reply-To: References: <007001cc2a99$c84db340$58e919c0$@scilab.org> Message-ID: Great. Thanks I will write the windows version. Best Fede 2011/6/21 : > > Hi, > > If you want to be packaged in ATOMS on Windows, your code must be compatible > with MSVC compiler > > To check you can use Visual studio 2010 C++ express > > http://www.microsoft.com/visualstudio/en-us/products/2010-editions/visual-cpp-express > > > Allan > > > On Tue, 21 Jun 2011 15:07:25 -0300, Federico Bergero > wrote: >> >> That's true. >> I tried to compile it on Windows but Scilab ask for MSVC. >> I don't have Visual Studio, can I use MINGW? >> Thanks >> Fede >> >> 2011/6/14 Allan CORNET : >>> >>> Hi, >>> >>> You created a ATOMS web page http://atoms.scilab.org/toolboxes/BackDoor >>> and >>> upload sources (it seems to be only a template in current state) >>> >>> We build for supported architectures for you and you will receive a build >>> log for each platform. >>> >>> And you we will do in scilab: >>> >>> atomsSystemUpdate() >>> atomsInstall("BackDoor") >>> >>> Currently, C source in BackDoor-0.1-1-src.zip ?will not build on Windows >>> since your template is empty for windows part >>> >>> Allan >>> >>> -----Message d'origine----- >>> De?: Federico Bergero [mailto:fedebergero at gmail.com] >>> Envoy??: mardi 14 juin 2011 15:15 >>> ??: dev >>> Objet?: [Scilab-Dev] Deploying a Scilab module >>> >>> Hi, I wrote a atoms module >>> (http://forge.scilab.org/index.php/p/BackDoor/) . >>> How can I distribute it through different machines/OS??? >>> Should I distribute it as a source and have a script to compile it and >>> install it? >>> If I distribute binary version, will this work with different OS? For >>> example if I compile it on an amd_64 machine, will it work on i386? >>> >>> Thanks >>> Fede >>> >>> -- >>> I find television very educational. Every time someone switches it on, I >>> go >>> into another room and read a good book. >>> >>> > > -- I find television very educational. Every time someone switches it on, I go into another room and read a good book. From communication at scilab.org Wed Jun 22 17:02:33 2011 From: communication at scilab.org (Scilab Communication) Date: Wed, 22 Jun 2011 17:02:33 +0200 Subject: D-7 - Registrate to the 3rd edition of Scilab Users Day, Wednesday 29 June 2011 Message-ID: <4E020409.7010703@scilab.org> *It is still time to registrate to ScilabTEC 2011* It is on wednesday 29 June at the ?cole Polytechnique, Palaiseau (91). Open invitation, online registration required: http://www.teratec.eu/gb/forum/inscription.php *With the participation of ArcelorMittal, Sirehna and Valeo.* Complete program: http://www.scilab.org/news/events/20110502 ScilabTEC2011 ---------------------------------- The Scilab Consortium http://www.scilab.org ---------------------------------- Digiteo Domaine de Voluceau Rocquencourt - B.P. 105 78153 Le Chesnay Cedex - France -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 75938 bytes Desc: not available URL: From fedebergero at gmail.com Fri Jun 24 22:03:24 2011 From: fedebergero at gmail.com (Federico Bergero) Date: Fri, 24 Jun 2011 17:03:24 -0300 Subject: [Scilab-Dev] Deploying a Scilab module In-Reply-To: References: <007001cc2a99$c84db340$58e919c0$@scilab.org> Message-ID: Hi, I'm writting the version for Windows but I find some differences. In my module I create a new thread listening to commands through a TCP port. In the linux version I call SendScilabJob from that "other" thread and it runs the job on the Scilab enviroment. On windows, when I call SendScilabJob it does nothing. For example if I run SendScilabJob("a=1") on Linux a variable a with the value 1 is created. On Windows that doesn?t work. I tried using the api_scilab but I don?t find any function to just run a job (I can read/write variables). Does anybody what?s going on here? Thanks Fed 2011/6/21 Federico Bergero : > Great. Thanks > I will write the windows version. > Best > Fede > > 2011/6/21 ?: >> >> Hi, >> >> If you want to be packaged in ATOMS on Windows, your code must be compatible >> with MSVC compiler >> >> To check you can use Visual studio 2010 C++ express >> >> http://www.microsoft.com/visualstudio/en-us/products/2010-editions/visual-cpp-express >> >> >> Allan >> >> >> On Tue, 21 Jun 2011 15:07:25 -0300, Federico Bergero >> wrote: >>> >>> That's true. >>> I tried to compile it on Windows but Scilab ask for MSVC. >>> I don't have Visual Studio, can I use MINGW? >>> Thanks >>> Fede >>> >>> 2011/6/14 Allan CORNET : >>>> >>>> Hi, >>>> >>>> You created a ATOMS web page http://atoms.scilab.org/toolboxes/BackDoor >>>> and >>>> upload sources (it seems to be only a template in current state) >>>> >>>> We build for supported architectures for you and you will receive a build >>>> log for each platform. >>>> >>>> And you we will do in scilab: >>>> >>>> atomsSystemUpdate() >>>> atomsInstall("BackDoor") >>>> >>>> Currently, C source in BackDoor-0.1-1-src.zip ?will not build on Windows >>>> since your template is empty for windows part >>>> >>>> Allan >>>> >>>> -----Message d'origine----- >>>> De?: Federico Bergero [mailto:fedebergero at gmail.com] >>>> Envoy??: mardi 14 juin 2011 15:15 >>>> ??: dev >>>> Objet?: [Scilab-Dev] Deploying a Scilab module >>>> >>>> Hi, I wrote a atoms module >>>> (http://forge.scilab.org/index.php/p/BackDoor/) . >>>> How can I distribute it through different machines/OS??? >>>> Should I distribute it as a source and have a script to compile it and >>>> install it? >>>> If I distribute binary version, will this work with different OS? For >>>> example if I compile it on an amd_64 machine, will it work on i386? >>>> >>>> Thanks >>>> Fede >>>> >>>> -- >>>> I find television very educational. Every time someone switches it on, I >>>> go >>>> into another room and read a good book. >>>> >>>> >> >> > > > > -- > I find television very educational. Every time someone switches it on, > I go into another room and read a good book. > -- I find television very educational. Every time someone switches it on, I go into another room and read a good book. From sylvestre.ledru at scilab.org Wed Jun 29 16:46:58 2011 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Wed, 29 Jun 2011 16:46:58 +0200 Subject: SEP 67: lines(0) default Message-ID: <1309358819.3567.7.camel@losinj.inria.fr> Hello, Here is a proposal for Scilab 5.4.0. To sum up, we would like to have lines being to set to 0 by default in Scilab. To make sure we can go back to the previous behavior, we add a new argument to lines: lines(-1) As usual, don't hesitate to comment. Sylvestre -------------- next part -------------- A non-text attachment was scrubbed... Name: SEP_067_lines_default_value.odt Type: application/vnd.oasis.opendocument.text Size: 20627 bytes Desc: not available URL: From Serge.Steer at inria.fr Thu Jun 30 10:22:40 2011 From: Serge.Steer at inria.fr (Serge Steer) Date: Thu, 30 Jun 2011 10:22:40 +0200 Subject: [Scilab-Dev] SEP 67: lines(0) default In-Reply-To: <1309358819.3567.7.camel@losinj.inria.fr> References: <1309358819.3567.7.camel@losinj.inria.fr> Message-ID: <4E0C3250.2000607@inria.fr> Le 29/06/2011 16:46, Sylvestre Ledru a ?crit : > Hello, > > Here is a proposal for Scilab 5.4.0. > To sum up, we would like to have lines being to set to 0 by default in > Scilab. > To make sure we can go back to the previous behavior, we add a new > argument to lines: lines(-1) > > As usual, don't hesitate to comment. > Sylvestre > > > I do not agree to disable the line control by default, many times I was obliged to kill a Scilab session because after I have disabled the line control I mistakely asked for the display of a huge matrix. In such case the display can take several minutes.... But it should be a good idea to have a default value for the number of lines larger than the number of lines currently visible in the console. (let say about 3 or 4 pages) Serge From sylvestre.ledru at scilab.org Thu Jun 30 10:47:27 2011 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Thu, 30 Jun 2011 10:47:27 +0200 Subject: [Scilab-Dev] SEP 67: lines(0) default In-Reply-To: <4E0C3250.2000607@inria.fr> References: <1309358819.3567.7.camel@losinj.inria.fr> <4E0C3250.2000607@inria.fr> Message-ID: <1309423648.2995.45.camel@losinj.inria.fr> Le jeudi 30 juin 2011 ? 10:22 +0200, Serge Steer a ?crit : > Le 29/06/2011 16:46, Sylvestre Ledru a ?crit : > > Hello, > > > > Here is a proposal for Scilab 5.4.0. > > To sum up, we would like to have lines being to set to 0 by default in > > Scilab. > > To make sure we can go back to the previous behavior, we add a new > > argument to lines: lines(-1) > > > > As usual, don't hesitate to comment. > > Sylvestre > > > > > > > I do not agree to disable the line control by default, many times I was > obliged to kill a Scilab session because after I have disabled the line > control I mistakely asked for the display of a huge matrix. In such > case the display can take several minutes.... > > > > But it should be a good idea to have a default value for the number of > lines larger than the number of lines currently visible in the console. > (let say about 3 or 4 pages) In the last few releases of the 5.3.X family, console performances have dramatically improved. It is less an issue than it used to be... However, I understand your point. While 3 or 4 pages seems a bit small, we could consider a bigger value here (10 or 20)... and this value could be configured in the future Scilab Preferences. Sylvestre From Serge.Steer at inria.fr Thu Jun 30 12:04:20 2011 From: Serge.Steer at inria.fr (Serge Steer) Date: Thu, 30 Jun 2011 12:04:20 +0200 Subject: [Scilab-Dev] SEP 67: lines(0) default In-Reply-To: <1309423648.2995.45.camel@losinj.inria.fr> References: <1309358819.3567.7.camel@losinj.inria.fr> <4E0C3250.2000607@inria.fr> <1309423648.2995.45.camel@losinj.inria.fr> Message-ID: <4E0C4A24.7030909@inria.fr> Le 30/06/2011 10:47, Sylvestre Ledru a ?crit : > Le jeudi 30 juin 2011 ? 10:22 +0200, Serge Steer a ?crit : > >> Le 29/06/2011 16:46, Sylvestre Ledru a ?crit : >> >>> Hello, >>> >>> Here is a proposal for Scilab 5.4.0. >>> To sum up, we would like to have lines being to set to 0 by default in >>> Scilab. >>> To make sure we can go back to the previous behavior, we add a new >>> argument to lines: lines(-1) >>> >>> As usual, don't hesitate to comment. >>> Sylvestre >>> >>> >>> >>> >> I do not agree to disable the line control by default, many times I was >> obliged to kill a Scilab session because after I have disabled the line >> control I mistakely asked for the display of a huge matrix. In such >> case the display can take several minutes.... >> >> >> >> But it should be a good idea to have a default value for the number of >> lines larger than the number of lines currently visible in the console. >> (let say about 3 or 4 pages) >> > In the last few releases of the 5.3.X family, console performances have > dramatically improved. It is less an issue than it used to be... > You are right, I just tested it. Good! > However, I understand your point. While 3 or 4 pages seems a bit small, > we could consider a bigger value here (10 or 20)... and this value could > be configured in the future Scilab Preferences. > > Ok! Serge From prateekbatla at gmail.com Thu Jun 30 17:07:35 2011 From: prateekbatla at gmail.com (Prateek Batla) Date: Thu, 30 Jun 2011 15:07:35 +0000 (UTC) Subject: [Scilab-Dev] Scilab 5.2.0 is released ! References: <4B29EE12.7050808@scilab.org> Message-ID: Pierre MARECHAL writes: > > > Hello, > > The Scilab Team is pleased to announce the release of Scilab 5.2.0. > > Misc information about this version: > http://www.scilab.org/download/ > What's new ? > See the 5.2.0 RELEASE_NOTES > file > See the 5.2.0 CHANGES file [5.1.1 ? 5.2.0] > See the changes since the beta release [5.2.0-beta-1 ? > 5.2.0] > > > Pierre > Hello sir, I am in use for this tool and unfortunately had find bugs in this. It was really difficult to get a post where i can reply you. Kindly please help me use this tool and let me know if i can discuus the errors with you. Regards Prateek Batla