from:"serkan . tas"

Re: TextConverter method call

2019-11-28 Thread serkan . tas




Alıntı Serkan Taş :


Hi Alex,

TextConverter :  
https://drive.google.com/open?id=1_6-rBQqTISbeoLvS2-yV8bSFkvS_ApxZ


It is working without any excepiton, but still can not show the text  
in TextArea.


Going to try to find-out why...

Thank,
Serkan

27.11.2019 08:57 tarihinde Alex Harui yazdı:
By deferring the initialization of _descriptors until it is  
actually needed, the code allows FormatDescriptor to get loaded.   
If the initialization code that needs FormatDescriptor runs too  
soon, then FormatDescriptor won't have been loaded yet.


At least, that's the theory,
-Alex

On 11/26/19, 9:50 PM, "serkan@likyateknoloji.com"  
 wrote:


Hi Alex,
 Sorry for inconvenience. I was just sent it before leaving  
home in the

morning. I am going to send you the real code and check your sample
later today.
 But I did not understand the what should I do for FormatDescriptor.
 Is there a workaround ?




--
Serkan Taş
Mobil : +90 532 250 07 71
Likya Bilgi Teknolojileri
ve İletişim Hiz. Ltd. Şti.
www.likyateknoloji.com

--
Bu elektronik posta ve onunla iletilen bütün dosyalar gizlidir. Sadece  
yukarıda isimleri belirtilen kişiler arasında özel haberleşme amacını  
taşımaktadır. Size yanlışlıkla ulaşmışsa bu elektonik postanın  
içeriğini açıklamanız, kopyalamanız, yönlendirmeniz ve kullanmanız  
kesinlikle yasaktır. Lütfen mesajı geri gönderiniz ve sisteminizden  
siliniz. Likya Bilgi Teknolojileri ve İletişim Hiz. Ltd. Şti. bu  
mesajın içeriği ile ilgili olarak hiç bir hukuksal sorumluluğu kabul  
etmez.


This electronic mail and any files transmitted with it are intended  
for the private use of  the persons named above. If you received this  
message in error, forwarding, copying or use of any of the information  
is strictly prohibited. Please immediately notify the sender and  
delete it from your system. Likya Bilgi Teknolojileri ve İletişim Hiz.  
Ltd. Şti. does not accept legal responsibility for the contents of  
this message.

--

Re: TextConverter method call

2019-11-26 Thread serkan . tas


Hi Alex,

Sorry for inconvenience. I was just sent it before leaving home in the  
morning. I am going to send you the real code and check your sample  
later today.


But I did not understand the what should I do for FormatDescriptor.

Is there a workaround ?


Alıntı Alex Harui :


That link took me to the FormatDescriptor class.

The FormatDescriptor exception is a side-effect of having naked  
static initialization code.  We want to defer static initialization  
until it is really needed so that the load order of classes doesn’t  
matter as much (or at all).


My current opinion (again without spending too much time thinking  
about it) is to convert the var into a get function.  Most other  
methods in TextConverter access _descriptor and thus would  
initialize it just-in-time as it is needed.  Something like:


Static private var __descriptors:Array;

static public function get _descriptors():Array
{
  If (!__descriptors) {
_descriptors = [];
addFormat(TEXT_LAYOUT_FORMAT, TextLayoutImporter,  
TextLayoutExporter, TEXT_LAYOUT_FORMAT,__descriptors);
addFormat(TEXT_FIELD_HTML_FORMAT,  
TextFieldHtmlImporter,  TextFieldHtmlExporter, null,__descriptors);
addFormat(PLAIN_TEXT_FORMAT, PlainTextImporter,  
PlainTextExporter, "air:text", __descriptors);

}
  }

And add an optional last param to addFormat to specify the array to  
add to, so it doesn’t access the getter during initialization.


HTH,
-Alex

From: Serkan Taş 
Reply-To: "users@royale.apache.org" 
Date: Tuesday, November 26, 2019 at 8:14 PM
To: "users@royale.apache.org" 
Subject: Re: TextConverter method call

Alex, I have implemented in other way, here it is : >  
https://drive.google.com/open?id=1oPLnVz7jyWJe7Z_V25o773hQYlrRaD6B


But I have another exception in other thread , can you check it ?

subject : "org.apache.royale.textLayout.conversion.FormatDescriptor  
is not a constructor"

27.11.2019 01:34 tarihinde Alex Harui yazdı:
Nevermind, that won’t work in this case.  I think you still need to  
initialize _descriptors with a static initializer.  I think I would  
use an internal version of addFormat for doing that.  Or maybe  
manually code _descriptors as a get/set.


HTH,
-Alex

From: Alex Harui 
Reply-To: "users@royale.apache.org"  


Date: Tuesday, November 26, 2019 at 2:22 PM
To: "users@royale.apache.org"  


Subject: Re: TextConverter method call

Yes, probably a good idea, in which I case I would just use a dummy  
initializer


/** @private */
static public function setFormatsToDefault():Boolean// No PMD
{
_descriptors = [];
addFormat(TEXT_LAYOUT_FORMAT, TextLayoutImporter,  
TextLayoutExporter, TEXT_LAYOUT_FORMAT);
addFormat(TEXT_FIELD_HTML_FORMAT, TextFieldHtmlImporter,  
 TextFieldHtmlExporter, null);
addFormat(PLAIN_TEXT_FORMAT, PlainTextImporter,  
PlainTextExporter, "air:text");

return true;
}
static public var _descriptors:Array;
static private var formatsSet:Boolean = setFormatsToDefault()




From: Serkan Taş  

Reply-To: "users@royale.apache.org"  


Date: Tuesday, November 26, 2019 at 11:44 AM
To: "users@royale.apache.org"  


Subject: Re: TextConverter method call

Do I have to keep addFormat and addFormatAt compatible for external  
usage, because they are public may be called from other classes ?

26.11.2019 21:15 tarihinde Alex Harui yazdı:
It “should” but we are not fully supporting “naked code” (code not  
in methods) right now.  I’ve never liked the pattern and I’m not  
sure all minifiers know how to handle it, so the easiest answer for  
now is to rewrite the pattern.


One way to rewrite is to have setFormatDefaults return an array and  
initialize _descriptors.  Something like:


// register standard importers and exporters
setFormatsToDefault();

