xmlvm-users — For current and interested XMLVM users, for public discussions and anouncements.

Re: [xmlvm-users] Synchronized Keyword

[Markus H. <ma...@ti...>]

Hi Sascha,

I was trying to build the typical "Hello World"-application these  
days: a twitter client :)

I'm using the twitter4j API http://yusuke.homeip.net/twitter4j/en/index.html 
  and was trying to convert that.

It supports some asynchronous stuff and uses threads and synchronized  
for that. I don't really need the asynchronous part right now, but I  
found it interesting to just put the whole library in and see how good  
XMLVM could convert it. There were lots of mappings missing, but I can  
do those myself. (They can be found in my git repository http://github.com/tisoft/xmlvm 
) But the synchronized stuff is too low for me level right now. Since  
I don't need it right now, I just have commented it out in the xsl, so  
that I can continue without it, but would of course be great if it  
actually works.

Markus

Am 17.10.2009 um 00:28 schrieb Sascha Haeberling:

> Hi Markus
>
> I am not familiar with the synchronized part of the stylesheet.  
> Thank you for pointing out the typo! We will try to take a look at  
> this. I don't think we are supporting Threads properly yet, though.  
> Can you let us know what you are trying to do?
>
> Thanks
> // Sascha
>
> On Fri, Oct 16, 2009 at 9:45 PM, Markus Heberling <ma...@ti...>  
> wrote:
> Hi,
>
> I have a problem with the synchronized keyword. The generated ObjC- 
> code does not compile. First error is a simple spelling error: http://github.com/tisoft/xmlvm/commit/2d75e56167dd41eee2705dd110895308ac256a80
>
> But fixing that doesn't help since the generated code is still wrong.
>
> Just try to convert a simple class like:
>
> public class X{
>        public void test(){
>                synchronized(this){
>                }
>        }
> }
>
> This creates some uncompilable stuff in ObjC:
>
> - (void) test
> {
>    XMLVMElem _stack[2];
>    XMLVMElem _locals[3];
>
>    int _sp = 0;
>    XMLVMElem _op1, _op2, _op3;
>    NSAutoreleasePool* _pool = [[NSAutoreleasePool alloc] init];
>    _locals[0].o = self;
>    label1:;
>    _stack[_sp++].o = _locals[0].o;
>    _op1 = _stack[_sp - 1];
>    _stack[_sp++] = _op1;
>    _op1.o = _stack[--_sp].o;
>    _locals[1].o = _op1.o;
>    _op1.o = _stack[--_sp].o;
>        @synchronized(_op1.o) {
>    @try {
>    _stack[_sp++].o = _locals[1].o;
>    }
>    } @catch (java_lang_Exception* _ex) {
>        _stack[_sp++].o = _ex;
>        goto label3;
>    }
>    goto label0;
>    @try {
>    label3:;
>    _op1.o = _stack[--_sp].o;
>    _locals[2].o = _op1.o;
>    _stack[_sp++].o = _locals[1].o;
>    }
>    } @catch (java_lang_Exception* _ex) {
>        _stack[_sp++].o = _ex;
>        goto label3;
>    }
>    _stack[_sp++].o = _locals[2].o;
>    _op1.o = _stack[--_sp].o;
>    @throw _op1.o;
>    label0:;
>    [_pool release];
>    return;
> }
>
> I'm not able to fix it myself, since I don't understand the  
> converting stuff yet, so it would be great if someone of you could  
> look into this.
>
> Greetings,
> Markus
> ------------------------------------------------------------------------------
> 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 list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
>

[xmlvm-users] memory management (again)

[Panayotis K. <pan...@pa...>]

In the initialization code of UIWindow, there is a [self retain]
I suspect that this is because, after exiting the  
"applicationDidFinishLaunching" method, UIWindow will get released  
(from the autorelease pool).
Although it's a convenient thing and helpful for starters, I believe  
it's a dangerous approach.

if we use more complex systems, like UIViewControllers (hint  
hint :P ), then we don't have just one and we change and replace these  
objects all the time.
So just retaining them like in UIWindow is not really acceptable.

Of course, if we have just a reference of them as a variable, and  
assign the UIWindow there, it's enough.
This is a common practive in UIViewControllers, anyway
But, it's not what it's done, up to now - and it seems like a non- 
uniformality

That's my questioning...

I'll be happy to hear   thoughts about it :)

Re: [xmlvm-users] Synchronized Keyword

[Sascha H. <sa...@xm...>]

Hi Markus

I am not familiar with the synchronized part of the stylesheet. Thank you
for pointing out the typo! We will try to take a look at this. I don't think
we are supporting Threads properly yet, though. Can you let us know what you
are trying to do?

Thanks
// Sascha

On Fri, Oct 16, 2009 at 9:45 PM, Markus Heberling <ma...@ti...> wrote:

