I am kinda of a new user here and don't have enough reputation points to comment/ask on this question: IDE support for Hack Lang.
So, I am hoping that since the last entry provided by Themis Beris someone has been able to get PHPStorm working properly with Hack. I followed the 3 steps described in the post I mentioned, but still get compile-time errors on the classes I've written using Hack. <?hh is not recognized, for instance.
Any suggestions as to how to get PHPStorm playing nice with Hack?
I have no idea what Themis Beris is talking about on the linked question. (He seems to be saying something about PHPUnit, which is a completely separate issue.)
JetBrains has a feature request open for Hack support and last I heard was very actively working on it. But as of this writing (Feb 2015) it's not released yet.
Xcode 4 has a very nice built-in help/documentation that you can access e.g. by alt-clicking an identifier in the code, or by opening the help panel in the right sidebar. However, this only works for classes and methods provided by Apple. Is there a way to write some kind of documentation comments (e.g. like the Javadoc comments in Java) in your own code to make Xcode display them in those documentation panels?
http://developer.apple.com/library/mac/#documentation/DeveloperTools/Conceptual/HeaderDoc/intro/intro.html
It's maintained by Apple so it should be well supported. I never actually used it, may try it later.
Ok, it looks like there's no good tool really... there are a few different ones, but they're imperfect and difficult to configure. I couldn't get Doxygen or Appledoc to work, and the tool mentioned by Avizzv92 is referred to as "a pile of poo" elsewhere, so I'd rather not try it... :)
Info that I've found:
How do you document your source code in Xcode?
http://wangling.me/2010/07/documentation-set-generation-tool-in-xcode-is-wanted/
http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
http://www.gentlebytes.com/home/appledocapp/
http://lists.apple.com/archives/xcode-users/2011/Apr/msg00238.html
Sorry if this is well known but Googling for my answer only came up with links about making Google Wave gadgets.
My question is, are there any Google Wave gadgets that allow for better collaborative code editing? I mean, I can set the font to fixed width etc., but are their any gadgets designed for it?
Responses shouldn't include anything about git or svn. I use those when I want to use those. This is about Google Wave!
Here is a huge list of robots available for Wave: http://www.chaaps.com/huge-list-of-125-google-wave-robots-add-bots-and-enjoy-wave.html
Maybe there is one in there?
Don't know how well it works but found an extension called CodeBot.
http://aaron.oirt.rutgers.edu/myapp/root/gadget/codeGadget
-- its a work in progress. Let me know if you want the source code.
I will package it and release it or something like it for the next WHIFF
release.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I didn't find a question on this while searching SO but if anyone does please tell me.
There are alot of questing on the pros and cons of IDE's and what IDE to use for this and that language, like "Why should I use an ide?" and "Are we too dependent on our IDE's?".
But as a beginner just starting to understand how to build GUI's with Swing and getting a grip on the workings of event handlers and whatnot I started to wonder, when should you actually start using an IDE to further productivity and not stifle the learning experience?
The intellisense function is really helpful but sometimes makes me feel lazy for not thinking that extra bit and looking things up in the book im reading or the api documentation.
However the ability to set flags in the code to step trough to find logical errors and actually go into the parent method are sometimes useful to get a better understanding about what goes on in the code.
I read somewhere that you should have a good grasp on the basics of a language before using the IDE, but what is the basics? And what is good?
The only downside to using an IDE would be using its tools and wizards and not understanding how the code they generate works. If you are using an IDE for code completion, syntax highlighting and debugging then that's great. If you are using it to generate GUIs that you can't build by hand or generate Web Service code that you don't know how it works, then that's bad. But that's bad regardless of whether you're a beginner or not.
Your instincts are right. Understand how things work and how to code things by hand before just trusting the tool blindly.
An IDE is a tool you should use from the start. Understanding how languages work is important but memorising every little detail, not so much. A builder would no more learn how to make a mud hut with his barehands before building something with power tools than you should learn to program without using an IDE.
That said, you should be aware of what the IDE is doing for you so that in circumstances where you are faced without one, you know the things you need to make up for. An IDE can't write good code for you, it can't even tell you how to write good code, or suggest good code, it can only supplement your own skillset (at least right now, in 2009 - I can't speak for our robot IDE overlords of 3452).
Don't start with an IDE. Here's why:
I learned Java using Notepad and the command line. If I needed to know what methods a particular class had, I looked at the APIs online.
I did that for about half of a semester. Then we switched to Eclipse.
Doing it that way, I became very familiar with the Java syntax, lots of the core libs, and how the Java 'compilation' and running process works.
People should never develop this way long term as it is terribly unproductive. But I feel it is the correct/best way to begin learning a language.
Don't start with an IDE.
I would suggest using an IDE right off the bat...but not worrying about most of the functionality. As you learn the language and become more familiar with processes, aspects of the IDE will suddenly become obvious at the right times.
I don't think you should get too hung up on delaying using an IDE. Let's face it, in the real world, you'll be using that IDE pretty much all the time.
When you're initially learning, I think the most important thing is to use the IDE, but know what it's doing.
For example, when Visual Studio.NET first came out, and I played with it and wrote my first "Hello World" app, then clicked the "green go button" (!), I watched the output window with all of it's information. I then looked at the help documentation to see that this is really just calling out to csc.exe and piping it's text output back into an IDE window. So I went off and started invoking csc.exe myself from the command line and saw it's parameters that it would accept. Then I jumped back into the IDE and saw how GUI checkboxes related to the csc.exe parameters.
This way, I started using the IDE straight away, but also learnt what the IDE is doing with regards to "shelling out" to command line based utilities.
From here, I even tried typing my first C# program in Notepad and compiling it from the command line. But I wouldn't get too hung up on it, though. Let's face it, in the "real world" you're very unlikely to need to do it. I was good to scratch the itch of my curiosity, though!
IDE saves you time and energy. I have no problem of using IDE even as beginner. It only helps.
If you know the ide well, it will help you explore a new language/technology that it supports.
If you don't know the ide, better don't use one at first. Use a simple text editor (notepad++ on windows), command line, and the official reference.
I think that you should be able to manually do anything that the Intellisense is doing for you automatically. For example, you should know what function you want to type before hitting Intellisense.
Well, if you're expirienced in other languages or just might have worked with them, then use IDE right away.
But for complete beginners, I wouldn't suggest it.
It doesn't have to be one or the other - try both. Life's short enough ;-)
I've seen many people saying XRCed very strong "if you have learned how to use it". Unfortuntately, there're few documents about it, and many of the links on SF.net home page is 404 now.
The best I can found is XRCed Tutorial, however it is too primitive - so, does anyone have some idea for where can I find better documents about it?
Just a suggestion; have you tried wxFormBuilder? XRCed seems a little outdated (hasn't been updated for a while), and it does the same thing as wxFB. I've been using wxFB for a while in several projects and it's a life saver.
Alongside the already mentioned wxFormBuilder, I'm going to throw in wxGlade, as well. While I prefer wxFormbuilders GUI, I found it to be lacking in the available widgets. So I moved to wxGlade based on the amount of widgets it offers.
Both can create XRC files (and some other codes like C++ and python) and I think both are actively maintained. I think XRCed hasn't been updated since 2007.
For ease of use, I would go with wxFormBuilder. If you want to use various different widgets, for the moment, go with wxGlade. I don't know if wxFormbuilder is planning on incorporating ToggleButtons and the like in their future releases. It isn't in the one that I am using...