New module dashboard

[yangoon1, 2009-12-21 12:52:26]

+ https://bugs.tryton.org/roundup/issue1343

Isn't this a core feature to be delivered directly with the server?

http://codereview.appspot.com/179112/diff/1/3
File INSTALL (right):

http://codereview.appspot.com/179112/diff/1/3#newcode8
INSTALL:8: * egenix-mx-base (http://www.egenix.com/products/python/)
not needed any more due to your great fixes;)

[ced1, 2009-12-21 13:08:30]

On 2009/12/21 12:52:26, yangoon wrote:
> 
> Isn't this a core feature to be delivered directly with the server?
> 

We must be as modular as possible.
If the feature can be put in a module, it is better.

[yangoon1, 2009-12-21 13:55:03]

On 2009/12/21 13:08:30, ced wrote:
> On 2009/12/21 12:52:26, yangoon wrote:
> > 
> > Isn't this a core feature to be delivered directly with the server?
> > 
> 
> We must be as modular as possible.
> If the feature can be put in a module, it is better.

Yes, ir, res, etc, are also modules, but they are included in the server.
I would propose a new folder sysmodules for core modules (and if not too
complicated to migrate all sys modules there)

[udono, 2009-12-21 17:19:34]

http://bugs.tryton.org/roundup/issue1345

[udono, 2009-12-21 18:08:20]

Very very nice! Works good for me.

[udono, 2009-12-21 18:14:54]

one feature whish:
when I select a record, it would be great, when the choosen record opens in form
view when I press open.

[udono, 2009-12-21 18:36:57]

When choosing Action Dashboard as Dasboard Action, the following error
results.It would be good, to filter the Dasboard from the Actions.

Traceback (most recent call last):
  File "/trytond/protocols/netrpc.py", line 47, in run
    res = dispatch(host, port, 'NetRPC', *msg)
  File "/trytond/protocols/dispatcher.py", line 119, in dispatch
    obj = pool.get(object_name, type=object_type)
  File "/trytond/pool.py", line 138, in get
    return self._pool[self.database_name][type][name]
KeyError: None

[udono, 2009-12-21 19:44:37]

On 2009/12/21 18:36:57, udo.spallek wrote:
> When choosing Action Dashboard as Dasboard Action, the following error
> results.It would be good, to filter the Dasboard from the Actions.
> 
> Traceback (most recent call last):
>   File "/trytond/protocols/netrpc.py", line 47, in run
>     res = dispatch(host, port, 'NetRPC', *msg)
>   File "/trytond/protocols/dispatcher.py", line 119, in dispatch
>     obj = pool.get(object_name, type=object_type)
>   File "/trytond/pool.py", line 138, in get
>     return self._pool[self.database_name][type][name]
> KeyError: None
Is fixed with Patch set 3. 

But I am missing the complete Dashboard inside the small frame ;-)

[udono, 2009-12-21 19:59:42]

Stack layouts work for me.

[udono, 2009-12-21 20:01:20]

Another feature idea:
Make frame-boarders user-resizable, and store the settings.

[yangoon1, 2009-12-22 12:13:18]

On 2009/12/21 20:01:20, udo.spallek wrote:
> Another feature idea:
> Make frame-boarders user-resizable, and store the settings.

Would be nice indeed! Frames are changing on switch view, but it would make
sense nevertheless.

[yangoon1, 2009-12-22 12:42:03]

On 2009/12/21 18:14:54, udo.spallek wrote:
> one feature whish:
> when I select a record, it would be great, when the choosen record opens in
form
> view when I press open.

I would support, that the mostly wished and expected behavior would be to see
the selected record(s) in form view. And it would be a great feature to be able
to open several selected records in new tabs at once.

Drawbacks: Since you can choose multiple records at once, a great number could
kill the client. Perhaps this could be solved by a max number of records to be
opened from a board view. And a request, if max number is exceeded: 'You are
going to open <number_of_records> tabs. Do you really want to proceed?'

[ced1, 2009-12-22 13:53:42]

On 2009/12/22 12:42:03, yangoon wrote:
> On 2009/12/21 18:14:54, udo.spallek wrote:
> > one feature whish:
> > when I select a record, it would be great, when the choosen record opens in
> form
> > view when I press open.
> 
> I would support, that the mostly wished and expected behavior would be to see
> the selected record(s) in form view. And it would be a great feature to be
able
> to open several selected records in new tabs at once.
> 
> Drawbacks: Since you can choose multiple records at once, a great number could
> kill the client. Perhaps this could be solved by a max number of records to be
> opened from a board view. And a request, if max number is exceeded: 'You are
> going to open <number_of_records> tabs. Do you really want to proceed?'

I think this is not the place to talk about new features.
You should use roundup or the wiki.