Copy constructors

[Tom Schindl]

So why are you not using the instance methods? BTW do you know about my
SVG to FXML converter [1]?

It is not based on XSLT but there are many many hard things to tackle
with XSLT (e.g. if the SVG contains an image) which are solved by it and
I agree with Greg why do you process the SVG inside your application
instead of running the conversion at build time.

Anyways a deep copy of an Node-Graph is something that has to be
provided by JavaAPI itself, its IMHO nothing the FXML tool has to deal with.

Tom

[1]http://tomsondev.bestsolution.at/2012/08/22/svg-to-fxml-converter-as-commandline-util/

Am 10.09.12 19:47, schrieb Scott Palmer:
> 
> On 2012-09-10, at 1:28 PM, Greg Brown <greg.x.brown at oracle.com> wrote:
> 
>>
>> Why not just partition the template contents into a separate FXML file and re-load it each time you need a new instance?
>>
> 
> 
> This brings up a question that I recently was pondering…
> The FXML loader only takes a URL. If you have a resource that you may load multiple times, how efficient is it?  I have used a XSLT to convert SVG into FXML so I can get scalable icons in my application.  There are two concern:
> 
> 1) If I choose to convert from SVG to FXML at runtime I need to make a temporary file for the FXML loader as it doesn't take a DOM or a String as a source.
> 2) The exact same component hierarchy is being parsed over and over (these icons may appear many many times in the GUI) - It might make sense for there to be an intermediate form that new copies of the FXML node hierarchy could be created from. 
> 
> Regards,
> 
> Scott
> 


-- 
B e s t S o l u t i o n . a t                        EDV Systemhaus GmbH
------------------------------------------------------------------------
tom schindl                 geschäftsführer/CEO
------------------------------------------------------------------------
eduard-bodem-gasse 5-7/1   A-6020 innsbruck     fax      ++43 512 935833
http://www.BestSolution.at                      phone    ++43 512 935834