ganahan man gud ko nga i-separate ang database sa main program bay kay para dili mabug-atan, then no enough knowledge man gud ko anang XML nya i think a text file is one of the lightest file where you can store a large database.
ganahan man gud ko nga i-separate ang database sa main program bay kay para dili mabug-atan, then no enough knowledge man gud ko anang XML nya i think a text file is one of the lightest file where you can store a large database.
this implementation would not be efficient as encart, but if it's homework, this is okey.
suggestion for the structure would be like this:
1) master.properties -- holds all the property files
2) a.properties -- holds all the words as keywords and definitions as values
...
n) z.properties -- holds all the words that starts with z and definitions as values
so if you search for 'abacus', it starts with a, so you should load a.properties and get the value from the key 'abacus'.
make sense?
Puwede XML imo gamit pag-implement lang ug SAX para dili dako ug memory consumption. Kung gusto ka try this XStream - About XStream.
bro, try to download ebook for java... hatagan lng nya tka link kung maka-upload ko sa ako mga notes and ebooks and sample programs pud... simple ra au na ang java bro.
or adto sa national bookstore, look for a Java na book by Deitel & Deitel na current version. naa didto tanan. ayaw buy ana book na Java, C++ and C#. dapat Java ra jud pra concentrated ang topic
why do you need SAX/XML/Java Object for dictionary?
how difficult is dictionary with structure such as:
abacus=a calculator that performs arithmetic
as simple as ResourceBundle, it's easy. You dont need to have to EventHandler on visiting xml elements/attributes. For sure maps are faster than xml parsing.
Similar Threads |
|