>>>Would be real nice to have it in a little app like the one from the link I gave you. I'll just make up one for myself. Thanks again for those API posts to all.
>
>>The problem with a desktop app is that it has to use a distributed database- since the API reference is a living, growing entity, this would severely hinder its timeliness.
>
>
>Time for me to investigate the Win32API. How is it growing?
The API is not growing, the reference here is.
>I figured like what was in here was better than nothing and would be nice to browse thru in the same fashion the app form the link I gave for VBers is.
What's the difference?
>Oh, are you saying you'll create an XML source for me? (Note to self: not funny, time for sleep)
Out of my hands. That would be up to Michel.
> But seriously is this where Publish/Subscribe will be handy dandy too?
Publish /subscribe wouldn't really come into the picture here, even if the app were distributed.
>Not just web sites like MyFloristDeliver.com retrieveing delivery info from another florist but even to the desktop with XML over your internet connection?
You could do that, and I have apps that do that now, but I don't see the use here. You write a client side app when a browser doesn't give you the functionality you need. Again, what's the problem with the browser interface?
Erik Moore
Clientelligence