I haven't found an editor for povray that I really like yet, and while 
I am competent enough to use the cli I don't really want to deal with it 
so... I am considering writing a povray plugin for kDevelop that could 
support features like:

povray projects
in line documentation
an insert menu
render options

All the other goodies of kDevelop

highlighting(kate already has the setup for povray)
find/replace
diff
perhaps some pov users could even benefit from subversion or cvs support 
to bach work up

	I am inexperienced with the Qt and KDE APIs but they look fairly simple 
and well designed but that means I may not be able to put all the listed 
features in for a while. What I was wondering was if there was any 
support for the idea. I'd like to also what you think about kdevelop (if 
it's too bloated). Or just any support or comments.

oh... and its my first post here so.. hey..

Post a reply to this message

Although KDevelop might be a bit bloated for the job, it's not too 
bloated, IMHO.

You're biggest task IMO would be to beat the usability of emacs and a 
console. One feature that would do this would be a better preview 
window, which included automatic render range selection like in windows.

Insert menu is nice, too. What do you mean with inline documentation? It 
would be very nice to have F1 open the help site for the word under the 
cursor.

I'm not sure I'd have use for advanced project management or diffs, but 
that's just my 2 cents :)

Anyways, I would use it :)

HTH,
Florian

Post a reply to this message

Lee McCuller wrote:
>     I haven't found an editor for povray that I really like yet, and 
> while I am competent enough to use the cli I don't really want to deal 
> with it so... I am considering writing a povray plugin for kDevelop that 
> could support features like:
> 
> povray projects
> in line documentation
> an insert menu
> render options
> 

A few things you should consider:

- KDevelop is not a central component of KDE - most non-programmers 
won't install it - it's not even part of the standard collection when 
building from source with konstruct.

- there are few things possible in KDevelop that are not available in 
Kate and that would be useful for POV-SDL work (except documentation 
integration maybe - see below).

- Documentation integration would indeed be an advantage since for 
KDevelop - you just need a toc file.  With such an index it is no 
problem OTOH to offer documentation lookup from Kate either (like 
already available for full text search on 
http://www.imagico.de/kminpovgui/index.html)

Christoph

-- 
POV-Ray tutorials, include files, Landscape of the week:
http://www.imagico.de/ (Last updated 07 Oct. 2005)
MegaPOV with mechanics simulation: http://megapov.inetart.net/

Post a reply to this message