Re: the Flex website

[Carlos Rovira]

Just tweeted about this:
https://twitter.com/ApacheFlex/status/1305273320280150020


El dom., 13 sept. 2020 a las 23:58, Nicholas Kwiatkowski (<
nicholaskwiatkow...@gmail.com>) escribió:

> Ok.  I updated the site with a new banner as well as an "Alert box" to let
> people know about the FP decommission and about Apache Royale.  Let me know
> if you think this is enough.
>
> I am still trying to untangle (re-learn) how the old CMS worked so that I
> can port things over to one of 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.
> > 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 after it),
> > of about 300px-400px height with a message like this:
> >
> > *"For those who need a frontend technology that runs in browsers without
> > Adobe Flash Player, *
> > *please check Apache Royale.*
> > *Apache Flex will still be used outside browsers with desktop
> technologies
> > (i.e, Adobe AIR) after December 31th, 2020."*
> >
> > And make the "Apache Royale" text link to the website (
> > https://royale.apache.org).
> > Please correct the spelling to match the right english translation.
> > If possible make the background green or blue and wording white with some
> > sizing so it captures attention."
> >
> > Thanks in advance.
> >
> > Carlos
> >
> >
> >
> > El mié., 26 ago. 2020 a las 14:40, Andrew Wetmore ()
> > escribió:
> >
> > > 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 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
> > > > markdown-based, which we don't use (and it would be a pain to convert
> > > over
> > > > to).
> > > >
> > > > I don't have a ton of time this week -- I'm trying to convert my
> > classes
> > > to
> > > > be online at the last second, again.  If anybody else on the list
> wants
> > > to
> > > > do the research to move it over, I can chime in to help.  I should
> have
> > > > some more time in a few weeks when things settle down.
> > > >
> > > > -Nick
> > > >
> > > > On Wed, Aug 19, 2020 at 9:12 AM Andrew Wetmore 
> > > > wrote:
> > > >
> > > > > 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 <
> > carlosrov...@apache.org
> > > >
> > > > > wrote:
> > > > >
> > > > > > 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. 2020 a las 11:32, Tom Chiverton (<
> > > t...@extravision.com
> > > > >)
> > > > > > escribió:
> > > > > >
> > > > > > > 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
> > > > > > > it served up... the site doesn't change so that would be
> easiest
> > > for
> > > > > us ?
> > > > > > >
> > > > > > > Tom
> > > > > > >
> > > > > > >
> > > > > > >
> > > >
> __
> > > > > > > This email has been scanned by the Symantec Email
> Security.cloud
> > > > > service.
> > > > > > > For more information please visit http://www.symanteccloud.com
> > > > > > >
> > > >
> __
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Carlos Rovira
> > > > > > http://about.me/carlosrovira
> > > > > >
> > > > >
> > > > 

Re: the Flex website

[Nicholas Kwiatkowski]

Ok.  I updated the site with a new banner as well as an "Alert box" to let
people know about the FP decommission and about Apache Royale.  Let me know
if you think this is enough.

I am still trying to untangle (re-learn) how the old CMS worked so that I
can port things over to one of 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.
> 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 after it),
> of about 300px-400px height with a message like this:
>
> *"For those who need a frontend technology that runs in browsers without
> Adobe Flash Player, *
> *please check Apache Royale.*
> *Apache Flex will still be used outside browsers with desktop technologies
> (i.e, Adobe AIR) after December 31th, 2020."*
>
> And make the "Apache Royale" text link to the website (
> https://royale.apache.org).
> Please correct the spelling to match the right english translation.
> If possible make the background green or blue and wording white with some
> sizing so it captures attention."
>
> Thanks in advance.
>
> Carlos
>
>
>
> El mié., 26 ago. 2020 a las 14:40, Andrew Wetmore ()
> escribió:
>
> > 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 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
> > > markdown-based, which we don't use (and it would be a pain to convert
> > over
> > > to).
> > >
> > > I don't have a ton of time this week -- I'm trying to convert my
> classes
> > to
> > > be online at the last second, again.  If anybody else on the list wants
> > to
> > > do the research to move it over, I can chime in to help.  I should have
> > > some more time in a few weeks when things settle down.
> > >
> > > -Nick
> > >
> > > On Wed, Aug 19, 2020 at 9:12 AM Andrew Wetmore 
> > > wrote:
> > >
> > > > 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 <
> carlosrov...@apache.org
> > >
> > > > wrote:
> > > >
> > > > > 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. 2020 a las 11:32, Tom Chiverton (<
> > t...@extravision.com
> > > >)
> > > > > escribió:
> > > > >
> > > > > > 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
> > > > > > it served up... the site doesn't change so that would be easiest
> > for
> > > > us ?
> > > > > >
> > > > > > Tom
> > > > > >
> > > > > >
> > > > > >
> > > __
> > > > > > This email has been scanned by the Symantec Email Security.cloud
> > > > service.
> > > > > > For more information please visit http://www.symanteccloud.com
> > > > > >
> > > __
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Carlos Rovira
> > > > > http://about.me/carlosrovira
> > > > >
> > > >
> > > >
> > > > --
> > > > Andrew Wetmore
> > > >
> > > > http://cottage14.blogspot.com/
> > > >
> > >
> >
> >
> > --
> > Andrew Wetmore
> > Technical Writer-Editor
> > Infra
> > *Apache Software Foundation*
> > andr...@apache.org
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>

Re: the Flex website

[Carlos Rovira]

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 model with AS3/MXML, View States, Binding, AMF (RPC), and much
more... through Apache Royale. For me having that productivity is
priceless.  Also mixing with the good stuff in the modern development world
means to boost what we already had. For example, I think CSS
implementation in browsers is far better than the subset we had in Flash
Player (and Flex), so that joins the Royale programming model through
normal CSS... or through SASS :).

