Re: [RT] Repositories & Artifacts

On 15/03/2012 14:17, Yennick Trevels wrote: While Sonatype may have a pretty strict requirement regarding project dependencies, it's also a good thing because it makes sure that all the dependencies can be found on the Maven Central repository. I do not bother so much about the strictness, i bo

Re: [RT] Repositories & Artifacts

While Sonatype may have a pretty strict requirement regarding project dependencies, it's also a good thing because it makes sure that all the dependencies can be found on the Maven Central repository. Maven Central is also the default repository for Maven, so the user doesn't have to specify an ext

Re: [OT] 360 Flex Denver 2012 - Apache Flex Discovery Room

On 3/14/12 8:16 PM, "Om" wrote: > Would this work? > http://www.vistaprint.com/name-tag-stickers.aspx?txi=212&xnid=VisitorHomePage2 > 12_202_131&xnav=TeaserItem > That looks more like name badges. I was thinking of a round button with just the logo and the word Committer. -- Alex Harui Fle

Re: [OT] 360 Flex Denver 2012 - Apache Flex Discovery Room

On 15/03/2012 12:45, Jonathan Campos wrote: No worries. If someone wants to handle this that is fine. Spoon is planning on taking care of that for the community. I try to repeat: "I (someone else too) can draft a design for a button with templates of the company printing the buttons." "If som

Re: [OT] 360 Flex Denver 2012 - Apache Flex Discovery Room

On Wed, Mar 14, 2012 at 10:40 PM, Martin Heidegger wrote: > I was asking about an organizer/etc. that would order (and take) the pins > for 360flex. No worries. If someone wants to handle this that is fine. Spoon is planning on taking care of that for the community. -- Jonathan Campos

Re: [OT] 360 Flex Denver 2012 - Apache Flex Discovery Room

Lol, unfortunately I will not join the 360 flex, I do have printing companies in japan i could contact. I was asking about an organizer/etc. that would order (and take) the pins for 360flex. yours Martin.

Re: [OT] 360 Flex Denver 2012 - Apache Flex Discovery Room

Would this work? http://www.vistaprint.com/name-tag-stickers.aspx?txi=212&xnid=VisitorHomePage212_202_131&xnav=TeaserItem If this is what you had in mind, I can whip something out with photoshop using the template they provided. Thanks, Om On Wed, Mar 14, 2012 at 7:58 PM, Martin Heidegger wrote:

Re: [OT] 360 Flex Denver 2012 - Apache Flex Discovery Room

On Wed, Mar 14, 2012 at 7:04 PM, Alex Harui wrote: > I'm afraid to ask but can anyone offer up a design? Maybe the current logo > with the word "Committer" underneath? > We can see what garth comes up with -- Jonathan Campos

Re: [OT] 360 Flex Denver 2012 - Apache Flex Discovery Room

On 15/03/2012 08:05, Alex Harui wrote: I was about to ask Wilker about a "Meet the Apache Flex Team" time slot. I think there used to be a "Meet the Flex Team" at past conferences, but I didn't see it on this year's schedule. Can you look into that as well? Also, I've been thinking about button

[RT] Repositories & Artifacts

Hello List, Today I am working on Gradle(Fx) & Maven integration for a test project of mine. It is my first trip in these fields so I might tell you things you already know. However: I think It is important to gain a little overview: A "repository" refers to a online storage (url) of released

Re: [OT] 360 Flex Denver 2012 - Apache Flex Discovery Room

How about the logo and the phrase: "I should be committed" :-) On 3/14/12 6:04 PM, Alex Harui wrote: On 3/14/12 4:45 PM, "Jonathan Campos" wrote: Just kidding but buttons are a great idea. I'm afraid to ask but can anyone offer up a design? Maybe the current logo with the word "Committer

Re: [OT] 360 Flex Denver 2012 - Apache Flex Discovery Room

On 3/14/12 4:45 PM, "Jonathan Campos" wrote: > Just kidding but buttons are a great idea. I'm afraid to ask but can anyone offer up a design? Maybe the current logo with the word "Committer" underneath? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui

Re: [OT] 360 Flex Denver 2012 - Apache Flex Discovery Room

> > Also, I've been thinking about buttons or ribbons for Apache Flex > committers. Thoughts on that? > Maybe a sign that says "buy me a drink and ill can commit your code. Just kidding but buttons are a great idea. > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com

Re: Apache Flex namespace and build script changes

Hi, > Unfortunately we haven't donated the asdoc directory yet That's OK I can use the directory from the OS Adobe SDK. Thanks for the help. I've managed to generate a "fat" rb swc. However the help still doesn't show in FB. Unless I doing do something wrong (which is quite possible) there must

