Part 3 _ initial plans

[hobranan]

There's alot to do from now until mar.13 (part3 due date) and the eclass 'project part 3' page suggests that we should have established half of the requirements ready by then. "This project part focuses on a working prototype with about half of the requirements. You must have some server connectivity working by this part." I personally think that we should have every requirement attempted/progressing (just not needed to be in final form).

I suggest we start dividing up the android .java and .xml file creation tasks between everyone (starting with the CRC classes that we know will be important bases of the app); and we start tackling specific user stories (also in order of general base importance going first). Additionally, we should review the user stories for possible enhancements on specifications (like some of the 'enhancement' issues already posted on the Project Board) and review the eclass forum for questions that other teams have asked (things that we also may want to consider).

[hobranan]

Harrison mentioned interest in doing areas of class creation and junit testing. I dont mind doing areas of aesthetics UI tuning (xml tuning).

[hobranan]

hi @everyone i started playing with the hash maker because i wanted to see what data examples we could produce so as put them on our UI (and app in general).

I have uploaded to my github branch an excel file with example strings to convert into sha256 hashcodes (they are mostly just random text, but some of them are strings i got from qrcodes/barcodes off pizza boxes and pop cans). i also made some example naming conventions for the generated code names ( something like spirited fighting goose), based on the first 3 hash chars.

i also uploaded an example android studio project that contains algorithms to take strings and convert into: hashcodes, generated names (as seen in the excel sheet), and a point system (it's similar to eclass examples, but the algorithm is complicated to me , but i made something to start with; mine is set where it checks every 4 hash chars at a time, but neglects to check the char in between the 4th and 5th, when iterating).

additionally, i made some example usernames in the excel to later attach to the qrcodes (whenever we get to that).

have a look at the excel sheet (list of species, etc...) and the android project (qrhashtester.zip) on my github branch. we can always change the output of names and points later. for now the hashcode generation works good.

[hobranan]

@everyone since we all split up into UI/xml production and backend/.java production: please state which files you are working on. I am currently doing the UI/xml startup pages (title screen, signup, homescreen, quick-navigation) and working my way forward in the same fashion as seen on the UI story flow path; which means i will next (after feeling like my startups are functional enough) probably work on add-code-camera-prompt xml, code-acquisition-description xml(s) (including the 'sorry couldnt get' and 'gotcha' and 'already got' xmls)