AutoHotkey Community

[Tuncay]

What do you mean tank? Why is the COM special in this case? Automatic downloading requires that the developer provides all needed information in a standardized manner also.
_________________
{1:"ahkstdlib", 2:"my libs", 3:"my apps", 4:"my license"}
--> Don't feed the troll! <--

[tank]

Sean makes updates and in this case has been successfull getting all references to point at his official download. this may have changed with COMAHK or ahk L and U

I bring it up because of limited current and possible version updates in the future
_________________

We are troubled on every side‚ yet not distressed; we are perplexed‚
but not in despair; Persecuted‚ but not forsaken; cast down‚ but not destroyed;

[aobrien]

I've been using AHK for a couple of years now and wrote and maintain Serial ( COM ) Port Console Script http://www.autohotkey.com/forum/viewtopic.php?t=28703&highlight=serial.

I believe that there needs to be some level of oversight and enforcement of minimum standards in stdlib for the project to be successful. Otherwise the stdlib will end up being a mess just like the functions section of the website. For instance, I think that my Serial COM Port functions should be included, however, as they stand now should not be accepted because (as was recently pointed out to me) they are not stdlib compatible.

Here are my thoughts on how to better organize the functions and begin a stdlib.

Definitions
Function - code that is intended to be included in another script.
Product – standalone script.

*There should be one webpage for productized Functions and one web page for productized Products.

*There should be perhaps one or two moderators for each page. The moderators will decide which Functions/Products get included in their respective productized Function/Products web page.

*Each Function/Product will get it's own entry and the thread will be locked to everyone (except the author/maintainer).

*These pages should include everything necessary for the end user to successfully apply the Function/Product (a link to discussion forum, documentation, source code, example code using the Function, description of how the Function/Product was tested, change logs).

*There should not be any discussions on the Function/Product pages. Discussion can be done in the Scripts & Functions section of the forum.

*Individuals can submit their Function/Product to the moderators for inclusion into the respective web page.

*The Function/Product should NOT be accepted unless the following criteria is met:

........-The Function/Product provides a solution for a non-trivial problem and will provide significant value to AHK. Otherwise it should just stay in the Scripts & Functions forum.

........-The submitter has provided the link to the discussion forum, documentation, source code, example code using the Function, description of how the Function/Product was tested.

........-The source code meets certain guidelines (readability, error checking, best practices, …)

........-The submitter accepts the responsibility of maintaining the Function/Product.

This way there will be a list of high value Functions/Products on the website that won't get lost in the haystack and can be easily implemented by the end user.

But of course there should be a zip file which includes all accepted Functions/Products and Tuncay's utility would be a very nice front end for the zip file.

Well, what ever the decision. I'd be willing to help wherever possible.

[Guest]

I agree with some of that, except is should not be the moderators final call, if a moderator "don't like you" you'd never get accepted...I don't think it should be dictatorship "you're allowed in", "you're not, get lost"...something less formal...or able to bypass a mean moderator...

[aobrien]

I suppose a rogue moderator could be a problem, however, this was the best way that I could think of maintaining some level of quality control. Hopefully these kinds of problems would be minimal. Your idea of having a way to bypass a moderator is good.

My main concern is that we don't let the stdlib end up like the functions & scripts section - thousands of mostly undocumented and unsupported functions. If the stdlib ends up like this then it will be essentially useless.

After I made the last post I was thinking more about documentation. The level of documentation of AHK is superb. I think the stdlib should try to maintain this excellent level of documentation. Perhaps the best way to accomplish this is to provide a link in the Functions/Products section to a wiki page. This way everyone in the community will be able to contribute to the documentation effort.

Like i said before, I'b willing to help in any way possible.