/** @private */
static public function setFormatsToDefault():Array// No PMD
{
var arr:Array = [];
addFormat(arr, TEXT_LAYOUT_FORMAT, TextLayoutImporter,  
TextLayoutExporter, TEXT_LAYOUT_FORMAT);
addFormat(arr, TEXT_FIELD_HTML_FORMAT,  
TextFieldHtmlImporter,  TextFieldHtmlExporter, null);
addFormat(arr,PLAIN_T

Re: Tree component not functions correctly

2019-11-06 Thread serkan . tas


Sure, I may have look later today, after work hours :)

Thanks,
Serkan

Alıntı Yishay Weiss :

It’s up to you. If you want to put a breakpoint in  
HierarchicalCollectionView.dispatchAddOrRemoveEvents() and come up  
with a fix that would be very helpful.



From: serkan@likyateknoloji.com 
Sent: Wednesday, November 6, 2019 10:07:13 AM
To: users@royale.apache.org 
Subject: Re: Tree component not functions correctly

Thank you for the info Yishay,

Let me know if I can do anything.

Serkan.


Alıntı Yishay Weiss :


The problem is in
HierarchicalCollectionView.dispatchAddOrRemoveEvents(). Item is
removed and index is incremented so the next item to be removed is
an index too high. I’ll see if I can come up with a safe fix later
today.


From: Yishay Weiss 
Sent: Wednesday, November 6, 2019 8:12:57 AM
To: users@royale.apache.org 
Subject: RE: Tree component not functions correctly


Never mind, I can reproduce it using the example upthread.




From: Yishay Weiss 
Sent: Wednesday, November 6, 2019 6:49:00 AM
To: users@royale.apache.org 
Subject: RE: Tree component not functions correctly


Hi Serkan,



If you open a bug with a clear test case I’ll have a look at it this week.



Thanks,

Yishay




From: Serkan Taş 
Sent: Wednesday, November 6, 2019 5:50:50 AM
To: users@royale.apache.org 
Subject: Re: Tree component not functions correctly

Alex, I am aware what is going on. I, my self emulated 10s of
classes last year. I am not a newcomer.

What I am trying to do is, to move one step forward.

My application is highly dependent on tree component. Can not work without.

I worked on code, tried to find out what is wrong with tree component.

As I do not have deep knowledge on framework, i could not move forward.

E.g. altough expand item function  is commented it is not clear why
still tree is  expended on click. Guess goes with event handling.

If you guide a little I may move further on fw.

Belive me I have lots of things to do on my site after passing fw.

Thanks,
Serkan

Android için Outlook'u edinin




On Wed, Nov 6, 2019 at 12:08 AM +0300, "Alex Harui"
mailto:aha...@adobe.com>> wrote:


Serkan,



In general that’s true of most components.  We emulate what people
need.  We don’t have enough committers to do things just-in-case.
If you tell us what you need, someone will work on it, although it
is even better if you figure out how to emulate whatever is missing
yourself.



Royale is not backed by some corporation like Adobe or Apache.  It
is up to the users to become committers and support and maintain the
code.



-Alex



From: Serkan Taş 
Reply-To: "users@royale.apache.org" 
Date: Tuesday, November 5, 2019 at 11:11 AM
To: "users@royale.apache.org" 
Subject: Re: Tree component not functions correctly



Alex, when I check Tree control, it is not completely emulated.

Just for info.

4.11.2019 07:40 tarihinde Serkan Taş yazdı:

Sure Alex,

1. Step open the page :

[cid:image001.png@01D593DA.0F4C2620]

2. Open "Outbox"

[cid:image002.png@01D593DA.0F4C2620]

3. Close "Outbox" => "Spam " is missing, "Personal" is shown

[cid:image003.png@01D593DA.0F4C2620]

4. Open "Inbox"

[cid:image004.png@01D593DA.0F4C2620]

5. Close "Inbox" =>  "Product Manager" is shown

[cid:image005.png@01D593DA.0F4C2620]

Thanks,
Serkan

4.11.2019 02:26 tarihinde Alex Harui yazdı:

Can you provide a sequence of steps to reproduce the problem? (click
on “foo”, open “bar”, “close “bar”, …)



Thanks,

-Alex



From: Serkan Taş

Reply-To: "users@royale.apache.org"

Date: Sunday, November 3, 2019 at 9:46 AM
To: "users@royale.apache.org"

Subject: Tree component not functions correctly



Hi,

Before trying to fix tree in my project I checked the example in
tourdeflex modules. I would like to learn if anyone has checked that
example because I couldn't make it work.

It fails after some and open/close clicks. Some of the menu items
disappear. I want to make it work before focusing on my own
implementation.

Here is the code :


http://ns.adobe.com/mxml/2009";
   xmlns:s="library://ns.apache.org/royale/spark"
   xmlns:mx="library://ns.apache.org/royale/mx"
   paddingBottom="0" paddingTop="0" paddingLeft="0"
paddingRight="0"
   height="100%" width="100%"
   >

Re: Tree component not functions correctly

2019-11-06 Thread serkan . tas


Thank you for the info Yishay,

Let me know if I can do anything.

Serkan.


Alıntı Yishay Weiss :

The problem is in  
HierarchicalCollectionView.dispatchAddOrRemoveEvents(). Item is  
removed and index is incremented so the next item to be removed is  
an index too high. I’ll see if I can come up with a safe fix later  
today.



From: Yishay Weiss 
Sent: Wednesday, November 6, 2019 8:12:57 AM
To: users@royale.apache.org 
Subject: RE: Tree component not functions correctly


Never mind, I can reproduce it using the example upthread.




From: Yishay Weiss 
Sent: Wednesday, November 6, 2019 6:49:00 AM
To: users@royale.apache.org 
Subject: RE: Tree component not functions correctly


Hi Serkan,



If you open a bug with a clear test case I’ll have a look at it this week.



Thanks,

Yishay




From: Serkan Taş 
Sent: Wednesday, November 6, 2019 5:50:50 AM
To: users@royale.apache.org 
Subject: Re: Tree component not functions correctly

Alex, I am aware what is going on. I, my self emulated 10s of  
classes last year. I am not a newcomer.


What I am trying to do is, to move one step forward.

My application is highly dependent on tree component. Can not work without.

I worked on code, tried to find out what is wrong with tree component.

As I do not have deep knowledge on framework, i could not move forward.

E.g. altough expand item function  is commented it is not clear why  
still tree is  expended on click. Guess goes with event handling.


If you guide a little I may move further on fw.

Belive me I have lots of things to do on my site after passing fw.

Thanks,
Serkan

Android için Outlook'u edinin




On Wed, Nov 6, 2019 at 12:08 AM +0300, "Alex Harui"  
mailto:aha...@adobe.com>> wrote:



Serkan,



In general that’s true of most components.  We emulate what people  
need.  We don’t have enough committers to do things just-in-case.   
If you tell us what you need, someone will work on it, although it  
is even better if you figure out how to emulate whatever is missing  
yourself.




Royale is not backed by some corporation like Adobe or Apache.  It  
is up to the users to become committers and support and maintain the  
code.




-Alex



From: Serkan Taş 
Reply-To: "users@royale.apache.org" 
Date: Tuesday, November 5, 2019 at 11:11 AM
To: "users@royale.apache.org" 
Subject: Re: Tree component not functions correctly



Alex, when I check Tree control, it is not completely emulated.

Just for info.

4.11.2019 07:40 tarihinde Serkan Taş yazdı:

Sure Alex,

1. Step open the page :

[cid:image001.png@01D593DA.0F4C2620]

2. Open "Outbox"

[cid:image002.png@01D593DA.0F4C2620]

3. Close "Outbox" => "Spam " is missing, "Personal" is shown

[cid:image003.png@01D593DA.0F4C2620]

4. Open "Inbox"

[cid:image004.png@01D593DA.0F4C2620]

5. Close "Inbox" =>  "Product Manager" is shown

[cid:image005.png@01D593DA.0F4C2620]

Thanks,
Serkan

4.11.2019 02:26 tarihinde Alex Harui yazdı:

Can you provide a sequence of steps to reproduce the problem? (click  
on “foo”, open “bar”, “close “bar”, …)




Thanks,

-Alex



From: Serkan Taş  

Reply-To: "users@royale.apache.org"  


Date: Sunday, November 3, 2019 at 9:46 AM
To: "users@royale.apache.org"  


Subject: Tree component not functions correctly



Hi,

Before trying to fix tree in my project I checked the example in  
tourdeflex modules. I would like to learn if anyone has checked that  
example because I couldn't make it work.


It fails after some and open/close clicks. Some of the menu items  
disappear. I want to make it work before focusing on my own  
implementation.


Here is the code :


xmlns:fx="http://ns.adobe.com/mxml/2009";

   xmlns:s="library://ns.apache.org/royale/spark"
   xmlns:mx="library://ns.apache.org/royale/mx"
   paddingBottom="0" paddingTop="0" paddingLeft="0"  
paddingRight="0"

   height="100%" width="100%"
   >


























  paddingBottom="10" paddingTop="10" paddingLeft="10"  
paddingRight="10"

  height="100%" width="100%">




labelField="@label"
 showRoot

Re: remoting-config.xml missing error

2019-10-28 Thread serkan . tas




Hi Alex,

Sorry, here are the details :

I updated royale-asjs git repo, and compiled my project with this repo.

I do not have that file in my project : remoting-config.xml


Thanks,
Serkan

Alıntı Alex Harui :

What were you compiling?  How did you get the source (from the repo,  
a source package, etc?


-Alex

From: Serkan Taş 
Reply-To: "users@royale.apache.org" 
Date: Monday, October 28, 2019 at 3:01 AM
To: "users@royale.apache.org" 
Subject: remoting-config.xml missing error

Hi,

After updating the repo, I got the exception below in logs. It does  
not break the compiling process but may someone want to know.


Thanks,
Serkan

remoting-config.xml (Sistem belirtilen dosyayı bulamıyor)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(Unknown Source)
at java.io.FileInputStream.(Unknown Source)
at  
com.google.common.io.Files$FileByteSource.openStream(Files.java:129)
at  
com.google.common.io.Files$FileByteSource.openStream(Files.java:119)
at  
com.google.common.io.ByteSource$AsCharSource.openStream(ByteSource.java:458)

at com.google.common.io.CharSource.readLines(CharSource.java:359)
at com.google.common.io.Files.readLines(Files.java:525)
at  
org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyaleEmitter.postProcess(MXMLRoyaleEmitter.java:525)
at  
org.apache.royale.compiler.internal.codegen.mxml.MXMLWriter.writeTo(MXMLWriter.java:73)
at  
org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:414)
at  
org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:265)
at  
org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:222)
at  
org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:369)
at  
org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:304)
at  
org.apache.royale.compiler.clients.MXMLJSC.staticMainNoExit(MXMLJSC.java:262)

