Re: [PR] FLEX-35434 Remove Google Analytics from the Flex Website [flex-site]

niallkp commented on PR #2: URL: https://github.com/apache/flex-site/pull/2#issuecomment-2637443062 Thank you @joshtynjala -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment.

Re: [PR] FLEX-35434 Remove Google Analytics from the Flex Website [flex-site]

joshtynjala merged PR #2: URL: https://github.com/apache/flex-site/pull/2 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@flex.apache.or

[PR] FLEX-35434 Remove Google Analytics from the Flex Website [flex-site]

niallkp opened a new pull request, #2: URL: https://github.com/apache/flex-site/pull/2 See https://issues.apache.org/jira/browse/FLEX-35434 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the spe

Re: Flex Website -- next steps

Happy new year! Please start a new Jira ticket aimed at Infra if there are steps you need help with. Andrew

Re: Flex Website -- next steps

Sorry -- I did miss this thread. Gmail decided to block it (grr!). Website hasn't been cut over yet, so no changes to the existing processes. We created the repository, but I haven't moved all the files in yet. I have to build a new script to move our docs over to the new website, which is taking

Re: Flex Website -- next steps

Jira has been raised: https://issues.apache.org/jira/browse/INFRA-21142 śr., 25 lis 2020 o 11:29 Piotr Zarzycki napisał(a): > Hi Guys, > > I'm going to raise an issue in Infra. Sorry for the delay. > > Thanks, > Piotr > > wt., 17 lis 2020 o 14:29 Carlos Rovira > napisał(a): > >> I think he was

Re: Flex Website -- next steps

Hi Guys, I'm going to raise an issue in Infra. Sorry for the delay. Thanks, Piotr wt., 17 lis 2020 o 14:29 Carlos Rovira napisał(a): > I think he was in charge of doing changes so he probably can know more > about all of that. > > El mar., 17 nov. 2020 a las 11:19, Piotr Zarzycki (< > piotrzar

Re: Flex Website -- next steps

I think he was in charge of doing changes so he probably can know more about all of that. El mar., 17 nov. 2020 a las 11:19, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > How this is connected with current website ? Is this doesn't work cause > APache changed something ? > > wt., 17 l

Re: Flex Website -- next steps

How this is connected with current website ? Is this doesn't work cause APache changed something ? wt., 17 lis 2020 o 11:15 Carlos Rovira napisał(a): > Hi Piotr, > > I think Nick probably is very busy and missing these emails, maybe you > could contact him directly to his inbox to know more abou

Re: Flex Website -- next steps

Hi Piotr, I think Nick probably is very busy and missing these emails, maybe you could contact him directly to his inbox to know more about his plans on reworking the website. Thanks El mar., 17 nov. 2020 a las 10:10, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > Hi Alex, > > Tha

Re: Flex Website -- next steps

Hi Alex, Thanks for letting me know, but this is not related to the current problem. I'm going to raise jire in INFRA. Thanks, Piotr pt., 13 lis 2020 o 17:31 Alex Harui napisał(a): > I have not paid attention to how publishing site files has changed (if at > all), but also consider this threa

Re: Flex Website -- next steps

I have not paid attention to how publishing site files has changed (if at all), but also consider this thread: https://lists.apache.org/thread.html/rd574c6d14e3174d237008f04ac27b54513ca6ec9fcb012dc7801978c%40%3Cusers.flex.apache.org%3E -Alex On 11/13/20, 2:57 AM, "Piotr Zarzycki" wrote: I

Re: Flex Website -- next steps

If no one knows. I will contact infra on Monday/Tuesday pt., 13 lis 2020 o 11:43 Piotr Zarzycki napisał(a): > Hi Guys, > > Does that mean that our website won't work anymore ? If I push something > new it won't work ? Can someone shed some light on it ? > > I have pushed MD5 update for playergl

Re: Flex Website -- next steps

Hi Guys, Does that mean that our website won't work anymore ? If I push something new it won't work ? Can someone shed some light on it ? I have pushed MD5 update for playerglobal.swc which should help get up installer on feet but I don't see changes yet. Thanks, Piotr niedz., 20 wrz 2020 o 12

Re: Flex Website -- next steps

Great Nicholas thanks! El dom., 20 sept. 2020 a las 0:41, Nicholas Kwiatkowski (< nicholaskwiatkow...@gmail.com>) escribió: > Since I haven't seen any -1's or other negative comments, I'll get working > down this path. > > -Nick > > On Mon, Sep 14, 2020 at 3:52 AM Olaf Krueger wrote: > > > +1 Th

