Talk:GSOC 2012 Project Manager Core

-- baazigar 18:50, 16 May 2012 (CEST)
Previously, JLuc and Malex discussed that it is important to define the core functionalities of PM for its success through GSoC. As discussed on Apr 17 on irc,

 Its important to define the core functionalities of PM.

 Final definitive proposal of PM.

 Is it necessary to split PM into 2 or not?

 Good solution requires exploring, thinking, designing :All PM students,scribus users and mentors please take part into this.

A fileformat to store shared resources and attributes?

 Its an option.

just add an attribute to styles, palettes etc. that says fromMaster="masterdoc" and write some update code.

 baazigar: since scribus docs already store all this stuff, why not reuse it?

would it require the fileformat be changed slightly for a slave document?

 baazigar: it shold at least know its masterdoc

 that's how i imagined it could be : defining a masterdoc

this would be a lot easier than making a new fileformat !!

 ok.. so.. i think we need to define this project a bit better within the team.. firstly, i see a project management module initially not modifying the scribes docs.. but being a resource manager, collector, etc.. theres significant work there.. then there is the side where the docs might actually get modified where they could inherit (like you have been saying) from "Project Master" master page etc

 this inheriting can be either 'physical' (copying attributes from master to slaves) or 'virtual' (getting access to data through links, when needed)

virtual would be better

 but harder.. and risky for existing docs

there are too many choices !

 no.. one just needs choosing that doesn't lock scribus into a corner