Quoting Stakesoft <m...@stakesoft.com>:
That's all very well but (DV aside) FB is far better and we are used
to it. It's not very useful to run 2 IDE's alongside otherwise we
could use FB4.6 and FB4.7 nor is it a forward step to use a
different IDE.
Wanting another IDE to get better just because the Adobe one has
just got worse is sole destroying, as is spending good time and
money on an IDE that's now going to be of little use. I don't want
to get into a rant, I'd rather be constructive.
Is Apache at least sympathetic towards this, does Adobe care about
this. Is there any hope at all?
Nigel
Being a committer I can say I totally understand what you are saying
about DV. I to am a visual person, although I never used DV that much
since I wrote more AS component type things, I can understand how it
would be included in design workflow.
The problem I see is just what you said, IDE, which one, don't want to
switch. Lets say I have the experience to start a project like this.
What IDE do I target? IDEA and Eclipse are two large IDEs with a huge
difference in plugin API.
Bam, I'm already dead in my tracks. Maintaining one code base for one
IDE is one thing but to maintain two, yeah right.
Wait lets do AIR, oh but 50%+ devs would only use an "IDE Plugin", so
then you only get half support for using a half baked AIR
implementation.
I see no real solution to this. Now lets add the fact we have to
incorporate the FlashPlayer in DV, you want dnd, haha that takes the
difficulty of coding 5 levels higher.
As a developer, I'm sure a lot are not speaking up on this subject
because our hands are tied, there is really no answer to this.
Mike
-----Original Message-----
From: charles.monte...@gmail.com [mailto:charles.monte...@gmail.com]
On Behalf Of Charles Monteiro
Sent: 02 October 2012 18:11
To: flex-dev@incubator.apache.org; apache-f...@bentbit.com
Subject: Re: Apache Flex GUI Designer tools
If that's all you need I would again check out Intellij IDEA Flash design
viewer plugin, that's exactly what it does, it even allows for configuring
of attributes though selecting the correct entity is buggy, doing a
"preview" is not
On Tue, Oct 2, 2012 at 1:04 PM, BentBit Apache-Flex <apache-f...@bentbit.com
wrote:
Hello,
I use design view to "preview" elements of my Flash Builder
project. Previewing makes the design workflow much faster because I can
see how the project is going to look. I rarely rely on design view to make
actual changes to my projects because it is slow and unreliable.
Would it be possible to develop some sort of a preview that would
function for Apache Flex and Adobe Flex? I am not worried about losing
design view, just the preview capability.
Best,
-Blake
-----Original Message-----
From: Stakesoft [mailto:m...@stakesoft.com]
Sent: Tuesday, October 02, 2012 10:32 AM
To: flex-dev@incubator.apache.org
Subject: RE: Apache Flex GUI Designer tools
Technical issues aside I suspect there a good few of us that rely on
design views (and we are not all noobs). Many are supporting not having a
DV as they don't use it and that's fine for them but a bit of a disaster
for others. There are IDE's with DV's and those without - the best in my
mind all have a DV.
If Adobe are not taking care of the SDK or the DV it leaves much less
advantage over other free software.
Non DV developers at Adobe please try and understand how important a DV is
to the many who use it. I wish 4.7 onwards all the best but it will just
about unusable for me.
Nigel
-----Original Message-----
From: Alex Harui [mailto:aha...@adobe.com]
Sent: 02 October 2012 17:12
To: flex-dev@incubator.apache.org
Subject: Re: Apache Flex GUI Designer tools
On 10/2/12 8:55 AM, "Sebastian Mohr" <masul...@gmail.com> wrote:
>
> @Adobe ... what's wrong with continuing building GUI
> designer tools for Apache Flex? Is that really something
> that is not worth investing into? You already created those
> tools. So, why not sharing some of your expertise with the
> community, and, not locking your code in the archives of
> Adobe history?
>
This has been discussed before. Design View is highly dependent on a Flex
SDK version. It is not practical for Adobe to maintain DV in FB now that
SDKs are coming from Apache.
I think the DV code is flawed for that reason and some others. It is
probably better to simply start over. AFAIK, it is "just" an Eclipse
plug-in.
If figuring out some aspect of the plug-in turns out to be difficult, I
can
try to see if there are some pieces we could donate, but the assessment
from
the owners of the code is that there isn't much that is re-usable.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
--
Charles A. Monteiro
www.monteirosfusion.com
sent from the road
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
