boen_robot

You are practically looking for the holy grail. The only thing missing is the requrement of a third column .In order to get the left column to the left, you obviously need float:left, but for the height.. That's much bigger issue.See this layout and try to adjust it, so it has only 2 columns.

What version of dreamwaver are you using? I use 8 and it's not doing that. When I write "t" it suggests table and other tags that start with "t" so I can either continue typing for a more detailed suggestion or select from the list (in short: auto complete). And that's it. The ">" is automatically written, but it's left to me to decide the things inside. There are no <tr>s and <td>s created. When I type "</" it automatically writes the closing </table> tag, unless I have written some other tag after, that needs closing.If you're using MX2004, well... yeah, it sucks.

Actually, because XQuery is not yet a recommendation, it's not avaiable for any official language yet. It's avaiable as a language for some databases as an expansion to SQL, but that's it.XQuery will be avaiable in XSLT 2.0 so that's when it's true power will be uncovered. Until then, in order to manipulate XML documents,you would need to use XPath inside XSLT or some server side scripting language.

Actually, if you're going to use ASP, it's MUCH better to store different types of data in both SQL and XML depending on their purpose. SQL for catalogue purposes, and XML for all other data (most often- interface data such as the titles for the different links). Using XSLT you can transform the data more... clearly and use ASP only to execute the transformation and manipulate the database.

Much better. This blue rocks . Though I think you could have let the red too, just incase someone else prefers it .

I don't think there's any way to tell if you're showing only the root of the Schema .

Did anyone read my post? Oh, for the love of god:

Actually, I think this is possible with aural CSS2 too .

I personally like blue best, but this particular: No. Why don't you make the other colors gradients too? I think that would be more fair .

What I meant to say is that PHP doesn't have built in XSLT processor. It is avaiable with an extension. See the XSL functions of PHP for details. If anyone knows how to install the extension, please, do tell.

Maybe using some predicates will do the trick? <xsl:template match="/"><xsl:variable name="name">Jane</xsl:variable><xsl:choose><xsl:when test="name=$name"><xsl:for each="Workers/Worker[name=$name]">Yes<br /></xsl:for-each></xsl:when><xsl:otherwise>No</xsl:otherwise></xsl:choose></xsl:template> If I am correct, the conditional will look into every name attribute in the document and compare it with the variable. If there are any matches, it will loop through all workers with the specified name and will output Yes for each one. If there's not any avaiable, there will be only one No.P.S. I haven't tested this.P.S.S. You'll need some DOM that would create the variable with the desired value from a form, if you want to make this application practical. I can't do that script though.

As far as I know, this whole part of the forum is for Suggestions about W3Schools. If you have some kind of "upgrade" for W3Schools or something, you could always present it at least.If you mean an article... well.. W3Schools is about learning the basics, not mastering the languages. There are many materials on the net where you can find "how to" tutorials and everything. W3Schools is about showing you what's all about.

I knew XSLT could write JavaScript and VBScript, but ADO? Really?!?! Isn't ADO part of ASP which is a server side scripting language?Khm... anyway, we have our last problem here. As far as I understood, mona works with PHP. This would complicate the things a bit, scince unlike ASP, PHP doesn't have an XSLT processor .

PHP doesn't have XSLT processor built in as I have stated many times. Unless you find a way to install some kind of extension (see php.net for details on this one), you can't make PHP process the XSLT unless you create your own XSLT processor with PHP itself. I don't know much about PHP, so I can't give you a sample of what I mean.And about the above example I meant for example a database which has a record like <hardware><ram>256mb</ram></hardware> And another record with for example <image><url>www.example.com/pic1.jpg</url><alt>pic1</alt></image> And now let's say we have a PHP file which creates an instanse of a container div for example and catches the data in the <hardware> element. It then displays it and actually shows that the content from the <ram> element is RAM memory. The same is done for the <image> of the current row.Normally, if this was ordinary XML, you would have to transform the data with XSLT and execute it with a server side language. But as said above, PHP doesn't have XSLT support. It does have XML thoguh.This approach is better then to keep each SQL data in it's own record, because it makes the data more structured and expandable. Instead of having another table for the images, you have a single column which contain it. However, this is not always better. Infact, there are not many cases, where this prooves to be usefull.

