Issue #8539 has been updated by naruse (Yui NARUSE).


jonforums (Jon Forums) wrote:
> naruse (Yui NARUSE) wrote:
> > jonforums (Jon Forums) wrote:
> > > Is the key issue bit rot (Tcl/Tk 8.6.0 released in 12/2012) in core, or something more strategic like continued interest in pushing as many extensions from core into gems?
> > 
> > Once we had an idea that Ruby distribution should be all-in-one package for every basic use caeses as rosenfeld says in [ruby-core:55533].
> > But now we have rubygems and it is good for libraries which is on different timeline.
> > Therefore we have such reactions.
> 
> I very much support extracting ext/tk into a gem as long as (a) no user loses access to cross-platform Tk GUI functionality, and (b) the gem install for Windows users is as easy as it is with the gtk2 mingw binary gem.

(a) normal gemify would do it
(b) if someone make binary gem, or add install-time downloading tk feature, or Rubyinstaller bundle tk binary gem
----------------------------------------
Feature #8539: Unbundle ext/tk
https://bugs.ruby-lang.org/issues/8539#change-40023

Author: naruse (Yui NARUSE)
Status: Open
Priority: Normal
Assignee: 
Category: ext
Target version: current: 2.1.0


How about unbundling ext/tk from Ruby repository?

ext/tk is a bundled extension library for GUI programming with tk.
It is introduced in 1999 and long maintained with CRuby itself.

But nowadays its maintenance is not so active.
Moreover ext/tk is not the de facto standard over Ruby GUI though it is bundled for 14 years.
(maybe because tk is not de facto of GUI toolkit)
GUI libraries for Ruby should compete in the wilds.

So I propose unbundling ext/tk.
It should be another repository for example on github and people should install it as gem.

How do you think?


-- 
http://bugs.ruby-lang.org/