Hi
Sent from my iPhone
> On Sep 28, 2017, at 4:15 PM, Idylog - Nicolas Granon
> wrote:
>
> Many thanks !
>
> It is amazing when you realize it is 2017, and we still do not have "smart"
> string comparison libraries...!!!
Actually Apache Lucene and Solr do handle
Many thanks !
It is amazing when you realize it is 2017, and we still do not have "smart"
string comparison libraries...!!! (but we have 4K videos on smartphones and
face recognition and TouchId and contactless credit cards and GPS-aware
watches...)
While you are at it, may I suggest that you
Many thanks for your comments and thoughts,
(this thread is a follow-up of "[FlexJS] Guidelines for implementation of
layout containers and navigation containers" but I felt that the topic was
getting more general).
(May I remind to the readers that my company is not very interested in keeping
Hey Nicolas,
Okay, I figured out the bug, and I think I have it fixed. No need to share your
code or compiler output anymore! Once the next nightly build finishes, you
should be able to download it to get the fix.
It turned out to be a case sensitivity issue. I was able to reproduce the issue
Hi Josh,
Thank you for your answer.
The "web server" is installed locally.
In the compiler arguments, it is just a directory path outside the workspace
with an absolute path (c:/etc.).
And yes, the drive is the same.
Is it possible that forward slashes or backward slashes make a difference ?
(I
I gave it a try on Windows, and I can reproduce the issue. It specifically
seems to be related to passing an absolute path to the output compiler option.
When I use a relative path instead, it shows the correct content inside the
.map file. I'll need to investigate further to figure out exactly
Hi Nicolas,
I just gave it a try on my machine with FlexJS 0.8, and source map file
contained the correct information for the functions in the tag when
I set the source-map option to true and provided a custom output path. I tried
both absolute and relative output paths, and the contents of
Hi Nicolas,
The Application developer is not required to use composition. They are
most welcome to use inheritance just like in regular Flex and in fact, the
MXML component workflow is the same as regular Flex and based on
inheritance.
You are correct about the Faucet analogy. Faucet
Nicolas,
Fully understand your needs. Thanks for a deeper explanation. One of the
things which you can get out of the box is for sure that your business
logic free from Flash dependency in your app can be just used. Compiler
should nicely consume it and give you an JS.
The problem with FlexJS is
Hi Piotr,
Many thanks for your help.
We are not interested *at all* in SWF compatibility or alignment between a SWF
and a JS version.
Our goal is to migrate our browser-based applications catalog out of Flash
player. We will keep AIR apps (desktop/mobile) under the Flex/AIR hood. Common
Check the Mobile project - there are tab and view stack navigators there.
There is also the MobileTrader example that uses them. They are sort-of
iOS oriented since that's what I'm more familiar with. We may need to
re-do these or have alternatives.
For layouts, there is also
Hi Nicolas,
I believe my answer will only partially satisfy you. About containers
exists in FlexJS (Royale) you can read more here [1]. I would strongly
suggest look first on our examples [2]. We do not have ViewStack container,
so I believe that is something which can be implemented and maybe
We need to « re-implement » a ViewStack container component class for use in
a FlexJS (test) project.
Is there a general walkthrough explaining (in details) the principles when
creating a container component for FlexJS (we are mostly interested in the
js output, not SWF).
We have read the docs
13 matches
Mail list logo