at org.apache.royale.compiler.clients.MXMLJSC.main(MXMLJSC.java:244)



--
Serkan Taş
Mobil : +90 532 250 07 71
Likya Bilgi Teknolojileri
ve İletişim Hiz. Ltd. Şti.
www.likyateknoloji.com

--
Bu elektronik posta ve onunla iletilen bütün dosyalar gizlidir. Sadece  
yukarıda isimleri belirtilen kişiler arasında özel haberleşme amacını  
taşımaktadır. Size yanlışlıkla ulaşmışsa bu elektonik postanın  
içeriğini açıklamanız, kopyalamanız, yönlendirmeniz ve kullanmanız  
kesinlikle yasaktır. Lütfen mesajı geri gönderiniz ve sisteminizden  
siliniz. Likya Bilgi Teknolojileri ve İletişim Hiz. Ltd. Şti. bu  
mesajın içeriği ile ilgili olarak hiç bir hukuksal sorumluluğu kabul  
etmez.


This electronic mail and any files transmitted with it are intended  
for the private use of  the persons named above. If you received this  
message in error, forwarding, copying or use of any of the information  
is strictly prohibited. Please immediately notify the sender and  
delete it from your system. Likya Bilgi Teknolojileri ve İletişim Hiz.  
Ltd. Şti. does not accept legal responsibility for the contents of  
this message.

--

Re: nested states not handled correctly

2019-10-22 Thread serkan . tas




I'll file the bug asap, after work.

Thanks,
Serkan

Alıntı Alex Harui :

OK, I will try to modify your simpler test case at some point.  Feel  
free to file a bug report with the modified simple test case.  The  
easier you make it for us to debug it, the sooner it will get fixed.


-Alex

On 10/21/19, 11:00 PM, "serkan@likyateknoloji.com"  
 wrote:



Alıntı Alex Harui :

> If you have a simple test case of “inclusion in exclusion” then we
> should look at that.  If the only way to see it is to run your
> actual code that’s fine, but I may not have time to look right away.

The code piece I sent, is a standalone single test case which has
excludeFrom in excludeFrom.
If you replace the inner excludeFrom to includeIn you can see the
behavior quickly.
I replaced in the source below, you can check if you like.

>
> I don’t know how many people have existing code with what I’ll call
> “unnecessary states” in them, so I don’t know how valuable it will
> be to the rest of the Royale folks to have an implementation that is
> fault tolerant.  It might be quick and simple to create a variant of
> the states implementation that is fault tolerant.  I don’t know,
> because I haven’t looked to see what the root problem is.
>
> I would stay with states, and either create that fault tolerant
> version or just clean up the “unnecessary states”.   Cleaning up the
> unnecessary states will make your code more efficient than building
> in fault tolerance.

Do you mean inclusion in exclusion is unnecessary or vice versa ?
Because the real case is not exclusion in exclusion but
inclusion exclusion, the sample is just for test as i mentioned.

If yes, than of course I would like to clean "unnecessary" things in
my project rather than doing unnecessary work.

>
> Also, if you really want a fault tolerant states impl,  it might be
> “cheaper” to see if one of the other committers has time to create
> it for you.

