[Bf-committers] Syntax Highlighting & Alternate Languages

François T. francoistarlier at gmail.com
Wed Jul 27 14:45:40 CEST 2011


hum I guess that's what meant Sergey with Scintilla :p my bad !!!



2011/7/27 François T. <francoistarlier at gmail.com>

> I have been using Notepad++ a lot in my previous company, and we were using
> LUA with custom function, and it was really easy to add as well. Our program
> at compile time was generating the needed XML, and put it in the notepad++
> folder. It was very handy indeed.
> I think notepad++ is based on scintilla as well !!!
>
> And actually I wonder if Blender couldn't reload external file
> automatically each time it as been saved on the harddrive, so we could use
> it external editor ? Even sending a hint to Blender via python maybe to run
> the script ?
>
> cheers,
>
> F.
>
>
>
> 2011/7/27 Tom Edwards <contact at steamreview.org>
>
>> There's no reason to keep the keywords list as a Python var. Who needs
>> constant access to it? It can be converted to a native C
>> vector/array/whatever immediately. Any highlighting extension that isn't
>> scriptable isn't worth doing IMO.
>>
>> On 27/07/2011 9:25, Benjamin Tolputt wrote:
>> > I'm pretty sure that putting the parsing code into the Python layer
>> > would slow the syntax highlighting code quite dramatically and, as
>> > such, is not likely to get the core team approval (let alone be
>> > appreciated by the users). I like the idea of that kind of
>> > flexibility, but the code is currently quite low level & speedy
>> > (integer comparisons from a char array). The speed hit to jump up to
>> > Python (with the string passing, Python string comparisons, and return
>> > path) is most likely going to rule this out almost completely. That
>> > said, in terms of the priority request, I'm willing to do the
>> > low-level code stuff myself. This isn't a request for other developers
>> > to code something for me, it is a request to pre-check whether it is
>> > worth putting the code together myself. It is contained in perhaps two
>> > files, there are no changes to the API required, and it is very close
>> > to a copy/paste job with alternate means of detecting comments,
>> > strings, and special strings. The changes are small, there is no
>> > performance penalty, and the upside is (for people like myself) quite
>> > high. If I cannot get approval for this - I don't think integrating
>> > Python would be worth mentioning ;)
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
>>
>
>
>
> --
> ____________________
> François Tarlier
> www.francois-tarlier.com
> www.linkedin.com/in/francoistarlier
>



-- 
____________________
François Tarlier
www.francois-tarlier.com
www.linkedin.com/in/francoistarlier


More information about the Bf-committers mailing list