Community
Participate
Working Groups
It is somewhat difficult for a new BIRT user to figure out how to build an aggregate without reading the help or looking at examples. It's even more difficult to build an advanced aggregate (those that take advantage of filtering and non-default groupin. The issues are: (1) Aggregates are buried under BIRT functions/Total object in Expression builder. A novice may not be able to immediately locate this when he needs an aggregate. (2) The filter and group parameters are difficult to figure out without help. We should consider adding an aggregate builder to the Expression Builder. Some usability study is needed to figure out the exact UI, but I suggest the following guidelines: * Expression builder should list Aggregates as a top level construct (alongside operators/functions/data sets etc) rather than listing them under functions. * When an aggregate is selected, the builder should have a dialog to help the user construct the various arguments to the aggregate function, including (1) picking a column (or build an expression) to aggregate on; (2) Pick a group from a list of available groups; (3) build a filter expression
schedule to RC0 to list Aggregates as a top level construct and creating a mock up for the rest of enhancements.
Created attachment 37134 [details] Move the Total from BIRT functions to main Category aggregates In Expression Builder, Birt Functions, Move the 'Total' and its expressions to a new category called 'Aggregates'(see mockup).
aggregate builder is being discussed. Most likely future milestone will have the implementation.
Please take care of this changes when implment data binding.
please see the attached mock up.
As comments #3, we already changed the thing in the mockup. The further research need to be done by GUI designer.
Synch up with Callisto schedule to rename RC1 as RC2 targeted 5/5/2006.
For the the UI part i have been thinking of the following. --------------------------------------------------------- - Add a new item in palette "Σ" under a new category - When user drags and drops the item from palette to the table layout view, show the new aggregation builder - Note the aggregateOn property is decided based on which area the user drops the aggregation function like table header/footter, group header/footer - THe new aggregation builder allows user to specify the name, functiona name, data type etc for the aggregation. - At the end of this UI operation, a new data item with a corresponding data binding column is created. Reassigning to Aashima for the UI mockups.
- One clarification add symbol Σ ( signma) to indicate its aggregation. - I have asked Bang to use the same idea for cross tab too, it is still under discussion.
Created attachment 65431 [details] aggregation builder UI
Created attachment 66741 [details] Updated UI on aggregation builder
Created attachment 66784 [details] revised with minor changes
GUI couldn't get the argment list for a purticular function name. Currently Model does not have any information of those function definitions.
Dateset aggregation builder is not same as column binding aggregation builder.
Please can you clarify which page number in the latest mockup attached are you talking about. It should be the same.
Fixed
Please refer to the mockup attached by Aashima in comment #12, The UI is not implemented as mocked up I am reopening the bug, as this the UI is not consistent witht he mockup.
see page 17 of the document
I have do it as the mockup described. But the actually result is not same as the scenario used in mockup. In the mockup, the SUM function does not have arguments, but in reality, the SUM function has 3 arguments(we fetch the function and it's arguments from model API), so it looks not consistent with the mockup. Please see page 4 and page 6 of the spec.
Qiangsheng, The issue with both the bugs is same the UI is not implemented as mocked up. Please refer to the attachments of this email - Firstly UI should not show groupName, filter and expression ( its redundant ) Example when SUM function is selected there are no parameters Looks like from Xiong's comments model is returning 3 parameters for SUM, i.e expression, group, filter. - We need to fix this, either model should be changed or UI should ignore filter, group and expression in the arguments I am reopening both these bugs
Created attachment 69359 [details] Mockup of the current implementation Please refer to the comments in hte mockup for what is missing. Thanks.
Reopening bug as already mentioned in email.
(In reply to comment #21) > Created an attachment (id=69359) [details] > Mockup of the current implementation > > Please refer to the comments in hte mockup for what is missing. Thanks. > The three fields you pointed out in the attached file are dynamically generated by selected function, the model API return the three arguments for the function SUM, so GUI display these fields. GUI did not hard code to display these fields, and i think we should not filter these fields on GUI side, so i reassign to model team.
The title issue has fixed by 189358
Fixed.
I am using May 31 build. The changes to aggregation builder dialog have not yet been fixed completely. Still some extra fields are seen. 1. We do not need 'expr' field. 2. Filter label should read 'Filter condition' Please see attachment 69359 [details] Same changes apply to x Tab aggregation builder also. Please reopen the bug
Looks like the expression field is still shown as an argument of the all the functions.
We've checked this bug yesterday. Verify with QA, there is no expression in today's build.
verified. Build id: v20070601-0630
Added this to the 2.2 plan.
