On 1/10/14 5:26 AM, Sönke Ludwig wrote:
> Am 10.01.2014 13:31, schrieb Gary Willoughby:
>> On Friday, 10 January 2014 at 10:26:54 UTC, Gary Willoughby wrote:
>>> On Friday, 10 January 2014 at 09:27:39 UTC, Jacob Carlborg wrote:
>>>> On 2014-01-10 10:21, Gary Willoughby wrote:
>>>>> Does the dub registry at code.dlang.org have problems?
>>>>>
>>>>> I registered two new packages yesterday and they are still not included
>>>>> in the registry. It's annoying that registering or updating existing
>>>>> packages take ages to be reflected on code.dlang.org.
>>>>
>>>> I can see that x11 was added/updated yesterday. Note that projects
>>>> with a version tag is sorted first.
>>>
>>> I also have another package waiting called 'tcltk' which hasn't been
>>> added yet and now all my packages in the UI have the following error:
>>>
>>> Failed to get GIT tags/branches: Failed to get tags: Failed to read
>>> JSON from https://api.github.com/repos/nomad-software/x11/tags:
>>> Unexpected reply for
>>> 'https://api.github.com/repos/nomad-software/x11/tags': Forbidden
>
> This most probably indicates that the API request limit for GitHub was reached. It will be reset on
> the next hour after that happens. The limit can be increased by registering code.dlang.org as a
> GitHub application, but that needs an OAuth client implementation first. Implementing a clear error
> message in this case would of course also be a good first step. Any contributions are welcome there!

OAuth is only needed if you need to perform actions as someone else.  Otherwise your own account creds are sufficient to be able to do 5000 queries an hour rather than the unauth'ed limit of 60 an hour.

