Left: | ||
Right: |
OLD | NEW |
---|---|
(Empty) | |
1 | |
2 | |
3 Tryton 1.4 is available | |
4 ======================= | |
5 | |
6 | |
7 This new series comes up with new modules, security and performance | |
8 improvements as well as the SQLite support and welcomes the arrival of | |
9 Neso, the standalone version of Tryton. As usual, database migration | |
10 is completely automated (and works on databases created with both the | |
11 1.0 and 1.2 series). Most of bugfixes from the last 6 months of | |
12 developments have already been backported in the 1.0 and 1.2 series. | |
13 | |
14 | |
15 Database Independence and SQLite Support | |
16 ---------------------------------------- | |
17 | |
18 Database handling and access get more and more generic. As a first | |
19 alternative backend Tryton now offers support for SQLite. | |
20 | |
21 * The server is now able to do the validation of the "NOT NULL" and | |
22 field length constraints. It was necessary as SQLite doesn't handle | |
23 them yet. Moreover, it provides more user friendly error messages | |
24 (in place of SQL error coming from the DBMS). | |
25 * Generalisation of the tables sequences handling and creation of | |
26 pagination clauses ("LIMIT" and "OFFSET"), those two concepts now | |
27 being independent of the DBMS. | |
28 | |
29 | |
30 Neso | |
31 ---- | |
32 | |
33 Neso is a standalone version of Tryton: Neso takes advantage of the | |
34 new SQLite support and integrates the client and server code of | |
35 Tryton. So it's a pure desktop application with the rallied power of | |
36 Tryton without the need to configure a separate server or | |
37 database. Neso is a perfect fit for single user usage or simply for | |
38 demonstration and testing purpose. | |
39 | |
40 Another facility that came with Neso is the possibility of an | |
41 automatic database update after the restoration. | |
42 | |
43 | |
44 Security | |
45 -------- | |
46 | |
47 Security has been improved on various points: | |
48 | |
49 * Password prompt on password change to prevent abuse. | |
50 * Evaluation of code strings now prevents code injection. | |
51 * Model access checks are also performed on property fields. | |
52 * The client now informs the server on user logout to prevent session | |
53 hijacking. | |
54 * Handling of read, write, create and delete permission on record | |
55 rules. | |
56 * Salted passwords improving encryption robustness against rainbow | |
57 table attacks. | |
58 | |
59 | |
60 Performance | |
61 ----------- | |
62 | |
63 Among the most important innovations, network communication and cache | |
64 handling have been improved: | |
65 | |
66 * Gzip compression support for pysocket and XML-RPC queries on the | |
67 server. | |
68 * Use of the the gzip compression on the client side. | |
69 * Cache improvement on the server: the cache has been moved from the | |
70 "BrowseRecordList" to the cursor thus ensuring that each record is | |
71 read at most once in the same transaction. | |
72 * Fill of the cursor cache on search prevents other read queries on | |
73 same records. | |
74 * New heuristic allowing to sharply reduce the length of queries | |
75 containing a lot of identifiers. | |
76 * Results are no more ordered if it's no more necessary. | |
77 * Support of "delete_all" on "One2Many" fields allows the deletion of | |
78 records without an extra read operation and brings more consistency | |
79 with the "Many2Many" field which has already this operator. | |
80 | |
81 | |
82 User Interface | |
83 -------------- | |
84 | |
85 * Wizards optionally preserve their sizes from successive calls. | |
86 * Allow to reset user default values. | |
87 * Support for fields that contain time duration: they express hours | |
88 but may contain values like "1d" (1 day) or even "1w 2d 1:30" (1 | |
89 week, two days and one and an half hour). | |
90 * The status bar can be hidden. | |
91 * Wizard can be opened in tabs (instead of a pop-up). | |
92 * The user can choose to allow or disallow keyboard shortcuts | |
93 (accelerators) creation from the main menu. | |
94 * Keyboard navigation with keyboards arrows between widgets. | |
95 * New filters "Starts with" and "Ends with" on fields containing | |
96 strings. | |
97 * Selection fields only shows values that comply with the current | |
98 domain. | |
99 | |
100 | |
101 Other New Features | |
102 ------------------ | |
103 | |
104 * Reload of modules if files have changed: This shortens the | |
105 development cycle as the server does not need to be restarted on | |
106 file modification. This also allows to update a production server | |
107 while keeping users connected. | |
108 * New field "datetime_field" one "One2Many" and "Many2Many": this | |
109 allows to read those fields at an arbitrary date in the past and | |
110 completes the visualization of historical data. | |
111 * Use the module dependency order to apply views inheritance. View | |
112 inheritance is now systematic and predictable. | |
113 * New model "ModelSingleton": Its main use is for configuration | |
114 options that are linked to the database itself (and not the user or | |
115 the company). | |
116 * OSV is renamed to Model in the Workfow module, furthering the | |
117 refactorisation that came with the 1.2 release. | |
118 * Improvement of the database migration tools: automatic handling of | |
119 table sequence and history table when a table is renamed; indexes, | |
120 constraints and foreign keys deletion available on arbitrary tables. | |
121 * Fixed words translations in datetime formatting on server side (for | |
122 month names and days of week). | |
123 * Provide a default file name when backup is created. | |
124 * Handling of the required attribute in domains. | |
125 * Support of call to "today()" on "ir.date" from XML-RPC: provides to | |
126 an external software for what is considered to be the current date | |
127 by the Tryton server. | |
128 * Authentication code has been moved on "res.user", allowing to | |
129 overload it and provide other authentication mechanisms (see | |
130 ldap_authentication here under). | |
131 * Temporary file names containing reports are now the report name | |
132 itself. | |
133 * Backup creation and restoration are now possible for PostgreSQL | |
134 connections that need a password. | |
135 | |
136 | |
137 New modules | |
138 ----------- | |
139 | |
140 * calendar: Add CalDAV support. Allows to define calendars and events | |
141 and sync them with all calendar clients that support the CalDAV | |
yangoon1
2009/10/20 11:40:39
...supporting...
| |
142 (http://en.wikipedia.org/wiki/CalDAV) protocol. | |
143 * calendar_todo: Allow to creates Todo's (or tasks) and sync them with | |
yangoon1
2009/10/20 11:40:39
create Todos
| |
144 calendar clients. | |
145 * company_work_time: Define work times in the company. | |
146 * google_translate: Translate items with Google Translate. | |
147 * ldap_authentication: Authenticate users with OpenLDAP and Active | |
148 Directory. | |
149 * ldap_connection: Add basic support for LDAP connection. | |
150 * party_vcarddav: Add CardDAV on parties. Allows to export contact | |
151 information with the vCard format or to sync them with other | |
yangoon1
2009/10/20 11:40:39
and to sync them with CardDAV capable clients.
| |
152 softwares like mail clients. | |
153 * product_pricelist: Define price list rules. | |
154 * project: Project management. Allow to define project, link them to | |
155 parties, define tasks and sub-tasks and track time spent on it. | |
yangoon1
2009/10/20 11:40:39
...spent on them.
| |
156 * project_revenue: Add product on timesheet lines and define allowed | |
157 services for each employees. | |
yangoon1
2009/10/20 11:40:39
services per employee.
| |
158 * sale_pricelist: Define sale price list on party and sale order. | |
159 * timesheet: Timesheet Module with: | |
yangoon1
2009/10/20 11:40:39
timesheet: Define works and timesheet lines. Comes
| |
160 - Work | |
161 - Timesheet line | |
162 | |
163 And with reports: | |
164 - Hours per work, | |
165 - Hours per employee per week, | |
166 - Hours per employee per month. | |
167 | |
168 | |
169 New Features in Existing Modules | |
170 -------------------------------- | |
171 | |
172 account | |
173 ~~~~~~~ | |
174 | |
175 * Origin tax is taken into account in tax rules. | |
176 * Fix digits of amounts on tax and tax lines. | |
177 | |
178 account_invoice | |
179 ~~~~~~~~~~~~~~~ | |
180 | |
181 * Set invoice date when the invoice is opened. | |
182 * Add the invoice number to the report name. | |
183 | |
184 | |
185 account_statement | |
186 ~~~~~~~~~~~~~~~~~ | |
187 | |
188 * Fix digits of start and end balance | |
189 | |
190 | |
191 analytic_account | |
192 ~~~~~~~~~~~~~~~~ | |
193 | |
194 * Use the right currency to compute balance, debit/credit of accounts | |
195 | |
196 | |
197 currency | |
198 ~~~~~~~~ | |
199 | |
200 * Add rounding option to currency round (allow other rounding than | |
201 Half to even) | |
202 * Allow to call "compute" on "currency.currency" from XML-RPC: this | |
203 provides the currency conversions to external softwares. | |
204 | |
205 | |
206 stock | |
207 ~~~~~ | |
208 | |
209 * New group of user "Stock Force Assignment": only members of this | |
210 group will be allowed to force assignations. | |
211 * Migrate "packing_in", "packing_out", etc. tables to "shipment_in", | |
212 "shipment_out", etc.. This closes the wording correction started with | |
213 the 1.2 version of the module and provides more consistency between | |
214 the labels shown to the user and the name of the tables. The goal | |
215 was to keep the module easy to understand and to maintain. | |
OLD | NEW |