> Hi,
>
> I have a problem with the synchronized keyword. The generated ObjC-code
> does not compile. First error is a simple spelling error:
> http://github.com/tisoft/xmlvm/commit/2d75e56167dd41eee2705dd110895308ac256a80
>
> But fixing that doesn't help since the generated code is still wrong.
>
> Just try to convert a simple class like:
>
> public class X{
>        public void test(){
>                synchronized(this){
>                }
>        }
> }
>
> This creates some uncompilable stuff in ObjC:
>
> - (void) test
> {
>    XMLVMElem _stack[2];
>    XMLVMElem _locals[3];
>
>    int _sp = 0;
>    XMLVMElem _op1, _op2, _op3;
>    NSAutoreleasePool* _pool = [[NSAutoreleasePool alloc] init];
>    _locals[0].o = self;
>    label1:;
>    _stack[_sp++].o = _locals[0].o;
>    _op1 = _stack[_sp - 1];
>    _stack[_sp++] = _op1;
>    _op1.o = _stack[--_sp].o;
>    _locals[1].o = _op1.o;
>    _op1.o = _stack[--_sp].o;
>        @synchronized(_op1.o) {
>    @try {
>    _stack[_sp++].o = _locals[1].o;
>    }
>    } @catch (java_lang_Exception* _ex) {
>        _stack[_sp++].o = _ex;
>        goto label3;
>    }
>    goto label0;
>    @try {
>    label3:;
>    _op1.o = _stack[--_sp].o;
>    _locals[2].o = _op1.o;
>    _stack[_sp++].o = _locals[1].o;
>    }
>    } @catch (java_lang_Exception* _ex) {
>        _stack[_sp++].o = _ex;
>        goto label3;
>    }
>    _stack[_sp++].o = _locals[2].o;
>    _op1.o = _stack[--_sp].o;
>    @throw _op1.o;
>    label0:;
>    [_pool release];
>    return;
> }
>
> I'm not able to fix it myself, since I don't understand the converting
> stuff yet, so it would be great if someone of you could look into this.
>
> Greetings,
> Markus
>
> ------------------------------------------------------------------------------
> 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 list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
>

[xmlvm-users] Synchronized Keyword

[Markus H. <ma...@ti...>]

Hi,

I have a problem with the synchronized keyword. The generated ObjC- 
code does not compile. First error is a simple spelling error: http://github.com/tisoft/xmlvm/commit/2d75e56167dd41eee2705dd110895308ac256a80

But fixing that doesn't help since the generated code is still wrong.

Just try to convert a simple class like:

public class X{
	public void test(){
		synchronized(this){
		}
	}
}

This creates some uncompilable stuff in ObjC:

- (void) test
{
     XMLVMElem _stack[2];
     XMLVMElem _locals[3];

     int _sp = 0;
     XMLVMElem _op1, _op2, _op3;
     NSAutoreleasePool* _pool = [[NSAutoreleasePool alloc] init];
     _locals[0].o = self;
     label1:;
     _stack[_sp++].o = _locals[0].o;
     _op1 = _stack[_sp - 1];
     _stack[_sp++] = _op1;
     _op1.o = _stack[--_sp].o;
     _locals[1].o = _op1.o;
     _op1.o = _stack[--_sp].o;
   	@synchronized(_op1.o) {
     @try {
     _stack[_sp++].o = _locals[1].o;
     }
     } @catch (java_lang_Exception* _ex) {
         _stack[_sp++].o = _ex;
         goto label3;
     }
     goto label0;
     @try {
     label3:;
     _op1.o = _stack[--_sp].o;
     _locals[2].o = _op1.o;
     _stack[_sp++].o = _locals[1].o;
     }
     } @catch (java_lang_Exception* _ex) {
         _stack[_sp++].o = _ex;
         goto label3;
     }
     _stack[_sp++].o = _locals[2].o;
     _op1.o = _stack[--_sp].o;
     @throw _op1.o;
     label0:;
     [_pool release];
     return;
}

I'm not able to fix it myself, since I don't understand the converting  
stuff yet, so it would be great if someone of you could look into this.

Greetings,
Markus

Re: [xmlvm-users] selectors and xmlvm

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

I guess you basically understand how we map the Cocoa API to the Java
version ;-) So probably your question is about the selector argument of
the call you pointed us to.

Basically we decided to map this kind of API to a strongly typed
interface. For the implementation that means

    * we define an interface which specifies a callback method
    * so our API's version of the method you mentioned does not have the
      selector parameter
    * our Objective C implementation would pass
      action:@selector(<callbackMethod>) to initWithBarButtonSystemItem

As an example have a look at the already existing method
UIControl.addTarget in the following files: UIControl.java,
UIControlDelegate.java and org_xmlvm_iphone_UIControl.m

