I suggest you ...

Have "beans" exporting text

It would be great to have new types of beans that can render text instead of images.

3 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Dupy Fabien shared this idea  ·   ·  Admin →

    4 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Dupy Fabien commented  · 

        Hi John,

        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&quot; />" 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 !

      • AdminJohn Goering (Admin, i-net software) commented  · 

        Thanks for clarifying!

        Dupy, it seems like what you want in this first idea is already possible. You can load an image from the internet using a formula field. Simply use the formula

        bytesFromFile("http://yourserver.com/yourfile.png")

        Regarding your second idea...the bean's properties are currently settable via Designer, since the report designer is able to add, modify or even remove beans in the report. The designer is itself using the API... we don't quite understand this second idea. Why would you not want external bean properties to be visible to the person designing the report?

      • 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.

      • AdminJohn Goering (Admin, i-net software) commented  · 

        Thanks for the idea, Dupy.

        Can you give us a quick example of what you mean? You are already able to use any bean whatsoever in your reports, including ones that render text into the bean area. What type of beans are you referring to? Thanks in advance...

      Feedback and Knowledge Base