From: Arno P. <ar...@pu...> - 2010-09-11 09:43:01
|
just to explain that change: NSTimer in Objective-C allows to trigger arbitrary methods. This is easy in Objective-C since this language is dynamically typed. So far we mimicked this in Java by using reflection. However, Java is a strongly typed language and doing it this way is not in the spirit of the language. That is why we introduced NSTimerDelegate. Note that at some point we need to make design decisions where we cannot easily map Objective-C to Java (another example are optional methods in Objective-C protocols. Here we also deviate from the "official Apple documentation"). Its a design decision but I believe its a good one. Arno On 9/11/10 2:35 AM, Panayotis Katsaloulis wrote: > Hello all! > > I'd like to ask you about the introduction of the NSTimerDelegate object. > I believe this idea was not so good. This is something that does not belong to the iOS sdk, and I strongly believer we should be as strict as possible with this, and violate it *only* there is NO other way of doing it. > We don't have specific documentation for xmlvm, so please at least b compatible with the documentation being written by others ;) ( namely Apple) > > > -- > Panayotis > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users |