If this doesn't help please let me know.

-- Wolfgang


Panayotis Katsaloulis wrote:
> Here is another question ;-)
> I'm sure you'll get sick of me :P
>
> This time has to do with selectors.
> I am not familiar with the low level details of the conversion of java  
> bytecode to XML. I hope the answer to this question is not obvious!
>
> How are selectors actually handled by this system? How do you think  
> they can be emulated in the native part?
>
> Let's take this example found here:
>
> http://developer.apple.com/iphone/library/documentation/UIKit/Reference/UIBarButtonItem_Class/Reference/Reference.html#/ 
> /apple_ref/occ/instm/UIBarButtonItem/ 
> initWithBarButtonSystemItem:target:action:
>
> How do you propose to implement this in java and native objective c?
>
> ------------------------------------------------------------------------------
> 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 list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>   

[xmlvm-users] selectors and xmlvm

[Panayotis K. <pan...@pa...>]

Here is another question ;-)
I'm sure you'll get sick of me :P

This time has to do with selectors.
I am not familiar with the low level details of the conversion of java  
bytecode to XML. I hope the answer to this question is not obvious!

How are selectors actually handled by this system? How do you think  
they can be emulated in the native part?

Let's take this example found here:

http://developer.apple.com/iphone/library/documentation/UIKit/Reference/UIBarButtonItem_Class/Reference/Reference.html#/ 
/apple_ref/occ/instm/UIBarButtonItem/ 
initWithBarButtonSystemItem:target:action:

How do you propose to implement this in java and native objective c?

Re: [xmlvm-users] Protocols, Interfaces & Delegates

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

I agree with you - the implementation should be consistent throughout
the various classes. Could you please provide a link to the
files/classes where you saw the mixture of interfaces and abstract
classes? So we have the chance to review that and make a decision how
the implementation actually should look like (and that should also
result in the suggestion you asked for  ;-)  ). After a decision has been
made it might be necessary to refactor the mixture you mentioned a bit.

-- Wolfgang


Panayotis Katsaloulis wrote:
> Hello
>
> I am trying to implement the UINavigationBar item.
> So I need to provide a delegate.
>
> I've seen that in your code for protocols you've a mixture of java  
> interfaces and abstract methods/classes.
> Why is that? What do you suggest?
>
> My opinion is to stay with interfaces, since with an interface you  
> don't nail down the type of object a delegate will be (and that's the  
> idea of the delegate, right?)
>
> I'd also suggest that the code should be consistent and probably  
> change that overall in the project (although I know it's not a high  
> priority)
>
> ------------------------------------------------------------------------------
> 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 list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>   

[xmlvm-users] Protocols, Interfaces & Delegates

[Panayotis K. <pan...@pa...>]

Hello

I am trying to implement the UINavigationBar item.
So I need to provide a delegate.

I've seen that in your code for protocols you've a mixture of java  
interfaces and abstract methods/classes.
Why is that? What do you suggest?

My opinion is to stay with interfaces, since with an interface you  
don't nail down the type of object a delegate will be (and that's the  
idea of the delegate, right?)

I'd also suggest that the code should be consistent and probably  
change that overall in the project (although I know it's not a high  
priority)

Re: [xmlvm-users] SDK update to 3.1

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

I took your comment seriously and I can understand your concerns. So I
changed the Makefile slightly. The Makefile's default iPhone SDK is still
3.1 but this setting can now be overwritten by setting an environment
variable IPHONE_SDK_HOME pointing to your SDK of choice. This is also
helpful in case someone didn't install the SDK to the default location.

-- Wolfgang


On Wed, Oct 14, 2009 at 2:33 AM, Panayotis Katsaloulis <
pan...@pa...> wrote:

>
> On 13 Οκτ 2009, at 3:42 μ.μ., Wolfgang Korn wrote:
>
>  Hi all,
>>
>> I just want to let you know, that we updated XMLVM to use the current
>> iPhone 3.1.2 SDK. In order to compile the samples for the SDKs iPhone
>> simulator, you have to update you iPhone SDK to the latest version.
>>
>> -- Wolfgang
>>
>>
> Why is that?
> A lot of people haven't updated their device yet, and forcing to compile
> only on the highest version shouldn't be necessary (after my opinion).
> Especially since, when compiling for 3.0 can be perfectly used under 3.0!

[xmlvm-users] (no subject)

[Nathan R. <na...@to...>]

Sent from my iPhone

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

[Sascha H. <sa...@xm...>]

Hi,
well 5600 LOC sounds much better. But again, it is quite big and I would
like you to give us feedback as early as possible. While we highly look
forward to your contribution, we should make sure you don't make major
changes that we might have disagreements on. We probably won't but as I
haven't seen your patch, I want to make sure no time is wasted. So try to
assemble a patch as soon as possible for us to reviews.

