801264 wrote:So in fact when you mean "full stack", you are referring to the compiler, an IDE and some sort of database? For the Java platform there are a few IDEs, with Netbeans and Eclipse being the most often used ones. Both can be used to build most, if not any, type of java application you can think of. If you are starting out I would seriously recommend you to NOT start with an IDE though, start from the command line using the basic java tools (java, javac and jar). Get to know the tools and the basics of Java before an IDE starts too hide too many details from you.
killed the rain forrest? that bad, huh?
What I want is a simple desktop app that pulls data from DB and save data to DB. you know, the standard server-client interaction. It reminds me of my former sidekick named Visual Basic 6.0 and SQL Server 2000. in VB 6.0 (hopefully you've heard of that), I already have the whole stack in one package (including the IDE). I just need to compile, and it will produce exe files. I'll put these exe files in the server, and put the shortcuts targetting these exe files in client PCs, and we're ready to roll. So, what's your recommendation for this kind of architecture? thanks
801264 wrote:Strange questions for someone who is OCPJP, I would expect you to know such trivial details. Yes use Swing rather than the seriously outdated AWT. I would agree holding off on JavaFX for serious production usage right now, but it cannot hurt to investigate it for future usage.
Uh-uh, I'm not a beginner anymore. I'm OCPJP 6 now, so I'm quite familiar with Java basics. So I should lean on Swing rather than AWT? As for JavaFX, perhaps I should wait till it's a little bit more stable. because, you see, it's still a new tech. while Swing and awt has been around for ages. Right?