summaryrefslogtreecommitdiff
path: root/test
Commit message (Collapse)AuthorAge
* Style changes, added additional assertions to test the setting of a page's ↵Will G2013-05-23
| | | | | | background [endlessm/eos-sdk#59]
* Updated PageManager docs to reflect background_uri change, added test for ↵Will G2013-05-21
| | | | | | changing page backgrounds [endlessm/eos-sdk#59]
* Various fixesP. F. Chimento2013-05-17
| | | | | | | | - Remove visible-page-background child property; only the window should be listening to this. - Style fixes - Monitor page child properties as in the toolbox and actions [endlessm/eos-sdk#59]
* Added a visible-page-background property and tests.matt2013-05-17
| | | | | | | visible-page-background property points to the URI of the background of the current page. Should probably be extended to give the correct background when page-managers are nested. [endlessm/eos-sdk#59]
* Background child property for pages, sets window background.matt2013-05-17
| | | | | | | The current page's background property controls the background of the window. EosWindow listens in on the page mangers notify signals to update its background. [endlessm/eos-sdk#59]
* Update test applicationP. F. Chimento2013-05-16
| | | | | | There is a toolbox widget and you can change the visibility of the fake action area on each page. Also, split up each test page into a different class.
* Integrate page manager and main area into EosWindowP. F. Chimento2013-05-16
|
* Add actions and toolbox child properties to page managerP. F. Chimento2013-05-16
| | | | | | | - Child property 'actions' (currently a boolean telling whether a fake action area is displayed as a red box; will become a JSON string in the future) - Child property 'custom-toolbox-widget'
* Added javascript override to the page manager add functionmatt2013-05-16
| | | | | | Added the autotooling to get our overrides installing as well. [endlessm/eos-sdk#70]
* Treat pages with no name as having name NULLP. F. Chimento2013-05-14
| | | | [endlessm/eos-sdk#58]
* Implement EosPageManagerP. F. Chimento2013-05-13
| | | | | | | Minimum functionality for EosPageManager. Currently uses a GtkNotebook internally until we decide what to do regarding GtkStack. (Philip; map/unmap Matt, Patrick)
* Merge pull request #56 from endlessm/issues/55P. F. Chimento2013-05-03
|\ | | | | Fix make distcheck
| * Fix make distcheckP. F. Chimento2013-05-02
| | | | | | | | | | | | Header file missing from a _SOURCES declaration, and wrong file name in POTFILES.in. [endlessm/eos-sdk#55]
* | Implements EosTopBar and integrates it in EosWindowFelipe Erias Morandeira2013-05-02
|/ | | | [endlessm/eos-sdk#7]
* Fix two-windows application testP. F. Chimento2013-04-30
| | | | Figured it out while testing [#42]
* Crash on eos_window_new (NULL)P. F. Chimento2013-04-30
| | | | | | | Creating a window that is not tied to an application should be a serious programming error. [#42]
* Testing and documentation improvements for EosWindowP. F. Chimento2013-04-25
| | | | [#12]
* EosWindow is fullscreenP. F. Chimento2013-04-25
| | | | | | | | 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]
* Rename C source and header filesP. F. Chimento2013-04-24
| | | | | | For consistency with GTK, blah.[ch] should be named eosblah.[ch]. [#23]
* Test fixture for testing an application windowP. F. Chimento2013-04-24
| | | | | | | | | 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.
* Application classP. F. Chimento2013-04-24
| | | | | | | | | 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]
* Enable GObject introspectionPhilip Chimento2013-04-17
| | | | | | | After running 'make install', run test/smoke-tests/introspection.js (and its Python counterpart) to test whether the GIR has been installed correctly. [#1]
* Add test frameworkPhilip Chimento2013-04-17
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]