On 4/5/13 5:10 PM, "Gordon Smith" wrote:
>>> Okay, at its heart, the danger Fred was worried about is that, using a merge
>>> workflow, the person who pulls the changes needs to make sure they commit
>>> all changes... even files they didn't touch, because they 'inherit' the
>>> merge.
>
>> D
On 4/5/13 7:22 PM, "Gordon Smith" wrote:
>
> Your link says "Merge is perfectly fine for managing your code." The only
> drawback it mentions is a more cluttered log. It has far stronger warnings
> about misusing rebase.
>
> How could anyone read this conclusion
>
>
> 1. Merge works grea
What should I do to resolve this bugs ?
can you mention what I have to install for that . I have the flash builder
4.5 installed into my system .
On Sat, Apr 6, 2013 at 9:54 AM, Justin Mclean wrote:
> Hi,
>
> There are currently:
> 1 unassigned unresolved blocker bugs
> 20 unassigned unresol
[
https://issues.apache.org/jira/browse/FLEX-33350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cyrill Zadra reopened FLEX-33350:
-
> CallOutButton for Web (desktop / not AIR)
> -
>
>
Congratulations!
On Sat, Apr 6, 2013 at 1:07 AM, Justin Mclean wrote:
> Hi,
>
> The Project Management Committee (PMC) for Apache Flex
> has asked Harbs to become a committer and we are pleased to
> announce that he has accepted.
>
> Harbs has been contributing to Apache Flex for many months on
I'm hoping starting next weekend I'll have a lot more time to dedicate to
getting to some of these. Many are over my head, but I can at least knock
out some of the moderate to easy ones.
-Nick
On Sat, Apr 6, 2013 at 12:24 AM, Justin Mclean wrote:
> Hi,
>
> There are currently:
> 1 unassigned un
Glad to hear you'd like to help. The getting involved page [1] has a
section on squashing bugs (not 100% up to date). It's not 100% up-to-date,
but the gist is you will be creating a patch file based upon your fixes.
To get started you will need to download a Git client. I prefer a GUI
driven o
+1
Successfully built source [1]. Successfully installed binaries[2] and had
it download the flex sdk.
Source built with latest git flex-sdk. Binaries installed with Adobe air
3.6
(Windows 7 64bit, en_US)
[1]
https://dist.apache.org/repos/dist/dev/flex/installer/2.5/RC5/sources/apache-flex-sdk
Hi,
> At least, nobody has gotten on my case for screwing up history.
Run gitk to view. You might be surprised. It's reasonable but it's not 100%
"clean" (for the SDK anyway).
Justin
Hi,
> What should I do to resolve this bugs ?
Take a look at the bug in JIRA [1] and if you can comment on any issue or
confirm or provide sample code showing the issue exists or even better provide
a patch to fix the issues that would be fantastic.
> can you mention what I have to install for
Hey Harbs, you made it ;-)
Glad to have you as part of the team,
EdB
On Sat, Apr 6, 2013 at 6:40 AM, Mark Kessler
wrote:
> Congratulations!
>
>
> On Sat, Apr 6, 2013 at 1:07 AM, Justin Mclean wrote:
>
>> Hi,
>>
>> The Project Management Committee (PMC) for Apache Flex
>> has asked Harbs to be
Mark Kessler created FLEX-33477:
---
Summary: Listbase doesn't expose setSelectedIndex
Key: FLEX-33477
URL: https://issues.apache.org/jira/browse/FLEX-33477
Project: Apache Flex
Issue Type: Improv
[
https://issues.apache.org/jira/browse/FLEX-33350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cyrill Zadra resolved FLEX-33350.
-
Resolution: Fixed
commited your changes - Thank you Marcus.
> CallOutButton for
[
https://issues.apache.org/jira/browse/FLEX-33477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Kessler resolved FLEX-33477.
-
Resolution: Fixed
Fix Version/s: Apache Flex 4.10.0
Updated the methods to be public. Rem
[
https://issues.apache.org/jira/browse/FLEX-33477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Kessler closed FLEX-33477.
---
> Listbase doesn't expose setSelectedIndex
>
>
>
Doesn't the ComboBox need its asdoc updated as well?
On 4/6/13 7:09 AM, "mkess...@apache.org" wrote:
> Updated Branches:
> refs/heads/develop 579e7c307 -> 192a5b2a7
>
>
> Changed setSelectedIndex from mxinternal to public.
>
>
> Project: http://git-wip-us.apache.org/repos/asf/flex-sdk/rep
Welcome on board Harbs.
-Fred
-Message d'origine-
From: Justin Mclean
Sent: Saturday, April 06, 2013 7:07 AM
To: dev@flex.apache.org
Subject: Welcome our newest Apache Flex committer Harbs
Hi,
The Project Management Committee (PMC) for Apache Flex
has asked Harbs to become a comm
Take the habit to prepend the issue id to your commit message, it is useful
if someone wants to see the modified code from the source tab of the Jira
issue.
-Fred
-Message d'origine-
From: mkess...@apache.org
Sent: Saturday, April 06, 2013 4:09 PM
To: comm...@flex.apache.org
Subject:
Tigran,
There are two ways of working with FlexJS/FalconJX. One is to overlay an
Apache Flex SDK with the FalconJX compiler, and another is to work from the
srouce code via Eclipse.
I am still finishing up a zip file and script that will overlay an SDK with
FalconJX. There are several steps, so
On 4/5/13 9:24 PM, "Justin Mclean" wrote:
> I can't see us making a release while we are in this state which is what we
> should be trying to do on a regular basis. We need to be supporting current
> users of the SDK.
How many of these did we "inherit" from Adobe? We should probably focus on
Sounds like an AIR thing. Is what you want possible via PhoneGap/Cordova?
We are looking into having the AS to JS conversion create PhoneGap apps.
On 4/5/13 10:38 AM, "Christian M. Cepel" wrote:
> I'm not certain how things stand with Apache incubating Flex and Adobe
> developing AIR.
>
> I'm
Good point, I'll update it here in a few mins.
On Sat, Apr 6, 2013 at 10:53 AM, Alex Harui wrote:
> Doesn't the ComboBox need its asdoc updated as well?
>
>
> On 4/6/13 7:09 AM, "mkess...@apache.org" wrote:
>
> > Updated Branches:
> > refs/heads/develop 579e7c307 -> 192a5b2a7
> >
> >
> > Ch
Will do. Was actually thinking about that after I checked the log and saw
other ones done that way.
On Sat, Apr 6, 2013 at 11:01 AM, Frédéric THOMAS wrote:
> Take the habit to prepend the issue id to your commit message, it is
> useful if someone wants to see the modified code from the source t
[
https://issues.apache.org/jira/browse/FLEX-33477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Kessler reopened FLEX-33477:
-
Correcting the ASDOC for the combobox to match the listbase asdoc.
> Listbase doesn'
[
https://issues.apache.org/jira/browse/FLEX-33477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Kessler resolved FLEX-33477.
-
Resolution: Fixed
Modified the ASDOC comments for the s:ComboBox setSelectedIndex to match that
[
https://issues.apache.org/jira/browse/FLEX-33477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Kessler closed FLEX-33477.
---
> Listbase doesn't expose setSelectedIndex
>
>
>
> Your link says "Merge is perfectly fine for managing your code." The
> only drawback it mentions is a more cluttered log. It has far stronger
> warnings about misusing rebase.
>
> How could anyone read this conclusion
>
>
> 1. Merge works great, but creates lots of empty merge commits when
Thanks!
It's my honor to be invited. I'll do my best to not disappoint you… :-)
I'm currently working on expanding some of the spark components (such as the
color picker that I just committed). I hope to help put together a CS Extension
for FXG and SVG graphics to make skinning easier as has be
Tigran,
You say "repo/falcon/trunk/compiler.jx/src/*": the 'trunk' in that
path makes me think you have used the SVN instead of the git repo...
Are you sure you are using the 'develop' branch in the git repository
at:
https://git-wip-us.apache.org/repos/asf/flex-falcon.git
EdB
On Sat, Apr 6, 2
Hi list,
ok based on this http://www.youtube.com/watch?v=5COE3hYqCJk tutorial I tried to
checkout the Git in IntelliJ. But I don't get it.
I created a new IntelliJ Project (Java Module) with the name "Apache Flex".
Then I clicked VCS -> Checkout from Version Control -> Git
In the new PopUp I u
What I would do, from memory and the with the experimental lib:
1- First of all clone the sdk as describe in the git wiki, the source root
will be
Setup the SDK (if you want to use the 4.9.1 as base, use the installer and
go directly to the point 6, will the path of the 4.9.1):
2- build t
HI,
> How many of these did we "inherit" from Adobe?
A fair number but certainly not all of them and some of them are still bugs
that need to be addressed.
People have been voting on issue but more votes would help:
https://issues.apache.org/jira/browse/FLEX#selectedTab=com.atlassian.jira.plug
Hi,
> + * @productversion Flex 4
May be best if we put ApacheFlex here that way we have a way to find methods
that have been added in Apache Flex and mark then up in AsDocs (like the Air
methods are).
Justin
So you would like something to the extent of [1]... for both the ComboBox
and ListBase? I don't mind changing them, was just matching them to what
they were supporting.
[1] * @productversion ApacheFlex 4.9
On Sat, Apr 6, 2013 at 6:43 PM, Justin Mclean wrote:
> Hi,
>
> > + * @productversi
BTW should we go back and change that for the previous changes we done as
well? Such as that doubleClickMode. Do we update the flash version and
air version to the current one we are on as well?
On Sat, Apr 6, 2013 at 6:43 PM, Justin Mclean wrote:
> Hi,
>
> > + * @productversion Flex 4
>
Hi,
> So you would like something to the extent of [1]... for both the ComboBox
> and ListBase? I don't mind changing them, was just matching them to what
> they were supporting.
There an open unresolved question if it means the version that it was added in
or the version it supports. I think t
On 4/6/13 5:58 PM, "Justin Mclean" wrote:
> Hi,
>
>> So you would like something to the extent of [1]... for both the ComboBox
>> and ListBase? I don't mind changing them, was just matching them to what
>> they were supporting.
>
> There an open unresolved question if it means the version t
HI,
> I would leave it as Flex instead of "Apache Flex" and update the version to
> 4.10 or whatever is correct.
Reason I suggested "Apache Flex" instead of "Flex" is so we can easily mark new
apache stuff in the asdocs (like AIR only methods etc are marked in ASDocs) I
did work on this ages
Are we trying to actually ship a release soon or is this just practice?
I'll try to get to it later this coming week.
On 4/5/13 9:09 PM, "Justin Mclean (JIRA)" wrote:
>
> [
> https://issues.apache.org/jira/browse/FLEX-33451?page=com.atlassian.jira.plugi
> n.system.issuetabpanels:all-tabp
On 4/6/13 9:25 PM, "Justin Mclean" wrote:
> HI,
>
>> I would leave it as Flex instead of "Apache Flex" and update the version to
>> 4.10 or whatever is correct.
> Reason I suggested "Apache Flex" instead of "Flex" is so we can easily mark
> new apache stuff in the asdocs (like AIR only method
Hi,
> Are we trying to actually ship a release soon or is this just practice?
1. About time we did it been several months since the last (4.9 was Dec/Jan,
4.9.1 was a very minor update). I like to see us releasing every 2 months at a
minimum. The longer we leave it the harder it is to make a re
41 matches
Mail list logo
