| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
| |
The first version is going to be version 0.0, after which we will
bump up to development version 0.1.
[endlessm/eos-sdk#418]
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Use the visible-child and visible-child-name properties of GtkStack
in lieu of visible-page and visible-page-name. Use the
transition-duration, transition-type and name properties of GtkStack
instead of proxying in page manager with properties of that same name.
The page manger becomes nothing more than a stack with custom child
properties for use in EosWindow, and becomes a lot simpler.
This breaks the page manager api and will require changes in the
apps as well
[endlessm/eos-sdk#985]
|
| |
|
|
|
|
|
|
|
| |
Rather than keeping an internal stack. This saves us from a lot of
proxied container vfuncs, which had some bugs. Before we were
avoiding doing this for adding persistent overlays above the pages,
but don't think thats currently in the plans so we can take the
simpler approach of subclassing GtkStack
[endlessm/eos-sdk#985]
|
| |
|
|
|
|
|
|
|
|
| |
This has been totally unused in all our applications and has been
having sizing problem with height for width and width for height
request.
We had grand plans for this, but since its unclear if there's a
future in which this widget is used think it makes sense to remove
[endlessm/eos-sdk#985]
|
| |
|
|
|
| |
Simpler and has a nicer memory layout. Needed glib 2.38 to do this.
[endlessm/eos-sdk#421]
|
| |
|
|
|
|
|
| |
They do nothing yet, just put the getters and setters in the page
manager.
[endlessm/eos-sdk#102]
|
| |
|
|
|
|
|
| |
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]
|
| |
|
|
|
| |
EosWindow will always use this type when transitioning the background.
[endlessm/eos-sdk#88]
|
| |
|
|
| |
[endlessm/eos-sdk#61]
|
| |
|
|
|
|
|
|
| |
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]
|
| |
|
|
| |
[endlessm/eos-sdk#59]
|
| |
|
|
|
|
|
|
| |
- 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]
|
| |
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
|
| |
- 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'
|
|
|
Minimum functionality for EosPageManager. Currently uses a
GtkNotebook internally until we decide what to do regarding GtkStack.
(Philip; map/unmap Matt, Patrick)
|