Re: Flex Website -- next steps

Since I haven't seen any -1's or other negative comments, I'll get working down this path. -Nick On Mon, Sep 14, 2020 at 3:52 AM Olaf Krueger wrote: > +1 Thank you for working on this!! > > > > -- > Sent from: http://apache-flex-development.247.n4.nabble.com/ >

Re: Flex Website -- next steps

+1 Thank you for working on this!! -- Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: Flex Website -- next steps

+1 with that. We can familiarize how do things in Pelican pon., 14 wrz 2020 o 09:00 Carlos Rovira napisał(a): > Hi Nick, > > +1 > > I don't know so much about Pelican, but sure will be the way to go since it > is the official. > For me using just GIT would be a great step forward since it was on

Re: Flex Website -- next steps

Hi Nick, +1 I don't know so much about Pelican, but sure will be the way to go since it is the official. For me using just GIT would be a great step forward since it was one of the things that stopped me in the past (SVN). Also, in Royale website repos (site and docs) we have a branch that is pub

Flex Website -- next steps

Looking for some opinions on moving forward with migrating the website off the old "Apache CMS" and onto something a bit more modern. For those who haven't dove into it -- Apache required the use of the "Apache CMS" which was their platform for allowing projects to host websites on the Apache serv

Re: the Flex website

pages for us :) > > -Nick > > On Thu, Aug 27, 2020 at 10:08 AM Carlos Rovira > wrote: > > > Hi Nicholas, > > > > In another thread we talked about adding a banner flex website to make > > Apache Royale be known for flex users. > > Could you please add t

Re: the Flex website

the other options. But for now, I got the old CMS to push out the new pages for us :) -Nick On Thu, Aug 27, 2020 at 10:08 AM Carlos Rovira wrote: > Hi Nicholas, > > In another thread we talked about adding a banner flex website to make > Apache Royale be known for flex users. >

Re: the Flex website

Hi Erik, As a long time Flex/Flash advocate I must say that runtime fate is set for a long time, so in that front we can't do much more and go with the flow like it happened with VHS/Beta, PC/Amiga, and many more... BUT, I think we can preserve what for me is of huge value: the Flex programming m

Re: the Flex website

Hey all: If you are a Flex devotee, like me, a longtime admirer of the beauty in Flex that introduced a declarative + procedural model that preceded Microsoft's C sharp and WPF models that essentially stole the idea from Flex for a structural MVC where the view and controller were represented b

Re: the Flex website

Yeah, Flex still is with us, and will be as long as AIR (at least) is here!! So don't worry more about Flex! :) El jue., 10 sept. 2020 a las 13:38, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > Leo, > > No one said it is going to happen. > > Thanks, > Piotr > > czw., 10 wrz 2020 o 13

Re: the Flex website

Leo, No one said it is going to happen. Thanks, Piotr czw., 10 wrz 2020 o 13:30 leokan23 napisał(a): > Sad to see Flex getting ready to be moved to the darkness of the attic :/ > We > still have a couple of million users, using our Flex mobile apps. > > > > -- > Sent from: http://apache-flex-d

Re: the Flex website

Sad to see Flex getting ready to be moved to the darkness of the attic :/ We still have a couple of million users, using our Flex mobile apps. -- Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: the Flex website

as!, please let us know when you add the Royale warning banner > to Flex website so we can see how it looks! :) > > >> El vie., 4 sept. 2020 a las 22:48, Olaf Krueger () >> escribió: >> >> This is, what Apache says: >> >> "When should a project mo

Re: the Flex website

to Attic could happen the day AIR is retired or unsupported, but since we have still official (commercial) support, all is ok. Thanks Nicholas!, please let us know when you add the Royale warning banner to Flex website so we can see how it looks! :) El vie., 4 sept. 2020 a las 22:48, Olaf

Re: the Flex website

This is, what Apache says: "When should a project move to the Attic? Projects whose PMC are unable to muster 3 votes for a release, who have no active committers or are unable to fulfill their reporting duties to the board are all good candidates for the Attic." [1] Olaf [1]https://attic.apache.

Re: the Flex website

