Free ActionScript IDE for Mac? - macos

I have been scrambling to find a good way to edit/run AS3 on Mac for free. AXDT for eclipse won't install, and for a while I was using Sublime text + Terminal but it sucked cause of no code completion. Any ideas? Obviously FD is out of the question, being Windows only.

Currently, there are no entirely free ActionScript IDEs for the Mac. There are, however, some solutions you could use, depending on what you're working on and what other language support features you need, other than simple code completion:
If you're working on open source stuff, you should take a look at IntelliJ IDEA, which is free for OSS projects.
Also, FDT has a free version, but it does not include advanced refactoring, as well as a number of other functions.
If you don't need project management, refactoring and such, you could keep using a text editor and compile via the command line. There is an ActionScript 3 syntax file for vim, and an ActionScript mode for Emacs.
If you're going to work with ActionScript (semi-)professionally, I would strongly recommend you reconsider paying for a good solution, though. There is so much more to a good IDE than just text highlighting and code completion!
IDEA, for example, actually helps you write better code in many ways: By enabling you to run unit tests (as suites, as single test class, and even as a single test method) directly from the editor window; by including highly advanced refactoring features, such as "change signature", "extract interface" or "inline method"; by analyzing what you write, and offering alternatives, etc.etc.
And then, of course, there's all the things that have nothing to do with the language itself, but make your life as a developer much easier: version control and issue tracking integration, build tools, dependency management, just to name a few.
If you're going to make any money with your code - and I mean, ANY money - a good IDE will earn its price quickly, probably even within a day's work.

Related

Is there an IDE that provides code completion for Cappuccino

I have tried almost every IDE listed here, but none of them provide code completion.
As a Flex developer I am used to code completion in Flash Builder. It saves tons of time and helps with spelling errors.
Does anybody know about IDE with code completion for Cappuccino? Is is difficult to create, or it is simply not as important for everybody as it is important for me?
Our company is gonna use Cappuccino heavily, and thus I don't mind to ask one developer to volunteer and create some kind of Eclipse plugin. Just let me know, how important it is and how difficult it would be.
There's no full IDE support that I know of, but several text editors have support. Coda ships with it, and there exist textmate and sublime text plugins (Several of the core team members use Sublime, and I hear it's pretty good.) https://github.com/aparajita/Cappuccino-Sublime
Also, unfortunately, the website is a pretty poor resource for finding relevant content, it works for some old stuff that hasn't changed (like the tutorials), but things like debugging and editors the info is almost certainly out of date because of how rapidly these things are changing.

need to make a simple Windows app, what languague should I use?

