Comment 27 for bug 501297

Revision history for this message
Raphaƫl Valyi - http://www.akretion.com (rvalyi) wrote : Re: [Bug 501297] Re: UI Useability Improvement propositions

Hello, the current o2m displaying the number "m" or related records in list
view also has a performance issue I think: it seems it makes 'm' requests to
name_get to the server to when counting the 'm' it will display (while it is
useless). For instance in the base_external_referentials modules we had to
drop the feature of displaying how many external mapping has each mapped
model because it was too slow, making hundreds of extra requests. I hope the
new system doesn't has this issue; sorry, so far I can't remember if that
was happening under the GTK or web client or both.

On Thu, Jan 7, 2010 at 4:18 AM, ppr (axelor) <email address hidden> wrote:

> Hi, Group by concept seems to be very much promising, will it it
> possible to show the O2M lines in a tree view with such gropby
> functionality instead of showing number of records. Same groupby icon,
> clicking on which will show the O2M record.
>
> Regards.
> PPR
>
> --
> UI Useability Improvement propositions
> https://bugs.launchpad.net/bugs/501297
> You received this bug notification because you are a member of OpenERP
> Drivers, which is subscribed to OpenObject Web Client.
>
> Status in OpenObject Web Client: Confirmed
>
> Bug description:
> We are working with useability experts to improve the user interface of the
> v5.2 fo OpenERP. Our deadlines:
> - January 2010 : finish all wireframes and start developments
> - February 2010: finish all designs
>
> We made some very early drafts wireframes to show you some ideas. The
> biggest changes:
>
> Search Views
> -----------------
>
> In trunk, we have new search views that can integrate buttons, business
> logic, custom filters, ... You can design custom search views per object.
> The search elements can change the domain (filter on records) or the context
> (change the values displayed of computed fields: example: the stock real and
> virtual depends on the selected warehouse in the search view of products.)
> Relational fields are available as selection box, where you can select or
> write text.The search view integrates custom filters, ability to create
> shortcuts, ...
>
> See the attached screenshot for more info. It already works in trunk GTK
> and web client.
>
> Menus
> ---------
>
> We'd like to change how OpenERP is perceived. Instead of being a "Global
> ERP that does everything", we'd like to change our image into a "Suite of
> Integrated Management Applications". The homepage, after the login, allows
> you to choose in which 'application' you want to work: Project Management,
> Accounting, ...
>
> After entering in an application, you see the menu of this application that
> always remains on the left side. All applications are visible on the above
> tabs. Someone can set is default application in his preferences. (a
> developper will remain in the Projact Management application and default to
> a context which is his current project).
>
> When you are in an 'application', you can set a default context. For
> example, in project management, you can select a project. Then all menus
> (bugs, tasks, features requests, wiki specifications, ...) automatically
> filters on this project. You may not select any project and you will see all
> tasks (like currently).
>
> For example, in the sales management tab, the context will be the
> department (case section) you are working in.
>
> Note, that this is just for the useability of the user interface. It
> doesn't change the way all objects are integrated together in OpenERP.
>
> In attached files, you have a draft wireframe design of this new UI and a
> sample .ODS file that describe the new menu structure.
>
> Dashboards
> ---------------
>
> We designed more collaborative dashboards (notes on projects, discussions,
> ...)
>
>
> Lists
> ------
>
> We will improve a lot the design of elements in a list. The attachment
> system will be simplified a lot, see the bottom right corner (normally on
> forms, not on lists). We don't open anymore the list/form of attachement.
>
>
>
>
> NOTE:
> * This is the first draft, I just received a completly different
> proposition from an other useability expert. Everything is still under
> discussion, feel free to contribute/propose others designs.
>
>
>