On Friday, 10 January 2014 at 12:47:54 UTC, Andrej Mitrovic wrote:
> On 1/10/14, Gary Willoughby <dev@nomad.so> wrote:
>> I also have another package waiting called 'tcltk' which hasn't
>> been added yet and now all my packages in the UI have the
>> following error:
>
> Hi,
>
> I have a D OOP Tk wrapper which I paused working on for a while since
> I had other plans at the moment. Currently it only works on Win32 (I
> didn't have the time to work on enabling it on other platforms yet)
> but it has lots of features and tests too:
> https://github.com/AndrejMitrovic/dtk/
>
> I'm not home right now though (~ next 3 weeks), so I can only
> periodically check the e-mail every now and then.

Actually, i'd be more than interested to learn how you support X11 (on which tcl/tk depends) on Windows?

Am 10.01.2014 21:10, schrieb Gary Willoughby:
> On Friday, 10 January 2014 at 12:47:54 UTC, Andrej Mitrovic wrote:
>> On 1/10/14, Gary Willoughby <dev@nomad.so> wrote:
>>> I also have another package waiting called 'tcltk' which hasn't
>>> been added yet and now all my packages in the UI have the
>>> following error:
>>
>> Hi,
>>
>> I have a D OOP Tk wrapper which I paused working on for a while since
>> I had other plans at the moment. Currently it only works on Win32 (I
>> didn't have the time to work on enabling it on other platforms yet)
>> but it has lots of features and tests too:
>> https://github.com/AndrejMitrovic/dtk/
>>
>> I'm not home right now though (~ next 3 weeks), so I can only
>> periodically check the e-mail every now and then.
>
> Actually, i'd be more than interested to learn how you support X11 (on
> which tcl/tk depends) on Windows?

Tcl/Tk is also native on Windows, why the X11 question?

On Friday, 10 January 2014 at 20:31:04 UTC, Paulo Pinto wrote:
> Am 10.01.2014 21:10, schrieb Gary Willoughby:
>> On Friday, 10 January 2014 at 12:47:54 UTC, Andrej Mitrovic wrote:
>>> On 1/10/14, Gary Willoughby <dev@nomad.so> wrote:
>>>> I also have another package waiting called 'tcltk' which hasn't
>>>> been added yet and now all my packages in the UI have the
>>>> following error:
>>>
>>> Hi,
>>>
>>> I have a D OOP Tk wrapper which I paused working on for a while since
>>> I had other plans at the moment. Currently it only works on Win32 (I
>>> didn't have the time to work on enabling it on other platforms yet)
>>> but it has lots of features and tests too:
>>> https://github.com/AndrejMitrovic/dtk/
>>>
>>> I'm not home right now though (~ next 3 weeks), so I can only
>>> periodically check the e-mail every now and then.
>>
>> Actually, i'd be more than interested to learn how you support X11 (on
>> which tcl/tk depends) on Windows?
>
> Tcl/Tk is also native on Windows, why the X11 question?

Because the Tk headers also import the X11 headers.

Am 10.01.2014 21:32, schrieb Gary Willoughby:
> On Friday, 10 January 2014 at 20:31:04 UTC, Paulo Pinto wrote:
>> Am 10.01.2014 21:10, schrieb Gary Willoughby:
>>> On Friday, 10 January 2014 at 12:47:54 UTC, Andrej Mitrovic wrote:
>>>> On 1/10/14, Gary Willoughby <dev@nomad.so> wrote:
>>>>> I also have another package waiting called 'tcltk' which hasn't
>>>>> been added yet and now all my packages in the UI have the
>>>>> following error:
>>>>
>>>> Hi,
>>>>
>>>> I have a D OOP Tk wrapper which I paused working on for a while since
>>>> I had other plans at the moment. Currently it only works on Win32 (I
>>>> didn't have the time to work on enabling it on other platforms yet)
>>>> but it has lots of features and tests too:
>>>> https://github.com/AndrejMitrovic/dtk/
>>>>
>>>> I'm not home right now though (~ next 3 weeks), so I can only
>>>> periodically check the e-mail every now and then.
>>>
>>> Actually, i'd be more than interested to learn how you support X11 (on
>>> which tcl/tk depends) on Windows?
>>
>> Tcl/Tk is also native on Windows, why the X11 question?
>
> Because the Tk headers also import the X11 headers.

I used to be an heavy Tcl/Tk user on Windows NT/2000 during 1999 - 2001.

Tk only imports X11 on UNIX platforms.

http://core.tcl.tk/tk/tree?ci=tip

--
Paulo

On Friday, 10 January 2014 at 20:57:51 UTC, Paulo Pinto wrote:
> I used to be an heavy Tcl/Tk user on Windows NT/2000 during 1999 - 2001.
>
> Tk only imports X11 on UNIX platforms.
>
> http://core.tcl.tk/tk/tree?ci=tip
>
> --
> Paulo

Looking at tk.h i see this:

#ifndef _XLIB_H
#   if defined(MAC_OSX_TK)
#	include <X11/Xlib.h>
#	include <X11/X.h>
#   else
#	include <X11/Xlib.h>
#   endif
#endif

Which intimates to me that all platforms include it? Then tkDecls.h uses types that the X11 headers define, e.g (XColor):

EXTERN int Tk_CanvasPsColor(Tcl_Interp *interp, Tk_Canvas canvas, XColor *colorPtr);

Am 10.01.2014 22:16, schrieb Gary Willoughby:
> On Friday, 10 January 2014 at 20:57:51 UTC, Paulo Pinto wrote:
>> I used to be an heavy Tcl/Tk user on Windows NT/2000 during 1999 - 2001.
>>
>> Tk only imports X11 on UNIX platforms.
>>
>> http://core.tcl.tk/tk/tree?ci=tip
>>
>> --
>> Paulo
>
> Looking at tk.h i see this:
>
> #ifndef _XLIB_H
> #   if defined(MAC_OSX_TK)
> #    include <X11/Xlib.h>
> #    include <X11/X.h>
> #   else
> #    include <X11/Xlib.h>
> #   endif
> #endif
>
> Which intimates to me that all platforms include it? Then tkDecls.h uses
> types that the X11 headers define, e.g (XColor):
>
> EXTERN int Tk_CanvasPsColor(Tcl_Interp *interp, Tk_Canvas canvas, XColor
> *colorPtr);


Yes, but if you cared to look at the rest of the code, you would have seen that those X11 calls are mapped to Win32 ones.

Maybe I should have expressed myself better.

--
Paulo

On Friday, 10 January 2014 at 22:07:41 UTC, Paulo Pinto wrote:
> Am 10.01.2014 22:16, schrieb Gary Willoughby:
>> On Friday, 10 January 2014 at 20:57:51 UTC, Paulo Pinto wrote:
>>> I used to be an heavy Tcl/Tk user on Windows NT/2000 during 1999 - 2001.
>>>
>>> Tk only imports X11 on UNIX platforms.
>>>
>>> http://core.tcl.tk/tk/tree?ci=tip
>>>
>>> --
>>> Paulo
>>
>> Looking at tk.h i see this:
>>
>> #ifndef _XLIB_H
>> #   if defined(MAC_OSX_TK)
>> #    include <X11/Xlib.h>
>> #    include <X11/X.h>
>> #   else
>> #    include <X11/Xlib.h>
>> #   endif
>> #endif
>>
>> Which intimates to me that all platforms include it? Then tkDecls.h uses
>> types that the X11 headers define, e.g (XColor):
>>
>> EXTERN int Tk_CanvasPsColor(Tcl_Interp *interp, Tk_Canvas canvas, XColor
>> *colorPtr);
>
>
> Yes, but if you cared to look at the rest of the code, you would have seen that those X11 calls are mapped to Win32 ones.
>
> Maybe I should have expressed myself better.
>
> --
> Paulo

I might be a bit tired here but i'm still not understanding what you mean. In tk.h, X11 is included for all platform AFAICS and the X11 types are use for many cross-platform functions parameters.

Am 10.01.2014 19:18, schrieb Brad Roberts:
> OAuth is only needed if you need to perform actions as someone else.
> Otherwise your own account creds are sufficient to be able to do 5000
> queries an hour rather than the unauth'ed limit of 60 an hour.
>

Good to know, I'll create a dummy account and test/implement that when I get some time (and nobody beats me to it ;)

On Friday, 10 January 2014 at 22:07:41 UTC, Paulo Pinto wrote:
> Am 10.01.2014 22:16, schrieb Gary Willoughby:
>> On Friday, 10 January 2014 at 20:57:51 UTC, Paulo Pinto wrote:
>>> I used to be an heavy Tcl/Tk user on Windows NT/2000 during 1999 - 2001.
>>>
>>> Tk only imports X11 on UNIX platforms.
>>>
>>> http://core.tcl.tk/tk/tree?ci=tip
>>>
>>> --
>>> Paulo
>>
>> Looking at tk.h i see this:
>>
>> #ifndef _XLIB_H
>> #   if defined(MAC_OSX_TK)
>> #    include <X11/Xlib.h>
>> #    include <X11/X.h>
>> #   else
>> #    include <X11/Xlib.h>
>> #   endif
>> #endif
>>
>> Which intimates to me that all platforms include it? Then tkDecls.h uses
>> types that the X11 headers define, e.g (XColor):
>>
>> EXTERN int Tk_CanvasPsColor(Tcl_Interp *interp, Tk_Canvas canvas, XColor
>> *colorPtr);
>
>
> Yes, but if you cared to look at the rest of the code, you would have seen that those X11 calls are mapped to Win32 ones.
>
> Maybe I should have expressed myself better.
>
> --
> Paulo

I understand that the X11 calls will be translated to the Win32 Api on Windows in the Tk source but i was talking about the headers.

I think i have found the problem.

At first glance dub seems to dumbly compile *everything* in the source directory whether it's imported or not and in this case that's a problem. In a few of the X11 D source files, C macros are substituted using functions which call other X11 functions which the linker then cannot resolve.

If i compile using the command line on Windows then only x.d and xlib.d are in fact compiled which have no calls to any X11 function so there are no linker errors regarding X11.

Now i just need to understand linking tcl/tk on windows using the optlink linker but that's a new thread :) http://forum.dlang.org/thread/xbrciixzdwkoysnnymht@forum.dlang.org