Subject:WYSIWYG Problem Author:Mohamed Nuur Date:30 Dec 2002 08:25 PM
I am working on a reports maker project where non-technical users can take a whole bunch of pre-made xsl stylesheets and modify them. Well so far all my xsl's are ready for the clients to modify at will and do what they will with it, the only problem i see is (and there are more, theyre not important --yet).... is that when you have a big if statement like:
Also is there any way in the WYSIWYG that clients can quickly get sums of collumns or rows (i dont think there is but i just want to verify).
Subject:Re: WYSIWYG Problem Author:Minollo I. Date:30 Dec 2002 09:19 PM
>The whole row becomes grayed out. But in smaller if's, it works.. the
>following works just fine:
The row is grayed out if the "if" statement is not successful on the sample
instance used to exercise wysiwyg; if the "if" is at the row level, you
should be able to click on the if marker on the left of the table so that
it's selected, then choose WYSIWYG|Conditional Processing (Table
Row)|Activate if; that will force WYSIWYG to choose the XML element on
which you are iterating that satisfies the condition.
If the "if" is visible as a glyph (not a the table row level), the
procedure is equivalent; select the inactive if glyph, and choose
WYSIWYG|Conditional Processing|Activate if.
>Also is there any way in the WYSIWYG that clients can quickly get sums of
>collumns or rows (i dont think there is but i just want to verify).
It's a PCR that we will eventually address. Currently no helper functions
are available to achieve that.
Subject:Re: WYSIWYG Problem Author:Mohamed Nuur Date:31 Dec 2002 01:26 PM
Thats exactly what I needed... and for the sums, I have an xsl template that has 4 rows by 4 collumns with the sums on either sides that has the code to do summing, and it mainly uses variables :( I want to get away from this soon but its something that only the advanced users can do for the time being.