In general, the smaller a patch the better it is and the more effective it
is for us to review.

About the error: Make sure your patch is created from the correct root. The
root should be:
http://xmlvm.svn.sourceforge.net/svnroot/xmlvm/trunk/xmlvm/

So in your patch file, the paths should start with 'src/'. If you don't get
it to work, feel free to send the patch to my e-mail address and I will take
a look.

Thanks
// Sascha

PS: I am sure you read it, but just to remind you: Please make sure your
code is formatted according to our code guidelines and is well documented (
http://xmlvm.org/contribute/) This will help us maintain a good quality of
the code and will make it easier for us to review. Thanks!


2009/10/14 Panayotis Katsaloulis <pan...@pa...>

>
> On 14 Οκτ 2009, at 1:49 π.μ., Sascha Haeberling wrote:
>
> > Hi Panayotis,
> >
> > first of all, I think the earlier you have a patch that is
> > consistent and doesn't break anything, the better it is. If the
> > patch is too large it will take us too long to review it. So I think
> > it is your responsibility to try to break the patch down into
> > manageable chunks.
> >
> > 390.000 lines of code sounds strange to me. Does this include a
> > bunch of auto-generates empty stubs?
> >
> > // Sascha
>
> No, but it had some refactoring, since as I said I separated the view
> of the GUI elements from the model, and so the public methods (of the
> GUI elements again) are clear and reflect what they really support.
>  They are not really 390K of code, since diff puts some extra headers
> in the beginning and in the end.
> A typical
> diff -ruN  xmlvm xmlvm.patched  | grep '^\+' | wc
> gives ~5600 lines of code
>
> The changes now are in *so* many places that I don't think it's
> possible to make smaller patches. I can only break it into (e.g.)
> patches for obj-c support library and patches for xmlvm core itself.
> But I'm not sure if this will help at all :)
> I can not even distinguish the patches for the demos, since some of
> them depend on the support library
>
> PS: I tried to upload the patch to http://xmlvm-reviews.appspot.com/
> new but every time I select a file I get an error message saying
> Patch set contains no recognizable patches
>
>
> PS2: Is there already a tool to create auto-generated empty stubs?
> Because I am coding one right now, and if there is it will save my time.
>
> ------------------------------------------------------------------------------
> 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 list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>

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

[Panayotis K. <pan...@pa...>]

On 14 Οκτ 2009, at 1:49 π.μ., Sascha Haeberling wrote:

> Hi Panayotis,
> ...
> 390.000 lines of code sounds strange to me. Does this include a  
> bunch of auto-generates empty stubs?

oops, you misunderstood
390.000 BYTES of code ;)

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

[Panayotis K. <pan...@pa...>]

On 14 Οκτ 2009, at 1:49 π.μ., Sascha Haeberling wrote:

> Hi Panayotis,
>
> first of all, I think the earlier you have a patch that is  
> consistent and doesn't break anything, the better it is. If the  
> patch is too large it will take us too long to review it. So I think  
> it is your responsibility to try to break the patch down into  
> manageable chunks.
>
> 390.000 lines of code sounds strange to me. Does this include a  
> bunch of auto-generates empty stubs?
>
> // Sascha

No, but it had some refactoring, since as I said I separated the view  
of the GUI elements from the model, and so the public methods (of the  
GUI elements again) are clear and reflect what they really support.
  They are not really 390K of code, since diff puts some extra headers  
in the beginning and in the end.
A typical
diff -ruN  xmlvm xmlvm.patched  | grep '^\+' | wc
gives ~5600 lines of code

The changes now are in *so* many places that I don't think it's  
possible to make smaller patches. I can only break it into (e.g.)  
patches for obj-c support library and patches for xmlvm core itself.
But I'm not sure if this will help at all :)
I can not even distinguish the patches for the demos, since some of  
them depend on the support library

PS: I tried to upload the patch to http://xmlvm-reviews.appspot.com/ 
new but every time I select a file I get an error message saying
Patch set contains no recognizable patches


PS2: Is there already a tool to create auto-generated empty stubs?
Because I am coding one right now, and if there is it will save my time.

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

[Sascha H. <sa...@xm...>]

Hi Panayotis,
first of all, I think the earlier you have a patch that is consistent and
doesn't break anything, the better it is. If the patch is too large it will
take us too long to review it. So I think it is your responsibility to try
to break the patch down into manageable chunks.

390.000 lines of code sounds strange to me. Does this include a bunch of
auto-generates empty stubs?

// Sascha

2009/10/14 Panayotis Katsaloulis <pan...@pa...>

