<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">Am 11.12.2014 um 14:29 schrieb Dmitry
Boyarintsev:<br>
</div>
<blockquote
cite="mid:CAMpTZrd3uxbABCK=_pdHHv=779YT+TH+MjyA8XzABXiOXfO6hg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Thu, Dec 11, 2014 at 1:11 AM,
Hans-Peter Diettrich <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:DrDiettrich2@gmx.de"
target="_blank">DrDiettrich2@gmx.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class=""></span>As I understand that: The components in
the LCL should be available with all supported widgetsets.
An implementation for only one widgetset is not worth of
adding it to the LCL, because it would burden the LCL
maintainers with the implementation for all other
widgetsets.<br>
</blockquote>
</div>
<br>
</div>
<div class="gmail_extra">On the other hand, it pretty much
blocks anyone else to add components to LCL. <br>
Because an author has to introduce a solution for all (or
most?) widgetsets by LCL.<br>
</div>
<div class="gmail_extra">With more widgetsets introduced to LCL,
it might be next to impossible for some developers.<br>
</div>
</div>
</blockquote>
Why not leave it to the LCL maintainers, which controls should be
added to the LCL, and which not? Provide them good reasons for doing
so...<br>
<br>
DoDi<br>
</body>
</html>