Menu
▾
▴
xmlvm-developers — Used to discuss development of XMLVM itself. Not for developers using XMLVM.
You can subscribe to this list here.
| 2011 |
Jan
|
Feb
|
Mar
(38) |
Apr
(34) |
May
(20) |
Jun
(46) |
Jul
(6) |
Aug
(13) |
Sep
(50) |
Oct
(27) |
Nov
(10) |
Dec
(3) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2012 |
Jan
(7) |
Feb
(3) |
Mar
(4) |
Apr
|
May
|
Jun
(2) |
Jul
(4) |
Aug
(3) |
Sep
(1) |
Oct
(2) |
Nov
|
Dec
|
| 2013 |
Jan
(1) |
Feb
|
Mar
(4) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <D.D...@ak...> - 2011-04-13 09:50:27
|
<font face="Sans Serif predefinito,Verdana,Arial,Helvetica,sans-serif" size="2"><div>Hi all,<br><br>I think I spotted a little bug you might be interested in. In my project, I send SOAP requests to a server that I compose in a stringbuffer, like the following<br><br>query.append("<TripInformationRequest xmlns=\<a class="moz-txt-link-rfc2396E" href="http://xml.amadeus.com/ori/bpel/TripInformation/schema/TripInformationRequest%5C">"http://xml.amadeus.com/ori/bpel/TripInformation/schema/TripInformationRequest\"</a>><recordLocator>");<br><br>When sending the request however, I was receiving a Routing Error from the server that I couldn't understand.<br>After some packet sniffing I found out that, in the Objectve-C version of the project, the line was translated as<br><br> _r3.o = @"<TripInformationRequest xmlns=\\042http://xml.amadeus.com/ori/bpel/TripInformation/schema/TripInformationRequest\\042><recordLocator>";<br><br>The \" pattern in the string was converted to \\042 which caused the problem.<br>I solved the problem by modifying the xslt sheet as follows (at line 2944)<br><br><xsl:value-of select="replace(replace(replace(replace(replace(replace(replace(replace(@value,'\\','\\\\'),<br> '\\\\011','\\t'),'\\\\012','\\n'),'\\\\015','\\r'),'\\\\014','\\f'),'\\\\010','\\b'),<br> '&quot;','\\&quot;'), '\\\\042','\\&quot;')"/><br><br>Practically I just added a new replace pattern at the end of all the others. Do you think it might be a good solution?<br><br>Thanks,<br><br>Domenico<br></div></font>
|
|
From: <D.D...@ak...> - 2011-04-13 08:02:01
|
<font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"><div>Hi,<br><br>Thank you for your help, surely the zip plugin is a good reference to start. Sorry Arno, I'm not too sure I understood what you suggested.<br>Do you mean that I should create the Objective-C classes for the DOM Java parser using the existing C backend?<br><br>Thanks,<br><br>Domenico<br></div><font color="#990099">-----Arno Puder <a class="moz-txt-link-rfc2396E" href="mailto:ar...@pu..."><ar...@pu...></a> a écrit : -----<br><br></font><blockquote style="padding-right: 0px; padding-left: 5px; margin-left: 5px; border-left: 2px solid #000000; margin-right: 0px;">A : <a class="moz-txt-link-abbreviated" href="mailto:xml...@li...">xml...@li...</a><br>De : Arno Puder <a class="moz-txt-link-rfc2396E" href="mailto:ar...@pu..."><ar...@pu...></a><br>Date : 12/04/2011 21:56<br>Objet : Re: [xmlvm-dev] Objective-C XML Parser<br><br><font face="Courier New,Courier,monospace" size="3"><br>my suggestion would be to use the C backend and simply cross-compile a <br>Java implementation of a DOM parser. Not sure, but there might already <br>be one in Harmony that is bundled with XMLVM.<br><br>Arno<br><br><br>On 4/12/11 6:43 AM, <a class="moz-txt-link-abbreviated" href="mailto:D.D...@ak...">D.D...@ak...</a> wrote:<br>> Hi everyone,<br>><br>> I'm working on the Java to Objective-C part of XMLVM, and I need to<br>> implement a DOM parser for my project. I've noticed however that only<br>> NSXMLParser is available in XMLVM,<br>> whereas I was thinking about using libxml, which is a C-based parser<br>> incuded in the iOS SDK. Do you have any idea of how I could accomplish this?<br>> The first step would be to add the library in the Header Search Path of<br>> the Project Setting, but I don't know where these settings are stored in<br>> XMLVM.<br>> Successively I think I should create some interface for the libxml<br>> classes in the Obj-C and Java compatibility libraries.<br>> Do you think it might be possible?<br>> Of course I'd be very happy to share my contribution should I be able to<br>> do this.<br>><br>> Thank you,<br>><br>> Domenico<br>><br>><br>><br>> ------------------------------------------------------------------------------<br>> Forrester Wave Report - Recovery time is now measured in hours and minutes<br>> not days. Key insights are discussed in the 2010 Forrester Wave Report as<br>> part of an in-depth evaluation of disaster recovery service providers.<br>> Forrester found the best-in-class provider in terms of services and vision.<br>> Read this report now! <a href="http://p.sf.net/sfu/ibm-webcastpromo">http://p.sf.net/sfu/ibm-webcastpromo</a><br>><br>><br>><br>> _______________________________________________<br>> Xmlvm-developers mailing list<br>> <a class="moz-txt-link-abbreviated" href="mailto:Xml...@li...">Xml...@li...</a><br>> <a href="https://lists.sourceforge.net/lists/listinfo/xmlvm-developers">https://lists.sourceforge.net/lists/listinfo/xmlvm-developers</a><br><br>------------------------------------------------------------------------------<br>Forrester Wave Report - Recovery time is now measured in hours and minutes<br>not days. Key insights are discussed in the 2010 Forrester Wave Report as<br>part of an in-depth evaluation of disaster recovery service providers.<br>Forrester found the best-in-class provider in terms of services and vision.<br>Read this report now! <a href="http://p.sf.net/sfu/ibm-webcastpromo">http://p.sf.net/sfu/ibm-webcastpromo</a><br>_______________________________________________<br>Xmlvm-developers mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:Xml...@li...">Xml...@li...</a><br><a href="https://lists.sourceforge.net/lists/listinfo/xmlvm-developers">https://lists.sourceforge.net/lists/listinfo/xmlvm-developers</a><br></font> </blockquote><br></font> |
|
From: Arno P. <ar...@pu...> - 2011-04-12 19:56:41
|
my suggestion would be to use the C backend and simply cross-compile a Java implementation of a DOM parser. Not sure, but there might already be one in Harmony that is bundled with XMLVM. Arno On 4/12/11 6:43 AM, D.D...@ak... wrote: > Hi everyone, > > I'm working on the Java to Objective-C part of XMLVM, and I need to > implement a DOM parser for my project. I've noticed however that only > NSXMLParser is available in XMLVM, > whereas I was thinking about using libxml, which is a C-based parser > incuded in the iOS SDK. Do you have any idea of how I could accomplish this? > The first step would be to add the library in the Header Search Path of > the Project Setting, but I don't know where these settings are stored in > XMLVM. > Successively I think I should create some interface for the libxml > classes in the Obj-C and Java compatibility libraries. > Do you think it might be possible? > Of course I'd be very happy to share my contribution should I be able to > do this. > > Thank you, > > Domenico > > > > ------------------------------------------------------------------------------ > Forrester Wave Report - Recovery time is now measured in hours and minutes > not days. Key insights are discussed in the 2010 Forrester Wave Report as > part of an in-depth evaluation of disaster recovery service providers. > Forrester found the best-in-class provider in terms of services and vision. > Read this report now! http://p.sf.net/sfu/ibm-webcastpromo > > > > _______________________________________________ > Xmlvm-developers mailing list > Xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers |
|
From: Panayotis K. <pan...@pa...> - 2011-04-12 14:20:23
|
On 12 Απρ 2011, at 4:43 μ.μ., D.D...@ak... wrote: > Hi everyone, > > I'm working on the Java to Objective-C part of XMLVM, and I need to implement a DOM parser for my project. I've noticed however that only NSXMLParser is available in XMLVM, > whereas I was thinking about using libxml, which is a C-based parser incuded in the iOS SDK. Do you have any idea of how I could accomplish this? > The first step would be to add the library in the Header Search Path of the Project Setting, but I don't know where these settings are stored in XMLVM. > Successively I think I should create some interface for the libxml classes in the Obj-C and Java compatibility libraries. > Do you think it might be possible? > Of course I'd be very happy to share my contribution should I be able to do this. > > Thank you, > > Domenico Have a look at the "zip" plugin. I think this should be enough to get started. |
|
From: <D.D...@ak...> - 2011-04-12 13:43:29
|
<font face="Sans Serif predefinito,Verdana,Arial,Helvetica,sans-serif" size="2"><div>Hi everyone,<br><br>I'm working on the Java to Objective-C part of XMLVM, and I need to implement a DOM parser for my project. I've noticed however that only NSXMLParser is available in XMLVM,<br>whereas I was thinking about using libxml, which is a C-based parser incuded in the iOS SDK. Do you have any idea of how I could accomplish this?<br>The first step would be to add the library in the Header Search Path of the Project Setting, but I don't know where these settings are stored in XMLVM. <br>Successively I think I should create some interface for the libxml classes in the Obj-C and Java compatibility libraries.<br>Do you think it might be possible? <br>Of course I'd be very happy to share my contribution should I be able to do this.<br><br>Thank you,<br><br>Domenico<br></div></font> |
|
From: Arno P. <ar...@pu...> - 2011-04-05 23:15:11
|
A byte is a signed 8 bit value that needs to be sign-extended to 32 bits when loaded into a register. Arno On Apr 5, 2011, at 3:30 PM, Panayotis Katsaloulis <pan...@pa...> wrote: > > On Apr 5, 2011, at 8:49 PM, Arno Puder wrote: > >> >> things are a little trickier. According to section 2.4.1 of the Java >> Specs: "The integral types are byte, short, int, and long, whose values >> are 8-bit, 16-bit, 32-bit, and 64-bit signed two's-complement integers, >> respectively, and char, whose values are 16-bit unsigned integers >> representing Unicode characters" >> >> Then in Section 3.11.1 of the Java spec it says: "Note that most >> instructions in Table 3.2 do not have forms for the integral types byte, >> char, and short. None have forms for the boolean type. Compilers encode >> loads of literal values of types byte and short using Java virtual >> machine instructions that sign-extend those values to values of type int >> at compile time or run time. Loads of literal values of types boolean >> and char are encoded using instructions that zero-extend the literal to >> a value of type int at compile time or run time." >> >> So, you are correct that a byte is a signed 8-bit value, however it >> needs to be properly sign extended. In the C backend I already use >> typedef's consistently, so it should be easy to fix. The Objective-C >> backend is not as cleanly implemented. >> >> Arno >> > > > So, the problem remains, should "byte" be a signed or unsigned char under ObjC backend, and especially in the Byte methods? > My understanding is that it is sometimes a signed integer, but in any case, it is *not* an unsigned char. > ------------------------------------------------------------------------------ > Xperia(TM) PLAY > It's a major breakthrough. An authentic gaming > smartphone on the nation's most reliable network. > And it wants your games. > http://p.sf.net/sfu/verizon-sfdev > _______________________________________________ > Xmlvm-developers mailing list > Xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers |
|
From: Panayotis K. <pan...@pa...> - 2011-04-05 22:30:38
|
On Apr 5, 2011, at 8:49 PM, Arno Puder wrote: > > things are a little trickier. According to section 2.4.1 of the Java > Specs: "The integral types are byte, short, int, and long, whose values > are 8-bit, 16-bit, 32-bit, and 64-bit signed two's-complement integers, > respectively, and char, whose values are 16-bit unsigned integers > representing Unicode characters" > > Then in Section 3.11.1 of the Java spec it says: "Note that most > instructions in Table 3.2 do not have forms for the integral types byte, > char, and short. None have forms for the boolean type. Compilers encode > loads of literal values of types byte and short using Java virtual > machine instructions that sign-extend those values to values of type int > at compile time or run time. Loads of literal values of types boolean > and char are encoded using instructions that zero-extend the literal to > a value of type int at compile time or run time." > > So, you are correct that a byte is a signed 8-bit value, however it > needs to be properly sign extended. In the C backend I already use > typedef's consistently, so it should be easy to fix. The Objective-C > backend is not as cleanly implemented. > > Arno > So, the problem remains, should "byte" be a signed or unsigned char under ObjC backend, and especially in the Byte methods? My understanding is that it is sometimes a signed integer, but in any case, it is *not* an unsigned char. |
|
From: Arno P. <ar...@pu...> - 2011-04-05 17:49:43
|
things are a little trickier. According to section 2.4.1 of the Java Specs: "The integral types are byte, short, int, and long, whose values are 8-bit, 16-bit, 32-bit, and 64-bit signed two's-complement integers, respectively, and char, whose values are 16-bit unsigned integers representing Unicode characters" Then in Section 3.11.1 of the Java spec it says: "Note that most instructions in Table 3.2 do not have forms for the integral types byte, char, and short. None have forms for the boolean type. Compilers encode loads of literal values of types byte and short using Java virtual machine instructions that sign-extend those values to values of type int at compile time or run time. Loads of literal values of types boolean and char are encoded using instructions that zero-extend the literal to a value of type int at compile time or run time." So, you are correct that a byte is a signed 8-bit value, however it needs to be properly sign extended. In the C backend I already use typedef's consistently, so it should be easy to fix. The Objective-C backend is not as cleanly implemented. Arno On 4/5/11 7:07 AM, Troy Gaines wrote: > Panayotis, > > From what I see, what you're saying is correct. > > http://en.wikipedia.org/wiki/C_variable_types_and_declarations > > It seems reasonable to typedef "byte" to make this more clear. > > > On Tue, Apr 5, 2011 at 8:16 AM, Panayotis Katsaloulis > <pan...@pa... <mailto:pan...@pa...>> wrote: > > Hello > > I had a look at the Byte implementation of the ObjC backend and I > saw that you have defined it as "unsigned char" instead of "signed > char". > > Here > http://download.oracle.com/javase/tutorial/java/nutsandbolts/datatypes.html > says that byte is signed in Java. > Am I missing something or is this a bug? > > (and if it is a bug, probably we should also check other locations > where byte as an unsigned char was used?) > ------------------------------------------------------------------------------ > Xperia(TM) PLAY > It's a major breakthrough. An authentic gaming > smartphone on the nation's most reliable network. > And it wants your games. > http://p.sf.net/sfu/verizon-sfdev > _______________________________________________ > Xmlvm-developers mailing list > Xml...@li... > <mailto:Xml...@li...> > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers > > > > > ------------------------------------------------------------------------------ > Xperia(TM) PLAY > It's a major breakthrough. An authentic gaming > smartphone on the nation's most reliable network. > And it wants your games. > http://p.sf.net/sfu/verizon-sfdev > > > > _______________________________________________ > Xmlvm-developers mailing list > Xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers |
|
From: Troy G. <tro...@gm...> - 2011-04-05 14:08:26
|
Panayotis, >From what I see, what you're saying is correct. http://en.wikipedia.org/wiki/C_variable_types_and_declarations It seems reasonable to typedef "byte" to make this more clear. On Tue, Apr 5, 2011 at 8:16 AM, Panayotis Katsaloulis < pan...@pa...> wrote: > Hello > > I had a look at the Byte implementation of the ObjC backend and I saw that > you have defined it as "unsigned char" instead of "signed char". > > Here > http://download.oracle.com/javase/tutorial/java/nutsandbolts/datatypes.html > says that byte is signed in Java. > Am I missing something or is this a bug? > > (and if it is a bug, probably we should also check other locations where > byte as an unsigned char was used?) > > ------------------------------------------------------------------------------ > Xperia(TM) PLAY > It's a major breakthrough. An authentic gaming > smartphone on the nation's most reliable network. > And it wants your games. > http://p.sf.net/sfu/verizon-sfdev > _______________________________________________ > Xmlvm-developers mailing list > Xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers > |
|
From: <D.D...@ak...> - 2011-04-05 13:20:37
|
<font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"><div>Hi, <br><br>Thank you for your help. The example I used is the following ()<br><br><h1 class="objc" style="font-family: monospace; font-weight: normal; font-style: italic;"><font size="3">UIAlertView <font color="#002200">*</font>alert;<br> <br>...<br> <br>alert <font color="#002200">=</font> <font color="#002200">[</font><font color="#002200">[</font><font color="#002200">[</font>UIAlertView alloc<font color="#002200">]</font> initWithTitle<font color="#002200">:</font><font color="#bf1d1a">@</font><font color="#bf1d1a">"Configuring Preferences<font color="#2400d9">\n</font>Please Wait..."</font><font color="#002200">:</font><font color="#a61390">nil</font> delegate<font color="#002200">:</font>self cancelButtonTitle<font color="#002200">:</font><font color="#a61390">nil</font> otherButtonTitles<font color="#002200">:</font> <font color="#a61390">nil</font><font color="#002200">]</font> autorelease<font color="#002200">]</font>;<br><font color="#002200">[</font>alert show<font color="#002200">]</font>;<br> <br>UIActivityIndicatorView <font color="#002200">*</font>indicator <font color="#002200">=</font> <font color="#002200">[</font><font color="#002200">[</font>UIActivityIndicatorView alloc<font color="#002200">]</font><font color="#002200">:</font>UIActivityIndicatorViewStyleWhiteLarge<font color="#002200">]</font>;<br> <br><font color="#11740a">// Adjust the indicator so it is up a few pixels from the bottom of the alert</font><br>indicator.center <font color="#002200">=</font> CGPointMake<font color="#002200">(</font>alert.bounds.size.width <font color="#002200">/</font> <font color="#2400d9">2</font>, alert.bounds.size.height <font color="#002200">-</font><font color="#2400d9">50</font><font color="#002200">)</font>;<br><font color="#002200">[</font>indicator startAnimating<font color="#002200">]</font>;<br><font color="#002200">[</font>alert addSubview<font color="#002200">:</font>indicator<font color="#002200">]</font>;<br><font color="#002200">[</font>indicator release<font color="#002200">]</font>; message initWithActivityIndicatorStyle</font></h1><br>which, in Java, I used as<br><br><font style="font-style: italic; font-family: Default Monospace,Courier New,Courier,monospace;" size="2">UIAlertView alert = new UIAlertView(message, null, null, null);<br>UIActivityIndicatorView indicator = new UIActivityIndicatorView(0);<br>CGPoint center = new CGPoint(</font><font style="font-style: italic; font-family: Default Monospace,Courier New,Courier,monospace;" size="2">alert.getbounds().size.width <font color="#002200">/</font> <font color="#2400d9">2</font>, alert.getbounds().size.height <font color="#002200">-</font><font color="#2400d9">50</font><font color="#002200">)</font>;<br>indicator.setCenter(center);</font><br>indicator.startAnimating();<br>alert.addSubview(indicator);<br><br><br>I really can't figure out what's wrong. Maybe I should try to use a UIProgressView instead, but still I'm interested in this to add some modifications to the dialog.<br><br><br>Thank you,<br><br>Domenico<br><br></div><font color="#990099">-----Panayotis Katsaloulis <a class="moz-txt-link-rfc2396E" href="mailto:pan...@pa..."><pan...@pa...></a> a écrit : -----<br><br></font><blockquote style="padding-right: 0px; padding-left: 5px; margin-left: 5px; border-left: 2px solid #000000; margin-right: 0px;">A : <a class="moz-txt-link-abbreviated" href="mailto:xml...@li...">xml...@li...</a><br>De : Panayotis Katsaloulis <a class="moz-txt-link-rfc2396E" href="mailto:pan...@pa..."><pan...@pa...></a><br>Date : 04/04/2011 10:07<br>Objet : Re: [xmlvm-dev] UIAlertViewDelegate<br><br><font face="Courier New,Courier,monospace" size="3"><br>On Apr 3, 2011, at 12:35 AM, Domenico De Fano wrote:<br><br>> Hi,<br>> <br>> I found an Objective-C example that worked and wanted to replicate it. In fact I think that's not the best way of doing it, but I couldn't find any other. I wonder if there is an official way of customizing dialogs.<br>> Still it seems strange that the getCenter() method doesn't work on the dialog while the getBounds() does.<br>> <br>> Domenico De Fano<br><br><br>I think the documentation says that you are not clearly allowed to do so. I think I've read (but I am not sure) that this behavior trigged also the application reject mechanism, although it is true that you can now find applications that are using it more or less.<br><br>In any case, xmlvm does not interfere with the procedure. The most common reason for his problem though is that he is not using the examples he found the way he should. My guess is, sInce this is a fragile feature by definition, probably the steps you are following are not exactly the correct ones.<br>------------------------------------------------------------------------------<br>Create and publish websites with WebMatrix<br>Use the most popular FREE web apps or write code yourself; <br>WebMatrix provides all the features you need to develop and <br>publish your website. <a href="http://p.sf.net/sfu/ms-webmatrix-sf">http://p.sf.net/sfu/ms-webmatrix-sf</a><br>_______________________________________________<br>Xmlvm-developers mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:Xml...@li...">Xml...@li...</a><br><a href="https://lists.sourceforge.net/lists/listinfo/xmlvm-developers">https://lists.sourceforge.net/lists/listinfo/xmlvm-developers</a><br></font> </blockquote><br></font> |
|
From: Panayotis K. <pan...@pa...> - 2011-04-05 13:16:54
|
Hello I had a look at the Byte implementation of the ObjC backend and I saw that you have defined it as "unsigned char" instead of "signed char". Here http://download.oracle.com/javase/tutorial/java/nutsandbolts/datatypes.html says that byte is signed in Java. Am I missing something or is this a bug? (and if it is a bug, probably we should also check other locations where byte as an unsigned char was used?) |
|
From: Panayotis K. <pan...@pa...> - 2011-04-04 08:07:32
|
On Apr 3, 2011, at 12:35 AM, Domenico De Fano wrote: > Hi, > > I found an Objective-C example that worked and wanted to replicate it. In fact I think that's not the best way of doing it, but I couldn't find any other. I wonder if there is an official way of customizing dialogs. > Still it seems strange that the getCenter() method doesn't work on the dialog while the getBounds() does. > > Domenico De Fano I think the documentation says that you are not clearly allowed to do so. I think I've read (but I am not sure) that this behavior trigged also the application reject mechanism, although it is true that you can now find applications that are using it more or less. In any case, xmlvm does not interfere with the procedure. The most common reason for his problem though is that he is not using the examples he found the way he should. My guess is, sInce this is a fragile feature by definition, probably the steps you are following are not exactly the correct ones. |
|
From: Domenico De F. <dom...@gm...> - 2011-04-02 21:34:38
|
Hi, I found an Objective-C example that worked and wanted to replicate it. In fact I think that's not the best way of doing it, but I couldn't find any other. I wonder if there is an official way of customizing dialogs. Still it seems strange that the getCenter() method doesn't work on the dialog while the getBounds() does. Domenico De Fano Le 2 avr. 2011 à 23:13, Arno Puder a écrit : > > to be honest, I don't think this is an XMLVM related problem. Although > UIAlertView inherits from UIView, I'm not sure if you are supposed to > add subviews. > > Any Cocoa Touch cracks out there? > > Arno > > > On 4/2/11 12:38 PM, Domenico De Fano wrote: >> Hi, >> >> Thank you Arno for your help, you're right. I noticed yesterday that I was >> trying to use the Java simulator classes to modify the behavior of the >> Obj-C application. >> However I'm still having problems in positioning the gear inside the >> alert. In fact, since I have some dinamically generated message in the >> alert, its dimension and position should be dynamic too. >> If I just insert the gear as a subview of the alert I get it into a >> weird position on the left side of the screen. I tried to use the >> getCenter() method of the alert in order to position the gear always in >> the alerts' center, but it doesn't seem to work. Do you know what that >> might be? >> >> Thanks, >> >> Domenico De Fano >> >> >> >> ------------------------------------------------------------------------------ >> Create and publish websites with WebMatrix >> Use the most popular FREE web apps or write code yourself; >> WebMatrix provides all the features you need to develop and >> publish your website. http://p.sf.net/sfu/ms-webmatrix-sf >> >> >> >> _______________________________________________ >> Xmlvm-developers mailing list >> Xml...@li... >> https://lists.sourceforge.net/lists/listinfo/xmlvm-developers > > ------------------------------------------------------------------------------ > Create and publish websites with WebMatrix > Use the most popular FREE web apps or write code yourself; > WebMatrix provides all the features you need to develop and > publish your website. http://p.sf.net/sfu/ms-webmatrix-sf > _______________________________________________ > Xmlvm-developers mailing list > Xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers |
|
From: Arno P. <ar...@pu...> - 2011-04-02 21:13:27
|
to be honest, I don't think this is an XMLVM related problem. Although UIAlertView inherits from UIView, I'm not sure if you are supposed to add subviews. Any Cocoa Touch cracks out there? Arno On 4/2/11 12:38 PM, Domenico De Fano wrote: > Hi, > > Thank you Arno for your help, you're right. I noticed yesterday that I was > trying to use the Java simulator classes to modify the behavior of the > Obj-C application. > However I'm still having problems in positioning the gear inside the > alert. In fact, since I have some dinamically generated message in the > alert, its dimension and position should be dynamic too. > If I just insert the gear as a subview of the alert I get it into a > weird position on the left side of the screen. I tried to use the > getCenter() method of the alert in order to position the gear always in > the alerts' center, but it doesn't seem to work. Do you know what that > might be? > > Thanks, > > Domenico De Fano > > > > ------------------------------------------------------------------------------ > Create and publish websites with WebMatrix > Use the most popular FREE web apps or write code yourself; > WebMatrix provides all the features you need to develop and > publish your website. http://p.sf.net/sfu/ms-webmatrix-sf > > > > _______________________________________________ > Xmlvm-developers mailing list > Xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers |
|
From: Domenico De F. <dom...@gm...> - 2011-04-02 19:38:56
|
Hi, Thank you Arno for your help, you're right. I noticed yesterday that I was trying to use the Java simulator classes to modify the behavior of the Obj-C application. However I'm still having problems in positioning the gear inside the alert. In fact, since I have some dinamically generated message in the alert, its dimension and position should be dynamic too. If I just insert the gear as a subview of the alert I get it into a weird position on the left side of the screen. I tried to use the getCenter() method of the alert in order to position the gear always in the alerts' center, but it doesn't seem to work. Do you know what that might be? Thanks, Domenico De Fano |
|
From: Arno P. <ar...@pu...> - 2011-04-02 00:15:59
|
You mentioned class UIAlertViewRenderer. This is an internal class for our Java based iPhone emulator. Where do you have your problems? With our Java emulator or with the cross compiled application? Note that our Java emulator is more a proof of concept and we have no plans to keep it up to date. Arno On Apr 1, 2011, at 1:11 AM, "D.D...@ak..." <D.D...@ak...> wrote: Hi everybody, I'm trying to implement a sort of progress dialog containing a spinning gear, to let users now that an action is being performed and they should wait. I'm trying to do it using the UIAlertView class and adding the UIActivityIndicatorView as a subview. However, I'm having problems setting the position of the UIActivityIndicatorView; exploring the UIAlertView class in AMAK I found out that the getFrame() method doesn't return the correct size of the dialog. Apparently, what I need is the viewingArea variable of the UIAlertViewRenderer; however, I tried to retrieve that parameter by creating a getter but nothing happens. I even tried to insert the UIActivityIndicatorView directly in the doLayout() method and still nothing happens. Could you suggest me the correct way of doing this? Thank you, Domenico De Fano ------------------------------------------------------------------------------ Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf _______________________________________________ Xmlvm-developers mailing list Xml...@li... https://lists.sourceforge.net/lists/listinfo/xmlvm-developers |
|
From: <D.D...@ak...> - 2011-04-01 08:11:24
|
<font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"><div>Hi everybody,<br><br>I'm trying to implement a sort of progress dialog containing a spinning gear, to let users now that an action is being performed and they should wait. I'm trying to do it using the UIAlertView class and adding the UIActivityIndicatorView as a subview. However, I'm having problems setting the position of the UIActivityIndicatorView; exploring the UIAlertView class in AMAK I found out that the getFrame() method doesn't return the correct size of the dialog.<br>Apparently, what I need is the viewingArea variable of the UIAlertViewRenderer; however, I tried to retrieve that parameter by creating a getter but nothing happens. I even tried to insert the UIActivityIndicatorView directly in the doLayout() method and still nothing happens.<br>Could you suggest me the correct way of doing this?<br><br>Thank you,<br><br>Domenico De Fano<br> </div></font> |
|
From: Arno P. <ar...@pu...> - 2011-03-28 16:35:16
|
I wanted to make one more comment concerning the overall issue: you may have noticed that there is a branch called branches/wp7. Markus and Oren are working in that branch to add another backend to XMLVM for WP7. The current version of XMLVM's Android Compat Lib is tied to iOS and the discussion we've had here with NSSelector is a good example. NSObject.performSelectorOnMainThread() is currently used in various places in the Android Compat Lib to run tasks on the UI thread, however, that class and method are iOS specific. One job that Oren and Markus will soon be working on is to refactor the Android Compat Lib and add a well-defined "Common Device API" that will make it easier to add new backends to XMLVM. So, instead of using NSObject/NSSelector all over the Android Compat Lib, the plan is to create an abstraction. Same is true for other iOS API that is used liberally throughout the Android Compat Lib, e.g., NSXMLParser, NSData, etc. Now, I just mention this to give a glimpse on things to come with XMLVM. It doesn't affect the current discussion and decisions regarding NSSelector. Panayotis patch is already introducing NSSelector within the Android Compat Lib. Once we advance with WP7, this will change again to the aforementioned Common Device API. I'm sure the WP7 guys will introduce their refactoring plans on this list for general discussion. Arno On 3/26/11 12:34 PM, Paul Poley wrote: > That's fine with me too. > > Paul > > On Sat, Mar 26, 2011 at 11:55 AM, Arno Puder <ar...@pu... > <mailto:ar...@pu...>> wrote: > > > I agree with you that (1) the name of a class/method should reflect its > semantics and (2) we should stick to the official API as much as > possible. In light of this, I also opt for the first option I mentioned > NSObject.performSelectorOnMainThread(NSSelector). > > Arno > > > On 3/26/11 3:46 AM, Panayotis Katsaloulis wrote: > > > > On Mar 25, 2011, at 3:19 AM, Arno Puder wrote: > > > >> > >> I guess the question boils down to the way to define the callback in > >> Java. Introduce a new interface (NSSelector) or use existing Java > >> interface (Runnable)? The method in question is > >> NSObject.performSelectorOnMainThread(). Considering the name of the > >> method, it might be awkward to pass a runnable. Perhaps renaming the > >> method to NSObject.performRunnableOnMainThread() although it doesn't > >> exists on the Objective-C side. > >> > >> So, the options are: > >> > >> 1. NSObject.performSelectorOnMainThread(NSSelector) > > > > I am actually more in favor of this solution, because it is > similar (or practically the same) with NSTimerDelegate > > > >> 2. NSObject.performSelectorOnMainThread(Runnable) > >> 3. NSObject.performRunnableOnMainThread(Runnable) > > > > I am afraid that this is not standard and nowhere documented, and > I am not really in favor for introducing non-existive API. > > > > > > More importantly though, it is required the others to express > their opinion. > |
|
From: Paul P. <bay...@gm...> - 2011-03-26 19:34:11
|
That's fine with me too. Paul On Sat, Mar 26, 2011 at 11:55 AM, Arno Puder <ar...@pu...> wrote: > > I agree with you that (1) the name of a class/method should reflect its > semantics and (2) we should stick to the official API as much as > possible. In light of this, I also opt for the first option I mentioned > NSObject.performSelectorOnMainThread(NSSelector). > > Arno > > > On 3/26/11 3:46 AM, Panayotis Katsaloulis wrote: > > > > On Mar 25, 2011, at 3:19 AM, Arno Puder wrote: > > > >> > >> I guess the question boils down to the way to define the callback in > >> Java. Introduce a new interface (NSSelector) or use existing Java > >> interface (Runnable)? The method in question is > >> NSObject.performSelectorOnMainThread(). Considering the name of the > >> method, it might be awkward to pass a runnable. Perhaps renaming the > >> method to NSObject.performRunnableOnMainThread() although it doesn't > >> exists on the Objective-C side. > >> > >> So, the options are: > >> > >> 1. NSObject.performSelectorOnMainThread(NSSelector) > > > > I am actually more in favor of this solution, because it is similar (or > practically the same) with NSTimerDelegate > > > >> 2. NSObject.performSelectorOnMainThread(Runnable) > >> 3. NSObject.performRunnableOnMainThread(Runnable) > > > > I am afraid that this is not standard and nowhere documented, and I am > not really in favor for introducing non-existive API. > > > > > > More importantly though, it is required the others to express their > opinion. > |
|
From: Arno P. <ar...@pu...> - 2011-03-26 16:55:54
|
I agree with you that (1) the name of a class/method should reflect its semantics and (2) we should stick to the official API as much as possible. In light of this, I also opt for the first option I mentioned NSObject.performSelectorOnMainThread(NSSelector). Arno On 3/26/11 3:46 AM, Panayotis Katsaloulis wrote: > > On Mar 25, 2011, at 3:19 AM, Arno Puder wrote: > >> >> I guess the question boils down to the way to define the callback in >> Java. Introduce a new interface (NSSelector) or use existing Java >> interface (Runnable)? The method in question is >> NSObject.performSelectorOnMainThread(). Considering the name of the >> method, it might be awkward to pass a runnable. Perhaps renaming the >> method to NSObject.performRunnableOnMainThread() although it doesn't >> exists on the Objective-C side. >> >> So, the options are: >> >> 1. NSObject.performSelectorOnMainThread(NSSelector) > > I am actually more in favor of this solution, because it is similar (or practically the same) with NSTimerDelegate > >> 2. NSObject.performSelectorOnMainThread(Runnable) >> 3. NSObject.performRunnableOnMainThread(Runnable) > > I am afraid that this is not standard and nowhere documented, and I am not really in favor for introducing non-existive API. > > > More importantly though, it is required the others to express their opinion. > ------------------------------------------------------------------------------ > Enable your software for Intel(R) Active Management Technology to meet the > growing manageability and security demands of your customers. Businesses > are taking advantage of Intel(R) vPro (TM) technology - will your software > be a part of the solution? Download the Intel(R) Manageability Checker > today! http://p.sf.net/sfu/intel-dev2devmar > _______________________________________________ > Xmlvm-developers mailing list > Xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers |
|
From: Panayotis K. <pan...@pa...> - 2011-03-26 10:46:59
|
On Mar 25, 2011, at 3:19 AM, Arno Puder wrote: > > I guess the question boils down to the way to define the callback in > Java. Introduce a new interface (NSSelector) or use existing Java > interface (Runnable)? The method in question is > NSObject.performSelectorOnMainThread(). Considering the name of the > method, it might be awkward to pass a runnable. Perhaps renaming the > method to NSObject.performRunnableOnMainThread() although it doesn't > exists on the Objective-C side. > > So, the options are: > > 1. NSObject.performSelectorOnMainThread(NSSelector) I am actually more in favor of this solution, because it is similar (or practically the same) with NSTimerDelegate > 2. NSObject.performSelectorOnMainThread(Runnable) > 3. NSObject.performRunnableOnMainThread(Runnable) I am afraid that this is not standard and nowhere documented, and I am not really in favor for introducing non-existive API. More importantly though, it is required the others to express their opinion. |
|
From: Arno P. <ar...@pu...> - 2011-03-25 01:19:58
|
I guess the question boils down to the way to define the callback in Java. Introduce a new interface (NSSelector) or use existing Java interface (Runnable)? The method in question is NSObject.performSelectorOnMainThread(). Considering the name of the method, it might be awkward to pass a runnable. Perhaps renaming the method to NSObject.performRunnableOnMainThread() although it doesn't exists on the Objective-C side. So, the options are: 1. NSObject.performSelectorOnMainThread(NSSelector) 2. NSObject.performSelectorOnMainThread(Runnable) 3. NSObject.performRunnableOnMainThread(Runnable) Opinions anyone? Arno On 3/24/11 7:53 AM, Paul Poley wrote: > I would not say wrapping performSelector... with a Runnable does not > stick to the Obj-C API. That's not to say I'm objecting to your > solution either. > > Just so I can understand what you mean, could you expand upon what > doesn't stick to it? After all, just because it was originally written > in Java doesn't mean it's not Obj-C after translation. Considering the > end result is running in Obj-C, it seems it is not possible to write > code that works unless it is sticking to the Obj-C API. > > Thanks, > Paul > > On Thu, Mar 24, 2011 at 9:21 AM, Panayotis Katsaloulis > <pan...@pa... <mailto:pan...@pa...>> wrote: > > > On Mar 24, 2011, at 4:12 PM, Paul Poley wrote: > > > Fortunately with XMLVM we can make use of "final" variables, > which are accessible inside run(), so you don't need an argument. > Most of the time you'll probably be writing anonymous inner > classes, which can use those variables. And a more standard class > that implements Runnable can store variables as members. > > > > The nature of Objective-C makes it more difficult to use > performSelectorOnMainThread if we didn't have a place to stick an > argument, but Java & therefore XMLVM makes it simple. > > > This approach is indeed true, my objection though is we don't stick > to the ObjC API then. > This specific method is an ObjC selector, not a Java interface, and > thus I believe we should stick to the official API as much as we can > (even if we create something in-between that doesn't really exist). > > The situation is exactly similar with the NSTimerDelegate - at that > point we could use a Runnable instead of the "NSTimerDelegate" to do > the same job. > Still I believe the path which was followed up to now (a > non-existing interface) is the best. > > > > > ------------------------------------------------------------------------------ > Enable your software for Intel(R) Active Management Technology to meet the > growing manageability and security demands of your customers. Businesses > are taking advantage of Intel(R) vPro (TM) technology - will your software > be a part of the solution? Download the Intel(R) Manageability Checker > today! http://p.sf.net/sfu/intel-dev2devmar > > > > _______________________________________________ > Xmlvm-developers mailing list > Xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers |
|
From: Panayotis K. <pan...@pa...> - 2011-03-24 16:50:44
|
So, to conclude, what the others also say about the API? What should I do? |
|
From: Paul P. <bay...@gm...> - 2011-03-24 14:53:59
|
I would not say wrapping performSelector... with a Runnable does not stick to the Obj-C API. That's not to say I'm objecting to your solution either. Just so I can understand what you mean, could you expand upon what doesn't stick to it? After all, just because it was originally written in Java doesn't mean it's not Obj-C after translation. Considering the end result is running in Obj-C, it seems it is not possible to write code that works unless it is sticking to the Obj-C API. Thanks, Paul On Thu, Mar 24, 2011 at 9:21 AM, Panayotis Katsaloulis < pan...@pa...> wrote: > > On Mar 24, 2011, at 4:12 PM, Paul Poley wrote: > > > Fortunately with XMLVM we can make use of "final" variables, which are > accessible inside run(), so you don't need an argument. Most of the time > you'll probably be writing anonymous inner classes, which can use those > variables. And a more standard class that implements Runnable can store > variables as members. > > > > The nature of Objective-C makes it more difficult to use > performSelectorOnMainThread if we didn't have a place to stick an argument, > but Java & therefore XMLVM makes it simple. > > > This approach is indeed true, my objection though is we don't stick to the > ObjC API then. > This specific method is an ObjC selector, not a Java interface, and thus I > believe we should stick to the official API as much as we can (even if we > create something in-between that doesn't really exist). > > The situation is exactly similar with the NSTimerDelegate - at that point > we could use a Runnable instead of the "NSTimerDelegate" to do the same job. > Still I believe the path which was followed up to now (a non-existing > interface) is the best. > > |
|
From: Panayotis K. <pan...@pa...> - 2011-03-24 14:21:54
|
On Mar 24, 2011, at 4:12 PM, Paul Poley wrote: > Fortunately with XMLVM we can make use of "final" variables, which are accessible inside run(), so you don't need an argument. Most of the time you'll probably be writing anonymous inner classes, which can use those variables. And a more standard class that implements Runnable can store variables as members. > > The nature of Objective-C makes it more difficult to use performSelectorOnMainThread if we didn't have a place to stick an argument, but Java & therefore XMLVM makes it simple. This approach is indeed true, my objection though is we don't stick to the ObjC API then. This specific method is an ObjC selector, not a Java interface, and thus I believe we should stick to the official API as much as we can (even if we create something in-between that doesn't really exist). The situation is exactly similar with the NSTimerDelegate - at that point we could use a Runnable instead of the "NSTimerDelegate" to do the same job. Still I believe the path which was followed up to now (a non-existing interface) is the best. |