>
> On 14 Οκτ 2009, at 12:09 π.μ., Wolfgang Korn wrote:
>
> > 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
>
> Nice!
>
> I was thinking that, since I do a lot of work on the library and on
> the obj-c part, I am afraid that after some time without reviewing my
> patches, it would be impossible to synchronize.
> I have a few issues before I finish my part, but the work that I've
> done is already a lot. Right now, all java-based things work, and some
> native need to tweak them a bit more.
>
> Do you believe should i do a patch even at this time, and upload it to
> the site?
> There are a lot of changes and they will accumulate when time goes by.
> I don't want to fork, I want to stay in your track.
>
> I think the best thing I could do is create a super-patch with all
> changes (I think from version 536) and upload it there.
> A diif with "diff -ruN" is more or less 390K !!!
> What do you think?
>
> ( Right now I am writing a tool to automatically create skeleton files
> from java files to objective-c files, so that creating the native part
> from the java library to be as easy as possible)
>
> ------------------------------------------------------------------------------
> 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 list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>

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

[Panayotis K. <pan...@pa...>]

On 14 Οκτ 2009, at 12:09 π.μ., Wolfgang Korn wrote:

> 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

Nice!

I was thinking that, since I do a lot of work on the library and on  
the obj-c part, I am afraid that after some time without reviewing my  
patches, it would be impossible to synchronize.
I have a few issues before I finish my part, but the work that I've  
done is already a lot. Right now, all java-based things work, and some  
native need to tweak them a bit more.

Do you believe should i do a patch even at this time, and upload it to  
the site?
There are a lot of changes and they will accumulate when time goes by.  
I don't want to fork, I want to stay in your track.

I think the best thing I could do is create a super-patch with all  
changes (I think from version 536) and upload it there.
A diif with "diff -ruN" is more or less 390K !!!
What do you think?

( Right now I am writing a tool to automatically create skeleton files  
from java files to objective-c files, so that creating the native part  
from the java library to be as easy as possible)

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
>
>
>
>

[xmlvm-users] SDK update to 3.1

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

Hi all,

I just want to let you know, that we updated XMLVM to use the current
iPhone 3.1.2 SDK. In order to compile the samples for the SDKs iPhone
simulator, you have to update you iPhone SDK to the latest version.

-- Wolfgang

Re: [xmlvm-users] Update of my work

[Panayotis K. <pan...@pa...>]

On 12 Οκτ 2009, at 7:50 μ.μ., Wolfgang Korn wrote:

> It looks like you are doing a lot of work to improve XMLVM ;-)
>
> If there is a UIColor implementation it should be possible to update  
> the
> Java version of UIAlertView to make use of this. I think I will look  
> at
> this after all your patches have been merged. The current  
> java.awt.Color
> based methods should be deleted if possible since they seem to cause
> some confusion.
>
> -- Wolfgang


Exactly that is what I did. Every (visible) Color reference went  
away :).
The same with Font which become UIFont.
Now I am rearranging and rewriting the GUI objects, to clearly  
indicate what is in the API and what is in the emulator.
In other words a clear separation of Model and View ;)
The reason for this is I was confused in the beginning what was  
supported and what wasn't. (Remember UIButton test?)
With this separation will be clear what is emulation-specific, what  
could be implemented (but it is not implemented yet) and what is  
already implemented (sort of).
And in general, the code will be much more clear!

As it goes, the full patch will be really really big :P

Re: [xmlvm-users] Update of my work

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

It looks like you are doing a lot of work to improve XMLVM ;-)

If there is a UIColor implementation it should be possible to update the
Java version of UIAlertView to make use of this. I think I will look at
this after all your patches have been merged. The current java.awt.Color
based methods should be deleted if possible since they seem to cause
some confusion.

-- Wolfgang


Panayotis Katsaloulis wrote:
> Since it seems I am creating a whole bunch of patches, I've decided to  
> send them all together when I have fairly finish a large part of it.
> Still I decided to give here an update of my process, so that there is  
> no need for someone to do a duplicate work.
>
> In general I have implemented UISlider, UISegmentedControl and  
> UIProgressView.
> I have also fixed UIColor, which is working as expected now (yes, I've  
> taken care not to break the UIButton alchemy you do there for alerts).
> Also properties hidden, userInteractionEnabled and background work as  
> expected (in both obj-c and simulator)
>
> I've done also some small fixes here and there, which I can't  
> remember ;-) 
>   
>
> ------------------------------------------------------------------------------
> 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 list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>   

Re: [xmlvm-users] Maths

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

The problem is that right now there is no Objective C wrapper for
java.lang.CharSequence. How did you (Java) compile your code? Did you
compile it against the regular Android SDK? That might cause the problem
since the original setText() expects a CharSequence. Try compiling it
against XMLVM's compatibility library instead.

-- Wolfgang


