Skip to content
  • Bernhard Beschow's avatar
    move drawing methods from MarbleModel to MarbleMap · 98b53552
    Bernhard Beschow authored
    Motivation
    ==========
    
    The whole painting should be implemented in the view rather than in the model because it decouples data and its representation. This allows for having different graphics
    backends (hello OpenGL!) while having a common interface to the data.
    
    Implementation
    ==============
    
    MarbleMap is now the owner of all painting objects, e.g. the MeasureTool, a new TextureLayer class, the LayerManager, and others. To see all painting objects owned by
    MarbleMap, see the modified MarbleMap_p.h.
    
    Since the LayerManager object is now owned by MarbleMap, the layer-relevant methods, slots, and signals (such as addLayer(), removeLayer(), renderPluginsInitialized()) are
    now forwarded by MarbleMap and Marblewidget rather than by MarbleModel.
    
    The DownloadRegionDialog has been modified to take a MarbleWidget instead of a MarbleModel.
    
    RB: 5902
    CCMAIL: kde-bindings@kde.org
    
    svn path=/trunk/KDE/kdeedu/marble/; revision=1202361
    98b53552