*bugfix: when create account journal period after closed account period , account journal period should be in done state. so, here I overload create method of 
account.journal.period, set state as a period state. (author hmo)

bzr revid: qdp-97b2ce65d9589a058d348903274cb1b63d3b2d5e

bzr revid: qdp-715a579b63f8382f24c121898102e879ab56b8cd

(Referenced by: Naresh (nch))

bzr revid: hda@tinyerp.com-7d27a7a217560495eace417ba5bc462b257d5685

bzr revid: hda@tinyerp.com-5f243bed9806444b47c622a08f5ca6d6319bffcb

bzr revid: mga@tinyerp.com-89e6ab8e9f1f332aa26949e2cd8d7d3722beb810

	Better view : extented vs simple views
		Modified several views
	Simplified Stock Mgt:
		remove stock.move.lot (packing of type delivery)
		remove mode.lot
	Chained locations
	Allows to define menus with parents
	Support logo in the company

bzr revid: fp@tinyerp.com-63555a2f8da964ab9f4b86e41e16306177a2087b

	Better view : extented vs simple views
		Modified several views
	Simplified Stock Mgt:
		remove stock.move.lot (packing of type delivery)
		remove mode.lot
	Chained locations
	Allows to define menus with parents
	Support logo in the company

bzr revid: fp@tinyerp.com-9dd4d862b64c393dbcc7b6c085e4ff039716d90c

bzr revid: mga@tinyerp.com-9cf3a8edc4429f112f27e106a9f03e1553f1b137

group_project_manager
group_project_member

bzr revid: mga@tinyerp.com-e35ca9447149b836feb311925fe7a5566a801b68

bzr revid: mga@tinyerp.com-5092a99b6cf09a30a73da31db59a40da87f510b7

bzr revid: mga@tinyerp.com-b2cf4ab283dab5004fec9179c79c53440d21b7f1

bzr revid: mga@tinyerp.com-d0e857b61ca2e2ec8fcb01a847ef00c9323ea2b5

bzr revid: stw-9e41eaa87e5b38325c28056c246749ae7b702a10

revert the previous patch about the support of <pageNumber /> in para tag, this implementation doesn't work with a lot of pages

bzr revid: stw-9f0e8efdd83695fc5ffab2d3dd8e12a37f815a70

bzr revid: ame@tinyerp.com-f8d2d7c8b03c9a57cbbd7bcdd9e74cf4cfa6c066

bzr revid: stw-5deabfe48bf2ecb63d734432127d0323d1ee4f16

bzr revid: chs@tinyerp.com-4b7b7b9042deab3f6f125e6eaf3b1a897545f199

bzr revid: chs@tinyerp.com-6d1dda3cfd9a7f71eec78ae198f0922b245a7ffb

bzr revid: qdp-48e437824538c027a523f4ac08fbed9e79c201fc

bzr revid: qdp-96b6724e9651427786bc2910ce5776adddadf255

code is in the comment part, just uncomment that part

bzr revid: mga@tinyerp.com-a1cc6b57c3c73a8f6333396f9f63290ec1700ace

problem in the name of group

bzr revid: mga@tinyerp.com-b98880a8bf0a05a75a995a9d158708d18db441a2

*bugfix: previously, we haven't ever checked whether the value could be False for functional many2one. This leads/could lead to errors in several places. (author jvo)

bzr revid: qdp-d220a909c14ca10abbd252842a785219afb8140b

bzr revid: hda@tinyerp.com-1e3b27368f6428262e1dec6394cbf550820cebb0

  It supports the concept of spanning of RML, but it isn't specified in the same way as HTML

bzr revid: stw-25e00dcd9d3208d87432379c2917ebcff0d06b6e

*added a new functionnality to allow the user to set the state of the  account_move from draft to validate (and existing account_move_lines related). This functionnality 
can be called from:
 ** a list of account_move_lines
 ** a menuitem in Financial Management\Periodical Processing\Validate Account Moves: it asks for a journal and set the state of all draft account_moves of this journal 
to validate.
*overwritten the name_get of the account_move in order to display the name with a star * before it if its state is in draft

bzr revid: qdp-2933c3b426bc6fcaf73f5941469eadba0e0862f4

*cleared views

bzr revid: qdp-f7dec55d7d3159ddce1e06b35059fc89a4b3de4c

bzr revid: fp@tinyerp.com-a52fb2798427107a6ca1e5569fc1371d4af3f42e

bzr revid: stw-ded09fe87421445d72f2357d32128695f2072396

bzr revid: chs@tinyerp.com-892d3a57d27c905952d8b0a4cca0ae2b6027a9a9

bzr revid: fp@tinyerp.com-91e1037ac30c2a1dddc5e572efece69c3379ce54

bzr revid: fp@tinyerp.com-7b7df9aa77fd9346e47ec49066374c96c494fbc0

bzr revid: fp@tinyerp.com-151a3e002af08a832b9c0ae0ccf5f4000517b00d

bzr revid: fp@tinyerp.com-be694ba8ded07d71ba41b4ff047044fe59804874

bzr revid: fp@tinyerp.com-0758c5620bf4880d2cda7e77c38791affd7ba042

bzr revid: fp@tinyerp.com-f3b4c883fd03a9488f2f3bf56e0e51a6fdfa7f0d

*when the wizard is run, all the invoices receive now a value for latest followup date and followup level (accordingly to the level of the account_move_line)
*the email sending is implemented. The email is structured as the report
*added a column for maturity date, in Financial Mngt\Periodical Processing\send followup\all receivable
*in the many2many of the wizard in Financial Mngt\Periodical Processing\send followup, added a filter per account type == receivable

bzr revid: qdp-f86c47df2d708c074e43717eb3f7441fe0247fac

*added a transition in workflow of sale_order + modify the wizard of invoicing line (wizard_sale_line_invoice.py) so that if all the lines of a sale_order have been 
invoiced, its state is set to 'progress' and the workflow is updated
*added a button on form view of sale_order_line in the form view of sale_order, to call the wizard for invoicing that line (visible only if the line is in 'confirmed' 
state)
*added a domain on Sales Management/Sales Order Lines/Uninvoiced Lines to filer on state <> 'draft' and state <> 'cancell'
*added a menuitem to see all the sale_order_lines

bzr revid: qdp-9fc9639961f28893e202d48b532e453c584c6679

bzr revid: chs@tinyerp.com-bceb1fca2454957e2c777d1bb615e1ab873225a2

bzr revid: chs@tinyerp.com-337e144d63dc6560c292ad41f393c128761a0417