Joseph Rukshan Fonseka wrote:
> So how come the code below fails for me? It gives me this error:
> It seems to want to use java_lang_CharSequence.h, how can I avoid this?
>
> com_home_imageviewer_ImageViewer.m:8:35: error:
> java_lang_CharSequence.h: No such file or directory
> com_home_imageviewer_ImageViewer.m: In function
> ‘-[com_home_imageviewer_ImageViewer onCreate___android_os_Bundle:]’:
> com_home_imageviewer_ImageViewer.m:132: warning:
> ‘android_widget_Button’ may not respond to
> ‘-setText___java_lang_CharSequence:’
> com_home_imageviewer_ImageViewer.m:132: warning: (Messages without a
> matching method signature
> com_home_imageviewer_ImageViewer.m:132: warning: will be assumed to
> return ‘id’ and accept
> com_home_imageviewer_ImageViewer.m:132: warning: ‘...’ as arguments.)
> make: *** [obj/com_home_imageviewer_ImageViewer.o] Error 1
>
>
> public class ImageViewer extends Activity {
>     /** Called when the activity is first created. */
>     @SuppressWarnings("deprecation")
> @Override
>     public void onCreate(Bundle savedInstanceState) {
>         super.onCreate(savedInstanceState);
>
>         
>
>         AbsoluteLayout layout = new AbsoluteLayout(this);
>         layout.setLayoutParams(new
> LayoutParams(LayoutParams.FILL_PARENT, LayoutParams.FILL_PARENT));
>         ImageView viewer = new ImageView(this);    
>         viewer.setImageResource(R.drawable.cat);
>         layout.addView(viewer, new
> AbsoluteLayout.LayoutParams(AbsoluteLayout.LayoutParams.WRAP_CONTENT,
> AbsoluteLayout.LayoutParams.WRAP_CONTENT, 0, 100));
>         Button text = new Button(this);
>         layout.addView(text, new
> AbsoluteLayout.LayoutParams(AbsoluteLayout.LayoutParams.WRAP_CONTENT,
> AbsoluteLayout.LayoutParams.WRAP_CONTENT, 0, 0));
>         setContentView(layout);
>
>         
>
>         text.setText("fffff"));
>     }
> }
>
>
> On 12/10/2009, at 10:05 PM, Wolfgang Korn wrote:
>
>> Currently our Android compativility library only has a method
>> TextView.setText(String). With respect to the allowed input types
>> this less flexible than the original Android method but it works.
>> Since java.lang.String implements java.lang.CharSequence code using
>> this method compiles with our compat lib as well as with the regular
>> Android SDK.
>>
>> -- Wolfgang
>>
>> Joseph Rukshan Fonseka wrote:
>>> Thanks that worked. How does one use the TextView.setText()  thats
>>> already defined in the TextWidget? 
>>>
>>> When it cross compiles to iphone I get this error, I understand that
>>> is because android's setText takes a CharSequence. But just
>>> wondering how the setText in compat library can be called.
>>>
>>> com_home_imageviewer_ImageViewer.m:9:35: error:
>>> java_lang_CharSequence.h: No such file or directory
>>> com_home_imageviewer_ImageViewer.m: In function
>>> ‘-[com_home_imageviewer_ImageViewer onCreate___android_os_Bundle:]’:
>>> com_home_imageviewer_ImageViewer.m:164: warning:
>>> ‘android_widget_Button’ may not respond to
>>> ‘-setText___java_lang_CharSequence:’
>>> com_home_imageviewer_ImageViewer.m:164: warning: (Messages without a
>>> matching method signature
>>> com_home_imageviewer_ImageViewer.m:164: warning: will be assumed to
>>> return ‘id’ and accept
>>> com_home_imageviewer_ImageViewer.m:164: warning: ‘...’ as arguments.)
>>> make: *** [obj/com_home_imageviewer_ImageViewer.o] Error 1
>>>
>>>
>>>
>>> On 12/10/2009, at 12:55 AM, Wolfgang Korn wrote:
>>>
>>>> It seems that the pop2 instruction is used to clean up the stack
>>>> here. Your code computes minimum and maximum of two values but
>>>> simply ignores the computed value. To remove this computation
>>>> result pop2 seems to be used. Until we implement the missing
>>>> instruction you can simply assign the results from the calls to
>>>> Math.min and Math.max to variables. In my case this removed the
>>>> pop2 from the class file.
>>>>
>>>> One last thing: Could you please upload a patch file for your
>>>> additions to Math.m/h to our review site
>>>> (http://xmlvm-reviews.appspot.com/) or create a patch and send that
>>>> instead of sending the whole files? This makes it easier to merge
>>>> in case if concurrent modifications.
>>>>
>>>> -- Wolfgang
>>>>
>>> ------------------------------------------------------------------------
>>>
>>> ------------------------------------------------------------------------------
>>> 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 list
>>> xml...@li...
>>> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>>>   
>>
>>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> 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 list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>   

Re: [xmlvm-users] Maths

[Joseph R. F. <ruk...@op...>]

So how come the code below fails for me? It gives me this error:
It seems to want to use java_lang_CharSequence.h, how can I avoid this?

com_home_imageviewer_ImageViewer.m:8:35: error:  
java_lang_CharSequence.h: No such file or directory
com_home_imageviewer_ImageViewer.m: In function ‘- 
[com_home_imageviewer_ImageViewer onCreate___android_os_Bundle:]’:
com_home_imageviewer_ImageViewer.m:132: warning:  
‘android_widget_Button’ may not respond to ‘- 
setText___java_lang_CharSequence:’
com_home_imageviewer_ImageViewer.m:132: warning: (Messages without a  
matching method signature
com_home_imageviewer_ImageViewer.m:132: warning: will be assumed to  
return ‘id’ and accept
com_home_imageviewer_ImageViewer.m:132: warning: ‘...’ as arguments.)
make: *** [obj/com_home_imageviewer_ImageViewer.o] Error 1


public class ImageViewer extends Activity {
     /** Called when the activity is first created. */
     @SuppressWarnings("deprecation")
	@Override
     public void onCreate(Bundle savedInstanceState) {
         super.onCreate(savedInstanceState);

         AbsoluteLayout layout = new AbsoluteLayout(this);
         layout.setLayoutParams(new LayoutParams 
(LayoutParams.FILL_PARENT, LayoutParams.FILL_PARENT));
         ImageView viewer = new ImageView(this);
         viewer.setImageResource(R.drawable.cat);
         layout.addView(viewer, new AbsoluteLayout.LayoutParams 
(AbsoluteLayout.LayoutParams.WRAP_CONTENT,  
AbsoluteLayout.LayoutParams.WRAP_CONTENT, 0, 100));
         Button text = new Button(this);
         layout.addView(text, new AbsoluteLayout.LayoutParams 
(AbsoluteLayout.LayoutParams.WRAP_CONTENT,  
AbsoluteLayout.LayoutParams.WRAP_CONTENT, 0, 0));
         setContentView(layout);

         text.setText("fffff"));
     }
}