I do not like to waste neither my nor the other guys time for the
things that are not really needed to implement.

Thanks,
Serkan

>
> My 2 cents,
> -Alex
>
> From: Serkan Taş 
> Reply-To: "users@royale.apache.org" 
> Date: Monday, October 21, 2019 at 7:02 PM
> To: "users@royale.apache.org" 
> Subject: Re: nested states not handled correctly
>
> Hi Alex,
> 22.10.2019 00:30 tarihinde Alex Harui yazdı:
> There might still be other bugs, but we have not tried to make the
> code worth with exclusions within exclusions.
> Also bugs in inclusion in exclusion
>
>
> In keeping with the PAYG philosophy, we don’t want to burden the
> States implementation with fault tolerance for such conditions.  You
> are welcome to create a variation of the States implementation with
> that fault tolerance if you want.
>
> My application flow is highly dependent on state implementation, so
> I have simply 3 options :
>
> 1. redesign flow without state implementation
> 2. wait for a time to have the bugs fixed
> 3. try to fix it with my own
>
> I am not sure which one feasible for my case, as I can not go P(AYG
> )without one of them, advises ?
>
>
>
> In your example, if the Form as excludeFrom loggedOutState, then
> there should be no need for the child formItem to also have
> excludeFrom loggedOutState.
>
> Seems like i could  not express my self clearly; This code piece is
> just prepared for those who want to see the bug clearly and simply,
> it is not the real case.
>
> Here is the original :
>  
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.google.com%2Fopen%3Fid%3D1AeLJndyE0SnDgCoSdIjgC6hfgubgFnPj&data=02%7C01%7Caharui%40adobe.com%7C16863b9265ed40e9f4e308d756b521fe%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637073208272463395&sdata=%2BoSgLFxgrdQi73tk3ImWGSttjzQYGLvCZBBFdVevvCk%3D&reserved=0

>
>
> Of course, I could be wrong…
> -Alex
>
>
> Thanks,
> Serkan
>
>
> From: Serkan Taş
> 
> Reply-To: "users@royale.apache.org"
> 
> Date: Monday, October 21, 2019 at 12:09 PM
> To: "users@royale.apache.org"
> 
> Subject: nested states not handled correctly
>
> Hi,
>
> Here is the simple example for test case.
>
> In this ex

Re: nested states not handled correctly

2019-10-21 Thread serkan . tas




Alıntı Alex Harui :

If you have a simple test case of “inclusion in exclusion” then we  
should look at that.  If the only way to see it is to run your  
actual code that’s fine, but I may not have time to look right away.


The code piece I sent, is a standalone single test case which has  
excludeFrom in excludeFrom.
If you replace the inner excludeFrom to includeIn you can see the  
behavior quickly.

I replaced in the source below, you can check if you like.



I don’t know how many people have existing code with what I’ll call  
“unnecessary states” in them, so I don’t know how valuable it will  
be to the rest of the Royale folks to have an implementation that is  
fault tolerant.  It might be quick and simple to create a variant of  
the states implementation that is fault tolerant.  I don’t know,  
because I haven’t looked to see what the root problem is.


I would stay with states, and either create that fault tolerant  
version or just clean up the “unnecessary states”.   Cleaning up the  
unnecessary states will make your code more efficient than building  
in fault tolerance.


Do you mean inclusion in exclusion is unnecessary or vice versa ?  
Because the real case is not exclusion in exclusion but

inclusion exclusion, the sample is just for test as i mentioned.

If yes, than of course I would like to clean "unnecessary" things in  
my project rather than doing unnecessary work.




Also, if you really want a fault tolerant states impl,  it might be  
“cheaper” to see if one of the other committers has time to create  
it for you.


I do not like to waste neither my nor the other guys time for the  
things that are not really needed to implement.


Thanks,
Serkan



My 2 cents,
-Alex

From: Serkan Taş 
Reply-To: "users@royale.apache.org" 
Date: Monday, October 21, 2019 at 7:02 PM
To: "users@royale.apache.org" 
Subject: Re: nested states not handled correctly

Hi Alex,
22.10.2019 00:30 tarihinde Alex Harui yazdı:
There might still be other bugs, but we have not tried to make the  
code worth with exclusions within exclusions.

Also bugs in inclusion in exclusion


In keeping with the PAYG philosophy, we don’t want to burden the  
States implementation with fault tolerance for such conditions.  You  
are welcome to create a variation of the States implementation with  
that fault tolerance if you want.


My application flow is highly dependent on state implementation, so  
I have simply 3 options :


1. redesign flow without state implementation
2. wait for a time to have the bugs fixed
3. try to fix it with my own

I am not sure which one feasible for my case, as I can not go P(AYG  
)without one of them, advises ?




In your example, if the Form as excludeFrom loggedOutState, then  
there should be no need for the child formItem to also have  
excludeFrom loggedOutState.


Seems like i could  not express my self clearly; This code piece is  
just prepared for those who want to see the bug clearly and simply,  
it is not the real case.


Here is the original :  
https://drive.google.com/open?id=1AeLJndyE0SnDgCoSdIjgC6hfgubgFnPj



Of course, I could be wrong…
-Alex


Thanks,
Serkan


From: Serkan Taş  

Reply-To: "users@royale.apache.org"  


Date: Monday, October 21, 2019 at 12:09 PM
To: "users@royale.apache.org"  


Subject: nested states not handled correctly

Hi,

Here is the simple example for test case.

In this example;

When you click on the button, the state is switched between two  
states : loggedOutState/loggedInState.


And according to the state definition the form is shows and hides  
according to the state.


The button "nevershown" is never shown because it is excluded from  
both states  loggedOutState/loggedInState.


The one which is strange is the form item "button1". It has the same  
state with the button "nevershown" ,  but behaves like it has no  
excludeFrom tag defined. It behaves similar when you use "includeIn"  
tag.


I am going to debug the code and try to find-out what is wrong, but  
if anybody has any solution and/or idea I highly appreciate.


Thank,
Serkan

Sample test case code


xmlns:fx="http://ns.adobe.com/mxml/2009";

 xmlns:s="library://ns.apache.org/royale/spark"

Re: [ANNOUNCE] Apache Royale 0.9.6 released!

2019-10-09 Thread serkan . tas

Congrats. Piotr and to hole team.

Alıntı Piotr Zarzycki :

The Apache Royale community is pleased to announce the release of Apache
Royale 0.9.6.

The Apache Royale project is the next generation of the Apache Flex SDK. It
lets developers use MXML and ActionScript 3 to generate HTML/JS/CSS
applications which can run natively in browsers. The cross-compiled code
can also run on platforms like Electron or Apache Cordova (Adobe PhoneGap)
to build mobile applications.

This release should be considered ‘beta’ quality, although we’re very close
to a 1.0 release and we have many applications in production at this point.
The purpose of this release is to continue to gather feedback about
Royale’s features and the project’s implementation strategies, and to
recruit new contributors. We hope to grow the code base into an SDK and
tool chain that delivers the highest productivity when developing
applications that can run on many platforms. Beta releases, however, may
not handle all production needs.

Changes in 0.9.6:

Apache Royale Framework 0.9.6:
https://github.com/apache/royale-asjs/blob/apache-royale-0.9.6/RELEASE_NOTES.md
Apache Royale Compiler 0.9.6:
https://github.com/apache/royale-compiler/blob/apache-royale-0.9.6/RELEASE_NOTES.md

Please file bugs at:

https://github.com/apache/royale-asjs/issues

If you happen to know it is a compiler issue, please use:

https://github.com/apache/royale-compiler/issues

For questions about how to use Royale, send email to users@royale.apache.org.
For questions and feedback on the development of the source code in the
release, send email to d...@royale.apache.org.

Apache Royale is available in source and binary form from the Apache
mirrors:

Source:
http://www.apache.org/dyn/closer.lua/royale/0.9.6/apache-royale-0.9.6-src.tar.gz

http://www.apache.org/dyn/closer.lua/royale/0.9.6/apache-royale-0.9.6-src.zip

Binary:
http://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js.tar.gz
http://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js.zip

Binary with SWF support:
http://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js-swf.tar.gz
http://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js-swf.zip

When downloading from a mirror site, please remember to verify the
downloads using signatures or MD5 hashes.

The binary packages can also be installed via NPM.

Mac:
sudo npm install @apache-royale/royale-js -g

Or for SWF Support:
sudo npm install @apache-royale/royale-js-swf -g

Windows:
npm install @apache-royale/royale-js -g

Or for SWF Support:
npm install @apache-royale/royale-js-swf -g

See the README for more information. The language reference (ASDoc) is
here: http://royale.apache.org/asdoc/

Additional documentation is here: https://apache.github.io/royale-docs/

The documentation is still a work in progress. Volunteers are welcome to
help improve it. Visit http://royale.apache.org/ for links to other
resources.

Please try Royale and become involved in shaping the future of application
development.

The Apache Royale Community
--

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

--
Serkan Taş
Mobil : +90 532 250 07 71
Likya Bilgi Teknolojileri
ve İletişim Hiz. Ltd. Şti.
www.likyateknoloji.com

--
Bu elektronik posta ve onunla iletilen bütün dosyalar gizlidir. Sadece
yukarıda isimleri belirtilen kişiler arasında özel haberleşme amacını
taşımaktadır. Size yanlışlıkla ulaşmışsa bu elektonik postanın
içeriğini açıklamanız, kopyalamanız, yönlendirmeniz ve kullanmanız
kesinlikle yasaktır. Lütfen mesajı geri gönderiniz ve sisteminizden
siliniz. Likya Bilgi Teknolojileri ve İletişim Hiz. Ltd. Şti. bu
mesajın içeriği ile ilgili olarak hiç bir hukuksal sorumluluğu kabul
etmez.

This electronic mail and any files transmitted with it are intended
for the private use of the persons named above. If you received this
message in error, forwarding, copying or use of any of the information
is strictly prohibited. Please immediately notify the sender and
delete it from your system. Likya Bilgi Teknolojileri ve İletişim Hiz.
Ltd. Şti. does not accept legal responsibility for the contents of
this message.

