VS.NET SDL Tutorial - Input needed - Tilted Forum Project Discussion Community

SecretMethod70 · 06-29-2003, 12:21 PM

Two of my friends put together a brief tutorial for setting up SDL (Simple Direct media Layer) in Visual Studio .NET, complete with tons of screenshots. They'd like feedback on how correct and easy/not easy it is to follow. I figured what better way to help out then ask the community here, so here is the link:

http://pgdc.purdue.org/sdltutorial/sdl_setup.html

Please comment with any constructive criticism and/or praises that you can come up with. They appreciate it. They plan to make another tutorial in a couple of weeks as well, after they finish this one.

SecretMethod70 · 06-30-2003, 03:23 PM

...no one has VisualStudio.NET and is willing to try this out?

He's trying to get feedback ASAP so he can move on to refining it

froseph · 06-30-2003, 03:53 PM

i have VisualStudio.NET (rarely use it), looked over it very briefly and it seems ok. I had it set up already in VC 6.0 so i use that more often (never really got used to .NET and it didnt work my mysql++). I don't like the idea of including the library into the solution/project. I think you can tell the linker to link it via project->properties->Linker->input->Additional Dependencies
but don't quote me on that (didn't try it out myself, but it looks like the right place for it)

charliex · 06-30-2003, 09:57 PM

if it were me i'd rewrite it to use relative paths so that you don't have to change the path for each project, setup as a tree based source layout so that the sdl is in the root and your projects are in in a sub directory. that way you can ..\ to the includes and libraries. It also allows you to integrate properly into source safe since it doesn't easily allow different source files from different trees in the same directory.

also i'm fairly sure the sample "hello world" app won't prove SDL libs are being correctly being included, since its not actually using anything from the libs, only the headers.

also instead of using a .lib set into the project settings, you can add a #pragma to get the lib to automatically include from the header.

Not using absolute paths is good practice when sharing with other programmers, and its good to start off that way, rather than say well it doesn't matter for now.

Also their HTML is broken for the sample code, they have to take care of the #includes bracketting.

06-29-2003, 12:21 PM	#1 (permalink)
SecretMethod70 Human Administrator Location: Chicago	VS.NET SDL Tutorial - Input needed Two of my friends put together a brief tutorial for setting up SDL (Simple Direct media Layer) in Visual Studio .NET, complete with tons of screenshots. They'd like feedback on how correct and easy/not easy it is to follow. I figured what better way to help out then ask the community here, so here is the link: http://pgdc.purdue.org/sdltutorial/sdl_setup.html Please comment with any constructive criticism and/or praises that you can come up with. They appreciate it. They plan to make another tutorial in a couple of weeks as well, after they finish this one. __________________ Le temps détruit tout "Musicians are the carriers and communicators of spirit in the most immediate sense." - Kurt Elling

06-30-2003, 03:23 PM	#2 (permalink)
SecretMethod70 Human Administrator Location: Chicago	...no one has VisualStudio.NET and is willing to try this out? He's trying to get feedback ASAP so he can move on to refining it __________________ Le temps détruit tout "Musicians are the carriers and communicators of spirit in the most immediate sense." - Kurt Elling

06-30-2003, 03:53 PM	#3 (permalink)
froseph Tilted	i have VisualStudio.NET (rarely use it), looked over it very briefly and it seems ok. I had it set up already in VC 6.0 so i use that more often (never really got used to .NET and it didnt work my mysql++). I don't like the idea of including the library into the solution/project. I think you can tell the linker to link it via project->properties->Linker->input->Additional Dependencies but don't quote me on that (didn't try it out myself, but it looks like the right place for it) __________________ sometimes it just takes a cat

06-30-2003, 09:57 PM	#4 (permalink)
charliex Junkie Location: North Hollywood	if it were me i'd rewrite it to use relative paths so that you don't have to change the path for each project, setup as a tree based source layout so that the sdl is in the root and your projects are in in a sub directory. that way you can ..\ to the includes and libraries. It also allows you to integrate properly into source safe since it doesn't easily allow different source files from different trees in the same directory. also i'm fairly sure the sample "hello world" app won't prove SDL libs are being correctly being included, since its not actually using anything from the libs, only the headers. also instead of using a .lib set into the project settings, you can add a #pragma to get the lib to automatically include from the header. Not using absolute paths is good practice when sharing with other programmers, and its good to start off that way, rather than say well it doesn't matter for now. Also their HTML is broken for the sample code, they have to take care of the #includes bracketting.