I don't think so. I don't have a compiler.jar in my sdk tree and themes
build.
The build is failing on flexTasks.tasks loading classes from one of the two
flexTasks.jar you see in the build.xml. For me, it is using the one in lib,
not in ant/lib. Is it possible you have a Falcon flexTasks.jar i
Hi,
> If Justin doesn't help you with asdoc, I will try to find time tomorrow.
My build is still broken (unable to build the themes) so unable to help. Are
you sure a falcon dependancy hasn't accidentally got into the SDK release build
- that's the only reference to compiler.jar I could find.
I had to pull before I could see your branch. Once I checked it out, the
build script ran fine on my Mac. If Justin doesn't help you with asdoc, I
will try to find time tomorrow.
On 3/26/13 10:50 AM, "Frédéric THOMAS" wrote:
> Ok, I double checked, all good for the release except the build nu
Yup, let's get it done.
On 3/26/13 7:55 PM, "Om" wrote:
> Here is David@Infra's note about the missing history in the flex-utilities
> git repo.
>
> I think we should accept the repo as it is and move ahead. Any objections?
>
> We can go back to SVN for any history that is missing. I doubt
Here is David@Infra's note about the missing history in the flex-utilities
git repo.
I think we should accept the repo as it is and move ahead. Any objections?
We can go back to SVN for any history that is missing. I doubt we would
need that because it was the early days of the Installer proje
[
https://issues.apache.org/jira/browse/FLEX-33349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Rovira resolved FLEX-33349.
--
Resolution: Fixed
Fix Version/s: Apache Flex 4.10.0
> TypeError #1009 happening in d
[
https://issues.apache.org/jira/browse/FLEX-33349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614822#comment-13614822
]
Carlos Rovira commented on FLEX-33349:
--
I found this weird bug in a combobox componen
[
https://issues.apache.org/jira/browse/FLEX-33349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Rovira reassigned FLEX-33349:
Assignee: Carlos Rovira
> TypeError #1009 happening in dataProviderRefreshed() of List.
>> So, I need to research more about how skinning works in HTML5, but I have
> >> this vague recollection that skins in HTML5 are entirely graphics.
> >
> >
> > I dont think so. SVG is part of the HTML5 spec now, so what we are doing
> > is completely legitimate.
> That's sort of what I meant. I
Get/set methods with prefixes are entirely possible - I just wrote the
implementation in FalconJx - just not very elegant. There is an
alternate solution that uses on function per property and depending on
the amount of arguments (1 for "set" and 0 for "get") it will either
execute the "get" or "se
On 3/26/13 10:44 AM, "Erik de Bruin" wrote:
> I was talking about changes to the JS output, not the AS input. There
> is some obsolete stuff in the Goog JSDoc annotation; the use of
> goog.base() instead of [functionname].call(); maybe use goog.bind()
> and I'm not at all sure what more. We'll
Ok, I double checked, all good for the release except the build number and
the asdoc, so, TLF, empty.properties and .gitignore are ok.
If someone wants to give a hand for the asdoc, run the asdoc target of the
experimental build after you built the sdk.
Once fixed, uncomment in framework.build.
I was talking about changes to the JS output, not the AS input. There
is some obsolete stuff in the Goog JSDoc annotation; the use of
goog.base() instead of [functionname].call(); maybe use goog.bind()
and I'm not at all sure what more. We'll need to discuss the use of
HTML5 "object" methods like "
Ok, I double checked, all good for the release except the build number and
the asdoc, so, TLF, empty.properties and .gitignore are ok.
If someone wants to give a hand for the asdoc, run the asdoc target of the
experimental build after you built the sdk.
Once fixed, uncomment target="doc" /> in
I'm sure you'll be ok too ;-)
Thanks,
-Fred
-Message d'origine-
From: Alex Harui
Sent: Tuesday, March 26, 2013 5:58 PM
To: dev@flex.apache.org
Subject: Re: Release build broken
I'm sure I'll be ok, I don't have any changes in flex-sdk so it will be much
simpler.
On 3/26/13 9:55 AM,
I'm sure I'll be ok, I don't have any changes in flex-sdk so it will be much
simpler.
On 3/26/13 9:55 AM, "Frédéric THOMAS" wrote:
> I have to go in 1h or so, if you want to ask me things before, you're
> welcomed but I think I wrote enough git commands to well start working on
> it.
>
> Thank
I have to go in 1h or so, if you want to ask me things before, you're
welcomed but I think I wrote enough git commands to well start working on
it.
Thanks,
-Fred
-Message d'origine-
From: Alex Harui
Sent: Tuesday, March 26, 2013 5:51 PM
To: dev@flex.apache.org
Subject: Re: Release bu
OK, I will try to run it in a few hours.
On 3/26/13 9:48 AM, "Frédéric THOMAS" wrote:
> Hi,
>
> If you want to work on the same release I'm working on and want the commits
> I did, I created a remote branch 'FLEX-33451'
>
> I assume you're on flex-sdk, whatever the branch you're currently on.
I created an issue for the release ones, so, I work on a branch until
everything will be ok, I'll merge after.
Yes, I need help fot asdoc.
-Fred
-Message d'origine-
From: Alex Harui
Sent: Tuesday, March 26, 2013 5:42 PM
To: dev@flex.apache.org
Subject: Re: Release build broken
On
Hi,
If you want to work on the same release I'm working on and want the commits
I did, I created a remote branch 'FLEX-33451'
I assume you're on flex-sdk, whatever the branch you're currently on.
Before to check it out:
git stash -u "my current work"
To check it out:
git checkout -b origin/FLE
On 3/26/13 9:23 AM, "Frédéric THOMAS" wrote:
> I'm building the release again too right now, do you want me to share my
> branch ?
It sounded like you had enough working to push it. Or are you waiting for
help on the asdoc? I'd rather not have to test the release target right
now, although i
On 3/26/13 12:04 AM, "Om" wrote:
>> But in thinking more about it, your transform of MXMLG or FXG to SVG is
>> essentially an optimization.
>
>
> I would characterize it more as laziness. An XSLT transform is the easiest
> way to get to our end goal, which is rendering fidelity between the
We have tried xsl:fo before and abandoned it because we continually had
issues with it and it didn't match up that well.
We use AlivePDF and have a process where we take pixel positions of text
lines and add lines to the pdf in those positions using the characters on
those lines.
If you change fo
When I test release target, I wait until it asks about OSMF, then copy all
of the downloads from some other folder into the in folder.
Ah ok, thanks.
-Fred
-Message d'origine-
From: Frédéric THOMAS
Sent: Tuesday, March 26, 2013 5:23 PM
To: dev@flex.apache.org
Subject: Re: Release bui
I'm building the release again too right now, do you want me to share my
branch ?
-Fred
-Message d'origine-
From: Alex Harui
Sent: Tuesday, March 26, 2013 5:14 PM
To: dev@flex.apache.org
Subject: Re: Release build broken
OK. Did you push? I didn't see a commit email.
When I test r
What would the change to FlexJS look like? Are you assuming that the
browser has getter/setter support or is there a flag for that?
If it is trivial I can tweak FalconJS to use the right pattern and then
adjust FlexJS for you.
On 3/26/13 3:08 AM, "Erik de Bruin" wrote:
> I wasn't being specif
OK. Did you push? I didn't see a commit email.
When I test release target, I wait until it asks about OSMF, then copy all
of the downloads from some other folder into the in folder.
On 3/26/13 5:44 AM, "Frédéric THOMAS" wrote:
> Just created https://issues.apache.org/jira/browse/FLEX-33451 f
[
https://issues.apache.org/jira/browse/FLEX-33452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614161#comment-13614161
]
Alex Harui commented on FLEX-33452:
---
Please attach source files. I noticed you are usin
Updated the FAQ [1], thank you to review, especially for my English.
Thanks,
-Fred
[1]
https://cwiki.apache.org/confluence/display/FLEX/Git+for+Apache+Flex+Guide
-Message d'origine-
From: Frédéric THOMAS
Sent: Monday, March 25, 2013 7:02 PM
To: dev@flex.apache.org
Subject: Re: [Git/
donjao created FLEX-33452:
-
Summary: NEP with MXMLC
Key: FLEX-33452
URL: https://issues.apache.org/jira/browse/FLEX-33452
Project: Apache Flex
Issue Type: Bug
Components: MXML Compiler
Just created https://issues.apache.org/jira/browse/FLEX-33451 for the issues
relative to the broken release to link with at commit time.
Please forget about "I added a variable 'keepDownloads' to avoid the
download of the thirdparty, usefull because I had to run the release 5
times, not sure y
Frédéric THOMAS created FLEX-33451:
--
Summary: The release build due to the Git migration is broken
Key: FLEX-33451
URL: https://issues.apache.org/jira/browse/FLEX-33451
Project: Apache Flex
Hi,
Just to keep you in touch:
BUILD SUCCESSFUL
Total time: 60 minutes 43 seconds
- I fixed TLF release build.
- I had to comment the asdoc target for the experimental lib until it will
be fixed, see the other thread.
- I will re-integrate into my branch what you did Justin removing the
empty
Hi,
Ok, it seems I solved the TLF release build issues, now I've got asdoc
issues [1] with the experimental lib, did it exist before ?
I don't know anything in as doc generation but from far, I would say, that's
a NS problem between http://flex.apache.org/experimental/ns and the Spark
one, s
I wasn't being specific enough... I should have said: support for
cross-compiling all AS features to FlexJS specific output. This means
basically getting the 'goog' emission complete (nearly there) and
fixing the FlexJS framework to be compatible with 'goog' output (or
introducing a FlexJS emitter,
Quoting Erik de Bruin :
Erik thinks he can do all of this in VanillaJS. I still think it will take
him too long to get to a minimal viable product and VanillaJS will have a
huge minimal download and worry that folks are waiting for him instead of
jumping in on FlexJS hoping he can provide the
The same as me and Alex, I'm on it.
Thanks,
-Fred
-Message d'origine-
From: Om
Sent: Tuesday, March 26, 2013 8:07 AM
To: dev@flex.apache.org
Subject: Re: Release build broken
My ant release fails as well, but because of a different reason:
doc:
[asdoc] Loading con
> What is the difference between goog and FlexJS? It might be better to make
> FlexJS goog-compliant.
There's not that much difference, like I said, for now it looks like
getter/setter handling is the major difference.
I am planning to make FlexJS fully 'goog' compliant as part of my
contributio
My ant release fails as well, but because of a different reason:
doc:
[asdoc] Loading configuration file
C:\p\flex_os\workspace\flexroot\git\flex-
sdk\frameworks\flex-config.xml
[zip] Updating zip:
C:\p\flex_os\workspace\flexroot\git\flex-sdk\framework
s\locale\en_US\mx_
On Mon, Mar 25, 2013 at 8:27 PM, Alex Harui wrote:
>
>
>
> Well, first off, thanks for motivating me to spend more time thinking about
> skinning. Honestly, I don't have a formal plan and your input is quite
> welcome. I spent a fair amount of time mulling over how to re-use as much
> of existi
40 matches
Mail list logo