Re: [OT] 360 Flex Denver 2012 - Apache Flex Discovery Room

On 3/14/12 3:58 PM, "j...@realeyes.com" wrote: > > 3. Are there any ideas you might have on how to make the Apache Flex > Discovery Room a success? I was about to ask Wilker about a "Meet the Apache Flex Team" time slot. I think there used to be a "Meet the Flex Team" at past conferences, bu

[OT] 360 Flex Denver 2012 - Apache Flex Discovery Room

The Spoon team has been working with John Wilker to get an Apache Flex Discovery Room set up at 360 Flex. John has been kind enough to offer us a room to use during the conference. That being said, I'm going to double-post to this ML what I had posted to the Spoon Google Group this afternoon.

RE: Flex and names spaces in MXML

What I meant was that if you write without declaring what s is (with xmlns:s="..." on that tag or on an enclosing tag) then you don't have valid XML. - Gordon -Original Message- From: David Francis Buhler [mailto:davidbuh...@gmail.com] Sent: Wednesday, March 14, 2012 1:55 PM To: flex-

Re: Flex and names spaces in MXML

On 12-03-14 1:54 PM, "David Francis Buhler" wrote: >Omitting the xmlns attributes in MXML would make MXML valid XML, it >just wouldn't prevent namespace collisions (because there is no >namespace prefix). Correct. XML NameSpaces are perhaps one of the most misunderstood mechanisms on the plane

Re: Flex and names spaces in MXML

Omitting the xmlns attributes in MXML would make MXML valid XML, it just wouldn't prevent namespace collisions (because there is no namespace prefix). On Wed, Mar 14, 2012 at 4:47 PM, Justin Mclean wrote: > Hi, > >> Omitting the xmlns attributes in MXML would make MXML not be valid XML. > > That'

Re: Apache Flex namespace and build script changes

Hi, > I'm in agreement with Jonathan here, using just Apache with no component set > name will give us problems further down the line if we dev a new set of > comps. So we could use 'a' + 'the first letter of the marketing name', then, > tag the full name on the end of the URL. We could end up

Re: Flex and names spaces in MXML

Hi, > Omitting the xmlns attributes in MXML would make MXML not be valid XML. That's probably an issue. Does anything currently require them to be 100% valid XML with namespaces (compared to well formed XML missing namespaces)? Thanks, Justin

Re: Flex and names spaces in MXML

You still need a default namespace attribute at the top of the mxml document. This allows you to use your components without having to use a namespace prefix. Thanks, Om On Wed, Mar 14, 2012 at 1:24 PM, Left Right wrote: > Hehe, found it :) > > > http://web.archive.org/web/20090106154553/http:

Re: Flex and names spaces in MXML

On Wed, Mar 14, 2012 at 3:24 PM, Left Right wrote: > Hehe, found it :) > > > http://web.archive.org/web/20090106154553/http://opensource.adobe.com./wiki/display/flexsdk/MXML+2009 > > Got to love this site some times. > > Best. > > Oleg > I don't think Gordon would disagree with you. I think he w

Re: Flex and names spaces in MXML

Sorry? Why? I think I can find some examples of Flex 4 beta code, where no namespaces were used... It's from the time when Fx prefix was debated, there were few builds that allowed MXML code w/o any namespaces, like click me etc. Best. Oleg

Re: Apache Flex namespace and build script changes

I'm in agreement with Jonathan here, using just Apache with no component set name will give us problems further down the line if we dev a new set of comps. So we could use 'a' + 'the first letter of the marketing name', then, tag the full name on the end of the URL. Tink Jonathan Campos wro

RE: Unit tests

>Yeah maybe. Are you committing to doing documentation and support? Because >if I do get the steps out there sooner, I don't want to be distracted by >answering questions. Yes, that was my plan. I would also work on the integration within the FlexUnit build and test process so we could have a

Re: Apache Flex namespace and build script changes

Unfortunately we haven't donated the asdoc directory yet but I just looked in the mpl kit which I downloaded awhile ago from the Adobe site and the asdoc directory appears to be in there. If you take a look at the build.xml file in the asdoc directory you will find all the path info. I just updat

Re: Unit tests

On 3/13/12 7:10 PM, "Michael A. Labriola" wrote: > Just thinking it would give people a way to start writing tests in this > supported way so that we are getting coverage on new code. I might put this on > my plate. Yeah maybe. Are you committing to doing documentation and support? Because i

Re: Apache Flex namespace and build script changes

