boen_robot

CSS isn't and it never was the future of XML styling. Only XSLT has the power to make the br tag a true line break. As for a line break with CSS, I think it could be done with "display: block" but even if I'm wrong, it still doesn't matter. XSLT forever .

PNG can't be animated, but W3C had made an animated module of it called MNG. It shares all image extras with PNG and can ONLY be animated just as PNG can ONLY be a still image. MNG however is not so widely supported yet, both by browsers and editors, so the safest way to go for now is still an animated gif.

There are many hosts that support server side scripting. In fact, every paid host supoorts some language. If the host supports MySQL this means that you can also get a database with your hosting plan. Of cource PHP is not the only solution to manipulate database and dynamical content. There are ASP(.NET), JSP, ColdFusion and many others perhaps(though they are not as popular as theese here).PHP on the other hand is most widely supported. Scince you can't be sure about your host, it's recommended to use PHP, but if you are serious about the game and have found a good host that supports other languages, there's no reason why not to write the game in that other language.

He means that using server side scripting eliminates the need of frames. So no- You don't need to put your stuff in frames. Learning a server side scripting language(PHP, ASP(.NET), ColdFusion, JSP, etc.) is more than enough for placing document in one another.By the way, try to avoid using tables as well. They are recommended only for tabular data, not for layout purposes. For layout you should try to use divs in combination with CSS for the presentation purposes. Don't look at W3Schools for example in this thing. They know they are not giving a good example of a clean layout, but they are focusing more on writing the tutorials, rather then the design of the site(I one saw kaijim's post regarding this topic).

An SSL protocol is not something you "include" in your site. If an https page is included in a frame or something, the user can never be sure if the whole thing is "valid" scince he/she won't be able to see the lock on the browser. Why? Because the browser can only see the status of the current page. The one which holds the frame, not the pages inside the frames.The SSL protocol it something your host must provide you with. To provide you with such a thing you would also have to pay for an SSL certificate to him or a third party issuer. If the host supports SSL he should provide you with an interface with which you can apply the certificate to the site.

IDs are a thing that you may use only one in a page per elememt. There can't be two elements called "green:yes" in a single XHTML. I also echo mreddy that ":" are probably reserved for pseudo classes though I'm not sure.However, I think you might be able to to the following: h1#green:yes {color: green}p#green:yes {color: green} If possible, tell the person who made the XHTML document to make theese IDs a single class AND remove the ":" from the ID and class names just in case.

Isn't it most convient to store the sctipt(s) in external file(s) and reference them with the "src" attribute inside the pages themselves(not the frameset that is)?

The best thing to do is to start the .aspx file which will reference the XML and the XSLT(s). It will execute the transformation then. In other words: instead of seeing the source XML and/or XSLT, the end-user will see the XHTML. This is really useful, scince Opera 8 and below, doesn't support XML.An ASP file that should execute the transformation can be found here. As said in the above post, you may execute several XSLTs in one ASP file. Then just create the ASP script itself. When the .aspx file is executed, it will transform the first XSLT, make the ASP script and continue with transforming the second XSLT and so on.Example: <%'Load XMLset xml = Server.CreateObject("Microsoft.XMLDOM")xml.async = falsexml.load(Server.MapPath("cdcatalog.xml"))'Load XSLset xsl = Server.CreateObject("Microsoft.XMLDOM")xsl.async = falsexsl.load(Server.MapPath("cdcatalogHEADER.xsl"))'Transform fileResponse.Write(xml.transformNode(xsl))%>If you want, you can place pure XHTML content here...<%'The ASP.NET content goes here%>...or here.<%'Load XMLset xml = Server.CreateObject("Microsoft.XMLDOM")xml.async = falsexml.load(Server.MapPath("cdcatalog.xml"))'Load XSLset xsl = Server.CreateObject("Microsoft.XMLDOM")xsl.async = falsexsl.load(Server.MapPath("cdcatalogFOOTER.xsl"))'Transform fileResponse.Write(xml.transformNode(xsl))%>

Instead of using ASP.NET inside XSLT you can do the opposite: use XSLT inside ASP.NET. How? By executing two or more XSLTs with ASP.NET and put the actual ASP.NET script(s) between.

Personally I would like it, but I think the forum will be flooded with advertisments then. A much better thig would be for everyone to place a link for their site in their signature(as they are actually doing currently) instead of making a new topic for each released site. Another thing might be a separated topic about this in the General forum, but something tells me it won't have a success.

Camtasia Studio is truly THE best tool out there and THE easiest. I think there's a trial version of it, so you can just record everything before it expires.Macromedia has an application which uses Flash in order to record and possibly interact with the user. The program is known as Captivate. By "interaction" we mean to make the end-user click on a certain area of the video so something could happen. It's a good thing, but it's not neccesarry you know .By the way, yaniv, would you mind showing us your company's site and possibly the application itself .

Using relative values is usually a good thing but if you are sure you want to disable your page from resizing I would suggest using absolute values, or to be more exact: Pixels.Like this: <span style="font-zise: 14px">The text with 14px size</span>

A WUSIWYG editor can never be close to relative positioning. Everything always varies afterall. I happen to have made a page that looks almost perfectly in Dreamwaver though. The reason is that it's a strict page. Therefore if it doesn't look good in dreamwaver it doesn't look good anywhere. The way I fixed it was described in http://www.quirksmode.com. Just add "overflow: hidden" and "height: 100%" to all floated DIVs.

Hello igourav_me,Please stop saying "Hello *username*, thanks for your reply". It's really annoying. Seriously... we aren't business men or some big corporation here after all. I know you are trying to be polite but still...Anyway. In order to process a form you would need SOME kind of language. What you use is totally up to you. You may use client side scripting (JavaScript, VBScript, etc.) or server side scripting (PHP, ASP(.NET), JSP, ColdFusion, etc.). There isn't a best language. It's all coming from the environment.If your host doesn't support server side scripting you'll have to use JavaScript or VBScript. The better choise from theese two is definetly JavaScript though scince it's more popular meaning that if you want to do something it's more likely that someone will help you.If your host does support a server sode scripting you'll have to see which one and learn the appropriate language. If it has a support for more than one server side I would recommend using the one that is not PHP unless you aren't sure if you're going to stay with that host.In anyways HTML and/or CSS alone are too simple for what you are asking. Instead of posting a new topic every time you want to do something "dynamical" I suggest you learn some of those languages yourself.

Excuse me for the stupid question, but with what exactly you need help with?

Everything you said is true besides the stylesheet thing. Every modern phone which has support for XHTML also has support for CSS(1...I'm not sure about 2 though). Infact if you look at the CSS tutorial on w3schools you'll see it's possible to make another stylesheet especially for mobile phones OR keep everything in a single stylesheet and separate the PC presentation and the Cell phone presentation like this: @media screen---CSS for PCs goes here---@media handheld---CSS for Mobile phones goes here--- Using relative values is also something to consider. The page will automatically be resized for the requred device if relative values are used.

As far as I know XML and XSLT files must be fully loaded before any actions are executed.If you execute them on the client, this means less load to the server but more time for the client scince he/she has to download the whole files first.If you execute the transformations on the server, this should mean that there won't be any time needed for downloading scince the files are there. However, this would mean more load to the server. Using many ASP.NET files should result in approximately the same performance as with XSLT on the server I think.Conclusion=> If your server can handle a huge load, using XSLT on server shouldn't mean less performace but it DOES mean better organization.Please note: I am not aware of how server side performs with XSLTs and I'm not fully aware of XSLT's performance as well. My opinions are only considerations of my own simple logical thinking(excluding the fact that XML files must be fully loaded before they are processed).

Make it a conditional statement. Something like: <xsl:for-each select="Contact"><xsl:if test="id"><tr><td><xsl:value-of select="id"/></td><td><xsl:value-of select="Name"/></td></tr></xsl:if></xsl:for-each> This should make the tr and td only if an ID element exist. Otherwise it will do nothing.

Using relative sizes probably. In other words: percentage values(like 100%) I think.

Your XML looks horrible ! I'm sorry, but I won't waste time understanding it. Instead I'll just give you an XPath expression that should do the trick . You (or someone else) decide where it's place should be: //E1EDL20/E1EDL24[POSNR ≡ 000010 or POSNR ≡ 000020] This is true if the POSNR is 000010 or 000020. False if anything else.Note: True means selected and False means not selcted.

First stop: This is an XSLT question and there is another forum for it.As for the question itself. As far as I know XSLT only selects something if it exist. You may apply conditional statements for the XSLT to do something if the attribute doesn't exist and tell it to do nothing if it does. In other words: reverse the effect.Example(an altered version of a test file I have used here): <?xml version="1.0" encoding="windows-1251"?><!-- DWXMLSource="test.xml" --><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"><xsl:output method="html" encoding="windows-1251"/><xsl:template match="/site/images"> <xsl:for-each select="image"> <xsl:choose> <xsl:when test="@id"> <xsl:variable name="location" select="location" /> <xsl:variable name="description" select="description" /> <img src="{$location}" alt="{$description}" /><br /> </xsl:when> <xsl:otherwise> <xsl:text>This is a text that will be shown if the image doesn't have an ID. If you remove this XSLT text element, the XSLT won't do anything if the image doesn't have an ID. The same way you may make the XSLT do something only if the image doesn't have an ID.</xsl:text><br /> </xsl:otherwise> </xsl:choose> </xsl:for-each></xsl:template></xsl:stylesheet>

Excuse me for the noobish question, but what's "Xor"?

The reason for this is that google have cached yor page in a moment where you had such a message. In order to "fix" this I suggest you sumbit your site to google the straight way:http://www.google.com/addurl/?continue=/addurland/or remove yourself from their database(see the link on the bottom of the page above.

Try setting the height to more than 100%. By the way, you would need to remove the "td" in "td.InfoTd" in order for the settings to take effect. You used divs in your page after all, right?

Exactly what would you need the XML for? Storing data about the sites? Hm... this is definetly a bad idea. An XML is fully loaded in the parser before any transormations are executed. If you keep huge amounts of such data in XML, this would cause serious performance problems to your search engine. A database like SQL is much better solution for this. You could however use XML to build the interface though. And the engine itself can't be contsructed with XML and related stuff. You would need a server side scripting language(PHP, ASP(.NET), ColdFusion, etc.).