You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As described in #22, separating tkimg from ttkthemes would improve platform compatibility, possibly negate issues with loading the library and still provide the possibility for all platforms to load all themes.
My design proposal is as follows:
Build a separate package named tkimg, that provides a function to load the tkimg library into a given Tcl interpreter (belonging to a Tk instance). This package could be installed with an installation parameter.
The themes can be split into two categories: plain GIF-themes, that always can be loaded by Tkinter, and PNG-themes. Currently, only theme arc is PNG-based. Its images should be converted to GIF-format (d2b75c9), then the artifacts should be fixed. Then the following folder structure could be used for the themes:
As described in #22, separating tkimg from ttkthemes would improve platform compatibility, possibly negate issues with loading the library and still provide the possibility for all platforms to load all themes.
My design proposal is as follows:
Build a separate package named
tkimg
, that provides a function to load thetkimg
library into a given Tcl interpreter (belonging to aTk
instance). This package could be installed with an installation parameter.The themes can be split into two categories: plain GIF-themes, that always can be loaded by Tkinter, and PNG-themes. Currently, only theme
arc
is PNG-based. Its images should be converted to GIF-format (d2b75c9
), then the artifacts should be fixed. Then the following folder structure could be used for the themes:Then, based on whether
TkImg
could be loaded orTk 8.6
is present, eitherpng.tcl
orgif.tcl
is evaluated.Thus, in steps:
TkImg
package and publish to PyPIarc
themeTkImg
fromttkthemes
and implement installation optionTkImg
check forset_theme_advanced
The text was updated successfully, but these errors were encountered: