Hi Serkan,
I'm sorry, I keep finding some of your emails in my junk mail. I haven't found
a way to prevent that. And it has been a particularly busy time for me
recently so sorry for not responding sooner.
I've read this three times now and I'm not sure what kind of response you are
looking for. I think we all appreciate that you are still working with us.
I’m still trying to find time to help you, but I can't always get to your
issues right away.
As with any user, the hope is that they will learn how the framework works and
improve their ability to work with us and eventually provide patches and pull
requests and earn committer status. Becoming less reliant on current
committers is your best insurance for the future. If you have ideas on how
that can happen let us know. I keep hoping other committers will help you
more, but they also have their own priorities to juggle. Also, many of the
available committers are independent developers so they are going to prioritize
paid work, whereas I don't have to.
IMO, working with the framework code is different than working on application
code, especially if the application code is your own code. You are not
obligated to try to learn the framework code and remain more of a user than a
committer. That said, the better your understanding of the framework, the more
efficient the cycle of reporting and fixing bugs will be because the test cases
will be easier to work with and you may even provide the answer yourself. So
similarly, if you are interested in learning the framework and have ideas on
how that can happen let us know. The unfortunate fact is that there really
isn't a whole lot of documentation and the current set of committers are
unlikely to be able to stop and provide a bunch of documentation so it tests
one's skill at figuring out other people's code.
I don't doubt that you are trying your best to provide good test cases. And my
apologies if you felt I singled you out by saying that your test cases could
use improvement. You are not the only one who submits test cases that need
fixing or simplification. I think that's something that would improve as your
knowledge of the internals of the framework improves.
For example, in this recent MenuBar case, the issue was not locales at all, but
two other parts of the framework: DataBinding to XML (not from) and Collection
notification. I was able to much more efficiently build and debug a test case
without involving locales. On your insistence, I did take the time to create a
test case to prove that locale changes would update XML via DataBinding
correctly. The better your understanding of the framework, the fewer times I
will have to go do that.
For the TextArea issue, stack traces are like fingerprints. They help identify
that the same culprit is the problem. Learning to identify stacktraces helps
make the development process more efficient. Instead of filing a bug with a
stack trace and waiting for me to find time, it would better if somehow you
could have realized it was the TextArea issue yourself and then we could have
saved time and started discussing the choices. I started on a "reduced"
emulation of Spark TextArea, but I put it on the shelf because it appeared that
you had switched to mx:TextArea. If you only have a few s:TextAreas, then it
might be more efficient to just replace those few instances instead of waiting
for me to find time to finish this version and debug it. But if you have
dozens of them, it might make more sense to see if we can get a reduced
emulation working.
If you are willing to keep using Royale, I will keep trying to help you. I may
not be able to help you as quickly as you like. If you can find a way to get
to know the framework code better, I think that will be the best thing for you
and hopefully all of us can help with that to some degree. If you have money,
you can pay one of the other committers to prioritize your issues. My help is
free and cannot be paid for, but then you can't get prioritized either.
HTH,
-Alex
On 5/29/20, 7:14 AM, "serkan" <ser...@likyateknoloji.com> wrote:
No response means some kind of response Harbs,
Thank you for considering
Serkan
27.05.2020 15:07 tarihinde Harbs yazdı:
> I noticed this email a couple of weeks ago assuming that someone who has
been more involved in the emulation work would respond. It just occurred to me
that Serkan never got a response.
>
> I assume people were busy and/or missed this.
>
> From my perspective I’ve been looking at what Serkan has been doing
favorably, but I have not been focused on emulation or really involved much in
that work.
>
> Piotr, Greg, Yishay or Alex (or anyone else who’s been involved) could
someone respond to this and give Serkan some feedback?
>
> Thanks!
> Harbs
>
>> On May 16, 2020, at 10:50 PM, serkan <ser...@likyateknoloji.com> wrote:
>>
>>
>> Hi all,
>>
>> Moving to list because it became something more than issue comment.
>>
>> Nearly two year - starting with emulating classes - I am trying to make
my flex application running with royale emulation.
>>
>> But more than my application, I am trying to be the part of the project
that I believe doing very good things mostly the help of Alex and help to
remove issues related with emulation components
>>
>> The way I go :
>>
>> 1. Running my app discovering the non-functioning parts.
>> 2. Trying to isolate the case from application - sometimes really time
consuming issue because it is client-server app.
>> 3. Preparing a case than can be compiled and executed without server and
simplify as possible
>> 4. Creating the issue and attaching the case to the issue
>> 5. Additionally porting the java script files to a server to make online
testing available.
>>
>> And let me go step by step.
>>
>> /*If you have an issue with locale change, then create a test case I can
run locally that uses a bundle I have (like one from Flex) that exposes the
issue. If it is notifications, it should not be necessary to involve MenuBar or
XML. Maybe a string in a Label.*
>>
>> /If every text in the application is changing with the locale change
except the menubar which is populated with xml, is staying with the initial
locale how can I create the case ?//I do not know any other to express myself/.
/I am open to advises.
>>
>> /*
>> Almost all of the past examples you've sent that involve resources have
been simplified by using string substitution. So that's what I did to this
example, and sure enough, the MenuBar did not update, so I proposed a
workaround.*/
>>
>> All the cases I am attaching the issues are the isolated sources from
the application sometimes does not have any similarity with app except the bug.
I value your propositions.
>>
>>
>> /*I don't recall asking you to host live examples of these scenarios. I
would only look at live examples if I could not reproduce a problem locally
because locally I have all of the source so I know there aren't any
side-effects from other modules and can re-compile with a change if needed.*/
>>
>> I am trying to make it easier for you to view the issue with less effort
but I can see it is going to the opposite direction.
>>
>>
>> /*For your TitleWindow issue, I just looked at the call stack and could
see that it was another case of s:TextArea.*/
>>
>> TitleWindow is the case that we have discussed couple of months ago.
Replacing s:TextArea with mx:TextArea need some additional investigation
because the component creation call hierarchy is working different and I am
going to let you know after my investigation.
>>
>> /*
>> I'm not going to first try remote debugging. It just isn't efficient for
me. I'm sorry you don't like the way I work. */
>>
>> My aim for preparing the live demo is not the alternative for the
attached case but the identical working one in case you need to see it alive.
>>
>> I am not trying teach anyone or you Alex which way to work, because I do
not want anyone to try to do the same to me, I am just trying to help you to
get case as soon as possible but unfortunately it did not worked.
>>
>> Do not have any comments on the way you work - like or dislike.
>>
>> /*
>> You are welcome to tell me not to help you anymore and get someone else
to help you.
>>
>> */Nearly 99% of the time only you are interested and involved in
emulation components and the bugs./**/How can this be possible or realistic ?
>>
>> At least why I should think that way ? Of course not. Just want to
express my self.
>>
>> But if you think this is not helping Royale for improving the emulation
components you just tell me to drop.
>> /*
>> */Thanks,
>> Serkan
>>
>> -------- İletilmiş İleti --------
>> Konu: Re: [apache/royale-asjs] Can not change locale for menubar
constructed via XMLList within declarations (#824)
>> Tarih: Sat, 16 May 2020 09:00:15 -0700
>> Kimden: aharui <notificati...@github.com>
>> Reply-To: apache/royale-asjs
<reply+abnu4sqwu5ue3vgvqfxd6v54zpxq7evbnhhcjgj...@reply.github.com>
>> Kime: apache/royale-asjs <royale-a...@noreply.github.com>
>> CC: Serkan Taş <ser...@likyateknoloji.com>, Author
<aut...@noreply.github.com>
>>
>>
>>
>> If you have an issue with locale change, then create a test case I can
run locally that uses a bundle I have (like one from Flex) that exposes the
issue. If it is notifications, it should not be necessary to involve MenuBar or
XML. Maybe a string in a Label.
>>
>> Almost all of the past examples you've sent that involve resources have
been simplified by using string substitution. So that's what I did to this
example, and sure enough, the MenuBar did not update, so I proposed a
workaround.
>>
>> I don't recall asking you to host live examples of these scenarios. I
would only look at live examples if I could not reproduce a problem locally
because locally I have all of the source so I know there aren't any
side-effects from other modules and can re-compile with a change if needed.
>>
>> For your TitleWindow issue, I just looked at the call stack and could
see that it was another case of s:TextArea. I'm not going to first try remote
debugging. It just isn't efficient for me. I'm sorry you don't like the way I
work. You are welcome to tell me not to help you anymore and get someone else
to help you.
>>
>> —
>> You are receiving this because you authored the thread.
>> Reply to this email directly, view it on GitHub
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F824%23issuecomment-629667547&data=02%7C01%7Caharui%40adobe.com%7C29ac717f0d82459c0a5c08d803da9ed4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637263584794753365&sdata=m8Hxn2%2B%2Bur2YpepzeVSa3kTh8miQ8On2m7n3DfAenDk%3D&reserved=0>,
or unsubscribe
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABNU4SVCTHKCFSOIGOD6GGDRR22A7ANCNFSM4M3I4SIQ&data=02%7C01%7Caharui%40adobe.com%7C29ac717f0d82459c0a5c08d803da9ed4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637263584794763356&sdata=ohlyri4fLGJl3GmCPUUQBx0lum3kUWa4jlIO8dhYUJ8%3D&reserved=0>.
>>
