57，Erik de Bruin 写道：
>
> > Talking about a "roadmap" is very sensitive on this list, and might
> > start another mega-thread ;-) Please search the archives on the
> > previous ones!
> >
> > The basic consensus is that Apache Flex is going where ever you,
hanks for your help.
李楠
在 2012-10-22，14:57，Erik de Bruin 写道：
> Talking about a "roadmap" is very sensitive on this list, and might
> start another mega-thread ;-) Please search the archives on the
> previous ones!
>
> The basic consensus is that Apache Flex is going wher
hanks for your help.
李楠
在 2012-10-22，14:57，Erik de Bruin 写道：
> Talking about a "roadmap" is very sensitive on this list, and might
> start another mega-thread ;-) Please search the archives on the
> previous ones!
>
> The basic consensus is that Apache Flex is going wher
hanks for your help.
李楠
在 2012-10-22，14:57，Erik de Bruin 写道：
> Talking about a "roadmap" is very sensitive on this list, and might
> start another mega-thread ;-) Please search the archives on the
> previous ones!
>
> The basic consensus is that Apache Flex is going wher
Talking about a "roadmap" is very sensitive on this list, and might
start another mega-thread ;-) Please search the archives on the
previous ones!
The basic consensus is that Apache Flex is going where ever you, me
and the other volunteers want to take it. Right now that means sett
Does apache flex have a release plan, you know, it is hard to catch up with all
the mails, so I am gonna ask this right here. It is very important for me and I
guess for everybody to know where apache is going. And it is even hard to find
this kind of answer in the SVN repo.
Many thanks for any
On Mon, Oct 1, 2012 at 6:10 PM, Blaine Bradbury
> wrote: On the Roadmap issue: I think it would be
> EXTREMELY useful to have a device which could show the current (as close to
> the present knowledge as is really manageable) trajectory that the Apache
> Flex project
On 10/1/12 11:21 PM, "Métairie, Stéphane" wrote:
> This page shown a rudimentary but interesting Roadmap that doesn't come
> magically by itself there ;)
> https://cwiki.apache.org/confluence/display/FLEX/Status+of+Project
>
> I'm insisting that Decision
On Tuesday, October 2, 2012, Bertrand Delacretaz wrote:
> On Tue, Oct 2, 2012 at 3:10 AM, Blaine Bradbury
> > wrote:
> > ...I think it would be EXTREMELY useful to have a device which could
> show the
> > current (as close to the present knowledge as is really manageable)
> > trajectory that the A
On Tue, Oct 2, 2012 at 3:10 AM, Blaine Bradbury
wrote:
> ...I think it would be EXTREMELY useful to have a device which could show the
> current (as close to the present knowledge as is really manageable)
> trajectory that the Apache Flex project is taking...
>From my experience with other Apache
he compiler because it brings joy to me. This is why
Apache does not use roadmaps, they know taking away developers joy in
project means certain death and a ghost town soon to follow.
Mike
Quoting Omar Gonzalez :
On Mon, Oct 1, 2012 at 11:21 PM, Métairie, Stéphane wrote:
This page sho
I think you should not be tensed with this Roadmap, and nobody will spend his
time to update a timeline ... the status of the project is sufficient, perhaps
more visible would be better. Just my opinion ;)
"But people committing, making patches and contributing will."
We agree.
---
On Mon, Oct 1, 2012 at 11:21 PM, Métairie, Stéphane wrote:
> This page shown a rudimentary but interesting Roadmap that doesn't come
> magically by itself there ;)
> https://cwiki.apache.org/confluence/display/FLEX/Status+of+Project
No, it doesn't automatically appear the
This page shown a rudimentary but interesting Roadmap that doesn't come
magically by itself there ;)
https://cwiki.apache.org/confluence/display/FLEX/Status+of+Project
I'm insisting that Decision Maker won't drill down the web site to reach the
confluence wiki to find t
On Mon, Oct 1, 2012 at 10:57 PM, Métairie, Stéphane wrote:
> For all observers (and FLEX orphans) the roadmap, or some milestones,
> publicly shared will be helpful and ... comforting : many IT decision-maker
> wonder if they have to continue with Flex or not.
>
>
There
For all observers (and FLEX orphans) the roadmap, or some milestones, publicly
shared will be helpful and ... comforting : many IT decision-maker wonder if
they have to continue with Flex or not.
-Original Message-
From: Omar Gonzalez [mailto:omarg.develo...@gmail.com]
Sent: mardi, 2
On Mon, Oct 1, 2012 at 6:10 PM, Blaine Bradbury
wrote:
> On the Roadmap issue:
>
> I think it would be EXTREMELY useful to have a device which could show the
> current (as close to the present knowledge as is really manageable)
> trajectory that the Apache Flex project is taking
On the Roadmap issue:
I think it would be EXTREMELY useful to have a device which could show the
current (as close to the present knowledge as is really manageable)
trajectory that the Apache Flex project is taking. On any given day, there
are folks hard at work contributing new things with the
It looks like it generated a roadmap.html page that it didn't clean up when
the page was renamed.
Not sure if it can be removed.
-omar
On Thu, Sep 13, 2012 at 10:25 AM, Raju Bitter <
r.bitter.mailingli...@googlemail.com> wrote:
> Thanks, Omar. That's what I guessed, I rememb
Thanks, Omar. That's what I guessed, I remember that the roadmap wiki
page was changed long ago. Strange that the old page is still online.
- Raju
On Thu, Sep 13, 2012 at 8:12 AM, Raju Bitter <
r.bitter.mailingli...@googlemail.com> wrote:
> There's still a Flex wiki page called roadmap page somewhere up on
> apache.org:
> https://cwiki.apache.org/FLEX/roadmap.html
> Quoting that page: " we're right
There's still a Flex wiki page called roadmap page somewhere up on apache.org:
https://cwiki.apache.org/FLEX/roadmap.html
Quoting that page: " we're right now deciding the roadmap for next
releases of Apache Flex"
You might want to take that offline, it's a bit conf
Quoting Carol Frampton :
I think we've been thru this before but I'm not going to take the time to
find the thread. I don't think people had a problem with putting together
a list of project suggestions and what people are working on. I think the
issue was more with the term &q
I think the
> issue was more with the term "Roadmap" because, at least in the corporate
> world, that generally implies a commitment and since this is a volunteer
> effort and people can work on whatever they wish there can be no
> commitments to a Roadmap.
>
Exactly. Som
I think we've been thru this before but I'm not going to take the time to
find the thread. I don't think people had a problem with putting together
a list of project suggestions and what people are working on. I think the
issue was more with the term "Roadmap" because,
On Wed, Sep 12, 2012 at 8:13 AM, Justin Mclean wrote:
> Hi,
>
>> Okay then, is there a road-map or a plan in this project??
> Being an open source project there is no roadmap as such. People are free to
> work on whatever they want when they want.
>
> If enough users of
Whiteboard/cframpton/adobe.next
Sent from my Motorola ATRIX™ 4G on AT&T
-Original message-
From: Tink
To: "flex-dev@incubator.apache.org"
Sent: Mon, Aug 13, 2012 21:04:02 GMT+00:00
Subject: [DISCUSS] Navigators (was [ROADMAP] Apache Flex Steering Survey -
Revised co
Hey Alex
Have the navigators been committed to a whiteboard anywhere?
I like to open up some discussion about navigators, but thought I'd wait for
these to be committed first.
cheers
Tink
On 3 Aug 2012, at 17:09, Alex Harui wrote:
>>4.6 ViewStack (listed in Flex White Paper - protoype)
f updates,
> for example. Spoon had the same problems as you had choosing a page title
> for your information. Spoon used alternate words to "Roadmap" like status,
> highlights, community objectives, and community priorities. In case you
> have not seen the newsletter - it is
eiving information about the
project. The August newsletter is full of updates, for example. Spoon had the
same problems as you had choosing a page title for your information. Spoon used
alternate words to "Roadmap" like status, highlights, community objectives, and
community priorit
ote:
>
> >
> >
> > On 8/11/12 12 :37PM, "Igor Costa" >
> > wrote:
> >
> > >I've setup a page in wiki to other developers see what's going on with
> > >committers.
> > >https://cwiki.apache.org/confluence/display/FLEX/Road
On Monday, August 13, 2012, Carol Frampton wrote:
>
>
> On 8/11/12 12 :37PM, "Igor Costa" >
> wrote:
>
> >I've setup a page in wiki to other developers see what's going on with
> >committers.
> >https://cwiki.apache.org/confluence/displ
On 8/11/12 12 :37PM, "Igor Costa" wrote:
>I've setup a page in wiki to other developers see what's going on with
>committers.
>https://cwiki.apache.org/confluence/display/FLEX/Roadmap
>
>Roadmap is subject of change, any decision we make for next release,
I agree with Omar. Igor, please change your use of the word "Roadmap".
An interesting thing to do might be to devise a survey to find out what is
important to our different segments of potential users and focus on
non-features like having some sort of forecast or roadmap is really
imp
and History.
>
>
>
> Igor Costa
> www.igorcosta.com
> www.igorcosta.org
>
This his been a topic of discussion a few times before.
Here are some links:
http://markmail.org/message/wtkxutq4qbgrtqcu?q=+list:org%2Eapache%2Eincubator%2Eflex-dev+roadmap&page=2
http://markmail.or
t;> https://cwiki.apache.org/confluence/display/FLEX/Roadmap
> >>
> >> Roadmap is subject of change, any decision we make for next release, we
> >> should add on this page.
> >>
> >>
> >> Regards
> >>
> >> ----
On Saturday, August 11, 2012, Omar Gonzalez wrote:
> On Saturday, August 11, 2012, Igor Costa wrote:
>
>> I've setup a page in wiki to other developers see what's going on with
>> committers.
>> https://cwiki.apache.org/confluence/display/FLEX/Roadmap
>&
On Saturday, August 11, 2012, Igor Costa wrote:
> I've setup a page in wiki to other developers see what's going on with
> committers.
> https://cwiki.apache.org/confluence/display/FLEX/Roadmap
>
> Roadmap is subject of change, any decision we make for next release, we
On Wed, Aug 8, 2012 at 5:30 AM, jude wrote:
> ...I'd love to see a live or frequently updated status sheet / page / app that
> shows what's being worked on (general topics or Jira issues) , progress,
> participation count and so on if some how we can gather and show this
> information...
I'm sure
> I've been on this list long enough to know people will work on whatever the
> heck they want but that idea is and was hard to accept and plan for.
This is the Apache Way. The survey has no official purpose and carries no
official weight in the project. Each person who participates in this open
; Steering Survey which currently has more than 375 respondents since July
> 26th.
>
> With the successful release of Apache Flex 4.8.0-incubating (previously
> announced below) it is timely to have a discussion/consensus around the
> priorities going forward. Below is a link to a su
On 8/7/12 8:24 AM, "dharfl...@yahoo.com" wrote:
> Alex,
>
> with respect to Gravity, when you say "won't happen unless " is the
> reasoning behind this related to the amount of effort involved in
> 're-packaging' for Apache and legal compliance ?
>
>
> dan
Yes. I think Adobe's re
embers monitoring this list, but some may not as they probably relied on Adobe
(and partners) sales & marketing effort to keep them posted.
>> Agree, AF is in a unique situation, it has an established
user-based, we just need to get organized to access and inform it.
I am not saying I li
> Although the survey attempts to get to the bottom of feature priorities, I
> can't help feeling that we should be including parties other than this
> mailing list to take part in the survey. Although many of this list's
> participants including myself have an exposure > to a subset of the corp
f these large spending corporations will have
members monitoring this list, but some may not as they probably relied on Adobe
(and partners) sales & marketing effort to keep them posted.
I am not saying I like the idea of a 'roadmap', but I do like the idea of a
'picklist
;flex-dev@incubator.apache.org"
Sent: Friday, 3 August 2012, 17:09
Subject: Re: [ROADMAP] Apache Flex Steering Survey - Revised component status
On 8/3/12 8:51 AM, "Keith Sutton" wrote:
> Based on Alex's email this is a revise component list to go into survey
Right! I was thinking that it refers to the granite piece.
El lunes, 6 de agosto de 2012, John Fletcher escribió:
> Why did they give it two names? Why not just call it CCF? This isn't a
> new OS release.
>
> The "Gravity" name is a bit unfortunate as Granite DS message push
> framework is also c
Why did they give it two names? Why not just call it CCF? This isn't a
new OS release.
The "Gravity" name is a bit unfortunate as Granite DS message push
framework is also called Gravity (and has been for years). So now we
have two Gravities in Flex.
John
2012/8/3 Keith Sutton :
> There have be
Agree with the idea of not using the term "roadmap". Since actually,
what we are talking about is not a roadmap at all in the conventional
sense, and is much better described with the title you mention below
Keith. In this sense it might be apropriate for the actual Flex site -
but then
Yeah, it's Monocle. OK I just saw the your post on Gravity further down. I
could use something like this on a project I'm working on now.
On Sun, Aug 5, 2012 at 11:36 AM, Keith Sutton wrote:
> Good on Squiggly Jude, Gravity below, can't find anything on Telemetry -
> did this become Monocle?
>
Good on Squiggly Jude, Gravity below, can't find anything on Telemetry -
did this become Monocle?
On 8/5/2012 1:27 AM, jude wrote:
Squiggly is an Action Script spell checking library for developers who work
in Adobe® Flash® Professional, Adobe Flex® Builder™, or other IDEs that
support ActionSc
>I don't know what Gravity is either. Is it Telemetry? BTW What happened to
>Telemetry?
Gravity is a framework which, in theory, solves the problems associated with
multiple domain applications using the Marshall plan by providing a structure
to work within. While my opinion may be somewhat con
Squiggly is an Action Script spell checking library for developers who work
in Adobe® Flash® Professional, Adobe Flex® Builder™, or other IDEs that
support ActionScript. The Squiggly package contains six .swc files – three
of which integration convenience classes called SpellUI, one for Flex 3,
ano
Ok thanks for the info
It's a relief to know at least somebody is maintaining and advancing it :)
It's a rather crucial piece for most video related apps.
On Fri, Aug 3, 2012 at 1:24 PM, Michael A. Labriola <
labri...@digitalprimates.net> wrote:
> >About OSMF. What is the status of OSMF? Is it
>About OSMF. What is the status of OSMF? Is it being actively maintained and
>developed by Adobe?
OSMF is still being actively maintained and expanded by Adobe, that is probably
part of the reason we won't see it soon/ever without some work on our part.
>
>
>>> All are in progress, TLF will probably be next.
>>
>> Squiggly
>>> * OSMF*
>>> Gravity
>>>
>> Won't happen unless we hear lots of people want it.
>>
>>
>>
>>
About OSMF. What is the status of OSMF? Is it being actively maintained and
developed by Adobe?
By "Won't happen...
Alex/Carol,
Awesome, thanks
We will role that back into the survey
On 8/3/2012 9:09 AM, Alex Harui wrote:
On 8/3/12 8:51 AM, "Keith Sutton" wrote:
Based on Alex's email this is a revise component list to go into survey
(PLEASE identify anything missing or in wrong place):
Available in 4.
On 8/3/12 8:51 AM, "Keith Sutton" wrote:
> Based on Alex's email this is a revise component list to go into survey
> (PLEASE identify anything missing or in wrong place):
>
> Available in 4.8
> 4.6 automation libraries
> 4.6 fabridge
> 4.6 flash-integration
> 4.6 samples
>
On 8/3/12 11 :51AM, "Keith Sutton" wrote:
>Based on Alex's email this is a revise component list to go into survey
>(PLEASE identify anything missing or in wrong place):
>
>Available in 4.8
>4.6 automation libraries
>4.6 fabridge
>4.6 flash-integration
>4.6 samples
>Flex MXM
Based on Alex's email this is a revise component list to go into survey
(PLEASE identify anything missing or in wrong place):
Available in 4.8
4.6 automation libraries
4.6 fabridge
4.6 flash-integration
4.6 samples
Flex MXML compiler source code
Yet to be donated
? 4.6 missing
There have been a number of question about Gravity (also referred to as
Client Component Framework).
"The ADEP Client Component Framework (codename Gravity) is an
ActionScript library that takes the concepts of OSGi and applies them to
ActionScript. It provides a module and/or plugin architect
The survey/roadmap are definitely in line with your guidance and will
likely be called "Community Objectives and Priorities for Apache Flex"
and would be posted on the Spoon website. Although it cannot be binding
it does act as:
1) An expression of the community and their collectiv
ily fail, if they're too
ambitions, and people are disappointed.
> ...We just need to be a little careful and make it clear that it's not a
> roadmap in the traditional sense ie a list of
> features that are planned to be done by a certain date
Yes, it's more a list of go
A roadmap is fine so long as we don't use it to tell someone else what they
should be working on. OTOH if the vast majority of users are interested in a
particular set of features those will get implemented without a roadmap. :)
Sent from my mobile device.
On Aug 3, 2012, at 6:56 AM, J
s and contrubitors to pitch in.
We just need to be a little careful and make it clear that it's not a roadmap
in the traditional sense ie a list of features that are planned to be done by a
certain date.
Thanks,
Justin
If Spoon have organisation and/or heirarchy, and Apache accepts
contribution from anyone, then it might be simple: the Spoon
Foundation creates a Spoon Roadmap - what they hope to deliver to Flex
and when. They can post it on their Spoon.as website. Those that want
to be part of an organised
Exactly - Strangely enough I was just asking for hepl and directions for
building the SDK in Linux for FDT5
~a~
www.ayobinitie.com
http://mrbinitie.blogspot.com
On 2 August 2012 14:13, João Fernandes
wrote:
> Ayo,
>
> what do you refer to? Like building the SDK in a linux environment?
>
>
> --
>
Ayo,
what do you refer to? Like building the SDK in a linux environment?
--
João Fernandes
Committers can veto your work, but for technical reasons,
> not
> > because it wasn't on the roadmap or a high enough priority.
>
> Maybe they should have referred to it not as "Roadmap" but as
> "Contribution Suggestion List" ;-)
>
> EdB
>
>
> There is no hierarchy in the engineering. Nobody gets to tell anyone else
> what to do. Committers can veto your work, but for technical reasons, not
> because it wasn't on the roadmap or a high enough priority.
Maybe they should have referred to it not as "Roadmap&qu
;?
>
I don't see the PMC as project leads. They have more of an administrative
responsibility than a technical one. See [1].
There is no hierarchy in the engineering. Nobody gets to tell anyone else
what to do. Committers can veto your work, but for technical reasons, not
because it wasn&#
>> Some direction (agreed upon
>> by all the project leads, to be sure) will help get things off the
>> ground, or at least move along at something more than a glacial
>> pace...
> But there are no project leads. Just a bunch of committers and lots of
> other folks on the mailing list.
I'm not be
On 8/1/12 11:23 PM, "ranboleelan" wrote:
> not all mx components have their spark equivalent ones, so i guess more spark
> components in future version would be nice.
>
The prototypes we have are waiting VP signature then they will be checked
in.
--
Alex Harui
Flex SDK Team
Adobe Systems, I
not all mx components have their spark equivalent ones, so i guess more spark
components in future version would be nice.
ranboleelan
From: Alex Harui
Date: 2012-08-02 14:14
To: flex-dev@incubator.apache.org
Subject: Re: [ROADMAP] Apache Flex Steering Survey
On 8/1/12 10:25 PM, "Er
On 8/1/12 10:25 PM, "Erik de Bruin" wrote:
>> next. No consensus has to be reached on what will be worked on. Folks are
>> free to do what they want.
>
> Free to create a roadmap and try to give some direction to people
> looking to contribute, but no
Keith,
I'm sorry I did not respond to your first roadmap email. Honestly, I
stopped reading after your first bullet point raising FUD about whether
Adobe would live up to its commitments without any quoting of the statements
behind your logic. I almost responded, but when nobody else d
ensus has to be reached on what will be worked on.
Folks are
free to do what they want.
Thanks for saying that. :-) I think a lot of folks are having
trouble getting their head around the "no roadmap / do what you want"
approach of Apache.
I can see, however, that this could be a go
> next. No consensus has to be reached on what will be worked on. Folks are
> free to do what they want.
Free to create a roadmap and try to give some direction to people
looking to contribute, but not sure where to begin, or which
features/bug fixes would benefit the end users the most
they want.
Thanks for saying that. :-) I think a lot of folks are having trouble
getting their head around the "no roadmap / do what you want" approach
of Apache.
I can see, however, that this could be a good (or at least different)
way to collect information than the Jira bug bas
of Apache Flex 4.8.0-incubating (previously
> announced below) it is timely to have a discussion/consensus around the
> priorities going forward. Below is a link to a survey that will help
> guide discussions on objectives, priorities, features and functions
> (roadmap) that can guid
around the
priorities going forward. Below is a link to a survey that will help
guide discussions on objectives, priorities, features and functions
(roadmap) that can guide effort over the next 6-12 months. This survey
is 8 questions and should take less than 5 minutes to complete. Your
input is
and ecosystem, Apache Flex does not have the luxury of time as
>organizations wrestle with the decisions in the 6-12 months over
>Flex versus HTML5/JS/CSS (hope is not a roadmap).
>
> After gleaning through emails and blog posts the following is a list of
> potential things-to-do-next
project that grows over time,
this is a commercially viable product with a significant customer
base and ecosystem, Apache Flex does not have the luxury of time as
organizations wrestle with the decisions in the 6-12 months over
Flex versus HTML5/JS/CSS (hope is not a roadmap).
After
I think this is an excellent idea.
The ANT Task could replace user-defined tokens inside both the HTML pages
and .AS/MXML files for copy.
BTW:The older Flash Ford Sync website (2009?) had an alternative HTML
version that displayed the same content as the Flash Version (complete with
images and me
Jude:
On 12-02-28 10:06 AM, "jude" wrote:
>Here is my comment [2].
>
>I think SEO search results come down to popularity. Is everyone linking to
>your page? It might have something to do with Google analytics. How long
>people stay on your page.
DN: Amen brother! That is correct.
>
>But as a c
A few years ago Google posted a proposal for making ajax crawlable [1].
You'll need to read it to get the details but basically if you used a
special URL it would return only the data result not the view. To quote,
In summary, starting with a stateful URL such as
http://example.com/dictionary.html
On 12-02-27 6:35 PM, "David Francis Buhler" wrote:
>While I respect your opinion that my theory is factually wrong, I
>respectfully disagree. The cloaking theory I suggested is possible, and
>does not require a Google Appliance. If cloaking is a violation of
>Google's
>Terms, that doesn't mean i
While I respect your opinion that my theory is factually wrong, I
respectfully disagree. The cloaking theory I suggested is possible, and
does not require a Google Appliance. If cloaking is a violation of Google's
Terms, that doesn't mean it doesn't happen.
[1] http://www.petitiononline.com/stope
On 12-02-27 5:18 PM, "David Francis Buhler" wrote:
>My hunch is that their authentication mechanism does not require bots to
>be
>authenticated. That might be why you can view the entire page without
>being
>authenticated if you request the cached version.
>
>[1]
>http://www.experts-exchange.com/
My hunch is that their authentication mechanism does not require bots to be
authenticated. That might be why you can view the entire page without being
authenticated if you request the cached version.
[1]
http://www.experts-exchange.com/Web_Development/Web_Languages-Standards/Flex/Q_27377143.html
On 12-02-27 3:51 PM, "Alex Harui" wrote:
>I'm not saying the SDK will try to force anybody to use anything. I just
>thought there were issues where folks want to have more control over what
>text is found in a SWF, what links are found in the SWF and what buttons
>get
>pushed. I don't remember
On 2/27/12 3:22 PM, "Duane Nickull" wrote:
> DN: I have never seen any evidence of google using content it can access.
> Same for Bing and Yahoo. Flex can basically give it 500 words but for
> starters Google only takes 200 per site in most cases. They can all get
> text today, but the real
>
>I watched both videos. I'm not sure why you think there isn't stuff that
>Flex can do better to assist in the better static indexing of content, and
>making the set links available to the search engines. I thought there
>were
>things that Ichabod needed help with (like getting past authenticat
On 2/27/12 11:20 AM, "Duane Nickull" wrote:
> I honestly think that after watching these, you will all agree there is
> nothing that belongs on an SDK discussion list WRT SEO. It is simply not
> needed.
I watched both videos. I'm not sure why you think there isn't stuff that
Flex can do bett
On Mon, Feb 27, 2012 at 3:55 PM, Michael A. Labriola <
labri...@digitalprimates.net> wrote:
> Wasn't arguing if you could.
Oh I know you weren't arguing. I wasn't saying you were wrong. Just
throwing in another opinion of how one person's results when working with
it. My solution though was also
>I've done many applications that are SEO compliant using Flex. In my blog I've
>even outlines a few ways to do this, however there was never something within
>the framework that fully supported this. I ended up having to make >a bunch of
>extra logic to make this work, but it was possible.
Was
On Mon, Feb 27, 2012 at 3:16 PM, Michael A. Labriola <
labri...@digitalprimates.net> wrote:
> This topic is extremely interesting. I have always told my clients that if
> you needed SEO with a Flex app, you were likely pondering the wrong
> technology. I have never seen Flex apps as something that
>I used to develop my "all flash" homepages in a way that I represented
>all the data structure I accessed as HTML pages.
>So I got all indexable content out with regular lists and content first.
>Then I started with the Flash Homepage and built it entirely on the
>content of the container homepa
Compiler list? Developer mailing-list: anything Flex related :)
Anways: I think this discussion is important because a development model
on a XHTML data structure/provider could allow a Flash AND HTML
development model.
Just because websites are not made in Flash anymore doesn't mean rich
webs
It is a very valuable discussion to have. I am just not sure if it
belongs in the Compiler list.
FWIW - I used XHTML data providers. Having the keyword in for a
better initial ranking.
BTW - I will be in Vienna next week if you want to grab a beer to discuss?
Duane
___
1 - 100 of 156 matches
Mail list logo
