Re: Question about html widget



On Fri, Mar 14, 2003 at 10:08:54PM +0000, Sander Vesik wrote:
> Christian Rose wrote:
> > 
> > Isn't that a bit odd, as people are from my understanding of past and
> > present posts moving away from gtkhtml2 [1]?
> > 
> > Maybe I'm misunderstanding a couple of things here, but I just got the
> > feeling of "a11y team keep working on a piece of code everyone else is
> > about to leave behind", and I don't like the idea of that (and
> > subsequent long rants and flames in all directions) happening again.
> > 
> 
> It can roughly be summarised as "Havoc said so, but this does not 
> necessarily make it be true". There haven't essentialy been any important 
> changes to the situation since the last time "lets kill off gtkhtml2" was up.
> 

What makes it true is that gtkhtml2 is unmaintained.  I'm simply
observing the reality, not dictating it.

You want to maintain gtkhtml2 - in its entirety, not just fixing a11y
or other pick-and-choose aspects - please do. If you don't, it's gonna
die as soon as we have a viable alternative. It's exactly the same
situation as zvt.

If someone feels they are the gtkhtml2 maintainer and is committing to
actively working on all important aspects of it going forward, then I
stand corrected and apologize. If no one is going to stand up and say
that, then we have to move to something maintained.

If you can't sell gtkhtml2 as a viable *overall* solution to Mikael
for yelp, then you lose. He's going to use something else and he
should use something else.

People had the fantasy that they could only fix a11y in Zvt but not
maintain/fix it otherwise, and that fantasy was bullshit.  Here the
situation is exactly the same. Someone steps up to maintain the
software, as a whole including crashes/i18n/etc., or as soon as
something else comes along we'll jump, and NO WHINING THIS TIME
because you were damn well warned. ;-)

/me puts out a press release and crossposts to all known lists that 
if gtkhtml2 doesn't get a maintainer it will be dropped

Havoc



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]