I need to make s very simple app, with a canvas where the user would be able to drag & drop PNG files, drag, scale and rotate them on the canvas and export to XML their name & coordinates.
I'm pretty good at Android(java) programming, but as I just tried plain java with windowsBuilder for the first time, it appeared to be rather inconvenient and probably would take at least a few days to find my way around in it.
So I thought, maybe you could suggest some simple "program maker" style language/ide that could be quickly picked up for such purpose?
Right now I'm thinking of Flash... any other ideas?
Thanks!
I would go with C#, with the .NET framework.
As you already know Java, it shouldn't be that hard, as C# is also an object-oriented language.
They are some differences, of course, and I won't explain them here.
But if you want a real Windows app, it may be your best choice, as you'll then have access to all the Windows features through the .NET framework.
Everything is very well documented.
You can also choose C++ (managed), but it might be a little harder, coming from Java.
About the IDE, simply use VisualStudio (the express edition is free).
Hope this will help.
I learned JavaScript (I know it's not Java, but similar nonetheless and still object oriented) first and then C++. The transition was quite easy since both are more-or-less object oriented. Like Macmade said, Visual Studio is great to begin, but I prefer using gedit and then compiling with G++. It's more forgiving than Visual Studio and you don't have to create a project and whatnot just to start writing the code. With a text editor like gedit and a standalone compiler, G++, it's much easier to just write the code and then build the program.
I'd stay away from Flash. I know AS2/3 pretty well and I can say that C is much easier to code, at least for me. Everyone has their personal preferences, though. One plus to C is you don't have to buy Flash.

Is Visual Studio also a good IDE for non .NET languages?

I'm a bit in IDE trouble, and I'm not alone I have noticed, still I haven't found an answer on many of my questions.
I would very much stop using different editors and become very good at one (on windows), adhering the pragmatic adage : "Learn one editor (ide) well". I' m willing to put in a lot of effort, to gain on the long term.
I have programmed (java) with Intellij and Eclipse, and am progamming c# now. (VS08 was at first very disappoing for me, till so at SOF mentioned Resharper and now I'm very happy with it, especially since I started writing macros for further adjustments)
For all purpose editors, VIM and EMACS come to mind, but I'm afraid they just cannot compete against VS08/Resharper when it comes to C#, which I'm using a lot on this moment. Further, it isn't clear to me if they support refactoring (after installing packages for the language in question?)
But since VS08/Resharper is so powerfull for c#, I would like to give VS a serious chance. But for that it should have support for langauges that don't compile to CIL.
hence my question : Is Visual Studio a good tool for non .NET languages?
(and like asked on the side : how about refactoring in VIM/EMACS?)
VS is IMO, better then average editor but not something you can't live without.
If you like your editor to open as fast as Notepad with bunch of features, try EditPlus (on the down side it uses older RegExp implementation but on the plus side it can be made to be portable.
If you would like total extensibility, fast startup, inovative fatures, integrated reposity etc.. try E-Editor, windows port of Mac TextMate.
VIM is ofc superb, but ... long learning curve may be a problem and some people can't find themselves in 2 mode editors.
About Resharper... mhm... almost all of its non-code analytic features may be integrated in mentioned editors. For its suggestive features I doubt there is alternative. I disabled it for the moment because I tend to let Resharper fill in my holes so it can be a double bladed sword - sonner or latter I will totally stop thinking about some things like, can this variable be null or can I move its declaration. I run resharper once I finished some working procedure or at the very end to polish the code.
I personaly use EditPlus for all of the NON MS languages, but E-Editor got my attention recently.
I tend to avoid using IDEs outside of the languages they are designed. A dedicated IDE can include class libraries, function references, code completion utilities, etc. out of the box.
Once you step outside that, however, you have a clunky and resource hungry text-editor. You might as well use a text editor in that case just to keep your workstation nimble.
It might be better not to learn one IDE well, but rather a text editor. I've used jEdit for years for several reasons: It's multiplatform, includes syntax highlighting for lots of languages, and can be feature-extended with plugins. It's become one of my standard tools, but it's only one in the box.
How about VI mode for VS? I think Eclipse has one too.
You'll just have to learn vi-related commands, but will be able to work in, C# (with VS), Java (with Eclipse), C++ (with VS or Eclipse), scripting languages (with vi), ...
"I would very much stop using different editors and become very good at one (on windows),"
Why?
"adhering the pragmatic adage : "Learn one editor (ide) well". " Really? How is this pragmatic?
After 30 years in this business, my lesson learned is "tools come and go."
Once upon a time we had big fights over vi vs emacs. Not vim with syntax coloring, but plain-text-vi on black-and-white monitors.
Why narrow your world to one tool? How will you cope with innovation if your tool is not the new state-of-the-art?
As far as C/C++ goes, Visual Studio is considered the gold standard (well, Visual Studio + VAX if you really want to get specific). It's not perfect, and it's certainly not as good as the C# tools it has, but it's still a damn sight better than anything else out there, on any platform. (Assuming you didn't want C99 support.)
Of course it doesn't really do non-.NET other than those two.
I think that there is good specialization at the moment. VS is the clear candidate for .Net, with Resharper and DevExpress as great augmentation for increased productivity.
Currently we use Aptana for the "Web 2.0" stuff - CSS/jQuery/MooTools, and that has been a great environment as well. I have avoided the Intellisense in VS 08 for jQuery and do prototyping in HTML/CSS/JS in Apatana, then do all the Domain design in VS. Works for us pretty well.
It is good for C/C++ but it is not comparable with what you get for C# or VB.Net ( i don't think it support other languages )
for javascript intelisense is still limited

DevExpress Refactor Pro vs JetBrains ReSharper

In my department, we are currently using ReSharper 4.0 and deciding whether to upgrade to 4.5 upon its release next week. I personally am a huge fan of ReSharper however a number of my colleagues have pointed out that they have been using a plug in from DevExpress called Refactor Pro that performs similar functionality.
http://www.devexpress.com/Refactor
http://www.jetbrains.com/resharper/beta.html
Has anyone previously compared these tools and hold any strong views on which tool would give us the greatest increase in productivity and why?
In my department, we also use ReSharper. Today, I installed 4.5, but had already used 3.something, 4.0 and 4.1 before. It really offers many great refactoring and code-writing supporting functions, renaming methods and functions, reordering parameters...
What I really like is that according to your corporate code style, you can configure ReSharper to give you hints on style violations in different severity levels (and quickly apply according changes, like MS StyleCop, but much easier to configure and more subtle).
My absolute favorite feature is Class-Searching by entering only the CamelCases, i.e. you type TSHWLOV and ReSharper will know that you mean the class from some referenced library named 'TerrificSearchHelperWithLotsOfVoodoo'.
Last year I have tried the DevExPress CodeRush/RefactorThis-Alternative, after I was quite impressed by the things that Oliver Sturm did with it on BASTA Spring 08.
The interface catchier and more impressive than Resharper, there are huge arrows flipping around your IDE and things like that, though the core functionality is rather similar.
I had the feeling that CodeRush is more focussed on code creation than on refactoring, i.e. more shortcuts for tasks like creating variables etc.
My favorite feature there was a sidebar, which always shows you all keyboard-shortcuts available in your current context. This makes you learn those commands quickly, where in ReSharper you have to look up most of them in nested submenus.
Both suites are really powerful and it after months of using them you will probably still discover new functions, which you have always needed without knowing it.
However, I decided in favor of ReSharper mostly because of I was more familiar with it and DevExpress was using much resources on my notebook and occasionally even slowed it down. By now, I use a much more powerful machine again, maybe I will give it another try soon.
I personally prefer CodeRush.
I find R#'s interface drives my (admittedly minor) OCD tendencies crazy. The little lightbulb insists on appearing on the far left of the screen, even if it's advice pertains to something in the middle or on the right. I find it garish and distracting.
By contrast, CodeRush's equivalent smart tag is lower contrast and smaller. It is therefore capable of locating itself within the code without distracting from said code. I find I can ignore this SmartTag when I need to, and it is always right in front of me when I decided I need it.
It is mainly this, that has prevented me from wanting to explore R# any further.
As far as CodeRush's feature set: Code Analysis, Refactorings, CodeProviders, Templates, TabToNextReference, QuickNavigation and many more.
I especially like CodeRush's extensibility which has allowed myself and several others to create many plugins for use within it. (http://code.google.com/p/dxcorecommunityplugins/)
CodeRush also has some top quality support and a very active community of users.
Certainly neither R# or CodeRush will suit all users. Every one has their own preferences. However, if you've not tried both, you should certainly do so.
If you come from the R# side of the equation and are looking to test out CodeRush, then you may find the compatibility plugin useful (http://code.google.com/p/dxcorecommunityplugins/wiki/CR_ReSharperCompatibility)
In addition CodeRush has a Free edition 'CodeRush Xpress' which Microsoft commissioned DevExpress to create, and which they have licensed on behalf of every user of Visual Studio 2008. This partnership will continue into VS2010 upon it's release.
If you have any questions regarding CodeRush you can find details for contacting me at the bottom of my community wiki page.
I should say that I do not work for DevExpress. I am what you might call a DevExpress MVP. To maintain this position, I answer questions in the DevExpress forums (and nothing else).
Everything I say is my own honest opinion.
If you have any questions, feel free to contact me :)
I'm using DevExpress which has a lot of "hidden" functionality, so you need to read the manuals to know how to activate some of the functionality. I find it very passive and subtle.
I used ReSharper and found it buggy and very invasive in my coding style. Bracket-closing drove me nuts, it ignored my preferences and couldn't cope with how I write my lines of code - which may not be most efficient but it's one of those things that ain't gonna change!
I've tried both, and really didn't get along with ReSharper. I found it to be just too intrusive for my coding style. When I switched to CodeRush / Refactor! it was like I'd found the perfect aid to my productivity. The refactorings are, for the most part, exactly what I wanted to see from this kind of product.
It is, however, horses for courses and you may well find that you prefer ReSharper. The best advice I can give is to try the other products and see which you prefer.
The only correct answer is to use both, of course! I do. You need a beefy laptop though. If I had to choose only one, I'd choose ReSharper... I think the static code analysis is a lot better.
ReSharper has a lot of great features, and DevExpress has a lot of great features.
When you put the two together, you end up w/ whole lot of AWESOME.
You need to jump through a few hoops to make them play nicely together: http://frazzleddad.blogspot.com/2010/01/making-devexpress-resharper-play-nicely.html
R# 4.5 is a free upgrade if you have a 4.0 license. So I'd suggest to get and use it - changing the "productivity tool" is always a pain because you'll have to get used to different ways, keyboard shortcuts etc. of doing things - no matter how good the tool actually is.
I have a personal copy of Refactor Pro but I use R# 4.1 at work with the StyleCop add-in as that is the team standard tool. I like RfP's arrows and code positioning stuff which is better than R#. Otherwise the tools are very similar.
However, at this time, its the StyeCop add-in that swings it in favor of R# for me.
Cheers
Benjy

Developer Setup for Starting Out with Cocoa/Mac Programming

I'd like to start experimenting with Cocoa and programming for Mac OSX. I'm not terribly concerned with Objective C syntax/constructs/bheaviors at this point, but more curious as to an efficient setup on in terms of an editor and/or IDE that will get me going quickly. Is there any IDE even remotely similar to Visual Studio (since that's where I've spent most of my time over the last 7 years) in terms of it's solution/project concept? Any other tools, tips, suggestions and/or resources to get up and experimenting quickly?
I'd like to avoid a lot of the intro stuff and get into things like "If you want to create an Mac desktop application, you can use Acme IDE and set up your project like this."
I was afraid Xcode was going to be the answer! :P I tried playing around with that -- literally just getting it off the DVD and just diving in with no idea what to expect (before I even knew that you used Objective C as the language). I figured, the wise guy that I am, that I could just sort of fumble around and get a simple app working ... wrong.
#Andrew - Thanks for the insight on those config settings. Based on my Xcode first impression, I think those may help.
I'd suggest you pick a fun little product and dive in. If you're looking for a book I'd suggest Cocoa Programming for Max OSX which is a very good introduction both to Objective-C and Cocoa.
XCode is pretty much the de facto IDE and free with OSX. It should be on your original install DVD. It's good but not as good as Visual Studio (sorry, it's really not).
As a long-time VS user I found the default XCode config a little odd and hard to adjust to, particularly the way a new floating window would open for every sourcefile. Some tweaks I found particularly helpful;
Settings/General -> All-In-One (unifies editor/debugger window)
Settings/General -> Open counterparts in same editor (single-window edit)
Settings/Debugging - "In Editor Debugger Controls"
Settings/Debugging - "Auto Clear Debug Console"
Settings/Key-binding - lots of binding to match VS (Ctrl+F5/Shift+F5,Shift+Home, Shift+End etc)
I find the debugger has some annoying issues such as breakpoints not correctly mapping to lines and exceptions aren't immediately trapped by the debugger. Nothing deal-breaking but a bit cumbersome.
I would recommend that you make use of the new property syntax that was introduced for Objective-C 2.0. They make for a heck of a lot less typing in many many places. They're limited to OSX 10.5 only though (yeah, language features are tied to OS versions which is a bit odd).
Also don't be fooled into downplaying the differences between C/C++ and Objective-C. They're very much related but ARE different languages. Try and start Objective-C without thinking about how you'd do X,Y,Z in C/C++. It'll make it a lot easier.
The first document to read and digest is the Mem management guide, understand this before moving on. This is a great guide to objective-c too. Infact the developer site at Apple is very good - but you would probably want to read the Hillegas book first.
In regards to Xcode vs Visual Studio - they are different. I wouldn't say one is better than the other - Windows developers come over from VS and expect it to be the same. This is just an arrogant attitude and please don't fall into this crowd. Having used VS since the AppStudio days and Xcode for a year or so now, both have strengths and weaknesses. Xcode is something that out of the box (and especially when coming from VS) doesn't seem that good, but once you start using and understanding it - it becomes very powerful.
Also, there are a lot more tools included with Xcode et al, such as Instruments and Shark that you simply can't get with VS, unless you open your wallet, and even then IMHO aren't as good.
Anyway, good luck. I still enjoy C#, but Objective-C/Cocoa somehow makes programming fun again once you get into it...
Don't bother digging up your OSX DVD as they've released a new version (3.1) of XCode since then.
First, you'll want to join Apple Developer Connection (it's free, and you need it to access their version of MSDN) - it uses your Apple ID so if you've ever had one for the itunes store etc, it's that same username/password
Once you've done that, click on downloads, then click on developer tools, to view this page, and go for the XCode 3.1 Developer DVD
One other suggestion: If you have feature or enhancement requests, or bugs that you've run into, be sure to file them at Apple's Bug Reporter. It's the best way for developers to communicate their needs to Apple, because every issue is tracked through the system.
You might try the demo of textmate and see how you like it for working with objective-c or any other type of text really. It will import xcode project settings so you can still compile and run from textmate rather than having to go back to xcode.
Xcode is the standard for editing source files, though you can use another editor in conjunction with the command line xcodebuild tool if you really want. I used Vim for all my Cocoa editing before finally giving in to Xcode. It's not the greatest IDE in the world, but it gets the job done, and the recent 3.x releases have had some nice improvements.
The real power tool of Cocoa development is Interface Builder. IB does not generate source code like many UI tools. Instead it manipulates real Cocoa views, controls, and objects which it then bundles into an archive (nib) that is loaded by your program at runtime. Most Cocoa programs use at least one nib file, and often many more.
No matter what IDE/editor combination you choose for hacking on source files, I recommend using IB where you can. Even if you're not a fan of other UI layout/generation tools, I suggest keeping an open mind, giving "the Cocoa way" a chance and at least learning what Interface Builder can do for your development process.
AFAIK, pretty much every OS X developer uses Xcode.
That, and Interface Builder for creating the GUIs.
FWIW, try to get hold of a copy of Hillegas's book, as it's a great introductory tutorial, and the reference Docs Apple provides really aren't. (They are generally very good reference docs, however).
Cocoa is huge. The hardest part of learning how to write apps on Mac is learning Cocoa. By the way. You do not need to know ObjC (though it helps tons). You can write Cocoa apps with Python or Ruby (right in the IDE).
I agree VS is a better IDE then Xcode. But if you throw in Interface Builder and all the other tools, I'm not so sure. Mac development is not about 1 giant IDE for everything. But VS is "kinder" on the developer then Xcode is.
Also if you want to do cross platform apps look at RealBasic. A fine tool (Basic though. But it runs on Linux too.) You'd be surprised how many Mac apps are written with RB.
I've heard the books currently out there are pretty out of date. The whole ecosystem seems to evolve very fast with dramatic changes made in every OS release.
He wrote a tutorial which pulls together some Apple documentation and other tutorials which should get you started. I think it covers the basics of using the IDE, writing simple apps, and then goes on to more advanced stuff.
I've been dabbling in Cocoa for the past couple years, and recently picked up Fritz Anderson's "Xcode 3 Unleashed." Highly recommended for getting into Xcode — especially with some of the big changes 3.0/Leopard brought.
Don't forget Hillegass' defacto Cocoa bible, "Cocoa Programming for Mac OS X - Third Edition."
#peter I don't know why you had trouble with getting a simple app working, right off the bat without doing anything your app gets a lot of benefits from the Cocoa framework. If you mean you were trying to do stuff like connect a button to an action and have it print a alert on screen or something like that then yes I could see where your going with it being difficult.
The problem for me starting with Cocoa many years back is that it was so different from anything else that it had a little bit of a learning curve. Whereas many other systems are compile time oriented Cocoa is very dynamic and runtime oriented. Once you get past learning how actions hook up to classes it just becomes a matter of learning how the Cocoa frameworks work.

Resources