Open GoogleCodeExporter opened 9 years ago
In general, the program is meant to be useful for both types of judging.
Admittedly, the queued judging components were easier to program due to the
smaller set of variables involved. In the spirit of your analogy above, let me
offer this one about the program.
BCOE&M is a tool, much like a hammer. Each competition that uses the program is
a nail. Each competition is unique because the particular set of resources for
the competition vary from other competitions (entries, participants, staff,
etc.). There are also many commonalities among all competitions (entries,
judges, stewards, etc.).
The software can only account for the commonalities among competitions and
cannot account for all variances and idiosyncrasies.
So, continuing the analogy, one competition could be a finishing nail, another
a 10 penny, and yet another a railroad spike. BCOE&M is just a plain old claw
hammer. It will get the job done on each, but the degree of hammering will
depend upon the user.
In the case of stewards, I agree with your suggestion and will look at a
solution.
Cheers,
Geoff
Original comment by gpzhumphrey
on 29 Oct 2012 at 8:28
Thanks Geoff! Just tossing them out there, you control the destiny of the
app.
Ted
On Mon, Oct 29, 2012 at 1:28 PM,
<brewcompetitiononlineentry@googlecode.com>wrote:
Original comment by ted.as...@gmail.com
on 29 Oct 2012 at 8:51
No worries, Ted. Thanks for being so diligent and forward-thinking.
Geoff
Original comment by gpzhumphrey
on 30 Oct 2012 at 3:31
Original issue reported on code.google.com by
ted.as...@gmail.com
on 25 Oct 2012 at 6:03