boen_robot

It's still only JavaScript, so I say "No" too. I don't see how XML fits in all this anyway. The only thing it has to do is that it's present in the name of the key object: XmlHttpRequest().

Haha... stop it, stop it... Khm... anyway... In order for a server to deliver data over an encrypted connection, the server actually needs to support the encryption method (and browser on that matter, but all of today's one do) and be configured as to where's the certificate, the port used, etc. are.W3Schools doesn't have an SSL certificate and because of that, they haven't set up their servers for HTTPS usage. They don't need to either though.OK. All of the above is probably not making scence at all. Let me say it "slowly".When you send a POST data to a server, that data is passed from your computer, to your network gateway (the machine delivering you internet) to your ISP's main machine (the one delivering all the internet of the ISP), to more routers, switches, gateways, etc. until it reaches the server. The server then uses that data and delivers content based on it. So, all of the above computers mentioned have your data "captured". This data might as well be a password or a credit card number. If anyone had access to those machines and knew what (s)he was looking for, he could find your data in the mixture of all others.So where does SSL come in this? The browser sends the data, but the other computers don't see it as it was sent, but see it the way the browser encrypted it before it sent the data to them. When the data reaches the server, it get's decrpted, so the server can see it's true form and thus perform it's actions.Secured connection is slower however, so only E-commerce sites use it, and even they only use when a sencetive input like credit card numbers or passwords will be entered. Other sites also use it, but again- only on logins or other types of screens where sencetive data will be sent.So, again, there's no difference between the content of a page sent by HTTP or HTTPS. The only difference is how data is being transmitted, not what one gets in the end.

Well, in that case, as I said, look no further then PHP. Simply take the input of the form, validate it (where needed) and create a new XHTML printer friendly page from it. PHP can do that with ease.

You could now try to set up another instance of CF to run on Apache as well CF's own server. There was an application for that in the CF's start menu shortcuts somewhere.

Uhhh.... so what data type is it then ? Result tree fragments can't be accessed with XPath expressions the same way node sets can as far as I know. Context template or not, it's just not defined as a legal action I mean.

It works the same way as it would if an XHTML page was trying to read data from existing XML file:Use XSLT and execute the transformation with a server side scripting language to deliver the output to the client.In the case of WML, the server side script would also need to detect if the user-agent supports XHTML first, and if not, deliver a WML variant.

Strange. I thought VS would be using MSXML (be it 3,4,5 or 6). This error is certanly a surprice.The first exception:[XsltException: Cannot convert the operand to 'Result tree fragment'.]is due to a small error in aalbetski's stylesheet. There's a msxsl:node-set() missing. It's: <xsl:value-of select="msxsl:node-set($zrow)/@*[name() = $attrib]" /> This of course would only imply if msxsl:node-set() was supported to begin with. It won't make a difference in your case.Here's an exhanced solution of mine. Note that I'm aiming at "extension free" way: <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:rs='urn:schemas-microsoft-com:rowset' xmlns:z='#RowsetSchema' xmlns:s='uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882' version="1.0"><xsl:template match="/"><table><thead><tr><xsl:for-each select="//s:AttributeType/@name"><th><xsl:value-of select="."/></th></xsl:for-each></tr></thead><tbody><xsl:for-each select="/xml/rs:data/rs:insert/z:row"><xsl:variable name="currentPosition" select="@*/position()"/><xsl:variable name="data" select="@*[name() = string(//s:AttributeType[position() = $currentPosition]/@name)]"/><tr><xsl:for-each select="//s:AttributeType"><td><xsl:value-of select="$data"/></td></xsl:for-each></tr></xsl:for-each></tbody></table></xsl:template></xsl:stylesheet> Would something like that work for you (note I haven't tested it)?

Now I remember. After the installation, CF opens a browser and does some weird stuff to enable support on Apache. If you've terminated that window before it was done, then that is what caused the problem and for that, you'll need to reinstall CF.

Use this script to call the transformation. It's tested and it's known to work in Opera 9, FF 1.5, IE6 and IE7. Haven't tested FF2, but it should work there.If that doesn't work for you, then it's the fault of some other script you have running (god knows which one).

It's not exactly a good practice, but yes... it's possible.PHP's output can be anything you want, so it doesn't really matter what it looks in the end.Let's say that with a PHP file, you create the CSS file "style.php". When displayed in a browser, it's plain text. Even though this file has a PHP extension, all the browser really cares for is the MIME type, specified in (X)HTML:<link rel="stylesheet" type="text/css" href="style.php" />and/or in the PHP file itself, sent with the header() function: header("Content-type: text/css")

Some codes or links would be nice.

Faxed automatically by the server? Damn... you're making it VERY hard.In order to fax something with PHP, you'll need some sort of fax extension (not built in PHP that is) or write your own one (with C(++)). Or use PHP to execute a premade application (again: made with C(++)) for doing that task. For both of those, you'll need to have full control of the server, but if you do, you might be better off simply putting the server in the restaurant, attach a printer to it, and print the page, instead of faxing it. I mean, printing a page might be easier, scince every computer has built in facilities for printing. You'll only need to execute an application that will "press" the print button.

The admin panel should be ran with CF's server. At least, that's how I do it. You may have done something wrong in setting up CF for Apache, so that's why it may not work there.

The server binary is the "httpd.exe" file in the "bin" folder. In my last post I already told you where the configuration file is. The full paths are as follows:C:\Program Files\Apache Software Foundation\Apache2.2\bin\httpd.exeC:\Program Files\Apache Software Foundation\Apache2.2\conf\httpd.conf

XPath axes are only for use in relative paths as far as I'm aware of.Try something with no axes://menu[@id=products]|//menu[@id=products]/node()

What exactly is not working?In any way, try to change <xsl:template match="/"> to <xsl:template match="/{http://tempuri.org/IncrepDataset.xsd}*"> or simply remove the namespace in the XML.

Instead of usingonsubmit="java script:return onFormSubmit()"over the form, useonClick="java script:return onFormSubmit()"over the submit button. To be exact:<input type="Submit" value="Submit" onClick="java script:return onFormSubmit()"/>

I also see another error. There's an extra space on :hover. Use a:hover {color: #FF00FF} instead.

I'm not much into DTD, but... can you reference the "/" as a numeric entity (I have no idea what the entity number is though)?

You're right. It's a matter of closing the element properly. You need <meta name="keywords" content="key1, key2, key3" /> instead. What stopped you from trying that anyway?

XForms is just not supported natively in any browser yet. It could only be enabled with a plug-in.The only browser today to support XForms natively is X-Smiles. It's good for testing, but you can definetly not convince anyone to use it all the time.

First stop, if you want to use JavaScript to render the output of an XSLT transformation, you'll be better off using this script as it's a cross browser one. The one you've copyed only works in IE.As for your problem. I really don't see how you've managed to get even a single entry. I mean, I don't see "tstamp" and "entry" elements. Only "TStamp" and "Entry" ones.What exacltly you want to display and in what order? If you want to display all "TStamp" and "Entry" elements in the order of which each appears in the document, you could do so with something like this: <?xml version="1.0" encoding="ISO-8859-1"?><!-- Edited with XML Spy v2006 (http://www.altova.com) --><xsl:stylesheet version="1.0"xmlns:xsl="http://www.w3.org/1999/XSL/Transform"><xsl:output method='html' version='1.0' encoding='UTF-8' indent='yes'/><xsl:template match="/"> <html> <body> <h2>Current Log</h2> <table border="1"> <tr bgcolor="#9acd32"> <th align="left">TStamp</th> <th align="left">Entry</th> </tr> <xsl:for-each select="//IncidentLog"> <tr> <td><xsl:value-of select="TStamp"/></td> <td><xsl:value-of select="Entry"/></td> </tr> </xsl:for-each> </table> </body> </html></xsl:template></xsl:stylesheet>

Huh. As it turns out, until recently, we were all using illegal images on our websites and we were making even more obviously illegal animations .As for the PNG thing, I'll currently stick with binary transparency if I need transparency (I'm not much of a designer...). A year or so would probably be enough for most people to update and that's when I would slowly start pushing PNG's Alpha slowly up.There is one thing that hopefully people won't use though. There was a bug in the RC1 build, which I think isn't fixed in the final either. When you use a transparency filter over alpha transparent PNG, it looses it's transparency even though the filter is applied. On the bright side, this bug is the best way to test how the same PNG would look in IE6 . I mean, if you make alpha filter of 99% opacity, the image would practically be opaque, yet degraded up to binary transparency.Now that I think of it, I may start using PNGs a lot sooner. The pages themselves would however suggest the latest version of the browser available (pointing out the version numbers of course). When people see a few sites telling about the new browser, they are more likely to upgrade . That is, if they read those notes to begin with. It's too bad we can't enforce people to download IE7 the same way they download Flash player. Good thing MS does.

That's just it. It's not. I tried telling you that from the start. A variable is a converted to a single string, not a node-set.But wait... I think I see what you're trying to do. For the desired output, wouldn't this part of the XML be enough: <z:row Date='13.05.2006' Time='09:15:20' TCC18='50' TCC19='40' TCC20='30'/><z:row Date='13.05.2006' Time='09:15:22' TCC18='60' TCC19='40' TCC20='10'/><z:row Date='13.05.2006' Time='09:15:23' TCC18='70' TCC19='70' TCC20='30'/><z:row Date='13.05.2006' Time='09:15:24' TCC18='80' TCC19='40' TCC20='30'/> So you could simply use: <table><thead><tr><xsl:for-each select="/xml/rs:data/rs:insert/z:row/@*"><th><xsl:value-of select="name()"/></th></xsl:for-each></tr></thead><tbody><xsl:for-each select="/xml/rs:data/rs:insert/z:row" ><tr><xsl:for-each select="/xml/rs:data/rs:insert/z:row/@*"><td><xsl:value-of select="."/></td></xsl:for-each></tr></xsl:for-each></tbody></table>

Read the PHP tutorial. It's described there. See the $_GET variable.