Bug 111011 - Need better indication of script errors
Summary: Need better indication of script errors
Status: ASSIGNED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: 1.0.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: Future   Edit
Assignee: Wenbin He CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-28 19:39 EDT by Don French CLA
Modified: 2006-12-25 00:56 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Don French CLA 2005-09-28 19:39:14 EDT 
The only indication that there was an error in a script appears at the end of a 
report.  This is very easy to miss. There needs to be a very obvious error 
indication, whether it be a pop-up window or a red flag somewhere that you 
don't need to scroll to the bottom of the report to see.
Comment 1 Stanley Wang CLA 2005-12-27 19:42:37 EST 
Investigate whether engine can throw an exception for viewer to catch at the end of the rendering, and put up some gesture through Ui to signify the error.
Comment 2 Wenfeng Li CLA 2006-03-06 16:50:22 EST 
Need further investigation on wha tis the right user experience is for different scenrios: view report as static HTML, command line generation of HTML, and web viewer.
Comment 3 Wei Yan CLA 2006-12-25 00:56:27 EST 
1. MODEL provides the line no of the script in the source design file.
2. ENGINE execute the script using report element id, event name, line no.
3. ENGINE add a ErrorHandler call back
4. VIEWER provides the ErrorHandler and add the error to the Eclipse's problem viewer.
5. When user click the problem viewer, DESIGNER jumps to the error line in the source editor or script editor.