[Bf-committers] Syntax Highlighting & Alternate Languages

[Benjamin Tolputt]

On 27/07/2011 1:07 PM, Kent Mein wrote:
> It sounds like a good reason to me for it to be included. Assuming it
> doesn't create any conflicts, I don't see any reason why this wouldn't
> be something to include, unless it has some external library
> requirements that makes blender more complicated and or it add's quite
> a bit to the file size. If there are conflicts I'm sure they can be
> worked around.

Well, so long as the syntax highlighting sticks only to the basics
(comments, strings, numbers, built-in variables/functions, and
keywords), it only requires a couple of extra functions in the
text_draw.c file & to use the showsyntax short as an index value as
opposed to a boolean one. The code is actually quite basic, but the core
development team needs to buy into the concept to make it worthwhile.

Quite simply put, there isn't much point in writing the extension if
everyone needs to patch & compile Blender themself. Not everyone has a
native compiler (I would bet a vast majority of users don't) and the
code in question is native, so not just a patch to the Python UI code.
I'm trying to make things easier not just for myself but for everyone
using the Blender text view for alternate scripting languages.

-- 
Regards,

Benjamin Tolputt