Re: Integrating Scite as an inlined Win32 child window (in a loadable DLL)

Hello Neil

Thank you for taking the time out of your workday to respond to my basic 
(exploratory) questions. That is much appreciated. 

> SciTE doesn’t really see that many substantial changes, with most updates 
occurring in Lexilla and Scintilla which are already quite separate.

That will leave the biggest, lasting impression on me for the long term. 
Having read through the change logs I had some concern about keeping ahead 
of future code changes. I've come to learn that it is all too easy to 
ignore code revisions then get into a pickle when needing to integrate 
years of neglected changes :-) Your comment is good to hear and I will keep 
that in mind for the future. 

> Producing a ’SciTE control’ is something I have actively avoided as it 
appears to be a large open-ended project. 

Just to be clear, I had no intention nor undue expectations of using SciTE 
as a control. That would be nice but I didn't expect to have the luxury of 
a quick "DLL" or ActiveX integration. On the flip side, the Visual Studio 
compilation was so utterly mindless as otherwise I was expecting to piece 
together a complex build process. At most, I just wanted to pick your brain 
for a few minutes just in case you had some "What I would do myself" series 
of comments. 

> Making the menus and toolbar more customizable would be a good direction 
with definitions in text files....

Actually, that is a very good idea. That did not come to mind until you 
mentioned it. Win32 menu customization isn't too hard to implement. I will 
keep that in mind as that would allow me to keep SciTE "fairly intact" 
without having to go into the source code and customize it too much. 

> The first decision here is whether the SciTE instance in your app will be 
a second window or will be embedded in an application window.

From my perspective, it will hopefully keep your code as-is except for (1) 
no WinMain and (2) parenting your window into one of my docking windows and 
(3) using my own message pump. I just want to keep all of those changes to 
a complete minimum, purely for long term code maintenance and merging with 
your addendums.

Thank you again for your comments. I'll try to pursue this integration in 
the near future. It was wonderful to come across SctiTE as otherwise I 
should have known more about it decades ago!

On Sunday, March 13, 2022 at 7:05:07 PM UTC-4 Neil Hodgson wrote:

> Rockwood Premiere:
>
> Producing a ’SciTE control’ is something I have actively avoided as it 
> appears to be a large open-ended project. There are limits to my ambition 
> and workload.
>
> > This will better suit Neil's constant code updates. It would run 
> in-lined within my app as a basic editor (DLL), mostly for myself to use.
>
>
> SciTE doesn’t really see that many substantial changes, with most updates 
> occurring in Lexilla and Scintilla which are already quite separate.
>
> > On the other hand, for example, in 2mins of review I've seen that 3ds 
> Max had modified/tweaked Scite's menus and probably other aspects of the 
> code. I'd be fine with doing that but I want to make future code 
> maintenance manageable as Neil makes new releases.
>
> Making the menus and toolbar more customizable would be a good direction 
> with definitions in text files instead of platform-specific resource 
> description or C++ source files. It should be possible for a user or 
> packager to take the menus or toolbar, as defined in a text file, change it 
> and point to the changed version with a property. There could even be an 
> augmentation protocol allowing menus, menu items, and toolbar buttons to be 
> added with a SciTEUserMenu.properties that would avoid reapplying 
> customization after updates.
>
> There may be reasonable changes that can be made to SciTE to make it 
> easier to host some portion like wSciTE or wContent within a host window or 
> as a second window in an application. The first decision here is whether 
> the SciTE instance in your app will be a second window or will be embedded 
> in an application window.
>
> Since adding side bars and similar are common desires, there could be an 
> extension point to allow this.
>
> Neil
>
>

-- 
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/scite-interest/d2ba3322-c853-48e1-b3b8-e93b6da37baan%40googlegroups.com.