Re: EventDispatcher.js:73 Uncaught TypeError: cls is not a constructor

2019-10-01 Thread serkan . tas


Hi Alex,

I registered to google cloud and created a single virtual machine to  
execute my application. I hope it is going to be ready at the end of  
next week, until I'am not available.


After, I will share the url of the application for your check.

Thanks,
Serkan

Alıntı serkan@likyateknoloji.com:

Ok Alex, I am going to work on finding a server to host my  
application and than let you know.


Thanks,
Serkan

Alıntı Alex Harui :

If you can host a test case on a server, we can try to run it in  
our debuggers and then it doesn’t have to be quite as simple.


-Alex

From: Serkan Taş 
Reply-To: "users@royale.apache.org" 
Date: Monday, September 30, 2019 at 12:27 PM
To: "users@royale.apache.org" 
Subject: Re: EventDispatcher.js:73 Uncaught TypeError: cls is not a  
constructor


Hi Alex,

It is related with TabBar. I am going to work on simplify the case  
for specifically of TabBar.


If we talk about the original problem;

I can use debugger, believe me, for over 20 years I use some kind  
:) Only the language is not js mostly.


Maybe it is better to leave this one for later, because it is very  
complex - advanced grid -  and deeply nested in the layout of my  
project.


Thanks,
Serkan
30.09.2019 19:57 tarihinde Alex Harui yazdı:
Not sure about your latest error.  If the TabBar buttons end up  
being Royale Basic components instead of MXRoyale components you  
will get problems like this, but we’ve also seen that the code was  
already set up like this but some sizing thing didn’t get triggered  
in our tests.


Regarding your original problem, did you try using the debugger as  
I suggested?  Learning how to use the debugger is worth it, IMO.   
Modern cars have fault codes for a reason.  It is far faster and  
cheaper to check a fault code and replace the right part than to  
guess as what part to replace.  Same for a debugger.  It can help  
you find the part to replace with far less guessing.


-Alex

From: Serkan Taş  

Reply-To: "users@royale.apache.org"  


Date: Sunday, September 29, 2019 at 6:27 AM
To: "users@royale.apache.org"  

Subject: Re: EventDispatcher.js:73 Uncaught TypeError: cls is not a  
constructor


As I mentioned in the preceding  mail, I could not solve the error.
I am trying to get deeper by disabling inner components.

Now, I am getting an error

[cid:image001.png@01D577D9.3261B390]

for component

child = mx.controls.listClasses.ListItemRenderer

at the line 2724 of UIComponenet.js that the method is  
"getExplicitOrMeasuredWidth()" undefined.


[cid:image002.png@01D577D9.3261B390]

This may be a misuse or bug ?

Thanks,
Serkan
23.09.2019 12:27 tarihinde Serkan Taş yazdı:
I tried removing "excludeFrom" but failed with the same error Harbs.

Here is the debug view of the step which throws exception :

[cid:image003.png@01D577D9.3261B390]

data array content :
[cid:image004.png@01D577D9.3261B390]

[cid:image005.png@01D577D9.3261B390]
[cid:image006.png@01D577D9.3261B390]

[cid:image007.png@01D577D9.3261B390]
23.09.2019 10:33 tarihinde Harbs yazdı:
A likely cause of the problem is the “excludeFrom” piece.  
Definitely try to narrow that down.


I’ve bumped into issues using “includeIn” in the past, and there’s  
likely still bugs related to states. I generally use state.visible  
instead of includeIn.


HTH,
Harbs

On Sep 23, 2019, at 8:45 AM, Serkan Taş  
mailto:serkan@likyateknoloji.com>>  
wrote:


Thanks Alex, just to be sure, can you see the images attached ?


23.09.2019 08:40 tarihinde Alex Harui yazdı:
You’ll have to catch the exception in the debugger and find out  
what “cls” is supposed to be.  That section of code could be run  
quite often when setting up an MXML-based UI.


The MXMLDataInterpreter is interpreting a data array from some .JS  
file representing an MXML file, and initializeStrandBasedObject is  
trying to initialize some component and probably calls  
generateMXMLObject to create some object that initializes some  
property.  You’ll have to figure out what was in the data arrays  
and what went wrong.  You should find that generateMXMLObject is  
passed a data array that is part of a different array passed to  
initializedStrandBasedObject.  Knowing what class that  
strandBasedObject is may help you figure out what part of what MXML  
is having a problem.


HTH,
-Alex



--
Serkan Taş
Mobil : +90 532 250 07 71
Likya Bilgi Teknolojileri
ve İletişim Hiz. Ltd. Şti.
www.likyateknoloji.com

--
Bu elektronik posta ve onunla iletilen bütün dosyalar gizlidir.  
Sadece yukarıda isimleri belirtilen kişiler arasında özel haberleşme  
amacını taşımaktadır. Size yanlışlıkla ulaşmışsa bu elektonik  
postanın içeriğini açıklamanız, kopyalamanız, yönlendirmeniz ve  
kullanmanız kesinlikle yasaktır. Lütfen mesajı geri gönderiniz ve  
sisteminizden siliniz

Re: EventDispatcher.js:73 Uncaught TypeError: cls is not a constructor

