Re: [Scaffoldhunter-devel] 2014 Getting closer to system

[<nl...@us...>]

Hi Andrew,

the bug you have mentioned is a tough one. I would like to propose one of 
these.

There are two feature requests related to creating subsets. Both should be 
easy to solve:
https://sourceforge.net/p/scaffoldhunter/feature-requests/23/
https://sourceforge.net/p/scaffoldhunter/feature-requests/38/

This one should also be doable:
https://sourceforge.net/p/scaffoldhunter/feature-requests/41/

This is more challenging and also related to your proposal:
https://sourceforge.net/p/scaffoldhunter/feature-requests/39/

To export the canvas as SVG or PNG we use Batik. Batik provides an 
implementation of Graphics2D that creates an SVG. Instead of painting the 
Piccolo2D scene graph to screen you can pass Batiks Graphics2D object to the 
Piccolo framework and obtain an SVG. However, thinks are a bit more difficult, 
e.g, you have to specify the area you actually want to export. Have a look at 
edu.udo.scaffoldhunter.view.util.SVGGenerator and see how it is used by the 
scaffold tree view. There is a lot of code dedicated to this task, e.g., to 
disable semantic zooming for the export etc. Best start with a basic version 
of the export and then adjust it. Feel free to ask questions on the mailing 
list.

Regards,
  Nils





On Wednesday 26 March 2014 11:02:03 Anjenson wrote:
> Hi everyone,
> 
> I have been looking for some bugs to fix and get to know the system
> better and I came across this one.
> <http://ehc.ac/p/scaffoldhunter/bug-reports/37/>
> So, I would propose to create a singleton wrapper around SVGCache that
> would store caches with different maxSize. And if needed some of them
> may be shared.
> At first, I wanted to propose to make SVGCache a singleton but then
> noticed that instances may have different maxSize.
> 
> I also will appreciate if you could point me to some good-first bug I
> could work on.
> 
> Regards,
> Andrew