I havn't seen very many tuts on WinINet before, and the ones that I have seen aren't of the greatest quality. So I wrote one.
http://queatrix.awardspace.com/wininet.html
What do you think of it?
Queatrix.
Printable View
I havn't seen very many tuts on WinINet before, and the ones that I have seen aren't of the greatest quality. So I wrote one.
http://queatrix.awardspace.com/wininet.html
What do you think of it?
Queatrix.
Wsaeconnrefused
?????????????
looks like someone stopped paying their hosting bills?
What on earth (not mars) are you talking about?
Oh dear, since you did not grant permission to use your tutorial... isn't it a little useless? ;)Quote:
Do not edit or use or copy this work
without permission from the author.
Hahaha!Quote:
Originally Posted by laserlight
I think that if you want to splatter legalese (or a lame attempt at it) on your writings you should at least make sure that legalese allows people to read the damn thing. And I'm not going to put a winky like laserlight did.Quote:
Originally Posted by Queatrix
As of now I didn't even look at the thing because it told me not to. "Don't use it without permission." Okay, following orders.
I'm very sorry about that.
I changed it to what it should've said in the first place.
You should get rid of the fixed-width font.
What font do you suggest? And why?
What do you think of the actual tutorial itself?
Is my wording clear?
Do I describe everything well?
If you can't get rid of the english grammar mistakes, at least run it through a spellchecker (OpenOffice with english dictionary) and get rid of the typing errors.
... and when are you starting to use the free HTML/CSS design I offered you ?
I recommend a font with serifs and variable character width because it is easier to read. Also, variable character width is more important than serifs.Quote:
Originally Posted by Queatrix
If you want more arguments, try to find a book which uses fixed character widths.
Good to see you're using dwks' code colourer! :)
You must have left off the rules file argument. ;)
I wouldn't say
because it is quite easy to override the default stylesheet and make the default text colour blue. Voila! It's all in the public domain. :)Quote:
Although the tutorial is copyrighted, the code (all that you see in blue) I place in the public domain, so you can use it for whatever you want, and do whatever you want with it.
Why would you want to copyright it anyway? I'm just curious. If you're worried about people taking your tutorial any saying "this is mine", use a very unrestrictive license that just requires derived works to mention the original author. Personally I think that if someone wants to copy or extend my work, it's a compliment. :)
I usually save web pages from the internet to read them later so I don't have to be connected all of the time. Your license prevents that. I cannot even save the page to view it later offline. What about the web server? Are they not allowed to make backups of your website because of your restrictive license?Quote:
Do not edit, rip, or copy this work
I don't see why you want to prevent copying. It's in a digital medium. Copying is what computers do best. (Well, pretty well, anyway.) As long as no one changes your work (assuming you want that), by all means let them copy it! Your work will spread further. If you think you'll be changing it a lot, just add something like "the latest version of this page can be obtained at whatever.com".
Where? How? People are generally stupid. It doesn't take you long to add a link and many more people will leave comments if you do.Quote:
Please tell me what you think of this tutorial by leaving a comment.
Also, do you really want to post your full name onto the internet?
I made some fixes, is the licence fine now?
Just because the classic Courier typeface looks like crap doesn't mean all monospace fonts are worthless. Try Letter Gothic for instance.Quote:
Originally Posted by Sang-drax
I really think the code should be in the public domain. I mean, will you be personally offended if someone borrows a code snippet without citing you in the docs (or elsewhere)? The actual code there is more likely to be incorporated [rewritten] into something that needs it anyway. It's not like you've used excerpts of a library you created and you're already offering it under another license. If the situation were different, I'd support copyrighting the tutorial and it's derivative works.