VBGamer

All Forums  VBGamer  VBGamer  The Code Bin

Note: You must be registered in order to post a reply.

Screensize: 640 x 480 800 x 600 1024 x 768 1280 x 1024 UserName: Password: Format Mode: Basic  Help  Prompt  Format: Font Andale Mono Arial Arial Black Book Antiqua Century Gothic Comic Sans MS Courier New Georgia Impact Lucida Console Script MT Bold Stencil Tahoma Times New Roman Trebuchet MS Verdana   Size 1 2 3 4 5 6   Color Black Red Yellow Pink Green Orange Purple Blue Beige Brown Teal Navy Maroon LimeGreen Message: * HTML is OFF * Forum Code is ON Smilies [quote][i]Originally posted by Eric Coleman[/i] [br]I've mentioned this quite a few times, and no one was willing to actually help me with it. I figure that I'll just work on it by myself in my free time. I've had two different ideas on how this could be accomplished. I'd like some feedback on which of these do you think would be more successfull. The concept is to have a repository of user submitted code. The code would not be complete programs, but individual functions and subs. Perhaps even classes. The way it would work would be for people to submit functions, and then people can search the database of functions, read descriptions of what the functions do, search for certain functions, and select which functions you want to download. A .bas file would be created containing all the functions you had selected for download, and then you simply download the .bas file and add it to your program. The functions could either be public or private. By this I don't mean "Public Function" or "Private Function", but a function uploaded by me could be a private function in the sense that only I can make modifications or edit the function. If I upload a function and make it public, then anyone can come along and make corrections or fix bugs in the function. See the difference? I should probably think of some terms other than public and private to describe this functionality. Imagine being able to download a generic FPS function, or a function to do collision detection between spheres and cubes. Most example programs that try to demonstrate some sort of concept generally have lots of other code to make the program function. A program that demonstrates skeletal animation on 3D characters in OpenGL is nice, but if you're using the program to try to accomplish the same thing in Directx, then all you really need to look at is the code specifically related to the skeletal animation. So that's one idea. Here is the other. The concept of owning a function or some piece of code is not new. Also, the first idea isn't that far off from having some sort of content management system. The big difference is that instead of a repository for snippets of code, it would be either a private or public repository of entire projects. The idea of this came about because of all the so called "community" projects that have failed due to any lack of organization. This version of the "code bin" would be similar to source forge. You'll be able to store all of your code on the server and restrict access to who can view or edit the code. It would work something like this. You create a project, and person A has access to the multiplayer code and can edit it. Person B has access to the graphics portion of the the code and can edit it. Person C has access to the multiplayer and graphics code, but can only read, and has read/write access to the scripting engine code. If more than one person has access to a section of code, then a library system will be used to determine who can edit the code. You can grant certain people time privalges to have access to a piece of code, and if they don't update or report back in after a set amount of time, then other people will have access to the code after that time has elapsed or the when the person updates the code. This would avoid the situation where more than one person is trying to modify the same portion of the program. Which idea is better? [/quote]    Insert an File Check here to include your profile signature. Check here to subscribe to this topic.