
 תש*%@S$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$S@*שת

            . the  cruelization  voting  assistant  future  plans .

 תש*%@S$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$S@*שת

     this is the stuff i will sooner or later add/improve in the assistant.
   if you any ideas, be sure to email me.  one thing - don't expect any of
   those at some specific time, i might go on a coding spree some weekend
   and do them all or i might not touch it for weeks :D . so, here:

   * modules crc/size verify, maybe also structure check for known types
     (i.e if it's a valid MOD S3M XM or whatever.)
   * auto-rename on wrong module types (i.e an IT saved as S3M or vice
     versa, etc.)
   * automatic composer alias retrival (mayle i'll just make you contestants
     include a .txt file together with the module, which txt would include
     your alias :)
   * record of composer statistics (times won, average score of all times,
     and so on) - that if i'll have totally NOTHING ELSE to do :)
   * external song/composer list datafile (will probably be added after those
     above, after all hardcoding the song lists into the EXE itself has
     cartain advantages). of course after making it so i will not have to
     recompile it every single time :P , and the datafile should be flexible,
     too (i.e not have any fixed structure, more of a header with information
     on it's structure).
   * voting guide (?) - upon selecting a score text will be displayed such as
     'totally amazing - everything about is is just overhelming' on 20,
     'really good, few minor flaws' on 15, etc. on the other hand, instead of
     doing it i might write a text file on the voting scale - what part of
     the score should be given for what (for example, tuning - 1-3, structure
     1-3, melody 1-5 etc.) . if you got any ideas on that, or want to write
     the texts - mail me.  of course all marks have to stay inside the 0-20
     scale.
   * another 'text editor window' function rewrite? ouch, i rewrote it 2 times
     already, now it finally seems to work and do the right realtime word wrap,
     although i'm sure it still has bugs (i had to be crude on memory to make
     some of the routines work in the plain C environment i was using, maybe i
     should do it C++ OOP in the 1st place. oh well, too late for that now.
     or maybe not. :) if you encounter any bugs,please report report them fast,
     because i spent more time on coding (mostly debugging) the realtime wrap
     than on coding the whole program (!) and god darnit, i sure hope it pays
     off. of course i could just make it a dumb textbox like some people did :)
     still, i thought about making it a regular text editor optionally, since
     some people may dislike real time word wrap viewing :) . the text will,
     eventually, be wrapped as needed for the results, since i don't want to
     make the results file huge just because it's full of empty lines, but
     the editing might be easier for some people in 'conventional' mode. mail
     me if you got a point on that, i might put in a 'realtime wordwrap on/off'
     option. i could also compromise and make a part word wrap function, like
     in trixter's mc4 votefile editor (good work trixter!) and a few others.
     also, the memory consumption could be reduced wonders (no need for all
     that RT reallocating). as for coders among you, if you got some ready
     made _working_ RT wrap modules in C/C++, i'd be really grateful if you'd
     send them my way :) . 
   * 'large mode' for voting screen. i.e all the screen is songs and scores
     shown against each song (and not against the highlited one as now), and
     by pressing enter you'd go to full screen comment editor. the old mode
     (one used now) will stay and will be available to choose, under 'compact
     mode'.   this addition i actually plan to implement pretty soon - after
     all, not much code is needed for that.
   * improve the menuing system... maybe one big menu with details entering,
     voting and 'exit, save' and 'exit, no save' options.. why should people
     rerun the program if they want to change details? :) probably will do
     this one soon, too. some internal stuff is ready for it already. (such
     as usiversal menuing funcs, and separate details entry, etc etc), i just
     have to make new screens/new menus processing mains and that should be it.
   * results viewer? i don't really think it would make any difference since
     the text file is pretty much it (well, the only decent use of a results 
     viewer i see is the ability to see comments separately) and it doesnt
     matter much if it's a text file/exe viewer anyway imho, but if you think
     otherwise - mail me.
   * and the usual, of course, bugfixes bugfixes bugfixes :) plus all that 
     cosmetic stuff here and there.

   * comment the code..!..COULD I POSSIBLY...?!?!...naah.    :D


     mail me with your ideas!

 תש*%@S$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$S@*שת

              - Cruel Creator -             - cruel@kosmic.com -

 תש*%@S$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$S@*שת


