posted 22 years ago
hi guys
here r the tips i used and that helped me
1. take a print out of the tree like sturcture of the following and stick it some place where u can stand and see them for about 20 mts everyday
visuals are better remembered than text
I/O
components
menu components
events
if u have a confusion between component or container coming first
remember "m" comes before "n"
for the events that do not have coressponding classes
remember IATA
these have only one method and hence no class
in the hierarchy structure, IATA and components come on the first line and the rest are below component
for the components that generate item events ... remember all the components beginning with "c" and "List"
the rest generate action events + "list" also
the more obvious ones "adjustement even" text event" there is no confusion or need to memorise
now to come to I/O
the File class does not create a file
Reader, Writer , InputStream, OutputStream are all abstract and cannot be instantiated
so if u see anywhere (new Reader) or any of the others mentioned above..... it is an error.
For object representation and primitive representation you would use the ObjectInputStream or DataInputStream (and ofcourse the coressponding writer)
for character encoding
we use InputStreamReader and OutputStreamWrtier
Only FileInputStream, ByteArrayInputStream .. the first line of heirarchy can take the File constraint, the rest cannot take the File constraint directly
For the RandomAcessFile
only two forms are possible "r", and "rw"
"rw" will create the file if the file does not exist
It takes the File constraint only
thats it guys
if anything else comes up i will post it for sure