summaryrefslogtreecommitdiff
path: root/test
Commit message (Collapse)AuthorAge
* Tests for EosActionMenu.Felipe Erias Morandeira2013-06-24
| | | | [endlessm/eos-sdk#79]
* Skeleton for EosActionMenu tests.Felipe Erias Morandeira2013-06-21
| | | | [endlessm/eos-sdk#79]
* Small changes to EosActionMenu. A more complete example of how to use it in ↵Felipe Erias Morandeira2013-06-21
| | | | | | an application, including changes to CSS. [endlessm/eos-sdk#79]
* Override Endless.ActionMenu.add_action() to hide GtkAction from the ↵Felipe Erias Morandeira2013-06-21
| | | | | | developer, as that will be deprecated in the future. [endlessm/eos-sdk#79]
* EosActionMenu: Implemented the functionality to add a GtkAction and have it ↵Felipe Erias Morandeira2013-06-21
| | | | | | linked to a EosActionButton in the menu. Added example code in action-buttons.js [endlessm/eos-sdk#79]
* Added tests for new background child props.Matt Watson2013-06-18
| | | | [endlessm/eos-sdk#102]
* Window background drawing uses new page background propsMatt Watson2013-06-18
| | | | [endlessm/eos-sdk#102]
* Fixed missing comma in app-windowFernando Farfan2013-06-17
| | | | [endlessm/eos-sdk#97]
* Corrected assertion failures.Fernando Farfan2013-06-17
| | | | | Modified EosTopbar to remove a handful of assertion failures when adding left/center topbar widgets. [endlessm/eos-sdk#97]
* Draw topbars in EosWindowFernando Farfan2013-06-17
| | | | | Work in progress. Topbars do not appear when using Endless theme. [endlessm/eos-sdk#97]
* Added support for left topbar and center topbar.Fernando Farfan2013-06-17
| | | | | | | Modified EosPageManager, EosTopbar and EosWindow to have support for the two new topbars. app-window.js includes some tests for these two widgets. [endlessm/eos-sdk#97]
* Fixed up main area tests to be more robust.Matt Watson2013-06-12
| | | | [endlessm/eos-sdk#88]
* Bugfixes. Window background handles case of no pages in pm.Matt Watson2013-06-12
| | | | | | Also updates main area tests in test-window.c to reflect new widget hierarchy of EosWindow. [endlessm/eos-sdk#88]
* No background animation switching between pages with same backgroundMatt Watson2013-06-12
| | | | | | When background URI is changes for the currently visible page, it will switch backgrounds without a transition animation. [endlessm/eos-sdk#88]
* EosWindow size allocate ignores border-width.Matt Watson2013-06-12
| | | | | | Background is drawn in an internal widget so using the border width would prevent it from drawing full screen. [endlessm/eos-sdk#88]
* visible-page property update if visible page is removedMatt Watson2013-06-10
| | | | | | | Before the visible page would be set to null if it was removed, instead of pointing to another page in the page manager. Also signals for property changes were not emitted. [endlessm/eos-sdk#101]
* Splash page manager's add will add child as the splash page.Matt Watson2013-06-03
| | | | | More documentation improvements too. [endlessm/eos-sdk#62]
* Fixed up the splash page documentation.Matt Watson2013-06-03
| | | | [endlessm/eos-sdk#62]
* Added test for the splash page manager.Matt Watson2013-06-03
| | | | | | Unfortunately, most of the getter setter test fail and are commented out, because of the remove bug in EosPageManager. [endlessm/eos-sdk#62]
* Added basic splash page manager functionality.matt2013-06-03
| | | | | | | Splash page and main page widget properties with getters and setters. Ability to switch between the splash and main page. Added splash- page.js smoke test. [endlessm/eos-sdk#62]
* Smoke test for EosActionButton; eosactionbutton.css contains the style ↵Felipe Erias Morandeira2013-06-03
| | | | | | settings that should eventually make it to eos-theme [endlessm/eos-sdk#30]
* Added transition type and duration props to page manager.matt2013-05-29
| | | | | | | | These just wrap the functionality of GtkStack. Added some dropdowns in the app-window.js to try the different transition options and some simple c tests. [endlessm/eos-sdk#61]
* Rename 'background' API to 'background-uri'P. F. Chimento2013-05-29
| | | | [endlessm/eos-sdk#59]
* 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]
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-01 22:15:31 +0000