Wintab32 dll devlopment

[Dimitrie O. Paun]

On Tue, 22 Apr 2003, Robert North wrote:

> 2. When to post patches
> I could start producing patches quite soon.
> For instance, I could post patches when the WTInfo function is working.
> Or, I could wait till the whole system is working fully with at least
> one app?

I would say produce patches sooner rather than later (with meaningful
changes, of course).

> 3. Size of the patches.
> Is it better to break patches into small (valid compile, but 
> non-functioning) chunks, or to release large functioning patches?

I prefer smaller (again meaningful) chunks.
 
> 4. Config files
> Wintab will need some config data.
> I assume the best place to put this is in the ~/.wine/config file,
> within a registry key named "wintab"?

Sounds good.
 
> 5. Development notes.
> I have some notes on the design that other developers will probably find 
> useful.
> Where in the wine project should they go?
> There seems to be no place for rough notes.

Put them at the top (after the LGPL header) of the main file.

> 7. Cross-platform abilities
> Is there any need to think about allowing alternatives to
> XInput to plug into the wintab dll?

I'd say let's first get something working (and integrated into the tree)
first, then worry about other alternatives.

-- 
Dimi.