From: Russ T. <ru...@i2...> - 2004-07-26 17:08:03
|
I'm inquiring as to whether or not anyone has implemented a custom date=20 field for mantis or if one is already in development. I'm considering=20 upgrading to 0.19 when it comes out, but I either need to migrate our=20 custom date field implementation to 0.19 or move to another implementation.= =20 If there isn't currently a design or implementation, I'd like to solicit=20 opinions on including this feature in an upcoming release. Our current=20 implementation is a text field that can be populated with the aid of=20 http://dynarch.com/mishoo/calendar/ or typed in directly. Search support is= =20 also present; however, I'm not sure how to handle that in the new version=20 of mantis. Thanks in advance for any feedback. =2D-=20 Russ Tennant ru...@i2... |
From: Mitch \(WebCob\) <mi...@we...> - 2004-07-26 18:20:40
|
Very nice - what do you use it for? Due date? ETA Date? What's the impact of this calendar library? Does it add much to the age loads? Is the license compatible? I've heard people go on about (and I agree to an extent) about the evils of creating dependancies... Ideally, there would probably be some easy separation of the date field (which could be manually entered and validated) which would make the JS code optional so that if it breaks another version could be implemented or it could be removed... I've not heard of this (date stuff) being completed, but I think there are outstanding issues recorded that need this sort of thing... m/ > -----Original Message----- > From: man...@li... > [mailto:man...@li...]On Behalf Of Russ > Tennant > Sent: Monday, July 26, 2004 10:08 AM > To: man...@li... > Subject: [Mantisbt-dev] Custom date field > > > > I'm inquiring as to whether or not anyone has implemented a custom date > field for mantis or if one is already in development. I'm considering > upgrading to 0.19 when it comes out, but I either need to migrate our > custom date field implementation to 0.19 or move to another > implementation. > > If there isn't currently a design or implementation, I'd like to solicit > opinions on including this feature in an upcoming release. Our current > implementation is a text field that can be populated with the aid of > http://dynarch.com/mishoo/calendar/ or typed in directly. Search > support is > also present; however, I'm not sure how to handle that in the new version > of mantis. Thanks in advance for any feedback. > > -- > Russ Tennant > ru...@i2... > |
From: Russ T. <ru...@i2...> - 2004-07-26 20:09:02
|
On Monday 26 July 2004 01:20 pm, Mitch (WebCob) wrote: > Very nice - what do you use it for? Due date? ETA Date? We use the dates to record when an issue is scheduled to be staged for qa /= =20 testing and when an issue is scheduled for release. This is used mostly to= =20 track web application type software.=20 > What's the impact of this calendar library? Does it add much to the age > loads? Is the license compatible? I've heard people go on about (and I > agree to an extent) about the evils of creating dependancies... Ideally, > there would probably be some easy separation of the date field (which > could be manually entered and validated) which would make the JS code > optional so that if it breaks another version could be implemented or it > could be removed... The code for the calendar (date picker) is licensed under the LGPL. It coul= d=20 be completely optional, there is no reason why someone couldn't type the=20 date into the field directly or use another date picker.=20 Mihai's calendar is fairly simple to install and use. It has no dependencie= s=20 that I'm aware of. The only problem I can think of is that some translation= =20 may need to be done to support all the languages that the calendar=20 supports. The version I have supports the following languages. af br ca cs da de du el en es fi fr hr hr hu it jp ko ko lt lt nl no pl pl= =20 pt ro ru si sk sp sv tr zh > I've not heard of this (date stuff) being completed, but I think there > are outstanding issues recorded that need this sort of thing... > > m/ =2D-=20 Russ Tennant ru...@i2... |
From: Paul R. <pa...@qu...> - 2004-07-26 20:33:55
|
I was wondering about whether add a date field as part of other custom field stuff I've been playing with. Had been briefly thinking about just using the same 'date selector' as the filter code uses atm. Thoughts? Paul > -----Original Message----- > From: man...@li... > [mailto:man...@li...] On Behalf > Of Russ Tennant > Sent: 26 July 2004 21:09 > To: man...@li... > Subject: Re: [Mantisbt-dev] Custom date field > > On Monday 26 July 2004 01:20 pm, Mitch (WebCob) wrote: > > Very nice - what do you use it for? Due date? ETA Date? > > We use the dates to record when an issue is scheduled to be > staged for qa / testing and when an issue is scheduled for > release. This is used mostly to track web application type software. > > > What's the impact of this calendar library? Does it add much to the > > age loads? Is the license compatible? I've heard people go on about > > (and I agree to an extent) about the evils of creating > dependancies... > > Ideally, there would probably be some easy separation of the date > > field (which could be manually entered and validated) which > would make > > the JS code optional so that if it breaks another version could be > > implemented or it could be removed... > > The code for the calendar (date picker) is licensed under the > LGPL. It could be completely optional, there is no reason why > someone couldn't type the date into the field directly or use > another date picker. > > Mihai's calendar is fairly simple to install and use. It has > no dependencies that I'm aware of. The only problem I can > think of is that some translation may need to be done to > support all the languages that the calendar supports. The > version I have supports the following languages. > > af br ca cs da de du el en es fi fr hr hr hu it jp ko ko lt > lt nl no pl pl pt ro ru si sk sp sv tr zh > > > I've not heard of this (date stuff) being completed, but I > think there > > are outstanding issues recorded that need this sort of thing... > > > > m/ > > > > > -- > Russ Tennant > ru...@i2... > |
From: Mitch \(WebCob\) <mi...@we...> - 2004-07-26 21:23:00
|
> -----Original Message----- > From: man...@li... > [mailto:man...@li...]On Behalf Of Paul > Richards > Sent: Monday, July 26, 2004 1:34 PM > To: man...@li... > Subject: RE: [Mantisbt-dev] Custom date field > > > I was wondering about whether add a date field as part of other > custom field > stuff I've been playing with. > > Had been briefly thinking about just using the same 'date selector' as the > filter code uses atm. > > Thoughts? > > Paul Personally, I like having both extreme's as an option. Let me type it, or let me pick it. The existing pick list system (though easy to implement and I admit doing similar myself) is a pain to type, and a pain to pick. my 2 pennies. As an aside... Also, what does "start date" and "end date" mean? Does it filter for any issues with activity in those dates? Or does it filter any issue created in those dates? or ? thanks. m/ |
From: Julian F. <ju...@be...> - 2004-07-26 22:23:17
|
Just as some more reference data there are more and more fairly simple applications coming out in javascript to do this kind of stuff. This is a particularly cool application for date inputs: http://simon.incutio.com/archive/2003/10/06/betterDateInput Not saying we necessarily want to go this way at all (I try to avoid JS as much as the next guy); I jus think it's interesting to see what can be done. And, combined with some server-side checks for base functionality this kind of thing can be a useful addition for those who *do* have JS enabled. Also, thinking about our problem of entering/choosing user names from the picklist with thousands of users, we could look at doing what PHP did with their documentation site: http://ca3.php.net/search.php?show=quickref& Or using something like this which is becoming pretty standard in the major browsers it seems: http://developer.apple.com/internet/webcontent/xmlhttpreq.html Hope these prove inspiring to somebody, Julian Mitch (WebCob) wrote: > >>-----Original Message----- >>From: man...@li... >>[mailto:man...@li...]On Behalf Of Paul >>Richards >>Sent: Monday, July 26, 2004 1:34 PM >>To: man...@li... >>Subject: RE: [Mantisbt-dev] Custom date field >> >> >>I was wondering about whether add a date field as part of other >>custom field >>stuff I've been playing with. >> >>Had been briefly thinking about just using the same 'date selector' as the >>filter code uses atm. >> >>Thoughts? >> >>Paul > > > Personally, I like having both extreme's as an option. > > Let me type it, or let me pick it. > > The existing pick list system (though easy to implement and I admit doing > similar myself) is a pain to type, and a pain to pick. > > my 2 pennies. > > As an aside... > > Also, what does "start date" and "end date" mean? Does it filter for any > issues with activity in those dates? Or does it filter any issue created in > those dates? or ? > > thanks. > > m/ > > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click > _______________________________________________ > Mantisbt-dev mailing list > Man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |
From: Russ T. <ru...@i2...> - 2004-07-27 15:54:22
|
On Monday 26 July 2004 05:23 pm, Julian Fitzell wrote: > Just as some more reference data there are more and more fairly simple > applications coming out in javascript to do this kind of stuff. > > This is a particularly cool application for date inputs: > > http://simon.incutio.com/archive/2003/10/06/betterDateInput > > Not saying we necessarily want to go this way at all (I try to avoid JS > as much as the next guy); I jus think it's interesting to see what can > be done. And, combined with some server-side checks for base > functionality this kind of thing can be a useful addition for those who > *do* have JS enabled. My opinions on different input methods: I personally like to use a calendar as a date picker. It is much quicker=20 than typing - two clicks in most cases. Also, it is a familiar interface to= =20 most people. Think about how personal information managers are used=20 (computer driven or paper driven). I'd rank a date picker that is three=20 drop downs (at most 6 clicks) about the same as typing the date (1 click += =20 typing). The drop downs are nicer than typing since there is no room for=20 guessing the format of the date. The nice thing about using the jscalendar= =20 as a date picker is it lets the user either type into the text box or pick= =20 the date via the calendar. Being able to type a date into the input area in= =20 many different formats is a neat idea, but less technical users may find=20 the interface confusing. I'd try to avoid freeform entry of structured data= =20 if it is possible.=20 The best way to make a decision would be to provide a sample interface with= =20 different input methods, then ask 3-4 non technical users of the bug=20 tracker which input method they prefer and why. I tried this with 2 people= =20 here at work on our modified bugtracker and the 0.19a2 bugtracker. Both=20 prefer the calendar because it mimics how they select dates for=20 appointments, it's similar to date selection in windows, etc. The dropdowns= =20 came in second. I didn't offer the input method that guesses the format of= =20 input in the interface, but I described it. =2D-=20 Russ Tennant ru...@i2... |
From: Lee O'M. <lee...@om...> - 2004-07-30 19:29:28
Attachments:
dhtml_filters.tar
|
Julian Fitzell wrote: ... > Or using something like this which is becoming pretty standard in the > major browsers it seems: > > http://developer.apple.com/internet/webcontent/xmlhttpreq.html > > Hope these prove inspiring to somebody, Okay, so I bit. I've updated the filters and assembled some javascript so that when you click on the field name, the value bellow is replaced with the appropriate form element(s), "live". This is achieved using XMLHttpRequest and DHTML. I've tested it (on WinXP) in IE 5, 5.5 & 6, Firefox 0.9 and Opera 7.5. The event handlers are assigned onload (the original href remains unaffected). If the browser doesn't support XMLHttpRequest, the links work as before. The attached contains five files: * dhtml_filters.patch : patch against latest CVS - view_all_inc.php and config_defaults_inc.php * javascript/dynamic_filters.js : calls the PHP script and handles the responses. Based on [1] * javascript/xmlhttprequest.js : compatibility layer for Opera [2] * javascript/addLoadEvent.js : event handler helper [3] * return_dynamic_filters.php : PHP script that responds to the JS requests 1. http://www.creatimation.net/journal/live-request 2. http://www.scss.com.au/family/andrew/webdesign/xmlhttprequest/ 3. http://simon.incutio.com/archive/2004/05/26/addLoadEvent I'm sure it's far from perfect, and I haven't been able to test on any other platforms. I did this mostly for the learning experience, since I'm no JS expert. I do like the effect though. If anyone has feedback(positive or otherwise) I'd appreciate it. -- Lee |
From: Andre E. <in...@gm...> - 2004-07-30 20:27:41
|
Missing file: core/filters_dynamic_inc.php On Fri, 30 Jul 2004 12:28:30 -0700, Lee O'Mara <lee...@om...> wrote: > Julian Fitzell wrote: > .... > > Or using something like this which is becoming pretty standard in the > > major browsers it seems: > > > > http://developer.apple.com/internet/webcontent/xmlhttpreq.html > > > > Hope these prove inspiring to somebody, > > Okay, so I bit. > > I've updated the filters and assembled some javascript so that when you > click on the field name, the value bellow is replaced with the > appropriate form element(s), "live". This is achieved using > XMLHttpRequest and DHTML. I've tested it (on WinXP) in IE 5, 5.5 & 6, > Firefox 0.9 and Opera 7.5. > > The event handlers are assigned onload (the original href remains > unaffected). If the browser doesn't support XMLHttpRequest, the links > work as before. > > The attached contains five files: > * dhtml_filters.patch : patch against latest CVS - view_all_inc.php and > config_defaults_inc.php > * javascript/dynamic_filters.js : calls the PHP script and handles the > responses. Based on [1] > * javascript/xmlhttprequest.js : compatibility layer for Opera [2] > * javascript/addLoadEvent.js : event handler helper [3] > * return_dynamic_filters.php : PHP script that responds to the JS > requests > > 1. http://www.creatimation.net/journal/live-request > 2. http://www.scss.com.au/family/andrew/webdesign/xmlhttprequest/ > 3. http://simon.incutio.com/archive/2004/05/26/addLoadEvent > > I'm sure it's far from perfect, and I haven't been able to test on any > other platforms. I did this mostly for the learning experience, since > I'm no JS expert. I do like the effect though. If anyone has > feedback(positive or otherwise) I'd appreciate it. > > -- > Lee > > > > |
From: Lee O'M. <lee...@om...> - 2004-07-30 22:05:38
Attachments:
filters_dynamic_inc.php
|
Andre Eisenbach wrote: > Missing file: > core/filters_dynamic_inc.php (blush) -- L |