Looks great! Although I hate glossy elements. =) But I like the colour-scheme.

Are you open for suggestions? ^^
I'd suggest a way to split the code window horizontally, the .c file at bottom, the .h file at top.

Support for Rackschas Genesis Precompiler would also be awesome. Probably in the future.

of couse, i´m open for suggestions. if there are cool features that could improve the editor, i will check if it´s worth to implement it


Definitely. Added to the To-Do-List. I will implement this code overview in the next or overnext version


this is already possible:

the interface (documents and panels) can be arranged freely. the split view i´ve shown is just for a second view of the same file


no plugins. they´re planned for the far future, but not for the next releases. for the next time i want to explore the usage, the handling of the tool and the feedback of users. i don´t see any need to open the editor if no one uses it (maybe you dislike the editor). so, let´s see what the future brings

ofcourse i wasnt thinking you need to add like rite now, like i said "add"
but as it seems feature packt already im in no doubt that you will make this
kick ass if people likes it ,it look's cool it has some nice features every
coder wants to have ,maby add some diffrent/custimizable color themes later
on because it seems no one wants to limit their visual color preference to
someone elses (if not already done),but in my opinion looks hot and yes
your totaly correct only time will tell how it stands up

I thought more of a "one window solution" (.h and .c file are treated as one file at opening). Then you can split the window itself like in SED.
But this seems to work well, too.

I suddenly have the idea of auto-creating prototypes.

Very, very useful and professionally looking application. I`m looking forward to this. Can`t wait for the release.

One thing would be cool: SED automatically shows the engine manual on the flow. When you type in "c_trace" in a .c file for example, SED shows the manual entry for "c_trace" ("Command Help"). That`s very useful and I`d prefer not having to give up using this functionality.

Oh, I hope your autocompletion adds brackets and function parameters where I can switch through with tab !

i havn´t planned the manual-binding this way. but like the visual studio way:
- while typing you can see the code completion window and the description of the engine-method taken from the manual (coming this version) or custom method (planned for version 2.2)
- an overloading-window shows you the parameter and their description for engine-methods taken from the manual (planned for version 2.1) and custom methods (planned for version 2.2)
- a mouseover on a symbol-name shows you the description (planned for version 2.1 / 2.2)

in the planning phase of version 2.0 (the coming release) i had to decide which way i want to go. the SED or the VS way. in both cases there are advantages and disadvantages: by implementing it like VS i have to parse the gamestudio-manual and extract the needed information. by implementing like SED i have to add an ie-frame and handle CHM-files (i dont know how and how good it works with awesomium). there i have to use the CHM-search or knowing the exact address of the page. finding a solution for this costs hours of testing (i´m not so familar with this format and CHM-related tools).
in the end i decided to do it like VS, because i can display descriptions of own methods and vars the same way.
but i agree with you, that this is a very useful feature of SED. and if i found a way, it should be easy to realize. so i will keep open the thought to implement the SED-way too.


No, there will no backets or params be added. but it is definitely planned (version 2.1). Horus grows incrementally and evolutionally. The Code-Completion is a feature i have underestimated. while implementing it, i realized that i havn´t thought clear enough on so much things (how to determine when the list have to pop up and with which content, when not and how to add the items fast enough (there are over 1300 entries. only the engine-stuff), calculating if a symbol is in scope, etc). this is a huge task, so the codecompletion will be be improved next versions

Implementation of Features complete.
Now entering Milestone 8 of 8 - the remaining documented bugs will be fixed and the final test will be run

Great, don't can wait for it.

1st May is over since a week. When can we test HorusIDE?
I'm really interested in it and can't wait longer for it, too.