#1974: Core shouldn't have to know about the clients in advance
-----------------------+----------------------------------------------------
 Reporter:  jumentous  |       Owner:                        
     Type:  bug        |      Status:  new                   
 Priority:  minor      |   Milestone:  Future                
Component:  other      |     Version:  other (please specify)
 Keywords:             |  
-----------------------+----------------------------------------------------
 So, #1971, #1972, #1973 are bugs that were discovered in the trying to fix
 this point.

 I am looking at adding a new UI to deluge, and in the process noticed that
 the core currently matches the chosen UI and launches the appropriate
 client. This makes it impossible to add a client developed out of the
 deluge tree.

 This patch modifies setup to export the UI classes as entry points and
 load the entry point for the class. Details for this method can be found
 here:
 http://aroberge.blogspot.com/2008/12/plugins-part-6-setuptools-based.html
 and http://peak.telecommunity.com/DevCenter/PkgResources#locating-plugins

 Note that it doesn't actually do a find_plugins yet, it's just moving
 towards it.

 Now i realize that there is already a plugin format for deluge however i
 thought this more appropriate for something that will be relatively static
 and can be deployed by rpm/deb.

 Obviously, comments/revisions are encouraged.

-- 
Ticket URL: <http://dev.deluge-torrent.org/ticket/1974>
Deluge <http://deluge-torrent.org/>
Deluge project

-- 
You received this message because you are subscribed to the Google Groups 
"Deluge Dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/deluge-dev?hl=en.

Reply via email to