k > > > On Thu, Aug 27, 2020 at 10:08 AM Carlos Rovira > wrote: > > > Hi Nicholas, > > > > In another thread we talked about adding a banner flex website to make > > Apache Royale be known for flex users. > > Could you please add that banner? I was unable

Re: the Flex website

k On Thu, Aug 27, 2020 at 10:08 AM Carlos Rovira wrote: > Hi Nicholas, > > In another thread we talked about adding a banner flex website to make > Apache Royale be known for flex users. > Could you please add that banner? I was unable to do it. Copy here what we > talked in th

Re: the Flex website

Hi Nicholas, In another thread we talked about adding a banner flex website to make Apache Royale be known for flex users. Could you please add that banner? I was unable to do it. Copy here what we talked in the other thread: "I think just a visible section (maybe before the main menu or

Re: the Flex website

Good to know. As far as I know, any of the static site generators that support MarkDown also support traditional HTML, so migrating should not require a general rewrite. Andrew On Wed, Aug 26, 2020 at 9:18 AM Nicholas Kwiatkowski < nicholaskwiatkow...@gmail.com> wrote: > Hey there -- checking i

Re: the Flex website

Hey there -- checking in (this thread ended up in my spam blocker somehow). We do still use the CMS, but we didn't use a ton of features in it. We mostly used it to glue on a header and footer to the straight HTML pages. It looks like the CMSs that were linked in the initial post are mostly markd

Re: the Flex website

The migration from the CMS to any of the likely static-site generators is more like a copy and paste than a rewrite, if the site uses HTML or markdown. a On Tue, Aug 18, 2020 at 2:34 PM Carlos Rovira wrote: > Hi, > > I think Tom's idea of dump html is the best. I tried recently to add a > simpl

Re: the Flex website

Hi, I think Tom's idea of dump html is the best. I tried recently to add a simple banner on the main home page and must abandon since it was difficult and use SVN. just an html dump where we can easily change a part of html would be enough for this migration and maintenance El mar., 18 ago. 202

Re: the Flex website

On 18/08/2020 07:45, Olaf Krueger wrote: I took a look into your migration guide and it sounds like that we have to rewrite the entire page by using other technologies, e.g. one of the static site generators. Is that right? Surely there has to be a way to just dump raw HTML in a folder and have

Re: the Flex website

Hi Andrew, not sure, but it looks like we're currently using the Apache CMS. This is from the Flex Wiki [1]: "It is currently running on the Apache CMS, which is loosely built on a combination of an mdtext compiler and Svnpubsub." IIRIC, Nicholas Kwiatkowski built the page originally. I took a

Re: the Flex website

Hi Andrew I'm not working with it On Mon, 17 Aug 2020 at 06:16, Andrew Wetmore wrote: > Hi: > > I wrote a couple of weeks ago about the Flex project website, but have not > seen a response. Whom should I contact directly? I am trying to see whether > your project still uses the Apache CMS and, i

Re: the Flex website

Hi: I wrote a couple of weeks ago about the Flex project website, but have not seen a response. Whom should I contact directly? I am trying to see whether your project still uses the Apache CMS and, if so, what our plans are to migrate off it. Thanks in advance for your help. Andrew On Tue, Aug

the Flex website

Hi: I am part of the Infrastructure team, and am writing to ask whether your project is still using the Apache CMS for your project website. As you know, the CMS is reaching end-of-life, and we need projects to move their websites onto a different option within the next few weeks. There are sever

Re: Apache Flex website reviewed!

apache.org website. It > generally > has positive comments. > > > https://communityovercode.com/2016/02/what-is-apache-flex-website-branding-review/ > > (Nice job Nick!) > > Thanks, > Om >

Re: Apache Flex website reviewed!

ly >has positive comments. > >https://communityovercode.com/2016/02/what-is-apache-flex-website-branding >-review/ > >(Nice job Nick!) > >Thanks, >Om

Re: Apache Flex website reviewed!

e.org website. It > >generally > >has positive comments. > > > > > https://communityovercode.com/2016/02/what-is-apache-flex-website-branding > >-review/ > > > >(Nice job Nick!) > > Interesting. Didn't the author fail to conform to branding requirements > for this post? ;-) > > -Alex > >

Re: Apache Flex website reviewed!

On 3/3/16, 3:26 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" wrote: >Someone did a branding review of our flex.apache.org website. It >generally >has positive comments. > >https://communityovercode.com/2016/02/what-is-apache-flex-website-branding &g