My inclination would have been "asf" rather than "a" but I am sure many others have opinions. Was thinking about "asf" or "af" myself. FlexBuilder uses fat swcs which include the Asdocs for that component. I just realized yesterday that this is something I/we will have to deal with once we

RE: Flex and names spaces in MXML

Omitting the xmlns attributes in MXML would make MXML not be valid XML. - Gordon Smith, Adobe -Original Message- From: Justin Mclean [mailto:jus...@classsoftware.com] Sent: Wednesday, March 14, 2012 12:44 AM To: flex-dev@incubator.apache.org Subject: Flex and names spaces in MXML Hi,

Re: Apache Flex Namespace URI

On 3/14/2012 12:36 PM, Omar Gonzalez wrote: On Wednesday, March 14, 2012, Jeffry Houser > wrote: > On 3/14/2012 5:39 AM, Justin Mclean wrote: >> >> Hi, >> >>> I don't know about Flex but in many cases changing namespace URIs is >>> problematic >> >> They have no

Re: Apache Flex Namespace URI

On Wednesday, March 14, 2012, Jeffry Houser wrote: > On 3/14/2012 5:39 AM, Justin Mclean wrote: >> >> Hi, >> >>> I don't know about Flex but in many cases changing namespace URIs is >>> problematic >> >> They have no effect on ActionScript code (ie 99% of the SDK). It would effect MXML code > >

Re: Apache Flex namespace and build script changes

Hi, > My inclination would have been "asf" rather than "a" but I am sure many > others have opinions. As I'm sure you know what you specify as a namespace prefix is totally up to each component/application. I could for example do this: ... It's more the name space URI that's th

Re: Apache Flex namespace and build script changes

On Wed, Mar 14, 2012 at 9:26 AM, Justin Mclean wrote: > > My vote is to keep the spark ns in the 4.x branch and then have a new > > namespace when we decide to create a new set of components. > 100% agree with that. Again not suggestion we change existing name space > just that we add one or two.

Re: Apache Flex namespace and build script changes

Hi, > My vote is to keep the spark ns in the 4.x branch and then have a new > namespace when we decide to create a new set of components. 100% agree with that. Again not suggestion we change existing name space just that we add one or two. > I do agree with Daniel in that we don't use "apache" o

Re: Apache Flex namespace and build script changes

On 3/14/12 2 :25AM, "Justin Mclean" wrote: > >I made a couple of decisions in doing this that will probably generate >some discussion. The major one being the Apache Flex namespace. > >The flex-config.xml file has a new namespace added for Apache Flex: > >http://www.apache.org/flex >a

Re: Apache Flex namespace and build script changes

On Wed, Mar 14, 2012 at 2:40 AM, Justin Mclean wrote: > Forgot to say there is an one advantage in having a different name space > for new stuff in that it tell you straight away that you need to use the > Apache Flex SDK not the Adobe 4.6 SDK. My vote is to keep the spark ns in the 4.x branch a

Re: Apache Flex Namespace URI

On Wed, Mar 14, 2012 at 8:39 AM, Jeffry Houser wrote: > It doesn't matter if it's a valid URL. The current namespace URL aren't. > In my experience most namespace URLs aren't. None may be valid now, but in the future we may find the need to link to a document or scheme. I would prefer that fr

Re: Apache Flex Namespace URI

