Qt.git - Qt s a cross-platform application framework that is used for developing application software that can be run on various software and hardware platforms with little or no change in the underlying codebase, while still being a native application with native capabilities and speed.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Update copyright year to 2010	Jason McDonald	2010-01-06	1	-1/+1
\| \| \| \|	Reviewed-by: Trust Me
*	Update license headers again.	Jason McDonald	2009-09-09	1	-4/+4
\| \| \| \|	Reviewed-by: Trust Me
*	Update tech preview license header for files that are new in 4.6.	Jason McDonald	2009-08-31	1	-13/+13
\| \| \| \|	Reviewed-by: Trust Me
*	Update contact URL in license headers.	Jason McDonald	2009-08-12	1	-1/+1
\| \| \| \|	Reviewed-by: Trust Me
*	Update license headers in files that are new in 4.6.	Jason McDonald	2009-06-17	1	-2/+2
\| \| \| \|	Reviewed-by: Trust Me
*	kill usage of QT_STATEMACHINE_SOLUTION	Kent Hansen	2009-06-04	1	-5/+0
\| \| \| \|	The define no longer exists.
*	compile with -qtnamespace, clean up the example .pro files	Kent Hansen	2009-05-20	1	-6/+1
\|
*	improve the docs for the trafficlight example	Kent Hansen	2009-05-12	1	-25/+22
\|
*	get rid of margin	Kent Hansen	2009-05-05	1	-1/+2
\|
*	compile after api changes	Kent Hansen	2009-04-28	1	-4/+4
\|
*	kill the stateactions api	Kent Hansen	2009-04-22	1	-3/+3
\| \| \| \| \| \| \| \| \| \| \| \|	It just didn't give us that much. Typically you just reimplement onEntry/onExit/onTransition when you want to do something. We go back to the signals-and-slots approach: states have entered() and exited() signals that you can connect to. It's still possible to have an action-based API, but then you build it on top of the core API, which is OK. Replacing 4 public classes (and one layer in the hierarchy) with 2 signals feels good.
*	Initial import of statemachine branch from the old kinetic repository	Alexis Menard	2009-04-17	2	-0/+204