there's probably a lot more that needs to be done.
Shit. Like what, for example?
(Now I gotta tell my boss that the project he gave me four days to work on is gonna take longer, as today is already day four.)
Got a question about technology? Ask it here. Discussion of hardware, software, TiVos, multi-region DVDs, Windows, Macs, LINUX, hand-helds, iPods, anything tech related. Better than any helpdesk!
there's probably a lot more that needs to be done.
Shit. Like what, for example?
(Now I gotta tell my boss that the project he gave me four days to work on is gonna take longer, as today is already day four.)
A recordset is different than an XML document, it probably has a different layout, and needs to be traversed differently. It may just work, but I don't have enough information on what you're trying to do.
Also, I am confused here. Let me back up. The transformation is currently done on the client, in a webpage. It's done in Javascript with the xml in a variable and the xsl embedded in the web page. The code is like this:
xmlTimesheet.loadXML(ip_xmlTimeSheet.xml);
xslSource.loadXML(xslTimesheetFromDB.xml);
xmlTimesheetHTML.loadXML(xmlTimesheet.transformNode(xslSource));
So I don't understand why the xsl document specified the rowset stuff. Anyway, I have to do this on the server, in a VB6 or VB.Net component. That's what I can't get to work.
When I run xsl it's from the command-line on a Unix system. I don't think I can help you with this.
OK, thanks anyway.
I think this is code for "Uses a TARDIS."
If he has a TARDIS and hasn't told me, he is in so much trouble.
$25 computer is barely larger than the average USB stick
The Raspberry Pi is one tiny computer that's actually functional enough for modern use. It doesn't get any more barebones than a little circuit board with a 700MHz ARM 11 processor, a USB port, an HDMI port and an install of Ubuntu Linux.
Designed by game developer David Braben and his friends, the Raspberry Pi's basic structure was created to encourage schoolchildren to hack and mod it to unlock its true potential. On the stock Raspberry Pi, all one needs to do is plug in a display through the HDMI port and a keyboard through the USB and it's good to go — getting online requires another adapter.
While pictures show only a processor, USB and HDMI port, Raspberry Pi's website actually reveals its other secret powers: 128MB of SDRAM, OpenGL ES 2.0, 1080p HD decoding, composite output, SD card slot and other flavors of Linux such as Iceweasel and Python. A 12 megapixel camera sensor can also be connected (as seen in pic above).
But will it run OSX?
Mr Scola, are you around today?
I am now trying to do my xsl transformation on the server in the .ASP page (using VB Script). I think I've almost got it working. Currently I'm testing the transformation using Editix. When I run it, I get the following error:
The URI 'http://www.w3.org/1999/XSL/Transform' does not identify an external Java class
That error occurs on the following line in the xsl document:
<xsl:if test="pay_date[@dow = xsl:getDOW($loopcounter) and @sf = xsl:getSF($loopcounter)]">
The function DOW is defined like so:
<msxsl:script language="JScript" implements-prefix="xsl">
function getDOW(iCounter){
if(iCounter == 8){
return 6;
}
if(iCounter == 7){
return 7;
}
if(iCounter == 1){
return 6;
}
return 7 - iCounter;
}
...
We don't use Java in our xsl stuff, so I'm not sure what's going on. The error might be because Editix doesn't have some Java it needs or something? Any ideas? (I'm not at work, so I can't try the transformation on the .ASP page right now.)
eta: OK, I think the problem is that Editix doesn't have access to the JScript interpreter. So I'll have to try this tomorrow on our web server.
I would try something along the lines of putting the function in its own namespace, i.e.
<msxsl:script language="JScript" implements-prefix="foo">
And then calling the function as foo:getDOW rather than xsl:getDOW.
You will also need to declare the namespace at the top of the document:
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="1.0"
xmlns:foo="http://your-url-here"
extension-element-prefixes="foo">
Again, I'm not very familiar with the MS toolset, so I don't know if this will work or not.