IDempiere/FullMeeting20130925 - Revision history

CarlosRuiz: drop JIRA notifications from log

2013-09-25T17:54:30Z

drop JIRA notifications from log

CarlosRuiz: full meeting

2013-09-25T17:54:03Z

full meeting

New page

⇐
[[IDempiere|Table of Contents]] |
[[IDempiere/Full Meeting Minutes|Full Meeting Minutes]] |
Full Meeting 2013-09-25


'''''CarlosRuiz''''': Good Morning 
'''''nmicoud''''': Bonjour 
'''''JanThielemann''''': hi 
'''''nmicoud''''': you said you were working on a 1.0d release. do you plan to integrate some improvvement of the peer review queue ? 
'''''CarlosRuiz''''': no, 1.0d would be a release from the release-1.0c branch 
'''''CarlosRuiz''''': that branch just accepting bug fixes, no new features 
'''''nmicoud''''': ok 
'''''CarlosRuiz''''': the peer review queue of new features will go into development branch - which means next release (don't know if named 1.1 or 2.0) 
'''''nmicoud''''': and do you know when you will able to integrate them in the development branch ? 
'''''CarlosRuiz''''': I think we can start today - most of the focus lately have been on stabilizing r1 - and I think is mostly done 
'''''nmicoud''''': great :) 
'''''CarlosRuiz''''': IDEMPIERE-1328 ready to integrate? 
'''''CarlosRuiz''''': ah, but you had a different idea for that one 
'''''nmicoud''''': for me,yes 
'''''nmicoud''''': yes, a new field is added on AD_Window to allow customization 
'''''nmicoud''''': it is then used for RecentItems and tab naùe 
'''''nmicoud''''': *name* 
'''''nmicoud''''': if empty, it uses the 'old' way 
'''''CarlosRuiz''''': a tip - you can include the migration scripts into the patch if you add them in mercurial (hg add) 
'''''nmicoud''''': easier than changing the name, thanks for the tip :) 
'''''CarlosRuiz''''': also - the release-1.0c scripts are going into 1.0c-release folder 
'''''CarlosRuiz''''': and the development scripts are going into 1.0z folder 
'''''nmicoud''''': and 1.0z are moved into 1.0d when the 1.0d is released ? 
'''''CarlosRuiz''''': nope - 1.0z is next release 
'''''CarlosRuiz''''': I'm still not sure if releasing 1.0d - it can become confusing 
'''''CarlosRuiz''''': in some way "1.0d" is released every day here http://ci.idempiere.org/job/iDempiere1.0cDaily/ 
'''''nmicoud''''': ok, so we will put the bug fix migration script on xxx- release folder ; and the new stuff are in the xxx.z folder ? 
'''''CarlosRuiz''''': exactly 
'''''CarlosRuiz''''': the next release "1.1" or "2.0" is released every day at http://ci.idempiere.org/job/iDempiereDaily/ (this includes development branch and 1.0z scripts) 
'''''nmicoud''''': ok, i understand 
'''''CarlosRuiz''''': on IDEMPIERE-1328 - how is intended the label to be filled? 
'''''CarlosRuiz''''': an example? 
'''''nmicoud''''': @Name@ for instance 
'''''nmicoud''''': @DocumentNo@ 
'''''nmicoud''''': any field that are used in the main tab 
'''''CarlosRuiz''''': ok, so is intended just to use context variables, not plain words - that sounds fine 
'''''CarlosRuiz''''': my question was because if intended to use plain words - we would need to add translation for that field 
'''''nmicoud''''': i guess you could use plain words 
'''''nmicoud''''': that should be useful no ? 
'''''CarlosRuiz''''': but in this case I think if you need plain words - you can add a message and use it? maybe using Msg.parse 
'''''nmicoud''''': yes, it can be done this way. But, maybe is easier to add a new field on AD_Window_Trl ? 
'''''CarlosRuiz''''': I think the intention is mostly context variables - translating it maybe make it more complex to configure (implementors tend to forget the translation and then things doesn't work on other languages as expected) 
'''''CarlosRuiz''''': and we can have the workaround in the rare case where a plain word is wanted 
'''''nmicoud''''': what should i put in the field if i want to have "BP : Joe Boss" 
'''''nmicoud''''': how the message will be identied ? 
'''''CarlosRuiz''''': that means it will show: "Business Partner: BP : Joe Boss" ? 
'''''CarlosRuiz''''': cos the window name comes first right? 
'''''nmicoud''''': let me check 
'''''nmicoud''''': yes, windowName + content of label 
'''''nmicoud''''': talking about Msg confused me 
'''''alara_Gh''''': good morning. 
'''''nmicoud''''': hi 
'''''CarlosRuiz''''': Hi Angel 
'''''CarlosRuiz''''': nmicoud, Heng Sin suggested to name the column TitleLogic instead of Label 
'''''alara_Gh''''': Can i implement a sql query as display logic? like we can do it in the default logic field? 
'''''CarlosRuiz''''': no 
'''''hengsin''''': @alara_Gh, no 
'''''hengsin''''': but you can do something like @C_DocType_ID.IsSOTrx@ 
'''''hengsin''''': that's the best you can do now 
'''''alara_Gh''''': ok i'll try that way. thanks 
'''''CarlosRuiz''''': hengsin, WDYT about this idea? https://groups.google.com/d/msg/idempiere/z1lq_6PCnow/cDtBMvec0q4J 
'''''hengsin''''': carlos, how's that different from ad_preference ? 
'''''CarlosRuiz''''': each column would be a preference - that allows us to configure the type and scope of each preference 
'''''hengsin''''': hmm ... is that supposedly an end user tool ? if yes, I think usability could be an issue here. 
'''''CarlosRuiz''''': yes - the idea is to replace the preference form by a normal window - so we can add preferences and users can set them without java coding 
'''''CarlosRuiz''''': which usability issue do you foresee? 
'''''hengsin''''': well, a window with hundreds of preference without any categorization is hardly user friendly. 
'''''CarlosRuiz''''': yep - I was thinking the categorization can be achieved with field groups 
'''''hengsin''''': how do you control security here if every column is a preference ? 
'''''CarlosRuiz''''': sorry - don't understand the question 
'''''hengsin''''': I means there might be some preference that is not settable by every role ? 
'''''nmicoud''''': sorry Carlos, did'nt see your msg ; no pb for changing column name 
'''''CarlosRuiz''''': ah, like LogMigrationScript and DictionaryMaintenance, I think those must be kept in WPreference, but mostly because those don't need to be persisted - you could also set role column access if needed for a preference 
'''''Edwin_Ang''''': hi everyone :) 
'''''nmicoud''''': Hi Edwin 
'''''Not-001''''': [IDEMPIERE] nberisha updated IDEMPIERE-1355 Attachment set to "AbstractADWindowContent.patch" 
'''''Not-001''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1355 
'''''Not-001''''': [IDEMPIERE] nberisha updated IDEMPIERE-1355 
'''''Not-001''''': [IDEMPIERE] Hi, Attached is the fix for this issue. It is working OK for me. Regards, Naim 
'''''Not-001''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1355 
'''''CarlosRuiz''''': Hi Edwin_Ang 
'''''Not-001''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-1355 labels set to "+Patch" 
'''''Not-001''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1355 
'''''Edwin_Ang''''': hi nicolas, carlos 
'''''hengsin''''': hi Edwin 
'''''Edwin_Ang''''': hi hengsin 
'''''Not-001''''': [iDempiere] CarlosRuiz_globalqss pushed 3 commits to release-1.0c [+2/-0/±10] https://bitbucket.org/idempiere/idempiere/commits/ 
'''''Not-001''''': [iDempiere] hengsin 70f292b - #1003117 IDEMPIERE-1305 Payment allocation form- Need alignment of field to be corrected 
'''''Not-001''''': [iDempiere] hengsin 62da40c - #1002861 Product Costing in Bizidum. Fixed reversal for matchpo, matchinv and cost adjustment. IDEMPIERE-1180 IDEMPIERE-1188 
'''''Not-001''''': [iDempiere] hengsin 740e9bb - #1002868 IDEMPIERE-1188 Invoice Price Variance for Average PO Costing. Add missing foreign key constraint. 
'''''CarlosRuiz''''': so, hengsin, in the preference idea - do you think is ok - or need more thinking - we can also do a preference configuration table - and let WPreference check there and paint it 
'''''hengsin''''': if there's categorization, then it is probably ok. However, in the long run, I guess column naming could be a tricky issue. 
'''''CarlosRuiz''''': yep - maybe some naming standard would be good there 
'''''CarlosRuiz''''': like what is happening in SysConfig - no naming standard 
'''''hengsin''''': for preference configuration table - I think the good thing is that will be more flexible and allow peoples to innovate on the kind of UI for it. 
'''''hengsin''''': if we were to do a preference configuration table, we should probably reuse the same design for sysconfig as well. a better UI for sysconfig is kind of long overdue. 
'''''Not-001''''': [iDempiere] CarlosRuiz_globalqss pushed 1 commit to development [+2/-0/±10] https://bitbucket.org/idempiere/idempiere/commits/ 
'''''Not-001''''': [iDempiere] globalqss 4f27d2b - hg merge release-1.0c (forward-porting) 
'''''CarlosRuiz''''': we could also create a WPreference that renders the AD_User_Preference window different - for example creating horizontal tabs for each field group - that is more common to group preferences 
'''''ocurieles_DCS''''': hi 
'''''CarlosRuiz''''': Hi Orlando 
'''''nmicoud''''': gtg ; bye bye 
'''''Not-001''''': [iDempiere] CarlosRuiz_globalqss pushed 1 commit to development [+2/-0/±12] https://bitbucket.org/idempiere/idempiere/commits/ 
'''''Not-001''''': [iDempiere] globalqss 589aaed - IDEMPIERE-1328 Change tab name dynamically 
'''''Not-001''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-1354 status set to "Resolved" -resolution set to "Fixed" 
'''''Not-001''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1354 
'''''Not-001''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-1370 status set to "Resolved" -resolution set to "Fixed" 
'''''Not-001''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1370 
'''''Not-001''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-1328 status set to "Resolved" -resolution set to "Fixed" 
'''''Not-001''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1328 
'''''CarlosRuiz''''': OK, IDEMPIERE-1328 Change tab name dynamically finished - will install it on http://demo.idempiere.com for tests - enjoy it :-)

