IDempiere/FullMeeting20140514

⇐ Table of Contents | Full Meeting Minutes | Full Meeting 2014-05-14

CarlosRuiz: Good morning
nmicoud: Bonjour
CarlosRuiz: will be checking queue
nmicoud: any chance to integrate https://idempiere.atlassian.net/browse/IDEMPIERE-1899 ?
CarlosRuiz: sure let me check it today
nmicoud: thanks
Deepak_: Good Morning/ Noon Everybody
Deepak_: Carlos, Do we have iDempiere architecture diagram?
CarlosRuiz: database?
Deepak_: No
Deepak_: Like system architecture document?
CarlosRuiz: I don't think so - I've seen several trials to document that - but none complete
hieplq: @CarlosRuiz, I sugest make new ticket for add more comment code, at least head of class and function
CarlosRuiz: yep - that sounds fine
CarlosRuiz: I remember reading about some agile practices against comments - not saying that we need to apply it here :-)
norbertbede: hi all dear team
CarlosRuiz: Hi norbertbede
norbertbede: we worked with hiep and together on issue 1334 - Run one or more processes from Info Window
norbertbede: looks me we have base code and would be nice to say opinion - screenshot and code is attached
norbertbede: we need support on this to decide and finish
norbertbede: thnks
hieplq: hi norberbede.
hieplq: I think option 3 can with a responsive design
hieplq: list button show when have a 3,4 button (it's rely to text in button) when total with of all button > max, auto swith to dropdow
CarlosRuiz: reading ...
hieplq: @CarlosRuiz, wdyt about IDEMPIERE-1334, 1. add support multi process button, 2. remove button of red, combine it to multi button, 3. add default print button
CarlosRuiz: yep - reading that one
CarlosRuiz: option 3 could be also to add a IsButton flag
CarlosRuiz: if not button - then is a dropdown
CarlosRuiz: the imageURL just make sense for button?
hieplq: yes.
CarlosRuiz: as a user I think I would prefer buttons - as implementor I would prefer to have the option for dropdown too :-)
hieplq: how to when too much button?
Deepak_: I thing adding multiple button make more sense
hieplq: yes. i also like button, but must resolve case have too much button
CarlosRuiz: you just keep adding buttons to the toolbar - it would jump to next line?
norbertbede: we talk about compact (dropdown) and comfortable version. i
hieplq: @CarlosRuiz. never test, just think about this case. will test it.
hieplq: but muilti line is not nice :)
CarlosRuiz: yep, that's when configurable dropdown makes sense
norbertbede: because that i why i vote for make default dropdown, make configurable isbutton
norbertbede: dropdown version not yet coded.
hieplq: it's not hard. will soon make it affter meeting
norbertbede: ok. thnks
CarlosRuiz: hieplq, and we would need to migrate the actual processID on master to the detail, and hide or inactivate the processID column on master
hieplq: yes. will do.
CarlosRuiz: another suggestion - when filling the dropdown list of processes (or list of buttons) - you need to check for role access
CarlosRuiz: if the role doesn't have access better not to show the button just to say later "you cannot execute it"
hieplq: ah. yes like this.
hieplq: @CarlosRuiz, how about default print button.
hieplq: i remeber hear it in a meeting
CarlosRuiz: what's that?
CarlosRuiz: on info window?
hieplq: yes.
hieplq: have a default print format for all info window. it print as excel
CarlosRuiz: like the account info
CarlosRuiz: that sounds good - just check the role has export permission
CarlosRuiz: now, wondering if you can set a report instead of a process in the button list
hieplq: report is more diffirence from process?
CarlosRuiz: in dictionary is the same
CarlosRuiz: reports are processes providing an output
hieplq: with output, I can't call it from button?
CarlosRuiz: not sure how would that work
CarlosRuiz: just a draft idea - no need to implement it at this stage
hieplq: ah yes. just idea. will discover process of report late
Deepak_: Yes, default print format. Also configurable report
Deepak_: Some time need to have multiple print format for same info view
hieplq: same print button in adwindow :)
Deepak_: yes, but making user friendly look
Deepak_: For example we can have easy access to print pick ticket, shipping label and invoice from shipment info window
norbertbede: i can imagine to show processess and print formats in same dropdown. we need a separator between and add prefix: process/report - change process button name to "RUN/start"
norbertbede: then we save place make it compact and improve functionality lot
hieplq: @CarlosRuiz. other ticket i want ask. https://idempiere.atlassian.net/browse/IDEMPIERE-1540
hieplq: I think autocomplete shoud replace default combobox in case combobox have a lot item
CarlosRuiz: there is already a flag AD_Column.IsAutoComplete
CarlosRuiz: is just enabled for strings AFAIR
CarlosRuiz: you could use it also for this purpose
hieplq: ah. i will implement autocomplete and leave for implementor decide.
CarlosRuiz: nmicoud, reviewing IDEMPIERE-1899
nmicoud: ok, thanks
CarlosRuiz: the method setContent is not used - can I drop it? or you need it?
nmicoud: let me check, do not remember
nmicoud: i've create a new setContentSignature method to keep the old one, but just for test purpose
nmicoud: i think we could remove the 'old' setContent
nmicoud: and rename setContentSignature =>setContent
CarlosRuiz: ok
norbertbede: @carlos take a look please to this. https://idempiere.atlassian.net/browse/IDEMPIERE-1792
norbertbede: we found default logic field was removed from info window. why. we cant get answer why how to set default value
norbertbede: eg. if open info window i want show dropdown active records = default
norbertbede: as in standard window
CarlosRuiz: have you tried with an advanced role?
norbertbede: hm not. but i will try it now mmt
norbertbede: i login as SuperUser@System.*/System Administrator opening Info window. default logic field mssing
CarlosRuiz: let me check in demo ...
norbertbede: this role has advanced role flag true
norbertbede: thanks
norbertbede: my developer report this too. believe its not our mistake...
CarlosRuiz: ah sorry - I thought the field was there before - but you say it has not been implemented
CarlosRuiz: yes - that can be helpful - as well as implementing preferences for those fields
norbertbede: we have in database. but that was migrated from adempiere
norbertbede: then we thought was removed
norbertbede: im crying now why im consultant cant coding.. :)
CarlosRuiz: nmicoud, the add text automatically is not happening
nmicoud: ah ? with patch v2 ?
CarlosRuiz: I see the code there - let me debug
CarlosRuiz: instead of new MUser(Env.getCtx(), Env.getAD_User_ID(Env.getCtx()), null)
CarlosRuiz: is better to use MUser.get
CarlosRuiz: that's not the issue - just a recommendation
CarlosRuiz: the problem was the tester :-D
nmicoud: héhé
nmicoud: first i used the cache
nmicoud: but then i remove it
CarlosRuiz: nmicoud, added one line and now it can parse the Name of the user
nmicoud: good
norbertbede: @carlos - simple but strategic decision required - https://idempiere.atlassian.net/browse/IDEMPIERE-1941
CarlosRuiz: nmicoud, great - received an email from Clark Kent
nmicoud: tada !
CarlosRuiz: uh oh
CarlosRuiz: but I have one problem
CarlosRuiz: two problems indeed
nmicoud: ah...
CarlosRuiz: I'll upload my modified patch - and comment there
CarlosRuiz: 1 - the other attachments are lost
CarlosRuiz: 2 - user would need to write his/her text in html notation
CarlosRuiz: all the non-html formatting from the user (i.e. newlines) is lost
CarlosRuiz: I'll upload a patch as I did some fixes
CarlosRuiz: BTW - diff --git
CarlosRuiz: to include binaries in the patch
nmicoud: ok will try it (but using windows)
nmicoud: for the html notation, perhaps we should integrate the ckEditor in WEmailEditor ?
CarlosRuiz: norbertbede, about IDEMPIERE-1941, what if you want to "inactivate" temporarily a locator (i.e. to avoid people using it)
CarlosRuiz: yep nmicoud - the string editor already has HTML capabilities in any string field
nmicoud: i means, you won't have to swith to the html mode
nmicoud: when opening, you will have the toolbar and besides the text
CarlosRuiz: I mean - what if somebody prefer to send plain text mail?
nmicoud: he won't :)
nmicoud: i see what you mean
nmicoud: so, maybe changing the current text field editor with a ckEditor ?
nmicoud: and right click / html to switch mode ?
CarlosRuiz: let me check if hengsin is available
nmicoud: and http://www.zkoss.org/zkmail/ ? or am i dreaming ?
norbertbede: @Carlos about IDEMPIERE-1941, we should implement dropdown - locator status (active, error, damaged...etc). i can design that.
norbertbede: main reason to make compactible with a big warehouse setup. and avoid picking sequences errors in layout
proSENSE: Is it possible, to configure BP or any other import, to import corretly latvian language... now its importing AÌENTS.LV as A?ENTS.LV
CarlosRuiz: proSENSE, must be an issue of the encoding you select
proSENSE: UTF-8
CarlosRuiz: nmicoud, in principle hengsin agreed that we can deprecate plain text email - and use just html - that can make the integration of the html editor easier
nmicoud: ah great!
CarlosRuiz: if is not too hard - maybe you can implement what you said
nmicoud: means that every mail sent will be HTML ?
CarlosRuiz: a toggle or right click for plain text
CarlosRuiz: but if is too hard - we can deprecate plain text
CarlosRuiz: and force html email always
nmicoud: will try it
nmicoud: but perhaps this would have to be done before 1899 ?
proSENSE: when there is a processing sales invoice - is it possible to add "service entry" or anything else as free txt? Or its needed to be entered in stock to sale?
CarlosRuiz: norbertbede, IMHO the active flag is useful in that case - to filter out things temporarily
CarlosRuiz: i.e. we don't have a way to "isolate" a portion of the warehouse during an inventory count (solved if we implement some perpetual inventory approach)
CarlosRuiz: but until those features are implemented I think allowing inactivate a locator is useful
norbertbede: ok. its ok. i will try to design this locator status proposal in a new issue
norbertbede: maybe system configurator should give us trust and make compactive until that
norbertbede: we found the issue when stockeeper deactivate 50 locators and system skips those locators on picking = make real trouble for company. in KNOW that is a specific area...
norbertbede: they scrap FIFO..
CarlosRuiz: what unpredictable behavior do you foresee?
CarlosRuiz: ah I see
CarlosRuiz: remembered a joke "a well documented bug can be a feature" :-D
CarlosRuiz: but seriously - I think the case is valid
CarlosRuiz: what if you want temporarily the system to skip a locator on picking? then that's the way
CarlosRuiz: the issue can be maybe to restrict the active flag to that user - and allow it just for a manager
norbertbede: main problem happening: when warehouse layout changing frequently, we found that after 1 year. on weekly basis for hundred of locations.
norbertbede: that shows, in extreme use cases cause issue
norbertbede: with active gflag. the problem is nobody know why a locator was deactivated. no purpose/reason
norbertbede: i dont want to push to base wms features for now
norbertbede: but we found to denied warehouse and locator deactivation when qty <>0 reasonable
norbertbede: hard to answer
norbertbede: this
norbertbede: why
norbertbede: the compromisse should be as you wrote - make role dependent that
norbertbede: agree.
norbertbede: for the future we can apply later locator statues, not importnt now.