Semantic highlight

[mistar]

As for 'bool IsAppStartingUp()' function, shall I provide a patch?

Yes, just do it similar to the IsShuttingDown method. I'm off the next few days - so you have enough time for a patch... Otherwise I can do if I'm back ;-)

Ok, I'll try to do it myself.

@Morten: I'm affraid I've lost in C::B architecture. Please guide me how to do that or do it for me (I think it would take you 5 min or so ).

[MortenMacFly]

@Morten: I'm affraid I've lost in C::B architecture. Please guide me how to do that or do it for me (I think it would take you 5 min or so ).

OK - I've done it and will commit after a few tests... (as this changes the SDK version).

[mistar]

@Morten: I'm affraid I've lost in C::B architecture. Please guide me how to do that or do it for me (I think it would take you 5 min or so ).

OK - I've done it and will commit after a few tests... (as this changes the SDK version).

Thanks!

[mistar]

Hi there.

I observed that whenever I close configuration dialog of C::B all Scintilla's styles are set to those for the built-in syntactic highlighter.
Is there any way to turn off the built-in highlighter when SH is loaded?

[mistar]

@Morten: I'm affraid I've lost in C::B architecture. Please guide me how to do that or do it for me (I think it would take you 5 min or so ).

OK - I've done it and will commit after a few tests... (as this changes the SDK version).

How about these changes? When do you expect them to be commited?

[MortenMacFly]

How about these changes? When do you expect them to be commited?

They are in head now, with the limitations I mentioned. Tell me when thee is new stuff to test.

[mistar]

Hi guys!
It's a long time since my last post
Sources of not-crashing plugin attached (maybe I'll find time to make some hg repository for future;))
Play with it and tell me what you think.
BUT!
* no config dialog so far
* if you go to editor settings and then back, the color scheme will revert to the C::B settings
   (how to turn this off???)
* I don't handle changes in project/build target settings and active build target changes (work in progress)
* due to some clang issues, there could be still places not colored properly (I've filed bugs for this)
* as usual, you need libclang installed (llvm and clang svn versions work fine for me; also remember to change
   linker options!)
* tested with C::B (rev 8836) SDK v1.15.0.
* [EDIT:] you need gcc >=4.6 with -std=c++0x or -std=c++11, or some other compiler supporting basic C++11 ('auto' and simple lambdas)

To handle options changes I need to know
* when project options are changed (what if I modify only build target options? Do I get cbEVT_PROJECT_OPTIONS_MODIFIED also?)
* when active build target is changed (that is set, not modified) -- what event should I use?

Enjoy!

[Alpha]

* no config dialog so far

I recently tested with providing semantic highlighting by hooking into the Scintilla lexer.  Pros: seamlessly integrates into the pre-existing highlighting settings.  Cons: the patch there is currently not usable (due to some sort of thread lock, I think, when you start typing).

[mistar]

Great!
But... how about the new C++11 standard? My plugin inherits C++11 support from clang,
which is quite decent. And what about errors in code? As you type, there are plenty of them...
Colors is a minor issue in my plugin; but clearly I need my own color config panel
because it has to be richer (semantic highlight has a lot more styles).
I think of using color scheme extending syntactic one, but I don't know whether it is possible
to control syntactic scheme in SDK.

[daniloz]

Yes, please, I want to see screenshots! 

[mistar]

Oh... I forgot: you need gcc >=4.6 with -std=c++0x or -std=c++11 to compile the plugin (or other compiler supporting 'auto' and simple lambdas).

[oBFusCATed]

Oh... I forgot: you need gcc >=4.6 with -std=c++0x or -std=c++11 to compile the plugin (or other compiler supporting 'auto' and simple lambdas).

Do you have any plans to remove all these c++11 things in the future, because some of us are stuck on older distros, which have only gcc-4.1 or gcc-4.4?

[mistar]

Oh... I forgot: you need gcc >=4.6 with -std=c++0x or -std=c++11 to compile the plugin (or other compiler supporting 'auto' and simple lambdas).

Do you have any plans to remove all these c++11 things in the future, because some of us are stuck on older distros, which have only gcc-4.1 or gcc-4.4?

Hmm... I probably could... and I'll try.

But... Do you have any plans to migrate to *newer* versions of gcc in the future?
4.6 is already stable
I recommend using C++11 features (e.g. rvalue references) that allow for cleaner and faster code.

[oBFusCATed]

But... Do you have any plans to migrate to *newer* versions of gcc in the future?

Yes, gcc4.4.6 will be my next gcc. Unfortunately if you're doing commercial software you have to work on older distros.

[mistar]

The code without c++0x features attached.
One more thing to config: in file CompileOptions.cpp change
#define GCC_VERSION_STR "4.6.3"
to your version (it is used in a workaround for clang using libstdc++).

And don't try to close editors while there are pending changes...
I'm working on it

EDIT: fixed crashes on editor close.