Fresh Start

2024-10-20T15:39:10.092000Z

After years of inactivity, I decided to give it another try. This time, I'm using the Irrlicht 3D engine, since that is already multi-platform, pretty small and easy to use. The old code will be abandoned, and new code published here, soon (I hope).

First classic tarball

2010-01-17T19:01:39Z

First classic tarball available.

Provided it's unpacked on a linux system with Coid3D and Qt devel-packages (include files and libraries), the tarball should unpack, configure && make && make install. At least it works on my system.

The build-system is new, so probably still buggy. I'd be glad if anyone could download, unpack and just try a "configure && make" on it.

Most probably it won't work out-of-the-box, but I'm working on that as fast as I can, so that I can get back to working on codive itself.

Priorities

2010-01-16T21:57:34Z

Okay, I'd really like to port the code to the windows platform, but I've decided to set the highest priority to autoconf/automake instead.

Windows users will just have to wait. I'd really like to make this easier for the linux people. That's where codive comes from, in the first place.

Meanwhile the windows people can rejoice about the fact that M$ is coming out with new OSes every now and then, while the M$ notepad still doesn't know how to show you line numbers (at least on windows XP).

More news at 11.

working on the editor

2009-11-29T23:08:31Z

Well, well, well, I am still bouncing into some walls, since I haven't worked with C++ and OpenInventor (Coin) in a long time. I also have zero experience with Qt, but I like it already.

Still, considering that I've been spoiled by all the modern IDEs for such a long time, it's a good feeling to work with the vim again, freak out over compiler errors like in the good ol days, and once more dive into some coding.

So far, codive reads a bunch of files and displays the content. I am currently working on some simple editor commands, the necessary event handling, and then save the contents back to the file.

Since I want to get ahead, I don't pay much attention to string handling or being extremely OS independent. I'll improve the code once I can start using codive itself to edit the code.

There's so much to do still, that my head starts rotating, but it's fun to be back on linux and code away with some music on a cold, grey autumn weekend.

Cheers, and let me know if you'd like to test codive, once it's in a testable state.

Hartmut Ehreke

First Release

2009-11-22T21:08:47Z

I was waaaaaayyy too lazy, but I finally got a simple starter running, which is now released. It doesn't do much: It starts an OpenInventor Viewer and displays its own source as 3D-text. It's not much but it works.

What you need to run this thing is: Coin3D, Qt and SoQt. If you have questions, just mail me.

Next up: display many source code files and let you look at your code from a whole new perspective.

Want to help? I really could use some help on automake/autoconf and of course some source code syntax coloring and some editor functionality. Once we got that, we should focus on the structures within source code and editing code. If anyone would like to help out, you're welcome.

Ready for coding

2009-07-15T14:54:16Z

codive will be a filebrowser that displays the folder tree and the files inside the current folder, pretty much like your normal filebrowser.

Unlike filebrowers embedded in GUIs like KDE or microsofts or apples GUIs, codive will display everything in 3D, including the most important thing: source files.

What might at first sound very silly could also be regarded as the "matrix-intro" brought to a real programmer's desktop, only that you don't see strange gibberish but real code.

Your code!

In order to render the 3D environment, codive was originally supposed to use the g3d framework, however that plan has been dropped.

codive will be implemented with the OpenInventor API or rather the Coin3D API. This has several reasons, most notably the ability of Coin3D to render text as stroked lines instead of bitmaps.