2019-09-30 Thread serkan . tas




Ok Alex, I am going to work on finding a server to host my application  
and than let you know.


Thanks,
Serkan

Alıntı Alex Harui :

If you can host a test case on a server, we can try to run it in our  
debuggers and then it doesn’t have to be quite as simple.


-Alex

From: Serkan Taş 
Reply-To: "users@royale.apache.org" 
Date: Monday, September 30, 2019 at 12:27 PM
To: "users@royale.apache.org" 
Subject: Re: EventDispatcher.js:73 Uncaught TypeError: cls is not a  
constructor


Hi Alex,

It is related with TabBar. I am going to work on simplify the case  
for specifically of TabBar.


If we talk about the original problem;

I can use debugger, believe me, for over 20 years I use some kind :)  
Only the language is not js mostly.


Maybe it is better to leave this one for later, because it is very  
complex - advanced grid -  and deeply nested in the layout of my  
project.


Thanks,
Serkan
30.09.2019 19:57 tarihinde Alex Harui yazdı:
Not sure about your latest error.  If the TabBar buttons end up  
being Royale Basic components instead of MXRoyale components you  
will get problems like this, but we’ve also seen that the code was  
already set up like this but some sizing thing didn’t get triggered  
in our tests.


Regarding your original problem, did you try using the debugger as I  
suggested?  Learning how to use the debugger is worth it, IMO.   
Modern cars have fault codes for a reason.  It is far faster and  
cheaper to check a fault code and replace the right part than to  
guess as what part to replace.  Same for a debugger.  It can help  
you find the part to replace with far less guessing.


-Alex

From: Serkan Taş  

Reply-To: "users@royale.apache.org"  


Date: Sunday, September 29, 2019 at 6:27 AM
To: "users@royale.apache.org"  

Subject: Re: EventDispatcher.js:73 Uncaught TypeError: cls is not a  
constructor


As I mentioned in the preceding  mail, I could not solve the error.
I am trying to get deeper by disabling inner components.

Now, I am getting an error

[cid:image001.png@01D577D9.3261B390]

for component

child = mx.controls.listClasses.ListItemRenderer

at the line 2724 of UIComponenet.js that the method is  
"getExplicitOrMeasuredWidth()" undefined.


[cid:image002.png@01D577D9.3261B390]

This may be a misuse or bug ?

Thanks,
Serkan
23.09.2019 12:27 tarihinde Serkan Taş yazdı:
I tried removing "excludeFrom" but failed with the same error Harbs.

Here is the debug view of the step which throws exception :

[cid:image003.png@01D577D9.3261B390]

data array content :
[cid:image004.png@01D577D9.3261B390]

[cid:image005.png@01D577D9.3261B390]
[cid:image006.png@01D577D9.3261B390]

[cid:image007.png@01D577D9.3261B390]
23.09.2019 10:33 tarihinde Harbs yazdı:
A likely cause of the problem is the “excludeFrom” piece. Definitely  
try to narrow that down.


I’ve bumped into issues using “includeIn” in the past, and there’s  
likely still bugs related to states. I generally use state.visible  
instead of includeIn.


HTH,
Harbs

On Sep 23, 2019, at 8:45 AM, Serkan Taş  
mailto:serkan@likyateknoloji.com>>  
wrote:


Thanks Alex, just to be sure, can you see the images attached ?


23.09.2019 08:40 tarihinde Alex Harui yazdı:
You’ll have to catch the exception in the debugger and find out what  
“cls” is supposed to be.  That section of code could be run quite  
often when setting up an MXML-based UI.


The MXMLDataInterpreter is interpreting a data array from some .JS  
file representing an MXML file, and initializeStrandBasedObject is  
trying to initialize some component and probably calls  
generateMXMLObject to create some object that initializes some  
property.  You’ll have to figure out what was in the data arrays and  
what went wrong.  You should find that generateMXMLObject is passed  
a data array that is part of a different array passed to  
initializedStrandBasedObject.  Knowing what class that  
strandBasedObject is may help you figure out what part of what MXML  
is having a problem.


HTH,
-Alex



--
Serkan Taş
Mobil : +90 532 250 07 71
Likya Bilgi Teknolojileri
ve İletişim Hiz. Ltd. Şti.
www.likyateknoloji.com

--
Bu elektronik posta ve onunla iletilen bütün dosyalar gizlidir. Sadece  
yukarıda isimleri belirtilen kişiler arasında özel haberleşme amacını  
taşımaktadır. Size yanlışlıkla ulaşmışsa bu elektonik postanın  
içeriğini açıklamanız, kopyalamanız, yönlendirmeniz ve kullanmanız  
kesinlikle yasaktır. Lütfen mesajı geri gönderiniz ve sisteminizden  
siliniz. Likya Bilgi Teknolojileri ve İletişim Hiz. Ltd. Şti. bu  
mesajın içeriği ile ilgili olarak hiç bir hukuksal sorumluluğu kabul  
etmez.


This electronic mail and any files transmitted with it are intended  
for the private use of  the persons named above. If you received this  
message in error, forwardi

46 matches

Mail list logo