| chat.freenode.net #tryton log beginning Wed Mar 27 00:00:01 CET 2013 | ||
| 2013-03-27 10:47 <Hamra> greetings everyone, on the windows client, what should i do to have the buttons (like "next record" "new record" "switch view" etc..) appear in the language the user chose? | ||
| 2013-03-27 10:59 -!- rpit58(~ralf@dslb-088-071-234-098.pools.arcor-ip.net) has left #tryton | ||
| 2013-03-27 10:59 -!- rpit(~ralf@dslb-088-071-234-098.pools.arcor-ip.net) has left #tryton | ||
| 2013-03-27 10:59 <prusglajotemis> cedk: yesterday i asked about BOM's tab, but today my situation is that: | ||
| 2013-03-27 11:00 <prusglajotemis> cedk: on one tryton server I see bom's, default locations and Products, but on other tryton server I see only Variants. both tryton servers identical (cloned from trunk) but on different computers. | ||
| 2013-03-27 11:01 <cedk> prusglajotemis: I guess they are not the same | ||
| 2013-03-27 11:06 <prusglajotemis> cedk: maybe it depends on some python's libs or lib version ? | ||
| 2013-03-27 11:08 <prusglajotemis> cedk: ok then what situation should de to see only Varinats in product form ? | ||
| 2013-03-27 11:17 <cedk> prusglajotemis: if it is a service | ||
| 2013-03-27 11:22 <prusglajotemis> cedk: but I see Variants then product type is Goods | ||
| 2013-03-27 11:50 <mrechte> Hello. Please is this type of code construction correct: | ||
| 2013-03-27 11:50 <mrechte> journals = Journal.browse(...) | ||
| 2013-03-27 11:51 <mrechte> for journal in journals | ||
| 2013-03-27 11:51 <mrechte> .. moves = Move.browse(...) | ||
| 2013-03-27 11:51 <mrechte> .. journal.moves = moves | ||
| 2013-03-27 11:53 <mrechte> I wish to pass "journals" to a report | ||
| 2013-03-27 12:09 <coeps> Hi, I havent found any hint towards Attachments in the docs. Is there a way to attach files as attachment by using the API ?? For example, it would be nice to add a report directly as an attachment when it is created. | ||
| 2013-03-27 12:12 <cedk> coeps: attachment is just a Model like any other | ||
| 2013-03-27 12:13 <cedk> mrechte: it is not clear what you want to do | ||
| 2013-03-27 12:43 <mrechte> cedk: I created the following code review: http://codereview.tryton.org/747004/ | ||
| 2013-03-27 12:45 <cedk> mrechte: can read anything and more over codreview of Tryton is for Tryton dev. | ||
| 2013-03-27 14:57 <coeps> Is it possible to use multiple inheritance, like inherit another producttype from product.template. If yes, must the template hold a One2Many field to each childclass? | ||
| 2013-03-27 15:07 <coeps> The docs only require the Many2One field in the spezialized class | ||
| 2013-03-27 15:09 <cedk> coeps: _inherits is gone in the next release | ||
| 2013-03-27 15:09 <cedk> coeps: better to no more develop base on it | ||
| 2013-03-27 15:11 <coeps> cedk: Thanks for the warning. Will inheritance be removed as a feature or will it be replaced by another concept? | ||
| 2013-03-27 15:11 <cedk> coeps: just removed | ||
| 2013-03-27 15:14 <cedk> coeps: indeed it doesn't change anything to the data modeling, it is just how you can display/create record that is changed | ||
| 2013-03-27 15:17 <coeps> cedk: I am confused, do you refer to inheritance (feature) or to the One2Many field question? | ||
| 2013-03-27 15:23 <cedk> coeps: inheritance | ||
| 2013-03-27 15:48 -!- the_ant(~asep@180.247.138.78) has left #tryton | ||
| 2013-03-27 16:18 <coeps> cdek: if inheritance is removed, will there be (or already is) another way to save coding when two models needs to be separated bur share a lot of common functionality? | ||
| 2013-03-27 16:18 <coeps> my plan was to implement the common stuff in a template and use 3 different children for the separation and the special functionality | ||
| 2013-03-27 16:19 <cedk> coeps: you can use Python oop | ||
| 2013-03-27 16:20 <coeps> cedk: but not including fields or? | ||
| 2013-03-27 16:23 <cedk> coeps: why? | ||
| 2013-03-27 16:26 <coeps> cedk: The moment your wrote that I had an Idea. One more detail, will there be a table for the baseclass in the db? or will the fields from the baseclass just be existent in the childtables? | ||
| 2013-03-27 16:30 <cedk> coeps: if you use Python oop, each Model will write in his own table | ||
| 2013-03-27 16:31 <cedk> coeps: but if you can have a look at product template/variant in trunk to see how you can do to share common values | ||
| 2013-03-27 16:52 <coeps> cedk: Am I correct that __getattr__ does the trick in template/variant? | ||
| 2013-03-27 16:55 <cedk> coeps: yes but only on server side | ||
| 2013-03-27 18:38 <coeps> cdek: I don't see how it is done on the client, but with seeing it in the client at the time will help. However, the new way of defining views, is that how it will be done from Version2.8 on? | ||
| 2013-03-27 18:39 <coeps> cedk: what I mean is the ir.ui.view part, separated and without cdata tag. | ||
| 2013-03-27 18:41 <cedk> coeps: yes | ||
| 2013-03-27 18:41 <cedk> coeps: it is already working in 2.6 but modules was not converted on time | ||
| 2013-03-27 18:43 <coeps> cdek: cool, so I know what I have todo now. The views are identified by the filename and must ly in the "view" subfolder. Anymore to consider? | ||
| 2013-03-27 18:43 <cedk> coeps: no | ||
| 2013-03-27 18:43 <coeps> cdek: Thanks | ||
| 2013-03-27 20:44 <coeps> cdek: You wrote that when using python oop, each model will create its own table. I created a baseclass A(Modelview,Modelsql) and created 2 subclases (sub(A), sub2(B)) in python style. Both subclasses have a custom field. In the database there is only one table module_baseclass. The fields of the subclass are just added to the baseclass. Did I totally misunderstand you? | ||
| 2013-03-27 20:45 <coeps> cdek: When marking both fields in subclass as required, I cannot add a single field to the table (I created a form for each model), since always one constraint is violated. | ||
| 2013-03-27 20:50 <cedk> coeps: of course a table is created for each Model you register | ||
| 2013-03-27 20:50 <cedk> coeps: but you can use Mixin to prevent that | ||
| 2013-03-27 20:53 <coeps> cdek: my classes are listed in __init__.py.register(), do I need to register them differently? | ||
| 2013-03-27 20:54 <cedk> coeps: I don't know what you want to do | ||
| 2013-03-27 21:00 <coeps> cedk: I think I found it (but I still have to test it). When adding the baseclass Base to the __ini__py.register() method, only the baseclass_table is created. The subcluass_tables are not created. When I remove it and only have the Subclasses registered, their tables will be created and (of course) not the baseclass one. | ||
| 2013-03-27 21:01 <coeps> cdek: in the first case, baseclass and subclasses are given to register() as arguments. |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!