What is wrong with the label height calculation?
On 3/14/14 9:17 AM, "Marcus Fritze" wrote:
>
>Am 13.03.2014 um 20:40 schrieb Alex Harui :
>>
>> And if you are using an IDE like IntelliJ or FB, then the easiest path
>>is
>> to use monkey-patching. Create a test project, point the source-path t
Am 13.03.2014 um 20:40 schrieb Alex Harui :
>
> And if you are using an IDE like IntelliJ or FB, then the easiest path is
> to use monkey-patching. Create a test project, point the source-path to
> include the modified AdvancedDataGridBaseEx.as and see if it works.
Thanks, this is working very
org"
Date: Thursday, March 13, 2014 12:33 PM
To: "dev@flex.apache.org"
Subject: Re: [REQUEST] A tutorial on how to fix bugs for the Flex SDK
Am 13.03.2014 um 18:32 schrieb Alex Harui :
So, what is the easies way for working on the SDK? I want to fix a bug.
Well, I'm t
Am 13.03.2014 um 18:32 schrieb Alex Harui :
>> So, what is the easies way for working on the SDK? I want to fix a bug.
> Well, I'm tempted to have you follow this:
> https://cwiki.apache.org/confluence/display/FLEX/Git+for+Apache+Flex+Guide
> because this sets up your environment like most of the
On 3/13/14 9:45 AM, "Marcus Fritze" wrote:
>https://cwiki.apache.org/confluence/display/FLEX/2.1+Flash+Builder
>
>Correct me when I am wrong, but it seems that is not a complete tutorial
>how to setup the SDK for compiling the SDK.
That's about how to use Apache Flex in Flash Builder.
>
>So, wh
, August 02, 2013 2:18 AM
> To: dev@flex.apache.org
> Subject: Re: [REQUEST] A tutorial on how to fix bugs for the Flex SDK
>
> Thanks for all the ideas and tutorial content so far. I think the
> structure that Mark suggested looks great.
>
> Can someone please volunteer to com
ache.org
Subject: Re: [REQUEST] A tutorial on how to fix bugs for the Flex SDK
Thanks for all the ideas and tutorial content so far. I think the
structure that Mark suggested looks great.
Can someone please volunteer to compile this info into a wiki page from
which we can start filling in content sl
t; Rgs,
> >
> > Sugan
> >
> > -----Original Message-----
> > From: jude [mailto:flexcapaci...@gmail.com]
> > Sent: 29 July 2013 05:41 AM
> > To: dev@flex.apache.org
> > Subject: Re: [REQUEST] A tutorial on how to fix bugs for the Flex SDK
> >
&g
Rgs,
>
> Sugan
>
> -Original Message-
> From: jude [mailto:flexcapaci...@gmail.com]
> Sent: 29 July 2013 05:41 AM
> To: dev@flex.apache.org
> Subject: Re: [REQUEST] A tutorial on how to fix bugs for the Flex SDK
>
> I have a suggestion on this tutorial writin
Great idea Jude! Simple and effective.
Rgs,
Sugan
-Original Message-
From: jude [mailto:flexcapaci...@gmail.com]
Sent: 29 July 2013 05:41 AM
To: dev@flex.apache.org
Subject: Re: [REQUEST] A tutorial on how to fix bugs for the Flex SDK
I have a suggestion on this tutorial writing thing
I have a suggestion on this tutorial writing thing. If anyone of you that
have this environment setup can record and upload a raw unedited video I
can edit it or rerecord it and republish it. What I'm thinking is that you
could log out and then log back in as guest, then go through recording the
en
Hmm. The source path is really
"/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/spark/sr
c" (with "/src")? And you aren't using RSLs?
What does a link report say for which Label.as it used?
On 7/26/13 11:57 AM, "Erik de Bruin" wrote:
>It was :-(
>
>EdB
>
>
>
>On Fri, Jul 26, 2
It was :-(
EdB
On Fri, Jul 26, 2013 at 4:10 PM, Alex Harui wrote:
>
>
> On 7/26/13 2:41 AM, "Erik de Bruin" wrote:
>
>>Ok, this is what I tried:
>>
>>I created a new project in FB. It uses the 4.10 SDK in the FB/sdks
>>folder. In "project properties/Flex Build Path" on the "Source path"
>>tab
On 7/26/13 2:41 AM, "Erik de Bruin" wrote:
>Ok, this is what I tried:
>
>I created a new project in FB. It uses the 4.10 SDK in the FB/sdks
>folder. In "project properties/Flex Build Path" on the "Source path"
>tab I added the folder
>"/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/pr
Justin,
I was trying out the method Om and Alex describe. I'm familiar with
the setup you use, as it is the one I use and have had no problems
with. I was interested in the 'direct' method because on paper (in
email) it sounds easier. But I was unable to get the setup to work. I
was hoping Om or A
On 26/07/2013 11:56, Justin Mclean wrote:
Hi,
I created a new project in FB. It uses the 4.10 SDK in the FB/sdks
folder. In "project properties/Flex Build Path" on the "Source path"
tab
Should be no need to do this it should pick up the source automatically.
Sounds like might have both the .sw
Hi,
> I created a new project in FB. It uses the 4.10 SDK in the FB/sdks
> folder. In "project properties/Flex Build Path" on the "Source path"
> tab
Should be no need to do this it should pick up the source automatically.
For instance in the new SDK I just installed command clicking of a framew
rge in the code" option checked ?
>>>
>>> -Message d'origine- From: Erik de Bruin
>>> Sent: Friday, July 26, 2013 11:41 AM
>>> To: dev@flex.apache.org
>>> Subject: Re: [REQUEST] A tutorial on how to fix bugs for the Flex SDK
>>&g
>> Did you make sure you have the "merge in the code" option checked ?
>>
>> -Message d'origine----- From: Erik de Bruin
>> Sent: Friday, July 26, 2013 11:41 AM
>> To: dev@flex.apache.org
>> Subject: Re: [REQUEST] A tutorial on how to fix bugs for the Flex SDK
&
;origine- From: Erik de Bruin
> Sent: Friday, July 26, 2013 11:41 AM
> To: dev@flex.apache.org
> Subject: Re: [REQUEST] A tutorial on how to fix bugs for the Flex SDK
>
>
> Ok, this is what I tried:
>
> I created a new project in FB. It uses the 4.10 SDK in the FB/sdks
Hi Erik,
Did you make sure you have the "merge in the code" option checked ?
-Message d'origine-
From: Erik de Bruin
Sent: Friday, July 26, 2013 11:41 AM
To: dev@flex.apache.org
Subject: Re: [REQUEST] A tutorial on how to fix bugs for the Flex SDK
Ok, this is what I tr
Ok, this is what I tried:
I created a new project in FB. It uses the 4.10 SDK in the FB/sdks
folder. In "project properties/Flex Build Path" on the "Source path"
tab I added the folder
"/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/spark",
thinking this will allow me to work on
On 7/25/13 3:37 PM, "Justin Mclean" wrote:
>Hi,
>
>> but also means you don't have to build the SWCs before testing your
>>changes.
>
>Perhaps I missing the point but if you make a change you will have to
>recompile that project, you just don't have to recompile the entire SDK.
You are correct
Hi,
> but also means you don't have to build the SWCs before testing your changes.
Perhaps I missing the point but if you make a change you will have to recompile
that project, you just don't have to recompile the entire SDK.
Justin
On 7/25/13 10:50 AM, "Erik de Bruin" wrote:
>Cool, this is new to me. The source-path route sound like the
>"easiest" to adopt (for anyone, not just noobs like me ;-)). Are there
>any drawbacks?
Compile time will take longer as it is re-compiling each of the source
files in the source-path ins
Cool, this is new to me. The source-path route sound like the
"easiest" to adopt (for anyone, not just noobs like me ;-)). Are there
any drawbacks? Also, does this mean that you don't even have to build
and decorate the SDK, but can work straight off the code you get from
git?
EdB
On Thu, Jul 2
>
> Like maybe just having folks point a source-path to their local working
> copies. Source-path is supposed to
> take precedence over anything found in the library path. It slows down
> compilation, of course, but also means you don't have to build the SWCs
> before testing your changes.
>
>
We
Just wondering: Should there be different processes for different kinds
of people?
For example, if you don't have any interest in becoming a committer but
have one null check to add, should we support a workflow where you monkey
patch in the null and submit the whole file to the mustella patch te
Clever ;-)
The thing is, you need to download the SDK to get the README. I think Om's
idea is to write up an article or steps page on the website or Wiki,
outlining the entire process of working on the SDK, something that doesn't
belong in the README at all.
EdB
On Thursday, July 25, 2013, Tom
On 25/07/2013 15:06, Erik de Bruin wrote:
IIRC following the README won't give you an SDK that you can use in
Flash Builder. That's why I indicated that a novice contributor might
benefit from a pointer to the 'ide/constructForIDE' script, which
would get his SDK in shape to be used to fix bugs t
IIRC following the README won't give you an SDK that you can use in
Flash Builder. That's why I indicated that a novice contributor might
benefit from a pointer to the 'ide/constructForIDE' script, which
would get his SDK in shape to be used to fix bugs the way you
describe.
EdB
On Thu, Jul 25,
Hi,
> There is a gap between how you build the SDK and how you make and test
> changes to the SDK
Not really once you have a working SDK set up you can just change it and
recompile sub projects as required.
> (working from memory here) After you build the SDK ('ant main') you
> run the script 'i
There is a gap between how you build the SDK and how you make and test
changes to the SDK:
(working from memory here) After you build the SDK ('ant main') you
run the script 'ide/constructFlexForIDE' to prepare the SDK for use in
Flash Builder. You then create your test application (in which you
w
Hi,
I took some notes while fixing this bug.
https://issues.apache.org/jira/browse/FLEX-33165
Any feedback and questions welcome.
Bug information
Note that it's marked as "easyfix" and a RTE. Generally these sort of bugs
don't take much to fix. Looking at the report you can see it's for a mobi
Hi,
This would be great. Yes, this would encourage more involved.
Regards.
Sugan
-Original Message-
From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of OmPrakash
Muppirala
Sent: 24 July 2013 08:09 PM
To: dev@flex.apache.org
Subject: [REQUEST] A tutorial on how to fix bugs fo
bid thumbs up for this
there are lot of people who want to contribute to flex and this would
really help them to get started
Regards
Sumudu
On Thu, Jul 25, 2013 at 5:22 AM, Mark Kessler
wrote:
> Where are we assembling this information? We can use our wiki since it
> already has some of this s
Where are we assembling this information? We can use our wiki since it
already has some of this started... Git information [1], Bug fixing [2].
Well just have to layout the structure before we start.
It's a lot of work up front to get started. Setting up to build the
nightly sdk can be daunting
Hi,
Yep I can help out there.
Justin
38 matches
Mail list logo