I think Flex/AIR will still be there for as long as people will use it,
maybe unfortunately few people now. For many others it's normal that they
must go with the rest of the world. For many of them, like you, maybe is
late since you'll go React (that's normal since companies tend to go to the
mainstream tech for security), but just say that in 2020, I think Apache
Royale and Jewel set has reach a very good state and it's a pleasure to
work with it, as it was Flex. So maybe giving a try in the current state
would surprise you, and will make your migration easier than going React.

I'll be presenting at ApacheCon at the end of this month (31th) a talk that
showcases the TodoMVC example here [1] and here [2]. Hope that helps others
to notice how far we reach, and that Royale is now a real option for all.

Talks are here [3], and the TodoMVC talk is "Starting from a blank file"

HTH

Carlos

[1] demo: https://royale.apache.org/todomvc-jewel/
[2] code:
https://github.com/apache/royale-asjs/blob/develop/examples/crux/todomvc-jewel-crux/readme.md
[3] https://www.apachecon.com/acah2020/tracks/royale.html


El vie., 11 sept. 2020 a las 4:40, Erik Thomas () escribió:

> 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 by
> the MXML and as3 respectively, I believe there is much life left in Flex.
>
> It is still a very relevant platform for creating single-codebase mobile
> apps for Android and iOS. It produces far smaller executables than Swift
> and most all other competing platforms. The availability of ANEs to access
> native capability provides near parity with native app development, not
> quite, but close enough to get multiplatform support for a single platform.
>
> I've been developing Flex apps since 2007 with the release of Flex 3 by
> Adobe. I was working for Intuit at the time Flex was a huge departure from
> Intuit's C++/MFC centric development platform that was used for QuickBooks
> (I was a QuickBooks engineer prior to accepting a challenge to develop a
> new product using Flex). It was refreshing to start a new project and not
> have to maintain and develop on a 6 million LOC C++ application.
>
> While I was at it I was also one of a team that was evaluating MS WPF so I
> learned that too, and while I still think WPF was amazing, it stole much of
> it's design from Macromedia that designed Flex, and I haven't seen a new
> paradigm to challenge the declarative/procedural design even today, IMHO.
> But the real power is in the runtime. Just like Java practically replaced C
> and C++ based web development because of the amazing advantages of a
> sandboxed runtime environment, the AIR runtime is brilliant, even today. No
> other major platform for mobile (or web, though the flash player is
> definitely dying) can equal the performance of the AIR runtime. One must
> compile to native and that comes with a boatload of problems especially
> multi-platform support. A runtime engine is still brilliant, just as Java
> runtimes still power nearly half of the billions of web apps on the
> internet.
>
> What I don't understand is why Flex doesn't attract more developers, but
> I'm sure it's because universities and colleges, and tech schools don't
> teach it because it's considered fringe. If people really understood what
> it could do we could see third party tools, ANEs, and new innovations that
> pushed it back into the mainstream.
>
> Oh well. Sometimes the best ideas and designs don't achieve mindshare and
> fail for reasons entirely unrelated to capability.
>
> Ancients like me will remember the VHS vs. Betacam wars where the latter
> was 10X better and still failed because of marketing, mindshare, and
> somewhat political reasoning.
>
> My company still has two very successful mobile apps built with Flex/AIR
> and some ANEs by Distriqt (the very best ANE developer on the planet
> without doubt): Linqto and Keiretsu Forum.
>
> Alas, we have even succumbed to pressure to replace these apps with REACT
> Native and will be 

Re: the Flex website

[Erik Thomas]

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 by the MXML and as3 
respectively, I believe there is much life left in Flex.

It is still a very relevant platform for creating single-codebase mobile apps 
for Android and iOS. It produces far smaller executables than Swift and most 
all other competing platforms. The availability of ANEs to access native 
capability provides near parity with native app development, not quite, but 
close enough to get multiplatform support for a single platform.

I've been developing Flex apps since 2007 with the release of Flex 3 by Adobe. 
I was working for Intuit at the time Flex was a huge departure from Intuit's 
C++/MFC centric development platform that was used for QuickBooks (I was a 
QuickBooks engineer prior to accepting a challenge to develop a new product 
using Flex). It was refreshing to start a new project and not have to maintain 
and develop on a 6 million LOC C++ application. 

While I was at it I was also one of a team that was evaluating MS WPF so I 
learned that too, and while I still think WPF was amazing, it stole much of 
it's design from Macromedia that designed Flex, and I haven't seen a new 
paradigm to challenge the declarative/procedural design even today, IMHO. But 
the real power is in the runtime. Just like Java practically replaced C and C++ 
based web development because of the amazing advantages of a sandboxed runtime 
environment, the AIR runtime is brilliant, even today. No other major platform 
for mobile (or web, though the flash player is definitely dying) can equal the 
performance of the AIR runtime. One must compile to native and that comes with 
a boatload of problems especially multi-platform support. A runtime engine is 
still brilliant, just as Java runtimes still power nearly half of the billions 
of web apps on the internet.

What I don't understand is why Flex doesn't attract more developers, but I'm 
sure it's because universities and colleges, and tech schools don't teach it 
because it's considered fringe. If people really understood what it could do we 
could see third party tools, ANEs, and new innovations that pushed it back into 
the mainstream.

Oh well. Sometimes the best ideas and designs don't achieve mindshare and fail 
for reasons entirely unrelated to capability. 

Ancients like me will remember the VHS vs. Betacam wars where the latter was 
10X better and still failed because of marketing, mindshare, and somewhat 
political reasoning.

My company still has two very successful mobile apps built with Flex/AIR and 
some ANEs by Distriqt (the very best ANE developer on the planet without 
doubt): Linqto and Keiretsu Forum. 

Alas, we have even succumbed to pressure to replace these apps with REACT 
Native and will be embarking on this road in the next month. It's a sad day. 
But now that a big company like Adobe has relinquished the reins of both Flex 
(some years ago) and AIR (to Harmann recently), it seems the fate of this 
amazing development platform is destined to the graveyard.

I know there's lots of great innovation with Royale to breathe live back into 
Flex apps, and there are migration options as well. These are great things, but 
in my opinion, unnecessary because the AIR runtime is FAR, FAR better than 
relying on any browser-based rendering engine to render javascript, html, and 
CSS. 

Just sharing my opinion as someone who has made his living with Flex since 
2007, was once a master/guru of MFC/C++ since Windows 1.5, and got my first 
contract in 1983.

Erik Thomas
Chief Architect 
http://linqto.com

Re: the Flex website

[Carlos Rovira]

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: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-development.247.n4.nabble.com/
> >
>
>
> --
>
> Piotr Zarzycki
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Re: the Flex website

[Piotr Zarzycki]

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-development.247.n4.nabble.com/
>


-- 

Piotr Zarzycki

Re: the Flex website

[leokan23]

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

[Stuart Thomas]

AIR is alive and well!!!

Sent from Beyond

> On Sep 5, 2020, at 12:04 AM, Carlos Rovira  wrote:
> 
> Hi,
> 
> I think Flex still has (and will have) its own future. What is going to an
> end is Flash Player Plugin (so Flash on Browsers). We tend to mix things on
> that front. Since Flash in AIR is still on desktop and mobile, Flex still
> has its use, and there are some people still using it.
> I think going 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 Krueger ()
>> escribió:
>> 
>> 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.org/
>> 
>> 
>> 
>> --
>> Sent from: http://apache-flex-development.247.n4.nabble.com/
>> 
> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

Re: the Flex website

[Carlos Rovira]

Hi,

I think Flex still has (and will have) its own future. What is going to an
end is Flash Player Plugin (so Flash on Browsers). We tend to mix things on
that front. Since Flash in AIR is still on desktop and mobile, Flex still
has its use, and there are some people still using it.
I think going 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 Krueger ()
escribió:

> 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.org/
>
>
>
> --
> Sent from: http://apache-flex-development.247.n4.nabble.com/
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Re: the Flex website

[Olaf Krueger]

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.org/



--
Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: the Flex website

[Piotr Zarzycki]

Hi Nick,

As long as Flex is on Desktop and Mobile from my sight would be -1 with
going to Attic with this project.

However we can talk and maybe someone convince me with that.

Thanks,
Piotr

pt., 4 wrz 2020 o 15:59 Nicholas Kwiatkowski 
napisał(a):

> Carlos,
>
> I'll look into it this weekend.
>
> We should also talk about starting the process to attic the Flex project as
> well.  Once Flash is done and gone in a few months, and AIR support is
> solely with a 3rd party, I don't think there is going to be much future for
> this project...
>
> -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 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 after it),
> > of about 300px-400px height with a message like this:
> >
> > *"For those who need a frontend technology that runs in browsers without
> > Adobe Flash Player, *
> > *please check Apache Royale.*
> > *Apache Flex will still be used outside browsers with desktop
> technologies
> > (i.e, Adobe AIR) after December 31th, 2020."*
> >
> > And make the "Apache Royale" text link to the website (
> > https://royale.apache.org).
> > Please correct the spelling to match the right english translation.
> > If possible make the background green or blue and wording white with some
> > sizing so it captures attention."
> >
> > Thanks in advance.
> >
> > Carlos
> >
> >
> >
> > El mié., 26 ago. 2020 a las 14:40, Andrew Wetmore ()
> > escribió:
> >
> > > 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 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
> > > > markdown-based, which we don't use (and it would be a pain to convert
> > > over
> > > > to).
> > > >
> > > > I don't have a ton of time this week -- I'm trying to convert my
> > classes
> > > to
> > > > be online at the last second, again.  If anybody else on the list
> wants
> > > to
> > > > do the research to move it over, I can chime in to help.  I should
> have
> > > > some more time in a few weeks when things settle down.
> > > >
> > > > -Nick
> > > >
> > > > On Wed, Aug 19, 2020 at 9:12 AM Andrew Wetmore 
> > > > wrote:
> > > >
> > > > > 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 <
> > carlosrov...@apache.org
> > > >
> > > > > wrote:
> > > > >
> > > > > > 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. 2020 a las 11:32, Tom Chiverton (<
> > > t...@extravision.com
> > > > >)
> > > > > > escribió:
> > > > > >
> > > > > > > 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
> > > > > > > it served up... the site doesn't change so that would be
> easiest
> > > for
> > > > > us ?
> > > > > > >
> > > > > > > Tom
> > > > > > >
> > > > > > >
> > > > > > >
> > > >
> __
> > > > > > > This email has been scanned by the Symantec Email
> Security.cloud
> > > > > service.
> > > > > > > For more information please visit http://www.symanteccloud.com
> > > > > > >
> > > >
> __
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Carlos Rovira
> > > > > > http://about.me/carlosrovira
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > 

Re: the Flex website

[Nicholas Kwiatkowski]

Carlos,

I'll look into it this weekend.

We should also talk about starting the process to attic the Flex project as
well.  Once Flash is done and gone in a few months, and AIR support is
solely with a 3rd party, I don't think there is going to be much future for
this project...

