"jcc7" <technocrat7@gmail.com> wrote in message news:f9f7oc$2ovj$1@digitalmars.com...
<snip>
> It's been mentioned on the wiki page at
> http://www.prowiki.org/wiki4d/wiki.cgi?WindowsAPI, but I think you're right that
> it's not in the "Translation instructions" section (and it probably should be there).
>
> I get the feeling that the WindowsAPI page at Wiki4D has gotten way too big to be
> efficient. I think that it should probably be split into subpages, but I would be
> afraid of stepping on the toes of the WindowsAPI team by doing it myself.

It probably could be split, though I'm not sure what would be the best approach.

> (Also, I wonder if it would work better to store the content that's current at
> Wiki4D in the bindings wiki instead [http://www.dsource.org/projects/bindings],
> since it is part of the bindings project and dsource wikis have a cool way of
> formatting D source code.)
<snip>

Maybe that would be a good idea.  I haven't used Dsource's wiki engine much - how does it compare to prowiki?  At least it seems able to show arbitrary versions of  a page like MediaWiki, rather than just the current version and the most recent edit.

Stewart. 

"Michael Butscher" <mbutscher@gmx.de> wrote in message news:MPG.21268ee9722f11e99896a9@news.digitalmars.com...
<snip>
> At least there should be only one place for the instructions. Currently
> there exists also a readme file in the SVN-repository with similar
> instructions.

They're meant to be the same, but probably have got a bit out of sync.

> Either the file should point to the wiki page(s) or vice versa.
<snip>

Having it in the SVN at least means that we have access to a revision history of the instructions.  But migrating it onto the Dsource wiki would be one way to avoid losing this.  Good thinking, whosever idea this was!

Stewart. 

"jcc7" <technocrat7@gmail.com> wrote in message news:f9hu7a$2j79$1@digitalmars.com...
<snip>
> I don't know how the people API project are talking to each other. I assumed it
> was via the wiki page, but for all I know they could be using IRC, AIM, or an
> e-mail mailing list. I was just trying to make the point that apparently it
> doesn't matter if anyone posts in the bindings forum because the people who might
> want to know that information don't seem to even be reading that forum.
<snip>

It is mostly via the wiki page and these newsgroups.  The problem is that not enough people are working on it, and those that do tend to disappear after a while.

Stewart. 

"Justin C Calvarese" <technocrat7@gmail.com> wrote in message news:f9lsdf$m5b$1@digitalmars.com...
> Michael Butscher wrote:
<snip>
>> The start page of the bindings project wiki has a link to the Wiki4D page, so the "WindowsAPI" page seems to be "official".
>
> Actually, I was the one who added that link, but it's been over a year, so if anyone objected, I hope they would've corrected it by now. ;)
> http://www.dsource.org/projects/bindings/wiki/WikiStart?action=diff&version=6&old_version=5

The page on Wiki4D is indeed the official one at the moment.

Stewart. 

== Quote from Stewart Gordon (smjg_1998@yahoo.com)'s article
> "jcc7" <technocrat7@gmail.com> wrote in message
> news:f9f7oc$2ovj$1@digitalmars.com...
> <snip>
> > It's been mentioned on the wiki page at
> > http://www.prowiki.org/wiki4d/wiki.cgi?WindowsAPI, but I think you're
> > right that
> > it's not in the "Translation instructions" section (and it probably should
> > be there).
> >
> > I get the feeling that the WindowsAPI page at Wiki4D has gotten way too
> > big to be
> > efficient. I think that it should probably be split into subpages, but I
> > would be
> > afraid of stepping on the toes of the WindowsAPI team by doing it myself.
> It probably could be split, though I'm not sure what would be the best approach.
> > (Also, I wonder if it would work better to store the content that's
> > current at
> > Wiki4D in the bindings wiki instead
> > [http://www.dsource.org/projects/bindings],
> > since it is part of the bindings project and dsource wikis have a cool way
> > of
> > formatting D source code.)
> <snip>
> Maybe that would be a good idea.  I haven't used Dsource's wiki engine
> much - how does it compare to prowiki?  At least it seems able to show
> arbitrary versions of  a page like MediaWiki, rather than just the current
> version and the most recent edit.

If you click on the "Archive" link, it will show you more versions, but you're right that Trac does keep track of edits more thoroughly.

As you noticed, Trac keeps all of the version of a file as it's changed (and it always keeps track of who changed it, too). On the other hand, I haven't quite been able to figure out how often ProWiki saves a version in the archive or even if they're saved permanently. And with ProWiki, it can be difficult to determine who changed what.

Trac is really good at formatting D code automatically (for an example, see: http://www.dsource.org/projects/tutorials/wiki/PrintfExample). By the way, the old formatter that I had worked on has been replaced with a much cooler formatter that is Pygments-based.

Trac allows you to get an RSS feed of project events (such when people change wiki pages and when SVN changes are committed). ProWiki will also give an RSS feed (which I think will even let you restrict your news to a particular page), but I think it's helpful to have the SVN changes and the wiki changes in the same feed. (I've been using RSS to watch that no one is being mischievous in the Tutorials project for a while.)

Also, every wiki engine seems to have it's own flavor of wiki syntax, of course, but you probably already realized that.

I think that using the Trac wiki pages would make more sense that using the ProWiki page. It probably would take a little time to change the pages from ProWiki syntax to   Trac wiki syntax, but I don't think it'd be that bad. And you wouldn't have to change all of the content at once. You could move one section of the page, then delete it from ProWiki, and so on. I'd even help you if you want.

Stewart Gordon wrote:
> "Michael Butscher" <mbutscher@gmx.de> wrote in message news:MPG.212522dc134a28d69896a8@news.digitalmars.com... <snip>
> > This might be an indication that this part of the headers is currently not used widely (maybe by some people changing their copy of the headers privately). But the published version definitely can't work.
> 
> Which headers - std.c.windows or my project?

I meant your headers. The std.c.windows headers work.


> And if people are creating private forks of my project, why?  True, it's PD, so who's to stop them, but what's to gain by doing this instead of contributing to the project?

Well, laziness is part of human nature.

First one should ask if the changes made privately were done in the right way to not produce chaos in the repository.

One has to find the subversion URL (I really had some problems with this step), check out the files, change it, check if the testcompile script works (which it didn't in the past due to, AFAIR d3d9.d) and finally commit the changes.


[...]
> >> Also, maybe this question is better suited in the Bindings project Dsource forum?
> >
> > You are right. I only found forums a bit impractical, but that's not a good argument.
> 
> And I don't tend to read the Dsource forums....

With the bindings forum there is also the additional problem that it is used by multiple subprojects and one has to guess by subject line if the topic belongs to Windows bindings or something else.



Michael