Kexi/Junior Jobs/Simple Form Widgets: Difference between revisions
< Kexi | Junior Jobs
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
*OPEN, DIFFICULTY=5/5 Progress Bar (based on QProgressbar), should bind to column of data type: int, user of course cannot change its value by clicking on it | *OPEN, DIFFICULTY=5/5 Progress Bar (based on QProgressbar), should bind to column of data type: int, user of course cannot change its value by clicking on it | ||
*OPEN, DIFFICULTY=5/5 Calendar (based on QCalendarWidget), should bind to column of data type: QDate | *OPEN, DIFFICULTY=5/5 Calendar (based on QCalendarWidget), should bind to column of data type: QDate | ||
* Recommended for [http://www.google-melange.com/gci/homepage/google/gci2011 Google Code-IN] program | |||
*Required skills: basic Qt, average C++ | *Required skills: basic Qt, average C++ | ||
Revision as of 08:15, 18 November 2011
Implement these widgets:
- OPEN, DIFFICULTY=3/5 Command Link Button (based on KexiCommandLinkButton from
kexiutils/), no data type
- OPEN, DIFFICULTY=5/5 Slider (based on QSlider), should bind to column of data type: int
- OPEN, DIFFICULTY=5/5 Progress Bar (based on QProgressbar), should bind to column of data type: int, user of course cannot change its value by clicking on it
- OPEN, DIFFICULTY=5/5 Calendar (based on QCalendarWidget), should bind to column of data type: QDate
- Recommended for Google Code-IN program
- Required skills: basic Qt, average C++
- Work within a new branch kexi-widgets-shreya, please create.
- All these widgets should be provided by plugins/forms/kexidbfactory.cpp and have implementation in individual files in plugins/forms/.
- Take care of: coding practices, coding style (see Techbase articles)
- Look at how Kexi's button widget is implemented/exposed in forms (for non-data widgets)
- Look how text line edit is implemented/exposed in forms (for data widgets)