aboutsummaryrefslogtreecommitdiff
path: root/libdbusmenu-glib
Commit message (Collapse)AuthorAgeFilesLines
* Adding in signals to get the update from the server updating the layout. ↵Ted Gould2009-05-051-0/+17
| | | | And parsing it.
* Implement the new_with_id function by making the id a property and building ↵Ted Gould2009-05-051-5/+57
| | | | some set_ and get_
* more debuggingTed Gould2009-05-041-0/+1
|
* Debug commentsTed Gould2009-05-041-1/+4
|
* Adding the layout into the error message.Ted Gould2009-05-041-1/+1
|
* Don't init the value, as DBus will do that.Ted Gould2009-05-041-2/+0
|
* Making sure to clear the call on error too.Ted Gould2009-04-281-0/+1
|
* Fix property names.Ted Gould2009-04-282-3/+9
|
* Putting in placeholders for the functions that got prototyped last revisionTed Gould2009-04-281-0/+14
|
* Okay, it think we're syncing the two XML hierarchies. Whew.Ted Gould2009-04-272-3/+51
|
* Getting up to the XML level. Whoo, up the protocol stack we go.Ted Gould2009-04-271-0/+26
|
* Handling all the DBus-isms of getting the property, now passing up the stack ↵Ted Gould2009-04-271-10/+44
| | | | to a parse function which will actually take care of the data.
* Creating a lifecycle for our dbus proxies. We created them, so we must ↵Ted Gould2009-04-271-1/+63
| | | | destroy them as well.
* Addign in the get and set properties.Ted Gould2009-04-271-1/+38
|
* Adding in properties.Ted Gould2009-04-271-0/+43
|
* Starting to flesh out the client a little bitTed Gould2009-04-201-0/+63
|
* A couple of debug strings and then making it so that if there is a root ↵Ted Gould2009-04-161-4/+6
| | | | menu, it's at the root of the XML data instead of having a root wrapped around it.
* Fixing the propertiesTed Gould2009-04-161-6/+6
|
* Adding in tests dictory, a test, and making it compileTed Gould2009-04-162-0/+9
|
* No warnings, put them in now I had to fix themTed Gould2009-04-162-2/+11
|
* Okay, let's build some XMLTed Gould2009-04-163-4/+16
|
* Putting in IDsTed Gould2009-04-161-0/+8
|
* Adding in all the public functions as real functions and implementing a ↵Ted Gould2009-04-161-7/+94
| | | | couple of children related ones.
* Okay, now we're getting and setting properties. Fleshing out these functions.Ted Gould2009-04-162-2/+51
|
* Adding in basic set and get functions for the propertiesTed Gould2009-04-161-0/+41
|
* Oops, forgot layout. That's make the dbus folks angry.Ted Gould2009-04-162-1/+8
|
* Adding in some server propertiesTed Gould2009-04-162-0/+20
|
* Changing the menuitem typeTed Gould2009-04-162-7/+7
|
* Adding in the server signalsTed Gould2009-04-164-5/+72
|
* Putting in the public interfacesTed Gould2009-04-161-1/+28
|
* Changing the type name to make more senseTed Gould2009-04-162-7/+7
|
* Changing the TYPE to make more sense and installing the dbus profileTed Gould2009-04-162-7/+14
|
* Building an API, woo hooTed Gould2009-04-152-2/+10
|
* Linking in the dbus prototypes generated by the dbus tools.Ted Gould2009-04-152-0/+39
|
* Adding basic client and server objects.Ted Gould2009-04-155-2/+178
|
* Building the DBus bindingsTed Gould2009-04-142-1/+92
|
* Designing some API babyTed Gould2009-04-131-2/+28
|
* Putting in more gobject based examples and getting all the libraries tied in ↵Ted Gould2009-04-135-10/+85
| | | | to make them work.
* Getting all the individual directories installing something and having a PC ↵Ted Gould2009-03-251-2/+2
| | | | file.
* Trying to make a directory to buildTed Gould2009-03-254-0/+49