Apache Flex website reviewed!

Someone did a branding review of our flex.apache.org website. It generally has positive comments. https://communityovercode.com/2016/02/what-is-apache-flex-website-branding-review/ (Nice job Nick!) Thanks, Om

Re: Apache Flex Website thought

is good starting point for FlexJS. We could experiment a > lot > > on such simple application. > > > > Piotr > > > > > > > > > > ----- > > Apache Flex PMC > > piotrzarzyck...@gmail.com > > -- > > View this message in context: > > > http://apache-flex-development.247.n4.nabble.com/Apache-Flex-Website-thought-tp46946p47022.html > > Sent from the Apache Flex Development mailing list archive at Nabble.com. > > >

Re: Apache Flex Website thought

sophisticated as an application, > but I think it is good starting point for FlexJS. We could experiment a lot > on such simple application. > > Piotr > > > > > - > Apache Flex PMC > piotrzarzyck...@gmail.com > -- > View this message in context: >

[FlexJS] Responsive UI (was Re: Apache Flex Website thought)

Forgot to respond to this. This deserves its own thread. I’m open to ideas as to what Responsive UI means in Flex. It isn’t clear how much we are going to rely on CSS and the browser for layout (I definitely hope to rely on CSS and the browser for lots of visuals). I would like FlexJS to suppor

Re: Apache Flex Website thought

ext: http://apache-flex-development.247.n4.nabble.com/Apache-Flex-Website-thought-tp46946p47022.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: Apache Flex Website thought

birth! [1]https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=27837830 -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Apache-Flex-Website-thought-tp46946p47018.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: Apache Flex Website thought

, 'Desktop & Mobile Apps' on front page and 'About >>>> Flex->Features' link to same page about-features.html >>>> <http://flex.apache.org/about-features.html> >>>> - 'Flex Showcase' and 'About Flex->Flex Showcase' link to same page >>>> community-showcase.html >>> <http://flex.apache.org/community-showcase.html> >>>> At least these two have same name ;) >>>> >>>> * When I want to see showcase of something, I don't want first thing >>> to >>> see >>>> 'How to submit your application?'. BTW 'Apps List' on this page is >>> ideal >>>> candidate to implement in carousel/slider. >>>> >>>> >>>> >>>> >>>> -- >>>> View this message in context: >>>> >>> >>> http://apache-flex-development.247.n4.nabble.com/Apache-Flex-Website- >>> thought-tp46946p46988.html >>>> Sent from the Apache Flex Development mailing list archive at >>> Nabble.com. >>>> >>> >

Re: Apache Flex Website thought

atures.html > >> > <http://flex.apache.org/about-features.html> > >> > - 'Flex Showcase' and 'About Flex->Flex Showcase' link to same page > >> > community-showcase.html > >><http://flex.apache.org/community-showcase.html> > >> > At least these two have same name ;) > >> > > >> > * When I want to see showcase of something, I don't want first thing > >>to > >> see > >> > 'How to submit your application?'. BTW 'Apps List' on this page is > >>ideal > >> > candidate to implement in carousel/slider. > >> > > >> > > >> > > >> > > >> > -- > >> > View this message in context: > >> > > >> > >> > http://apache-flex-development.247.n4.nabble.com/Apache-Flex-Website- > >>thought-tp46946p46988.html > >> > Sent from the Apache Flex Development mailing list archive at > >>Nabble.com. > >> > > >> > >

Re: Apache Flex Website thought

On Wed, May 27, 2015 at 3:52 PM, Michael Schmalle wrote: > > BTW, Did you mean Joseph, not Josh? The one with the videos? > > Yes, sorry about that. My eyes wandered to something else and I didn't type the write name. Sorry Joseph! -Nick

Re: Apache Flex Website thought

; link to same page >> > community-showcase.html >><http://flex.apache.org/community-showcase.html> >> > At least these two have same name ;) >> > >> > * When I want to see showcase of something, I don't want first thing >>to >> see >> > 'How to submit your application?'. BTW 'Apps List' on this page is >>ideal >> > candidate to implement in carousel/slider. >> > >> > >> > >> > >> > -- >> > View this message in context: >> > >> >>http://apache-flex-development.247.n4.nabble.com/Apache-Flex-Website- >>thought-tp46946p46988.html >> > Sent from the Apache Flex Development mailing list archive at >>Nabble.com. >> > >>

