https://bugs.kde.org/show_bug.cgi?id=353216

--- Comment #36 from Yichao Yu <yyc1...@gmail.com> ---
> I give up. There are a number of people that would have helped you when I 
> first mentioned this to you four years ago. It's a shame. I won't comment on 
> this anymore.

Since you are making it sound like I intentionally did nothing and asked for no
help I'll make it clear even though I think I'm not really obligated to give an
explaination otherwise.

First, there are times (ok, twice maybe) that I was offered help privately in
terms of actually contributing code but then didn't hear back. I see this both
as a missing opportunity to get it ported and a sign of maybe it is not as
trivial as I thought it was.

Secondly, I've also looked at the help in terms of documentation and the issue,
as mentioned above, is that the complexity from the qtcurve side. I can see
that if one know the qtcurve side of things well, the port shouldn't be very
hard. (In case it is not clear, I did not write the qt4 version of the kwin
theme.) It is trivial to use the template implementation to get something
working while throwing away everything qtcurve currently have. The difficulty
is in large part to figure out what the code in qtcurve is doing and I assume
none of the help are in that area. Note that this is very different from the
widget theme, where basically everything has a 1-1 mapping, the porting is much
more mechanical and fixes afterwards can be done mostly incrementally.

Now those are my accessments, most if not all of the conclusions are actually
scattering among the few comments I've already made above. They may or may not
be accurate but that's what I find and why I determined it is harder than I
want to spend much time on any time soon. If any of the assumptions/findings I
had above are not accurate making this easier than what I thought, I'm
certainly open to constructive suggestions.

> Do you want to close this bug report and mark it as WONTFIX?

No, I've left this open as an acknowledgement that this is a nice to have
feature. This can be close if it doesn't make sense to have, which is not the
case.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to