@@ Line 82: / Line 82: @@
 '''''Edwin_Ang''''': hi everyone :)<br>
 '''''nmicoud''''': Hi Edwin<br>
 '''''CarlosRuiz''''': Hi Edwin_Ang <br>
 '''''Edwin_Ang''''': hi nicolas, carlos<br>
 '''''hengsin''''': hi Edwin<br>
 '''''Edwin_Ang''''': hi hengsin<br>
 '''''CarlosRuiz''''': so, hengsin, in the preference idea - do you think is ok - or need more thinking - we can also do a preference configuration table - and let WPreference check there and paint it<br>
 '''''hengsin''''': if there's categorization, then it is probably ok. However, in the long run, I guess column naming could be a tricky issue.<br>
@@ Line 103: / Line 92: @@
 '''''hengsin''''': for preference configuration table - I think the good thing is that will be more flexible and allow peoples to innovate on the kind of UI for it.<br>
 '''''hengsin''''': if we were to do a preference configuration table, we should probably reuse the same design for sysconfig as well. a better UI for sysconfig is kind of long overdue.<br>
 '''''CarlosRuiz''''': we could also create a WPreference that renders the AD_User_Preference window different - for example creating horizontal tabs for each field group - that is more common to group preferences<br>
 '''''ocurieles_DCS''''': hi<br>
 '''''CarlosRuiz''''': Hi Orlando<br>
 '''''nmicoud''''': gtg ; bye bye<br>
 '''''CarlosRuiz''''': OK, IDEMPIERE-1328 Change tab name dynamically finished - will install it on http://demo.idempiere.com for tests - enjoy it  :-)<br>