Off we go...

Although I am still kind of clueless how this whole project will evolve and what steps it will successfully pass until I'm too bored or busy to further work on it and abandon efiRay... I prepared for the optimistic case - a longer period of work. :D

Three brand new books (displayed on the right hand side) will assist and guide me through the design and development phase of efiRay.


Here's a short list of things that will probably be implemented or adopted in efiRay:

r.a.d.RibbonBar for storing the vast amount of functionality of efiRay and providing quick access to all the views, buttons and other resources... (In short words: "eye candy"- pseudo-usability-increasing eye-candy...)

A MS Application Block for professional logging that could (or could not) be used even for monitoring network rendering. Or:
log4net as part of a homebrew logging solution.

Piccolo, a discontinued, but incredibly useful 2D-graphics framework that could be easily used to provide node-map-views for connecting multiple render passes to a rendering pipeline or for stacking and combining procedural textures from their generators. (Maybe also to generate more flexible TreeView "component")

Something like this to get the overheads of XML (disk space) and compression algorithms (time) out of scene files.

Command Management to separate UI from functionality and to make several occurrences of the same command possible without having additional logic or double passages to implement

This Library and controls collection could provide useful functionality such as a picture preview, a syntax highlighted editor, visual studio like document tabs and maybe much more.

...more thoughts to come!