StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13212877
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-11-03T19:51:08.967
FavoriteCount
0
LastActivityDate
2012-11-03T19:56:49.183
LastEditDate
2012-11-03T19:56:49.183
LastEditorUserId
401257
OwnerUserId
401257
ParentId
10371965
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I found it a bit daunting when i started with my lexer but everything boils down to a few important ideas: <ul> <li>Put lexer in lexer folder</li> <li>Tell scintilla about the lexer you added</li> <li>Add your constants to scintilla.iface</li> <li>Tell scintilla about your own Constants (if you use any)</li> <li>Code/Compile + Repeat until satisfied</li> </ul> An actual example is: After you create your Lexer Template you name it LexNEW.cxx <ul> <li>Put LexNew.cxx in <code>/lexers</code> folder</li> <li>Enter in <code>/src</code> and run <code>LexGen.py</code>, this tells scintilla that there is a new lexer by adding it to Scintilla.h</li> </ul> Now you add your constants to the .iface file. The most important ones are: <code>val SCLEX_NEW=108</code> where <code>108</code> is an unused id number and <code>lex new=SCLEX_NEW SCE_NEW_</code> where <code>new</code> is a valid unique short identifier for your lexer. Put them in the same sections as the others (to avoid confusion later on) and if in doubt use one of the other definitions as a template! Now below your <code>lex new=</code> line you can define your own constant values like: <pre><code>val SCE_NEW_DEFAULT=0 val SCE_NEW_COMMENTLINE=1 val SCE_NEW_COMMENTBLOCK=2 val SCE_NEW_ERROR=31 </code></pre> After this step you are almost ready. <ul> <li>Enter in <code>/include</code> and run <code>Hface.py</code> which tells scintilla about your new constants.</li> </ul> If your lex code is valid then you are ready to compile. Remember to repeat that last step every time you create a new constant. The <code>HFace.py</code> script adds those values to SciLexer.h which you can do manually if you prefer not to do two steps every time. And thats it my friend after compiled make sure your program sets your lexer with something like: <code>sci.SetLexer(108)</code> and put some colors to each state like <code>sci.StyleSetFore(01, 0x008800) // SCE_NEW_COMMENTLINE</code> and so on. One last thing you will want to use <code>SciLexer.dll</code> which is the one that contains all lexers not <code>scintilla.dll</code> Good luck!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to start a project with Scintilla?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USRaptorX
UserOwnerUserId
1. USRaptorX
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.