techlobo wrote:
A working theme builder would be very nice, but accurate (/comprehensive) documentation on the configuration files (and how they relate to the applications, and each other) is essential.
A working 'Thing that must not be named' wouldn't just be nice but very important to get people started.
techlobo wrote:
....Failing that however then some good documentation on how themes work is a must, particularly if you want to encourage more people to get into theme creation!
Well, something like a comprehensive (and comprehensible!) 'user guide to creating themes' inc. full documentation of the configuration files is perhaps an easier option to implement than 'The thing....' and would at least help more advanced users, however, I rather suspect that it still might leave complete theming virgins rather stumped.
techlobo wrote:
I would still vote for a theme section on the forum - but as was concluded last time this was raised, it only works if people engage.
Well, yes, when even a post about theme building results in just two or three people responding and very little interest shown in terms of views you can see that a theme forum would be a complete waste of space, alas.
What would help the whole situation wrt themes and theme creation would, without doubt, be the completion of and public access to the Winstep theme repository, preferably in tandem with the guide to theme building and/or 'The thing....'. The first has been hanging in the air for about three years now if memory serves, and 'The thing....' for considerably longer even.

techlobo wrote:
BTW on a different aspect of the original post
Quote:
If no one gets involved, Jorge, and one day you no longer have the possibility of continuing to take care of Winstep, everything risks collapsing like a house of cards...
- this is likely to be the case anyway. As far as I can tell Jorge is the owner of, and only person with access to, the Winstep source code - so if he no longer provides support then its lifetime is limited anyway!
Well, Winstep is Jorge's life's project and work, in a way you could say his magnum opus, and I think I can safely say that he'd never willingly abandon it. The only way that could happen as far as I could see would be if MS made it practically impossible to support pure Win32 apps. (We already get a foretaste of such a possibility with the latest Windows 11 Insider Beta....) Admittedly, the latter is by no means beyond what MS might get up to at some point - their biggest ambition is to actually move away from the desktop completely eventually, anyway, as the OS itself is no longer a major revenue source and has not been one for quite some time. (The prospect of this could only benefit Linux - there's nowhere else to go. Forget 'The Rotten Fruit', they'd go the same way as MS, and why move from one shite platform to an even more shite one anyway!)
So, in that scenario of cessation of pure Win32 support, it wouldn't help anybody to have access to the Winstep source code. While in general, I have come to favour Open Source software to the fullest, whether that be the 'full Monty' as in the FOSS definition - Free and Open Source Software - free at least in the sense that anybody can use it in any way they like etc. etc., distribute it, and whatever else, though not necessarily by definition free of cost, or just Open Source in that the source can be studied and audited and the like, I don't really think Winstep's code being made Open Source in any way, shape, or form would be beneficial to anyone at any point