You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by "Justin M. Hill" <Ju...@Prominic.NET> on 2014/09/23 06:02:43 UTC
Public campaign to improve FlashDevelop specificall for Apache Flex
Apache Flex Team,
I attended the Flex 360 conference with many of you earlier this year in
San Jose. While I do not follow the list daily, I know you are all working
very hard and we appreciate it very much.
One of the most important things Apache Flex needs to succeed is a 100%
free, easy to use, cross platform IDE which runs on Mac, Linux, and
Windows. Obviously Flash Builder, FDT, and IntelliJ are all options
already.
When I started to evaluate the next investment we would make in IDE tooling
post-Adobe, I came across this comparison:
http://www.simtechmedia.com/blog/2010/10/ide-showdown-intellij-fdt-flashdevelop-2/
This in turn got me interested in FlashDevelop. Even though it was
Windows-only, I decided to work with my contacts at
https://www.codeweavers.com (a commercial support company for WINE) to get
it working under our standard development platform: Mac.
In a relatively short period of time, I was able to get FlashDevelop to
work on Mac. I then made a nominal donation to Mika (one of the
FlashDevelop project leads) to alert him to this breakthrough and encourage
him to spend time testing on Mac. He also found it to be mostly a success.
Mika then went on to create a CrossTie installer which makes it easier for
other users to install FlashDevelop on Mac and Linux using CrossOver.
[Side note for Mac and Linux users: I realize CrossOver is commercial and
if it is a dependency for FlashDevelop on Mac and Linux, it is not totally
free on those platforms. I am not concerned with that and hope the topic
does not steer in that direction.]
I then asked Santanu, Walker, and Joel to review Flash Builder compared to
FlashDevelop on Mac to determine what else needs to make FlashDevelop an
acceptable replacement for Flash Builder. Santanu produced a PDF which I
will ask him to reply to this message in text form with the contents of the
PDF in a text readable fashion so that it is readable on the mailing list.
I asked Mika to commit to a full test of all FlashDevelop features on Mac,
including Flash player debugging, compiling, Apache Flex installer testing,
etc. He then put me in contact with Hector who he indicated may have more
time and had already started a campaign to raise funds to enable him to
dedicated more time to improve FlashDevelop for Flex:
https://www.linkedin.com/groupItem?view=&gid=4296888&type=member&item=5905327257437630464&commentID=5920018570217009152&report%2Esuccess=8ULbKyXO6NDvmoK7o030UNOYGZKrvdhBhypZ_w8EpQrrQI-BBjkmxwkEOwBjLE28YyDIxcyEO7_TA_giuRN#commentID_5920018570217009152
https://www.indiegogo.com/projects/flashdevelop-improved-flex-support
There is at least one other commercial entity set to help Hector meet his
fundraising goals. Between the other company and Prominic, along with
anyone else who can help, we can and will make FlashDevelop better for
Flex. We need to see it better specifically on Mac as well, and I would
like to ask other Mac users out there in the Flex world to participate now
in defining exactly what goals we need Hector to achieve.
Please categorize these into at least two different areas.
A) Making FlashDevelop great for Apache Flex
B) Making FlashDevelop great for Apache Flex under Mac and Linux using
CrossOver.
I envision FlashDevelop having an integrated Apache Flex installation
process that works without the confusion of the current one which offers
too many different downloads. I would like to see a launch page that
makes it very easy to get started with your first Flex project.
Similarly, a start page might also be appropriate for those interested in
FeathersUI or pure Flash work. Right now everything is assumed that the
user will know how to create a project for their preferred target, and that
is not as intuitive as it should be.
I would also like to see better import support for Flash Builder projects,
and thorough testing of the integrated Flash Player with debug mode enabled
under CrossOver, or possibly integrated with running the Mac version of the
debug player.
Santanu, please reply with your specific list of requests.
Hector, please integrate Santanu's request into your master list and reply
back as well.
I welcome anyone else who can provide concrete direction for the goal list.
The last revision I had from Hector on September 17, 2014 is as follows:
1. package: Code Completion and MXML
1. Code completion bugfixes: there are some bugs in code completion.
ie.: sometimes it forgets the inherited properties until I open the
base class.
2. Replace file bugfixes: there are extreme bugs when I try to replace
a file or a folder, and FD updates the namespaces. Sometimes it
deletes codes and replaces wrong texts. It’s very dangerous, but it
would be very useful.
3. Custom mxml component code completion support in AS files: FD should
support not only native, but custom MXML components. It partly have
code completion when we use an mxml class in AS files, but mostly
inherited properties and functions are disappear.
4. Mxml generation: Code generation (like class generation) and
completion during editing MXML files.
5. Manifest support: You can define custom manifest files, where can
describe for flex compiler the names and class paths (ie: <component
id="Text" class="com.ui.controls.Text"/>). We would like a native
support for these files.
6. Code navigation inside mxml: With F4 FD should jump to the inherited
property as in native AS files.
7. Relative path support inside custom configs: we use custom configs,
for defining our custom flex mxml manifest files, but the Flex SDK
requires absolute path-s (or at least relative to mxmlc compiler). We
would need a path support like in template generation (ie.: $
(ProjectPath) )
2. package: RSL and SWC
1. Real RSL support: right now it has config in the project settings for
RSL, but it was impossible to make it work. Right now I can use it
with additional compiler options, but it’s really difficult to
disable-enable it all the time.
2. SWC generation support: there is already a plugin, but it’s very
limited and have a lot of bugs. It should also have the possibility
for selectable generation, like in Flash Builder.
3. Support for RSL generation: native support for generate RSL files
from generated SWC. (it most be unzipped, optimized with the Flex
optimizer, and signed)
3. package: FlexUnit
1. Flex unit support: native support for FlexUnit testing. It should
show the test results and detailed informations about the where did
the test break.
4. package: Debugging
1. Breakpoint stack filter: sometimes there is a huge list in breakpoint
stack, and it would be great to have a filter in this list by
keywords (positive and negative). Filter also should support regexp
and escaped characters.
2. Visual debugger, inspector (similar to firebug): it would be great to
have a live inspector like in firebug. Inspect the DisplayObject
tree, jump on the tree with I mouse click (like inspect in FireBug),
live change the properties of any class (right now there is something
like this, but it’s not enough user friendly)
3. Profiler improvements: in Flash Builder there are some nice features
in the profiler that would be also great in FD.
4. Flex state handling: native code completion support for Flex States.
5. package: UI improvements
1. Intelligent CTRL+C and CTRL+V: after width = exactWidth ctrl+v
generates height = exactHeight. For sure it should have a different
shortcut like CTRL+ALT+V and CTRL+ALT+C or something like that.
2. Interface generation from code: sometimes we create code before the
interface, so we would need a plugin, that generates interface from
code.
3. Crl+click navigate support: it should do the same as F4. It’s a very
nice feature in a FD plugin, and sometimes it’s very handy.
4. Ignore whitespaces search: in every search there should be a checkbox
to ignore whitespaces. So if it’s enabled it would search for myVar =
", when the code is myVar =
"something".
5. Negative filter in search: we could specify a negative filter for the
search. So for example I want to find every SampleVO string, but only
in those classes where there is no SomethingVO. Like in google the
negative filter (ie: flash RSL –adobe)
6. package: Mercurial HG
1. Real HG support: it would be great to have an integrated HG Mercurial
support like in PHP storm
Thank you,
Justin Hill
http://Prominic.NET
Skype: JustinProminic
https://twitter.com/JustinProminic
https://www.linkedin.com/in/justinprominic
Re: Public campaign to improve FlashDevelop specificall for Apache Flex
Posted by jude <fl...@gmail.com>.
Justin,
I agree that the lack of a free Flex IDE for Mac and Linux is a barrier for
new Flex developers. If one were available, they could get started and
later on they will have the option to upgrade to other IDE's.
One thing we may want to consider is adding a simple mxmlc compiler into
the Apache Installer which is one step better than the command line. You
pick the application in a open file dialog and it compiles or doesn't
(super simple).
Or it may be better as a separate program. Just something to create a
sample project and directory and then compile and run the application in
it. I would say install it with the installer. At the same time we provide
links to the Flex IDE's including FD.
Anyway, I would say get feature parity with FB first with what the
developer works in the most (the code editor).
1. So focus on nearly all the options in 1. package Code Completion
2. Next work on 5. package UI improvements
3. The next isn't on the list but a screen that has templates and demo
projects for new users to get started. You described this in your initial
email.
4. Add support to Import FB projects
5. Make the Mac and Linux versions as seamless as possible to those
platforms. Make it feel like a real Mac or Linux program if that makes
sense.
Jude
On Mon, Sep 22, 2014 at 11:02 PM, Justin M. Hill <Ju...@prominic.net>
wrote:
>
> Apache Flex Team,
>
> I attended the Flex 360 conference with many of you earlier this year in
> San Jose. While I do not follow the list daily, I know you are all working
> very hard and we appreciate it very much.
>
>
> One of the most important things Apache Flex needs to succeed is a 100%
> free, easy to use, cross platform IDE which runs on Mac, Linux, and
> Windows. Obviously Flash Builder, FDT, and IntelliJ are all options
> already.
>
> When I started to evaluate the next investment we would make in IDE tooling
> post-Adobe, I came across this comparison:
>
>
> http://www.simtechmedia.com/blog/2010/10/ide-showdown-intellij-fdt-flashdevelop-2/
>
> This in turn got me interested in FlashDevelop. Even though it was
> Windows-only, I decided to work with my contacts at
> https://www.codeweavers.com (a commercial support company for WINE) to get
> it working under our standard development platform: Mac.
>
> In a relatively short period of time, I was able to get FlashDevelop to
> work on Mac. I then made a nominal donation to Mika (one of the
> FlashDevelop project leads) to alert him to this breakthrough and encourage
> him to spend time testing on Mac. He also found it to be mostly a success.
> Mika then went on to create a CrossTie installer which makes it easier for
> other users to install FlashDevelop on Mac and Linux using CrossOver.
>
> [Side note for Mac and Linux users: I realize CrossOver is commercial and
> if it is a dependency for FlashDevelop on Mac and Linux, it is not totally
> free on those platforms. I am not concerned with that and hope the topic
> does not steer in that direction.]
>
> I then asked Santanu, Walker, and Joel to review Flash Builder compared to
> FlashDevelop on Mac to determine what else needs to make FlashDevelop an
> acceptable replacement for Flash Builder. Santanu produced a PDF which I
> will ask him to reply to this message in text form with the contents of the
> PDF in a text readable fashion so that it is readable on the mailing list.
>
> I asked Mika to commit to a full test of all FlashDevelop features on Mac,
> including Flash player debugging, compiling, Apache Flex installer testing,
> etc. He then put me in contact with Hector who he indicated may have more
> time and had already started a campaign to raise funds to enable him to
> dedicated more time to improve FlashDevelop for Flex:
>
>
> https://www.linkedin.com/groupItem?view=&gid=4296888&type=member&item=5905327257437630464&commentID=5920018570217009152&report%2Esuccess=8ULbKyXO6NDvmoK7o030UNOYGZKrvdhBhypZ_w8EpQrrQI-BBjkmxwkEOwBjLE28YyDIxcyEO7_TA_giuRN#commentID_5920018570217009152
>
> https://www.indiegogo.com/projects/flashdevelop-improved-flex-support
>
>
> There is at least one other commercial entity set to help Hector meet his
> fundraising goals. Between the other company and Prominic, along with
> anyone else who can help, we can and will make FlashDevelop better for
> Flex. We need to see it better specifically on Mac as well, and I would
> like to ask other Mac users out there in the Flex world to participate now
> in defining exactly what goals we need Hector to achieve.
>
> Please categorize these into at least two different areas.
> A) Making FlashDevelop great for Apache Flex
>
> B) Making FlashDevelop great for Apache Flex under Mac and Linux using
> CrossOver.
>
>
> I envision FlashDevelop having an integrated Apache Flex installation
> process that works without the confusion of the current one which offers
> too many different downloads. I would like to see a launch page that
> makes it very easy to get started with your first Flex project.
> Similarly, a start page might also be appropriate for those interested in
> FeathersUI or pure Flash work. Right now everything is assumed that the
> user will know how to create a project for their preferred target, and that
> is not as intuitive as it should be.
>
> I would also like to see better import support for Flash Builder projects,
> and thorough testing of the integrated Flash Player with debug mode enabled
> under CrossOver, or possibly integrated with running the Mac version of the
> debug player.
>
> Santanu, please reply with your specific list of requests.
> Hector, please integrate Santanu's request into your master list and reply
> back as well.
>
> I welcome anyone else who can provide concrete direction for the goal list.
> The last revision I had from Hector on September 17, 2014 is as follows:
>
> 1. package: Code Completion and MXML
> 1. Code completion bugfixes: there are some bugs in code completion.
> ie.: sometimes it forgets the inherited properties until I open the
> base class.
> 2. Replace file bugfixes: there are extreme bugs when I try to
> replace
> a file or a folder, and FD updates the namespaces. Sometimes it
> deletes codes and replaces wrong texts. It’s very dangerous, but it
> would be very useful.
> 3. Custom mxml component code completion support in AS files: FD
> should
> support not only native, but custom MXML components. It partly have
> code completion when we use an mxml class in AS files, but mostly
> inherited properties and functions are disappear.
> 4. Mxml generation: Code generation (like class generation) and
> completion during editing MXML files.
> 5. Manifest support: You can define custom manifest files, where can
> describe for flex compiler the names and class paths (ie: <component
> id="Text" class="com.ui.controls.Text"/>). We would like a native
> support for these files.
> 6. Code navigation inside mxml: With F4 FD should jump to the
> inherited
> property as in native AS files.
> 7. Relative path support inside custom configs: we use custom configs,
> for defining our custom flex mxml manifest files, but the Flex SDK
> requires absolute path-s (or at least relative to mxmlc compiler). We
> would need a path support like in template generation (ie.: $
> (ProjectPath) )
>
> 2. package: RSL and SWC
> 1. Real RSL support: right now it has config in the project settings
> for
> RSL, but it was impossible to make it work. Right now I can use it
> with additional compiler options, but it’s really difficult to
> disable-enable it all the time.
> 2. SWC generation support: there is already a plugin, but it’s very
> limited and have a lot of bugs. It should also have the possibility
> for selectable generation, like in Flash Builder.
> 3. Support for RSL generation: native support for generate RSL files
> from generated SWC. (it most be unzipped, optimized with the Flex
> optimizer, and signed)
>
>
> 3. package: FlexUnit
> 1. Flex unit support: native support for FlexUnit testing. It should
> show the test results and detailed informations about the where did
> the test break.
>
>
> 4. package: Debugging
> 1. Breakpoint stack filter: sometimes there is a huge list in
> breakpoint
> stack, and it would be great to have a filter in this list by
> keywords (positive and negative). Filter also should support regexp
> and escaped characters.
> 2. Visual debugger, inspector (similar to firebug): it would be great
> to
> have a live inspector like in firebug. Inspect the DisplayObject
> tree, jump on the tree with I mouse click (like inspect in FireBug),
> live change the properties of any class (right now there is something
> like this, but it’s not enough user friendly)
> 3. Profiler improvements: in Flash Builder there are some nice
> features
> in the profiler that would be also great in FD.
> 4. Flex state handling: native code completion support for Flex
> States.
>
> 5. package: UI improvements
> 1. Intelligent CTRL+C and CTRL+V: after width = exactWidth ctrl+v
> generates height = exactHeight. For sure it should have a different
> shortcut like CTRL+ALT+V and CTRL+ALT+C or something like that.
> 2. Interface generation from code: sometimes we create code before the
> interface, so we would need a plugin, that generates interface from
> code.
> 3. Crl+click navigate support: it should do the same as F4. It’s a
> very
> nice feature in a FD plugin, and sometimes it’s very handy.
> 4. Ignore whitespaces search: in every search there should be a
> checkbox
> to ignore whitespaces. So if it’s enabled it would search for myVar =
> ", when the code is myVar =
> "something".
> 5. Negative filter in search: we could specify a negative filter for
> the
> search. So for example I want to find every SampleVO string, but only
> in those classes where there is no SomethingVO. Like in google the
> negative filter (ie: flash RSL –adobe)
>
> 6. package: Mercurial HG
> 1. Real HG support: it would be great to have an integrated HG
> Mercurial
> support like in PHP storm
>
>
>
> Thank you,
>
> Justin Hill
> http://Prominic.NET
> Skype: JustinProminic
> https://twitter.com/JustinProminic
> https://www.linkedin.com/in/justinprominic
Re: Public campaign to improve FlashDevelop specificall for Apache Flex
Posted by jude <fl...@gmail.com>.
UPDATE: Just noticed I replied only to dev and not all so replying for
those not subscribed to dev mailing list. Original email below:
Justin,
I agree. It would be great to have this. I think the lack of a free Flex
IDE for Mac and Linux is a barrier for new Flex developers. If one were
available, anyone could get started and going with Flex and later on they
will have the option to upgrade to other IDE's if they so choose.
One thing we may want to consider is adding a simple mxmlc compiler into
the Apache Installer which is one step better than the command line. You
pick the application in a open file dialog and it compiles or doesn't
(super simple).
Or it may be better as a separate program. Just something to create a
sample project and directory and then compile and run the application in
it. I would say install it with the installer. At the same time we provide
links to the Flex IDE's including FD.
Anyway, I would say focus on feature parity with FB first since that is
what the developer works in the most (the code editor).
1. So focus on nearly all the options in 1. package Code Completion
2. Next work on features in 5. package UI improvements
3. The next isn't on the list but a screen that has templates and demo
projects for new users to get started. You described this in your initial
email.
4. Add support to Import FB projects
5. Make the Mac and Linux versions as seamless as possible to those
platforms. Make it feel like a real Mac or Linux program if that makes
sense.
On Mon, Sep 22, 2014 at 11:02 PM, Justin M. Hill <Ju...@prominic.net>
wrote:
>
> Apache Flex Team,
>
> I attended the Flex 360 conference with many of you earlier this year in
> San Jose. While I do not follow the list daily, I know you are all working
> very hard and we appreciate it very much.
>
>
> One of the most important things Apache Flex needs to succeed is a 100%
> free, easy to use, cross platform IDE which runs on Mac, Linux, and
> Windows. Obviously Flash Builder, FDT, and IntelliJ are all options
> already.
>
> When I started to evaluate the next investment we would make in IDE tooling
> post-Adobe, I came across this comparison:
>
>
> http://www.simtechmedia.com/blog/2010/10/ide-showdown-intellij-fdt-flashdevelop-2/
>
> This in turn got me interested in FlashDevelop. Even though it was
> Windows-only, I decided to work with my contacts at
> https://www.codeweavers.com (a commercial support company for WINE) to get
> it working under our standard development platform: Mac.
>
> In a relatively short period of time, I was able to get FlashDevelop to
> work on Mac. I then made a nominal donation to Mika (one of the
> FlashDevelop project leads) to alert him to this breakthrough and encourage
> him to spend time testing on Mac. He also found it to be mostly a success.
> Mika then went on to create a CrossTie installer which makes it easier for
> other users to install FlashDevelop on Mac and Linux using CrossOver.
>
> [Side note for Mac and Linux users: I realize CrossOver is commercial and
> if it is a dependency for FlashDevelop on Mac and Linux, it is not totally
> free on those platforms. I am not concerned with that and hope the topic
> does not steer in that direction.]
>
> I then asked Santanu, Walker, and Joel to review Flash Builder compared to
> FlashDevelop on Mac to determine what else needs to make FlashDevelop an
> acceptable replacement for Flash Builder. Santanu produced a PDF which I
> will ask him to reply to this message in text form with the contents of the
> PDF in a text readable fashion so that it is readable on the mailing list.
>
> I asked Mika to commit to a full test of all FlashDevelop features on Mac,
> including Flash player debugging, compiling, Apache Flex installer testing,
> etc. He then put me in contact with Hector who he indicated may have more
> time and had already started a campaign to raise funds to enable him to
> dedicated more time to improve FlashDevelop for Flex:
>
>
> https://www.linkedin.com/groupItem?view=&gid=4296888&type=member&item=5905327257437630464&commentID=5920018570217009152&report%2Esuccess=8ULbKyXO6NDvmoK7o030UNOYGZKrvdhBhypZ_w8EpQrrQI-BBjkmxwkEOwBjLE28YyDIxcyEO7_TA_giuRN#commentID_5920018570217009152
>
> https://www.indiegogo.com/projects/flashdevelop-improved-flex-support
>
>
> There is at least one other commercial entity set to help Hector meet his
> fundraising goals. Between the other company and Prominic, along with
> anyone else who can help, we can and will make FlashDevelop better for
> Flex. We need to see it better specifically on Mac as well, and I would
> like to ask other Mac users out there in the Flex world to participate now
> in defining exactly what goals we need Hector to achieve.
>
> Please categorize these into at least two different areas.
> A) Making FlashDevelop great for Apache Flex
>
> B) Making FlashDevelop great for Apache Flex under Mac and Linux using
> CrossOver.
>
>
> I envision FlashDevelop having an integrated Apache Flex installation
> process that works without the confusion of the current one which offers
> too many different downloads. I would like to see a launch page that
> makes it very easy to get started with your first Flex project.
> Similarly, a start page might also be appropriate for those interested in
> FeathersUI or pure Flash work. Right now everything is assumed that the
> user will know how to create a project for their preferred target, and that
> is not as intuitive as it should be.
>
> I would also like to see better import support for Flash Builder projects,
> and thorough testing of the integrated Flash Player with debug mode enabled
> under CrossOver, or possibly integrated with running the Mac version of the
> debug player.
>
> Santanu, please reply with your specific list of requests.
> Hector, please integrate Santanu's request into your master list and reply
> back as well.
>
> I welcome anyone else who can provide concrete direction for the goal list.
> The last revision I had from Hector on September 17, 2014 is as follows:
>
> 1. package: Code Completion and MXML
> 1. Code completion bugfixes: there are some bugs in code completion.
> ie.: sometimes it forgets the inherited properties until I open the
> base class.
> 2. Replace file bugfixes: there are extreme bugs when I try to
> replace
> a file or a folder, and FD updates the namespaces. Sometimes it
> deletes codes and replaces wrong texts. It’s very dangerous, but it
> would be very useful.
> 3. Custom mxml component code completion support in AS files: FD
> should
> support not only native, but custom MXML components. It partly have
> code completion when we use an mxml class in AS files, but mostly
> inherited properties and functions are disappear.
> 4. Mxml generation: Code generation (like class generation) and
> completion during editing MXML files.
> 5. Manifest support: You can define custom manifest files, where can
> describe for flex compiler the names and class paths (ie: <component
> id="Text" class="com.ui.controls.Text"/>). We would like a native
> support for these files.
> 6. Code navigation inside mxml: With F4 FD should jump to the
> inherited
> property as in native AS files.
> 7. Relative path support inside custom configs: we use custom configs,
> for defining our custom flex mxml manifest files, but the Flex SDK
> requires absolute path-s (or at least relative to mxmlc compiler). We
> would need a path support like in template generation (ie.: $
> (ProjectPath) )
>
> 2. package: RSL and SWC
> 1. Real RSL support: right now it has config in the project settings
> for
> RSL, but it was impossible to make it work. Right now I can use it
> with additional compiler options, but it’s really difficult to
> disable-enable it all the time.
> 2. SWC generation support: there is already a plugin, but it’s very
> limited and have a lot of bugs. It should also have the possibility
> for selectable generation, like in Flash Builder.
> 3. Support for RSL generation: native support for generate RSL files
> from generated SWC. (it most be unzipped, optimized with the Flex
> optimizer, and signed)
>
>
> 3. package: FlexUnit
> 1. Flex unit support: native support for FlexUnit testing. It should
> show the test results and detailed informations about the where did
> the test break.
>
>
> 4. package: Debugging
> 1. Breakpoint stack filter: sometimes there is a huge list in
> breakpoint
> stack, and it would be great to have a filter in this list by
> keywords (positive and negative). Filter also should support regexp
> and escaped characters.
> 2. Visual debugger, inspector (similar to firebug): it would be great
> to
> have a live inspector like in firebug. Inspect the DisplayObject
> tree, jump on the tree with I mouse click (like inspect in FireBug),
> live change the properties of any class (right now there is something
> like this, but it’s not enough user friendly)
> 3. Profiler improvements: in Flash Builder there are some nice
> features
> in the profiler that would be also great in FD.
> 4. Flex state handling: native code completion support for Flex
> States.
>
> 5. package: UI improvements
> 1. Intelligent CTRL+C and CTRL+V: after width = exactWidth ctrl+v
> generates height = exactHeight. For sure it should have a different
> shortcut like CTRL+ALT+V and CTRL+ALT+C or something like that.
> 2. Interface generation from code: sometimes we create code before the
> interface, so we would need a plugin, that generates interface from
> code.
> 3. Crl+click navigate support: it should do the same as F4. It’s a
> very
> nice feature in a FD plugin, and sometimes it’s very handy.
> 4. Ignore whitespaces search: in every search there should be a
> checkbox
> to ignore whitespaces. So if it’s enabled it would search for myVar =
> ", when the code is myVar =
> "something".
> 5. Negative filter in search: we could specify a negative filter for
> the
> search. So for example I want to find every SampleVO string, but only
> in those classes where there is no SomethingVO. Like in google the
> negative filter (ie: flash RSL –adobe)
>
> 6. package: Mercurial HG
> 1. Real HG support: it would be great to have an integrated HG
> Mercurial
> support like in PHP storm
>
>
>
> Thank you,
>
> Justin Hill
> http://Prominic.NET
> Skype: JustinProminic
> https://twitter.com/JustinProminic
> https://www.linkedin.com/in/justinprominic
Re: Public campaign to improve FlashDevelop specificall for Apache
Flex
Posted by Tom Chiverton <tc...@extravision.com>.
> I realize CrossOver is commercial and if it is a dependency for
FlashDevelop on Mac and Linux, it
> is not totally free on those platforms.
It's not, based on some recent testing :
http://www.flashdevelop.org/community/viewtopic.php?f=9&t=11922&p=52295#p52295
Runs under Wine on Linux fine.
The crosstie is useful though, and having a supported (GUI) install
system is a massive plus for some people.
Tom