On Mon, Jan 28, 2013 at 10:36 AM, Michael Schmalle
<apa...@teotigraphix.com>wrote:
Quoting Frank Wienberg <fr...@jangaroo.net>:
Hi Alain,
for Jangaroo, I answered this question here:
http://markmail.org/message/**bwjwc7sxfbertu7f<http://markmail.org/message/bwjwc7sxfbertu7f>
For Flex / FalconJx, it seems nobody was extremely fond of the idea to
have
to keep all the white-space and take care of generating JS code in the
exact line of the source AS code.
Ok, Do I have to start another thread with exclamation marks for everybody
to tone the .... down!
I cannot believe this conversation is taking the spin it is right now,
some of the discussions the last two days have been ridiculous and serve no
constructive purpose to any of these "initiatives".
Frank, Being that I am about the only one working on FalconJx "innards"
and conceived a way to even HAVE alternate outputs (just look at FalconJS's
rats nest code), I would be offended by the above statement, if I was the
type that actually get offended, which I'm not. (I left out the "doomed"
statement)
Sorry, Mike, I surely didn't mean to offend you. If it sounded like that, I
apologize. You probably know I am not a native speaker, so maybe this got
across badly.
I just wanted to say that I brought in the Jangaroo idea to keep the
white-space, and the common reaction was that we should (at least for the
first iteration) go without that feature, to keep things simple and focused
on the main problems. I accepted that, while I admit I am still a bit
disappointed that it seems the value of this feature is not shared by
everyone. Sorry again if I got carried away.
Talking about the "doomed" statement, please don't take this out of
context. It was my reaction on Erik's answer that sounded to me like he
thinks debugging in Flash suffices (he put that right later on). I thought
you share the vision that Flex must be usable for (pure) HTML5 projects to
have a bright future. This is the reason why I support this project,
because I believe in the HTML5 platform, but it needs better development
support, which Flex could offer! I never said anything like Flex should
drop the Flash or AIR target, I just said if it does not also support
JS/HTML5 as a first class target platform, I consider it doomed (and this
is my personal judgement).
I SAID I would get you going on the output you need for "your" vision(with
line numbers if need be) of the javascript emitter.
What on earth made you think I doubt that you will do so? I marvel at your
work on FalconJx and I'm sure you are the best person to get me into it!
I have put 100's of hours into this project and will be damned if it is
doomed by squabbling over implementations. I'm a tool maker, Don't confuse
the tool with the JOB! You and Erik are bickering about the Job, I am
working on the tool, please do not confuse the two.
I don't get exactly what you mean by the "Job". The Goal? Before building a
tool, you have to know what it should be used for. Erik and I seem to have
different views on what people will use the Apache Flex tool for. I feel it
is important to at least find out that this is so, even if you cannot
settle the differences.
Well, I guess I started another thread cause I don't want this buried.
Mike
No, I don't want this to be buried, either. I am still quite new in this
community, so please forgive me if I stepped on your or somebody else's
foot. It is really hard for me, having worked on the topic AS->JS for so
many years, to not be biased toward a solution that has formed from that
experience. So I am quite passionate about some points and I still hope I
can help you (plural!) to not run into some of the dead-ends I already
visited on my journey.
Best,
-Frank-
