| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
| |
Minimum functionality for EosPageManager. Currently uses a
GtkNotebook internally until we decide what to do regarding GtkStack.
(Philip; map/unmap Matt, Patrick)
|
|\
| |
| | |
Fix make distcheck
|
| |
| |
| |
| |
| |
| | |
Header file missing from a _SOURCES declaration, and wrong file name
in POTFILES.in.
[endlessm/eos-sdk#55]
|
|/
|
|
| |
[endlessm/eos-sdk#7]
|
|
|
|
| |
Figured it out while testing [#42]
|
|
|
|
|
|
|
| |
Creating a window that is not tied to an application should be a
serious programming error.
[#42]
|
|
|
|
| |
[#12]
|
|
|
|
|
|
|
|
| |
EosWindow maximizes itself on creation. This code does not enforce
maximization or forbid the window from resizing, since that is the
window manager's job.
[#12]
|
|
|
|
|
|
| |
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]
|