|
Notice: This page contains information for the legacy Phidget21 Library. Phidget21 is out of support. Bugfixes may be considered on a case by case basis. Phidget21 does not support VINT Phidgets, or new USB Phidgets released after 2020. We maintain a selection of legacy devices for sale that are supported in Phidget21. We recommend that new projects be developed against the Phidget22 Library.
|
|
button in the menu bar to go to the Phidget22 version of this page.
User:Cora: Difference between revisions
From Phidgets Legacy Support
| Line 94: | Line 94: | ||
=Outreach= | =Outreach= | ||
Edgy - | Edgy - Dependable - Accessible | ||
"It's normal and cool to want to play, or build seriously" | "It's normal and cool to want to play, or build seriously" | ||
Revision as of 22:20, 13 April 2012
Links
Documentation Log - Language Pages Casting Roles - All Templates - All Files (Uploads)
To be rolled into Application Guides and Primers (i.e. content extracted and then pages deleted):
To Be Done
App Guides
Background Priorities:
- Clean up sentence above uses of Using a Phidget in Code General
- Language - Python - Mac OS
- And other Mac OS sections on language pages
- Language - C/C++
- Clean up Links to General API
- Code Snippets for:
- Language - C Sharp - Phi?
- ....?
- Check device API pages - no pseudo code
- Commit
- Android HelloWorld x 2
- C HelloWorld
- Java HelloWorld
- Python HelloWorld
- Figure out licenses
And, ongoing:
- Tech support additions
- Phidget Manager, and dictionary?
Completed
Newly Done:
- Cleaned wiki of link references to Phidget Webservice, replaced by Phidget WebService
- Data Logging With a Thermocouple
- Temperature Sensor Primer#Emissivity (And associated Trac bug report)
Last Week:
- Language - Python - Code Snippets
- Language - Python - Linux section
- OS - Android
- Language - Android Java
- All old (red) Manual Installation links redirected to Windows Page
- OS - OS X - Structure, with content suggestions
Older:
- Phidget WebService
- OS - Windows - Structure and content suggestions
- Language - Java - Linux section
- Template:ExamplePseudocode Change to Hello World - Java Page
Software Flow
Don't get lost!
- Getting Started for Device
- Pick Your Operating System
- Pick Your Language
- Examples, run and build
- Learn about General Phidget Programming
- Device Specific Pseudocode in API
- Code Snippets / Hello World pseudocode on Language Pages
- Write Your Own Code
- Language-specific API
- General API - TO BE DELETED
- Device Specific API
Outreach
Edgy - Dependable - Accessible
"It's normal and cool to want to play, or build seriously"
- Mini robots driven by phone - Save money automating energy - Explore science with your kids or class - Do it exactly the way you want, customizing
Currently, how are gyros, accelerometers, GPS, etc used on phones for cool things? Maybe spy via Arduino + Android books? (These seem like hobby projects - we are more serious)
Strengths of Arduino:
- They have Shields
- Solution: VINT can probably improve our third-party interest if we expose the HW comm API?
- They appear as not-for-profit
- Solution: Whatever. They're in it for the money. Make it clear we're in it for the customer! And, for the coolness and fun factor.
- Strong Community, which comes from open source, and being hard to use so people feel like they're learning
- Solution: This will probably be helped by exposing the HW API comm in VINT, in which case we are open enough for third-party add ons
- Solution: Primers! People will learn that way. Maybe mesh primers with app guides so that people can learn hands-on.
- They have multiple O'Rielly books, magazines, Evil Genius books
- Solution: Man oh man do we need some rad app guides.
- Solution: More beginner stuff (physics classes, physical computing, experiments)
- Solution: Phidgets are not just about learning, they are about building real, useable, durable systems (a photo book? a video tour?)
Strengths of Sparkfun:
- Custom - Almost Digikey-level modularity
- Our Solution: Basic hardware with lots of different versions for different needs
- Scrappy and edgy
- Our Solution: Hipsters can't ride long distances in tight blue jeans. We have endurance.
- Our Solution: More creative, scrappy kits ('robot in a can')
- Solution: More humour and wit in our writing for application guides
- Solution: We can be more in touch with colleges and communities
- Solution: Expose good relationships with our mfg community, help relationships to be built with others there
- Strong Community, which comes from their staff diversity and connections to colleges
Strengths of National Instruments:
- Dependability
- Solution: Advertise our calibration and spec confirmation methods
- Solution: Show many real-world uses
- Solution: VINT can maybe interface with third-party sensors?
- Market themselves as 'industry solution leaders' (white papers, trend predictions)
- Solution: Don't do this. You're not the expert unless you're -really- the expert, and NI is not the expert, they're just another company.
- Solution: Make it clear that we think the customer knows best. They know their systems the best, their requirements the best. We just help them.
Our possible additional strengths:
- Expose our entire product development and mfg process
- Allow and help our partners (i.e. China) to make new relationships directly with our customers
- Share ideas and manufacturing/design experience with China to make new products and add some Sparkfun-like agility to customer needs
- Make this an iterative process so we have some control and they have some learning and we don't suffer the three-hour-woodchipper effect
Random Software Mess
- Language - C/C++
- Language - C Sharp
- Language - MATLAB
- Language - Python
- Language - Java
- Language - Android Java
High-Level Pages
- Software Overview
- Getting Started with Phidgets
- General Phidget Programming NOT the API (Guts) page
- General API The Guts page. No device-specific APIs. - TO BE DELETED
Guidelines and Goals
| Primer Primer | High-level philosophy for primer construction |
| Software Example Design | What examples should contain, exceptions for different languages |
| Internal - Code Example Guidelines | Formatting, style, variable naming conventions, interaction philosophy |
| Internal - Software Wiki Structure Guidelines | A more formal layout of the structure and flow between Software pages |
| Application Guide² | Guide to the Application Guides |
| Application Guides | Internal list of most guides and some structure |
Strawmen and Templates
Product Related Pages
| Product Page - Template | Base for Product stubs |
- Product - 1018 - PhidgetInterfaceKit 8/8/8
- Product - 1023 - PhidgetRFID
- Product - 1045 - PhidgetTemperatureSensor IR
- Product - 1061 - PhidgetAdvancedServo 8-Motor
- Product - 1066 - PhidgetAdvancedServo 1-Motor
Them Templates
General
| Template:ContentNeeded | Red box and bold |
| Template:ProblemSolution | Red and bold text |
| Template:KnownIssues | The tech support catch-all at the bottom of stubs |
For Language Specific Pages
| Template:LanguageSupport | Full API, etc notes, support section at top |
| Template:UsingAPhidgetInCodeGeneral | Introduction to how to write code (open, etc) |
| Template:ExampleCodeReasons | Why you want to start with example code |
| Template:ExamplePseudocodeLogic | For logic-only languages |
| Template:ExamplePseudocode | For event and logic based languages |
For Specific Device Pages
| Template:RFIDPseudocode | RFID pseudocode for API |
| Template:InterfaceKitPseudocode | Interface Kit pseudocode for API |
| Template:UsingAPhidgetInCodeSpecific | Sections before device specific API on product page |
To Be Deleted
Nothing right now
