3 votesDupy Fabien commented
thanks for the tips !
if I use directly bytesFromFile, I will have the image embedded directly into the document. Sometimes I just want to have this kind of html tag generated:
"<img src="http://yourserver.com/yourfile.png" />" and to be sure that Crystal Clear is not going to acess this url (for resilience questions), because the document generated (html) will be sent by email, therefore the resolve of the image can be done on client side.
About the hidden properties of the beans, I use them to give a context for the bean rendering an url:
If I have 2 resource servers (where I store my images) for test and production purpose, and I have exactly the same resources on both, but the domain name is not the same. If I want to change the domain of the url at formatting time (to be able to run the same layout on my 2 environments) and not to force the people who design layouts to use a datbase field to know the environment, my formatting server can goes through the layout and set the context property (isTestServer = true;).
Hope that will clarify !Dupy Fabien commented
The idea behing that is to be able to generate html directly from a bean (in order to have an image that is hosted anyware on internet and not relative to the folder where the document is generated).
The second idea is to be able to define hidden attributes on that bean (to have particular behavior), they are not visible into the designer, but we can modify them while browsing the Engine object.Dupy Fabien shared this idea ·