Re: [iText-questions] HTMLWorker image handling improvements
(PauloSoares)
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits.
I'll keep the properties map instead of the get/setImageProvider to avoid
the proliferation of get/set methods.
Paulo
- Original Message -
From: "robert engels" <[EMAIL PROTECTED]>
To:
Sent: Saturday, May 26, 2007 6:51 PM
Subject: Re: [iText-questions] HTML
Having the ImageProvider interface allows for easy custom protocol
handling, and simple embedded image processing.
The code below is what we are doing in our custom 1.4.8 derivation.
Adding get/setImageProvider to HTMLWorker would be a better solution
than using the properties map.
In this w
: "Post all your questions about iText here"
Sent: Saturday, May 26, 2007 11:05 AM
Subject: Re: [iText-questions] HTMLWorker image handling improvements
> robert engels wrote:
>> In general you should NEVER use concrete classes
>> when the interface suffices.
>
> Th
robert engels wrote:
> In general you should NEVER use concrete classes
> when the interface suffices.
That's true, and we sin against this rule on many
places in iText. For the moment I uploaded the HashMap/Map
change. If I have the time to have a closer look at HTMLWorker
(also related to the T
Using HTMLWorker and dynamically providing images is a bit
cumbersome. Dynamic images are important when reducing maximum memory
uses, and having a catalog of available images for the user to select.
Currently, you need to do something similar to:
class MyImageProvider extends HashMap {
