| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
| |
For consistency with GTK, blah.[ch] should be named eosblah.[ch].
[#23]
|
| |
|
|
|
|
|
|
|
| |
Test harness improvement: ADD_APP_WINDOW_TEST(test_path, test_func)
creates an EosApplication and connects test_func() to the "startup"
handler of the application, then runs it.
Commented out /application/two-windows test, because it's apparently
not deterministic.
|
| |
|
|
|
|
|
|
|
| |
Add an EosApplication class. Functionality:
- present main application window when activated
- warn if more than one application window is added
Also add a stub EosWindow class that overrides GtkWindow's
"application" property to be a construct-only property.
[#4]
|
| |
|
|
|
|
|
| |
After running 'make install', run test/smoke-tests/introspection.js
(and its Python counterpart) to test whether the GIR has been installed
correctly.
[#1]
|
|
|
There are automated tests which run when you do 'make check', and also
smoke tests which demonstrate one piece of functionality, which can be
used as a sort of sanity check or demo.
[#1]
|
