That's because Opera and FF conform to xhtml/css standards. (increase the window size)Originally Posted by okinrus
Hey Prelude. Nice website
A small fix: the css and xhtml validator links are switched
That's because Opera and FF conform to xhtml/css standards. (increase the window size)
Hey Prelude. Nice website
A small fix: the css and xhtml validator links are switched
I don't like fixed backgrounds.
Last edited by Sang-drax : Tomorrow at 02:21 AM. Reason: Time travelling
You could just add a 3D prelude... ok I have too much time.
GAH! WHAT THE HELL IS THAT THING?You could just add a 3D prelude... ok I have too much time.
-Govtcheez
[email protected]
I think you've mistaken the mouth as a nose. Take a closer look.You could just add a 3D prelude... ok I have too much time.
If I did your homework for you, then you might pass your class without learning how to write a program like this. Then you might graduate and get your degree without learning how to write a program like this. You might become a professional programmer without knowing how to write a program like this. Someday you might work on a project with me without knowing how to write a program like this. Then I would have to do you serious bodily harm. - Jack Klein
That is a pretty funny picture.You could just add a 3D prelude... ok I have too much time.
I think this is what it is supposed to look like though:
edit:: If I am wrong, I blame my wife.
edit 2 :: She said I could say that...
Not bad, not bad at all. And very clean coding I might add.
Nice simple website.
And I see we have the same tastes in web comics.
I see you didn't put my favourite, nuklear power though.
And although the art at MegaTokyo has improved, the story has gone down alot.
Well, I think at least with HTML the browser can choose to display any way they want to. I don't know about the xhtml/css standards.That's because Opera and FF conform to xhtml/css standards. (increase the window size)
I also don't think increasing the window size is the best option. I tried both 800x600 and 1024x760 with the screen maximisedthe problem is still there. (With 1024x760 and the problem is almost gone but still there.) I think a temporary fix would be to shorten a few lines, maybe using "typedef struct jsw_tree jsw_tree".
>>I also don't think increasing the window size is the best option. I tried both 800x600 and 1024x760 with the screen maximisedthe problem is still there. (With 1024x760 and the problem is almost gone but still there.) I think a temporary fix would be to shorten a few lines, maybe using "typedef struct jsw_tree jsw_tree".
*bang*
>> I don't know about the xhtml/css standards.
Then shut yer mouth.
>but the dark brown code boxes aren't very pleasant
That's a consistent complaint, so I'll look for a better color. Fortunately, I planned ahead and all I need to change is my stylesheet.
>the css and xhtml validator links are switched
I wonder how that happened.
>I don't like fixed backgrounds.
I'm divided. I like the extra bit of style that they add, but sometimes scrolling is jerky. However, with the looooong pages, I set the background as fixed to keep it from being too dull.
>You could just add a 3D prelude...
Not nearly cute enough.
>And very clean coding I might add.
I'm anal about things like that.
>And although the art at MegaTokyo has improved, the story has gone down alot.
Actually, I think that the story has only gotten better as Fred-rin has gotten more experienced. Sure, it's more of a drama now than a humor comic, but that's a good thing IMO.
>I tried both 800x600 and 1024x760 with the screen maximisedthe problem is still there.
This is a tricky area. Resolution isn't the only thing you have to think about when building a web page. For example, different text sizes will render differently and could throw off the entire layout. When I get around to it, I'll determine which boxes are likely to have a problem and set the overflow to scroll. I prepared for that and have a scroll class ready, but the scroll bars are kinda fugly.
>I think a temporary fix would be to shorten a few lines, maybe using "typedef struct jsw_tree jsw_tree".
My best code is written with the delete key.
ober, why? do you agree with me that the standards should matter in this case? Every xml standard I've read defines a way of structuring data not presenting data, and every browser is going to choose a different way to present the data, right?Then shut yer mouth.
Prelude, maybe the overlap was the text setting as well the resolution. It looks good when viewed through IE and IE doesn't use scroll bars, so maybe you could get firefox and opera to do what IE does? In any case, if you do use scroll bars make sure the vertical text is large. I've tried to read code that only has three or four lines vertically and it's almost impossible.This is a tricky area. Resolution isn't the only thing you have to think about when building a web page. For example, different text sizes will render differently and could throw off the entire layout. When I get around to it, I'll determine which boxes are likely to have a problem and set the overflow to scroll. I prepared for that and have a scroll class ready, but the scroll bars are kinda fugly.
Some people have made cases that using "struct s" instead of "typedef struct s" isn't just style, but nowdays I think it doesn't matter.All stylistic reasons for avoiding that aside, I loathe changing my style just to meet formatting needs. I'd rather add a scroll to the box than change my code.
No. xhtml/css standard is clear. Markup and presentation. Content and looks. css exists for some reason.
When internet became popular by 93~94, there was a browser war about adding new html tags - anarky. Netscape introduces the font tag with size and color, later internet explorer introduced the font face attribute, and it was caos. Browser wars, each one adding as much tags a possible, just to said tha browser X is good, browser Y doesn't support this and that. In 1999 w3C created the standard with defined every little piece of influence each tag would make in a final document. Currently all major browsers stick to this standard to keep html documents portable. All, except for one: IE which still lives in the stone age, with known security holes for more that 2 years, but Ms doesn't care a bit about it. IE comes with windows. most windows users are unexperienced so they use IE. IE respects old standard, and IE specific syntax for javascript, html. Since IE owns 88% of browser market share, MS doesn't care a bit about updating that piece of crap software, which I call a virus myself. Therefore 90% of webpages are made of broken stupid code, written by WYSIWYG stupid editors, or with IE specific coding. Then people rant about Opera's or FF lack for rendering all webpages well. The problem is not with the browser but yes with the page.
Do a favour to yourselves and the www: don't use IE.
My recomendation: opera
MS has already anounced IE 7, obviously only to fight against the increasing market share of alternative browsers. It'll have tabbed browsing, rss feed, and probably a bit more of support for standard xhtml/css. If so, many webportals will render bad in IE7 and prove those webmasters should be cleaning toilets in a bus stop.
Last edited by xErath; 07-05-2005 at 08:04 PM.
Tony G. used Adobe Illustrator for our book and his other books.When I find some time to play with Photoshop, I'll replace the lame ASCII art with proper images.
Also, do you have plans to add more on the following tree topics:
1. B Trees
2. B+ Trees
3. Tries (Lexical Search Trees)
JC
Mr. C: Author and Instructor
Everything is good except for the code background and one major problem you used C and not C++
Last edited by prog-bman; 07-05-2005 at 09:55 PM.
Woop?
