Skip to main content
Jump to: navigation, search

Difference between revisions of "Newsreader/sources"

(Getting Started)
(Getting Started)
Line 8: Line 8:
  
 
*IArticle  
 
*IArticle  
*:sdfsdfsdf
+
*:Contains the article metadata
*IInputOutputSystem
+
 
*INewsgroup  
 
*INewsgroup  
 +
*:The newsgroup metadata
 
*IServer
 
*IServer
**C
+
*:the newsserver metadata
 
*IServerConnection  
 
*IServerConnection  
 +
*:The class that handles i/o with the server. Got from the server by getConnection()
 
*IServerStoreFacade  
 
*IServerStoreFacade  
 +
*: The class that manages synchronization between the store and the server.
 
*IStore  
 
*IStore  
*IStoreEvent
+
*:The place where fetched articles are stored. A filesystem store reference implementation exists.
*IStoreEventListener
+
 
*IStoreEventProvider
+
 
 +
Other interesting classes are ServerRegex, ISalvoResource, SalvoResourceFactory.
 +
 
 +
==Loading the view==
 +
The main view is populated using the GroupView.getInitialInput() method. This triggers the SubscribedServerProvider class which delivers IServers, etcetera. The store implementation bundle should start early to initialize the "store service" (in my case currently a class is initialized) See launch config in application class.

Revision as of 17:55, 10 August 2009

Salvo Sources

The sources are here
Media:salvo.0.5.0.sources.zip

Getting Started

The interesting stuff can be found in the model which classes are declared in
com.weltvree.salvo.model

  • IArticle
    Contains the article metadata
  • INewsgroup
    The newsgroup metadata
  • IServer
    the newsserver metadata
  • IServerConnection
    The class that handles i/o with the server. Got from the server by getConnection()
  • IServerStoreFacade
    The class that manages synchronization between the store and the server.
  • IStore
    The place where fetched articles are stored. A filesystem store reference implementation exists.


Other interesting classes are ServerRegex, ISalvoResource, SalvoResourceFactory.

Loading the view

The main view is populated using the GroupView.getInitialInput() method. This triggers the SubscribedServerProvider class which delivers IServers, etcetera. The store implementation bundle should start early to initialize the "store service" (in my case currently a class is initialized) See launch config in application class.

Back to the top