Re: [as-devel] Re: Themes policy

• Messages sorted by: [ date ][ subject ][ author ]
• Next message: Ethan "[as-devel] Re: Themes policy"
• Previous message: "Re: Themes policy"

Since there are so few current AS themes (at least as published on
as.themes.org and ftp.afterstep.org), disabling backwards compatibility
shouldn't ruffle too many feathers.  (Unlike WM with its 1700+ themes).

I've been working on several themes myself, and was just about to post to
the list regarding the best way to ensure that the themes will work with the
newest development versions of AS.  Then all of a sudden comes the idea of
updating the theme support.  Perfect timing! :-)

-Jordy

>...
>Here's a possibly controversial idea: perhaps we should disable
>backwards compatibility code in the devel version, to encourage people
>to create new-theme-handler compatible themes?  They can then be turned
>back on via a compile time flag (which is by default off) if the user
>really wants/needs compatibility.  If we do this, though, I'd want to
>keep the ETA for 1.8 as short as possible.
>
>----
>Ethan Fischer
>allanon@crystaltokyo.com
>http://members.xoom.com/allanon1

• Next message: Ethan "[as-devel] Re: Themes policy"
• Previous message: "Re: Themes policy"