| Not-f142 | [IDEMPIERE] mpowacht created IDEMPIERE-3427 Estimated Landed Cost in local currency (or any other currency) | 04:55 |
|---|---|---|
| Not-f142 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3427 | 04:55 |
| *** fachmi has joined #idempiere | 07:16 | |
| fachmi | hello | 07:17 |
| *** fachmi has quit IRC | 07:22 | |
| Not-f142 | [IDEMPIERE] hieplq updated IDEMPIERE-3426 | 14:03 |
| Not-f142 | [IDEMPIERE] don't know why but Keylistener avoid to combine alt, ctr, shift. only can use single modify key. so i use alt + pgup and alt + pgdown | 14:03 |
| Not-f142 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3426 | 14:03 |
| Not-f142 | [IDEMPIERE] hieplq updated IDEMPIERE-3426 Attachment set to "IDEMPIERE-3426-shortcutKey.patch" | 14:03 |
| Not-f142 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3426 | 14:03 |
| Not-f142 | [IDEMPIERE] hieplq created IDEMPIERE-3428 wizard to input parameter | 14:46 |
| Not-f142 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3428 | 14:46 |
| *** Adotts has joined #idempiere | 17:46 | |
| *** Adotts has quit IRC | 17:47 | |
| Not-f142 | [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-3428 | 18:05 |
| Not-f142 | [IDEMPIERE] [~hieplq], I don't get the idea, maybe an example can show better what is. If I understood correctly the plan is to replace one screen (for example with 4 parameters) with four screens with 1 parameter each? It sounds like a different way to enter data, but I think some newbie users can like that, but experienced users probably will hate it. BTW - if that's the idea I think you don't need extra tables - | 18:05 |
| Not-f142 | process parameters, sequence, help, display logic, etc. Everything is there, is just to show it in a different way. | 18:05 |
| Not-f142 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3428 | 18:05 |
| Not-f142 | [IDEMPIERE] norbert.bede updated IDEMPIERE-3428 | 19:41 |
| Not-f142 | [IDEMPIERE] [~hieplq] i suggest draw a GUI flow - or experimental prototype - to validate concept should working well. i suggest - Implement the solution on various levels: wizard is something specific to System/Client/Role/user level - cant be common for system. (ideally scriptable - i met this approach in sf.com) - i don't prefer to implement only in system-app dict level. - Also would be important attach multiple | 19:41 |
| Not-f142 | wizards for same process - usually complex process/reports lead users across various flows. - must be generally disabled to keep legacy approach - per installation. - to above parameters - isStart isFinal can be replaced by seqno regular element - define order and first/last panel - NextPanelLogic/code looks me as worklow/node/transition condition. probably same concept can be used. (probably too complex but | 19:41 |
| Not-f142 | workflows can be re-used in process parameters - however an be too complicated) ps. we submit a ticket for simplify parameter entry - re-use concept same in window customisation [~aconn7] should be involved IDEMPIERE-3025. hope my ideas help. | 19:41 |
| Not-f142 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3428 | 19:41 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!