Ggallery
02-03-2010, 09:46 PM
The FTP is very chaotic. After relying on only it for a month, I discovered I was reinventing the wheel on many things after going thru the download sections of the regular website. I swear there are scores of things on the site that arent in the ftp. They could be there but the directory structure of the FTP is very daunting. Too many root folders with subfolders and so on. I strongly feel it discourages people from uploading and participating in the ftp side of development. I argue that there should only be a folder for each system, and people should upload their additions into the applicable system folder. They just need to add their handle into the file or folder they're adding instead of create their own main folder with subfolders for whatever they have to offer. This should be a rule, perhaps. Currently it appears people have been dumping stuff in at random. I argue they NEED a clear framework to avoid their own confusion.
The HS directory structure is nice and clean, simple. All laid out with each system having its own folder to keep the mess it entails discreet from the others. (except i dont think the Databases folder needs subfolders for each system!)
The FTP on the other hand is a handful of folders with seemingly non-sensical contents within each. For instance, files related to any one system may be spread out across the spectrum, in the form of files, folders and ZIP's. I had to dig deep into places I didnt expect to notice things... I didnt expect.
What I propose is structuring the FTP just as we find it when we install HS: a folder for each system, and some extras such as "Main Menu". Perhaps only allow those systems currently found in a recent HS install in the main root, with an "Others" folder that has seperate folders for each system people are trying to work on not yet 'official'. (But I dont suggest having 3 seperate root folders how we find in HS, where it IS needed. I dont think thats needed in the FTP which is just a collection of HS related data.)
This would allow people to add their different XML files, and so on, for others to reference, add upon and use. With little text files for each system containing AHK code for hyperlaunch, etc, there would be less NEW threads asking what code others have used. This trend would also support better collaboration.
I think this alone would encourage people to contribute. But my other idea is to add 'public' UPLOAD folder with anonymous access for people to upload stuff. I think this would get their foot in the door to want to then donate to get to the other stuff, especially if they could see the other stuff just not download any of it with their anon logins.
My guess is the restructuring part would take less than an hour, which wouldnt bother the flow of peoples access much.
As long as peoples additions are properly named this system would be ideal. For instance, current having a databases folder with subfolders containing default XML's is redundant. All that is really needed is each XML in the main root folders titled 'etc DEFAULT etc', zipped up even perhaps. I'm sure you get the idea. I'd be willing to help.
The HS directory structure is nice and clean, simple. All laid out with each system having its own folder to keep the mess it entails discreet from the others. (except i dont think the Databases folder needs subfolders for each system!)
The FTP on the other hand is a handful of folders with seemingly non-sensical contents within each. For instance, files related to any one system may be spread out across the spectrum, in the form of files, folders and ZIP's. I had to dig deep into places I didnt expect to notice things... I didnt expect.
What I propose is structuring the FTP just as we find it when we install HS: a folder for each system, and some extras such as "Main Menu". Perhaps only allow those systems currently found in a recent HS install in the main root, with an "Others" folder that has seperate folders for each system people are trying to work on not yet 'official'. (But I dont suggest having 3 seperate root folders how we find in HS, where it IS needed. I dont think thats needed in the FTP which is just a collection of HS related data.)
This would allow people to add their different XML files, and so on, for others to reference, add upon and use. With little text files for each system containing AHK code for hyperlaunch, etc, there would be less NEW threads asking what code others have used. This trend would also support better collaboration.
I think this alone would encourage people to contribute. But my other idea is to add 'public' UPLOAD folder with anonymous access for people to upload stuff. I think this would get their foot in the door to want to then donate to get to the other stuff, especially if they could see the other stuff just not download any of it with their anon logins.
My guess is the restructuring part would take less than an hour, which wouldnt bother the flow of peoples access much.
As long as peoples additions are properly named this system would be ideal. For instance, current having a databases folder with subfolders containing default XML's is redundant. All that is really needed is each XML in the main root folders titled 'etc DEFAULT etc', zipped up even perhaps. I'm sure you get the idea. I'd be willing to help.