headers
SourceForge.net | 1 Feb 2007 04:20
Picon
Favicon

[ scintilla-Bugs-1649350 ] ExternalLexer.cxx can't be compiled if __WX__ defined

Bugs item #1649350, was opened at 2007-02-01 03:20
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=102439&aid=1649350&group_id=2439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Scintilla
Group: Bug
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: heromyth (heromyth)
Assigned to: Nobody/Anonymous (nobody)
Summary: ExternalLexer.cxx can't be compiled if __WX__ defined

Initial Comment:
OS: WinXP SP2
Compiler: gcc version 3.4.5 (mingw special)
Others: wxScintilla wxWidgets 2.6.3

Command line:

mingw32-g++.exe -Wall -pipe -mthreads -fmessage-length=0 -fexceptions -Winvalid-pch
-DHAVE_W32API_H -D__WXMSW__ -DWXUSINGDLL -DwxUSE_UNICODE -D__WX__ -DWINVER=0x0400 -DSCI_LEXER
-DLINK_LEXERS -DWXMAKINGDLL_SCI -I ../include -I../src/scintilla/include
-I../src/scintilla/src -IE:\wxWidgets-2.6.3\lib\gcc_dll\mswu -IE:\wxWidgets-2.6.3\include 
-Os -fno-exceptions  -fno-rtti -mno-cygwin -o ExternalLexer.o -c ../src/scintilla/src/ExternalLexer.cxx
(Continue reading)

Permalink | Reply | 1 comment |
headers
Neil Hodgson | 2 Feb 2007 00:12
Picon

Re: [ scintilla-Bugs-1649350 ] ExternalLexer.cxx can't be compiled if __WX__ defined

> Bugs item #1649350, was opened at 2007-02-01 03:20
> Summary: ExternalLexer.cxx can't be compiled if __WX__ defined

   Committed.

   Neil
Permalink | Reply | 0 comments |
headers
EmailJonNOW | 2 Feb 2007 04:42
Picon

Highlighting PHP Class Methods?

Hello, 

I'm new to the lists and to scintilla. Scintilla is definitely a great 
engine and I love that it is multi-platform - this allows me to have the 
same development platform on all the different OSes I work on. I was 
wondering if scintilla had any capability of detecting methods 
($mysqli->query(), $class->method() ) in php and whether API files could be 
written for these methods? It would be good if built-in methods such as in 
mysqli could have autocomplete and APIs. 

Thanks,
Jonathan
Permalink | Reply | 1 comment |
headers
Neil Hodgson | 2 Feb 2007 06:16
Picon

Re: Highlighting PHP Class Methods?

