You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(15) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(1) |
Feb
(11) |
Mar
(18) |
Apr
(1) |
May
(10) |
Jun
(5) |
Jul
(7) |
Aug
(5) |
Sep
(12) |
Oct
(2) |
Nov
|
Dec
(13) |
| 2004 |
Jan
(13) |
Feb
(46) |
Mar
(20) |
Apr
(10) |
May
(13) |
Jun
(8) |
Jul
(5) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(47) |
Aug
(14) |
Sep
(7) |
Oct
(1) |
Nov
|
Dec
|
| 2006 |
Jan
(11) |
Feb
(17) |
Mar
(5) |
Apr
(9) |
May
(1) |
Jun
|
Jul
(5) |
Aug
(4) |
Sep
(1) |
Oct
|
Nov
(1) |
Dec
(1) |
| 2007 |
Jan
(5) |
Feb
(2) |
Mar
|
Apr
(1) |
May
|
Jun
(2) |
Jul
(18) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
(3) |
Mar
(8) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(6) |
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(2) |
Oct
(4) |
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
(2) |
Mar
(4) |
Apr
|
May
|
Jun
(4) |
Jul
(1) |
Aug
(2) |
Sep
|
Oct
(1) |
Nov
(3) |
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|
From: Ricardo F. <rf...@if...> - 2004-04-03 04:52:37
|
Hi, Animal 0.10.6 is out. I've fixed the configure script to correctly detect the latest Gandalf 1.3.2 on many systems. Download it at: http://animal.sf.net The problem was very obscure and not easy to solve. It happens that some NVIDIA OpenGL libraries (and maybe some others) has some badly undefined symbols that made it impossible to link some OpenGL programs, in particular Gandalf (which uses OpenGL). The fix was very hard to find, but it all should be OK now. Please report immediately to this list any errors you have while compiling Animal and SIP. best, Ricardo. -- Ricardo Fabbri, Cybernetic Vision Research Group, USP, Brazil. TEL: +15 (16) 273.9882 ICQ: 208974212 "With pain and suddenness is how Real Offsprings are born. But they must result from intense pleasure and a long period of development." |
|
From: Ricardo F. <rf...@if...> - 2004-03-24 19:55:44
|
On Wed, 24 Mar 2004, Vitor Vasconcelos Araujo Silva wrote: > Ricardo, > > I'm sure that is not the better solution but: can you send me the files > (xml, dtd, xls)? This way I can help you with the files and later I can > worry about my SIP install. I'm so busy here the few times I remain in > front of my computer... Hi, Vitor, these files are inside the "man" directory of the latest SIP-devel tree: sip-dev-20040320/man/*.xml // new files but with incomplete information sip-dev-20040320/man/*.man // old files but with complete information sip-dev-20040320/man/mansip.dtd sip-dev-20040320/man/html-sip.xsl just to recall: the task is basically to compare the new XML with the old MAN files and include any missing information in the XML. thx, Ricardo. -- Ricardo Fabbri, Cybernetic Vision Research Group, USP, Brazil. WEB: cyvision.if.sc.usp.br/~rfabbri ICQ: 208974212 "With pain and suddeness is how Real Offsprings are born. But they must result from intense pleasure and a long period of development." |
|
From: Vitor V. A. S. <vi...@cn...> - 2004-03-24 13:09:19
|
Ricardo, I'm sure that is not the better solution but: can you send me the files (xml, dtd, xls)? This way I can help you with the files and later I can worry about my SIP install. I'm so busy here the few times I remain in front of my computer... Cheers, Vitor |
|
From: Vitor V. A. S. <vi...@cn...> - 2004-03-23 19:54:35
|
> Vitor, I can help you to compile it under Linux. You can contact me by > ICQ: 208974212 and I will probably be able to give you instant help. Thanks. I had no problems before, so, I think is possible to do it without spend your time. But thanks a lot. I'll contact you if I need. > I finished my part already and I am trying to port SIP for Windows > now. Great ideia. I want to finish mine soon. > > Everybody is short in time, I know. > anyway, thanks for your help, > Ricardo. It's a pleasure. I prefer to do it than many of my "obligations". But I'm finishing the credits in the M.Sc, so I'm busy with projects that not intests me a lot... But I want to get involved most and most with SIP. Thanks, Vitor |
|
From: Ricardo F. <rf...@if...> - 2004-03-23 19:05:36
|
On Tue, 23 Mar 2004, Vitor Vasconcelos Araujo Silva wrote: > Hello Ricardo, > > I experienced problemns yesterday to install SIP. My other version was > the binary and when I tried to perform 'make' few erros ocurred. I had > not much time to work on it, but I hope get some time today or tomorrow > to try to install again and (hope not) report detailed erros if then > keep ocuring. Vitor, I can help you to compile it under Linux. You can contact me by ICQ: 208974212 and I will probably be able to give you instant help. I finished my part already and I am trying to port SIP for Windows now. Everybody is short in time, I know. anyway, thanks for your help, Ricardo. -- Ricardo Fabbri, Cybernetic Vision Research Group, USP, Brazil. WEB: cyvision.if.sc.usp.br/~rfabbri ICQ: 208974212 "With pain and suddeness is how Real Offsprings are born. But they must result from intense pleasure and a long period of development." |
|
From: Vitor V. A. S. <vi...@cn...> - 2004-03-23 11:30:50
|
Hello Ricardo, I experienced problemns yesterday to install SIP. My other version was the binary and when I tried to perform 'make' few erros ocurred. I had not much time to work on it, but I hope get some time today or tomorrow to try to install again and (hope not) report detailed erros if then keep ocuring. Thanks and count with me to help with the files. Cheers, Vitor |
|
From: Ricardo F. <rf...@if...> - 2004-03-21 04:00:19
|
Oh, If anybody else can help us, you are welcome to work on these unassigned functions (but please tell us the ones youre interested to avoid duplicate work): sip_fftshift.xml curvature2d.xml curvature.xml unfollow.xml xgetpixel.xml xor.xml erode.xml thanks for any help, Ricardo. On Sun, 21 Mar 2004, Ricardo Fabbri wrote: > The most complex XML files are mogrify.xml and imwrite.xml, which you > should take as MODELS for editing the other XML files. I ask that you > guys help me revise the rest of the XML files. I suggest the work be > assigned as bellow: > > Here's what we have to do (it's not much): > > - take the files that I finished as a model on how to write good > quality help pages. > - match the XMLs to corresp. .man's to see if everything is included > - Split the PARAMETERS section into INPUT/OUTPUT parameter sections, > whenever both exist (see mogrify.xml for an example on this) > - in the description section, when we have something of the form: > <P> > imwrite(Img, filename) creates an image filename in disk, from > Img matrix. For truecolor images, Img is a MxNx3 hypermatrix, > so for example Img(:,:,1) stands for the red channel. For binary > images or intensity grayscale images, Img is a MxNx1 matrix. > </P> > <P> > imwrite(Index, Map, filename) does the same work, but from Index > (MxN) and Map (Mx3) matrices. Grayscale and Paletted images are > written in this way. > </P> > > That is, a commands folowed by their description, we should change to > this: > > <DESCRIPTION_INDENT> > <DESCRIPTION_ITEM label="imwrite(Img, filename)"> > creates an image filename in disk, from > Img matrix. For truecolor images, Img is a MxNx3 hypermatrix, > so for example Img(:,:,1) stands for the red channel. For binary > images or intensity grayscale images, Img is a MxNx1 matrix. > </DESCRIPTION_ITEM> > <DESCRIPTION_ITEM label="imwrite(Index, Map, filename)"> > does the same work, but from Index (MxN) and Map (Mx3) > matrices. Grayscale and Paletted images are written in this way. > </DESCRIPTION_ITEM> > </DESCRIPTION_INDENT> > > (if anybody can write a script to automate this, we'll be glad) > > - function names, variables, and other programming elements should > be between <TT> </TT> tags. > - when you finish your review of the XML file, please send it to me. > - any doubts: email. > > HINTS: > - type "make" to generate the HTML file from XML under Unix systems > - its faster to use an ordinary browser to view the resulting .htm > file while you're writing it, without calling scilab. > > If anybody can/wants to do it all, just tell us. > OTOH, no problem if you don't have the time to finish or even do any > of your part; just drop an email to this list so we can reassign the > task. Don't worry about the time, do what you can in your own pace. > > I'll be working on other toolbox tasks after I finish my part. > thank you all, > > PS: you can now reach me by ICQ: 208974212 almost all day long. > Ricardo. |
|
From: Ricardo F. <rf...@if...> - 2004-03-21 03:52:21
|
Hi, all, Download the new development version (20040320) at: http://siptoolbox.sf.net/devel In this version, all the files are already using new sections, such as "Availability", and many more. We now use our own XSL and DTD files. The problem of linking to external Scilab functions was solved by requiring the HTML pages to be built in the user's machine, which is the best solution I could find. Futurely, the binary version will either require the user to have XSLTPROC command in his machine, or else we will have to make some processing to the HTML files using SED to replace the links to correct locations in the user's machine. I have done most improvements to all XML files using some scripting utilities (SED, etc). However, there is still important work to be done which I couldn't automate. The only XML files that are complete and finished are: drawline.xml, gray_imread.xml, imread.xml, imshow.xml, mogrify.xml, and imwrite.xml There still remains about 50 files to be revised. For this task, I included the old ".man" files in the new devel distro so you can help me match their content to the corresp XML files, if you have the time. The most complex XML files are mogrify.xml and imwrite.xml, which you should take as MODELS for editing the other XML files. I ask that you guys help me revise the rest of the XML files. I suggest the work be assigned as bellow: RICARDO bwdist.xml skel.xml thin.xml watershed.xml minmax.xml VITOR angle.xml bwborder.xml bwlabel.xml dilate.xml edge.xml edilate.xml hello_sip.xml hough.xml ihough.xml im2bw.xml im2gray.xml imconv.xml JOCELYN imcorrcoef.xml unwrapl.xml unwrapp.xml imphase.xml improfile.xml imroi.xml imvariance.xml interferometry_gui.xml pifilter.xml poledetection.xml sip_colormap.xml mkfftfilter.xml LINCHPIN normal.xml ntsc2rgb.xml percol.xml perim.xml rgb2ntsc.xml sip_fftshift.xml curvature2d.xml curvature.xml unfollow.xml xgetpixel.xml xor.xml erode.xml Here's what we have to do (it's not much): - take the files that I finished as a model on how to write good quality help pages. - match the XMLs to corresp. .man's to see if everything is included - Split the PARAMETERS section into INPUT/OUTPUT parameter sections, whenever both exist (see mogrify.xml for an example on this) - in the description section, when we have something of the form: <P> imwrite(Img, filename) creates an image filename in disk, from Img matrix. For truecolor images, Img is a MxNx3 hypermatrix, so for example Img(:,:,1) stands for the red channel. For binary images or intensity grayscale images, Img is a MxNx1 matrix. </P> <P> imwrite(Index, Map, filename) does the same work, but from Index (MxN) and Map (Mx3) matrices. Grayscale and Paletted images are written in this way. </P> That is, a commands folowed by their description, we should change to this: <DESCRIPTION_INDENT> <DESCRIPTION_ITEM label="imwrite(Img, filename)"> creates an image filename in disk, from Img matrix. For truecolor images, Img is a MxNx3 hypermatrix, so for example Img(:,:,1) stands for the red channel. For binary images or intensity grayscale images, Img is a MxNx1 matrix. </DESCRIPTION_ITEM> <DESCRIPTION_ITEM label="imwrite(Index, Map, filename)"> does the same work, but from Index (MxN) and Map (Mx3) matrices. Grayscale and Paletted images are written in this way. </DESCRIPTION_ITEM> </DESCRIPTION_INDENT> (if anybody can write a script to automate this, we'll be glad) - function names, variables, and other programming elements should be between <TT> </TT> tags. - when you finish your review of the XML file, please send it to me. - any doubts: email. HINTS: - type "make" to generate the HTML file from XML under Unix systems - its faster to use an ordinary browser to view the resulting .htm file while you're writing it, without calling scilab. If anybody can/wants to do it all, just tell us. OTOH, no problem if you don't have the time to finish or even do any of your part; just drop an email to this list so we can reassign the task. Don't worry about the time, do what you can in your own pace. I'll be working on other toolbox tasks after I finish my part. thank you all, PS: you can now reach me by ICQ: 208974212 almost all day long. Ricardo. -- Ricardo Fabbri, Cybernetic Vision Research Group, USP, Brazil. WEB: cyvision.if.sc.usp.br/~rfabbri ICQ: 208974212 "With pain and suddeness is how Real Offsprings are born. But they must result from intense pleasure and a long period of development." |
|
From: Ricardo F. <rf...@if...> - 2004-03-19 21:19:51
|
> > Here is the result of my tests: > 1) Trying to load the brand new sip in scilab, I got: > add_help_chapter(libtitle,SIPDIR+'man'); > !--error 4 > undefined variable : add_help_chapter > yeah, this is a new CVS function, I didn't realize. > 2) I tested the hyperlinks: inside SIP, it's allright. > But, I looked at sip_fftshift, then clicked on the fft link. > couldn't open Important pblm. I'm trying to solve it. Probably the html files will have to be built in the user's machine so the links gets resolved. I'm affraid this will not be a robust solution, at least for the binary version. > 3) I saw a help page for sip_colormap, but no macro for it. > The interferometry_gui.dem is a bit outdated. I sent a better version to the > list (which uses the new colormaps). Sorry, I've updated now for the next release. thx. > I'm happy of the implication of Vitor too. Yes, without his contribution, SIP's XML help wouldn't be real. Ricardo. -- Ricardo Fabbri, Cybernetic Vision Research Group, USP, Brazil. WEB: cyvision.if.sc.usp.br/~rfabbri ICQ: 208974212 "With pain and suddeness is how Real Offsprings are born. But they must result from intense pleasure and a long period of development." |
|
From: Ricardo F. <rf...@if...> - 2004-03-19 21:11:46
|
Hi, Vitor! On Thu, 18 Mar 2004, Vitor Vasconcelos Araujo Silva wrote: > If you want, I can write a little manual to explain "where to put what" > to help developers to generate they help files. Sure, but wait until I release our final XSL and DTD's. You could write this in "sip_help.xml" (suggestion) > > > - we propose these XSL and DTD to Scilab group, but we continue to > > use/maintain our own versions of these. xmltohtml enables us to specify > > our own XSL. > > Good. But what it means in fact? These new files could be part of > Scilab distribution and changes in xmltohtml would be made too? Yes, but changes to xmltohtml are not necessary (at least until now). > > Excelent job. If you need any specific help, feel free to contact me > directly. I have no so much time, but would be glad to help you. Ok, Thanks! Ricardo. -- Ricardo Fabbri, Cybernetic Vision Research Group, USP, Brazil. WEB: cyvision.if.sc.usp.br/~rfabbri ICQ: 208974212 "With pain and suddeness is how Real Offsprings are born. But they must result from intense pleasure and a long period of development." |
|
From: DRUEL J. <joc...@li...> - 2004-03-19 17:36:02
|
Hi, Le Lundi 15 Mars 2004 05:09, vous avez écrit : > Hi, all, > > a new development release is out, with help files now in XML format, > in spite of some problems with not-yet-supported help sections, such > as REMARKS and others. > > Download the new version at: > http://siptoolbox.sf.net/devel > Here is the result of my tests: 1) Trying to load the brand new sip in scilab, I got: add_help_chapter(libtitle,SIPDIR+'man'); !--error 4 undefined variable : add_help_chapter So I changed the line in loader.sce to use the %helps syntax. It worked fine. The help pages are now beautiful ! Good work ! 2) I tested the hyperlinks: inside SIP, it's allright. But, I looked at sip_fftshift, then clicked on the fft link. Here is the error: couldn't open "/home/jo/softs/scilab-2.7/contrib/sip/man/../../../../../../usr/lib/scilab-2.7/man/eng/signal/fft.htm": no such file or directory If scilab is not installed in the usual place (/usr/lib) then it causes a problem. 3) I saw a help page for sip_colormap, but no macro for it. The interferometry_gui.dem is a bit outdated. I sent a better version to the list (which uses the new colormaps). Sorry, I had no time to have a better look at the colorbars these days. I'm happy of the implication of Vitor too. Best regards Jocelyn -- Powered by Linux |
|
From: Vitor V. A. S. <vi...@cn...> - 2004-03-18 12:16:29
|
> First, I'll try to accommodate some inexistent manual sections under > DESCRIPTION_ITEM tags. Other sections will be treated like this: > > - we'll use/distribute our own XSL and DTD to translate and define new > tags. I suggest generic SECTION and SUBSECTION tags, and the name of > the section as a sub-tag NAME of these. Hello Ricardo, I think these are "clean" solutions. The additional problem is to generate and maintaing our own XSL and DTD, but, made it, I think the problems of "different" tags are solved. If you want, I can write a little manual to explain "where to put what" to help developers to generate they help files. > - we propose these XSL and DTD to Scilab group, but we continue to > use/maintain our own versions of these. xmltohtml enables us to specify > our own XSL. Good. But what it means in fact? These new files could be part of Scilab distribution and changes in xmltohtml would be made too? > I'm just saying that we could have used formatman to translate our old > man to xml just like you did in PERL, but this doesn't matter anymore. Ok. Right. > Now I'm sure. Here's an excerpt from http://www.w3schools.com/xml/xml_cdata.asp: > "Everything inside a CDATA section is ignored by the parser. > If your text contains a lot of "<" or "&" characters - as program > code often does - the XML element can be defined as a CDATA section." > > So invalid characters in code examples inside CDATA don't need to be escaped. Thanks. > This will certainly be fixed by patching "xmltohtml.sci". > > So most problems seems to be solved in theory now, > I'll be implementing the solution tomorrow. > Any comments are welcome. Excelent job. If you need any specific help, feel free to contact me directly. I have no so much time, but would be glad to help you. Greetings, Vitor vi...@cn... |
|
From: Ricardo F. <rf...@if...> - 2004-03-18 00:14:25
|
Hi, still working on XML help, I've made some progress today, after learning more about this technology. First, I'll try to accommodate some inexistent manual sections under DESCRIPTION_ITEM tags. Other sections will be treated like this: - we'll use/distribute our own XSL and DTD to translate and define new tags. I suggest generic SECTION and SUBSECTION tags, and the name of the section as a sub-tag NAME of these. - we propose these XSL and DTD to Scilab group, but we continue to use/maintain our own versions of these. xmltohtml enables us to specify our own XSL. On Mon, 15 Mar 2004, Vitor Vasconcelos Araujo Silva wrote: > > translates old .man help pages into xml, just as your script does, > > but I don't know if it works. Anyway, this is not of much use now, > > since you already translated them. > > I only took I look, but I thank that would be easist to work to put the > xml tags and not the .man format. The lack of information to generate > the .man tags is even worst to generate xml tags. I'm just saying that we could have used formatman to translate our old man to xml just like you did in PERL, but this doesn't matter anymore. > > - In the EXAMPLE section, we don't need to escape invalid characters, > > I guess. CDATA is not parsed by XML. Now I'm sure. Here's an excerpt from http://www.w3schools.com/xml/xml_cdata.asp: "Everything inside a CDATA section is ignored by the parser. If your text contains a lot of "<" or "&" characters - as program code often does - the XML element can be defined as a CDATA section." So invalid characters in code examples inside CDATA don't need to be escaped. > > - In SEE_ALSO, comments to links are ignored. For instance: > > > > <SEE_ALSO_ITEM> <LINK>mogrify</LINK>(-segment option) </SEE_ALSO_ITEM> > > > > The "(-segment option)" string is plainly ignored by xmltohtml, even > > though the DTD file allows #PCDATA to be part of SEE_ALSO_ITEM. This will certainly be fixed by patching "xmltohtml.sci". So most problems seems to be solved in theory now, I'll be implementing the solution tomorrow. Any comments are welcome. Ricardo. -- Ricardo Fabbri, Cybernetic Vision Research Group, USP, Brazil. WEB: cyvision.if.sc.usp.br/~rfabbri ICQ: 208974212 "With pain and suddeness is how Real Offsprings are born. But they must result from intense pleasure and a long period of development." |
|
From: Vitor V. A. S. <vi...@cn...> - 2004-03-15 12:48:41
|
> Hi, Vitor and other SIP developers, Hello people, > I'm finished with an initial build and installation framework for the > new XML help files. A development version with XML help files will be > announced just right after this email. It would be good if somebody > could test this version on a unix box. Ok. > I didn't have an easy time with XML help, because there are many > details that Scilab is still not getting right. Some remarks about this: > > - The main error is that some tags are ignored by xmltohtml, or, > worst, aren't even available in the Scilab help DTD.. I'm now trying to > solve this, please send me any suggestions. The ignored tags are > REMARKS (present in DTD but ignored by xmltohtml) > BUGS AND SHORTCOMINGS > AVAILABILITY > KNOWN PROBLEMS > FILE FORMATS > ARGV FILES > IMAGE SEGMENTATION > Without these tags we can't even switch to XML definitely, so this is > a relatively serious problem. Yes, I think it's a seriously problem. My first ideia when I faced this problem was modify the man pages to "acommodate" the missing instructions under the functional tags. An example is the mogrify function, probabily one of the most powerfull and very dependent of tags with problem. To answer your question, I really don't see another solution. > - The LINK command should be used, not ALINK. ALINK does not work. Thank you. I didn't checked it correctly. > - Vitor, did you check out the Scilab "formatman" command? It > translates old .man help pages into xml, just as your script does, > but I don't know if it works. Anyway, this is not of much use now, > since you already translated them. I only took I look, but I thank that would be easist to work to put the xml tags and not the .man format. The lack of information to generate the .man tags is even worst to generate xml tags. > - In the EXAMPLE section, we don't need to escape invalid characters, > I guess. CDATA is not parsed by XML. I'm not sure about that. The only problem I had was with the ">" and "<" caracters, but concerning to the perl script. > - In SEE_ALSO, comments to links are ignored. For instance: > > <SEE_ALSO_ITEM> <LINK>mogrify</LINK>(-segment option) </SEE_ALSO_ITEM> > > The "(-segment option)" string is plainly ignored by xmltohtml, even > though the DTD file allows #PCDATA to be part of SEE_ALSO_ITEM. > > Scilab's TCL/TK browser also has some limitations: > - contents page has undesirable blank lines, because the browser > is not displaying <dd> tags nicely > - there are some strange vertical bars around examples Yes, I've noted this bars and really don't know waht they're doing there. > Anybody is welcome to comment and help us on those issues, > specially those with XML/DTD knowledge. > > > Best regards, > Ricardo. Ricardo, I'm available. What do you think about "change" the files the not behave properly with the crazy dtd? Would be nice hear the SCILAB developers opinion. Wish to help you in any decicision. Best regards and keep in touch, Vitor Vasconcelos M.Sc Student COPPE/UFRJ Computer Graphics and Image Processing Group www.lcg.ufrj.br |
|
From: Ricardo F. <rf...@if...> - 2004-03-15 04:11:05
|
Hi, all, a new development release is out, with help files now in XML format, in spite of some problems with not-yet-supported help sections, such as REMARKS and others. Download the new version at: http://siptoolbox.sf.net/devel Compilation and installation is suited for Linux, but should work correctly in other unix systems. I use Slackware Linux 9.1, but please report to the list any problems that you find with SIP in other distros. You shall install the new SIP version over the older ones without problems, but if you want, you can remove the old version like this: in the unix shell, change dir to the old SIP-dev then type the following: prompt# make uninstall best, Ricardo. -- Ricardo Fabbri, Cybernetic Vision Research Group, USP, Brazil. WEB: cyvision.if.sc.usp.br/~rfabbri ICQ: 208974212 "With pain and suddeness is how Real Offsprings are born. But they must result from intense pleasure and a long period of development." |
|
From: Ricardo F. <rf...@if...> - 2004-03-15 02:53:03
|
Hi, Vitor and other SIP developers,
I'm finished with an initial build and installation framework for the
new XML help files. A development version with XML help files will be
announced just right after this email. It would be good if somebody
could test this version on a unix box.
I didn't have an easy time with XML help, because there are many
details that Scilab is still not getting right. Some remarks about this:
- The main error is that some tags are ignored by xmltohtml, or,
worst, aren't even available in the Scilab help DTD.. I'm now trying to
solve this, please send me any suggestions. The ignored tags are
REMARKS (present in DTD but ignored by xmltohtml)
BUGS AND SHORTCOMINGS
AVAILABILITY
KNOWN PROBLEMS
FILE FORMATS
ARGV FILES
IMAGE SEGMENTATION
Without these tags we can't even switch to XML definitely, so this is
a relatively serious problem.
- The LINK command should be used, not ALINK. ALINK does not work.
- Vitor, did you check out the Scilab "formatman" command? It
translates old .man help pages into xml, just as your script does,
but I don't know if it works. Anyway, this is not of much use now,
since you already translated them.
- In the EXAMPLE section, we don't need to escape invalid characters,
I guess. CDATA is not parsed by XML.
- In SEE_ALSO, comments to links are ignored. For instance:
<SEE_ALSO_ITEM> <LINK>mogrify</LINK>(-segment option) </SEE_ALSO_ITEM>
The "(-segment option)" string is plainly ignored by xmltohtml, even
though the DTD file allows #PCDATA to be part of SEE_ALSO_ITEM.
Scilab's TCL/TK browser also has some limitations:
- contents page has undesirable blank lines, because the browser
is not displaying <dd> tags nicely
- there are some strange vertical bars around examples
Anybody is welcome to comment and help us on those issues,
specially those with XML/DTD knowledge.
Best regards,
Ricardo.
--
Ricardo Fabbri, Cybernetic Vision Research Group, USP, Brazil.
WEB: cyvision.if.sc.usp.br/~rfabbri ICQ: 208974212
"With pain and suddeness is how Real Offsprings are born. But they
must result from intense pleasure and a long period of development."
|
|
From: DRUEL J. <joc...@li...> - 2004-03-12 13:47:28
|
Le Mercredi 3 Mars 2004 21:07, vous avez écrit : > Hi, Jocelyn, > > your function sip_colormap has just been included in my sip-dev tree. > I decided to keep the name. I was also thinking about accepting a > string as the first argument, in addition to the integer one. This > would be easy to do and allows the user to remember the colormap > without effort. Good idea. I send you an improved version. Best regards Jocelyn -- Powered by Linux |
|
From: Ricardo F. <rf...@if...> - 2004-03-10 22:38:19
|
Hi, The harddisk of our server had been busted since last week. We fixed it and the SIP homepage was recovered. Everything should be back to normal. best, Ricardo. -- Ricardo Fabbri, Cybernetic Vision Research Group, USP, Brazil. WEB: cyvision.if.sc.usp.br/~rfabbri ICQ: 208974212 |
|
From: Ricardo F. <rf...@if...> - 2004-03-10 02:00:05
|
Hi, all, the SIP home page is out due to a problem with our server. Technicians are currently taking care of this. Until then, please download SIP from the Sourceforge project page: http://sourceforge.net/projects/siptoolbox Ricardo. -- Ricardo Fabbri, Cybernetic Vision Research Group, USP, Brazil. WEB: cyvision.if.sc.usp.br/~rfabbri ICQ: 208974212 |
|
From: Ricardo F. <rf...@if...> - 2004-03-03 21:38:44
|
Hi, all, I'd like to introduce you to Linchpin (aka Anuj Sharma), our new contributor. He's a grad Electrical Eng and have worked on GA's & ANN's, and with multi spectral satellite image classification. Linchpin, lets get started. In this project, coding is rather independent. Basically, you pick a function you want to see in SIP, code it, write a manual page, and send it to this list. Other kind of activity is porting and documentation. Here are specifics I suggest you start with: - Is there any method, classification system, or application you have already implemented that would be of general interest? You could code them into SIP. Start with simple ones to learn how the SIP code is organized. - About documentation, we are in need for more demos. To get started with SIP, you could write a demo, be it a text demo, be it visual and interactive (harder). You could write a demo on a cool application you know/worked with/want to learn. If you want to do other (more ambitious) stuff, try this: - You could code some recognition system such as PCR/eigenfaces, antifaces, or some other you want. - An OCR system. It could be simple. I suggest that you try to integrate functionality available in other free software: http://jOCR.sourceforge.net/ - Always try reuse or incorporate functions from other toolboxes, whenever they don't suck... Please take a look at the following toolboxes to see what could be useful to you: Neural nets toolbox ftp://ftp.inria.fr/INRIA/Scilab/contrib/ANN/ ENRICO graphics toolbx ftp://ftp.inria.fr/INRIA/Scilab/contrib/ENRICO/ EVOL (genetic alg. toolbox)ftp://ftp.inria.fr/INRIA/Scilab/contrib/EVOL/ - We need to port SIP 0.3.1 from Linux to, yuck, Windowz. This is an important but tedious task and one developer already gave up on it. If you feel youre tough enough for this, SIP will be greatly rewarded and this could be a usage boom, as Windowz has so many users thirsty for a new SIP :) Too many choices on what to do can be daunting, but there are no bosses here; you do whatever you want. looking forward to see some results, regards, Ricardo. -- Ricardo Fabbri, Cybernetic Vision Research Group, USP, Brazil. WEB: cyvision.if.sc.usp.br/~rfabbri ICQ: 208974212 "With pain and suddeness is how Real Offsprings are born. But they must result from intense pleasure and a long period of development." |
|
From: Ricardo F. <rf...@if...> - 2004-03-03 20:22:12
|
Hi, Jocelyn, your function sip_colormap has just been included in my sip-dev tree. I decided to keep the name. I was also thinking about accepting a string as the first argument, in addition to the integer one. This would be easy to do and allows the user to remember the colormap without effort. Meanhwile, I'm finishing including/revising/improving Vitor's XML contrib and rewriting the manpage build system to support the new scheme. About Bruno Pincon, could you please you contact him and include his functions into SIP? best, Ricardo. On Wed, 18 Feb 2004, DRUEL Jocelyn wrote: > Hi, > > > > > thanks for the new colormaps. I will be seeing it during the next few days > > and I will also compare its interface to the equivalent in Matlab. > > > > kind regards, > > Ricardo. > > As I looked for colormaps in Scilab, I found that Bruno Pincon already worked > on this subject: > At his homepage: > http://www.iecn.u-nancy.fr/~pincon/scilab/scilab.html > > there are 2 tools: > 1) a colorbar.sci function to display a colormap on the right of an image (it > integrates without problem with the imshow function: example: > map=sip_colormap(i);xbasc();colorbar(0,1);imshow(a,map); > > It's a cool feature. > > 2) a more sophisticated package that allows interactive modification of a > colormap. > (I think that's what Ricardo means by > "Color transform curves GUI" in the Todo list.) > > Maybe Bruno Pincon would be interested to integrate these tools in SIP to > allow: > 1) a better SIP package > 2) a wider use of his code > > I can contact him (or maybe Ricardo knows him already). > > Best regards > Jocelyn |
|
From: DRUEL J. <joc...@li...> - 2004-02-20 09:07:54
|
Hi,
Still working on my GUI, I integrated the possibility to view images in false
colors (by changing the colormap).
Even if the sip_colormap function changes in syntax, it won't be difficult to
adapt, because all I need is a function that returns a 256 levels colormap.
I also tried to take advantage of the xset("pixmap",1).
I also rearranged menus in a more logical (I hope) way.
It's still far from perfect, but is a usefull tool for me.
Something else:
I wondered if it was possible to create submenus: for example, in the
Operation menu, I'd like to create an item Filtering, which would open a
submenu with gaussian filter, etc...
It could lighten the GUI.
I could not find it, so if you know...
Best regards
Jocelyn
--
Powered by Linux |
|
From: Ricardo F. <rf...@if...> - 2004-02-19 12:36:10
|
Hi, I saw your nice presentation. Thanks. In the future, if you have problems with server space, you may use Sourceforge.net. They offer illimited storage for projects, for free. Just tell me whenever you need it. best, Ricardo. On Thu, 19 Feb 2004, DRUEL Jocelyn wrote: > Hi, > I intend to present SIP to colleagues of other "BTS genie optique" centers. > One of my friends will first present Scilab. > > So, I inspired from Ricardo's presentation for the general presentation and > added some examples to convince my public that SIP is simple and powerful. > > Sorry, it's in french (but with many images). > The site is still: > http://genie-optique.chez.tiscali.fr/SIP > > It's a StarOffice presentation, but you can also browse it online. > |
|
From: DRUEL J. <joc...@li...> - 2004-02-19 09:59:02
|
Hi, I intend to present SIP to colleagues of other "BTS genie optique" centers. One of my friends will first present Scilab. So, I inspired from Ricardo's presentation for the general presentation and added some examples to convince my public that SIP is simple and powerful. Sorry, it's in french (but with many images). The site is still: http://genie-optique.chez.tiscali.fr/SIP It's a StarOffice presentation, but you can also browse it online. best regards Jocelyn -- Powered by Linux |
|
From: Ricardo F. <rf...@if...> - 2004-02-19 01:51:11
|
On Thu, 19 Feb 2004, DRUEL Jocelyn wrote: > Hi, > > > > > Bruno Pincon's colormap stuff seem to be really neat. > > > > My only restrictions to their inclusion into SIP is that the final > > functions be as similar to M4t1Ab as possible, in case there exists an > > equivalent in that software. > > Aren't you afraid that one day, M4t1Ab says SIP plagiarize their software ? Not at all ;) Simply because it doesn't plagiarize. It is just my opinion that SIP should try to keep some compatibility with other well known software. (read bellow) > I remember a very nasty story about a software called Krayon in Suse that > caused Suse to be prevented from selling its boxes in Germany: > > http://news.com.com/2100-1001-803724.html?legacy=cnet Interesting. > > Personaly, I think giving same names and syntaxes as M4t1Ab will cause > problems (although it's easier for users to migrate) if SIP becomes more > popular. This year, I had a sale representative of Mathworks on the phone for > my school. He was not quite happy of the existence of Scilab. That makes /me/ quite happy :) > Common points are natural, but SIP is not a (cheap) clone of the M4t1Ab Image > Processing toolbox. I consider it as a complementary tool, or as another tool > which allows image manipulation. > You are right, SIP is really not a mtlb image toolbox clone. I'm just suggesting that, whenever possible, we keep compatibility. Here is what I suppose is reasonable about this, please tell me if you agree: Whenever we invent an interface to a function that is clearly better than the interface of the corresp. function in mtlb, I think we should use our new interface and forget about the matlab interface. However, I think we should always improve, never do inferior function interfaces. If you have a different function interface that is clearly worst than the corresp. in mtlb, we should use something at least similar to the better one. On the other hand, if you have a function interface that is better than mtlb, then, sure, lets use it, since what we want here is not a clone, but a good software package above all. If a function interface is different from mtlb, and we are not sure if it is better or not, then we should discuss it or merely use the one that users are more familiar with. I'm not doing anything wrong, but I confess I'm taking a slight risk here. You always risk yourself whenever you get in the way of big companies, even if you are right under law. I am pretty sure that most of the interface issues cannot be copyrighted nor be intelectual property in any ways. Except for some countries, of course, but I'm not afraid of that. I'm willing to to the best for an image processing software that we're crafting, and this does not means cloning some other tool that, we all know, is not perfect. cheers, Ricardo. -- Ricardo Fabbri, Cybernetic Vision Research Group, USP, Brazil. WEB: cyvision.if.sc.usp.br/~rfabbri ICQ: 208974212 |
