Hello Luis,

You are "allowed" to do this, sure, just like (as I believe you know) I
have projects under the PDL namespace that aren't part of PDL itself, such
as PDL::Graphics::Prima. Note, however, that some projects (like DBI) have
policies for modules that add additional things (hence the DBIx namespace).
Have you found any such policy for Tk? It looks like the "Tkx" namespace is
for a different Tk interface, by Gisle Aas, so I guess you wouldn't want to
put it under Tkx::Knob.

In general, these sorts of rules are really just policy preferences
specified by the project owners. They are not enforced by CPAN.

Hope that helps!
David

On Wed, Jul 20, 2016 at 7:48 PM, Luis Mochan <moc...@fis.unam.mx> wrote:

> Dear Lars,
>
> Thanks for the suggestion. However, I just found that there is already a
> Tk::Dial
> widget in cpan (http://search.cpan.org/dist/Tk-Contrib/Dial.pm), but it
> rotates at most 3/4 of a circle. Mine is different, in that it can
> rotate an arbitrary number of turns. So I guess I can't use Dial.
>
> Nevertheless, my worry was about the use of 'Tk::' in my widget, as
> I'm not author nor contributor to the 'Tk' package. Am I allowed to do
> this? (I confess I don't have much experience uploading packages to
> CPAN).
>
> Best regards,
> Luis
>
>
>
> On Thu, Jul 21, 2016 at 12:43:29AM +0200, Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 wrote:
> > I suggest to use "dial", that's the word this widget is most commonly
> > known as. Compare with Qt: <https://google.com/search?tbm=isch&q=qdial>
>
>
>
> --
>
>                                                                   o
> W. Luis Mochán,                      | tel:(52)(777)329-1734     /<(*)
> Instituto de Ciencias Físicas, UNAM  | fax:(52)(777)317-5388     `>/   /\
> Apdo. Postal 48-3, 62251             |                           (*)/\/  \
> Cuernavaca, Morelos, México          | moc...@fis.unam.mx   /\_/\__/
> GPG: 791EB9EB, C949 3F81 6D9B 1191 9A16  C2DF 5F0A C52B 791E B9EB
>
>
>


-- 
 "Debugging is twice as hard as writing the code in the first place.
  Therefore, if you write the code as cleverly as possible, you are,
  by definition, not smart enough to debug it." -- Brian Kernighan

Reply via email to