[ This is really about the  SciTE application - Scintilla is the
editing component. SciTE's mailing list is at
http://mailman.lyra.org/mailman/listinfo/scite-interest]

Jonathan:

> wondering if scintilla had any capability of detecting methods
> ($mysqli->query(), $class->method() ) in php and whether API files could be
> written for these methods? It would be good if built-in methods such as in
> mysqli could have autocomplete and APIs.

   SciTE does not do enough analysis to determine the type of a
variable so it can not autocomplete instance methods. Depending on the
language, it may be able to autocomplete static methods, that is
methods that depend on being prefixed by a class name.

   Neil
Permalink | Reply | 0 comments |
headers
Joerg Schneider | 2 Feb 2007 09:18

Requirements for linking external lexer

Hi,

we are using Scintilla as the editor for text and binary data in CrypTool
(www.cryptool.org).

I've developed an external lexer (Windows DLL) to do some highlighting,
which basically works fine.

I had some problems getting it linked. To resolve undefined symbols I had
to add the following file from a scintilla\win32 directory:

WindowAccessor.obj PropSet.obj PlatWin.obj XPM.obj UniConversion.obj

Is this the normal way to link external lexers?

If yes, wouldn't it be nicer to export the required symbols from
scilexer.dll or a separate DLL, which comes with Scintilla?

Cheers,

Jörg
Permalink | Reply | 4 comments |
headers
Robert Roessler | 2 Feb 2007 11:13
Favicon

Re: Requirements for linking external lexer

Joerg Schneider wrote:
> we are using Scintilla as the editor for text and binary data in CrypTool
> (www.cryptool.org).
> 
> I've developed an external lexer (Windows DLL) to do some highlighting,
> which basically works fine.
> 
> I had some problems getting it linked. To resolve undefined symbols I had
> to add the following file from a scintilla\win32 directory:
> 
> WindowAccessor.obj PropSet.obj PlatWin.obj XPM.obj UniConversion.obj
> 
> Is this the normal way to link external lexers?
> 
> If yes, wouldn't it be nicer to export the required symbols from
> scilexer.dll or a separate DLL, which comes with Scintilla?

I originally built and tested the OCaml lexer (LexCaml.cxx) as an 
external lexer, and actually built the DLL *with* PropSet.cxx and 
WindowAccessor.cxx as part of it.  Look at the source (particularly 
the parts conditionally compiled with BUILD_AS_EXTERNAL_LEXER) to see 
how I did it.

Yes, in some ways it indeed seems "nicer" to build Scintilla with a 
much smaller core and most or all of the lexers as externals... but 
then building, distributing, and maintaining everything can become 
something of a nightmare when trying to keep everything working on all 
the platforms supported by Scintilla.

And the people who want (or don't care about) all the lexers coming
(Continue reading)

Permalink | Reply | 0 comments |
headers
Neil Hodgson | 2 Feb 2007 12:39
Picon

Re: Requirements for linking external lexer

Joerg  Schneider:

> I had some problems getting it linked. To resolve undefined symbols I had
> to add the following file from a scintilla\win32 directory:
>
> WindowAccessor.obj PropSet.obj PlatWin.obj XPM.obj UniConversion.obj
>
> Is this the normal way to link external lexers?
>
> If yes, wouldn't it be nicer to export the required symbols from
> scilexer.dll or a separate DLL, which comes with Scintilla?

   The intention was to not require any direct linkage to Scintilla,
hence isolating external lexers from changes in internal classes. Each
of the 4 functions receives flattened 'C' compatible arguments rather
than pointers to classes. You may use Scintilla classes in your
implementation but it should also be possible to implement a lexer in
C or Delphi.

   I don't see much reason for distributing external lexers. If you
are distributing an application that incorporates Scintilla you should
be releasing a tested set of Scintilla and lexers. Static linking
produces more efficient code and there is less to go wrong.

   Neil
Permalink | Reply | 2 comments |
headers
SourceForge.net | 2 Feb 2007 09:45
Picon
Favicon

[ scintilla-Bugs-1650371 ] Scite172:CloseFile? Ping.

Bugs item #1650371, was opened at 2007-02-02 00:45
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=102439&aid=1650371&group_id=2439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Scite172:CloseFile? Ping.

Initial Comment:
Scite172:CloseFile? Ping.

Scite172(clean):WinXp.Pro.Sp2
Just a behavioral note. (patch material?)

When closing a changed file/buffer, there will only be sound ping with the "Save...?" popup when the
closing is initiated with a middle mouse click on the file tab of the file in question.

All other close option, are silent in this respect.
- Window.Menu:File,Close
- shortcut:CTRL+w
(Continue reading)

Permalink | Reply | 0 comments |
headers
SourceForge.net | 2 Feb 2007 15:20
Picon
Favicon

[ scintilla-Feature Requests-1650649 ] Hide the bar under tabs on gtk

Feature Requests item #1650649, was opened at 2007-02-02 06:20
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=352439&aid=1650649&group_id=2439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Hide the bar under tabs on gtk

Initial Comment:
On linux there is a bar with full path under tabs, it would be very nice to have some option to remove this
annoying useles thing.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=352439&aid=1650649&group_id=2439
Permalink | Reply | 0 comments |
headers
Neil Hodgson | 3 Feb 2007 01:19
Picon

Patch for multiline insertion

   There is a patch available on SourceForge which implements the
ability to type into multiple lines by first creating a rectangular
selection. Its unlikely I'll add this without at least a visual
indication with a multiline caret.

https://sourceforge.net/tracker/?func=detail&atid=352439&aid=545068&group_id=2439

   Neil
Permalink | Reply | 0 comments |

Gmane