On 12/10/2009, at 10:05 PM, Wolfgang Korn wrote:

> Currently our Android compativility library only has a method  
> TextView.setText(String). With respect to the allowed input types  
> this less flexible than the original Android method but it works.  
> Since java.lang.String implements java.lang.CharSequence code using  
> this method compiles with our compat lib as well as with the regular  
> Android SDK.
>
> -- Wolfgang
>
> Joseph Rukshan Fonseka wrote:
>>
>> Thanks that worked. How does one use the TextView.setText()  thats  
>> already defined in the TextWidget?
>>
>> When it cross compiles to iphone I get this error, I understand  
>> that is because android's setText takes a CharSequence. But just  
>> wondering how the setText in compat library can be called.
>>
>> com_home_imageviewer_ImageViewer.m:9:35: error:  
>> java_lang_CharSequence.h: No such file or directory
>> com_home_imageviewer_ImageViewer.m: In function ‘- 
>> [com_home_imageviewer_ImageViewer onCreate___android_os_Bundle:]’:
>> com_home_imageviewer_ImageViewer.m:164: warning:  
>> ‘android_widget_Button’ may not respond to ‘- 
>> setText___java_lang_CharSequence:’
>> com_home_imageviewer_ImageViewer.m:164: warning: (Messages without  
>> a matching method signature
>> com_home_imageviewer_ImageViewer.m:164: warning: will be assumed to  
>> return ‘id’ and accept
>> com_home_imageviewer_ImageViewer.m:164: warning: ‘...’ as arguments.)
>> make: *** [obj/com_home_imageviewer_ImageViewer.o] Error 1
>>
>>
>>
>> On 12/10/2009, at 12:55 AM, Wolfgang Korn wrote:
>>
>>> It seems that the pop2 instruction is used to clean up the stack  
>>> here. Your code computes minimum and maximum of two values but  
>>> simply ignores the computed value. To remove this computation  
>>> result pop2 seems to be used. Until we implement the missing  
>>> instruction you can simply assign the results from the calls to  
>>> Math.min and Math.max to variables. In my case this removed the  
>>> pop2 from the class file.
>>>
>>> One last thing: Could you please upload a patch file for your  
>>> additions to Math.m/h to our review site (http://xmlvm-reviews.appspot.com/ 
>>> ) or create a patch and send that instead of sending the whole  
>>> files? This makes it easier to merge in case if concurrent  
>>> modifications.
>>>
>>> -- Wolfgang
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> 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 list
>> xml...@li...
>> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>>
>
>

Re: [xmlvm-users] Maths

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

