RE: o.c.swt.widgets: ...

["Chen, Xihui" <chenx1@ornl.gov>]

Hi,

Thanks Andrew for your nice words! But I should also thanks Zen for his harsh criticism because it pushes me to dig the code deeper and finally improved BOY again.

Hi Zen, After two days of full time debugging, I finally found and fixed the bug which will queue the image drawing requests up when the PV updating frequency increased. This bug will not result in memory leak, but it will result in several unnecessary copies of data residing in memory. Now you should not see the OutofMemory error even if you decrease the maximum Java Virtual Machine memory size to 256M. It should have no problem in displaying your 4MB camera image at 7Hz. But we will still leave the Byte2Long conversion there because it doesn't influence the use of BOY at SNS and the current PV layer will probably be replaced by Gabriele's PV Manager in future. 

For the latest build of CSS, you may get it from here https://irmis-dev.bnl.gov/hudson/view/CSS/ . It is an automatically build whenever there is a change in the source repository. But it seems doesn't work on my machine. You can still have a try though. Otherwise, you either need to build your own CSS from sourceforge repository or wait for our next release.

Thanks,
Xihui




-----Original Message-----
From: Andrew Johnson [mailto:anj@aps.anl.gov] 
Sent: Monday, September 20, 2010 1:29 PM
To: Szalata, Zenon M.
Cc: tech-talk@aps.anl.gov
Subject: Re: o.c.swt.widgets: ...

Hi Zen,

I can understand your frustration that CSS/BOY doesn't meet your requirements, 
but for a tool that is only 14 months old (the first commit was on July 21, 
2009) I think Xihui and Kay have done an amazing job and I thank them for 
contributing this code to the EPICS collaboration.  Berating the author(s) of 
a Free/Open Source project is rarely productive, and remember that's Free as 
in libre, not necessarily gratis.

We are all constrained by limited budgets and management priorities, maybe you 
could help out by starting to write some of the documentation for newcomers 
that you feel is missing as you work out how to check out and build BOY.  As 
Kay just said it is a standard CSS/Eclipse plugin whose source code is in the 
Mercurial repository on SourceForge with the rest of CSS.  The CSS Wiki would 
be an ideal location for that kind of documentation.

- Andrew
-- 
The best FOSS code is written to be read by other humans -- Harald Welte