Hi, me again. People say bad things about the French nationalised industries, but France Telecom just replaced 1/2 mile of cable through trees to my house within 24 hours of localising a fault to that area. For free. Vive la France!
I'm back online, so start asking!
WOW! I wish we still had Telefonica in Spain as nationalized industry. We don't! and they are now sub-contracting other enterprises to do the job, with not much of control.
Anyway, in relation to the project, I hope you have had time to see what I sent previously. I finished tha part of the job that jas to do with building the structure. It works and looks nice. Disregard the lack of exception controls. I know it is a bad practice, but it has been so much to me to try to understand Java and start this not easy homework, for which I only have until th eend of this month. I also have to study the matter. This homework is only to be allowed to do the exams, so I have decided to focus on the functionalities and, if I have time, to learn about exceptions and try to put more controls. Thanks for reading this long Paragraph() with XXX Phrases() and XXXXX Words() ;-)
So, you can see my solution and tell me whatever comes to your mind that you find useful.
I would like to know your opinion about, on one hand, declaring elementoCompuesto as an abstract class or even an interface and, on the other hand, insert a generic ArrayList<T> in this super-class. I still have to code some extra methods for showing, finding, replacing... contents of each class's ArrayList, that I would have to write time after time, adapting the almost identical code to each.
As for declaring an interface... would I lose the inheritances? I need to put some inheritance in my work, as they want me to use as much OOP concepts I could.
As for Abstract, would this help me in any way apart from "using abstract code" as an OOP concept itself?
Thankyou, guys, for your time.