Re: [xmlvm-users] NsTimerDelegate

[Arno P. <ar...@pu...>]

I'm sure there are plenty of "dark corners" in XMLVM where we are (not 
yet) consistent.  :-)  But I'm sure that will be cleaned up eventually.

A support package for non-standard classes/interfaces is a good idea!

Arno


On 9/11/10 4:08 AM, Panayotis Katsaloulis wrote:
>
> 11 Σεπ 2010, 1:59 μ.μ., ο/η Arno Puder<ar...@pu...>  έγραψε:
>
>>
>> well, I was referring to the fact that sometimes we map Objective-C
>> protocols to Java class and sometimes to Java interfaces. Of course we
>> do this consistently, but its a design decision. Likewise its a design
>> decision to map Objective-C @selector to a strongly-typed interface in
>> those cases where it is possible.
>>
>> Arno
>
> Well, probably I am missing something, but I think that this is not always the case. There are some locations, like the one I mentioned before, that don't follow the strongly typed nature of Java.
> In any case, if you really believe that a strongly typed declaration is preferred, I'd at least suggest to create a new package for all these situations, something like org.xmlvm.iphone.support (or anything similar) and keep all non-standard objects there, while having heavy documentation on these classes (although still I believe is not the best solution)
> ------------------------------------------------------------------------------
> 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