Very cool however i feel that the recomended hardware camera part should give a bit more detail as to frame rates perhaps tabulate it as many of these cams will support multiple framerates and resoloutions also ROI.

I need to fix the cover art. I can send it 2 you later. Other then that woot!!!

What a good new!
I’ve reading Dan Saffer’s book, but with this… I think will be a great help to everyone really interested in multitouch, lot of thanks

Pretty good!  I see the bugs I filed earlier got fixed, but I ran across a few more in my quick skim of it so I’ve filed those.  I don’t have indesign, so I can’t preview in that file, so it would be nice if each time a commit was made an updated PDF preview would also be committed to the repository to aid community proofreaders

Also, there’s no need to make a new file for each draft in the repository - that’s what SVN does automatically (it’s purpose is to retain previous versions), so you really just need the latest ID file, the latest dependencies, and the latest PDF export, and get rid of all the rest of the clutter in the repository - makes it easier for people to find things and know they’re the latest, plus it won’t confuse developers like me as much.

Hi, Basically is very good, I think the software .net portion need to update, CsTi is old and not update, can be check when was the last post. or most activities in last 6 months for .net threads

Win 7 MT SDK coming up this year. I see the mainstream MS services is Daniel D FW as input provider for win 7. and as controls, WPF MT FW, Mira, MultiTouchCore .. etc

I think it is good idea ask them their thought to see now and next 2 year road map. That way, they can combine their thought instead of create another wheel for same things.

Just only my thought, no offence for anyone. and sorry if I do.

Thanks for all the feedback guys.
justin - Ok, sounds good.
ajlovegrove - created a task: http://nuicode.com/issues/304
rpavlik - I’m a SVN noob Thanks for explaining that, I’ll clean up the repository tonight. I’ll correct the bugs you submitted tonight and re-upload a draft. We have been uploading updated PDFs frequently to the repository, but in the mess they’re probably impossible to find
uncledj - Thanks for your input - I’ll create a new task for that as well to discuss it: http://nuicode.com/issues/305

-rbedi100

hey guys… really stunning job on book i’m sure this will be a big help to future members!

justin - 02 June 2009 06:23 AM

I need to fix the cover art. I can send it 2 you later. Other then that woot!!!

That would be real great. Please file a bug on nuicode.com and attach the file there.. Thanks

Wow that’s very great news, because I’m in the final stage of writing my diploma thesis and I need some more detailed infos. Now I’ve got a very good source filled with expert knowledge

You’re all doing a great job and that’s what I really love about this community!
I really appreciate your hard work!

Well done to gorkem and rbedi100 and all who contributed to the realease of this book…

This will make a great resource to all studying multitouch

Great job guys… not to sound like a hater but some of the margins are off in the the document i would fix that.

Hey Taha,
Thx - Do you mean the inside margin? I made it 0.25” bigger than the outside margin on purpose - it accounts for the curling of the page when you bind it as a paper-back.

Hello,

I’m interested in the reading the book, but it will not download…

Shawn

Hi Shawn,
Here’s the direct download link: http://nuicode.com/attachments/download/112/First_Edition_Community_Release.pdf - if it doesn’t work, PM me your email and I’ll send it to you.
-rbedi100

rpavlik - 02 June 2009 11:12 AM

Pretty good!  I see the bugs I filed earlier got fixed, but I ran across a few more in my quick skim of it so I’ve filed those.  I don’t have indesign, so I can’t preview in that file, so it would be nice if each time a commit was made an updated PDF preview would also be committed to the repository to aid community proofreaders

Also, there’s no need to make a new file for each draft in the repository - that’s what SVN does automatically (it’s purpose is to retain previous versions), so you really just need the latest ID file, the latest dependencies, and the latest PDF export, and get rid of all the rest of the clutter in the repository - makes it easier for people to find things and know they’re the latest, plus it won’t confuse developers like me as much.

This is what we are planning to do:

- Collect as much bugs as we can in a time frame, and then release another PDF file with a suffix of -updateN-datemonthyear.pdf where N increases 1 by 1 each time. These will be amendments to the 1st edition, and each update will include an update to the CHANGELOG file on the same directory.

- CHANGELOG will tell which bugs and/or feature requests are fixed.

- After a certain amount of time (i.e 2 to 4 months), we release an edition which includes all the amendments in previous updates.

This way, end users will only download the latest file, and we’ll be able to eliminate any potential misunderstandings.

Görkem