sbrownii
-
Posts
137 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by sbrownii
-
If you want to skip over an element... just include a comparison that checks if the selectedIndex is equal to the index of the element you want to skip... or the other way around, if you want to skip the element at the beginning, just make sure the selectedIndex is greater than that of the first element...
-
Sounds like a perfect job for server-side scripting - you probably only need to make use of the include() function in php.If server-side scripting isn't available you could use Javascript, but server-side is a better match for this job...
-
If you are wanting to dynamically change what content is being scrolled, then you would need some sort of scripting. If the content needs to be updated continuously while being viewed you need client-side scripting such as javascript.If you just need the content to be inserted when the page is sent to the user (and not changed again until they either reload the page or visit again), then you can use server side scripting such as php or asp.
-
I think you would do well to read the documentation for what you are using. You can configure Apache to use whatever directory you want as the root directory for your site.But the default would be somewhere inside the apache directory in a folder named "htdocs" as scot100 showed.i think xampp has "/XAMPP/htdocs" as the default DocumentRoot, so you should put your files in C:\Program Files\XAMPP\htdocsif your server won't start, it's probably because there is a problem with the config file. Just post again if you need help. Once you get the idea of how apache's httpd.conf file works, it will get easier...
-
you can only use a particular id once in an html document. Maybe you could use a class named "deprecated" instead of an id. Then you could loop through the elements of the document looking for matches to that class.if you want to just use the mouseover even like you were trying.. change it to thisjavascript function setTitle(element){ element.title="A deprecated element or attribute is one that has been outdated";} html The applet element was <span class="deprecated" onmouseover="setTitle(this)" title="">deprecated</span> in HTML 4.01. You could change the function to accept additional parameters so that it can work for more than one term. You could store definitions in an 2 dimensional array first column would be the term, second the definition... just make sure you change the function calls to match...if you use server-side scripting... you could just store the definition in a variable and print that variable into the title attribute of all the elements you need it in. If you need to make a change, just change the value of the variable.you could use style definitions to set the cursor, font color, background color, text-decoration, etc... to let the user know there is something different about that text...An alternative to using the mouseover would be to have the user click and get a popup that displays the definition in an easier to view format...
-
Is it your host that wacks your markup? Or is that how you wrote it?The link element referring to stylesheets should be in the <head> element. The <style> element should also be in the <head> element.I think you should search the net for "css 2 column layout" or "css 3 column layout" and start over as far as your layout goes. Using tables in this case makes no sense, because you are hardly using them for layout.It may take you longer, but I think it will be worth it for you to look through some good articles about getting the layout you want. It will make things much easier for you in the future.I would normally try to give you a fix for you problem, but I really think you should just redo the page.Some good pages to look at...http://www.glish.com/css/http://www.saila.com/usage/layouts/
-
If you want the comment to "stay" it will have to be stored somewhere. In order to store it you will need to use some server-side scripting.If you store it in a file, just print the comment to a file. To show it again later, you can use include(), or you can actually read from the file and print it out. If you want to read from the file, you could keep each comment on one line, then read the file a line at a time.You might find a few tutorials about making a guest book using php or asp or whatever language you are wanting to use.I would recommend following through some tutorials or examples of similar projects until you feel comfortable with the basic ideas being used. Then you can just adjust those ideas to match the project you are working on for allowing users to post comments on images...
-
xamppfiles for windows can be found hereIf you download the zip you can just unzip it and run it as is. If you like installers then get the installer...If you use linux... then you should be able to figure out how to download something from sourceforge.net ...By reading php files... do you mean to edit them? just use any text editor...Do you mean to view the result of the pages? just access them in your server - usually http://localhost
-
Did you not come across this site? http://www.w3schools.com/tags/default.aspor maybe this one for opera?http://www.blooberry.com/indexdot/html/index.htmlSupport for HTML elements that are part of the w3c standards is not a problem. Most problems come in the elements that Microsoft created for IE that aren't part of the standard.
-
If you are just trying to make it so people can leave comments about an image...There are a few ways to get it done. A not so great idea is to simply write the new "comments" to a file, so that the file contains all the comments for a particular image.A more common way is to store the comments in a database. Maybe the database table just has one field for the image name, one for the comment, another for author, another for date, etc... Your for adding comments, your server-side script can get data submitted from a form and insert it into a database. Then to display comments, your script just needs to query the database for all comments associated with the image name of the image you are displaying.Not sure if that is helpful at all...
-
Your html code has you nesting the "info" iframe inside the "content" iframe and not even closing one of them - probably just a mistake... That is your problem... IE forgives you ... FF doesn't...Just fix it so that you have to separate iframe elementsYour original code (formatted for easy viewing): <center> <iframe src="../months/blank.htm" name="calendar" frameborder="0" scrolling="auto" width="200" height="230"></center> <iframe src="../months/blank.htm" name="info" frameborder="0" scrolling="auto" width="200" height="230"> </iframe> How it should be: <center> <iframe src="../months/blank.htm" name="calendar" frameborder="0" scrolling="auto" width="200" height="230"> </iframe></center> <iframe src="../months/blank.htm" name="info" frameborder="0" scrolling="auto" width="200" height="230"> </iframe>
-
In php you can us isset() to check if a certain variable has been set.if the variable is called "gifted" and sent by post: if ( isset($_POST["gifted"]) ){ echo "gifted is set";} else { echo "gifted is not set";}
-
A link to the working (or in this case, not working) page would be helpful.If that isn't possible, please post code (javascript and php files)
-
I don't think it should be any problem. Just use unicode as your encoding if you plan to use many languages on a page.As far as javascript corrupting the strings, in the example posted above, Blue helped me realize about the only problem comes when the file is not encoded properly.
-
I am not sure what your expected result is...Do either of them look how you want?If so... which one?
-
The point is you used a hack that didn't even have effect.Like I said, no offense intended. When I first learned Javascript, I learned how to detect the browser and then use separate code for each browser. I used that for years, until I realized that in the case of modern browsers that support javascript, I could usually use techniques that worked equally well in all browsers, instead of writing separate code for each.I have come across many sites that still use the old ways and for no good reason - and half the time they forget to mantain one of the sets of code, so it doesn't work right in all browsers anyway! And the hardly ever define the script tags according to w3c standardsSince I've been looking at this forum, I've noticed many many people do hacks first. It leads to messy code (sometimes not so messy...) that often has no effect.I've seen lots of people having problems getting layouts to work in both browsers, and after looking at their code, was amazed how much code and how many hacks they used to achieve simple layouts.My point was that one of the places the hack was used had no effect... Just making an observation.BTW... I'm not saying never to use hacks...
-
IMHO...The best is to work with unicode.This works for all languages. I often use utf-8 charset. You just have to be sure to actually save your files as the same encoding.
-
Maybe my eyes are just bad... but I see problems with nested quotes in the javascript...change the opening and closing quotes of your document.write() to single quotes and you will be fine...
-
I guess my point is more that if the image is part of the actual content of the site, it is better to use image elements. It is mostly an issue of accessiblity. Think of how the page will render with text only. That is why the img element has the alt attribute. When you use a background image, there are tricks to have text but use style to replace the text wth a background image.You can read an old article here -> http://www.stopdesign.com/articles/replace_text/but pay attention to the notes, since that particular method doesn't actually work so well...
-
You need to send headers Before ANY output. This includes any html tags in the page, too, not just output directly from php.
-
when you mouseover the element it becomes hidden which means the mouse can't be over it, which means the mouseout event fires whichs shows the element, which the mouse is now over so the element is hidden, but then because the element is hidden the mouse isn't over it anymore so the mouseout event fires which.... and on... and on...sounds like a fun idea...
-
No offense intended in anyway, but this is an example of the result of too many articles about how to use hacks, instead of truly cross-browser css.
-
Please only make images into background images if they are actually background images. The image element is for displaying images. Defining backgrounds in css is for... well.. defining backgrounds...As real_illusions suggested, you can specify the height and width of the img element using either the properties of that element, or using css. This will establish the layout before the image even loads, and is actually the recommended practice.Be sure to add the "alt" attribute to the element for accessibility.
-
Amaya is a good editor to use if you aren't sure some of the standards. It has menu options that let you choose what DTD, charset, etc.. to specify for the document. Can save a lot of time (or a lot of copy/paste)
-
HEIL INACCESSIBILITY!