What (if any) major parts of the Xesam interface are we missing? Or do we implement poorly? If we are 100%, that's awesome, but if not, I want to look into getting us completely compliant so we can push nautilus/gtkfilechooser supporting Xesam, not individual API's.
On Dec 13, 2007 11:27 AM, Arun Raghavan <[EMAIL PROTECTED]> wrote: > On 13/12/2007, Anders Rune Jensen <[EMAIL PROTECTED]> wrote: > > Hi > > > > With the new libbeagle interface he is a patch that implements the > > missing inSet keyword in the Xesam interface. > > Modified a bit and committed (r4280). Thanks! > -- > Arun Raghavan > (http://nemesis.accosted.net) > v2sw5Chw4+5ln4pr6$OFck2ma4+9u8w3+1!m?l7+9GSCKi056 > e6+9i4b8/9HTAen4+5g4/8APa2Xs8r1/2p5-8 hackerkey.com > _______________________________________________ > Dashboard-hackers mailing list > Dashboard-hackers@gnome.org > http://mail.gnome.org/mailman/listinfo/dashboard-hackers > -- Cheers, Kevin Kubasik http://kubasik.net/blog _______________________________________________ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers