> bullsh...
> I agree it's possible to make some minor changes in 2-3h. But, try to make 
> full featured an well designed invoice in rml from given MS .doc sample!!! 


Well the main popose of thi is not enter in a war of report designers, is only 
a comment, but, i can ensure that we can make very complex reports (THis 
obvious dont take 2 hours), BTW is only an opinion but is not a bullsh..... ;-)

I can send several examples of reports so so so so complex and you don't need 
to lear another thing more that python, rml and framework [And is obvious that 
you theorically alrady know because you are working on OpenERP].

I repeat, several options is good but make _perfect_ only one and embebed is 
beter this is only one option.


> - As Nhomar says, OpenERP's RML is not complete, missing some core features. 
> For example in OpenERP's RML is not possible to show the invoice totals in a 
> fixed position on the footer because the PTO (please-turn-over) feature of 
> RML is missing (see bug 
> https://bugs.launchpad.net/openobject-server/+bug/509266 BTW, a patch has 
> been available for a year). 


@Borja,

This is the message, Is not perfect yet, we need to make it perfect, we use 
your patch in all our implementation,. Did you try on V6? we didn't yet, we can 
make the change and propose for merge, What do you think?


> On the Spanish localization we implemented several wizards like this: The 
> main thread (the one launched by the client) runs a wizard action of type 
> "choice". The first time it is called, it spawns a background task to do the 
> job. If the task takes more than 20 seconds the choice action returns a "Job 
> in progress (X%). Continue waiting? Work in Background? Cancel?" view so the 
> user is informed of the progress. This way this wizards never time-out. But 
> the user still has to clic the "continue waiting" for the choice action to be 
> called again cause there is no auto-refresh option for the wizard forms!


Totally agree.


> 
>  L10n modules: our plan is to efficiently integrate all localisation and work 
> with contributors of each country to make something strong and adapted to 
> OpenERP accounting guidelines. I will dedicate a team to do this after rc1 
> (~mi-october), we need to start organize the collaboration.
> 


EXCELENT, 

One question: some features are needed on core [Or at least on our country], 
like an Strong[recursive] reference between invoice and reverse document 
related (Credit Note), we have a module that do that debit_credit_note, how do 
we make the procedure, modify the core of account or only port the module to V6 
and propose for merge on addons? for example to know how will we work on our 
improvements to v6?

------------------------
Nhomar Hernandez
CTO at
http://openerp.netquatro.com




-------------------- m2f --------------------

--
http://www.openobject.com/forum/viewtopic.php?p=61262#61262

-------------------- m2f --------------------


_______________________________________________
Tinyerp-users mailing list
http://tiny.be/mailman2/listinfo/tinyerp-users

Reply via email to