boen_robot
-
Posts
8,493 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Everything posted by boen_robot
-
JavaScript is totally not the answer. I can always turn my JavaScript and see the page OR look at the source code and copy the right URL.An .htaccess file could do it, but then again, a server side would be better.
-
Add something like: <input type="submit" value="Go"> in the form element to get a Submit button. You may have some JavaScript to activate it.Also, the form must have the action attribute to point to a JavaScript funcion or a server side file to process the form.
-
I'm not sure I want to know what the output of all this should look like .But I do see two small (yet significant) mistakes:1. The name of the variable is Feat and it's callers use $feat instead. That's wrong scince XML is case sencetive. Rename the variable to feat or rename the callers to $Feat.2. <xsl:value-of select=" ' ' " /> Is that even valid? If you are trying to select the current node, you could use a dot instead: <xsl:value-of select="." /> And if you want a space, you can just make a space instead of getting an emty value. An <xsl:value-of /> is suppose to contain an XPath expression or a variable.
-
The way I see it, you've already figured it all (kind'a weird that I'm not sure where are we going ). The only thing you need is the format-number() function: <xsl:value-of select="format-number(current(), 0000#) /> This should output the number before the "," (in our case: the current node) with zeroes and a digit. The zeroes would be replaced by the correct number if the value is higher then 9, so there are no worries here .
-
I don't get it... it works in the tryit editor but...when you save the code on the left as note.html: <html><head><script type="text/javascript">var xmlDocfunction loadXML(){//Code for IEif (window.ActiveXObject) { xmlDoc = new ActiveXObject("Microsoft.XMLDOM"); xmlDoc.async=false; xmlDoc.load("note.xml"); getmessage() }//Code for Mozillaelse if (document.implementation && document.implementation.createDocument) { xmlDoc=document.implementation.createDocument("","",null); xmlDoc.load("note.xml"); xmlDoc.onload=getmessage }else { alert('Your browser cannot handle this script'); }}function getmessage(){var x=xmlDoc.getElementsByTagName("note")document.write(x.item(0).getAttribute("time"))}</script></head><body onload="loadXML()"></body></html> And have this XML file in the same folder: <?xml version="1.0" encoding="ISO-8859-1"?><!-- Edited with XML Spy v2006 (http://www.altova.com) --><note time="12:03:46"> <to>Tove</to> <from>Jani</from> <heading>Reminder</heading> <body>Don't forget me this weekend!</body></note> It should work .
-
Summing the known spells is easy. Just use the sum() function: <xsl:value-of select="/node/node/sum(@name)" /> However, showing the node's name AND attribute would be a bit more difficult... perhaps variables? <xsl:variable name="node" select="node/local-name(current())" /><xsl:variable name="attribute-name" select="node/node/local-name(@*) /><xsl:variable name="name" select="node/node/@name" /><{$node} {$attribute-name}="{$name}">whatever</{$node}> I don't know if this would work... I'll try some other methods, but I think that variables are in some way the answer.
-
Well of course you won't get ads. Who is going to pay for a host with ads?As for the host itself. If it has unlimited bandwidth it would be worth it even if there isn't PHP. If there is: great!I once saw a host with PHP support and unlimited bandwidth for $15 per year. I forgot them though. At that time I wasn't aware how hard is to find such a host and I wasn't aware of PHP's full potencial. Not to mention that my knowledge of HTML at that time finished with the presentation of the <b> tag .And the space... for me, atleast 50MB thank you . After all, I know free hosts that offer more, though they don't have PHP support and they offer subdomains .
-
How about placing a transparent rectangle over the image (create a group and manipulate it's size and position to avoid emty places or unclickable parts) and apply the link ot it instead?
-
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.