ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> scintilla-interest
scintilla-interest
Re: [scintilla] UltraLex.cxx - The final lexer?
by Neil Hodgson other posts by this author
Feb 28 2004 10:28PM messages near this date
Re: [scintilla] UltraLex.cxx - The final lexer? | Re: [scintilla] UltraLex.cxx - The final lexer?
Mike:


>  Very well put, lots of times I have been referred to look at Scite's
>  source, only to have my eye begin to water and I realize that find/replace
>  or whatever is interwoven to the point that it would be difficult to
>  extract.

   Yes, and that is difficult to work around. With a richer calling
environment, it may be reasonable to provide a base find/replace dialog that
could be subclassed by the application. Even with the component technologies
used in Scintilla this is possible but it would be quite a large job to
produce something worth using. Another candidate here would be a style
definition UI.

>  Here's what I'm faced with. Here are my choices:
>  ...
>  3) Work with you to try and extract and encapsulate Scite logic to be
>  reused in Scintilla

   I am very demanding in ensuring Scintilla doesn't include low quality or
badly thought through code. I certainly won't include SciTE's current
automatic line indentation.

>  4) Go ahead and spend the money and purchase another Control, with
>  Numerical Studio's ProgramEdit being the control of choice, after all $49
>  dollar is less that an hours work at my billiing, this option makes the
>  most choice, however Sctinlla is well tested.

   You should never use an open source component in a commercial project on
the basis of cost as developer time is far too expensive.

>  So how much work would it be for us to get the Find, Search/Replace,
>  HTML/RTF export, smart indent, Print and Print Preview, split views, ect
>  into scintilla?

   The question for me is whether I will be able to maintain Scintilla with
these added features. I don't think so, so my preference is for these to go
into an extended control that is maintained by someone else.

>  Months I would imagine, and then I'm faced with the
>  orignal reason I posted this thread, lexers are written for specific
>  languages, you cannot roll your own,

   Of course you can roll your own lexer by writing it in whatever language
you are using for your application.

>  I think it would be possible for Scintilla to do all that ProgramEdit does
>  but it would take an initiative, a grass roots effort to create "Son of
>  Scintilla" but it would basically put these guys all out of business which
>  in way would be interesting.

   It is not my goal to put anyone out of business. I hope to see continued
improvement in commercial editing components. Scintilla will continue to be
useful where its features or quality are better, where source code is
wanted, and where the deliverable will also be open source. As a competitor
to commercial products, it can act as a minimum level of functionality these
products should meet. It can even be a source of code for them.

   Neil

_______________________________________________
Scintilla-interest mailing list
Scintilla-interest@[...].org
http://mailman.lyra.org/mailman/listinfo/scintilla-interest
Thread:
Philippe Lhoste
Neil Hodgson


Privacy Policy | Email Opt-out | Feedback | Syndication
© ActiveState Software Inc. All rights reserved