Currently our Android compativility library only has a method
TextView.setText(String). With respect to the allowed input types this
less flexible than the original Android method but it works. Since
java.lang.String implements java.lang.CharSequence code using this
method compiles with our compat lib as well as with the regular Android SDK.

-- Wolfgang


Joseph Rukshan Fonseka wrote:
> Thanks that worked. How does one use the TextView.setText()  thats
> already defined in the TextWidget? 
>
> When it cross compiles to iphone I get this error, I understand that
> is because android's setText takes a CharSequence. But just wondering
> how the setText in compat library can be called.
>
> com_home_imageviewer_ImageViewer.m:9:35: error:
> java_lang_CharSequence.h: No such file or directory
> com_home_imageviewer_ImageViewer.m: In function
> ‘-[com_home_imageviewer_ImageViewer onCreate___android_os_Bundle:]’:
> com_home_imageviewer_ImageViewer.m:164: warning:
> ‘android_widget_Button’ may not respond to
> ‘-setText___java_lang_CharSequence:’
> com_home_imageviewer_ImageViewer.m:164: warning: (Messages without a
> matching method signature
> com_home_imageviewer_ImageViewer.m:164: warning: will be assumed to
> return ‘id’ and accept
> com_home_imageviewer_ImageViewer.m:164: warning: ‘...’ as arguments.)
> make: *** [obj/com_home_imageviewer_ImageViewer.o] Error 1
>
>
>
> On 12/10/2009, at 12:55 AM, Wolfgang Korn wrote:
>
>> It seems that the pop2 instruction is used to clean up the stack
>> here. Your code computes minimum and maximum of two values but simply
>> ignores the computed value. To remove this computation result pop2
>> seems to be used. Until we implement the missing instruction you can
>> simply assign the results from the calls to Math.min and Math.max to
>> variables. In my case this removed the pop2 from the class file.
>>
>> One last thing: Could you please upload a patch file for your
>> additions to Math.m/h to our review site
>> (http://xmlvm-reviews.appspot.com/) or create a patch and send that
>> instead of sending the whole files? This makes it easier to merge in
>> case if concurrent modifications.
>>
>> -- Wolfgang
>>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> 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 list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>   

[xmlvm-users] [Fwd: Re: Maths]

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

Oops - that was supposed to the mailing list ...

Re: [xmlvm-users] Maths

[Joseph R. F. <ruk...@op...>]

Thanks that worked. How does one use the TextView.setText()  thats  
already defined in the TextWidget?

When it cross compiles to iphone I get this error, I understand that  
is because android's setText takes a CharSequence. But just wondering  
how the setText in compat library can be called.

com_home_imageviewer_ImageViewer.m:9:35: error:  
java_lang_CharSequence.h: No such file or directory
com_home_imageviewer_ImageViewer.m: In function ‘- 
[com_home_imageviewer_ImageViewer onCreate___android_os_Bundle:]’:
com_home_imageviewer_ImageViewer.m:164: warning:  
‘android_widget_Button’ may not respond to ‘- 
setText___java_lang_CharSequence:’
com_home_imageviewer_ImageViewer.m:164: warning: (Messages without a  
matching method signature
com_home_imageviewer_ImageViewer.m:164: warning: will be assumed to  
return ‘id’ and accept
com_home_imageviewer_ImageViewer.m:164: warning: ‘...’ as arguments.)
make: *** [obj/com_home_imageviewer_ImageViewer.o] Error 1



On 12/10/2009, at 12:55 AM, Wolfgang Korn wrote:

> It seems that the pop2 instruction is used to clean up the stack  
> here. Your code computes minimum and maximum of two values but  
> simply ignores the computed value. To remove this computation result  
> pop2 seems to be used. Until we implement the missing instruction  
> you can simply assign the results from the calls to Math.min and  
> Math.max to variables. In my case this removed the pop2 from the  
> class file.
>
> One last thing: Could you please upload a patch file for your  
> additions to Math.m/h to our review site (http://xmlvm-reviews.appspot.com/ 
> ) or create a patch and send that instead of sending the whole  
> files? This makes it easier to merge in case if concurrent  
> modifications.
>
> -- Wolfgang
>

[xmlvm-users] Update of my work

[Panayotis K. <pan...@pa...>]

Since it seems I am creating a whole bunch of patches, I've decided to  
send them all together when I have fairly finish a large part of it.
Still I decided to give here an update of my process, so that there is  
no need for someone to do a duplicate work.

In general I have implemented UISlider, UISegmentedControl and  
UIProgressView.
I have also fixed UIColor, which is working as expected now (yes, I've  
taken care not to break the UIButton alchemy you do there for alerts).
Also properties hidden, userInteractionEnabled and background work as  
expected (in both obj-c and simulator)

I've done also some small fixes here and there, which I can't  
remember ;-)