gbmcneil
asked on
How Do I Get an XSL Application to Page The Output of the Records Displayed?+
Hello Gertone:
In an earlier discussion...
https://www.experts-exchange.com/questions/23856726/Is-there-a-method-to-read-a-XML-file-in-IExplorer-that-doesn't-involve-Msxml2-DOMDocument.html?anchorAnswerId=22829616#a22829616
I received assistance in creating a web application that would "page" the number of records displayed. That is, the after displaying 15 records, the app would pause and display PREVIOUS and NEXT buttons to guide the user back and forth through the data.
You provided me with the basics of this system and thus far I have a system that does exactly that - it pauses after the first 15 records have been displayed. But, I still cannot move to the next page. There must be a bug somewhere. I am know re-posting the XSLT code for your review.
Do you have any idea what must be changed to get the next page to appear (and once there, move to the previous group of 15 records)?
Thanks for all your help so far.
In an earlier discussion...
https://www.experts-exchange.com/questions/23856726/Is-there-a-method-to-read-a-XML-file-in-IExplorer-that-doesn't-involve-Msxml2-DOMDocument.html?anchorAnswerId=22829616#a22829616
I received assistance in creating a web application that would "page" the number of records displayed. That is, the after displaying 15 records, the app would pause and display PREVIOUS and NEXT buttons to guide the user back and forth through the data.
You provided me with the basics of this system and thus far I have a system that does exactly that - it pauses after the first 15 records have been displayed. But, I still cannot move to the next page. There must be a bug somewhere. I am know re-posting the XSLT code for your review.
Do you have any idea what must be changed to get the next page to appear (and once there, move to the previous group of 15 records)?
Thanks for all your help so far.
ASKER
And, here is the html that calls the XSL -
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Dow Jones for Gordon</title>
<script language="javascript">
function TransF(page, first) }
// create and load the XML document
var oXML = new ActiveXObject("Msxml2.DOMDocument");
oXML.async = false;
oXML.load("Dow_Stocks_Data.xml");
// create and load the XSL document
var oXSL = new ActiveXObject("Msxml2.FreeThreadedDOMDocument");
oXSL.async = false;
oXSL.load("Dow-Stocks.xsl");
// create the template processor
var oTmpl = new ActiveXObject("Msxml2.XSLTemplate");
oTmpl.stylesheet = oXSL;
oProc = oTmpl.createProcessor();
oProc.input = oXML;
// add parameters
oProc.addParameter("price", price);
oProc.addParameter("sector", sector);
oProc.addParameter("sort", sortseq);
oProc.addParameter("page", page);
oProc.addParameter("first", first);
// make the transform
oProc.transform();
var resHTM = oProc.output;
// write the transformation result as the inner HTML of the div
document.getElementById("RB").innerHTML = resHTM;
}
</script>
</head>
<body>
<div>
<button type="SUBMIT" name="Button1" value="Button1" onclick="TransF(1,15);">
<img src="button.gif"/>
</button>
</div>
<div>
<div id="RB"></div>
<div>
</body>
</html>ASKER
Gertone -
One thing that I observe is that when the XSL code calls TransF - this function is located in located in the html code.
Now, it is not apparent to me that calling the transform in the html that that links the XSL code in the html program.
The tipoff is that when the XSL code calls the TransF function it does not trigger the alert() that was included for debugging purposes.
Do you think that we should duplicate the TransF function in the XSL file (if that is possible) so it can see this function?
One thing that I observe is that when the XSL code calls TransF - this function is located in located in the html code.
Now, it is not apparent to me that calling the transform in the html that that links the XSL code in the html program.
The tipoff is that when the XSL code calls the TransF function it does not trigger the alert() that was included for debugging purposes.
Do you think that we should duplicate the TransF function in the XSL file (if that is possible) so it can see this function?
I am not sure that I grasp this question completely.
The TransF() is never called in the XSLT.
In the XSLT we create some HTML snippte, that is pulled in, in an <div>
so the serialisation of the resulting HTML has the TransF()
If you call it, it will be from the browser window (unaware of the XSLT) and it should execute the allert()
If you want to "allert" information from your XSLT internals (such as variable values) you should simply output them, so they become visible in the HTML
The TransF() is never called in the XSLT.
In the XSLT we create some HTML snippte, that is pulled in, in an <div>
so the serialisation of the resulting HTML has the TransF()
If you call it, it will be from the browser window (unaware of the XSLT) and it should execute the allert()
If you want to "allert" information from your XSLT internals (such as variable values) you should simply output them, so they become visible in the HTML
ASKER
Hi Gertone:
Well, it does not execute the alert() referenced in the XSLT when either the PREVIOUS or NEXT buttons are pressed. And, if the Transf() code is not being executed by depresssing the buttons, there is no way the record list is going to "page".
Well, it does not execute the alert() referenced in the XSLT when either the PREVIOUS or NEXT buttons are pressed. And, if the Transf() code is not being executed by depresssing the buttons, there is no way the record list is going to "page".
ASKER
Gertone:
Does your version of the code page the data?
Does your version of the code page the data?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Believe it or not I just came to the same conclusion myself. So, there are params that require single quote marks and variables that don't. Pretty challenging I'd say. Let me play with it a little. I think it's time you went to sleep.
Well, the ones I showed in my example don't require quotes,
since they are integers, not cast to string for the function call
price is most of the time an integer too, but you have 'All', so you should add quotes there,
the other two are obvious, they are always strings
anyway, basically you can put quotes around all of them
and yes, I am of to bed now (1AM here)
cheers
Geert
since they are integers, not cast to string for the function call
price is most of the time an integer too, but you have 'All', so you should add quotes there,
the other two are obvious, they are always strings
anyway, basically you can put quotes around all of them
and yes, I am of to bed now (1AM here)
cheers
Geert
ASKER
Good Morning Gertone:
After making sure there was consistency between the calling variables, parameters, and TransF - the "paging" code functions, but in a very strange way. When the NEXT button is pressed the the app will add the next page of data to the bottom of the existing data. The desired way, obviously, is to replace the line items with the current page-full of records.
And when going backwards (by pressing the PREVIOUS button) the code does more or less the same thing. It subtracts the current pageful of records from the existing records that are shown.
This type of functionality becomes most obvious when the number of records in a page (the "$Page" variable is set to 10. That creates the opportunity to see 3 pages (if total number of records is 30), and put a little stress on the PREV and NEXT buttons.
Do you know where the logic would be to display, say, only records "11 to 20" or "21 to 30" - replacing what is currently displayed? Thanks.
Gordo
After making sure there was consistency between the calling variables, parameters, and TransF - the "paging" code functions, but in a very strange way. When the NEXT button is pressed the the app will add the next page of data to the bottom of the existing data. The desired way, obviously, is to replace the line items with the current page-full of records.
And when going backwards (by pressing the PREVIOUS button) the code does more or less the same thing. It subtracts the current pageful of records from the existing records that are shown.
This type of functionality becomes most obvious when the number of records in a page (the "$Page" variable is set to 10. That creates the opportunity to see 3 pages (if total number of records is 30), and put a little stress on the PREV and NEXT buttons.
Do you know where the logic would be to display, say, only records "11 to 20" or "21 to 30" - replacing what is currently displayed? Thanks.
Gordo
I will look into this.
Of course, your desired way is the way I intended this to be, so there must be a small bug
Of course, your desired way is the way I intended this to be, so there must be a small bug
This is an interesting bug indeed
I have used the original apply-template sfrom my example (since that was the shorter version)
But it is equal
where you now have
<xsl:apply-templates select="Record[Exchange='N
you should have
<xsl:apply-templates select="Record[Exchange='N
or
<xsl:apply-templates select="Record[Exchange='N
it is an interesting example where
[position() >= $first and position() < ($first + $page)]
and
[position() >= $first ][ position() < ($first + $page)]
are not equal
In the second case, the position() in the second predicate, is the position() in the allready selected nodeset,
(so starting from $first)
It is a stupid mistake to make in the first place, but a damn hard one to trace in debugging :-)
I have used the original apply-template sfrom my example (since that was the shorter version)
But it is equal
where you now have
<xsl:apply-templates select="Record[Exchange='N
you should have
<xsl:apply-templates select="Record[Exchange='N
or
<xsl:apply-templates select="Record[Exchange='N
it is an interesting example where
[position() >= $first and position() < ($first + $page)]
and
[position() >= $first ][ position() < ($first + $page)]
are not equal
In the second case, the position() in the second predicate, is the position() in the allready selected nodeset,
(so starting from $first)
It is a stupid mistake to make in the first place, but a damn hard one to trace in debugging :-)
ASKER
Very Good Gertone -
I would have never found that bug. For the benefit of those following this discussion, I think that we should point up that one of the lines in the "<xsl:apply-templates select" section of code should change to:
<xsl:apply-templates select="Record[Exchange !='XXXX'] [EndPrice > $low-price-level][EndPrice
and that the "less than the first position plus the page should include a "<" rather than <. The processor often doesn't like the < sign.
Thanks very much again for your contribution.
I would have never found that bug. For the benefit of those following this discussion, I think that we should point up that one of the lines in the "<xsl:apply-templates select" section of code should change to:
<xsl:apply-templates select="Record[Exchange !='XXXX'] [EndPrice > $low-price-level][EndPrice
and that the "less than the first position plus the page should include a "<" rather than <. The processor often doesn't like the < sign.
Thanks very much again for your contribution.
welcome
ASKER
Hello Gertone:
I've made great progress at this end, but still have a bug. Do you have any energy left to look into it?
Gordon
I've made great progress at this end, but still have a bug. Do you have any energy left to look into it?
Gordon
of course, tell me
ASKER
Gertone:
There is some very unusual behavior displayed when the sort sequence is defined to be something other than the default (by EquityName) as is the arrangement in the XML file.
For example, if it is desirable to see our little list of Dow Index stocks sorted by their most recent prices (EndPrice), then the processor appears to be breaking down the total number of stocks into the number we've defined per page and sorting each of these two pages separately. So, if the page is defined as having 15 stocks, there end up being two pages (each containing 15 stocks eacg) making up the Dow list.
Now, what appears to be happening is that Page 1 is sorted. Then Page 2 is sorted. Obviously, what is desired is for the records making up Pages 1 and 2 to be sorted all at the sametime and then all displayed in descending order from records 1 thru 15 to records and then 16 thru 30.
I think what is throwing the system off is the steps taken to arrive at the final sort. In the code -
<xsl:when test="$sort='EndPrice' and $sector = 'All'">
<xsl:apply-templates select="Record[Exchange !='XXXX'] [EndPrice > $low-price-level][EndPrice
<xsl:sort select="EndPrice" data-type="number" order="descending"/>
</xsl:apply-templates>
</xsl:when>
it seems that a request is being made to select only so many records as are less than the first (position) plus the the number per page. If the "sort" could be done first followed by the "select", one might think that the correct order would result.
Any thoughts?
There is some very unusual behavior displayed when the sort sequence is defined to be something other than the default (by EquityName) as is the arrangement in the XML file.
For example, if it is desirable to see our little list of Dow Index stocks sorted by their most recent prices (EndPrice), then the processor appears to be breaking down the total number of stocks into the number we've defined per page and sorting each of these two pages separately. So, if the page is defined as having 15 stocks, there end up being two pages (each containing 15 stocks eacg) making up the Dow list.
Now, what appears to be happening is that Page 1 is sorted. Then Page 2 is sorted. Obviously, what is desired is for the records making up Pages 1 and 2 to be sorted all at the sametime and then all displayed in descending order from records 1 thru 15 to records and then 16 thru 30.
I think what is throwing the system off is the steps taken to arrive at the final sort. In the code -
<xsl:when test="$sort='EndPrice' and $sector = 'All'">
<xsl:apply-templates select="Record[Exchange !='XXXX'] [EndPrice > $low-price-level][EndPrice
<xsl:sort select="EndPrice" data-type="number" order="descending"/>
</xsl:apply-templates>
</xsl:when>
it seems that a request is being made to select only so many records as are less than the first (position) plus the the number per page. If the "sort" could be done first followed by the "select", one might think that the correct order would result.
Any thoughts?
You are right in your observation, paging happens too early
You should remove th epaging predicate from the apply templates and create a test in the Record template,
since you can't have variables in the predicate of the match attribute,
you will need an if statement
something like this
<xsl:template match="Record">
<xsl:if test ="position() >= $first and position() < ($first + $page)">
... do all that you had previously in your record template ...
</xsl:if>
</xsl:template>
You should remove th epaging predicate from the apply templates and create a test in the Record template,
since you can't have variables in the predicate of the match attribute,
you will need an if statement
something like this
<xsl:template match="Record">
<xsl:if test ="position() >= $first and position() < ($first + $page)">
... do all that you had previously in your record template ...
</xsl:if>
</xsl:template>
ASKER
Thank you for your help. Let me play with it a little.
ASKER
I have removed the record predicate from the <xsl:template match="Records"> section and moved it to the <xsl:template match="Record"> section as as test.
The result does not seem to be any different. My code is shown below.
The result does not seem to be any different. My code is shown below.
<!-- Record select and sort -->
<xsl:template match="Records">
<DIV>
<table border="1" width="500" cellpadding="3" cellspacing="3">
<xsl:call-template name="header"/>
<xsl:choose>
<xsl:when test="$sort='EquityName' and $sector = 'All'">
<xsl:apply-templates select="Record[Exchange !='XXXX'] [EndPrice > $low-price-level][EndPrice < $high-price-level] [position() >= $first and position() < ($first + $page)]">
<xsl:sort select="EquityName" data-type="text" order="ascending"/>
</xsl:apply-templates>
</xsl:when>
<xsl:when test="$sort='EquityName' and $sector != 'All'">
<xsl:apply-templates select="Record[Exchange = $sector] [EndPrice > $low-price-level][EndPrice < $high-price-level] [position() >= $first and position() < ($first + $page)]">
<xsl:sort select="EquityName" data-type="text" order="ascending"/>
</xsl:apply-templates>
</xsl:when>
<xsl:when test="$sort='EndPrice' and $sector = 'All'">
<xsl:apply-templates select="Record[Exchange !='XXXX'] [EndPrice > $low-price-level][EndPrice < $high-price-level] ">
<xsl:sort select="EndPrice" data-type="number" order="descending"/>
</xsl:apply-templates>
</xsl:when>
<xsl:when test="$sort='EndPrice' and $sector != 'All'">
<xsl:apply-templates select="Record[Exchange = $sector] [EndPrice > $low-price-level][EndPrice < $high-price-level] ">
<xsl:sort select="EndPrice" data-type="number" order="descending"/>
</xsl:apply-templates>
</xsl:when>
<xsl:when test="$sort='Change' and $sector = 'All'">
<xsl:apply-templates select="Record[Exchange !='XXXX'] [EndPrice > $low-price-level][EndPrice < $high-price-level] [position() >= $first and position() < ($first + $page)]">
<xsl:sort select="Change" data-type="number" order="descending"/>
</xsl:apply-templates>
</xsl:when>
<xsl:when test="$sort='Change' and $sector != 'All'">
<xsl:apply-templates select="Record[Exchange = $sector] [EndPrice > $low-price-level][EndPrice < $high-price-level] [position() >= $first and position() < ($first + $page)]">
<xsl:sort select="Change" data-type="number" order="descending"/>
</xsl:apply-templates>
</xsl:when>
</xsl:choose>
<!--
<th STYLE="bgcolor:#d4d0c8"></th>
-->
</table>
<div>
<xsl:variable name="new-first-p">
<xsl:choose>
<xsl:when test="($first - $page - 1) > 1">
<xsl:value-of select="$first - $page"/>
</xsl:when>
<xsl:otherwise>1
</xsl:otherwise>
</xsl:choose>
</xsl:variable>
<xsl:variable name="new-first-n">
<xsl:choose>
<xsl:when test="($first + $page) > $cnt-records">
<xsl:value-of select="$first"/>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="$first + $page"/>
</xsl:otherwise>
</xsl:choose>
</xsl:variable>
<xsl:variable name="last-number">
<xsl:value-of select="$cnt-records mod $page"/>
</xsl:variable>
<xsl:variable name="last-first">
<xsl:choose>
<xsl:when test="$last-number > 0">
<xsl:value-of select="$cnt-records - $last-number + 1"/>
</xsl:when>
<xsl:when test="$last-number < 1">
<xsl:value-of select="$cnt-records - $page + 1"/>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="0"/>
</xsl:otherwise>
</xsl:choose>
</xsl:variable>
<xsl:variable name="max-records">
<xsl:choose>
<xsl:when test="$first + $page - 1 >= $cnt-records">
<xsl:value-of select="$cnt-records"/>
</xsl:when>
<xsl:when test="$first + $page - 1 < $cnt-records">
<xsl:value-of select="$first + $page - 1"/>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="0"/>
</xsl:otherwise>
</xsl:choose>
</xsl:variable>
<H4 STYLE="font-family: Arial, Helvetica, Sans-Serif; font-weight: 900; font-size: 11px"><xsl:value-of select="$first"/> to <xsl:value-of select="$max-records"/> of <xsl:value-of select="$cnt-records"/> Record(s) </H4>
<H5 STYLE="position: absolute; top: 103px; left: 525px; font-family: Arial, Helvetica, Sans-Serif; font-weight: 900; font-size: 11px; color:#ffffff"><xsl:value-of select="$first"/> to <xsl:value-of select="$max-records"/> of <xsl:value-of select="$cnt-records"/> Record(s) </H5>
<!---
<H6><xsl:value-of select="$last-first"/></H6>
-->
<button STYLE="font-family: Arial, Helvetica, sans-serif; font-weight: medium; font-size: 11px" type="SUBMIT" name="First" value="First" onClick="TransF('{$price}', '{$sector}', '{$sort}', '{$page}', 1);">First</button>
<button STYLE="font-family: Arial, Helvetica, sans-serif; font-weight: medium; font-size: 11px" type="SUBMIT" name="Prev" value="Prev" onClick="TransF('{$price}', '{$sector}', '{$sort}', '{$page}', {$new-first-p});">Prev</button>
<button STYLE="font-family: Arial, Helvetica, sans-serif; font-weight: medium; font-size: 11px" type="SUBMIT" name="Next" value="Next" onClick="TransF('{$price}','{$sector}', '{$sort}', '{$page}', {$new-first-n});">Next</button>
<button STYLE="font-family: Arial, Helvetica, sans-serif; font-weight: medium; font-size: 11px" type="SUBMIT" name="Last" value="Last" onClick="TransF('{$price}', '{$sector}', '{$sort}', '{$page}', {$last-first});">Last</button>
</div>
</DIV>
<button STYLE="position: absolute; top: 102px; left: 370px; font-family: Arial, Helvetica, sans-serif; font-weight: medium; font-size: 11px" type="SUBMIT" name="First" value="First" onClick="TransF('{$price}', '{$sector}', '{$sort}', '{$page}', 1);">First</button>
<button STYLE="position: absolute; top: 102px; left: 401px; font-family: Arial, Helvetica, sans-serif; font-weight: medium; font-size: 11px" type="SUBMIT" name="Prev" value="Prev" onClick="TransF('{$price}', '{$sector}', '{$sort}', '{$page}', {$new-first-p});">Prev</button>
<button STYLE="position: absolute; top: 102px; left: 434px; font-family: Arial, Helvetica, sans-serif; font-weight: medium; font-size: 11px" type="SUBMIT" name="Next" value="Next" onClick="TransF('{$price}','{$sector}', '{$sort}', '{$page}', {$new-first-n});">Next</button>
<button STYLE="position: absolute; top: 102px; left: 467px; font-family: Arial, Helvetica, sans-serif; font-weight: medium; font-size: 11px" type="SUBMIT" name="Last" value="Last" onClick="TransF('{$price}', '{$sector}', '{$sort}', '{$page}', {$last-first});">Last</button>
</xsl:template>
<!-- Header row templates -->
<xsl:template name="header">
<tr>
<th style="color: #000000; text-align: left; font-family: Arial, Helvetica ; font-weight: 900; font-size: 11px;">RecNo...</th>
<th style="color: #000000; text-align: left; font-family: Arial, Helvetica ; font-weight: 900; font-size: 11px;">Symbol</th>
<th style="color: #000000; text-align: left; font-family: Arial, Helvetica ; font-weight: 900; font-size: 11px;">Exchange</th>
<th style="color: #000000; text-align: left; font-family: Arial, Helvetica ; font-weight: 900; font-size: 11px;">EquityName</th>
<th style="color: #000000; text-align: right; font-family: Arial, Helvetica ; font-weight: 900; font-size: 11px;">BeginPrice</th>
<th style="color: #000000; text-align: right; font-family: Arial, Helvetica ; font-weight: 900; font-size: 11px;">EndPrice</th>
<th style="color: #000000; text-align: right; font-family: Arial, Helvetica ; font-weight: 900; font-size: 11px;">Difference</th>
<th style="color: #000000; text-align: right; font-family: Arial, Helvetica ; font-weight: 900; font-size: 11px;">Change</th>
</tr>
</xsl:template>
<xsl:template match="Record">
<xsl:if test ="position() >= $first and position() < ($first + $page)">
<tr>
<xsl:if test="Difference < 0">
<xsl:attribute name="style">
<xsl:text>color: #990000;</xsl:text>
</xsl:attribute>
</xsl:if>
<xsl:if test="Difference > 0">
<xsl:attribute name="style">
<xsl:text>color: #006B00;</xsl:text>
</xsl:attribute>
</xsl:if>
<td><xsl:value-of select="position() + $first - 1"/></td>
<td><xsl:value-of select="Symbol"/></td>
<td><xsl:value-of select="Exchange"/></td>
<td><xsl:value-of select="EquityName"/></td>
<td style="text-align: right;">
<xsl:value-of select="format-number(BeginPrice, '#.00')"/></td>
<td style="text-align: right; format-number(. , '#.00')">
<xsl:value-of select="format-number(EndPrice, '#.00')"/></td>
<td style="text-align: right; format-number(. , '#.00')">
<xsl:value-of select="format-number(Difference, '#.00')"/></td>
<td style="text-align: right; format-number(. , '#.00')">
<xsl:value-of select="format-number(Change, '#.00')"/></td>
</tr>
</xsl:if>
</xsl:template>
</xsl:stylesheet>
ASKER
Gertone:
I am still having problems with my app. It will not sort correctly. I have posted my code above which moves the predicate to the Martch Templateb Record section for the situaton where the user is trying to sort by EndPrice. Can you find some time to take a look a it.
Thanks.
Gordo
I am still having problems with my app. It will not sort correctly. I have posted my code above which moves the predicate to the Martch Templateb Record section for the situaton where the user is trying to sort by EndPrice. Can you find some time to take a look a it.
Thanks.
Gordo
does it sort correctly without paging?
ASKER
If I set the "Lines Per Page" to 30 (which is the entire group of records in the recordset), the sort is correct for all three possible sequences - EquityName, EndPrice, and %Change.
If I set the page to 15 records, EquityName is okay (I think because that is how the collection of records is pre-sorted to begin with). But, when the sequence requested is by EndPrice or %Change, I get two different sorts per selection, one for each page of data.
If I set the page to 15 records, EquityName is okay (I think because that is how the collection of records is pre-sorted to begin with). But, when the sequence requested is by EndPrice or %Change, I get two different sorts per selection, one for each page of data.
Hi Gordo,
well, I have tested my suggestion from
https://www.experts-exchange.com/questions/23879943/How-Do-I-Get-an-XSL-Application-to-Page-The-Output-of-the-Records-Displayed.html?cid=748&anchorAnswerId=22913516#a22913516
and it works wonderfully well with my code (which is a simplified version of what you must have now)
Theoretically it should anyway
Something must have gone wrong in the implementation of it
I suggest that you post your current XSLT (maybe package the whole thing again, either mail or here) so I can look at it
cheers
Geert
well, I have tested my suggestion from
https://www.experts-exchange.com/questions/23879943/How-Do-I-Get-an-XSL-Application-to-Page-The-Output-of-the-Records-Displayed.html?cid=748&anchorAnswerId=22913516#a22913516
and it works wonderfully well with my code (which is a simplified version of what you must have now)
Theoretically it should anyway
Something must have gone wrong in the implementation of it
I suggest that you post your current XSLT (maybe package the whole thing again, either mail or here) so I can look at it
cheers
Geert
ASKER
Open in new window