BIRT Exchange Forum: Calendar control , HTML DOM, Viewer Size issues. - BIRT Exchange Forum

Jump to content


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Calendar control , HTML DOM, Viewer Size issues. Rate Topic: -----

#1 User is offline   kukkri 

  • Member
  • PipPipPip
  • Group: Members
  • Posts: 31
  • Joined: 30-September 09

Posted 16 October 2009 - 11:49 AM

Hi Brian,
As per our discussion, the calendar control was erroring out when I select the previous or next or cancel buttons inside the QuickStart JSAPI tab. The reason for it was the basetag was set to a pre-determined value...and I needed to set iFrame = true in my navitem references to the JSAPI tab.

However, with the iFrame the viewer cut off the report with a scroll bar i.e the report viewer window was small. Changing the width and height values in setheight and setwidth did not help when the iframe = true.
It works when iFrame was not set.

Please advise.
0

#2 User is offline   bhanley 

  • Senior Member
  • View blog
  • Group: Members
  • Posts: 558
  • Joined: 26-October 07

Posted 22 October 2009 - 05:25 AM

Can you post the HTML page containing the JSAPI code so we can review it? You can simply paste the markup into the thread or attach the file itself to the thread.
0

#3 User is offline   kukkri 

  • Member
  • PipPipPip
  • Group: Members
  • Posts: 31
  • Joined: 30-September 09

Posted 25 October 2009 - 01:08 PM


<html>



Mashup








<body onload="acload()">










QA Report Selector


Report:













0

#4 User is offline   bhanley 

  • Senior Member
  • View blog
  • Group: Members
  • Posts: 558
  • Joined: 26-October 07

Posted 26 October 2009 - 05:11 AM

I do not see in your Javascript where you are actually loading the report. Is that happening in popup.html? I can follow the flow of the code through the instantiation of the parameter component, but then you invoke the pop-up and I an not seeing the completion. I am assuming that the final step is coded in popup.html.

If you can add the code in popup.html that should help me finish working this through.

Thanks!
0

#5 User is offline   kukkri 

  • Member
  • PipPipPip
  • Group: Members
  • Posts: 31
  • Joined: 30-September 09

Posted 26 October 2009 - 11:40 AM

Here you go:


<html>



<body onload="acload()">








<body>
<html>
0

#6 User is offline   bhanley 

  • Senior Member
  • View blog
  • Group: Members
  • Posts: 558
  • Joined: 26-October 07

Posted 26 October 2009 - 02:08 PM

I am running these pages without any problem. Do you have fixed dimensions on the components in your BIRT report that could be limiting the screen real estate available to render into?

I pointed these two pages at the JSAPI samples bundled into the standard iServer install and it worked like a champ. The working samples were ONLY changed to point to the content. All the other code running is the same as your installation. This leads me to believe the problem may well be in the BIRT designs themselves.
0

#7 User is offline   kukkri 

  • Member
  • PipPipPip
  • Group: Members
  • Posts: 31
  • Joined: 30-September 09

Posted 27 October 2009 - 09:34 AM

attached couple of my sample reports....not sure where the issue is.

Attached File(s)


0

#8 User is offline   bhanley 

  • Senior Member
  • View blog
  • Group: Members
  • Posts: 558
  • Joined: 26-October 07

Posted 28 October 2009 - 09:06 AM

I took a look at the QA_SWAndRef... report. You have a lot of fixed dimensions in this report (Some as large as 13 inches). That is not ideal for the web as the dimensions you are rendering into (Such as the Pop Up window you are trying to use) can vary widely. Have you tried leveraging BIRT's auto-layout functionality by coding in relative widths through percentages? It may help BIRT deal with the available space when you request the content via JSAPI.
0

#9 User is offline   kukkri 

  • Member
  • PipPipPip
  • Group: Members
  • Posts: 31
  • Joined: 30-September 09

Posted 29 October 2009 - 08:16 AM

I see....I will use that method and set the iFrame = true. That should help me correct?
0

#10 User is offline   kukkri 

  • Member
  • PipPipPip
  • Group: Members
  • Posts: 31
  • Joined: 30-September 09

Posted 29 October 2009 - 01:03 PM

Hi Brian,
I went back and looked at the report...and it is set to Auto Layout by default.

No matter I change it to percentage....it returns back to inches. I tried changing the table width to % but it returned back to inches...so also with the columns.

Please advise.
0

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users