I'm thinking of writing (at least starting) a simple SDK tool (fxSDK's main program). I also think Qt is the mosts appropriate toolkit for most platforms, so the code will have to be under the GPL license.
A simple draft of the main applications look: (No real coding has started, and therefore no code in SVN)
[attachment=0:2ebfqhk2]screen.png[/attachment]
(The text area in the bottom is for the output of programs that are a part of the build process, a console of sorts)
(The unused space to the right of the file names could be used to display file info and change compile options. It is of course also possible to align the two areas vertically.)
There is no point in having an editor as part of the application, but instead choose a sane default editor (depending on OS), and let the user specify one himself if he wants.
'fxSDK Manager' (or something) will only be used to organize source code into projects and as a control panel to run smaller utilities. With utilities, I mean programs that can be used independently, like xfer9860, gcc, binutils, a program for adding .G1A headers etc..
Some input on this project is what I am looking for - what sort of features would you expect from an open and free toolkit like this? Remember that this toolkit is not the place to add custom code for the calculator, revolution-fx is.
fxSDK can only provide the minimum that is needed to make the users code compile and possibly a minimal reimplementation of Casio's functions. For example; a menu option for importing revolution-fx into the project, with selectable modules (graphics, serial etc) would be great, but revolution-fx and fxSDK should each do their 'thing'
So again, what would you expect?
