MCA:
quote:
by-the-way Brian can you more explain "what are the tasks for beta testers"?
Interest, who knows.
greetings.
What I mean is that new UDF database system is nearing completion. We're looking for you experts that can help us to populate it, and in doing so, offer suggestions on how to improve the database system...
For example: The UDF submission wizard will allow you to enter your UDF using a form, using the standard template system (like the KiX manual, our UDF library and this forum).
You'll enter the Action:, select the number of parameters, what type they are, and whether they are required or optional. Other files like Remarks, Examples, and Source (of course). You'll evene be able to itemize dependencies on other UDFs.
The system will allow visitors to use checkboxes to select multiple functions and a bot will compile the requested UDFs into a TXTFILE attachment and e-mail it directly to the visitor. Of course the bot will be smart enough that if you select FunctionA and it is dependent on FunctionB, FunctionB will be automatically included in the sent attachment.
Since version control (created/last updated) will be part of the database, visitors -- upon returning to the UDF site, will be notified that there are new functions and or updates to functions they previously downloaded.
The original author will have exclusive rights to directly modify the UDF once submitted, and everyone else can post comments/suggestions/etc. in a forum style (much like RFCs).
Of course, name duplication will be eliminated due to the database design.
Where the 'beta testing' comes in is helping us, by being part of the design and testing process. Is our submission wizard too strict? Are fields too limited? etc. Influence the look, feel, navigation, etc.
There's really a lot to the design of this. I've only mentioned some of the features here -- we've really been working on this for quite some time. We also know it can be even better with all your support & suggestions.
I guess the easiest thing will be to post something here when we are ready to start testing it.
