AVR Freaks

Thd point was that you should, for your own sake and for the projects sake, change the name ASAP before you get tangled in a mess of confused and possibly irritated people. I'll leave it to you to check whether Atmel registered "AVR Studio" as a trademark (which would now be owned by Microchip).

It starts, but at the same time (in the CMD window which I start from):

C:\Users\MyUserName\AVR\abdalmoniem\AVR-Studio-master\Binaries\bin>java -jar AVR-Studio.jar
java.lang.UnsatisfiedLinkError: no rxtxSerial in java.library.path thrown while loading gnu.io.RXTXCommDriver
Exception in thread "Thread-2" java.lang.UnsatisfiedLinkError: no rxtxSerial in java.library.path
        at java.lang.ClassLoader.loadLibrary(Unknown Source)
        at java.lang.Runtime.loadLibrary0(Unknown Source)
        at java.lang.System.loadLibrary(Unknown Source)
        at gnu.io.CommPortIdentifier.<clinit>(CommPortIdentifier.java:123)
        at mainPckg.Studio$3.run(Studio.java:968)
        at java.lang.Thread.run(Unknown Source)

If you catch this exception then you could produce a much more helpful error message to the user. (How many of your potential users do you think will know what rxtxSerial is?) Something probably went wrong in your project setup, since...

C:\Users\MyUserName\AVR\abdalmoniem>dir /s /b rxtx*.*

C:\Users\MyUserName\AVR\abdalmoniem\AVR-Studio-master\Binaries\bin\dependencies\RXTXcomm.jar
C:\Users\MyUserName\AVR\abdalmoniem\AVR-Studio-master\Binaries\bin\lib\RXTXcomm.jar
C:\Users\MyUserName\AVR\abdalmoniem\AVR-Studio-master\Source Code\AVR-Studio\RXTXcomm.jar
C:\Users\MyUserName\AVR\abdalmoniem\AVR-Studio-master\Source Code\AVR-Studio\dist\lib\RXTXcomm.jar

C:\Users\MyUserName\AVR\abdalmoniem>

First reactions: 

The UI is "wiggly". When moving the mouse-cursor over the textbox for searching the list of AVR models, the tex-tbox changes size and the combo-box to the right of it moves as a result.

I give that text-box focus and type a few characters, then erase them. Now the text-box has lost focus..

Are you planning on releasing the sources?

Any support for newer programmers, e.g. JTAGICE-II, JTAGICE3 or Atmel-ICE?

Did you write the flash programming yourself? (One idea would be to use AVRDude, which for a long time now has been divided into one library with the programming code proper and one application with the (command line) UI. You would "only" need the library and then all programmers supported would be available to your IDE. AVRDude has firm support and has been around for a long time. It is extremely well tested and supports most all existing and decent programmers.

Next, I tried to build (I assumed that is what you call "Verify"). It failed, since avr-gcc and all the binutils could not be found. You need to document that this needs to be installed separately and that it needs to be in the path.

Just for fun I tried "Upload". Then everything hangs (no, no programmer attached). No chance to stop the application via it's UI. It's looping hard somewhere, the mouse cursor flickers between the arrow and an I-bar, but apart from that the IDE is completely dead UI-wise.

Switching over to the command window from which I started the IDE there is a steady flow of:

1 error, 0 warning
Compilation Terminated, could not generate hex file !!!
avr-gcc -std=c99 -g -Os -mmcu=attiny28 -c "C:\Users\MyUserName\AppData\Local\Temp\sketch_jun18_17\sketch_jun18_17.c" -o "C:\Users\MyUserName
\AppData\Local\Temp\sketch_jun18_17\sketch_jun18_17.o"
avr-gcc -g -mmcu=attiny28 -o "C:\Users\MyUserName\AppData\Local\Temp\sketch_jun18_17\sketch_jun18_17.elf" "C:\Users\MyUserName\AppData\Local
\Temp\sketch_jun18_17\sketch_jun18_17.o"
avr-objcopy -j .text -j .data -O ihex "C:\Users\joMyUserName\AppData\Local\Temp\sketch_jun18_17\sketch_jun18_17.elf" "C:\Users\MyUserName\AppD
ata\Local\Temp\sketch_jun18_17\sketch_jun18_17.hex"
rm -f "C:\Users\MyUserName\AppData\Local\Temp\sketch_jun18_17\sketch_jun18_17.o" "C:\Users\MyUserName\AppData\Local\Temp\sketch_jun18_17\ske
tch_jun18_17.elf"

1 error, 0 warning
Compilation Terminated, could not generate hex file !!!
avr-gcc -std=c99 -g -Os -mmcu=attiny28 -c "C:\Users\MyUserName\AppData\Local\Temp\sketch_jun18_17\sketch_jun18_17.c" -o "C:\Users\MyUserName
\AppData\Local\Temp\sketch_jun18_17\sketch_jun18_17.o"
avr-gcc -g -mmcu=attiny28 -o "C:\Users\MyUserName\AppData\Local\Temp\sketch_jun18_17\sketch_jun18_17.elf" "C:\Users\MyUserName\AppData\Local
\Temp\sketch_jun18_17\sketch_jun18_17.o"
avr-objcopy -j .text -j .data -O ihex "C:\Users\MyUserName\AppData\Local\Temp\sketch_jun18_17\sketch_jun18_17.elf" "C:\Users\MyUserName\AppD
ata\Local\Temp\sketch_jun18_17\sketch_jun18_17.hex"
rm -f "C:\Users\MyUserName\AppData\Local\Temp\sketch_jun18_17\sketch_jun18_17.o" "C:\Users\MyUserName\AppData\Local\Temp\sketch_jun18_17\ske
tch_jun18_17.elf"

  .
  .
  .

So, something goes very wrong there..

More questions and observations:

The reason I wanted to just build was that I was curious as to what compiler and linker options you are using. Will there be any provision to set those? Immediate things I come to think of is include, directories, .o libraries to link with and a search path for such, provisions for defining a preprocessor symbol, options for removing unused functions (needs to be set on both compilation and linking commands).

The File, New file command does absolutely nothing. (I wanted to try having several source files, partly to see if I could spot how you do linking in such a scenario).

I switched to using a makefile, and generated its content. I now see you're using AVRDude. This is not in the furbished in your installation. You need to document that it needs to be installed separately and that it needs to be in the path.

Also, since you are using AVRDude, why is rxtxSerial needed? (AVRDude does not need it on Windows as far as I know, but I might be wrong..)

-----

I hope my first reactions does not make you lose your motivation. I like the initiative!

But without proper testing you will get disappointed users and the come-back from that is not easy. It'll be up-hill.. For anything new released, commercial or open-source or "free", it is important to get the best possible start. Test, test and test again. Get a few "beta-testers" that will help find the bugs you won't because you know how "it ought to be used and work". Expect to spend just as much time testing as you do writing code. Divide the application so that you can write automated unit-tests for as much of the application as at all possible. (The only thing not being testable like this is a very thin layer of UI. If you do it "right"..) Now you can code and refactor with much more security and much less risk of introducing regression bugs etc.

-----

I'm about to connect my Atmel-ICE now and see how your IDE reacts.. (The STK500/600s are tucked away deep somewhere..)

-----

NOTE: All testing above done on Windows 7 Professional.

Java version:

C:\Users\MyUserName\AVR\abdalmoniem>java -version
java version "1.8.0_51"
Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)