Hi, > It doesn't matter if it's a valid URL. The current namespace URL aren't. In > my experience most namespace URLs aren't. Sure they don't have to be and it's not essential in any way. Just think it would be nice if new name spaces were valid URLs then each application would contain a (val

Re: Apache Flex Namespace URI

On 3/14/2012 8:32 AM, Bertrand Delacretaz wrote: On Wed, Mar 14, 2012 at 1:27 PM, Jeffry Houser wrote: ... I'm all for following the 'Adobe" convention and using something like this: http://www.apache.org/flex/mxml ... Which will never be a valid URL, as Apache Flex won't own that URL space.

Re: Apache Flex Namespace URI

On Wed, Mar 14, 2012 at 1:27 PM, Jeffry Houser wrote: > ... I'm all for following the 'Adobe" convention and using something like > this: > > http://www.apache.org/flex/mxml >... Which will never be a valid URL, as Apache Flex won't own that URL space. Don't you think http://flex.apache.org/ns

Re: Flex and names spaces in MXML

Hi, > It doesn't really work that way. I'm not saying have no namespaces but just define the likely ones by default. You would still have to specify or to indicate which list component you want to use. And of course you still could define your own name spaces. > So, if this problem was to b

Re: Apache Flex Namespace URI

On 3/14/2012 5:39 AM, Justin Mclean wrote: Hi, I don't know about Flex but in many cases changing namespace URIs is problematic They have no effect on ActionScript code (ie 99% of the SDK). It would effect MXML code Which is 99% of the code people write. Changing namespaces will cause mor

Re: Flex and names spaces in MXML

It doesn't really work that way. Especially not since Flex 4. There was an attempt at having no namespace at all and to assume mx namespace to be the default. But since in Flex 4 there are a lot of components in the SDK that come in two flowers, but with same names, but not only that, the code gene

Re: Apache Flex Namespace URI

Yeah course. I thought Justin was implying they should be working URLs, which would be nice, but they are not. Tink Omar Gonzalez wrote: >On Wednesday, March 14, 2012, Tink wrote: >> We need to support separate names spaces for spark, mx and fx though. >> >> Tink >> >> > >org.apache.flex.spar

Re: Apache Flex Namespace URI

Hi, > We need to support separate names spaces for spark, mx and fx though. I'm not proposing we change the existing name spaces. Do you mean packages in new names spaces? Thanks, Justin

Re: Apache Flex Namespace URI

On Wednesday, March 14, 2012, Tink wrote: > We need to support separate names spaces for spark, mx and fx though. > > Tink > > org.apache.flex.spark... org.apache.flex.mx... org.apache.flex.fx... That doesn't work? -omar

Re: Apache Flex Namespace URI

We need to support separate names spaces for spark, mx and fx though. Tink Justin Mclean wrote: >Hi, > >> I don't know about Flex but in many cases changing namespace URIs is >> problematic >They have no effect on ActionScript code (ie 99% of the SDK). It would effect >MXML code (but only fi

Re: Apache Flex Namespace URI

On Wed, Mar 14, 2012 at 10:39 AM, Justin Mclean wrote: > ...It would be easy enough to have an incubating URI and another URI when we > graduate. > They could even point to the same manifest file (basically a list of classes > for that namespace) ah ok, cool then. -Bertrand

Re: Apache Flex Namespace URI

Hi, > I don't know about Flex but in many cases changing namespace URIs is > problematic They have no effect on ActionScript code (ie 99% of the SDK). It would effect MXML code (but only files using the new name space) if a URI was changed. As far as I'm aware anyway there may be a something I

Re: Haxe and Flex

I tried once to use some spark components with very reduced functionality for the purpose of using GFX - that's why I mentioned it. I *hope* that there may be a way do build a PoC using some Spark interfaces masking alternative smaller implementations. However, I fell victim to Ubuntu update %) an

Re: Haxe and Flex

Would seriously love to get started with porting Flex onto Haxe. That is something I prize most of all the changes. Flex was known for being the best single RIA tool in the market for a long time. Now over the past months it is losing its glitter. Perhaps porting it to Haxe and making it truly cro

Re: Apache Flex Namespace URI

On Wed, Mar 14, 2012 at 10:18 AM, Justin Mclean wrote: > ...Rather than using "http://www.apache.org/flex"; should we use > "http://incubator.apache.org/flex/"; > as the namespace URI and change to "http://flex.apache.org";  (which I assume > would be the correct URL) > when we graduate?  Having

Apache Flex Namespace URI

Hi, Rather than using "http://www.apache.org/flex"; should we use "http://incubator.apache.org/flex/"; as the namespace URI and change to "http://flex.apache.org"; (which I assume would be the correct URL) when we graduate? Having a URI that maps to a valid URL (and not the manifest file) is

Flex and names spaces in MXML

Hi, I think that you can define public namespaces in actionscript like so: public namespace fx = "http://ns.adobe.com/mxml/2009";; public namespace s = "library://ns.adobe.com/flex/spark"; public namespace mx = "library://ns.adobe.com/flex/mx"; Is there any way we can define the common namespaces

Re: Apache Flex namespace and build script changes

Hi, >> If someone wants to add an "mx-ish" component, should that go in the >> mx namespace or the apache namespace? Forgot to say there is an one advantage in having a different name space for new stuff in that it tell you straight away that you need to use the Apache Flex SDK not the Adobe 4.6

Re: Apache Flex namespace and build script changes

Hi, > Does adding a new apache component namespace paint us into a corner in the > future as opposed to using something more abstract (halo, spark, etc.)? I don't think so we can change it at any time and we're a while away from the first non parity release. I thought I just go ahead and do it to

Re: Apache Flex namespace and build script changes

> > > I made a couple of decisions in doing this that will probably generate > some discussion. The major one being the Apache Flex namespace. > > The flex-config.xml file has a new namespace added for Apache Flex: > >http://www.apache.org/flex >apache-manifest.xml > > > This means you w