I built FalconJS and then tried compiling the sample TestApp.as in the
falcon/trunk/compiler.js/tests as described in the
falcon/trunk/compiler.js/README. I get the following error output:
D:\WORK\Projects\ApacheFlex\repo\falcon\trunk\compiler.js\tests>"../bin/mxml
c" TestApp.as -output TestApp.js
Do I understand it correct that there are currently 2 separate projects for
AS to JS compilation (your, as the Wiki refers to "the Alex's FlexJS" way
and the FalconJx way) which you now try to merge to avoid fragmenting the
efforts?
-Original Message-
From: Alex Harui [mailto:aha...@adobe
We are currently trying to get FalconJX to compile MXML and AS to JS with
output that works with FlexJS. We might change code in FlexJS to make it
easier on FalconJX or vice-versa. FalconJX uses a lot of classes from
Falcon, and more care is needed in changing Falcon as Falcon has to compile
SWFs
I am actually trying to understand how to contribute to the efforts to
compile ActionScript to JS/HTML. I do have some experience with compilers
and the stuff so I hope I will be able to help.
Can you please give me some direction? I tried not to bother anyone and just
follow the instructions in t
[
https://issues.apache.org/jira/browse/FLEX-33350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621786#comment-13621786
]
Justin Mclean commented on FLEX-33350:
--
I noticed there a fair amount of code comment
My guess is that someone working in SVN had a screwed up auto-props
configuration (the part of the config file that maps an added file's extension
to a set of svn properties), resulting in lots of added files incorrectly
getting svn:executable set.
- Gordon
-Original Message-
From: Gor
frameworks/projects/advancedgrids/bundles/en_GB/datamanagement.properties
mistakenly had svn:executable set to * in the SVN repo. I'd guess that any
files actually in the Git repo that have mode 100755 and shouldn't are due to
the same problem originating from incorrect SVN properties. We can si
$ git ls-files --stage | grep "100755"
shows that there are a lot of files that are set as executable that don't need
to be, like:
frameworks/projects/advancedgrids/bundles/en_GB/datamanagement.properties
--Dasa
On Apr 3, 2013, at 4:36 PM, Dasa Paddock wrote:
> You can use this to see what
Ah ok, well, I guess that could be the reason too.
-Fred
-Message d'origine-
From: Gordon Smith
Sent: Thursday, April 04, 2013 1:38 AM
To: dev@flex.apache.org
Subject: RE: How to get a clean working tree for flex-sdk
I do Ant and Git in Cygwin on Windows. Maybe that makes a difference
I do Ant and Git in Cygwin on Windows. Maybe that makes a difference.
- Gordon
-Original Message-
From: Frédéric THOMAS [mailto:webdoubl...@hotmail.com]
Sent: Wednesday, April 03, 2013 4:36 PM
To: dev@flex.apache.org
Subject: Re: How to get a clean working tree for flex-sdk
The weird th
You can use this to see what the mode is set to for a file:
$ git ls-files --stage
--Dasa
On Apr 3, 2013, at 4:29 PM, Frédéric THOMAS
wrote:
> I just read the git mode particularities from [1]
>
> In this case, you’re specifying a mode of 100644, which means it’s a normal
> file. Other opt
The weird thing is it didn't happened to me :P
-Fred
-Message d'origine-
From: Gordon Smith
Sent: Thursday, April 04, 2013 1:32 AM
To: dev@flex.apache.org
Subject: RE: How to get a clean working tree for flex-sdk
So it sounds like the build scripts have somehow made these files
"exec
Cleaning up after building in a Git repo shouldn't be any different than
cleaning up after building in a SVN repo. You do 'ant clean' and if it doesn't
remove everything you fix the 'clean' target.
- Gordon
-Original Message-
From: Harbs [mailto:harbs.li...@gmail.com]
Sent: Wednesday,
+1, in more, I'm doing a wiki to have a good working git configuration and I
have a branch that once merged will solve other issues.
-Fred
-Message d'origine-
From: Gordon Smith
Sent: Thursday, April 04, 2013 1:30 AM
To: dev@flex.apache.org
Subject: RE: How to get a clean working tree
So it sounds like the build scripts have somehow made these files "executable",
which makes no sense for .java and .xml files. I'd prefer that we fix that
rather than ignore mode diffs.
- Gordon
-Original Message-
From: Frédéric THOMAS [mailto:webdoubl...@hotmail.com]
Sent: Wednesday,
Amen to that… ;-)
On Apr 4, 2013, at 2:26 AM, Mark Kessler wrote:
> After reading this, I think I'll stay with my syncing the Flex-SDK to a
> separate folder when I want to build it. Sounds like cleaning up files
> after building in your git repo is a PITA.
>
> -Mark
Well, we're not discussing whether 'ant clean' fully removes all build output.
I hope it does, but I'm not sure how to tell any more. (Probably somehow
running 'git status' without a .gitnore would do it.)
We're discussing the fact that we generally want 'git status' to not show build
output bu
I just read the git mode particularities from [1]
In this case, you’re specifying a mode of 100644, which means it’s a normal
file. Other options are 100755, which means it’s an executable file; and
12, which specifies a symbolic link. The mode is taken from normal UNIX
modes but is much l
The Ant scripts are rewriting these files to inject version numbers. (Ugh!) So
many your suggestion of ignoring mode differences is a good idea.
However, I would still like to understand whether it is possible for Git to set
the executable bit on scripts like mxmlc, like Subversion did.
- Gordo
After reading this, I think I'll stay with my syncing the Flex-SDK to a
separate folder when I want to build it. Sounds like cleaning up files
after building in your git repo is a PITA.
-Mark
AFAIK, yes.
-Fred
-Message d'origine-
From: Gordon Smith
Sent: Thursday, April 04, 2013 1:21 AM
To: dev@flex.apache.org
Subject: RE: How to get a clean working tree for flex-sdk
I looked at these two files in Subversion. Both have only the svn:ol-style
property set, like many other f
I looked at these two files in Subversion. Both have only the svn:ol-style
property set, like many other files.
When you check out a Git branch, can some files get a different mode than
others? In other words, does Git store a mode for each file?
- Gordon
-Original Message-
From: Frédé
You might be right, it's better to determinate why they're changed by the
build, maybe we should find how they were in Svn, it might have happened
that those modes changed during the migration.
-Fred
-Message d'origine-
From: Gordon Smith
Sent: Thursday, April 04, 2013 12:53 AM
To: d
I don't think there is any reason why the file mode of these files should be
changing, so I'm not convinced we should start ignoring diffs of file modes.
- Gordon
-Original Message-
From: Frédéric THOMAS [mailto:webdoubl...@hotmail.com]
Sent: Wednesday, April 03, 2013 3:52 PM
To: dev@fl
Yes.
-Fred
-Message d'origine-
From: Gordon Smith
Sent: Thursday, April 04, 2013 12:50 AM
To: dev@flex.apache.org
Subject: RE: How to get a clean working tree for flex-sdk
Are you saying that it tells Git to ignore differences in a file's mode?
- Gordon
-Original Message-
Fr
Are you saying that it tells Git to ignore differences in a file's mode?
- Gordon
-Original Message-
From: Frédéric THOMAS [mailto:webdoubl...@hotmail.com]
Sent: Wednesday, April 03, 2013 3:48 PM
To: dev@flex.apache.org
Subject: Re: How to get a clean working tree for flex-sdk
It will a
It will avoid git to consider those files as modified, so they won't appear
on git status
-Fred
-Message d'origine-
From: Gordon Smith
Sent: Thursday, April 04, 2013 12:39 AM
To: dev@flex.apache.org
Subject: RE: How to get a clean working tree for flex-sdk
Please explain what that wi
Sorry, you right, I thought I had already merged my branch where the
.gitignore is updated.
-Fred
-Message d'origine-
From: Gordon Smith
Sent: Thursday, April 04, 2013 12:37 AM
To: dev@flex.apache.org
Subject: RE: How to get a clean working tree for flex-sdk
Your repo is not up to d
> that there are some files that need to have their executable bit set, such as
> the mxmlc script.
I knew how to make that happen in SVN, with per-file properties, but I have no
idea in Git.
- Gordon
-Original Message-
From: Gordon Smith [mailto:gosm...@adobe.com]
Sent: Wednesday, A
Please explain what that will do. And before we decide to do this, please be
aware that there are some files that need to have their executable bit set,
such as the mxmlc script.
- Gordon
-Original Message-
From: Frédéric THOMAS [mailto:webdoubl...@hotmail.com]
Sent: Wednesday, April 0
> Your repo is not up to date as I can see from your .gitignore
Why do you think it is not up to date? My .gitignore seems to be like the
current .gitignore in flex-sdk's develop branch, as seen at
https://git-wip-us.apache.org/repos/asf?p=flex-sdk.git;a=blob;f=.gitignore;h=0c84fc394c4ab4a92795a
or 'git config --global core.filemode false' for the general git settings.
-Fred
-Message d'origine-
From: Frédéric THOMAS
Sent: Thursday, April 04, 2013 12:34 AM
To: dev@flex.apache.org
Subject: Re: How to get a clean working tree for flex-sdk
Then I guess everybody should run 'git c
Then I guess everybody should run 'git config core.filemode false' on their
repos, I will add it to the wiki.
-Fred
-Message d'origine-
From: Gordon Smith
Sent: Thursday, April 04, 2013 12:29 AM
To: dev@flex.apache.org
Subject: RE: How to get a clean working tree for flex-sdk
I'd be
> I'd be curious as to what did change in flex-config and Version.java.
Something changed the mode of these two files:
gosmith@GOSMITH-WIN7 /cygdrive/d/asf/flex-sdk
$ git diff frameworks/flex-config.xml
diff --git a/frameworks/flex-config.xml b/frameworks/flex-config.xml
old mode 100644
new mod
Are you saying that if Git says my repo says it is up to date it isn't
necessarily up to date?
No, I never seen that before.
I'm not comfortable which making any changes to this file. I didn't
configure it in the first place as far as I know. Where did it come from?
For the .gitconfig, you s
Are you saying that if Git says my repo says it is up to date it isn't
necessarily up to date?
I'm not comfortable which making any changes to this file. I didn't configure
it in the first place as far as I know. Where did it come from?
- Gordon
-Original Message-
From: Frédéric THOMAS
I can't see anything special but I suggest you to replace its content by [1]
and in more what there's in the wiki relative to the .config, to add
excludesfile = .gitignore to the core section, I'll update the wiki later.
-Fred
[1]
[core]
repositoryformatversion = 0
filemode = false
ba
gosmith@GOSMITH-WIN7 /cygdrive/d/asf/flex-sdk
$ cat .git/config
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
ignorecase = true
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = https
Humm, no idea, could you show me your /.git/config ?
-Fred
-Message d'origine-
From: Gordon Smith
Sent: Wednesday, April 03, 2013 8:01 PM
To: dev@flex.apache.org
Subject: RE: How to get a clean working tree for flex-sdk
If my repo is not up to date, why does doing "git pull" while I'm
If my repo is not up to date, why does doing "git pull" while I'm on the
develop branch produce the output "Already up to date"?
- Gordon
-Original Message-
From: Frédéric THOMAS [mailto:webdoubl...@hotmail.com]
Sent: Wednesday, April 03, 2013 10:51 AM
To: dev@flex.apache.org
Subject: R
Gordon,
Check
https://cwiki.apache.org/confluence/display/FLEX/Git+for+Apache+Flex+Guide
for your .gitconfig
Your repo is not up to date as I can see from your .gitignore, do a git
reset --hard HEAD followed by a git pull --rebase and then rebuild the sdk.
Thanks,
-Fred
-Message d'origi
JC Franco created FLEX-33474:
Summary: RichEditableText should support truncation if editing is
disabled
Key: FLEX-33474
URL: https://issues.apache.org/jira/browse/FLEX-33474
Project: Apache Flex
This is awesome. Thanks Fred!
Om
On Wed, Apr 3, 2013 at 1:12 AM, Frédéric THOMAS wrote:
> Hi all,
>
> I’m please to announce Fisheye has been plugged to our Jira [1], meaning
> that if you prepend the Jira issue id to your commit message, a link to the
> sources relative to this commit will sho
When I have time, I'll investigate whether the unexpected output from 'git
status' is a result of also building flex-falcon with 'ant clean all' after
building flex-sdk with 'ant clean main checkintests'. For example, Falcon tests
recompile a bunch of SWCs and may be producing the bundles.proper
[
https://issues.apache.org/jira/browse/FLEX-33442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imtiaz Islam resolved FLEX-33442.
-
Resolution: Fixed
Re installed Apache Flex 4.9.1 with the option "BlazeDS (Optional)" selected,
Ah, yes, the ASJS Publisher. My bad... I never updated that. I moved
the functionality it provided into FalconJx, so building a project
using that should also provide you with a 'debug' and 'release' build.
So, the Publisher is obsolete, I'll remove it a.s.a.p.
EdB
On Wed, Apr 3, 2013 at 9:09 A
Raimundas Banevicius created FLEX-33473:
---
Summary: DataGrid one direction sorting is not supported.
Key: FLEX-33473
URL: https://issues.apache.org/jira/browse/FLEX-33473
Project: Apache Flex
Hi,
I downloaded and built develop branch of Flex SDK (successful), then built
falcon and falconjx (successful), adjusted build.properties in the ASJS
directory and then tried to publish the sample using ASJS publisher using
the following command line as advised in the README:
ant -Dproject.main.
Btw, thanks Dasa, I didn't know this one.
-Fred
-Message d'origine-
From: Dasa Paddock
Sent: Monday, April 01, 2013 8:10 PM
To:
Subject: Re: Can't build compiler.jx in Eclipse
FYI:
$ git update-index --assume-unchanged
See:
http://git-scm.com/docs/git-update-index
--Dasa
On
And your /.gitignore too ?
Thanks,
-Fred
-Message d'origine-
From: Frédéric THOMAS
Sent: Wednesday, April 03, 2013 10:24 AM
To: dev@flex.apache.org
Subject: Re: How to get a clean working tree for flex-sdk
Gordon,
It looks like your repo is not updated or your config is messy.
Can yo
Gordon,
It looks like your repo is not updated or your config is messy.
Can you show up your /.gitconfig please ?
Thanks,
-Fred
-Message d'origine-
From: Gordon Smith
Sent: Wednesday, April 03, 2013 6:24 AM
To: dev@flex.apache.org
Subject: How to get a clean working tree for flex-sdk
Hi all,
I’m please to announce Fisheye has been plugged to our Jira [1], meaning that
if you prepend the Jira issue id to your commit message, a link to the sources
relative to this commit will show up in the Jira issue source tab as you can
see here [2].
Thanks,
-Fred
[1]
https://support.at
52 matches
Mail list logo
