boen_robot

I think he refers to the JAVA applications which are normally embed inside pages with the <embed> tag, but scince it's deprecated, there should be another way.As fat as I know, the other way is the <object> tag, but I have no idea on how it should be adjusted for a JAVA application.

It's a W3C reccomendation to use background-color and color together to ensure a text is always visible. Simply add "color: black;" to body and "background-color:inherit;" to .mainfont.I'm not sure about the second waring though. I don't know to which CSS property it refers to. Place your CSS properties on different lines and you are sure to see.

Personally I height marketing terms. I think it would have had been much better if people could get a single tutorial in schools or universities on what marketing terms exist and what they include and then stop using them in their publications (like knowing "history", you know).Such terms include the above mentioned RIA, DHTML, AJAX and possibly some more .To me there are only pure languages and scripting/programming/graphic skills .The general languages that all involved in the web development should know are XHTML, CSS and XML. From then on, there are many different paths:Client side ways (in my point of view, that's the "light side of the force")- JavaScript, RSS, XSLT, and the other languages from the XML family.Server side ways (logically: "the dark side of the force")- PHP, ASP(.NET), JSP, CGI, Perl, Cold Fusion, etc.For a proffesional realization, one needs to know the basics, at least one client side way and at least one server side way. My personal choice currently in the client side realm is XSLT, along with some of the other XML languages, among which is RSS of cource. I still haven't chosen a server side way, simply because I'm teased of Cold Fusion, ASP.NET is somehow attractive and PHP... it has one major problem* for which currently I height it. And the others... they are even worse. However, in Bulgaria some people all refer to PHP as if it's the only way for server side scripting. Therefore, there aren't any ASP.NET and Cold Fusion hosts. I could always get an international host, but that could complicate thing I would otherwise be able to solve "personally".If by "web interface design" you meant graphical design, then what Skemcin suggest is truly it: Adobe Photoshop and perhaps a vector graphics editor such as Corel Draw or Adobe Illustrator.As for Flash. I personally height it and prefer SVG a lot more, scince I'm already fammiliar with XML based stuff. But I still have to admit that folks who decide "hey, let's build a web site" still refer to Flash as if it's the only option. Sad, but true.The best method for university plan in my opinion would be to have some kind of lecture to explain all of the language's possibilities, advantages and drawbacks and let the student decide for themselves. There's no right path TODAY. There will be once browsers support CSS3 completely along with all XML based languages. Until then: we can't decide what's the best path in the client side reaml at least. In the server side realm... never, scince they aren't browser dependant.*Doesn't have a built in support for executing XSLT transformations. Some kind of extensions are requred, but I don't know which and how to install. Even if I was able to install such extensions, most (all?) free PHP hosts would not bother installing extensions and payed ones... I have no idea, but I wouldn't like to take the risk.

What if you replace the XPath expression in the string-lenght() with the current() function? <xsl:if test="string-lenght(current())!=0"> Would this work?And yeah, a more concret example of imput and desired output would make things easier.

Come on people!!! Doesn't anyone have some kind of opinion about this, or is it just my bad luck with creating new topics ?!?!

I would generally use definition lists when I have a group of something and I want to declare it. Example: <dl><dt>Validators:</dt><dd><a href="http://validator.w3.org/check/referer">valid HTML</a></dd><dd><a href="http://jigsaw.w3.org/css-validator/check/referer">valid CSS</a><dd><dl> With a bit of styling, you could make the dt appear... let's say on the left, and the links right next to it (floated) and it's structually better then an ul.But for navigation it's definatly better to use ul, scince nested lists (submenus) would structually and visually (without CSS) be better.I know we haven't mentioned anything about "ol"s yet, but just to avoid later asking, they are not good, because you can't know the order in which a user should look at your site. Or should I say it's not wise to do so.

Before getting deep into your XSLT, I think I should try to give you a basic XPath way to navigate: <xsl:for-each select="//para"> <xsl:if test="para!= ' ' "> <para> <xsl:value-of select="para" /> </para> </xsl:if></xsl:for-each> This simply means that if para has any content, it would be outputted inside a para element, otherwise it's skiped. This is a simple kind of filter which I haven't tested, but I have seen it before in other XSLT stylesheets, so it should work.I'm not completely sure if that was what you were asking for, so if not, I guess I'll take it deeper .

Of course there is. You are completely free to adjust the XHTML inside. It won't give any other results: <td class="data"> <xsl:for-each select="CPhone"> <xsl:value-of select="current()" /><br /> </xsl:for-each> </td>

Not to mention that their HTML is ancient and you are suppose to use XHTML, right?Use big sites to see how NOT to do the things. Use smaller but standart compilant sites to see how you SHOULD do the things. See aspnetguy's site (spatterdesign) for instance .

Maybe if you dwaw a prototype website on a paper or something and try achieving each of it's components one by one? Practise is the key I mean...

LOL. An XSLT database (practically). Bad idea... nevermind...In truth, XSLT only visualises what you want, but it doesn't actually give the disired output. You need some server side scripting language or a custom made C++ application that would generate the REAL source code when the file is accesed. I mean that for example: <p> <xsl:variable name="link" select="link" /> <a href="{$link}>some text</a></p> Is displayed as if it was: <p><a href="whatever the value of 'link' is">some text</a></p> but when browsers and other languages refer to the XML or XSLT, they read their respective codes, not the output. In order for the browser or application to read the output, the output must fisrt be generated with some kind of parser.A note to keep in mind of using multiple variables is that they must be used in the order they are declared. <xsl:variable name="link" select="link" /><xsl:variable name="value" select="value" /> This will give you an error if you use value before link, but it won't give an error if link is used at least once before value.So yes, I personally think it's better to declare all the variables at the top, as long as you know their order.As for how to get a value of a variable in a node. No. It's not like you did it. It's more simple : <stringvalue name="wounds"><xsl:value-of select="$wounds" /></stringvalue>

First stop: really interesting use of XML and XSLT. Nice . I think the first quote in my signature actually refers to projects like this one .Khm... anyway... looking at the GUI program, it doesn't have a node with name "name", but it does have an attribute with that name. If all other of your XPath expressions are correct, the answer should be: <node name="charsheet"> <node> <xsl:attribute name="name"> <xsl:value-of select="@name"/> </xsl:attribute> Notice the "@" before the name. It's an XPath selector for attributes.By the way, there's another method of using attributes, which I prefer. If you have some spare time, experiment with it: <node name="charsheet"> <xsl:variable name="NAME" select="@name" /> <node name="{$NAME}"> It takes less code, easier to read, and can be used multiple times over as long as it's withing the element it's used in (in our case: multiple times inside the <node name="charset"> element.

Or a JavaScript that would hide the desired images and show them when appropriate links/buttons are here, simillarly to scripts used for tree-like menus.However, such thing would let all images download, though the shown will be with priority, so a server side script is truly reccomended.

li {list-style: I don't know what should be here}?

There's no "must"s in XML and related technologies. However, there's always "better" possibilities, when server side scripting is avaiable.Server side script however doesn't refer to C#. It refers only to languages such as:PHP, ASP(.NET), Cold Fusion, Jigsaw (a.k.a. CGI), JSP, Perl, etc.Web services that would use XML would be any, which doesn't contact with a huge kind of database. However, if you want interactivity, you'll have to use at least JavaScript.You can also use XML to carry the data for the site and use XSLT to tranform the XML into XHTML. But that doesn't allow interactivity again.Conclusion: There's a need for SOME language. Which one is highly up to you.

Well, again I must say, that only the main site... the XHTML site must be with SSL encrypted protocol. The SSL allows every submitted information to be delivered to the end point, without a risk of being viewed by phishers (people who monitor traffic on certain sites, so they can steal a user's details).There's no need for encrypting the WAP site, scince payments are done to the operator, not by submitting some info to the site. SSL encryption is requred only when there is info to be sent. Yeah, the operator should know how to proceed with the "link billing" and all.Infact, it's NOT reccomended to have such encryption on WAP site, scince some users have old phones, which don't support this kind of encryption. All modern computer browsers do support this encryption properly and as said above, most users are smart enough not to buy from a site without it.As for "how", here's a good kind of plan:1. Look for a coder to build a WEB site. By the way, ask for a tableless designs and CSS for mobile phones. This may cost you extra, but XHTML enabled mobile phones would be able to browse through the main site, bringing you extra possibilities. Of cource, that's all optional, scince you'll have a WAP site anyway.2. Look for host offers with options for SSL/HTTPS protocol. If they allow you to have both HTTP and HTTPS pages, it's the best. Otherwise, you'll need to support two kinds of (sub)domains (that's what I meant by saying that encrypting the protocol is only a "detail").3. Speak with the operators for the billing stuff and all.4. Build and fill the WAP site.5. Look for a SSL certificate issuer and get an SSL certificate. The most trusted one is VerySign though. You need it for proper SSL "trust" or so to say. You shouldn't get it before the WAP site is built, because before issueing, they check the organization's activities. Having a working WAP site would make it easier for them to issue you the certificate.6. Ask the coder to add E-Commerce system to the XHTML site and fill it's content.7. Import the certificate to your XHTML section of the site. Keep the WAP pages on HTTP. Ask the host or the coder for support. They are sure to know the tricks for this.Done.Most of the details in theese steps have people who know better how to deal with them. You are practically only requred to manage the whole thing.Cheers.

I think the question of the Poll is clear enough. Which one of the two vector graphic animations you prefer and why?I personally like SVG for quite a few reasons:1. Support is no longer something to compare. Adobe SVG viewer helps IE6 and Firefox and it could be installed on Opera. Opera 9 and Firefox have some native support for it too.2. It's text based, meaning there's not a "must" for a single commercial editor to stick with.3. It could be binded with XML data, making it very flexible.4. A lot of phones are actually now supporting SVG Tiny, though they are not as cheap and popular yet. Still: using the same thing for both Phones and computer screens sounds attractive.5. No need to learn additional language for scripting. JavaScript could be used inside SVG to give it all requred functionality which can't be delivered directly by SVG.

I have no idea what theese coding camps are actually. Those things you wrote sound more like kinds of mobile networks, which is quite different.If users get sticked by security issues, they won't give you a second chance. If you are going to make a credit card payment, it HAS to include an SSL encryption from the first time. It's not the "XHTML" which has to be secure. It's the HTTP protocol, but that's just a detail. A phone payment won't requre this though, scince everything is done inside the operator's system.By the way, I don't get it.... how can you possibly organize a payment that would not requre a computer at all? How can anyone preview the thing he/she wants properly? And most importantly: How are they going to pay?There are only 2 ways I can think of:1. SMS payment. A user memorizes some code and types it as an SMS to an appropriate number for the appropriate price.2. Traffic payment. The payment is done when the user clicks on a download button and his internet bill gets extra charged with the appropriate price.In both ways: you need operator's support. The more- the better.If there was one central operator (the same way there's ICANN for the world wide web), there would be ONLY mobile phone payments .

The HTML tutorial on W3Schools is based on HTML 4.01, so this means you already know it. Move to XHTML and CSS now. Most of the advanced part in the HTML tutorial doesn't contain anything useful.

The codediv.p {CSS properties here} Will apply the CSS properties to all divs in the (X)HTML who look like this: <div class="p">Some content to be styled</div><div>But this content won't, because it doesn't have a class p.</div> And a code in the CSS which looks like this: div p {CSS properties here} Will apply the styles to all p elements inside div ones, like this: <p>This content is not going to be styled.</p><div>This content is not be styled either, but <p>this one will, because this p element is inside a div.</p><div> Following the above logic, the code: div, p {CSS properties here} Will style both div and p elements. Example: <p>This element is going to be styled</p><div>And this one too</div>

That's not exactly right. Here yo go:div.p = styles every div with class p.div p = styles all p's contained within a div only.div, p = styles all div and p's

If you mean that the systax of XML is colored, well... yes it is. They already told you XML is different then XHTML. And XML files without stylesheets applyed to them leave to the browser to decide how to make them look. IE automatically applyes it's systax coloring for previewing purposes, but it doesn't allow you to edit the source directly and (as you have noticed) it hides some parts (such as the doctype).

Why don't you group all the things in the XML file and access them separatly. Example: <people><person><fname>Allan</fname><lname>Rogers</lname></person><person><fname>Madonna</fname></person><person><fname>Peter</fname><lname>Smith</lname></person></people>

True, I admit this is a very "boring like" system. It's normal that you don't care that much for security, but a large varaity of users does, so you should compile with their needs.An SMS payment did came into my mind, however, it would probably cover only one country (Norway?) and perhaps with later investments, one or two more countries. I don't think it would work as international kind of payment. If you could make an international SMS payment system that would be supported by all mobile operators and would be on internationally acceptable prizes, you'll be a world hit.

Well, the easiest way I can think of is to archive (zip) your videos, so the users would be forced to download them first. If you want them to save raw movies, then... I don't think there's a way. It's all user's settings. At least, I think it's only that though.