On 11/23/14, 1:57 AM, "Christofer Dutz" wrote:
>Eventually the ant build bundled the core classes in the opt packages.
>Maven only packages the classes inside the artifact. If you had written
>which classes actually were missing I could have had a better guess.
>Probably you would need to copy
Hi,
> If we get complaints, we should try to find neutral words, but keep in
> mind that the Apache LICENSE itself contains words with “ize” like
> “authorize”. I don’t see how you’ll be able to remove all US English from
> our release packages.
>
> I would need to see a clear picture on how cha
On 11/23/14, 1:59 AM, "Christofer Dutz" wrote:
>I said it's a pain, but I am sadly also familiar with it ;-)
>But not as experienced as he is. So probably he could help setting all up
>and I could continue to maintain the thing.
Makes me nervous because we can still be stranded if you both are
Mustella does try to kill the process after some amount of time with no
output coming to the log but it isn’t always successful. If FlexMojos has
a superior way of killing the player, I suppose we can’t borrow its code,
but if there is some principle missing from Mustella’s process killer,
maybe y
> >>property of type NavigationStack, marked with [ExcludeClass], what does
> that mean?
>
> [ExcludeClass] prevents FlashBuilder from hinting the class and excludes
> it from ASDoc.
>
> I know, I guess I made myself not too clear. I meant with regards to
children nodes auto-completion, subclasses
On 11/23/14, 12:24 AM, "Justin Mclean" wrote:
>Hi,
>
>It boils down to this: About 60-70% of our users understand International
>English, only minor changes are required to accommodate that and be more
>inclusive, why wouldn't we do that?
If we get complaints, we should try to find neutral wor
>>property of type NavigationStack, marked with [ExcludeClass], what does
that mean?
[ExcludeClass] prevents FlashBuilder from hinting the class and excludes it
from ASDoc.
-Darrell
On Sun, Nov 23, 2014 at 6:49 PM, Darrell Loverin
wrote:
> I not sure how complete the MXML support in the falco
Thanks for the tip, it will be rather helpful when the time comes, right
now I've hit some sort of roadblock, I've extended support for
ArrayElementType and DefaultProperty, and I've seen the more classes FD has
to check, the more time it takes to check type constraints. There isn't any
sort of cac
I not sure how complete the MXML support in the falcon compiler so I
checked the old mxmlc compiler. The old mxmlc validates with specialized
if/else statements based on parent and child types for elements that do not
provide [DefaultProperty]. For example, here is a code snippet from
ComponentBuil
Hi Piotr,
I fixed the bug that was causing the vast majority of the errors. Currently
there’s no errors, but six failures in FloatTest:
[flexunit] Suite: UnitTest.Tests.FloatTest
[flexunit] Tests run: 56, Failures: 6, Errors: 0, Skipped: 1, Time elapsed:
22.253 sec
[flexunit]
[flexunit] Re
Phew!
Looks like I fixed this issue. Once I found the problem, the fix was
straight-forward... There’s still some failures with FloatTests, but nothing as
bad as what we were getting before.
I’m going to comment on the other FlexUnit discussion about the remaining
errors.
On Nov 23, 2014, at
Duh!
I’ve actually been working on this for so long, I forgot what I’ve done! :-(
I just looked through the git logs and I see, that I’m the one that added
_curLineStart. The code used to get the index from the TextBlock, but that is
no longer a reliable method of getting the index, so I added
Here’s what I *think* is happening:
1) ComposeState.composeNextLine() calls createTextLine() and gets a TextLine.
2) Part of what BaseCompose.createTextLine() does is: _curLineStart +=
_curLine.textLength. That increases the index of where the line is supposed to
start from. _curLineStart is the
I think this is a minor change and the votes should carry over.
Thanks,
Om
On Nov 23, 2014 10:26 AM, "Justin Mclean" wrote:
> Hi,
>
> > Do the votes from previous RCs carry over?
>
> Depends if you think the changes require checking or not. I'd assume that
> any change to a NOTICE file would req
I went through all the ParagraphElements and TextFlowLines. I added it up, and
it’s clear to me that the _curElementOffset and _cur is being upped by 41 which
is the length of the current line before the line is initialized. That seems to
be throwing everything out of whack.
Now I just need to
I’m back on this. I have a simpler case where things are getting out of sync.
I have a line where the _curElementOffset is 382, the _curElementStart is 803
(total 1201).
The total textLength of the textFlow is 1201.
The _curLineStart is 1185 and the rawTextLength of the TextLine returned by the
Hi,
> Do the votes from previous RCs carry over?
Depends if you think the changes require checking or not. I'd assume that any
change to a NOTICE file would require PMC to re-check and not carry over votes,
given that's one of the critical parts of a release.
Thanks,
Justin
Do the votes from previous RCs carry over?
Thanks,
Om
On Nov 23, 2014 8:29 AM, "Justin Mclean" wrote:
> Hi,
>
> Please place all discussion in this thread and not in the vote thread.
>
> Thanks,
> Justin
>
Hi,
This is a TourDeFlex 1.2 Release Candidate 2. Please see the RELEASE_NOTES and
the README.
Changes since the last RC:
- Re added back in 3rd party examples
- Changes to NOTICE file
The release candidate can be found here;
https://dist.apache.org/repos/dist/dev/flex/TourDeFlex/1.2/rc2/
Bef
Hi,
Please place all discussion in this thread and not in the vote thread.
Thanks,
Justin
What error do you have ?
--- Message initial ---
De : "Christofer Dutz"
Envoyé : 23 novembre 2014 13:14
A : dev@flex.apache.org
Objet : [FALCON] Problems merging tool-api-changes to falcons develop branch
Hi,
I just updated my scripts to use the released version of the flex-tool-api and
want
Hi,
I just updated my scripts to use the released version of the flex-tool-api and
wanted to merge my changes (and some changes to falcon) to the develop branch.
I always had this output when doing a build:
Ant build completed with 5 errors and 44 warnings in 19s at 23.11.14 13:10
So I sort
I think the main problem is that Mustella doesn't seem to be able to handle
problems with the Flash or Air runtime. As far as I understood whenever the
build hangs, usually a flashplayer instance is locked and a user has to click
on a popup. In flexmojos we have this timeout mechanism and it kil
Eventually the ant build bundled the core classes in the opt packages. Maven
only packages the classes inside the artifact. If you had written which classes
actually were missing I could have had a better guess. Probably you would need
to copy some of the 4 core blazeds libs (probably only commo
I said it's a pain, but I am sadly also familiar with it ;-)
But not as experienced as he is. So probably he could help setting all up and I
could continue to maintain the thing.
Chris
Von: Alex Harui
Gesendet: Sonntag, 23. November 2014 07:34
An: dev@fl
Please don’t quote a partial statement. I explained why I thought it will lead
to inconsistency.
I’m done with this discussion until more people weigh in.
Thanks,
Harbs
On Nov 23, 2014, at 11:33 AM, Justin Mclean wrote:
>> But I DO care that whatever it is, it should be consistent.
>
> And I
Hi,
> First of all, we have no data on what percentage of users prefer US English
> relative to International English.
Yes we do see installer download stats in google analytics it give a reasonably
good indication, especially as the sample set is large. You can even get a good
approximation f
For the record:
I have no problems with anyone reworking wording to make the wording more
neutral (as per Alex’s suggestion).
(I personally am not going to invest my own time doing that though…)
On Nov 23, 2014, at 10:54 AM, Harbs wrote:
> Hi Justin,
>
> First of all, we have no data on what
Hi Justin,
First of all, we have no data on what percentage of users prefer US English
relative to International English. Statistics on where users come for are
somewhat of an indication, but only a partial indication. How many people come
from countries where the primary language is English? I
Hi,
It boils down to this: About 60-70% of our users understand International
English, only minor changes are required to accommodate that and be more
inclusive, why wouldn't we do that? Or are you saying that data is incorrect?
Granted most of the users don't care one way or another and that's
The only project which has English other than US English is OpenOffice, and
that is for USER documentation.
I have not seen any evidence that anyone has a problem anywhere with US English
developer documentation.
If none of the other Apache projects have seen a need to translate to
Internation
31 matches
Mail list logo
