Arduino 2009 (or other, but 2009 is my favorite for now)
the usual : iron, solder, leds, copper, finger, sweat, ...
Buttons are displayed and arranged like on a iPhone (landscape position). On touch, button gets "activated" (lightened/box?) and a command is sent to the Arduino that forwards it to the PC via USB that is interpreted by the ardTouch Connector on the PC
Buttons are groupped in panel and user can switch panel. One panel for work, one for music, one is a calculator ...
User defined buttons
User can choose his buttons per panel (hard to implement, expecially the icons upload)
Like in the ardNotifier have a bar that displays latest received mail and unread mail
With a RGB led, implement a "mood" that could be customized per user or per message. ...ok, it's bling bling
Add a button that displays the current calendar (service will have to tell the date to the box once in a while). I need to dig out my algorithm for calendar, but I wrote it somewhere... (requires panel implementation)
Add a button to switch to calculator mode (requires panel implementation)
Use some analog port to read outside temperature (stick the component outside the box !)
Find a nice box for baby and if possible don't cut it too poorly for I won't have many failure options
Make a special panel (need the panel evol) to display buttons for WMP commands
Aim to save power ... and not kill the screen with a 24/7 identical display. Different options :
the simple turnoff and then on when touched
more sexy : black random marching ants
Touch detection is ... not perfect (to say politely). I don't know if it's just my model, but sometimes there is strong misreading of the touch position (like 1~2 cm away). This is ok if the touch lands on nothing, but if you click on "notepad" icon and it interprets as "reboot the pc" it could be more annoying. I have a spare DS touch screen, I'll cross check the LiquidWare code vs. some other guys code... in case.
I though for long time the SoftwareSerial lib was not ok so I changed to NewSoftSerial, but the problem was caused by the here above issue. So not really an issue...
The TouchShield is ... a shield. Which is great for prototyping, but kinda annoying for setting the whole stuff in a box, or if you want to use other pins (covered by the shield) ! I'll use a vanilla board to redirect some pins to allow myself to play with it and design the box to my idea.
All content on this site is shared under the MIT licence (do what u want, don't sue me, hat tip appreciated) electrogeek.cc ~ Formerly known as Kalshagar.wikispaces.com (AlanFromJapan [2009 - 2019])