Bug 43597 - Add high-level API for Chan.I.FileTransfer.Metadata interface
Summary: Add high-level API for Chan.I.FileTransfer.Metadata interface
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-qt (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords: patch
Depends on: 43591
Blocks: 43590
  Show dependency tree / graph
 
Reported: 2011-12-07 12:23 UTC by Andre Moreira Magalhaes
Modified: 2019-12-03 20:29 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Andre Moreira Magalhaes 2011-12-07 12:23:54 UTC 

    


    


      



        
          Comment 1
        

        
          Daniele E. Domenichelli

        

        
        

        
          2012-12-06 13:22:04 UTC
        

      






I tried to add a high-level API, branch here:

https://gitorious.org/drdanz-telepathy-kde/telepathy-qt4/commits/ft-metadata

Requires telepathy-gabble from master, since the Chan.I.FileTransfer.Metadata was not correctly exported in latest release (0.17.1).

    


    


      



        
          Comment 2
        

        
          Daniele E. Domenichelli

        

        
        

        
          2013-01-16 22:58:10 UTC
        

      






Works with telepathy-gabble 0.17.2

    


    


      



        
          Comment 3
        

        
          GitLab Migration User

        

        
        

        
          2019-12-03 20:29:06 UTC
        

      






-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-qt/issues/36.

    



  






  














    


  Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.