[Scilab-users] Toolboxes startup

[Stéphane Mottelet]

Hello again,

Le 26/04/2021 à 12:38, Samuel Gougeon a écrit :
> Hello,
>
> Le 26/04/2021 à 09:41, Stéphane Mottelet a écrit :
>>
>> Hi all,
>>
>> I just made available for macOS and Linux the toolboxes stixbox 
>> depends upon for macOS (distfun and linalg) and my remark is that 
>> when a lot of modules are loaded at startup then the output can 
>> become very long and sometimes messy, since we don't impose a 
>> normalized output:
>>
>> *Scilab branch-6.1 (Apr 19 2021, 23:19:29)**
>> *
>>
>> *Start Distfun**
>> **
>> **Start Helptbx**
>> **
>> **Start Specfun**
>> **
>> **Start Makematrix**
>> **
>> **Start Apifun**
>> **    Load macros**
>> **    Type "help apifun_overview" for a quick start.**
>> **
>> **Start Linalg**
>> **
>> **Start Stixbox*
>>
>> I would rather expect something like:
>>
>>
>> *Scilab branch-6.1 (Apr 19 2021, 23:19:29)**
>> *
>>
>> *Start modules: Distfun, Helptbx, Specfun, Makematrix, Apifun, 
>> Linalg, Stixbox.*
>>
>> *--> *
>>
>> The verbosity level of the output (with the above default) could be 
>> defined in user preferences, and checked in module startup script in 
>> order to output the required amount of information.
>>
>> That's just a propostion to be discussed, of course.
>>
>
> Such a wish was reported 10 years ago as bug 6801 
> <https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/bugzilla.scilab.org/show_bug.cgi?id=6801>.
>
> To me, the only way to overcome any mprintf or disp made in *.start 
> files of external modules would be to become able to redirect the 
> standard output to null (or anywhere else as in a file, as with diary, 
> that forks the stream instead of redirecting it).
> I don't think that %toolboxes aims to become public. 
> atomsGetInstalled() and atomsGetLoaded() (and others) would likely be 
> more suited to test the atoms status.
>
> For contribution,
> Samuel

Yeah that's the idea. But better than redirection of the standard 
output, all the stuff displayed in the .start file should go in a 
Journal, to which display methods can be associated. So instead of 
explicitely calling disp or mprinf, etc. the .start script should just 
add some stuff + associated verbosity level to the journal. What would 
be actually really displayed will depend on the level of the used 
Journal. That's the way the output is controlled in Ipopt, for example 
(but at the C++ level).

S.


>
>
> _______________________________________________
> users mailing list
> users at lists.scilab.org
> https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users

-- 
Stéphane Mottelet
Ingénieur de recherche
EA 4297 Transformations Intégrées de la Matière Renouvelable
Département Génie des Procédés Industriels
Sorbonne Universités - Université de Technologie de Compiègne
CS 60319, 60203 Compiègne cedex
Tel : +33(0)344234688
http://www.utc.fr/~mottelet

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/users/attachments/20210426/ffc8f984/attachment.htm>