2012/1/14 Bertrand Delacretaz :
> But nothing prevents ApacheFlex from including, alongside its core
> product, various sample applications that demonstrate various
> approaches.
of course not, and I really like the idea of having a contrib or samples area.
Dirk.
On Fri, Jan 13, 2012 at 12:23 PM, Dirk Eismann wrote:
> ...IMHO there is no "right" (nor "wrong") way in how to architect a Flex
> application at all. And as you can see it's actually depending very
> much on your very POV and preferences. Getting consensus on this hot
> (religious?) topic will be
It's a good thing I don't get worked up about things. :P
#toomuchcaffeineortechnomusic
On Friday, January 13, 2012, jude wrote:
> The Flex SDK (the Apache Flex project) is the source of everything
related to Flex. If you want to get Flex you come here. Isn't this now the
official channel / site?
I would be glad to write it but it seems to me that people are suggesting
resources or tutorials (no matter what they are) shouldn't be apart of this
project. I disagree with that. Or I'm suggesting that we have a descendant
site that does provide these resources.
As far as the best way to design
Original Message
> From: "Sebastian Mohr"
> Sent: sexta-feira, 13 de Janeiro de 2012 11:35
> To: flex-dev@incubator.apache.org
> Subject: Re: Goal for Flex: Strengthening large-scale Flex applications
>
> Hey Jude ...
>
... Don't make it bad.
Sorry, I couldn't help myself... :)
The Flex SDK (the Apache Flex project) is the source of everything related
to Flex. If you want to get Flex you come here. Isn't this now the official
channel / site? Is there another site that people will go? If this *is* the
official place then it should be the landing page for Flex resources or
No offence but now I know what my Project Manager goes through when we have
a design discussion. *tongue in cheek*
Thanks
Avinash Y
On Fri, Jan 13, 2012 at 5:13 PM, David Arno wrote:
> > From: jude [mailto:flexcapaci...@gmail.com]
> > Sent: 13 January 2012 10:48
> >
> > I have to agree with Se
> From: jude [mailto:flexcapaci...@gmail.com]
> Sent: 13 January 2012 10:48
>
> I have to agree with Sebastian on this. I think it is the responsibility
of the architects to
> show how they intend the architecture should be used. At least in an
abstract way.
I'm going to repeat myself from yeste
Hey Jude ...
I had to understand yesterday ... this flex-dev
list is not the place to discuss these issues.
Maybe an analogy to the car industry
would help to make this clear:
"We are here to build car parts. But we don't care which
type of car you build, and, how you'd drive that thing."
Pr
agree. I also think this should be handled differently and not by Apache Flex.
IMHO there is no "right" (nor "wrong") way in how to architect a Flex
application at all. And as you can see it's actually depending very
much on your very POV and preferences. Getting consensus on this hot
(religious?)
m]
Sent: 13 January 2012 10:48
To: flex-dev@incubator.apache.org
Subject: Re: Goal for Flex: Strengthening large-scale Flex applications
I have to agree with Sebastian on this. I think it is the responsibility of
the architects to show how they intend the architecture should be used. At
least in an
Jude don't get me wrong but clearly I still don't believe it's an Apache
Flex matter. Apache Flex exists to drive the future of the project, not to
teach people how they should do something. Yes, if new stuff comes around,
documentation about new features should be available,eventually some specs
m
I have to agree with Sebastian on this. I think it is the responsibility of
the architects to show how they intend the architecture should be used. At
least in an abstract way.
Flex apps with or without micro frameworks have a common setup across them
in general. It would be helpful going forward
On Wednesday, January 11, 2012, Sebastian Mohr wrote:
> @Roland
>
> hmm ... maybe you are right ;) But this is not my concern
> now. I am talking about building large-scale Flex apps and
> how to build them the best way.
>
>
> -- Sebastian
>
>
I get what you're saying and I totally feel you, but
I think what would be MUCH more productive is a PR effort to show off
really large, well-done Flex apps in enterprises. Developing really large
apps in Flex is much easier than doing the same in HTML/JS today. Even if
the framework might lend itself to some bad practices, or if we don't have
best p
On Wed, Jan 11, 2012 at 2:09 PM, Sebastian Mohr wrote:
> I am talking about building large-scale Flex apps and
> how to build them the best way.
>
Eh. I'd say that you'd be spinning your wheels on this one and don't know
how many people would catch on. There are so many frameworks and ways to
de
@Roland
hmm ... maybe you are right ;) But this is not my concern
now. I am talking about building large-scale Flex apps and
how to build them the best way.
-- Sebastian
On Jan 11, 2012, at 8:51 PM, Roland Zwaga wrote:
> Hehe, I think Alex mean the Flash Player as the constrained environme
On 1/11/12 11:47 AM, "Sebastian Mohr" wrote:
> Sorry ... where is a constraint environment in an open Apache Flex?
Flash is a constrained environment. It is a VM running in a browser in an
operating system, surrounded by various layers of security. Developing for
it is not too far removed fr
> From: Raju Bitter [mailto:rajubit...@googlemail.com]
> Sent: 11 January 2012 18:59
>> I will repeat my cautionary statement that we are working in a
>> constrained environment and will likely need to cheat on occasion.
>Right, we only need to know when we should cheat. :-)
I got the impressio
Hehe, I think Alex mean the Flash Player as the constrained environment
here, i.e. it has some limitations.
On 11 January 2012 20:47, Sebastian Mohr wrote:
> @Alex ...
>
> > Some coding practice document will be a good thing, but I can still write
> > bad code using it.
>
>
> IMHO ... there is n
@Alex ...
> Some coding practice document will be a good thing, but I can still write
> bad code using it.
IMHO ... there is no need to waste time in writing more documentation ...
we need more a "SHOW ME THE CODE" (in short "SMTC") approach ...
just "SMTC" and only "SMTC". Time to philosophize
On 1/11/12 10:59 AM, "Raju Bitter" wrote:
> Right, we only need to know when we should cheat. :-)
Here's a real life example. In a prototype of carving UIComponent into many
little pieces, it suffered from overhead of calling between the styles and
layout pieces. It might be in some future,
> I will repeat my cautionary statement that we are working in a constrained
> environment and will likely need to cheat on occasion.
Right, we only need to know when we should cheat. :-)
On 1/11/12 8:17 AM, "Sebastian Mohr" wrote:
> I think what the Flex community really needs is some
> kind of website where best coding practice examples
> will be collected and managed for the next ongoing
> years of Flex.
Some coding practice document will be a good thing, but I can still wri
On Jan 11, 2012, at 4:41 PM, Quentin Le Hénaff wrote:
> I propose to list all bad design we know about the Flex 3 and 4 frameworks
> and propose technical/designs solutions ; should the JIRA do the stuff?
For the moment, I have done it the other way
around ... which means proposing "good design"
>
> As part of my research, for now I think "Building large-scale
> Flex applications is simple" is a false-proof statement. If you
> don't believe that, please have a look to all those Flex application
> which have to deal with more then 150 MXML files and all their
> worries and issues they ran i
26 matches
Mail list logo
