openerp-community team mailing list archive

[Nhomar Hernández <nhomar@xxxxxxxxx>]

A new Feedback.

Which should be the right command to run OpenERP testing 100% of "views" at
least from the PoV of syntax and namespace.

I read in some place that Xavier develop some kind of wrapper to do that,
or I need to develop an unit test per web view?

Both answers are valid, I just want to be sure what is the correct approach
becaause in development time, it is so difficult to click in all views with
small changes it should be cool a wrapper to automate that.

Regards.


2014-01-28 Mantavya Gajjar <mga@xxxxxxxxxxx>

> Yes I  agree with you, that website should have the RSS, I am thinking
> about the correct approach,by then it should be implement with OpenERP.
>
>  Mantavya Gajjar
> Director
> Tiny ERP Private limited
> 16 & 17 IT Tower-I
> Info City, Gandhinagar
> Pin code: 382009
> Gujarat, India
>
> Phone : +91 79 40 500 100, Ext. 202
> Website: http://www.openerp.com
> Twitter: @mantavyagajjar
>
>
>
>
>
>
>
> On 28-Jan-2014, at 7:48 pm, Nhomar Hernández <nhomar@xxxxxxxxx> wrote:
>
>
> 2014-01-28 Mantavya Gajjar <mga@xxxxxxxxxxx>
>
>> - If we do one RSS it will push lots of information sometime people may
>> not want
>> - Its not good idea to publish everything in a single RSS, We need to
>> separate all those information it means we need a complex mechanism to
>> maintain the different RSS List
>> - Again maintain those Open and Closes RSS from security perspectives
>>
>
> Sorry I think I am confusing people.
>
> Friend. If the rss is generic you will be able to show only public
> information in a pre-built xml that all.
>
> And yes but i.e: without rss in all models in a generic way (when i say
> all models I mean models which explicitaly we tell "build a rss feed") we
> will need to reimplement in ir.ui.view (to see new pages) in
> product.product (to see new public products) in events (to see new events)
> in blogs (to see new blogs)
>
> In every single object you need to build in server side the XML that will
> be published, i.e: body is the concatenation of date + name + first 2 chars
> of description.
>
> Without a correct approach of this it can become in a "Do it in your way"
> feature which can bring a lot of performance problems.
>
> Even the most simple cms  have this feature embeded, in drupal for example
> every "content type" generate them rss.
>
> So, as we have a content based on models "not in content type" in one
> place you make some "Public information" available already (because your
> model have the correct ACL) and in other place (may be the same model) you
> just "build" the rss trought jinja2 or qweb may be.
>
> I don't understand really why it is too difficult to understand:
>
> 1.- rss is necesary (I think both are agree here).
> 2.- Every "Public Model" needs a feed to follow.
>
> If we don't think in this way, you will build a "wired " feature to blogs
> only, making you re-write again when you see we are right, or "worst" as it
> is unuseful you take off for v9 because you "think" it is not good enought
> (it happen)
>
> 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
>
>
>


-- 
--------------------
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