boen_robot
-
Posts
8,493 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Everything posted by boen_robot
-
It is, it is !!!! The pop-up blocker is causing the script below, and the ad blocker is causing the script in the head section(or something like that)! I always though of "sym" as in "SYsteM" as if it was some statistic or something. Symantec didn't came into scence before I realized we both have NIS.I think this topic may be locked now, thank you .
-
click me
-
Even without seeing the file I think I could guess. The file you gave him was probably a PHP file which contained all the styling in it. What aspnetgy's favourite part is, is designing CSS templates (or I have got the wrong idea?) which is a whole lot easier and more fun to make then looking into a PHP file with all of the functionality AND styling all in one. This forum for example has PHP file and CSS file(s). The PHP files give the funcionality and the CSS file(s): the look. One could easily create a theme without any risk of hurting the functionality.
-
It might be best for w3schools if there's an RSS feed with such tips of the day stuff. You'll get notified AND you'll visit w3schools even more. After all, w3schools' income comces from sponsors who on the other hand want to see traffic .
-
It should be <xsl:output method="html" version="1.0" encoding="UTF-8" indent="yes"/> Look at your code again... you have set it to method="xml". You should use that(xml) only if you want the output to be another xml document which is then retransformed with another stylesheet.P.S. I made a long speech about the variable and yet you use the attribute. It seems I'm not as convincing as I was hoping for .
-
I think I see a pattern here... I have Norton AntiVirus, Norton Internet Security and Norton System Works 2006. In short: the full package. I have allowed each to analyze everything and make all corrections automatically but ask me if something is not certain (example: unknown virus). I made a full system scan yesterday just in case, and I got nothing, so my system too is clean. That's my first time I use NIS though. I don't know how it works and what it does. Could this be some addition of it? Anyway... the purpose of this code is what troubles me most.
-
Actually, it seems that any browser I use to open the page shows theese two scripts in the source code. However, if I open the exact same file in Dreamwaver or Notepad I don't see theese scripts. Note that theese files are executed on my own PC(localhost/filename.html or MyIP/filename.html) and the EXACT same file(not a copy of it!) is opened in the editor... that's really odd .[edit] I also noticed it at few other sites. In fact, THIS page has it. It all starts to get more and more odd . I'm starting to think that this is something modern browsers automatically add everywhere, but why? What is this for?[/edit]
-
Recently I started to notice some weird script appearing on few pages' codes. <script language="JavaScript"><!--var SymRealOnLoad;var SymRealOnUnload;function SymOnUnload(){ window.open = SymWinOpen; if(SymRealOnUnload != null) SymRealOnUnload();}function SymOnLoad(){ if(SymRealOnLoad != null) SymRealOnLoad(); window.open = SymRealWinOpen; SymRealOnUnload = window.onunload; window.onunload = SymOnUnload;}SymRealOnLoad = window.onload;window.onload = SymOnLoad;//--></script> What's most interesting in it is that it's placed AFTER the closing html tag. I'm a noob to JavaScript and I haven't got ANY idea of DOM stuff. Could anyone please explain me what is this code used for? Is it needed, etc.?Btw, the oddest thing. The latest beta of Opera 9 shows this csript on one of my pages that I keep on my computer. THAT script is used once in the after the closing <html> tag. There's also another script in the <head> though. <script language="JavaScript"><!--function SymError(){ return true;}window.onerror = SymError;var SymRealWinOpen = window.open;function SymWinOpen(url, name, attributes){ return (new Object());}window.open = SymWinOpen;//--></script> I haven't used even a single copy of any of those scripts. What's going on ?
-
Yes. .myclass:link and a.myclass:link are both valid and are both working properly in all browsers. I'm not sure for :link though. I would reccomend that you don't use it. Typing only a.myclass or .mylass Works the same way and I'm completely sure there aren't problems with it.What aspnetguy is suggesting means a link(<a>) inside any element with a class .myclass. It's not euivalent to the ones above, but it's still a good trick to know.
-
It is possible only if the class refers to a link. Or should I say "if you are aiming for maximum compatability". Firefox and Opera understand :hover (and other pseudo classes on that matter) everwhere in a document. IE6 however only understands it when it's on a link. Otherwise, it doesn't do anything about it.
-
Either eliminate the paragraphs' margins with CSS or write your text inside the code box of Dreamwaver where you can include true <br /> tags. I don't see other way around it.[edit] I haven't tryed pmdesign's idea though. It's so crazy that it might actually work [/edit]
-
Of course it is. You can use either <xsl:attribute> or <xsl:variable> to achieve this.Note: In theese examples I presume you want to use <type> as the naming of the link. You myst specify another path if this is not what should be displayed.xsl:attribute <a> <xsl:attribute name="href"> <xsl:value-of select="/food/info" /> </xsl:attribute> <xsl:value-of select="/food/type" /></a> <xsl:attribute> is an element which gives a certain attribute to the element it's contained in. In this case the attribute is called "href" which is what you need to create a link. The value of that attibute is determened by the content inside the <xsl:attribute> element. In this case, the value will be the URL itself. The other <xsl:value-of> outside the <xsl:attribute> is what you need for the text of the link.xsl:variable <xsl:variable name="link" select="/food/info" /><a href="{$link}"> <xsl:value-of select="/food/type" /></a> In this case you declare a variable before the anchor itself. Then by using the "$" you call on the variable by name. The "{" and "}" are placed because this is not supposed to be part of the URL but a calling to a variable. If you call a variable withing an XPath expression, you should avoid the brackets.I personally prefer the variable method (excuse the pun) for few very good reasons: Less code to look at. A variable could be used multiple times in a document. The <xsl:attribute>'s name and value must be typed everywhere that attribute is used. Much easier to see what is going to be outputed as a value and what as an attribute. A variable can hold everything, just as the <xsl:attribute> can. It could be used for everything. You just have to open the variable. Something like <xsl:variable name="linktext">This link is going to lead you to <xsl:value-of select="/food/info"></xsl:variable> Variables have many other different usages that may make the XSLT extremely flexible (by that I mean easy to edit). Their possibilities are hard to explain, and even more harder to handle if it gets crowded (one fails- everything fails). Using variables for simple tasks such as this one might make the struggle with a variables less painful on a later stage. Note on using multiple variables: The variables' declaring order must be exactly like the one each will first be called on a page. <xsl:variable name="value" select="/food/type" /><xsl:variable name="link" select="/food/info" /> That will produce an error if "link" is used before "value". It will, however, NOT produce an error if "value" is used at least once before "link".
-
While reading this I flipped my head sideways(like 45 degrees or so ) trying to figure out what is this about... so... what is it about? If you want to acces any kind an information of an ASP.NET file, isn't there some kind of server side include? The ASP(.NET) tutorials on w3schools seem pretty complete. How come this isn't covered?
-
Because it seems no one is turning attention to a very important post of mine, I'm goint to give a link to it here:http://w3schools.invisionzone.com/index.ph...indpost&p=11008Come on people! Repot to Microsoft!!! I hate it when I (or anyone else) give a link and no one turns it attention and later on curses the product (in this particular case: IE7) as if he/she didn't had a chance to suggest things about it .P.S. The previous product which the above statement refers to was WMP10. I was testing the Technical beta preview, and I suggested a lot of things to the development team along with another person (there were other suggestions of course but we were the only ones with over 400 posts ). I gave a link to the newsgroup at one forum, but when the final version was released, THEN the people started cursing instead of when I gave them the link . Why didn't they told me theese things earlyer so I could suggest them, or tell Microsoft directly? Huh... nevermind... just please... before you star critisising IE7, tell your opinipon to Microsoft first.
-
I think you should actually explain first to yourself and us what each part of the number means.20060213 is most probably 13 february 2006, but what about the rest? Anyhow, it would be best if you could actually check each part of the number. I don't know of such a script though. Perhaps someone else does...
-
Align the text in an element: text-align: center; Align the element itself: margin: 0 auto; That should work... and really... remove the "align: center".
-
If any of you have any suggestions for IE7 (and I bet you do have many), tell them in the IE7 beta 2 newsgroup.After that, I suggest you give a link to your post there, so all the rest of us could vote for your suggestion. Why? Microsft only turns attention to suggestions with the most votes .I personally am NOT going to suggest them anything because I know why they won't complete the CSS support in IE7. The article in the top link of this page explains it.... they don't want pages previously optimized for IE6 to suddenly crash due to the completely new specification, so they balance between new features and and compatability.I also can't allow myself to suggest anything else, scince I wan't able to get as detailed preview of IE7 as I hoped (see the story above).
-
What they mean is probably the fact that a too large stylesheet would make the page load slow, but then again, a single large XHTML file can also make the page load slow.Splitting the CSS into several ones won't help. What matters is the total amount of KBs that are transmitted at one time. Having two stylesheets still means the same amount of code, thus the same amount of KBs.
-
http://w3schools.invisionzone.com/index.php?showtopic=1912
-
Did you at least tryed to manually remove the txt and leave only the wml? If notepad makes this bug(cause if you have folloed the above path and it doesn't work, that is a bug) you can always make "raw" filename changes .
-
"li a:hover" means the hovered link(<a>) inside a list item(<li>), not a "<li a> tag(because such tag doesn't exist to begin with). You don't need to change anything in the XHTML in order for this to work, scince CSS is "smart" enough to find his way .
-
That's the reason why we all love CSS. With editing of one file you edit it all and make drastic changes .What we are doing is that we are changing the selector of the CSS which is suppose to be changing the list. Because IE only supports :hover over links we change the selector to select only links inside a list (li a:hover) instead of selecting the list items themselves(li:hover).What's the thing that is not making scence in all of this?
-
To save any king of "special" file in notepad, all you need to do is select it to show all files instead of *.txt files only and enter your file's name with a ".wml" suffix.No. You don't need something special for creating *.wml pages, but it is better if you have some (for tag colouring purposes for starters...).Most (all?) new phones support XHTML 1.0 strict. In fact, if you have heard of CSS media types, you have probably noticed "handled". This is used for handled devices such as PDAs and cell phones. If you use a specific stylesheet optimized for handled devices' needs and another for computer screens, your page(s) should look good in both kind of devices.You can use any server side to generate content. The client (in this case- cell phone) is not requred to have a support for that language. It all depends on the server (this applyes to all other king of devices as well).However, old phones (still used by a large number of people) support only WAP, so having both XHTML strict page optimized with a CSS for handled devices and WML pages is the best solution.Geocities, as far as I know accept all kinds of files but don't have any "special" support for them (such as server side scripting). A *.wml file is not a server side script, so there's no reason not to be supported. If it's not- there are always other free hosts you know. ALL of them support *.wml scince uploading a *.wml is equvalent to uploading a plain text file (the server doesn't treat it like anything special).
-
I actually didn't knew it's possible to have a template inside a template. Wow . As for what's your mistake... hm... I'm not sure But I think the template is called only if it's defined above the call-template element.
-
What's Omnimark?