RE: Apache Flex Website thought

ginal Message- From: Nicholas Kwiatkowski [mailto:nicho...@spoon.as] Sent: Wednesday, May 27, 2015 1:44 PM To: dev@flex.apache.org Subject: Re: Apache Flex Website thought I'm willing to take on a bit of a refresh of the website after I get a few other commits taken care of. Idealy, I

Re: Apache Flex Website thought

* When I want to see showcase of something, I don't want first thing to > see > > 'How to submit your application?'. BTW 'Apps List' on this page is ideal > > candidate to implement in carousel/slider. > > > > > > > > > > -- > > View this message in context: > > > http://apache-flex-development.247.n4.nabble.com/Apache-Flex-Website-thought-tp46946p46988.html > > Sent from the Apache Flex Development mailing list archive at Nabble.com. > > >

Re: Apache Flex Website thought

e.html <http://flex.apache.org/community-showcase.html> > At least these two have same name ;) > > * When I want to see showcase of something, I don't want first thing to see > 'How to submit your application?'. BTW 'Apps List' on this page is ideal > candi

Re: Apache Flex Website thought

ps List' on this page is ideal candidate to implement in carousel/slider. -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Apache-Flex-Website-thought-tp46946p46988.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: Apache Flex Website thought

Yeah, the Apache Flex website needs a little love for developers who are new to Flex. A couple of thoughts: * The big hero image carousel might be a little too big. I've seen multiple studies that say that carousels aren't very effective. They tend to hide important things because pe

Re: Apache Flex Website thought

On 5/27/15, 9:01 AM, "JosephLabrecque" wrote: > >Great. I'll start developing a small "wish list" of learning and demo >resources that could be produced. > >My wiki username is "josephlabrecque". Thanks. > OK, you should be able to add and edit pages now. -Alex

Re: Apache Flex Website thought

: latest release info, simple 123 get started, download, documentation and tour de flex. -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Apache-Flex-Website-thought-tp46946p46960.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: Apache Flex Website thought

EX/Apache+Flex+Wiki Great. I'll start developing a small "wish list" of learning and demo resources that could be produced. My wiki username is "josephlabrecque". Thanks. -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Apache-Fl

Re: Apache Flex Website thought

On the web site, how about a column that shows simple quick links to the major parts of the site? WIKI, Source code, some "incubating projects" within the Apache Flex project. I know this stuff is in the drop down, but if people see it on the front page, they are more likely to click into and read

Re: Apache Flex Website thought

On 5/27/15, 7:48 AM, "Joseph Labrecque" wrote: > is there a mechanism to keep a list or wiki within Apache? There is a wiki for Apache Flex. It is at [1]. You don’t have to be a committer to contribute content to the wiki. If you are interested in creating wiki content, go to the wiki, crea

RE: Apache Flex Website thought

The problem I see with most of this content is that it is very old - using older versions of Flex and older tools like Flex Builder. This is one of the reasons I started to create some tutorials around Apache Flex and IntelliJ - for there to be some updated content out there using modern IDEs,

Apache Flex Website thought

I know I haven't been around for two years but this will be my case in point. When I left back in 2013 for some other jobs, the 3 articles/images on the site's front page are still the same as they are in 2015. - The Flex in a Week Series

RE: Third-party tools / solutions on Apache Flex website

Thanks !!! On Apr 2, 2014 4:47 AM, "Maurice Amsellem" wrote: > done > > -Message d'origine- > De : Flexicious.com [mailto:flexici...@gmail.com] > Envoyé : mercredi 2 avril 2014 04:49 > À : dev@flex.apache.org > Objet : Re: Third-party tools / solut

Re: Third-party tools / solutions on Apache Flex website

Ok. Thanks Nick. :) - Apache Flex Committer piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Third-party-tools-solutions-on-Apache-Flex-website-tp36116p36631.html Sent from the Apache Flex Development mailing list archive at

Re: Third-party tools / solutions on Apache Flex website

Nick is working on flex unit > tutorials. > > Piotr > > > > > - > Apache Flex Committer > piotrzarzyck...@gmail.com > -- > View this message in context: > http://apache-flex-development.247.n4.nabble.com/Third-party-tools-solutions-on-Apache-Flex

RE: Third-party tools / solutions on Apache Flex website

47.n4.nabble.com/Third-party-tools-solutions-on-Apache-Flex-website-tp36116p36627.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: Third-party tools / solutions on Apache Flex website

m, new way to handle PureMVC notifications, > events and many more... > > Thanks, > Piotr > > > > > - > Apache Flex Committer > piotrzarzyck...@gmail.com > -- > View this message in context: > http://apache-flex-development.247.n4.nabble.com/Third-

Re: Third-party tools / solutions on Apache Flex website

avril 2014 04:49 > À : dev@flex.apache.org > Objet : Re: Third-party tools / solutions on Apache Flex website > > Sure: > Flexicious provides custom components for Flex and Air developers. Our > products include Flexicious Classic, Advanced and Spark, which are > extensions to th

RE: Third-party tools / solutions on Apache Flex website

done -Message d'origine- De : Flexicious.com [mailto:flexici...@gmail.com] Envoyé : mercredi 2 avril 2014 04:49 À : dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website Sure: Flexicious provides custom components for Flex and Air developers. Our pro

Re: Third-party tools / solutions on Apache Flex website

d'origine- > De : Flexicious.com [mailto:flexici...@gmail.com] > Envoyé : mercredi 2 avril 2014 04:49 > À : dev@flex.apache.org > Objet : Re: Third-party tools / solutions on Apache Flex website > > Sure: > Flexicious provides custom components for Flex and Air deve

RE: Third-party tools / solutions on Apache Flex website

tions on Apache Flex website Sure: Flexicious provides custom components for Flex and Air developers. Our products include Flexicious Classic, Advanced and Spark, which are extensions to the Flex SDK DataGrid, AdvancedDataGrid and Spark DataGrid components, as well as Flexicious Ultimate DataGrid

Re: Third-party tools / solutions on Apache Flex website

f text (to be fair with others). > > Maurice > > -Message d'origine- > De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] > Envoyé : mardi 1 avril 2014 23:40 > À : dev@flex.apache.org > Objet : RE: Third-party tools / solutions on Apache Flex website >

RE: Third-party tools / solutions on Apache Flex website

Sorry, rather 2~3 lines of text (to be fair with others). Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : mardi 1 avril 2014 23:40 À : dev@flex.apache.org Objet : RE: Third-party tools / solutions on Apache Flex website IMO, Flexi

RE: Third-party tools / solutions on Apache Flex website

se provide the content you would want to be included (3 ~ 5 lines paragraph) . Maurice -Message d'origine- De : Flexicious.com [mailto:flexici...@gmail.com] Envoyé : mardi 1 avril 2014 23:20 À : dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website H

Re: Third-party tools / solutions on Apache Flex website

: > Thanks Maurice I will do this soon. :) > > Piotr > > > > - > Apache Flex Committer > piotrzarzyck...@gmail.com > -- > View this message in context: > http://apache-flex-development.247.n4.nabble.com/Third-party-tools-solutions-on-Apache-Flex-website-tp36116p36

RE: Third-party tools / solutions on Apache Flex website

Thanks Maurice I will do this soon. :) Piotr - Apache Flex Committer piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Third-party-tools-solutions-on-Apache-Flex-website-tp36116p36578.html Sent from the Apache Flex Development

RE: Third-party tools / solutions on Apache Flex website

Piotr, Please feel free to add the section on Fabrication. Maurice -Message d'origine- De : piotrz [mailto:piotrzarzyck...@gmail.com] Envoyé : mardi 1 avril 2014 22:01 À : dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website Hi Guys! First of

Re: Third-party tools / solutions on Apache Flex website

otr - Apache Flex Committer piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Third-party-tools-solutions-on-Apache-Flex-website-tp36116p36575.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: Third-party tools / solutions on Apache Flex website

+1 Disclaimer -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Tuesday, April 01, 2014 11:12 AM To: dev@flex.apache.org; Franck Wolff Subject: RE: Third-party tools / solutions on Apache Flex website Hey guys, Thanks for getting this done. I'm tempted to add

Re: Third-party tools / solutions on Apache Flex website

ex.apache.org > Subject: RE: Third-party tools / solutions on Apache Flex website > > >Well, you're free to modify the page as you want. > > I have extended the description on Parsley. > > Maurice > > De : Franck Wolff [mailto:frawo...@gmail.com] > Envoyé : mar

RE: Third-party tools / solutions on Apache Flex website

I agree for the disclaimer. -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 1 avril 2014 17:12 À : dev@flex.apache.org; Franck Wolff Objet : RE: Third-party tools / solutions on Apache Flex website Hey guys, Thanks for getting this done. I'm temp

