Closed cjcodeproj closed 4 months ago
What the code considers elements are tricky, because they have share attributes from the parent object that contain them.
For example, on a Van Halen CD, the album artist is obviously Van Halen. And if individual songs in the XML structure do not have <catalog>
elements that identify the artist as Van Halen, then the Song
object needs to reference the Album
object and grab the artist values from that.
Which is good, because the code is capable of doing all the heavy lifting, and it's a better trade off than having more XML elements than necessary. I should only have to list the artist as Van Halen once.
Create a class hierarchy to handle songs.
Create a code structure to handle the
<elements>
element, and the child elements<song>
and<dialogue>
.