You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Cloudlogs 'Contest-Configuration' just contains a contest name and an identifier.
I would like to include bands/modes (and maybe exchange type) into the contest configuration.
My proposal would be, to just have 2 (3) additional columns in the contest table, bands, modes (and exchange) for comma separated bands and modes (and exchange-type) and to have the client-side javascript on the contest-logging page reduce the available options in the bands- and mode-dropdown <select>.
While I'm quite sure about the bands and modes thing, I'm unsure about contest-exchange (which could benefit from some work anyway ;) ), as there are contests, where the exchange differs if e.g. you are member of some club or not.
I'd be happy about some discussion and while I'll happily contribute client-side-javascript, or server-side php (or some wild mixture of any of the stuff...), I'm not too sure, how Cloudlog handled DB-changes in the past and thus would be grateful for some primer, hints, or help :).
Vy 73 de Cedric DJ3CE
The text was updated successfully, but these errors were encountered:
Currently Cloudlogs 'Contest-Configuration' just contains a contest name and an identifier.
I would like to include bands/modes (and maybe exchange type) into the contest configuration.
My proposal would be, to just have 2 (3) additional columns in the
contest
table,bands
,modes
(andexchange
) for comma separated bands and modes (and exchange-type) and to have the client-side javascript on the contest-logging page reduce the available options in the bands- and mode-dropdown<select>
.While I'm quite sure about the bands and modes thing, I'm unsure about contest-exchange (which could benefit from some work anyway ;) ), as there are contests, where the exchange differs if e.g. you are member of some club or not.
I'd be happy about some discussion and while I'll happily contribute client-side-javascript, or server-side php (or some wild mixture of any of the stuff...), I'm not too sure, how Cloudlog handled DB-changes in the past and thus would be grateful for some primer, hints, or help :).
Vy 73 de Cedric DJ3CE
The text was updated successfully, but these errors were encountered: