Just as a "me too" I can say that not checking in the .* files is the way
to go when working in teams. There are many problems it solves. I
completely agree with nick here.
On Apr 7, 2012 8:18 AM, "Nicholas Kwiatkowski" wrote:
> Your Flex 4.6 is not the same as my Flex 4.6. They are close, but t
Your Flex 4.6 is not the same as my Flex 4.6. They are close, but the
problem is I don't have an SDK compiler named "Flex 4.6.0" on my machine (I
have "Flex 4.6.0-23043" and "Flex 4.6.0-23201"). Additionally, I also add
certain compiler arguments to all of my projects. By having it included,
its
Just keep in mind that svn:ignore can't be applied on files already checked in
the repository. These should be manualy removed first and then set svn:ignore.
Tomislav
On 7. 4. 2012., at 13:22, Left Right wrote:
> svn:ignore is a Subversion documented property, whatever sets it is using
> Subv
svn:ignore is a Subversion documented property, whatever sets it is using
Subversion to support it, so it's fine to do that from any client. This
setting also gets transferred to other checkouts, so if you ignore a file
on your end, and I happen to create a file by the same name on my end, it
will
On 4/7/2012 4:11 AM, Tomislav Pokrajcic wrote:
Before committing project from Eclipse try setting svn:ignore for various Eclipse
settings files (Team -> add to svn:ignore).
That way you only commit sources and keep project settings for yourself.
Wouldn't these settings be specific to the SVN
On 4/7/2012 3:38 AM, Justin Mclean wrote:
HI,
Once I set my compiler options to what they are supposed to
be on my machine, the errors cleared up and everything was fine.
I'd assume the SDK wasn't set to a version in the project but just "use
default". This could also cause errors if you had
the update. That's just another example I thought of that I've seen happen.
That said I was just kind of recommending it, but I think we should all be
free to do whatever we want in our whiteboard areas. I just think its
annoying when I find Eclipse/IntelliJ/whatever files in code repo
Before committing project from Eclipse try setting svn:ignore for various
Eclipse settings files (Team -> add to svn:ignore).
That way you only commit sources and keep project settings for yourself.
Cheers,
Tomislav
On 7. 4. 2012., at 04:45, Jeffry Houser wrote:
> On 4/6/2012 10:22 PM, Nich
How I set up the project:
1. I didn't merge the SDKs, instead I imported from both locations the
libraries I needed.
2. My eclipse workspace contains a lot of settings (mostly syntax
highlighting), that I don't want to loose, and it's in an entirely
different place from where I check the source cod
Hi,
> Yep, pretty much why it's an annoyance.
Actually I think it's more of an annoyance if you don't know what the compiler
settings, SDK version, library paths etc etc are.
Even if you don't use Flash Builder the file are still mostly human readable
and contain the required settings.
Altern
HI,
> Once I set my compiler options to what they are supposed to
> be on my machine, the errors cleared up and everything was fine.
I'd assume the SDK wasn't set to a version in the project but just "use
default". This could also cause errors if you had a different SDK set by
default and impor
On 4/6/2012 10:22 PM, Nicholas Kwiatkowski wrote:
I would recommend against it. It forces me to import your project
into my workspace, versus having a new project that I can import
cleanly from SVN.
I don't understand why it forces you to import the project, as opposed
to creating your ow
On Friday, April 6, 2012, Nicholas Kwiatkowski wrote:
> Jeffery,
>
> I would recommend against it. It forces me to import your project into my
> workspace, versus having a new project that I can import cleanly from SVN.
> When I imported your code, it had about 30 errors I had to hunt and peck
>
gt;
>> While this may be convenient for some Flash Builder users it leaves
>> useless files behind for people that don't use Flash Builder. I think those
>> shouldn't be committed but I think in whiteboards that can be up to the
>> whiteboard area 'owner&#x
or some Flash Builder users it leaves
useless files behind for people that don't use Flash Builder. I think
those shouldn't be committed but I think in whiteboards that can be up
to the whiteboard area 'owner' so to speak.
I would not want to see anything like that in a
On 4/6/2012 8:04 PM, Left Right wrote:
I have no idea what the "Apache" way is regarding this. But,
checking in the Flash Builder /Eclipse project files will make
it insanely easy for anyone--who uses Flash Builder--to share
the project. They just "import proje
h Builder users it leaves
useless files behind for people that don't use Flash Builder. I think those
shouldn't be committed but I think in whiteboards that can be up to the
whiteboard area 'owner' so to speak.
-omar
>
> I have no idea what the "Apache" way is regarding this. But, checking in
>> the Flash Builder /Eclipse project files will make it insanely easy for
>> anyone--who uses Flash Builder--to share the project. They just "import
>> projects from another workspace" and it works. It's much easier t
sake
of making sure they can be manipulated.
I did that. and they all moved w/o issues. I'm trying again with a
brand new checkout of the whiteboard, then adding my new stuff in; then
seeing if that'll work.
I would of course, suspect Eclipse to lock it's workspace settings
I had this error happen to me before many times when using Surefire reports
(with Maven builds). It used to locks files, but it can be just any other
program not closing pipes to open files.
So, can you try to move all staged files elsewhere, just for the sake of
making sure they can be manipulated
On 4/6/2012 1:42 PM, Left Right wrote:
Are you sure the error is not on your end?
No, I'm not.
All files staged are accessible (read permissions, not locked, not in
the read-only fs)?
Correct; all the files I was trying to commit should be accessible
without issues.
--
Jeffry Houser
Te
Are you sure the error is not on your end? All files staged are accessible
(read permissions, not locked, not in the read-only fs)?
Best.
Oleg
On 4/6/2012 12:44 PM, Alex Harui wrote:
You are using https?
Yes!
On 4/6/12 9:30 AM, "Jeffry Houser" wrote:
I'm not quite sure if this problem is my fault or something else is
going on; but I'm trying to commit something to my whiteboard area; and
a few files i
You are using https?
On 4/6/12 9:30 AM, "Jeffry Houser" wrote:
>
> I'm not quite sure if this problem is my fault or something else is
> going on; but I'm trying to commit something to my whiteboard area; and
> a few files in I got a "Generic I/O Error&
I'm not quite sure if this problem is my fault or something else is
going on; but I'm trying to commit something to my whiteboard area; and
a few files in I got a "Generic I/O Error" and I'm at a complete loss
what to do next.
A little background:
1) I'm co
On 4/3/12 4 :43AM, "Justin Mclean" wrote:
>Hi,
>
>Basically using the contrib library made the ant script easier to write
>and understand. I do agree as you pointed out that was at a cost to
>people who want to compile the SDK.
>
>The patch you supplied does fix this issue but the contrib lib i
Hi,
> committers (who want to test the change to the code before committing it).
It will need to wait until the modules code is committed into the trunk (which
hopefully will occur this weekend).
Once that happens I'll take a look at the patch and applying it to the patches
branch.
Thanks,
Ju
>
> The patch you supplied does fix this issue but the contrib lib is also
> required for Mustella. Perhaps it's best to wait until that donated and
> then see how the build scripts can be improved?
>
> But Mustella isn't included in the SDK yet, it's only needed for
committers (who want to test th
Hi,
Basically using the contrib library made the ant script easier to write and
understand. I do agree as you pointed out that was at a cost to people who want
to compile the SDK.
The patch you supplied does fix this issue but the contrib lib is also required
for Mustella. Perhaps it's best to
Oh, come on, seriously... there are people doing (or wanting to do) a Maven
build - let them staff their build with gigabytes of nonsense, please,
don't do it in the basic setup... Remember an old man who liked to shave so
much he was known for his razor? What's redundant is wrong. This particular
Hi,
> hmm, why the ant contrib can not be in something like i.e. ant.lib
> subdirectory?
Binary files should only be included if there's no other option I believe
(although I'm not 100% sure on the "official" rules).
However the ant script could download and install the ant contrib jar file to
hmm, why the ant contrib can not be in something like i.e. ant.lib
subdirectory? it is from apache with (i suppose) compatible license?
if we add it to the ant file it will not require additional
configuration / copying to the ant. It can be included at runtime
without knowledge / configuration, us
Hi,
Perhaps the Ant Script could download/install the ANT contrib and/or echo
instructions for doing so?
Thanks,
Justin
> Also mustella requires ant-contrib. I think ant-contrib
> should just be documented as part of the required software (which sorry I
> missed since I've had ant installed for so long).
>
> Also the formatting in the patch you submitted is messed up. Each indent
> should be 4 spaces. It looks l
I'm not sure I agree with this. While the script does work, it is much
harder to read. Also mustella requires ant-contrib. I think ant-contrib
should just be documented as part of the required software (which sorry I
missed since I've had ant installed for so long).
Also the formatting in the p
https://issues.apache.org/jira/browse/FLEX-35 I posted the patch. It seem
to work for me.
Best.
Oleg
While we are at it, what is the convention for property names in Ant
scripts? I can find these: CAPS_LOCK_IS_HERE, names.with.dots and
sTuRdYcApS, which one should I use if I need to add a new property?
Best.
Oleg
>
>
> Oleg, if you want to see something like this get done, it is best to do it
> yourself and submit the patch.
>
> I absolutely will. Was just asking whether this was intended.
On 4/1/12 3:32 AM, "olegsivo...@gmail.com" wrote:
> Hi Justin, I understand what it's used for. I am asking that because I
> think that simplicity of compilation for others > simplicity of writing for
> the author.
> Besides, I know a lot of people who would, out of principle disallow ant
> co
Hi Justin, I understand what it's used for. I am asking that because I
think that simplicity of compilation for others > simplicity of writing for
the author.
Besides, I know a lot of people who would, out of principle disallow ant
contrib libraries. And I quite share their viewpoint. Compilation s
Hi,
> Was this conrib library inherited or added on purpose? I'd rather we loose
> it. It's not required really.
It's needed for the if ant task which is used in the download ant script. While
it possible to write conditional ant tasks without it it makes them much
simpler and easier to underst
Was this conrib library inherited or added on purpose? I'd rather we loose
it. It's not required really.
Best.
Oleg
>Just a note to anyone trying to compiling that the download.xml script uses
>the ant task which is not part of the standard ant install.
>You'll need to get it form here:
>http://sourceforge.net/projects/ant-contrib/files/ant-contrib/ant-contrib-1.0b2/
Also on windows, it is best to run these
Hi,
Just a note to anyone trying to compiling that the download.xml script uses the
ant task which is not part of the standard ant install.
You'll need to get it form here:
http://sourceforge.net/projects/ant-contrib/files/ant-contrib/ant-contrib-1.0b2/
On OSX you need to download the file and
Although Alex got the signed software grant from Adobe to Apache on Friday it
was not recorded so infra can not load the dump file this weekend. I just
added the files that are in the dumpfile to my whiteboard area:
https://svn.apache.org/repos/asf/incubator/flex/whiteboard/cframpton/trunk
I
Hi,
I think Ok is usually OK even in German :-)
Justin
vate in asdoc for private
>> functions. This isn't necessary. Internally, we only recently dropped
>> the requirement to have @private on private functions so most of the
>>code
>> still has those tags.
>>
>>
>> Carol
>>
>> On 3/15/12 5 :02PM, &qu
hose tags.
>
>
> Carol
>
> On 3/15/12 5 :02PM, "JP Bader" wrote:
>
>>I was reviewing some of Tink's code in the whiteboard and I have
>>questions about why the comments say private, but the setter methods
>>are public. Is this a coding convention that I
te on private functions so most of the code
still has those tags.
Carol
On 3/15/12 5 :02PM, "JP Bader" wrote:
>I was reviewing some of Tink's code in the whiteboard and I have
>questions about why the comments say private, but the setter methods
>are public. Is this a co
I refactored it to use the resource manager so that others can add their
own locales :) I'm only half-compentent in engrish anyway ;)
I will apply your patch on this thread. To others -- please feel free to
add resource bundles to this whiteboard space. I'm not going to be
ch
anged Ok to OK which I believe is how it is normally written
### Eclipse Workspace Patch 1.0
#P Apache Flex SVN
Index: whiteboard/quetwo/MobileAlert/locale/en_AU/MobileAlert.properties
===
--- whiteboard/quetwo/MobileAlert/locale/
Hi,
>incubator/flex/whiteboard/quetwo/MobileAlert/locale/en_US/
>
> incubator/flex/whiteboard/quetwo/MobileAlert/locale/en_US/MobileAlert.properties
Would it be rude to commit an en_AU locale into your whiteboard area? (It's
identical to the US one BTW)
Justin
can contain
additional text along with the@private tag, which is also excluded from the
output.
It allows comments to be included that shouldn't be exposed to any
documentation.
On Thu, Mar 15, 2012 at 2:02 PM, JP Bader wrote:
> I was reviewing some of Tink's code in the whiteboa
I was reviewing some of Tink's code in the whiteboard and I have
questions about why the comments say private, but the setter methods
are public. Is this a coding convention that I'm just not aware of?
For example, ViewGroup, line 70, private, but method is public.
Regards,
JP
On W
Agree with that!
Good job Tink!
On Tue, Mar 13, 2012 at 12:56 PM, Arnoud Bos wrote:
>
> Hi Tink,
>
> Your layouts / navigators are of great value! So consider this as interest
> :-)
> Maybe because they just work and people can grab them from the whiteboard
> there is not much feedback.
>
>
Original Message
> From: "Arnoud Bos"
>
> Hi Tink,
>
> Your layouts / navigators are of great value! So consider this as interest :-)
> Maybe because they just work and people can grab them from the whiteboard
> there is not much feedback.
Inter
Tink,
Love your stuff as well.
I'm working on a respons to your idea about step-scrolling-layouts. Just trying
to find the time (and the brains) to do it in code.
Keep up the good work!
/E
>
> Hi Tink,
>
> Your layouts / navigators are of great value! So consider this as interest
> :-)
> Maybe because they just work and people can grab them from the whiteboard
> there is not much feedback.
>
> Looks to me like some really well architectured code wi
Hi Tink,
Your layouts / navigators are of great value! So consider this as interest :-)
Maybe because they just work and people can grab them from the whiteboard
there is not much feedback.
Looks to me like some really well architectured code with good documentation and
examples and definitely
On Thu, Mar 1, 2012 at 11:57, Carol Frampton wrote:
>
> On 2/29/12 10 :20PM, "Rafael Santos" wrote:
>
> >As long as I can remember Spark does not cover every component that exist
> >on mx. Many components were left behind (ViewStack, Accordion, LinkButton
> >and many others).
> >
> >Rafael Santo
On 2/29/12 10 :20PM, "Rafael Santos" wrote:
>As long as I can remember Spark does not cover every component that exist
>on mx. Many components were left behind (ViewStack, Accordion, LinkButton
>and many others).
>
>Rafael Santos - Specta
Only because we didn't get to those. The intent was to
2012/3/1 Jarosław Szczepankiewicz
> 4.9 ? and where is 4.7 and 4.8 ;)
>
> https://cwiki.apache.org/confluence/display/FLEX/Decisions+so+far
4.9 ? and where is 4.7 and 4.8 ;)
2012/3/1 Rafael Santos :
> Maybe we can consider this as minor changes for version 4.9 ?
>
> I will work with you on that.
>
> Rafael Santos - Specta
> On Mar 1, 2012 5:55 AM, "Omar Gonzalez" wrote:
>
>> On Thu, Mar 1, 2012 at 12:53 AM, Carlos Rovira <
>> carlos.
Maybe we can consider this as minor changes for version 4.9 ?
I will work with you on that.
Rafael Santos - Specta
On Mar 1, 2012 5:55 AM, "Omar Gonzalez" wrote:
> On Thu, Mar 1, 2012 at 12:53 AM, Carlos Rovira <
> carlos.rov...@codeoscopic.com> wrote:
>
> > Take into account that s:Accordion,
On Thu, Mar 1, 2012 at 12:53 AM, Carlos Rovira <
carlos.rov...@codeoscopic.com> wrote:
> Take into account that s:Accordion, s:ViewStack are already done by Adobe
> and are part of the donation
>
Until I see code in our repository I will keep the status on that wiki page
as MISSING. Right now its
enderer
> I agree with you for the others.
> Matt
>
> -Message d'origine-
> De : Rafael Santos [mailto:rsan...@spectacompany.com.br]
> Envoyé : jeudi 1 mars 2012 04:44
> À : flex-dev@incubator.apache.org
> Objet : Re: Missing Spark components (was: Re: svn comm
12 04:44
À : flex-dev@incubator.apache.org
Objet : Re: Missing Spark components (was: Re: svn commit: r1295396 - in
/incubator/flex/whiteboard/jmclean/validators: ./ src/ src/mx/ src/mx/core/
src/mx/core/Version.as src/mx/validators/
src/mx/validators/PostCodeValidator.as src/tests/ src/tests/PostC
On Thu, Mar 1, 2012 at 00:31, Omar Gonzalez wrote:
> On Wed, Feb 29, 2012 at 7:20 PM, Rafael Santos <
> rsan...@spectacompany.com.br
> > wrote:
>
> > As long as I can remember Spark does not cover every component that exist
> > on mx. Many components were left behind (ViewStack, Accordion, LinkBut
On Wed, Feb 29, 2012 at 7:20 PM, Rafael Santos wrote:
> As long as I can remember Spark does not cover every component that exist
> on mx. Many components were left behind (ViewStack, Accordion, LinkButton
> and many others).
>
> Rafael Santos - Specta
>
True, I've just been using Spark componen
As long as I can remember Spark does not cover every component that exist
on mx. Many components were left behind (ViewStack, Accordion, LinkButton
and many others).
Rafael Santos - Specta
On Thu, Mar 1, 2012 at 00:17, Justin Mclean wrote:
> Hi,
>
> > Out of curiosity, is there a reason you cho
Flex 3.6 or Flex 4.x mixed mx and spark applications about.
>
True, maybe I'll make an MX version of the ConfirmStringValidator I put in
my whiteboard.
>
> There still nothing in Spark that's similar to mx:Form right?
>
There is a s:Form now since 4.5 I believe.
>
>
Hi,
> Out of curiosity, is there a reason you chose to make it an MX based
> Validator as opposed to a Spark validator?
I find a lot of people still use mx components, there are still a fair number
of Flex 3.6 or Flex 4.x mixed mx and spark applications about.
There still nothing in Spark that'
Hi Justin,
Out of curiosity, is there a reason you chose to make it an MX based
Validator as opposed to a Spark validator?
--
Omar Gonzalez
s9tpep...@apache.org
Apache Flex PPMC Member
> I mean add-on / extension. https://addons.mozilla.org/en-US/firefox/
>
> Not every browser supports add-ons either tho. What I was thinking was a
> sidebar that showed something like the package explorer or even an
> extension that took, "http://localhost/my_application.mxml"; and ran mxmlc
> on
I mean add-on / extension. https://addons.mozilla.org/en-US/firefox/
Not every browser supports add-ons either tho. What I was thinking was a
sidebar that showed something like the package explorer or even an
extension that took, "http://localhost/my_application.mxml"; and ran mxmlc
on it (which t
On 2/20/12 1:09 AM, "jude" wrote:
> What about a browser plug in that would handle .mxml files? Then you'd just
> drag and drop an MXML file to the browser and it would render?
It is the fact that certain browsers don't support plug-ins that put us in
this situation in the first place.
--
Al
On 21/02/2012 01:52, David Francis Buhler wrote:
Google's Dart is gaining traction and is now offered as a browser plug-in
(for Chrome).
[1]
http://news.cnet.com/8301-30685_3-57380050-264/googles-dart-language-arrives-in-chrome-test-version/
There are strong discussions against dart in a release
Google's Dart is gaining traction and is now offered as a browser plug-in
(for Chrome).
[1]
http://news.cnet.com/8301-30685_3-57380050-264/googles-dart-language-arrives-in-chrome-test-version/
On Mon, Feb 20, 2012 at 4:42 AM, ganaraj p r wrote:
> If browser plugins were a future we would be wo
Let me rephrase, I mean Firefox Add-on.
On Mon, Feb 20, 2012 at 3:42 AM, ganaraj p r wrote:
> If browser plugins were a future we would be worrying quite a bit about
> releasing Flex 4.7 or Flex 5. The problem is, the most popular plugin in
> the world seems to have a hazy future, which is proba
If browser plugins were a future we would be worrying quite a bit about
releasing Flex 4.7 or Flex 5. The problem is, the most popular plugin in
the world seems to have a hazy future, which is probably the reason for all
the discussion about moving away from Flash.
On Mon, Feb 20, 2012 at 9:09 AM
The ease of making HTML pages was partly what hooked me so long ago. I
could type something in a text editor and it would show up rendered in the
browser.
What about a browser plug in that would handle .mxml files? Then you'd just
drag and drop an MXML file to the browser and it would render?
Jud
I was working on something like an AspectJ implementation ...
Compile-time-AOP has the obvious problem that you can not load an
additional library at runtime into a container. That is one of the main
reason for the popularity of spring in java - it offered reasonably fast
AOP at runtime tha
l A. Labriola
Sent: Tuesday, February 07, 2012 1:35 AM
To: flex-dev@incubator.apache.org
Subject: RE: Starting with the Whiteboard Code
>> Writing unit tests for the framework is something that could be
>>started now. The framework code is out there.
>>Are the other ones logical te
incubator.apache.org
Sent: Friday, February 10, 2012 9:07 AM
Subject: Re: [RT] Awesome FlexNext User Experience (was: Starting with the
Whiteboard code)
Agreed. One of the things we need to also demonstrate is the ease of
development concept, something that David pointed out with Sencha, Go
and e
@yahoo.com
>> Phone: 650-690-2213
>> Fax: 650-641-0031
>> Cell: 650-823-8699
>>
>>
>>
>> From: JP Bader
>> To: flex-dev@incubator.apache.org
>> Sent: Friday, February 10, 2012 9:07 AM
>> Subject: Re: [RT]
, 2012 9:07 AM
> Subject: Re: [RT] Awesome FlexNext User Experience (was: Starting with the
> Whiteboard code)
>
> Agreed. One of the things we need to also demonstrate is the ease of
> development concept, something that David pointed out with Sencha, Go
> and even tryruby.org. An
031
Cell: 650-823-8699
From: JP Bader
To: flex-dev@incubator.apache.org
Sent: Friday, February 10, 2012 9:07 AM
Subject: Re: [RT] Awesome FlexNext User Experience (was: Starting with the
Whiteboard code)
Agreed. One of the things we need to also demonstrate
To: flex-dev@incubator.apache.org
Sent: Friday, February 10, 2012 9:02 AM
Subject: Re: [RT] Awesome FlexNext User Experience (was: Starting with the
Whiteboard code)
I'd also like to see a showcase of applications developed that not only
inspire developers as to what's possible, but p
: Friday, February 10, 2012 8:23 AM
Subject: Re: [RT] Awesome FlexNext User Experience (was: Starting with the
Whiteboard code)
I'd like to see the examples and documentation be part of an improved,
cohesive 'brand' outlined. The rest of the outline I agree with.
Someone else had
Agreed. One of the things we need to also demonstrate is the ease of
development concept, something that David pointed out with Sencha, Go
and even tryruby.org. An interactive tutorial would be great for
getting Apache Flex out to the masses for ease of use, and examples
should be focused on curr
On 11/02/2012 01:56, Haykel BEN JEMIA wrote:
Nice proposal Mike. Regarding 'Fully portable', is that not just a matter
of skinning or are you thinking about more?
Haykel
The word "Skin" has certain restrictions in the current Flex model which
is why I tried to avoid it.
I am talking about rule
I'd also like to see a showcase of applications developed that not only
inspire developers as to what's possible, but provide useful code either
for developers creating proof or concepts for internal approval or as
starting code for actual projects.
This would not be a tour de flex, but rather a n
Nice proposal Mike. Regarding 'Fully portable', is that not just a matter
of skinning or are you thinking about more?
Haykel
On 10 February 2012 17:00, Martin Heidegger wrote:
> Dear List,
>
> it can be hard to find a vision for the next version of Flex. Developers
> like us like discussions
I'd like to see the examples and documentation be part of an improved,
cohesive 'brand' outlined. The rest of the outline I agree with.
Someone else had suggested the idea of emulating the
examples/documentation Sencha/JQuery use, which I second. Likewise,
Google does an excellent job with http:/
> Date: Sat, 11 Feb 2012 01:00:16 +0900
> From: m...@leichtgewicht.at
> To: flex-dev@incubator.apache.org
> Subject: [RT] Awesome FlexNext User Experience (was: Starting with the
> Whiteboard code)
>
> Dear List,
>
> it can be hard to find a vision for the next
I am completely up for this. I vote for doing something along this line...
On Fri, Feb 10, 2012 at 4:00 PM, Martin Heidegger wrote:
> Dear List,
>
> it can be hard to find a vision for the next version of Flex. Developers
> like us like discussions about technical details and they are boring.
>
>
Dear List,
it can be hard to find a vision for the next version of Flex. Developers
like us like discussions about technical details and they are boring.
I think that is not enough! I think we need something that inspires us
to create something new - something that makes us believe that the
W dniu 2012-02-09 19:52, Martin Heidegger pisze:
1) A framework that produces awesome(in other words new!) experiences:
Great design, super interactivity. Its enough if they are published
like minimalcomps: without CSS or anything. Just so people see Apache
Flex is coll and they want that o
On 10/02/2012 05:05, Michael A. Labriola wrote:
DI in flex isn't a hard problem. It's actually pretty trivial. There are just a
few places where the Flex compiler hard-codes new operators without an ability
to intercept the object creation. After those lines of code are fixed (and it
is a very
>>I totally agree: Lets take all the momentum we have got! It sounded like you
>>have an concept of how you would see DI in Flex Next. It would be nice if you
>>could write the important bits and pieces down in the wiki >>so we have
>>something to talk about!
DI in flex isn't a hard problem. It
1 - 100 of 184 matches
Mail list logo
