On Nov 17, 2014 2:56 AM, "Erik de Bruin" wrote:
>
> Nice!
>
> Om, Aaron, do you think that you will be able to land the remaining
> contributions in the next two weeks?
>
Yes, highly likely to wrap everything up in the next couple of weeks.
Thanks,
Om
> EdB
>
>
>
> On Mon, Nov 17, 2014 at 2:43
On Mon, Nov 17, 2014 at 3:05 PM, Alex Harui wrote:
> On 11/17/14, 3:02 AM, "Flexicious.com" wrote:
>
> >
> >Sorry team for being late to the topic, but having read through the
> >thread,
> >am I correct in assuming that we need to provide a 600X400 image for our
> >products?
>
> Hi,
>
> Om wro
On 11/17/14, 3:02 AM, "Flexicious.com" wrote:
>
>Sorry team for being late to the topic, but having read through the
>thread,
>am I correct in assuming that we need to provide a 600X400 image for our
>products?
Hi,
Om wrote the code so he’d know for sure, but I think it just has to be
“high-r
Right. My question is more related to TextFlowLines than Slugs though.
Let’s say a flowComposer has an array of TextFlowLines and the geometry of them
does not fit in the new composition space. What is supposed to happen to the
old TextFlowLines? I’m having trouble understanding the architecture
I don’t know for sure, I just looked up the Slug class. It says it is
created by Parcels to track geometrical line information.
Maybe a simpler test case would help you understand the desired behavior?
I would think at some point if the composable areas change, the Parcels
and their Slugs get upd
+1 (Binding)
OS: Win7 64bit
Java: 1.8 64bit
Readme/Release notes/Notice/license: fine.
Source build: successful (16 mins).
Poked around on some examples worked fine.
-Mark
On Fri, Nov 14, 2014 at 8:40 AM, Justin Mclean
wrote:
> Hi,
>
> This is a TourDeFlex 1.2 Release Candidate 1. Please
Hi Om,
I created another pull request, this fixes a few bugs and an issue with the
lateral menu sliding out. I also added in a drag to close and a new view for
some more native air features. I would like to create a better landing page,
any ideas?
thanks,
Aaron
--
View this message in context
Hi Om,
here is the jira ticket I created for stagedtextinput, stagedtextarea,
textinput, and textarea.
https://issues.apache.org/jira/browse/FLEX-34641
Let me know if you have any issues.
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/iOS7-component-s
+1
Package
https://repository.apache.org/content/repositories/orgapacheflex-1002/org/a
pache/flex/flex-tool-api/1.0.0/flex-tool-api-1.0.0-source-release.zip
Java 1.7
OS: Mac OS X x86_64 10.9.5
Source kit signatures match: y
Source kit builds: y
README is ok: y
RELEASE_NOTES is ok: y
NOTICE is ok:
OK, added.
On 11/17/14, 4:01 AM, "Frédéric THOMAS" wrote:
>Squiggly as Components is not set yet, I selected "Runtime Shared
>Libraries".If someone as the Karma and the time to set "Squiggly" as
>Components, I'll change it.
>
>Frédéric THOMAS
>
>> Date: Mon, 17 Nov 2014 11:59:33 +
>> From: j
# AIR version numberair.version = 14.0
Frédéric THOMAS
From: webdoubl...@hotmail.com
To: dev@flex.apache.org
Subject: RE: [Installer] versions mismatch (was: [jira] [Created] (FLEX-34640)
Squiggly: Generate / Package RSLs and deploy with Maven)
Date: Mon, 17 Nov 2014 14:10:12 +
Anyway, I
Anyway, I don't think it is correct in build.xml:
Frédéric THOMAS
> From: webdoubl...@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: [Installer] versions mismatch (was: [jira] [Created]
> (FLEX-34640) Squiggly: Generate / Package RSLs and deploy with Maven)
> Date: Mon, 17 Nov 2014 13:17:1
I've been able to make the build generate / package RSLs and deploy them in my
local maven repo, 2 things though :
1- In maven.xml, the next version is 1.1 (), is it wise given 1.0-snapshot hasn't been released yet ?
(I would rather set it to 1.0 until we release)
2- The RSLs can be generated fro
Forget about that, just noticed player global was hard coded in the
main/build.xml, I thought it was a mismatch, sorry for the noise.
Frédéric THOMAS
> From: webdoubl...@hotmail.com
> To: dev@flex.apache.org
> Subject: [Installer] versions mismatch (was: [jira] [Created] (FLEX-34640)
> Squiggly
Hi,
One moth ago or so, I used the Installer 3.1.0 to install flex-4.13-AIR-15,
today, I tried with Ant to build Squiggly against it, I ran into something
weird, when it tried to compile libs like the Spelling Framework against the
player global, I received this message [1] following the failure
Squiggly as Components is not set yet, I selected "Runtime Shared Libraries".If
someone as the Karma and the time to set "Squiggly" as Components, I'll change
it.
Frédéric THOMAS
> Date: Mon, 17 Nov 2014 11:59:33 +
> From: j...@apache.org
> To: iss...@flex.apache.org
> Subject: [jira] [Crea
Just to be a little clearer:
I’m not sure why this used to work, and now it doesn’t.
It seems to me that if the parcel changes on a TextFlowLine, the
outerTargetWidth could be changed and the TextLine regenerated. (Then the Slug
and the outerTargetWidth should match.) The thing is, the code did
I’ve tried to make as few changes to the APIs as possible. 99.9% of users will
be able to switch transparently.
I am currently using the tables branch in the beta version of my software.
That’s how I’m turning up these bugs. When I’m ready to push out to production,
it should be in pretty good
Harbs,
Once you will be ready to start working on tests for tables we can schedule
another session on skype. I will guide you through code one of the existing
test class. :)
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.2
Hi Erik,
I did merge of my code (TLF unit tests - develope) into the Harbs's branch
(tables). I have managed to successful launch most of the tests on Harbs's
code however couple of them failed.
I will try to find some time later this week and look into this.
Piotr
-
Apache Flex PMC
pio
Sorry team for being late to the topic, but having read through the thread,
am I correct in assuming that we need to provide a 600X400 image for our
products?
On Tue, Nov 11, 2014 at 2:27 PM, OmPrakash Muppirala
wrote:
> >
> > 1) get your thoughts on taking Flexicious out of 3rdparty.xml so t
What is you 'gut feeling' about the backwards compatibility of the table
branch? In your project, I assume you use a lot of TLF code. I think I
remember you have a very large text based application ... Will you be using
your branch for your release software?
I'm asking so I can figure out if we wa
Right now I’m working on a pretty serious bug in the table code related to
recomposition of TextFlowLines. (See the other thread.)
Once I have that behind me, I plan on trying to get some tests set up. Piotr
already merged the test code in with the table code, so that part is done.
On Nov 17, 2
Nice!
Om, Aaron, do you think that you will be able to land the remaining
contributions in the next two weeks?
EdB
On Mon, Nov 17, 2014 at 2:43 AM, quick6black wrote:
> Hi Om,
>
> I have them done, will submit them tomorrow
>
> Aaron
>
>
>
> --
> View this message in context:
> http://apache
Hi guys,
Can you update us on the status and "planning" (note the quotes, the
project doesn't require any schedule) of your contributions?
Thanks,
EdB
On Wed, Oct 29, 2014 at 12:13 PM, piotrz wrote:
> Thanks Erik! :)
>
> Harbs I've sent you an invitation on skype.
>
> Piotr
>
>
>
> -
>
I took a little break on this to deal with some other crises.
I found where it’s going off:
In BaseCompose.fitLineToParcel() this check was failing:
// check to see if we got a good line
if (Twips.to(_lineSlug.width) !=
_curLine.outerTargetWidthTW
Github user doublefx commented on the pull request:
https://github.com/apache/flex-utilities/pull/3#issuecomment-63282420
Has been merged.
This closes #3
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user doublefx closed the pull request at:
https://github.com/apache/flex-utilities/pull/3
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Hi,
I just dropped the RC2 staging repo and created a new one RC3
(orgapacheflex-1002) which should contain all the pom-fixes we recently
discussed. Now the README is fixed and all assembly descriptors have Apache
headers.
You can have a look at the staging repo at:
https://repository.apache.
Ok ... so after all adjusting the files again, I fixed the README again and
staged RC3 ... hopefully now all will be sattisfied :-)
Chris
PS: Starting the new vote thread now
Von: Erik de Bruin
Gesendet: Montag, 17. November 2014 09:28
An: dev@flex
I ran rat, it didn't catch anything but the DEPENDENCIES, for which I added
an exception. Are these files platform specific?
And the 'nits', you can basically do what you think is best, but at the
risk of starting another huge thread about nothing: either en_US or en_GB
are perfectly fine for the
31 matches
Mail list logo
