cl3b34 / vocabuilder Goto Github PK

Currently I'm storing meta data from the SetOfCards and data from the Card
in all the records saved to RMS.

This is highly inefficient for parsing the data back. Data from the set
needs to be read all the time.

A new format for the metadata should be created. Since I want to keep using
the DataInputStream and DataOutputStream facilities, I have to create a
fixed format for the metadata in the *second* record or store a XML or JSON
version of the metadata in a String in the first record. 

The second option seems too complex for the current needs, since I don't
need to transfer the data anywhere, creating a parser would be too much
overhead.

For the first option the record format should be something like:

setOfCardsTitle setOfCardsIsDone setOfCardsStudyTime totalCardsDisplayed
lastTimeSetViewed lastTimeSetMarkedDone markedDoneSetCounter

which translates to the Java types:

String boolean long int long long int int

The metadata is stored in the second record because I want to create a
'file format version' metadata so I'm able to maintain backwards
compatibility in case I need to change the file format again. This metadata
will be stored in the *first* record and has the format:

fileFormatVersion

int

The data about the FlashCards will be stored from the 3rd record on and
follows the format:

cardSideOneTitle cardSideOneText cardSideTwoTitle cardSideTwoText
cardIsDone cardTip cardViewedCounter cardMarkedDoneCounter
cardLastTimeViewed cardLastTimeMarkedDone 

String String String String boolean String int int long long 

After 'turning' show the finnish word still on the page; easier to 
remember when you can see the finnish and the english word on the same 
page when guessed incorrectly

If you press the 'red' (hang up) button while using the application, the
current state is lost (studied cards).

Before it was saved during the application exiting process, but I changed
it in issue 3 to save when showing the statistics page. 

The current version of the application comes with a list of card built-in.

The list is included in the JAR and packaged with the application.

We want to allow the user to load a new list via http and then manage the 
lists locally, deciding which list he wants to load for studying.

That way, we can have several smaller lists on different subjects (say 
body parts, animals, objects, etc) and also introduce different languages 
(a user could have a list of Italian-English words and another of 
Portuguese-English that he would load at will).

What steps will reproduce the problem?
None.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

Ranking between test takers would be nice additional feature. Should use
the network and nicknames.

In certain handsets the very long list of words that currently accompany
the application (like the Portuguese/english, with 9634 cards) cannot be
loaded without risking an OutOfMemoryException.

This is mainly due to the very limited amount of memory on the handsets. 

In order to overcome this limitation and make these very long lists more
usable, I need to break them in smaller lists with a maximum of 2000 cards
each, which can then be loaded and studied at will.

What steps will reproduce the problem?
1. Exit from card screen
2. No option to exit gracefully

Exit option 

Currently the application only supports one list of cards that comes built 
in.

We need to be able to load and unload lists at the user's criteria.

With that, it will be possible to use the application to learn several 
languages by just loading a new list.

What steps will reproduce the problem?
1. Create data file which contains cyrillic letters in utf-8 encoding.
2. Build and run vocabuilder
3. Cyrillic letters will be dispalyed as garbage

What is the expected output? What do you see instead?
Correct displaing of cyrillic letters is expected

What version of the product are you using? On what operating system?
Nokia E63 with EN/RU/UA language support

Please provide any additional information below.