Perhaps it's the namespace... I recently encountered simmilar thing. Try giving the RSS it's namespaces back. Also, execuse me for my lasiness, but you might want to try "isolating" the problem first. Apply all different changes and removals one by one and see where the problem first arises.

Yes. You must insert the code from this topic in all of your XHTMLs and of course, adjust it properly. That code would display the transformation at the place of the element which has the appropriate ID.

Not with data islands. With XSLT is simpler though. There's the <xsl:sort> element, specialized for this task.

The Web Primer tutorial was written for cases like this. There's a link to it in the middle of the home page. It describes what a web developer needs to know and it practically follows the orders in which one should learn.In short I could say: XHTML, CSS, JavaScript, XML + some server side scripting language of your choise. It might be PHP, ASP, Cold Fusion, etc.The other tutorials are advises for optimizing your work, not for creation of web sites.

Using relative sizes in your CSS for starters?

What is that suppose to mean?

What do you mean by "navigation page"? A site map? Well, it's quite simple actually. Just have your menu data in some XML, transform it with some kind of XSLT and use ASP to execute that transformation. Example:xml <?xml version="1.0" encoding="utf-8"?><menu> <item> <title>Home</title> <link>#</link> </item> <item> <title>About us</title> <link>#</link> </item> <item> <title>News</title> <link>#</link> </item> <item> <title>Links</title> <link>#</link> </item> <item> <title>Images ></title> <link>#</link> <menu> <item> <title>Photos</title> <link>#</link> </item> <item> <title>Wallpapers</title> <link>#</link> </item> </menu> </item></menu> XSLT <?xml version="1.0" encoding="utf-8"?><!-- DWXMLSource="navigation.xml" --><!DOCTYPE xsl:stylesheet [ <!ENTITY nbsp " "> <!ENTITY copy "©"> <!ENTITY reg "®"> <!ENTITY trade "™"> <!ENTITY mdash "—"> <!ENTITY ldquo "“"> <!ENTITY rdquo "”"> <!ENTITY pound "£"> <!ENTITY yen "¥"> <!ENTITY euro "€">]><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"><xsl:output method="html" encoding="utf-8"/><xsl:template match="menu"><xsl:variable name="link" select="link" /><ul class="menu"><xsl:for-each select="item"> <li class="navlink"> <xsl:choose> <xsl:when test="menu"> <a class="hide" href="{$link}"><xsl:value-of select="title" /></a> <xsl:apply-templates select="menu"/> </xsl:when> <xsl:otherwise> <a class="navlink" href="{$link}"><xsl:value-of select="title" /></a> </xsl:otherwise> </xsl:choose> </li></xsl:for-each></ul></xsl:template></xsl:stylesheet> And the ASP from XSLT on the server example.With some CSS, the above could also be a menu (as it's root node implies). Infact, this is the XSLT of the first CSS only menu from cssplay. I'm having some difficulties getting the conditional comments for IE properly, but I'll do it soon hopefully.

A much more speedy solution in my opinion would be for the database to contain the parts of the XML itself and the server side script would only have to assemble and/or transform the data there.

Considering the fact that posting requres interaction with the user and the server, I think the classical approach for the server side scripted forum is better at this poing. Mostly for security reasons. Using XML for every item that doesn't need to be secured sounds as a good thing though. Think about every possible situation that the user might to with the fully accessable XMLs.

The only way I can think of is to restructure the XML itself "manually". Instead of having <doctor><name><first>John</first><last>Smith</last></name></doctor> You could use <doctor><name first="John" last="Smith" /></doctor> And remove ALL line breakes and extra spaces. Example: <doctor><name first="John" last="Smith"/></doctor> But even this is not going to compress the data very much. Infact, that's the reason why XML was never ment to replace traditional databases such as MS Access, MySQL, Oracle and so on.

The wrong is that you have used Data Islands which are supported ONLY in IE6 scince they are not part of any W3C specification, but only Microsft's. That's different from bilbob's problem though, scince the examples he gives use JS, which is more supported.