openerp-community team mailing list archive

[Joël Grand-Guillaume <joel.grandguillaume@xxxxxxxxxxxxxx>]

Hi Humberto,

No big deal, thanks for coming back ! Do not hesitate to setup a meeting
with Frédéric to make a the GAP between our and your work.

Regards,

Joël


On Mon, Nov 11, 2013 at 2:27 PM, Humberto Arocha
<humbertoarocha@xxxxxxxxx>wrote:

> Wow, I have come to realize that this theme was delayed by me that much,
>
> Hello Dear, Joel,
>
> then we are in common ground
>
> let's work together in a new branch, let it account-financial-report/trunk
> or 8.0
>
> Lets create a blueprint with the Wishlist and the problems we have to
> overcome.
>
> That way beginning with a fresh start.
>
> It is always wonderful work on community,
>
> Best Regards.
>
>
> 2013/10/29 Joël Grand-Guillaume <joel.grandguillaume@xxxxxxxxxxxxxx>
>
>> Dear Humberto,
>>
>>
>> Just a few words to say that I'm entirely with you on that point. I think
>> the same, the problem is not the techno (webkit, RML, Pentaho,
>> whatever...). The problem is how do we compute !
>>
>> This is more on that point that I'm arguing (and Frédéric too). I'm sorry
>> if that was not clear. We don't care about webkit or not, doesn't matter.
>> We do car about how we computed our report in our webkit report. This is :
>> how do we compute the perdiod sum, the balance, the opening entries, etc...
>>
>> This is where our knowledge have value for us ! This is what we are not
>> agree on rebuilding something else.
>>
>> So I think we're perfectly in-line here ! Let's build a way to compute
>> stuff and let people chose a renderer ! Let me know what we can do.
>>
>> Regards,
>>
>> Joël
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Mon, Oct 28, 2013 at 6:23 PM, Humberto Arocha <
>> humbertoarocha@xxxxxxxxx> wrote:
>>
>>> Ok, Good Day, Comm Guys.
>>>
>>> Thanks to all you guys who have been aware of this thread and have been
>>> keeping up-to-date
>>>
>>> First we there were two reports and them keep from fighting each other,
>>>
>>> they draw a Line, I'll keep in RML, you'll keep in Webkit, an the
>>> promise: don't mess with
>>> my type of report.
>>>
>>> When we began to coordinate efforts, I think (now) we did it the wrong
>>> way,
>>> We focused on the type of the report and not on the background of the
>>> problem.
>>> (And now I think that) It was not about to build reports in different
>>> types of engine reports,
>>> instead it was on building a common ground that in the future would
>>> avoid friction among the stakeholders,
>>>
>>> And I think that we have to begin to build a common ground agnostic from
>>> the report engine,
>>> an API, something that with little effort can be used no matter your
>>> report engine of preference
>>>
>>> To avoid beginning a fight about whose reports are better than whom.
>>>
>>> If we build this common ground we can afford to please almost everyone,
>>>
>>> anyone else can then create his own report in his preferred report
>>> engine, ReportLab, Jasper,
>>> Webkit, Pentaho, BIRT, etc.
>>>
>>> We cannot think the same: *If two people think the same someone is
>>> thinking by the other.*
>>>
>>> So today, this is what is drawing our attention, And it has been
>>> wonderful because
>>> in early stages we can fix wrong-designed approaches, and make then
>>> better.
>>>
>>> In the meantime, I will withdraw the MP that I have submit, because we
>>> have step on
>>> the ground of webkit, now it has become a territorial war. (In good
>>> sense), :-)
>>> We will keep from messing with webkit,
>>>
>>> While, we have to make agreements in building an *Accounting Financial
>>> Reports Agnostic, *
>>> *An API, something where everybody can plug and create their own reports
>>> on top of *
>>> *Our API + Preferred Report Engine.*
>>>
>>> There are good features in the reports and in order to be coherent we
>>> should both recede.
>>>
>>> Lately our module have become less dependant on parsers or special
>>> features that are only
>>> available to a particular tools, in order to keep our customers more
>>> open to new tools
>>> this way we have being building this agnostic approach I am talking
>>> about,
>>>
>>> It is good for the sake of survival letting two different or more of the
>>> same kind to adapt and survive.
>>>
>>> Then What I will ask you Comm Guys from this Issue is make a coordinated
>>> effort,
>>> I liked rml, and I like webkit, but none of them can be superseded by
>>> the other, each
>>> one has its weakness and strengths. That was the reason to step on your
>>> side.
>>>
>>> Now we should schedule an agenda, to begin our new roadmap to 8, with
>>> common grounds.
>>>
>>> PD.: making wired reports like Excel one is an awful idea, can be done
>>> with no hassle
>>> making webkit to print reports in html, I Think is prettier,
>>> but feel free to disrgard my comments
>>>
>>>
>>> Best Regards.
>>>
>>> Hbto.
>>>
>>>
>>> 2013/10/28 Frédéric Clementi <frederic.clementi@xxxxxxxxxxxxxx>
>>>
>>>> English Doc for account_financial_reports_webkit here ->
>>>> http://bit.ly/16g3uSZ
>>>>
>>>>
>>>>
>>>> Cordialement,
>>>>
>>>>
>>>>
>>>>
>>>> *camptocamp*
>>>>
>>>> INNOVATIVE SOLUTIONS
>>>>
>>>>
>>>>
>>>>
>>>> BY OPEN SOURCE EXPERTS
>>>>
>>>> *Frédéric Clementi*
>>>>
>>>>
>>>>
>>>>
>>>> Project Manager
>>>> Business Solutions
>>>>
>>>> +41 21 619 10 41
>>>>
>>>>
>>>>
>>>>
>>>> www.camptocamp.com
>>>>
>>>>
>>>>
>>>> 2013/10/25 Nhomar Hernández <nhomar@xxxxxxxxx>
>>>>
>>>>>
>>>>> 2013/10/25 Frédéric Clementi <frederic.clementi@xxxxxxxxxxxxxx>
>>>>>
>>>>>> So Nhomar ask me a documentation about
>>>>>> 'account_financial_reports_webkit'
>>>>>> so he could compare more easily. That's what I did... here it is as
>>>>>> attachement.
>>>>>>
>>>>>
>>>>> Put a public link the list in launchpad block attachments ;-)
>>>>>
>>>>> We are almost sure the "Merge" of concepts and a clean up will be
>>>>> necesary in both modules, to be able to merge such concepts.
>>>>>
>>>>> Yo have good points and we too and IMHO think both are already
>>>>> audited, then, maybe we must move feature by feature before a merge.
>>>>>
>>>>> We are open to discuss and merge, honestly mantain the FInancial
>>>>> reaports almost by ourselve is so time consuming, it is better if we make a
>>>>> better approach.
>>>>>
>>>>> Maybe, and Just maybe due to this feature is only reporting we can
>>>>> start a new "merge" branch backporteable to 7 - 6.1 and future 8 to manage
>>>>> three computation.
>>>>>
>>>>> Another point is the IFRS compliance which become even mode difficult,
>>>>> or an estandard GAAP included, we dont have any of them we have part of one
>>>>> or another.
>>>>>
>>>>> Let's make a better proposal.
>>>>>
>>>>> For the moment: Lets read the documentation it is a good start.
>>>>>
>>>>> Regards
>>>>>
>>>>>
>>>>> --
>>>>> --------------------
>>>>> Saludos Cordiales
>>>>>
>>>>> Nhomar G. Hernandez M.
>>>>> +58-414-4110269
>>>>> Skype: nhomar00
>>>>> Web-Blog: http://geronimo.com.ve
>>>>> Servicios IT: http://vauxoo.com
>>>>> Linux-Counter: 467724
>>>>> Correos:
>>>>> nhomar@xxxxxxxxxxxxxx
>>>>> nhomar@xxxxxxxxxx
>>>>> twitter @nhomar
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~openerp-community
>>>> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~openerp-community
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openerp-community
>>> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~openerp-community
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>
>> --
>>
>>
>> *camptocamp*
>> INNOVATIVE SOLUTIONS
>> BY OPEN SOURCE EXPERTS
>>
>> *Joël Grand-Guillaume*
>> Division Manager
>> Business Solutions
>>
>> +41 21 619 10 28
>> www.camptocamp.com
>>
>>
>>
>


-- 


*camptocamp*
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

*Joël Grand-Guillaume*
Division Manager
Business Solutions

+41 21 619 10 28
www.camptocamp.com