info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Interest in Tk
149 views
Skip to first unread message
gourin...@gmail.com
Mar 10, 2018, 7:23:30 AM3/10/18
to
Are TCLers developers loosing interest in TK?
Cecil Westerhof
Mar 10, 2018, 9:59:07 AM3/10/18
to
I have, but I just started with Tcl and was until now mostly a back-end
developer, so I have a lot to learn.
--
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof
developer, so I have a lot to learn.
--
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof
Robert Heller
Mar 10, 2018, 10:25:10 AM3/10/18
to
At Sat, 10 Mar 2018 04:23:27 -0800 (PST) gourin...@gmail.com wrote:
>
> Are TCLers developers loosing interest in TK?
I don't think so.
>
> Are TCLers developers loosing interest in TK?
>
--
Robert Heller -- 978-544-6933
Deepwoods Software -- Custom Software Services
http://www.deepsoft.com/ -- Linux Administration Services
hel...@deepsoft.com -- Webhosting Services
Ricardo kozmate.net
Mar 10, 2018, 5:13:49 PM3/10/18
to
Em 10/03/18 12:23, gourin...@gmail.com escreveu:
--
{ricardo from kozmate.net}
> Are TCLers developers loosing interest in TK?
>
Why do you ask?
>
--
{ricardo from kozmate.net}
gourin...@gmail.com
Mar 10, 2018, 5:44:52 PM3/10/18
to
because the TCLers developer are not accepting any improvement of the Tk's documentation, I sent a some suggestions but no answer, I want at leadt add an explanation of the "ptoxy" in panedwindow widget but no answer, before I aked them to group the configure and cget command for normal widget under seperate section as for themed widget but nothing. All of these make me think that you are loosing interest in your toolkit.
You should know that I use Tkinter.
You should know that I use Tkinter.
Rich
Mar 10, 2018, 6:09:44 PM3/10/18
to
gourin...@gmail.com wrote:
[Please quote an appropriate amount of context when replying.]
> because the TCLers developer are not accepting any improvement of the
> Tk's documentation, I sent a some suggestions but no answer, I want
> at leadt add an explanation of the "ptoxy" in panedwindow widget but
> no answer,
>> Date: Wed, 28 Feb 2018 14:12:52 -0800 (PST)
>> Message-ID: <9a34560f-aee3-43a7...@googlegroups.com>
>> Subject: panedwindow - proxy?
>> From: gourin...@gmail.com
>>
>> In panedwindow widget some optoins and commands are about "proxy", what
>> it means?
Proxy question posted Feb. 28. Today is Mar. 10.
That is *at most* nine days of elapsed time from asking here until now.
Nine days is not enough time to decide "but no answer" from individuals
who work on Tk on a *volunteer* basis.
Also, did you actually post an item in the bug tracker, or are you
measuring time from your posting here on Usenet? Because if you are
just measuring from the post here on Usenet, then it is quite possible
the *volunteer* who should see your comment does not read the posting
here at all.
Plus, in general, when dealing with any software created by volunteers,
you will also find that you get a much better (and sometimes faster)
response the more effort you put in up front. I.e., in order:
1) submitting a *demand* (or anything that sounds even remotely like
a *demand* or *command*) that the volunteer do something - likely
ignored entirely
2) submitting a comment that something could be improved with a
change (but with no suggested change) - a bit better than #1, but
any response will likely only occur "when time is available"
3) submitting a comment that something could be improved, with a
suggestion for the alternate change (i.e., supplying the words
that would be the change) - much better than #2, more likely to
get noticed and be acted upon by the volunteer
4) submitting an actual patch to the most current version of the file
in question such that the volunteer merely has to review the
change and choose to commit - best possible submission, very
likely to get noticed, and very likely to get handled first when
time becomes available, and/or for time to be "made available" to
handle it, because the commitment from the volunteer is minimal
here.
Complaining here of no response, after at most nine days, for work from
volunteers, implies the possibility that your submission might have
fallen on the smaller number end of the list above.
[Please quote an appropriate amount of context when replying.]
> because the TCLers developer are not accepting any improvement of the
> Tk's documentation, I sent a some suggestions but no answer, I want
> at leadt add an explanation of the "ptoxy" in panedwindow widget but
> no answer,
>> Message-ID: <9a34560f-aee3-43a7...@googlegroups.com>
>> Subject: panedwindow - proxy?
>> From: gourin...@gmail.com
>>
>> In panedwindow widget some optoins and commands are about "proxy", what
>> it means?
Proxy question posted Feb. 28. Today is Mar. 10.
That is *at most* nine days of elapsed time from asking here until now.
Nine days is not enough time to decide "but no answer" from individuals
who work on Tk on a *volunteer* basis.
Also, did you actually post an item in the bug tracker, or are you
measuring time from your posting here on Usenet? Because if you are
just measuring from the post here on Usenet, then it is quite possible
the *volunteer* who should see your comment does not read the posting
here at all.
Plus, in general, when dealing with any software created by volunteers,
you will also find that you get a much better (and sometimes faster)
response the more effort you put in up front. I.e., in order:
1) submitting a *demand* (or anything that sounds even remotely like
a *demand* or *command*) that the volunteer do something - likely
ignored entirely
2) submitting a comment that something could be improved with a
change (but with no suggested change) - a bit better than #1, but
any response will likely only occur "when time is available"
3) submitting a comment that something could be improved, with a
suggestion for the alternate change (i.e., supplying the words
that would be the change) - much better than #2, more likely to
get noticed and be acted upon by the volunteer
4) submitting an actual patch to the most current version of the file
in question such that the volunteer merely has to review the
change and choose to commit - best possible submission, very
likely to get noticed, and very likely to get handled first when
time becomes available, and/or for time to be "made available" to
handle it, because the commitment from the volunteer is minimal
here.
Complaining here of no response, after at most nine days, for work from
volunteers, implies the possibility that your submission might have
fallen on the smaller number end of the list above.
Francois Vogel
Mar 11, 2018, 5:33:43 PM3/11/18
to
Le 11/03/2018 à 00:09, Rich a écrit :
> Nine days is not enough time to decide "but no answer" from individuals
> who work on Tk on a *volunteer* basis.
>
> Also, did you actually post an item in the bug tracker, or are you
> measuring time from your posting here on Usenet? Because if you are
> just measuring from the post here on Usenet, then it is quite possible
> the *volunteer* who should see your comment does not read the posting
> here at all.
Thanks Rich for your answer. Your patience largely exceeds mine and I
> Nine days is not enough time to decide "but no answer" from individuals
> who work on Tk on a *volunteer* basis.
>
> Also, did you actually post an item in the bug tracker, or are you
> measuring time from your posting here on Usenet? Because if you are
> just measuring from the post here on Usenet, then it is quite possible
> the *volunteer* who should see your comment does not read the posting
> here at all.
admire you. You are absolutely right and I really hope the OP will
understand it.
The OP complainer did not do anything else than asking several times the
same question, here and on tcl-core list, basically just prompting me
for doing something for him for free, and immediately.
I finally did:
https://core.tcl.tk/tk/tktview/3e490c13869
The other option was to put him in my kill file.
F.
gourin...@gmail.com
Mar 11, 2018, 6:13:10 PM3/11/18
to
I never thought that what I did is so AWFUL :-(, my sincere MY APOLOGISES, but may be your rules are not the same as in Python mailing list , in addition it is the first time I learn about your "Ticket" and I never thought that to ask something I have to pay. I repeat my apologise, but in other way it express my attachement to your toolkit and I made I great effort to translate your tk documentation to python (tkinter-manual.blogspot.com).
I am shamed when I saw your answer.
I am shamed when I saw your answer.
Gerald Lester
Mar 11, 2018, 10:35:49 PM3/11/18
to
On 03/11/2018 05:13 PM, gourin...@gmail.com wrote:
> I never thought that what I did is so AWFUL :-(, my sincere MY APOLOGISES, but may be your rules are not the same as in Python mailing list , in addition it is the first time I learn about your "Ticket" and I never thought that to ask something I have to pay. I repeat my apologise, but in other way it express my attachement to your toolkit and I made I great effort to translate your tk documentation to python (tkinter-manual.blogspot.com).
>
> I am shamed when I saw your answer.
>
One does not have to pay to ask -- but as has been pointed out
> I never thought that what I did is so AWFUL :-(, my sincere MY APOLOGISES, but may be your rules are not the same as in Python mailing list , in addition it is the first time I learn about your "Ticket" and I never thought that to ask something I have to pay. I repeat my apologise, but in other way it express my attachement to your toolkit and I made I great effort to translate your tk documentation to python (tkinter-manual.blogspot.com).
>
> I am shamed when I saw your answer.
>
elsewhere, the best way is to submit a ticket (free to submit) with a
proposed correction.
--
+----------------------------------------------------------------------+
| Gerald W. Lester, President, KNG Consulting LLC |
| Email: Gerald...@kng-consulting.net |
+----------------------------------------------------------------------+
William J Giddings
Mar 20, 2018, 6:05:44 AM3/20/18
to
Interested in Tk but not used it in a long time.
Most of my work is on the Linux desktop so I use Gnocl. (www.gnocl.org),
fully Gnome compliant.
If I stilled worked on Windoze or Mac then perhaps.
WJG
Most of my work is on the Linux desktop so I use Gnocl. (www.gnocl.org),
fully Gnome compliant.
If I stilled worked on Windoze or Mac then perhaps.
WJG
0 new messages