-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 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 after it),
> of about 300px-400px height with a message like this:
>
> *"For those who need a frontend technology that runs in browsers without
> Adobe Flash Player, *
> *please check Apache Royale.*
> *Apache Flex will still be used outside browsers with desktop technologies
> (i.e, Adobe AIR) after December 31th, 2020."*
>
> And make the "Apache Royale" text link to the website (
> https://royale.apache.org).
> Please correct the spelling to match the right english translation.
> If possible make the background green or blue and wording white with some
> sizing so it captures attention."
>
> Thanks in advance.
>
> Carlos
>
>
>
> El mié., 26 ago. 2020 a las 14:40, Andrew Wetmore ()
> escribió:
>
> > 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 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
> > > markdown-based, which we don't use (and it would be a pain to convert
> > over
> > > to).
> > >
> > > I don't have a ton of time this week -- I'm trying to convert my
> classes
> > to
> > > be online at the last second, again.  If anybody else on the list wants
> > to
> > > do the research to move it over, I can chime in to help.  I should have
> > > some more time in a few weeks when things settle down.
> > >
> > > -Nick
> > >
> > > On Wed, Aug 19, 2020 at 9:12 AM Andrew Wetmore 
> > > wrote:
> > >
> > > > 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 <
> carlosrov...@apache.org
> > >
> > > > wrote:
> > > >
> > > > > 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. 2020 a las 11:32, Tom Chiverton (<
> > t...@extravision.com
> > > >)
> > > > > escribió:
> > > > >
> > > > > > 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
> > > > > > it served up... the site doesn't change so that would be easiest
> > for
> > > > us ?
> > > > > >
> > > > > > Tom
> > > > > >
> > > > > >
> > > > > >
> > > __
> > > > > > This email has been scanned by the Symantec Email Security.cloud
> > > > service.
> > > > > > For more information please visit http://www.symanteccloud.com
> > > > > >
> > > __
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Carlos Rovira
> > > > > http://about.me/carlosrovira
> > > > >
> > > >
> > > >
> > > > --
> > > > Andrew Wetmore
> > > >
> > > > http://cottage14.blogspot.com/
> > > >
> > >
> >
> >
> > --
> > Andrew Wetmore
> > Technical Writer-Editor
> > Infra
> > *Apache Software Foundation*
> > andr...@apache.org
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>

Re: the Flex website

[Carlos Rovira]

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 after it),
of about 300px-400px height with a message like this:

*"For those who need a frontend technology that runs in browsers without
Adobe Flash Player, *
*please check Apache Royale.*
*Apache Flex will still be used outside browsers with desktop technologies
(i.e, Adobe AIR) after December 31th, 2020."*

And make the "Apache Royale" text link to the website (
https://royale.apache.org).
Please correct the spelling to match the right english translation.
If possible make the background green or blue and wording white with some
sizing so it captures attention."

Thanks in advance.

Carlos



El mié., 26 ago. 2020 a las 14:40, Andrew Wetmore ()
escribió:

> 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 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
> > markdown-based, which we don't use (and it would be a pain to convert
> over
> > to).
> >
> > I don't have a ton of time this week -- I'm trying to convert my classes
> to
> > be online at the last second, again.  If anybody else on the list wants
> to
> > do the research to move it over, I can chime in to help.  I should have
> > some more time in a few weeks when things settle down.
> >
> > -Nick
> >
> > On Wed, Aug 19, 2020 at 9:12 AM Andrew Wetmore 
> > wrote:
> >
> > > 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
> > > > 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. 2020 a las 11:32, Tom Chiverton (<
> t...@extravision.com
> > >)
> > > > escribió:
> > > >
> > > > > 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
> > > > > it served up... the site doesn't change so that would be easiest
> for
> > > us ?
> > > > >
> > > > > Tom
> > > > >
> > > > >
> > > > >
> > __
> > > > > This email has been scanned by the Symantec Email Security.cloud
> > > service.
> > > > > For more information please visit http://www.symanteccloud.com
> > > > >
> > __
> > > > >
> > > >
> > > >
> > > > --
> > > > Carlos Rovira
> > > > http://about.me/carlosrovira
> > > >
> > >
> > >
> > > --
> > > Andrew Wetmore
> > >
> > > http://cottage14.blogspot.com/
> > >
> >
>
>
> --
> Andrew Wetmore
> Technical Writer-Editor
> Infra
> *Apache Software Foundation*
> andr...@apache.org
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Re: the Flex website

[Andrew Wetmore]

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 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
> markdown-based, which we don't use (and it would be a pain to convert over
> to).
>
> I don't have a ton of time this week -- I'm trying to convert my classes to
> be online at the last second, again.  If anybody else on the list wants to
> do the research to move it over, I can chime in to help.  I should have
> some more time in a few weeks when things settle down.
>
> -Nick
>
> On Wed, Aug 19, 2020 at 9:12 AM Andrew Wetmore 
> wrote:
>
> > 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
> > > 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. 2020 a las 11:32, Tom Chiverton ( >)
> > > escribió:
> > >
> > > > 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
> > > > it served up... the site doesn't change so that would be easiest for
> > us ?
> > > >
> > > > Tom
> > > >
> > > >
> > > >
> __
> > > > This email has been scanned by the Symantec Email Security.cloud
> > service.
> > > > For more information please visit http://www.symanteccloud.com
> > > >
> __
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
> >
>


-- 
Andrew Wetmore
Technical Writer-Editor
Infra
*Apache Software Foundation*
andr...@apache.org

Re: the Flex website

[Nicholas Kwiatkowski]

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
markdown-based, which we don't use (and it would be a pain to convert over
to).

I don't have a ton of time this week -- I'm trying to convert my classes to
be online at the last second, again.  If anybody else on the list wants to
do the research to move it over, I can chime in to help.  I should have
some more time in a few weeks when things settle down.

-Nick

On Wed, Aug 19, 2020 at 9:12 AM Andrew Wetmore  wrote:

> 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
> > 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. 2020 a las 11:32, Tom Chiverton ()
> > escribió:
> >
> > > 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
> > > it served up... the site doesn't change so that would be easiest for
> us ?
> > >
> > > Tom
> > >
> > >
> > > __
> > > This email has been scanned by the Symantec Email Security.cloud
> service.
> > > For more information please visit http://www.symanteccloud.com
> > > __
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>

Re: the Flex website

[Andrew Wetmore]

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
> 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. 2020 a las 11:32, Tom Chiverton ()
> escribió:
>
> > 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
> > it served up... the site doesn't change so that would be easiest for us ?
> >
> > Tom
> >
> >
> > __
> > This email has been scanned by the Symantec Email Security.cloud service.
> > For more information please visit http://www.symanteccloud.com
> > __
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: the Flex website

[Carlos Rovira]

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. 2020 a las 11:32, Tom Chiverton ()
escribió:

> 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
> it served up... the site doesn't change so that would be easiest for us ?
>
> Tom
>
>
> __
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> __
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Re: the Flex website

[Tom Chiverton]

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 
it served up... the site doesn't change so that would be easiest for us ?


Tom


__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__

Re: the Flex website

[Olaf Krueger]

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 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?

Thanks,
Olaf


[1]
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=30754191



--
Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: the Flex website

[Daniel Swid]

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, if so, what our plans are to
> migrate off it.
>
> Thanks in advance for your help.
>
> Andrew
>
> On Tue, Aug 4, 2020 at 10:54 AM Andrew Wetmore  wrote:
>
> > 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 several alternatives available, including those listed on this
> > page [1] on managing project websites. Infra is assembling a Wiki page
> [2]
> > on migrating a website from the CMS, and is looking forward to helping
> > projects with this transition.
> >
> > Please let me know whether your site is still on the Apache CMS and, if
> > so, who will be the project point-of-contact with Infra for the
> migration.
> >
> > Thank you!
> >
> >
> >
> >
> > [1] https://infra.apache.org/project-site.html
> >
> > [2]
> >
> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
> >
> >
> > --
> > Andrew Wetmore
> > Technical Writer-Editor
> > Infra
> > *Apache Software Foundation*
> > andr...@apache.org
> >
> >
> > <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
> Virus-free.
> > www.avast.com
> > <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> > <#m_2173626166079508585_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >
>
>
> --
> Andrew Wetmore
> Technical Writer-Editor
> Infra
> *Apache Software Foundation*
> andr...@apache.org
>

Re: the Flex website

[Andrew Wetmore]

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 4, 2020 at 10:54 AM Andrew Wetmore  wrote:

> 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 several alternatives available, including those listed on this
> page [1] on managing project websites. Infra is assembling a Wiki page [2]
> on migrating a website from the CMS, and is looking forward to helping
> projects with this transition.
>
> Please let me know whether your site is still on the Apache CMS and, if
> so, who will be the project point-of-contact with Infra for the migration.
>
> Thank you!
>
>
>
>
> [1] https://infra.apache.org/project-site.html
>
> [2]
> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
>
>
> --
> Andrew Wetmore
> Technical Writer-Editor
> Infra
> *Apache Software Foundation*
> andr...@apache.org
>
>
> 
>  Virus-free.
> www.avast.com
> 
> <#m_2173626166079508585_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>


-- 
Andrew Wetmore
Technical Writer-Editor
Infra
*Apache Software Foundation*
andr...@apache.org

Re: Apache Flex website reviewed!

[OmPrakash Muppirala]

Lol.  We should contact him and ask him to fix the attributions ;-)

On Thu, Mar 3, 2016 at 3:40 PM, Alex Harui  wrote:

>
>
> 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
> >-review/
> >
> >(Nice job Nick!)
>
> Interesting.  Didn't the author fail to conform to branding requirements
> for this post? ;-)
>
> -Alex
>
>

Re: Apache Flex Website thought

[OmPrakash Muppirala]

Can someone with time update the website's home page?  I think there are
several new videos created by Joseph that we can use.

Thanks,
Om

On Wed, May 27, 2015 at 9:50 PM, piotrz  wrote:

> Maybe writing whole website at this point in FlexJS will be really hard to
> achieve. But what about split everything into two directions.
> - Modify/write website in an "old" fashion in html
> - Start writing CMS for this website in FlexJS
>
> Many years ago I was working for some company where we wrote website in
> html
> and cms in Flex. All that CMSs was not so 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:
> 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.
>

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

[Alex Harui]

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 support as much CSS as possible, especially Media
Query.  I have not looked into how folks are making their apps respond to
different screen sizes in the browser world today.  Is there a clear
winner or two?  If it is a pain point and FlexJS can do better, we should.

-Alex

On 5/27/15, 1:13 PM, Harbs harbs.li...@gmail.com wrote:

Now THAT, is a really interesting idea!

I can’t think of a better way to promote it (assuming it looks good…)

It might also be a good way to flush out some of the components.

If we’re on that topic: Has anyone given thought to responsive HTML in
FlexJS?

On May 27, 2015, at 11:04 PM, Alex Harui aha...@adobe.com wrote:

 And FTR, my wild dream is to write our site using FlexJS. ;-)  If this
was
 all MXML and AS, wouldn’t it be much easier to maintain?
 
 -Alex
 
 On 5/27/15, 12:52 PM, Michael Schmalle teotigraphix...@gmail.com
wrote:
 
 If I can manage to get my foothold with my business int he direction I
 want, I would be up to helping keep it fresh (in the future).
 
 One thing that would help Nic is when you go through and make updates,
 write a wiki page explaining what you did and the exact places that
should
 be kept up and a little explanation of how to do it with the template.
 
 I remember when you put all the time in it way back when and yeah, it
 served a purpose for the start of this project.
 
 Like I said, I am really trying to justify my time from a business
 perspective, anybody that knows my history, knows I put a HUGE amount
of
 time into blogging and tutorials when the project first started.
 
 Anyway, seems like there is an opportunity to re-brand Apache Flex this
 year and the project shouldn't miss it.
 
 BTW, Did you mean Joseph, not Josh? The one with the videos?
 
 Mike
 
 
 On Wed, May 27, 2015 at 3:44 PM, Nicholas Kwiatkowski
nicho...@spoon.as
 wrote:
 
 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'd like to integrate the newly
 donated Flex Docs into the site (with search, etc.), so doing a quick
 refresh of the content would make sense.
 
 The biggest concern when we launched the website originally was that
 there
 little content for us to include.  With Josh making this /huge/
 donation of
 time and effort this will be lessened, but if we could get a few
people
 to
 help collect external content for us to link to, that would be great.
 Even
 better, if anybody would like to step up and write tutorials for the
 website (or maintain things like the showcase, etc) that would help
keep
 the site fresh.
 
 -Nick
 
 On Wed, May 27, 2015 at 3:01 PM, Nemi nemino...@gmail.com wrote:
 
 Agree. More my comments:
 
 * Double/triple linking to same content doesn't make website more
 rich of
 content, it makes it not organized. For example:
 - 'Licensing' on front page and 'About Flex-License  Trademarks'
 link
 to
 same page  about-licensing.html
 http://flex.apache.org/about-licensing.html
 - 'Tooling', '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-Websit
e-
 thought-tp46946p46988.html
 Sent from the Apache Flex Development mailing list archive at
 Nabble.com.
 
 
 

Re: Apache Flex Website thought

[Josh Tynjala]

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 people don't stick around to see every item. I
think two or more side-by-side sections with the biggest selling points for
Flex should be front and center.

* Licensing probably shouldn't be the first thing mentioned in the four
boxes below the hero. It's important, but it can wait. If no other changes
could be made, I would put those four boxes in this order: Desktop  Mobile
Apps, Tooling, Licensing, Showcase.

* I think an example of MXML code would be nice somewhere on that page.
Just something simple to show how components can be put into containers as
child elements in the XML and maybe some binding. You could possibly put a
screenshot of the final output next to the MXML. However, as long as the
code is clear enough about what components are being used, it would be a
good start even without showing the result.

- Josh

On Wed, May 27, 2015 at 9:10 AM, Nemi nemino...@gmail.com wrote:

 For me, experienced with Flex, flex.apache.org is totally not useful. If
 I am
 new to Flex and go on website, I would be confused and give up.

 It does not look like some SDK website. More like some template site left
 alone. That big slider on frontpage? Come on... For every release one text
 line is enough with more link. So much unsed blank space, almost every
 image
 and titles are too large, no consistency on typography, but most important
 -
 content text - is too small, and Carrois Gothic is hard to read...

 For me, at least first things I want to see on front page (not hidden in
 menu) are: 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

[Nemi]

Agree. More my comments:

* Double/triple linking to same content doesn't make website more rich of
content, it makes it not organized. For example:
- 'Licensing' on front page and 'About Flex-License  Trademarks' link to
same page  about-licensing.html
http://flex.apache.org/about-licensing.html  
- 'Tooling', '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

[Michael Schmalle]

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 a bit.

BTW, this stuff is not my forte so I am just suggesting things for people
who layout and write well. :)

Mike

On Wed, May 27, 2015 at 11:49 AM, Alex Harui aha...@adobe.com wrote:



 On 5/27/15, 7:48 AM, Joseph Labrecque joseph.labrec...@du.edu 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, create an account, let me know what
 it is and I’ll give you create/edit access (unless someone objects which I
 doubt will happen).

 [1] https://cwiki.apache.org/confluence/display/FLEX/Apache+Flex+Wiki

Re: Apache Flex Website thought

[JosephLabrecque]

Alex Harui wrote
 On 5/27/15, 7:48 AM, Joseph Labrecque lt;

 Joseph.Labrecque@

 gt; 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, create an account, let me know what
 it is and I’ll give you create/edit access (unless someone objects which I
 doubt will happen).
 
 [1] https://cwiki.apache.org/confluence/display/FLEX/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-Flex-Website-thought-tp46946p46957.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: Apache Flex Website thought

[Nemi]

For me, experienced with Flex, flex.apache.org is totally not useful. If I am
new to Flex and go on website, I would be confused and give up. 

It does not look like some SDK website. More like some template site left
alone. That big slider on frontpage? Come on... For every release one text
line is enough with more link. So much unsed blank space, almost every image
and titles are too large, no consistency on typography, but most important -
content text - is too small, and Carrois Gothic is hard to read... 

For me, at least first things I want to see on front page (not hidden in
menu) are: 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

[Alex Harui]

On 5/27/15, 7:48 AM, Joseph Labrecque joseph.labrec...@du.edu 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, create an account, let me know what
it is and I’ll give you create/edit access (unless someone objects which I
doubt will happen).

[1] https://cwiki.apache.org/confluence/display/FLEX/Apache+Flex+Wiki

RE: Apache Flex Website thought

[Joseph Labrecque]

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, 
distributions, and somewhat related frameworks (Starling, Feathers).

I have seen things shifting around and it seems there are a number of people 
coming back to the technology and new people giving it a go. If I was 
interested in Apache Flex and all I had access to were outdated tutorials - I'd 
probably forget about it. From a new user perspective things must appear active 
and recent.

Obviously, if a new user had a peek at this mailing list it would be obvious 
how active Apache Flex really is - but this is not front facing... and neither 
is it an appropriate mechanism for introducing users to the platform.

Here is a question: what sort of tutorials (written, video, demos) would be 
useful in both attracting new users and getting the attention of bitter old 
Flex devs who still have a little spark of mxml left in their souls?  I'm 
willing to continue putting some stuff together - and I bet there are others 
out there too.

Traditional Apache Flex, FlexJS, and eventually the Feathers Flex stuff that 
Josh is building all have great potential and having up to date resources that 
reflect that is essential. I'm absolutely willing to dedicate time to all three 
areas - and to seek out others who may have contributions to make... so if 
anyone has any ideas... is there a mechanism to keep a list or wiki within 
Apache?

-- 
Joseph Labrecque 
Senior Interactive Software Engineer 
University of Denver 

Adobe Education Leader | Adobe Community Professional

Re: Apache Flex Website thought

[Alex Harui]

On 5/27/15, 9:01 AM, JosephLabrecque joseph.labrec...@du.edu 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

[Michael Schmalle]

If I can manage to get my foothold with my business int he direction I
want, I would be up to helping keep it fresh (in the future).

One thing that would help Nic is when you go through and make updates,
write a wiki page explaining what you did and the exact places that should
be kept up and a little explanation of how to do it with the template.

I remember when you put all the time in it way back when and yeah, it
served a purpose for the start of this project.

Like I said, I am really trying to justify my time from a business
perspective, anybody that knows my history, knows I put a HUGE amount of
time into blogging and tutorials when the project first started.

Anyway, seems like there is an opportunity to re-brand Apache Flex this
year and the project shouldn't miss it.

BTW, Did you mean Joseph, not Josh? The one with the videos?

Mike


On Wed, May 27, 2015 at 3:44 PM, Nicholas Kwiatkowski nicho...@spoon.as
wrote:

 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'd like to integrate the newly
 donated Flex Docs into the site (with search, etc.), so doing a quick
 refresh of the content would make sense.

 The biggest concern when we launched the website originally was that there
 little content for us to include.  With Josh making this /huge/ donation of
 time and effort this will be lessened, but if we could get a few people to
 help collect external content for us to link to, that would be great.  Even
 better, if anybody would like to step up and write tutorials for the
 website (or maintain things like the showcase, etc) that would help keep
 the site fresh.

 -Nick

 On Wed, May 27, 2015 at 3:01 PM, Nemi nemino...@gmail.com wrote:

  Agree. More my comments:
 
  * Double/triple linking to same content doesn't make website more rich of
  content, it makes it not organized. For example:
  - 'Licensing' on front page and 'About Flex-License  Trademarks' link
 to
  same page  about-licensing.html
  http://flex.apache.org/about-licensing.html
  - 'Tooling', '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

[Alex Harui]

And FTR, my wild dream is to write our site using FlexJS. ;-)  If this was
all MXML and AS, wouldn’t it be much easier to maintain?

-Alex

On 5/27/15, 12:52 PM, Michael Schmalle teotigraphix...@gmail.com wrote:

If I can manage to get my foothold with my business int he direction I
want, I would be up to helping keep it fresh (in the future).

One thing that would help Nic is when you go through and make updates,
write a wiki page explaining what you did and the exact places that should
be kept up and a little explanation of how to do it with the template.

I remember when you put all the time in it way back when and yeah, it
served a purpose for the start of this project.

Like I said, I am really trying to justify my time from a business
perspective, anybody that knows my history, knows I put a HUGE amount of
time into blogging and tutorials when the project first started.

Anyway, seems like there is an opportunity to re-brand Apache Flex this
year and the project shouldn't miss it.

BTW, Did you mean Joseph, not Josh? The one with the videos?

Mike


On Wed, May 27, 2015 at 3:44 PM, Nicholas Kwiatkowski nicho...@spoon.as
wrote:

 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'd like to integrate the newly
 donated Flex Docs into the site (with search, etc.), so doing a quick
 refresh of the content would make sense.

 The biggest concern when we launched the website originally was that
there
 little content for us to include.  With Josh making this /huge/
donation of
 time and effort this will be lessened, but if we could get a few people
to
 help collect external content for us to link to, that would be great.
Even
 better, if anybody would like to step up and write tutorials for the
 website (or maintain things like the showcase, etc) that would help keep
 the site fresh.

 -Nick

 On Wed, May 27, 2015 at 3:01 PM, Nemi nemino...@gmail.com wrote:

  Agree. More my comments:
 
  * Double/triple linking to same content doesn't make website more
rich of
  content, it makes it not organized. For example:
  - 'Licensing' on front page and 'About Flex-License  Trademarks'
link
 to
  same page  about-licensing.html
  http://flex.apache.org/about-licensing.html
  - 'Tooling', '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

[Nicholas Kwiatkowski]

Yeah.  Ultimately, I'd really love to see the site powered by a CMS.  The
bastardization of a CMS we have right now really makes even the small
changes like smashing a triakis tetrahedron peg into a round hole. With the
advent of modern CMSs generating static sites and Apache really wanting to
go away from the solution they provide, it might be something we can do.

-Nick

On Wed, May 27, 2015 at 4:04 PM, Alex Harui aha...@adobe.com wrote:

 And FTR, my wild dream is to write our site using FlexJS. ;-)  If this was
 all MXML and AS, wouldn’t it be much easier to maintain?

 -Alex

 On 5/27/15, 12:52 PM, Michael Schmalle teotigraphix...@gmail.com
 wrote:

 If I can manage to get my foothold with my business int he direction I
 want, I would be up to helping keep it fresh (in the future).
 
 One thing that would help Nic is when you go through and make updates,
 write a wiki page explaining what you did and the exact places that should
 be kept up and a little explanation of how to do it with the template.
 
 I remember when you put all the time in it way back when and yeah, it
 served a purpose for the start of this project.
 
 Like I said, I am really trying to justify my time from a business
 perspective, anybody that knows my history, knows I put a HUGE amount of
 time into blogging and tutorials when the project first started.
 
 Anyway, seems like there is an opportunity to re-brand Apache Flex this
 year and the project shouldn't miss it.
 
 BTW, Did you mean Joseph, not Josh? The one with the videos?
 
 Mike
 
 
 On Wed, May 27, 2015 at 3:44 PM, Nicholas Kwiatkowski nicho...@spoon.as
 wrote:
 
  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'd like to integrate the newly
  donated Flex Docs into the site (with search, etc.), so doing a quick
  refresh of the content would make sense.
 
  The biggest concern when we launched the website originally was that
 there
  little content for us to include.  With Josh making this /huge/
 donation of
  time and effort this will be lessened, but if we could get a few people
 to
  help collect external content for us to link to, that would be great.
 Even
  better, if anybody would like to step up and write tutorials for the
  website (or maintain things like the showcase, etc) that would help keep
  the site fresh.
 
  -Nick
 
  On Wed, May 27, 2015 at 3:01 PM, Nemi nemino...@gmail.com wrote:
 
   Agree. More my comments:
  
   * Double/triple linking to same content doesn't make website more
 rich of
   content, it makes it not organized. For example:
   - 'Licensing' on front page and 'About Flex-License  Trademarks'
 link
  to
   same page  about-licensing.html
   http://flex.apache.org/about-licensing.html
   - 'Tooling', '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

[Nicholas Kwiatkowski]

On Wed, May 27, 2015 at 3:52 PM, Michael Schmalle teotigraphix...@gmail.com
 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

[Nicholas Kwiatkowski]

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'd like to integrate the newly
donated Flex Docs into the site (with search, etc.), so doing a quick
refresh of the content would make sense.

The biggest concern when we launched the website originally was that there
little content for us to include.  With Josh making this /huge/ donation of
time and effort this will be lessened, but if we could get a few people to
help collect external content for us to link to, that would be great.  Even
better, if anybody would like to step up and write tutorials for the
website (or maintain things like the showcase, etc) that would help keep
the site fresh.

-Nick

On Wed, May 27, 2015 at 3:01 PM, Nemi nemino...@gmail.com wrote:

 Agree. More my comments:

 * Double/triple linking to same content doesn't make website more rich of
 content, it makes it not organized. For example:
 - 'Licensing' on front page and 'About Flex-License  Trademarks' link to
 same page  about-licensing.html
 http://flex.apache.org/about-licensing.html
 - 'Tooling', '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

[Joseph Labrecque]

I'm willing to help out in both regards: content creation and maintenance. 

The docs integration right up front would be a great improvement!

-- 
Joseph Labrecque 
Senior Interactive Software Engineer 
University of Denver 

Adobe Education Leader | Adobe Community Professional


-Original 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'd like to integrate the newly donated 
Flex Docs into the site (with search, etc.), so doing a quick refresh of the 
content would make sense.

The biggest concern when we launched the website originally was that there 
little content for us to include.  With Josh making this /huge/ donation of 
time and effort this will be lessened, but if we could get a few people to help 
collect external content for us to link to, that would be great.  Even better, 
if anybody would like to step up and write tutorials for the website (or 
maintain things like the showcase, etc) that would help keep the site fresh.

-Nick

On Wed, May 27, 2015 at 3:01 PM, Nemi nemino...@gmail.com wrote:

 Agree. More my comments:

 * Double/triple linking to same content doesn't make website more rich 
 of content, it makes it not organized. For example:
 - 'Licensing' on front page and 'About Flex-License  Trademarks' 
 link to same page  about-licensing.html 
 http://flex.apache.org/about-licensing.html
 - 'Tooling', '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-Websi
 te-thought-tp46946p46988.html Sent from the Apache Flex Development 
 mailing list archive at Nabble.com.

Re: Apache Flex Website thought

[Harbs]

Now THAT, is a really interesting idea!

I can’t think of a better way to promote it (assuming it looks good…)

It might also be a good way to flush out some of the components.

If we’re on that topic: Has anyone given thought to responsive HTML in FlexJS?

On May 27, 2015, at 11:04 PM, Alex Harui aha...@adobe.com wrote:

 And FTR, my wild dream is to write our site using FlexJS. ;-)  If this was
 all MXML and AS, wouldn’t it be much easier to maintain?
 
 -Alex
 
 On 5/27/15, 12:52 PM, Michael Schmalle teotigraphix...@gmail.com wrote:
 
 If I can manage to get my foothold with my business int he direction I
 want, I would be up to helping keep it fresh (in the future).
 
 One thing that would help Nic is when you go through and make updates,
 write a wiki page explaining what you did and the exact places that should
 be kept up and a little explanation of how to do it with the template.
 
 I remember when you put all the time in it way back when and yeah, it
 served a purpose for the start of this project.
 
 Like I said, I am really trying to justify my time from a business
 perspective, anybody that knows my history, knows I put a HUGE amount of
 time into blogging and tutorials when the project first started.
 
 Anyway, seems like there is an opportunity to re-brand Apache Flex this
 year and the project shouldn't miss it.
 
 BTW, Did you mean Joseph, not Josh? The one with the videos?
 
 Mike
 
 
 On Wed, May 27, 2015 at 3:44 PM, Nicholas Kwiatkowski nicho...@spoon.as
 wrote:
 
 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'd like to integrate the newly
 donated Flex Docs into the site (with search, etc.), so doing a quick
 refresh of the content would make sense.
 
 The biggest concern when we launched the website originally was that
 there
 little content for us to include.  With Josh making this /huge/
 donation of
 time and effort this will be lessened, but if we could get a few people
 to
 help collect external content for us to link to, that would be great.
 Even
 better, if anybody would like to step up and write tutorials for the
 website (or maintain things like the showcase, etc) that would help keep
 the site fresh.
 
 -Nick
 
 On Wed, May 27, 2015 at 3:01 PM, Nemi nemino...@gmail.com wrote:
 
 Agree. More my comments:
 
 * Double/triple linking to same content doesn't make website more
 rich of
 content, it makes it not organized. For example:
 - 'Licensing' on front page and 'About Flex-License  Trademarks'
 link
 to
 same page  about-licensing.html
 http://flex.apache.org/about-licensing.html
 - 'Tooling', '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

[piotrz]

Maybe writing whole website at this point in FlexJS will be really hard to
achieve. But what about split everything into two directions. 
- Modify/write website in an old fashion in html
- Start writing CMS for this website in FlexJS

Many years ago I was working for some company where we wrote website in html
and cms in Flex. All that CMSs was not so 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: 
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

[kevin.godell]

I don't mean to pile on, but the user groups section[1] needs a little
attention. Some of the links go to dead websites or groups that no longer
exist. From my perspective, which is that of an amateur at best, I had found
the website and wiki difficult to navigate.  And when I had tried to visit
some of the user groups that were listed in the wiki, well... let's just say
that I was less than inspired to find very little signs of life. But of
course, we can change that. We can make Flex strong again. I predict that
zillions of Flex user groups will be flocking to be part of the rebirth!

[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.