Re: Extended Rough for Build Tracker

At 12:27 PM 10/5/00 +0200, André Langhorst wrote:

Hi Zak, great work!

Thanks!

Important edit: We do not want to know (though it´s interesting) primarily which Server people are using PHP with, we do want to know which SAPI they´re using.

My thinking on this was that the configure line will let us know what SAPI they are using. The server list is there so that we can easily find what people are using their CGI versions with. If you check... crap, cvs.php.net is down again... ok, if you take a look at the extension_list.txt file in qaweb/build_tracker, you can see all of the extensions that I think the harvest form should gather extra information about - this should include all of the SAPIs. (This list is used by comparing it to the person's configure line. For every match found, a set of fields is added to the harvest form.) Try putting --with-nsapi in the field for 3.4 on the filter page and then see what the harvest form displays. (Note, if the form - or this message - seems unclear, it is :)

You can copy a list of all SAPIs (including CGI) from cvs /repository/php4/sapi there are some folders. The next step (on the next page or dynamically through javascript displayed) would be to list some common servers (versions) for the selected SAPI eg. CGI -> list all (is the server information important here?) / list none Apache -> Apache (perhaps we do need the version numbers too?) ISAPI -> IIS4, IIS5...

This is a good idea - I would put it at lower priority - maybe something to be done after the form is working?

I´d be nice to have a "custom" input field there too.

This is the way that it currently is. Note, if someone chooses Netscape as a server and has --with-nsapi in their configure line, their will be two separate sets of form fields brought up for netscape - I will fix this.

Suggested edit: We should use the benefits of HTML4 in our MEGA-MULTIPLE-OPTION select boxes (in this case OS box), it won´t hurt people with ancient or old browser and it will help people with modern browsers. Try this code fragment with Mozilla. OPTGROUP allows you to group options and assign them a label (mozilla displays, IE5 does not, IE5.5 don´t know) <SELECT name="ComOS"> <OPTION selected label="none" value="none">None</OPTION> <OPTGROUP label="PortMaster 3"> <OPTION>PortMaster 3 with ComOS 3.7.1</OPTION> <OPTION>PortMaster 3 with ComOS 3.7</OPTION> <OPTION>PortMaster 3 with ComOS 3.5</OPTION> </OPTGROUP> <OPTGROUP label="PortMaster 2"> <OPTION>PortMaster 2 with ComOS 3.7</OPTION> <OPTION>PortMaster 2 with ComOS 3.5</OPTION> </OPTGROUP> </SELECT>

huh... you learn something new every day. I think that I should get the tracker working before tackling something like trying to provide an accurate and comprehensive list of OS versions/sub-flavors. Perhaps this should be considered during the initial design, and then added after the tracker is running. Thanks for the feedback! :) - zak