>> I was wondering if we could use the wiki as a collaborative windows.d
>> editing project?  If everyone was conscientious about it every time
>> you added a delaration to your own local windows.d file you could check
>> the wiki and add it to the windows.d page if it did not exist.  Then you
>> could also periodically cut and paste the code to you own local file to
>> get everyone elses changes.
>
>Sounds like a good idea. Just be careful not to violate Microsoft's copyrights on it.

they could get the information from the Wine project http://www.winehq.com/

"Patrick Down" <pat@codemoon.com> wrote in message news:Xns937C5530F801Bpatcodemooncom@63.105.9.61...
> "Walter" <walter@digitalmars.com> wrote in news:b9v4em$um$1 @digitaldaemon.com:
> > "Patrick Down" <Patrick_member@pathlink.com> wrote in message news:b9u622$23pe$1@digitaldaemon.com...
> >> I was wondering if we could use the wiki as a collaborative windows.d editing project?  If everyone was conscientious about it every time you added a delaration to your own local windows.d file you could check the wiki and add it to the windows.d page if it did not exist.  Then
you
> >> could also periodically cut and paste the code to you own local file to get everyone elses changes.
> > Sounds like a good idea. Just be careful not to violate Microsoft's copyrights on it.
> Yes this is one of the things I was worried about and I'm no expert on the legal issues.  Does any one know anything about this?

I'm not a lawyer, either, but I think you're clear if you rewrite the api in your own words. If you copy Microsoft's comments, etc., I think that's a violation. If somebody has done a GPL'd windows.h, you can modify that one.

BTW, Microsoft was kind enough to grant a license to Digital Mars to use the Microsoft .h files.

Patrick Down wrote:
> 
> In article <b9u0tu$1tv6$1@digitaldaemon.com>, Walter says...
> 
> >> - What is the strategy of extending windows.d into a full
> >>   Win32 interface? (Asking this because bugging Walter with
> >>   "please add this and that" may not be a viable solution...)
> >
> >Just add anything missing as needed.
> 
> I was wondering if we could use the wiki as a collaborative windows.d
> editing project?  If everyone was conscientious about it every time
> you added a delaration to your own local windows.d file you could check
> the wiki and add it to the windows.d page if it did not exist.  Then you
> could also periodically cut and paste the code to you own local file to
> get everyone elses changes.

