Re: [xmlvm-users] java.awt.Color and family

[Wolfgang K. <wol...@xm...>]

I just committed a refactoring of the Objective C String class
implementation. java.lang.String is now based on NSString while
java.lang.StringBuffer is still based on NSMutableString. So Strings are
immutable now as they are in Java.

-- Wolfgang


On Sun, Oct 11, 2009 at 5:37 PM, Wolfgang Korn <wol...@xm...> wrote:

>  The patch you sent makes sense to me. Its pretty much the same as it is
> implemented in UIButton. To catch more than one event type with the same
> target it is possible to provide the ORed values of the corresponding
> UIControlEventValues. The iPhone SDK reference says:
>
> For example, you could request a certain action message be sent to a
> certain target when a finger touches down in a control or is dragged into it
> (UIControlEventTouchDown<http://developer.apple.com/iphone/library/documentation/UIKit/Reference/UIControl_Class/Reference/Reference.html#//apple_ref/c/econst/UIControlEventTouchDown>|
> UIControlEventTouchDragEnter<http://developer.apple.com/iphone/library/documentation/UIKit/Reference/UIControl_Class/Reference/Reference.html#//apple_ref/c/econst/UIControlEventTouchDragEnter>).
>
>
> -- Wolfgang
>
>
>
> Panayotis Katsaloulis wrote:
>
>
> On 11 Οκτ 2009, at 10:05 π.μ., Wolfgang Korn wrote:
>
> The only features a UIButton supports right now is creation, setting its
> title and to register an event handler. Especially all the color stuff
> you mentioned is currently not supported. What you saw in the Java
> version of UIButton (these methods based on java.awt.Color) are only
> used inside our Java emulator to create a UIAlertView with properly
> colored buttons. This Java implementation should be fixed as soon as we
> support color operations based in UIColor. And thanks for mentioning the
> UIButtonTest. Since this uses the java.awt.Color based methods it cannot
> be cross-compiled. I think we should remove that from the repository to
> avoid confusion.
>
> Coming to the String question. I lately noticed that the
> java_lang_String implementation is based on NSMutableString. This should
> be fixed since in Java strings are immutable. That's one thing I have on
> my list - but not with highest priority.
>
>
>
>
> So, for example I found that the UIControlEventValueChanged is not
> understood in the simulator, while it is perfectly understood in the native
> application.
> In order to implement things like that in the emulator, is something like
> this patch appropriate?
> it still has some issues but I just want to understand the main idea.
>
> In order to catch more than one of these events, should I double the
> request like here, or I can do something like
> ( UIControlEventTouchUpInside | UIControlEventValueChanged )
>
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!http://p.sf.net/sfu/devconference
>
> ------------------------------
>
> _______________________________________________
> xmlvm-users mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
>
>
>