RE: Third-party tools / solutions on Apache Flex website

esday, April 1, 2014 4:59 AM To: Franck Wolff Cc: dev@flex.apache.org Subject: RE: Third-party tools / solutions on Apache Flex website >Well, you're free to modify the page as you want. I have extended the description on Parsley. Maurice De : Franck Wolff [mailto:frawo...@gmail.com] Env

RE: Third-party tools / solutions on Apache Flex website

>Well, you're free to modify the page as you want. I have extended the description on Parsley. Maurice De : Franck Wolff [mailto:frawo...@gmail.com] Envoyé : mardi 1 avril 2014 13:55 À : Maurice Amsellem Cc : dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex

RE: Third-party tools / solutions on Apache Flex website

1 avril 2014 13:55 À : Maurice Amsellem Cc : dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website Thanks Maurice! That was fast ;) Note: the testing section is not complete IMO. it's missing FlexMonkey, HP QTP (QuickTest Professional) [not the same as LoadR

Re: Third-party tools / solutions on Apache Flex website

er description. > > > > Otherwise, great stuff. > > > > Maurice > > > > > > *De :* Franck Wolff [mailto:frawo...@gmail.com] > *Envoyé :* mardi 1 avril 2014 11:41 > *À :* dev@flex.apache.org > *Cc :* Maurice Amsellem > > *Objet :* Re: Third-p

RE: Third-party tools / solutions on Apache Flex website

avril 2014 11:41 À : dev@flex.apache.org Cc : Maurice Amsellem Objet : Re: Third-party tools / solutions on Apache Flex website Done: FLEX-34199<https://issues.apache.org/jira/browse/FLEX-34199>. Franck. 2014-04-01 6:09 GMT+02:00 Alex Harui mailto:aha...@adobe.com>>: For record

Re: Third-party tools / solutions on Apache Flex website

ill format it, review it and get it > published. > > Maurice > > -Message d'origine- > De : Franck Wolff [mailto:frawo...@gmail.com] > Envoyé : lundi 31 mars 2014 16:34 > À : dev@flex.apache.org > Objet : Re: Third-party tools / solutions on Apache Flex website &g

RE: Third-party tools / solutions on Apache Flex website

Objet : Re: Third-party tools / solutions on Apache Flex website The new page is just a modification of an existing Apache Flex page, it follows the look & feel of the website and I believe it could be even published as is (hard to say without knowing which CMS you use). Anyway: can somebody

RE: Third-party tools / solutions on Apache Flex website

Maurice -Message d'origine- De : Franck Wolff [mailto:frawo...@gmail.com] Envoyé : lundi 31 mars 2014 16:34 À : dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website The new page is just a modification of an existing Apache Flex page, it follows the look & fe

Re: Third-party tools / solutions on Apache Flex website

ssage d'origine- >> De : Franck Wolff [mailto:frawo...@gmail.com] >> Envoyé : lundi 31 mars 2014 14:27 >> À : dev@flex.apache.org >> Objet : Re: Third-party tools / solutions on Apache Flex website >> >> Thanks Justin. >> >> I don't thi

Re: Third-party tools / solutions on Apache Flex website

nck Wolff [mailto:frawo...@gmail.com] > Envoyé : lundi 31 mars 2014 14:27 > À : dev@flex.apache.org > Objet : Re: Third-party tools / solutions on Apache Flex website > > Thanks Justin. > > I don't think it should be just a Wiki page. In my mind, it should rather >

RE: Third-party tools / solutions on Apache Flex website

: dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website Thanks Justin. I don't think it should be just a Wiki page. In my mind, it should rather be a regular page of the website, either in the "About Flex" or "Community" section (your call). Can yo

Re: Third-party tools / solutions on Apache Flex website

Thanks Justin. I don't think it should be just a Wiki page. In my mind, it should rather be a regular page of the website, either in the "About Flex" or "Community" section (your call). Can you grant me a (temporary) write access to the website? Where should I put this new page? Franck. 2014-0

Re: Third-party tools / solutions on Apache Flex website

HI, > Any chance to get this page published anytime soon (with Andrew's > modifications applied)? You don't have to be a committer to make wiki edits changes/ just ask for wiki access put the file there yourself may be the quickest way. Thanks, Justin

  1   2   >