You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Justin Mclean <ju...@classsoftware.com> on 2012/07/28 04:17:24 UTC
Where to place new apache flex components
Hi,
In the patches branch I created a new apache target in the build script to compile an an apache.swc and a new apache namespace (http://flex.apache.org/ns) to place new components in including the PostCode validator and format classes I created. Is this stuff the preferred option? I'm not entirely sure if consensus was reached on where new components should go.
Thanks,
Justin
Re: Where to place new apache flex components
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> I'm not a big fan of the current "patches" directory only being the
> frameworks directory.
As the build scripts have significantly changed so much I'm transferring it over change by change to the trunk. Once it's done I think the branch can be deleted.
Thanks,
Justin
Re: Where to place new apache flex components
Posted by Nicholas Kwiatkowski <ni...@spoon.as>.
I'm not a big fan of the current "patches" directory only being the
frameworks directory. I don't know what's been submitted to that (other
than the locale's). Is there any way to make sure it includes everything
from trunk?
-Nick
On Mon, Jul 30, 2012 at 9:59 AM, Carol Frampton <cf...@adobe.com> wrote:
>
>
> On 7/27/12 10 :47PM, "Jeffry Houser" <je...@dot-com-it.com> wrote:
>
> >
> > I don't think there has been any consensus. I don't even remember any
> >discussion.
>
> I don't think there has been consensus either other than we don't like the
> odd/even numbering scheme to represent stable and unstable.
>
> Alex and I have been talking about it.
>
> I looked at patches but I don't think that is the right place for two
> reasons - it isn't a complete branch and it needs a better name. I think
> we want a branch from trunk which is the entire trunk so it is easier to
> merge changes back to trunk.
>
> When we talked on Thursday Alex and I decided that we would recommend a
> new branch called unstable which is a complete copy of trunk. New work
> which is more disruptive should go somewhere in the whiteboard area. I am
> going to peruse some of the other projects first to see if I see something
> I think might be better.
>
> I'm willing to create the branch when we decide what we want.
>
> Carol
>
>
Re: Where to place new apache flex components
Posted by Justin Mclean <ju...@classsoftware.com>.
HI,
> I don't think there has been any consensus.
There was at least on the name space URI, the "official" name space prefix "a" or "asf" or "something else" probably not although I went with "a" and that what was checked into the patches branch for several months.
> I don't even remember any discussion.
Might refresh your memory:
http://markmail.org/thread/645gp26orbltmsnr
http://markmail.org/thread/jjrhgx4xuxggzlxx
Plus there were several other long threads.
Thanks,
Justin
Re: Where to place new apache flex components
Posted by Carol Frampton <cf...@adobe.com>.
On 7/30/12 10 :14AM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>Hi,
>
>> I don't think there has been consensus either other than we don't like
>>the
>> odd/even numbering scheme to represent stable and unstable.
>Not sure how this is relevant.
>
>> I think we want a branch from trunk which is the entire trunk so it is
>>easier to
>> merge changes back to trunk.
>+1 to that.
>
>However doesn't really answer my question where these components (which
>have been reviewed on the list and have full unit tests) should be placed
>in the trunk and what namespace they should use.
I see that now. I think you might want to adjust your title to something
like "What namespace should we use for new components?" because both the
namespace and the branch are open questions at this point.
Carol
Re: Where to place new apache flex components
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> I don't think there has been consensus either other than we don't like the
> odd/even numbering scheme to represent stable and unstable.
Not sure how this is relevant.
> I think we want a branch from trunk which is the entire trunk so it is easier to
> merge changes back to trunk.
+1 to that.
However doesn't really answer my question where these components (which have been reviewed on the list and have full unit tests) should be placed in the trunk and what namespace they should use.
Thanks,
Justin
Re: Where to place new apache flex components
Posted by Carol Frampton <cf...@adobe.com>.
On 7/27/12 10 :47PM, "Jeffry Houser" <je...@dot-com-it.com> wrote:
>
> I don't think there has been any consensus. I don't even remember any
>discussion.
I don't think there has been consensus either other than we don't like the
odd/even numbering scheme to represent stable and unstable.
Alex and I have been talking about it.
I looked at patches but I don't think that is the right place for two
reasons - it isn't a complete branch and it needs a better name. I think
we want a branch from trunk which is the entire trunk so it is easier to
merge changes back to trunk.
When we talked on Thursday Alex and I decided that we would recommend a
new branch called unstable which is a complete copy of trunk. New work
which is more disruptive should go somewhere in the whiteboard area. I am
going to peruse some of the other projects first to see if I see something
I think might be better.
I'm willing to create the branch when we decide what we want.
Carol
Re: Where to place new apache flex components
Posted by Jeffry Houser <je...@dot-com-it.com>.
I don't think there has been any consensus. I don't even remember any
discussion.
For the moment, I haven't thought beyond putting stuff in my own
personal white board. For whatever reason, I'm overly cautious about
branching out beyond that.
On 7/27/2012 10:17 PM, Justin Mclean wrote:
> Hi,
>
> In the patches branch I created a new apache target in the build script to compile an an apache.swc and a new apache namespace (http://flex.apache.org/ns) to place new components in including the PostCode validator and format classes I created. Is this stuff the preferred option? I'm not entirely sure if consensus was reached on where new components should go.
>
> Thanks,
> Justin
--
Jeffry Houser
Technical Entrepreneur
203-379-0773
--
http://www.flextras.com?c=104
UI Flex Components: Tested! Supported! Ready!
--
http://www.theflexshow.com
http://www.jeffryhouser.com
http://www.asktheflexpert.com
--
Part of the DotComIt Brain Trust