I'm a wiki enthusiast and really won't mind if someone tried to do this using a wiki page e. g. in Wiki4D ( http://www.prowiki.org/wiki4d/wiki.cgi ).

But I have some doubts, because I think that
  - CVS is the tool for that task
  - the 400+ KB of the windows.d file are a PITA to handle in a wiki page

If someone really want to do it, I think I would have to support it in some kind of sections that can be easily edited and are integrated to the complete file when downloaded. Should be no problem, but has never been done, as far as I know.

--
Helmut Leitner    leitner@hls.via.at Graz, Austria   www.hls-software.com

I know this doesn't help the discussion in this thread, but I've made some changes to get a program working.  Since there is no forum or wiki yet, I wanted to let Walter and Justin know about these changes to win.d and windows.d, and let them discard or accept as they see fit.

I needed to set the current directory (SetCurrentDirectory) as well as loop
thru files (FindFirstFile, FindNextFile) in that directory.  So, my
additions are the following:

-----
windows.d (around line 260, 5/15/2003 version)

alias FindFirstFileA FindFirstFile;
alias FindNextFileA FindNextFile;

-----
win.d (5/14/2003 version)
 - rem'd out 2675 thru 2689 (the struct WIN32_FIND_DATA and aliases)
 - rem'd out 3264 thru 3274
 - rem'd out 3292 thru 3295

 - at end:

/+  -------------------------------------------
 +  from winbase.h
 + -------------------------------------------
 +/

alias SetCurrentDirectoryA SetCurrentDirectory;

extern(Windows)
{
 export
 {

  BOOL SetCurrentDirectoryA(LPCSTR);
  BOOL SetCurrentDirectoryW(LPCWSTR);
 }
}

I am a newbie to D, and hope that I made the right changes to expose these methods to my D app.  In any case, the app works great, and is mind-bogglingly fast.  Any feedback on what I did is welcome.

Cheers,
Brad







"J C Calvarese" <jcc7@cox.net> wrote in message news:b9ubk3$2a08$1@digitaldaemon.com...
> Patrick Down wrote:
> > In article <b9u0tu$1tv6$1@digitaldaemon.com>, Walter says...
> >
> >
> >>>- What is the strategy of extending windows.d into a full
> >>>  Win32 interface? (Asking this because bugging Walter with
> >>>  "please add this and that" may not be a viable solution...)
> >>
> >>Just add anything missing as needed.
> >
> >
> > I was wondering if we could use the wiki as a collaborative windows.d
> > editing project?  If everyone was conscientious about it every time
> > you added a delaration to your own local windows.d file you could check
> > the wiki and add it to the windows.d page if it did not exist.  Then you

> > could also periodically cut and paste the code to you own local file to get everyone elses changes.
>
> I've noticed that many useful Win32 constants, types, and prototypes aren't included in Phobos's windows.d.  Somehow I think we should have a unified effort to either add these to windows.d (if Walter is willing), or develop supplemental headers that work in friendly fashion with Phobos.  A wiki could be a good way to do a collaborative project.
>
> I've come up with 3400+ lines of Win32 symbols that aren't in windows.d (maybe some of them should be).  If you want to use it, just add "import win.d;" in your import section.
>
> You can download my file at: http://www.geocities.com/jccalvarese/d/win.zip
>
> I'm sure my header isn't perfect.  It's not particularly organized.  It may still include conflicts with Phobos.  (I've removed conflicts as I've found them, but they can be hidden.)  If you find any problems with it, let me know and I can try to fix it.
>
> Justin
>

Brad,

Thanks for pointing out the conflicts (oops).  I removed the extra code from win.d.  My line numbers don't seem to  match up with yours--maybe I made some cosmetic changes after I uploaded it.  I also cleaned up some code all over the place.  (I think every time I used "bit" I meant "BOOL".)

I think that the lines you suggested adding to windows.d would work just as well in win.d for the time being, so I hope you won't be offended that I've left my alias's to Find*File in there.  My current strategy is to keep track of the stuff that'd be nice to put in windows.d in win.d.  That way when I install a new release of DMD, I don't lose the changes I made to windows.d.  Now if Walter adds some of this stuff to windows.d, of course I'll remove those items from win.d.

Same download URL, new file: http://www.geocities.com/jccalvarese/d/win.zip

Justin

Brad Anderson wrote:
> I know this doesn't help the discussion in this thread, but I've made some
> changes to get a program working.  Since there is no forum or wiki yet, I
> wanted to let Walter and Justin know about these changes to win.d and
> windows.d, and let them discard or accept as they see fit.
> 
> I needed to set the current directory (SetCurrentDirectory) as well as loop
> thru files (FindFirstFile, FindNextFile) in that directory.  So, my
> additions are the following:
> 
> -----
> windows.d (around line 260, 5/15/2003 version)
> 
> alias FindFirstFileA FindFirstFile;
> alias FindNextFileA FindNextFile;
> 
> -----
> win.d (5/14/2003 version)
>  - rem'd out 2675 thru 2689 (the struct WIN32_FIND_DATA and aliases)
>  - rem'd out 3264 thru 3274
>  - rem'd out 3292 thru 3295
> 
>  - at end:
> 
> /+  -------------------------------------------
>  +  from winbase.h
>  + -------------------------------------------
>  +/
> 
> alias SetCurrentDirectoryA SetCurrentDirectory;
> 
> extern(Windows)
> {
>  export
>  {
> 
>   BOOL SetCurrentDirectoryA(LPCSTR);
>   BOOL SetCurrentDirectoryW(LPCWSTR);
>  }
> }
> 
> I am a newbie to D, and hope that I made the right changes to expose these
> methods to my D app.  In any case, the app works great, and is
> mind-bogglingly fast.  Any feedback on what I did is welcome.
> 
> Cheers,
> Brad
> 

> code all over the place.  (I think every time I used "bit" I meant
> "BOOL".)

Ehh, I wish D would make such additional comments unnecessary... ;)

Cheers,
Sz.

Am Wed, 14 May 2003 19:39:46 +0000 (UTC) hat Patrick Down <Patrick_member@pathlink.com> geschrieben:

> I was wondering if we could use the wiki as a collaborative windows.d
> editing project?

Hi, I don't want to start big discussions about the best way to go but please have a look at http://www.xpeers.net (Attention CSS2 used :-|), which is a P2P collaboration platform I'm involved in.

I'm running a demo-server and could give people access to this platform. With this it's quite easy to keep one version in sync without a big infrastructure setup. We could than automatically update new versions for download as well.

Just an offer to the community. Anyone interested?

--
Robert M. Münch
IT & Management Freelancer
http://www.robertmuench.de