 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussion GroupsGeneralPHPASPPerlColdFusionFlashHTML, CSS, ScriptsBrowsers |
Webmaster Forum / HTML, CSS, Scripts / CSS / March 2006aligning with css
Hi, I have no clue. - I want to align the red, green, blue boxes in one line - red,green,blue must be 45px high - red (center) must be as wide as possible - yellow must start exactly below the line - yellow must be left aligned with red one. Please, please help! <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//DE"> <html> <head> <style> /* MAIN AREA*/ .X1{ display:inline; background-color: green; margin-left: 32px; width: 12px; height: 45px; } .X2{ display:inline; background-color: red; width: 90%; height: 45px; } .X3{ display:inline; background-color: blue; width: 12px; height: 45px; } .Y2{ width:90%; background-color: yellow; margin-top: 45px; margin-left: 44px; } </style> </head> <body> <div class="X1"> </div> <div class="X2">Header</div> <div class="X3"> </div> <div class="Y2">Her is some long text</div> </body></html>  Signature-Gernot int main(int argc, char** argv) {printf ("%silto%c%cf%cgl%ssic%ccom%c", "ma", 58, 'g', 64, "ba", 46, 10);} ________________________________________ Looking for a good game? Do it yourself! GLBasic - you can do www.GLBasic.com >I have no clue. Here are a few: Don't multi post. Don't upload code, upload a minimised example using real content. SignatureSpartanicus >>I have no clue. > > Here are a few: > > Don't multi post. I was told that this NG handles CSS, so I posted here, knowing what the other answer would be. > Don't upload code, upload a minimised example using real content. Take a look at my code - it _is_ the minimum required code for my problem. Any idea about my problem? >>> I have no clue. >> Here are a few: [quoted text clipped - 3 lines] > I was told that this NG handles CSS, so I posted here, knowing what > the other answer would be. <snip> What's that to do with this? Do you even have any idea what multipost means? http://smjg.port5.com/faqs/usenet/xpost.html http://www.cs.tut.fi/~jkorpela/usenet/xpost.html Stewart. Signature-----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS/M d- s:-@ C++@ a->--- UB@ P+ L E@ W++@ N+++ o K-@ w++@ O? M V? PS- PE- Y? PGP- t- 5? X? R b DI? D G e++>++++ h-- r-- !y ------END GEEK CODE BLOCK------ My e-mail is valid but not my primary mailbox. Please keep replies on the 'group where everyone may benefit. >> I have no clue. > > Here are a few: > > Don't multi post. > Don't upload code, upload a minimised example using real content. How can one upload an example of this kind of thing without uploading code? Stewart. Signature-----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS/M d- s:-@ C++@ a->--- UB@ P+ L E@ W++@ N+++ o K-@ w++@ O? M V? PS- PE- Y? PGP- t- 5? X? R b DI? D G e++>++++ h-- r-- !y ------END GEEK CODE BLOCK------ My e-mail is valid but not my primary mailbox. Please keep replies on the 'group where everyone may benefit. >>> I have no clue. >> [quoted text clipped - 5 lines] > How can one upload an example of this kind of thing without uploading > code? More liberally translated: Don't post code here, upload a minimised example using real content to your web server, then post the URL here. Signature-bts -Warning: I brake for lawn deer <snip> > More liberally translated: > > Don't post code here, upload a minimised example using real content to > your web server, then post the URL here. But why? Have you weighed up the pros and cons of the two approaches? Stewart. Signature-----BEGIN META GEEK CODE BLOCK----- Version: 1 gc ------END META GEEK CODE BLOCK------ My e-mail is valid but not my primary mailbox. Please keep replies on the 'group where everyone may benefit. > <snip> >> More liberally translated: [quoted text clipped - 3 lines] > > But why? Have you Have I personally? > weighed up the pros and cons of the two approaches? Yes. Why would I want to wade through dozens (sometimes people post hundreds) of lines of HTML/CSS? Maybe a long line will wrap in my newsreader, causing an error. In order to test someone's problem, I would have to copy the code, save it as an HTML file, possibly create a separate style sheet file, load it on my development PC's web server, and view it in a browser just to begin to see what is going on. And everyone reading the post would have to do the same. Then perhaps we discover that the OP did not include everything in the 'code post'. Or hand-typed with errors. This happens all the time. If you place your sample on your own web server, we have instant access to a full example, with your code. For CSS questions, I can then even play with it live using my browser (Firefox/Web Developer's Toolbar). Signature-bts -Warning: I brake for lawn deer >> <snip> >>> More liberally translated: [quoted text clipped - 8 lines] > > Yes. So why have you, in what follows, addressed neither a single pro of posting code here nor a single con of uploading code to the WWW and posting a URL here? > Why would I want to wade through dozens (sometimes people post > hundreds) of lines of HTML/CSS? Maybe a long line will wrap in my > newsreader, causing an error. It may be true that posting hundreds of lines of code to a newsgroup isn't a good idea. But whether code is posted on a newsgroup or uploaded to the web has little effect AFAICT on the undesirability of wading through hundreds of lines of it. If it's been minimised efficiently, then unless it's a particularly complex problem, it probably won't be more than a dozen or two lines. And there's still the option of uploading it to the web for these more complex problems. > In order to test someone's problem, I would have to copy the code, save > it as an HTML file, possibly create a separate style sheet file, load it > on my development PC's web server, and view it in a browser just to > begin to see what is going on. I had no idea that Firefox didn't allow you to browse pages locally on your hard disk without a web server. Every browser I've ever used does. > And everyone reading the post would have to do the same. And I can't believe that you've got as far as you have (judging by some of your posts) and yet remained in your world of delusion that not a single web browser ever invented allows you to browse on the local filesystem. > Then perhaps we discover that the OP did not include everything in the > 'code post'. Or hand-typed with errors. This happens all the time. > > If you place your sample on your own web server, we have instant access > to a full example, with your code. For CSS questions, I can then even > play with it live using my browser (Firefox/Web Developer's Toolbar). Try telling people who use dial-up connections (yes, such people still exist before you ask) and read newsgroups offline that they have "instant" access. You've mentioned a few bad habits of some people who post code samples on newsgroups: - posting very long code samples - including long lines that will break in some newsreaders - not including all relevant code in the sample - deciding by some obscure thought process that hand-copying is superior to the electronic copy and paste approach Just because some people commit these sins doesn't mean that posting code samples on newsgroups is a sin. Do you avoid painkillers at all costs, just because some silly people overdose on them? On the contrary, reducing code to a minimal example small enough to post on a newsgroup has benefits in itself. It makes it easier for everyone on the newsgroup to find where the problem is. Occasionally, it may even help the person who's about to post here to find the cause of the problem him/herself and thereby not have to post here after all. A good technique is to reduce the code one step at a time, and at each step to test the code to see if it still reproduces the problem. See also http://tinyurl.com/ru8g3 (Google cached page - the live page seems to be down at the mo) Stewart. Signature-----BEGIN META GEEK CODE BLOCK----- Version: 1 gc ------END META GEEK CODE BLOCK------ My e-mail is valid but not my primary mailbox. Please keep replies on the 'group where everyone may benefit. > I had no idea that Firefox didn't allow you to browse pages locally on > your hard disk without a web server. Every browser I've ever used does. It does. But that won't show if the problem is due to a Web server mis-configuration or, for instance, a mis-stated path. I'd much rather see the example and/or actual page in its environment. SignatureEd Mullen http://edmullen.net http://mozilla.edmullen.net http://abington.edmullen.net >> I had no idea that Firefox didn't allow you to browse pages locally on >> your hard disk without a web server. Every browser I've ever used does. > > It does. But that won't show if the problem is due to a Web server > mis-configuration or, for instance, a mis-stated path. I'd much rather > see the example and/or actual page in its environment. This 'group is about CSS, isn't it? Not about how to configure a web server. IMHO the average person is likely to test trimmed-down examples locally, not just on a web server. Stewart. Signature-----BEGIN META GEEK CODE BLOCK----- Version: 1 gc ------END META GEEK CODE BLOCK------ My e-mail is valid but not my primary mailbox. Please keep replies on the 'group where everyone may benefit. >>> I had no idea that Firefox didn't allow you to browse pages >>> locally on your hard disk without a web server. Every browser [quoted text clipped - 6 lines] > This 'group is about CSS, isn't it? Not about how to configure a > web server. It's about CSS on the WWW, not on your computer. > IMHO the average person is likely to test trimmed-down examples > locally, not just on a web server. Then the average person isn't seeing it how it will actually look on the web server either. Many problems don't appear until a page is actually on line. I guess you've never heard the saying "When in Rome, do as the Romans do"? You're not the only one to come into a newsgroup and think you are going to change years of convention. It didn't work for them and its not going to work for you. What will happen if you continue going against convention is you'll be killfiled by those you are asking for help thereby getting you no help at all. By the lack of responses, I'd guess some have already got you in the kf. Beauregard gave you several reasons for this convention and you ignored them all by saying "I don't do that." No, maybe not, but many do; thus the convention of requesting URLs instead of poring through code that may be meaningless anyway. SignatureStan McCann, "Uncle Pirate" http://stanmccann.us/ Webmaster, NMSU at Alamogordo http://alamo.nmsu.edu/ Now blocking Google Grouper posts and replies. http://blinkynet.net/comp/uip5.html <snip> >> This 'group is about CSS, isn't it? Not about how to configure a >> web server. > > It's about CSS on the WWW, not on your computer. In all my life, I'd never imagined that they were two different languages. Please enlighten me. What's the difference? >> IMHO the average person is likely to test trimmed-down examples >> locally, not just on a web server. > > Then the average person isn't seeing it how it will actually look on > the web server either. Many problems don't appear until a page is > actually on line. I can think of several examples, but that's pretty much irrelevant. _If_ the problem cannot be reproduced on the local filesystem, _then_ it goes without saying that it's foolish to expect anybody to reproduce it from code posted on a newsgroup. If OTOH the problem manifests equally when testing locally, as is often the case, then it should be harmless to post the code to the newsgroup, and then anyone can easily c&p the code into a text editor in order to test and even experiment with it. In order to test fixes to the problem before posting, people will need to make their own copies of the code anyway. Uploading code to the web in order to illustrate the problem is certainly no panacea. Test cases will often not be uploaded to the same URL where the live page is going to be, especially if doing so would damage the existing site while an improvement is in progress. This difference can in itself lead to problems that will appear in the testcase but not in the live version when it comes, or vice versa. Yet another possibility is that the testcase and the live site don't strictly coincide in the human errors that were committed in the very process of uploading. Moreover, what if the person with the problem doesn't even _have_ a web hosting account? Maybe someone is working for weeks or months on composing the site before putting it online, and plans to cross the bridge of finding a host when he/she gets to it. Or maybe someone is writing HTML pages not for the WWW, but for an intranet, to distribute on a CD or other medium, or for software documentation bundled with the software itself. He/she/it is thus faced with a choice of three evils: (a) to sign up for a paid-for hosting account earlier than planned, at potentially higher cost (how significant this is will depend on how long it's likely to be before the real site goes live) (b) sign up for a free hosting account, and risk (considering the (general) lower reliability of free hosts) the server being down at the time somebody is trying to help or the adverts that the host inflicts screwing things up (c) putting up with the people on these newsgroups who refuse to test code that's posted on them, instead pontificating their biased arguments against this practice > I guess you've never heard the saying "When in Rome, do as the Romans > do"? You're not the only one to come into a newsgroup and think you > are going to change years of convention. It didn't work for them and > its not going to work for you. Try telling that to the people behind the phasing out of Latin being taught in British schools. > What will happen if you continue going against convention is you'll be > killfiled by those you are asking for help thereby getting you no help > at all. By the lack of responses, I'd guess some have already got you > in the kf. If some people can't handle such constructive debate, that's their problem. > Beauregard gave you several reasons for this convention and you ignored > them all by saying "I don't do that." No I didn't. I tried to make the argument fairer by (a) telling the other side of the story (b) pointing out places where the reasoning falls apart There are indeed good reasons to do what Beauregard is trying to promote, but that doesn't mean that it should be a convention. There doesn't even need to be a convention at all. People should be allowed to choose whichever practice both works and suits them best. > No, maybe not, but many do; thus the convention of requesting URLs > instead of poring through code that may be meaningless anyway. Just because _some_ people make mistakes while doing X doesn't mean that X is universally a wrong course of action. If it were, then it would be wrong even to write web pages. And like I said, do you avoid painkillers at all costs, just because some silly people overdose on them? Everybody, please stop over-generalising. Stewart. Signature-----BEGIN META GEEK CODE BLOCK----- Version: 1 gc ------END META GEEK CODE BLOCK------ My e-mail is valid but not my primary mailbox. Please keep replies on the 'group where everyone may benefit. >> It's about CSS on the WWW, not on your computer. > > In all my life, I'd never imagined that they were two different > languages. Please enlighten me. What's the difference? A trivial example: A webserver might send your stylesheets with type "text/plain" or "text/html" or "text/css;charset=utf-7", which are all wrong for this purpose. You cannot solve such a problem - cannot even see it - when you only supply a few lines of source text. SignatureAll free men, wherever they may live, are citizens of Denmark. And therefore, as a free man, I take pride in the words "Jeg er dansker!" >>> It's about CSS on the WWW, not on your computer. >> In all my life, I'd never imagined that they were two different [quoted text clipped - 4 lines] > or "text/html" or "text/css;charset=utf-7", which are all > wrong for this purpose. Yes, that's quite a straightforward example. Another is transferring from a case-insensitive to a case-sensitive file system. But these aren't aspects of the CSS language itself. > You cannot solve such a problem - cannot even see it - when you only > supply a few lines of source text. But if the poster has already established that no problem of this nature is occurring, e.g. by testing locally, then it doesn't matter in this respect. Stewart. Signature-----BEGIN META GEEK CODE BLOCK----- Version: 1 gc ------END META GEEK CODE BLOCK------ My e-mail is valid but not my primary mailbox. Please keep replies on the 'group where everyone may benefit. >>>> It's about CSS on the WWW, not on your computer. >>> In all my life, I'd never imagined that they were two different [quoted text clipped - 8 lines] > from a case-insensitive to a case-sensitive file system. But these > aren't aspects of the CSS language itself. True enough. But if the author /thinks/ the problem is CSS-related that would lead to posting here. No way to help if you can't see the problem online. >> You cannot solve such a problem - cannot even see it - when you only >> supply a few lines of source text. > > But if the poster has already established that no problem of this nature > is occurring, e.g. by testing locally, then it doesn't matter in this > respect. And what if he hasn't? SignatureEd Mullen http://edmullen.net http://mozilla.edmullen.net http://abington.edmullen.net I'm sorry you didn't care for my answer. Signature-bts -Warning: I brake for lawn deer > So why have you, in what follows, addressed neither a single pro of > posting code here nor a single con of uploading code to the WWW and > posting a URL here? You have been clearly advised, by folk who surely have more experience here than you have, that the best way to go about getting quality advice is to upload a stripped-down test case, complete, to the server that you use. This is good advice: having verified that it still exhibits the problem that one is complaining about, one can then apply the various on-line validators to be sure there aren't any obvious errors (many problems are solved by this means already, without any recourse to usenet), then post a clear statement of the problem, with the relevant URL, and anyone - you included - stands a good chance of getting a quality answer. Whether you take the advice or not is no care of mine; I for one haven't got time to argue with you about why it's good advice. If you stay around, I confidently predict you'll learn that it is. > I had no idea that Firefox didn't allow you to browse pages locally > on your hard disk without a web server. Every browser I've ever > used does. [...] > And I can't believe that you've got as far as you have (judging by > some of your posts) and yet remained in your world of delusion that > not a single web browser ever invented allows you to browse on the > local filesystem. So, you're an ill-mannered buffoon, too. The killfile awaits. The choice seems to be up to you now. Tue, 28 Mar 2006 17:01:41 +0100 from Stewart Gordon <smjg_1998 @yahoo.com>: > So why have you, in what follows, addressed neither a single pro of > posting code here nor a single con of uploading code to the WWW and > posting a URL here? Because it's been done to death. This is why proper etiquette is to read a group for a significant period of time before posting -- so you get yourself up to speed and don't post churlish demands for a discussion to be repeated for your benefit. SignatureStan Brown, Oak Road Systems, Tompkins County, New York, USA http://OakRoadSystems.com/ HTML 4.01 spec: http://www.w3.org/TR/html401/ validator: http://validator.w3.org/ CSS 2.1 spec: http://www.w3.org/TR/CSS21/ validator: http://jigsaw.w3.org/css-validator/ Why We Won't Help You: http://diveintomark.org/archives/2003/05/05/why_we_wont_help_you > Tue, 28 Mar 2006 17:01:41 +0100 from Stewart Gordon <smjg_1998 > @yahoo.com>: [quoted text clipped - 3 lines] > > Because it's been done to death. Please provide a link to the discussion I missed. > This is why proper etiquette is to read a group for a significant > period of time before posting -- so you get yourself up to speed and > don't post churlish demands for a discussion to be repeated for your > benefit. How long is a "significant period of time" IYO? I've been on and off this 'group probably for years, and never recall seeing a subject line to the effect of a discussion on this topic. Stewart. Signature-----BEGIN META GEEK CODE BLOCK----- Version: 1 gc ------END META GEEK CODE BLOCK------ My e-mail is valid but not my primary mailbox. Please keep replies on the 'group where everyone may benefit. Wed, 29 Mar 2006 10:45:41 +0100 from Stewart Gordon <smjg_1998 @yahoo.com>: > > Tue, 28 Mar 2006 17:01:41 +0100 from Stewart Gordon <smjg_1998 > > @yahoo.com>: [quoted text clipped - 5 lines] > > Please provide a link to the discussion I missed. *plonk* SignatureStan Brown, Oak Road Systems, Tompkins County, New York, USA http://OakRoadSystems.com/ HTML 4.01 spec: http://www.w3.org/TR/html401/ validator: http://validator.w3.org/ CSS 2.1 spec: http://www.w3.org/TR/CSS21/ validator: http://jigsaw.w3.org/css-validator/ Why We Won't Help You: http://diveintomark.org/archives/2003/05/05/why_we_wont_help_you >> Tue, 28 Mar 2006 17:01:41 +0100 from Stewart Gordon <smjg_1998 >> @yahoo.com>: [quoted text clipped - 14 lines] > this 'group probably for years, and never recall seeing a subject > line to the effect of a discussion on this topic. This topic is rarely seen in the *Subject* of a post, but often in a reply. Here's an example from 1998: <http://groups.google.com/group/comp.infosystems.www.authoring.html/msg/338b1417d d124f09> Signature-bts -Warning: I brake for lawn deer JRS: In article <lhcWf.641828$qk4.516317@bgtnsc05-news.ops.worldnet.att .net>, dated Tue, 28 Mar 2006 15:05:53 remote, seen in news:comp.infosys tems.www.authoring.stylesheets, Beauregard T. Shagnasty <a.nony.mous@example.invalid> posted : >> <snip> >>> More liberally translated: [quoted text clipped - 24 lines] >to a full example, with your code. For CSS questions, I can then even >play with it live using my browser (Firefox/Web Developer's Toolbar). That's rather egocentric. While long code should undoubtedly not be put in the newsgroup, short code is immediately accessible to those with off-line newsreaders, and can be executed locally without delay. If the code is only on the Web, the other readers will see the answer; but will, not having seen the question, be less able to evaluate the answer. If the code has, as you desire, been minimised, and is then reasonably short, the best approach is to put it in News (by copy'n'paste) and also on the Web. That way both types of reader are suited. Signature© John Stockton, Surrey, UK. ?@merlyn.demon.co.uk Turnpike v4.00 IE 4 © <URL:http://www.jibbering.com/faq/> JL/RC: FAQ of news:comp.lang.javascript <URL:http://www.merlyn.demon.co.uk/js-index.htm> jscr maths, dates, sources. <URL:http://www.merlyn.demon.co.uk/> TP/BP/Delphi/jscr/&c, FAQ items, links. > That's rather egocentric. What is? I did not make up the convention that it is better to post a URL to a web page than to post code here. Jeez. I fill in a better description of someone else's very brief comment about it and guys start pickin' on me... Go pick on them guys from 1998. Signature-bts -Warning: I brake for lawn deer JRS: In article <n7GWf.41610$bn3.29349@bgtnsc04-news.ops.worldnet.att.n et>, dated Thu, 30 Mar 2006 01:03:15 remote, seen in news:comp.infosyste ms.www.authoring.stylesheets, Beauregard T. Shagnasty <a.nony.mous@example.invalid> posted : >> That's rather egocentric. > >What is? That is. I quoted it. >I did not make up the convention that it is better to post a URL to a >web page than to post code here. But you seem to be supporting it. Or, in fact, you seem to be saying that the best thing to do is to post ONLY a URL, without considering that there are alternative alternatives - posting ONLY code, and posting both URL and (brief) code. >Jeez. I fill in a better description of someone else's very brief >comment about it and guys start pickin' on me... Go pick on them guys >from 1998. You are not responsible for what you support; but you are responsible for supporting it. Signature© John Stockton, Surrey, UK. ???@merlyn.demon.co.uk Turnpike v4.00 MIME. © Web <URL:http://www.merlyn.demon.co.uk/> - FAQish topics, acronyms, & links. Check boilerplate spelling -- error is a public sign of incompetence. Never fully trust an article from a poster who gives no full real name. >> Don't post code here, upload a minimised example using real content to >> your web server, then post the URL here. > > But why? Have you weighed up the pros and cons of the two approaches? Why don't you just accept the fact that posting a URL is the accepted convention of this newsgroup? If you want to play here, following the rules will get you a whole lot farther than ignoring them. ;) SignatureReply email address is a bottomless spam bucket. Please reply to the group so everyone can share. >>>Don't post code here, upload a minimised example using real content to >>>your web server, then post the URL here. [quoted text clipped - 6 lines] > If you want to play here, following the rules will get you a whole lot > farther than ignoring them. ;) Unless he's really just here to argue. What's green, and lives under a bridge? >> If you want to play here, following the rules will get you a whole lot >> farther than ignoring them. ;) > > Unless he's really just here to argue. The more he posts, the more I think that is the case. Otherwise, he is either arrogant or naive (maybe both) if he thinks he is the first to state posting complete code is somehow better than a URL. :-\ SignatureReply email address is a bottomless spam bucket. Please reply to the group so everyone can share. > I have no clue. > - I want to align the red, green, blue boxes in one line > - red,green,blue must be 45px high > - red (center) must be as wide as possible > - yellow must start exactly below the line > - yellow must be left aligned with red one. In X1, X2, X3 change "display:inline" to "float:left". In Y2 change "margin-top: 45px" to "margin-right: 44px". Delete "width:90%". Signaturejmm (hyphen) list (at) sohnen-moe (dot) com (Remove .AXSPAMGN for email) >> I have no clue. >> - I want to align the red, green, blue boxes in one line [quoted text clipped - 6 lines] > In Y2 change "margin-top: 45px" to "margin-right: 44px". Delete > "width:90%". looks perfect on FF, but IE(6) messes it up... Good point to start playing, though. Thanks a lot. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.