RE: [Rainbowportal-devel] Porting issuetracker to Rainbow
Brought to you by:
danijel_kecman,
manudea
From: Mark G. <mgr...@gt...> - 2005-04-16 02:24:33
|
I use a bug tracker called btnet from sourceforge. We have modified it to get rid of some bugs and to suit our purpose. It has several features that are worth considering, including being able to email bugs to the bugtracker. We have been considering porting it to rainbow, as we do not think this will be a major task. Mark, What issuetracker are you looking at? Regards, Mark -----Original Message----- From: rai...@li... [mailto:rai...@li...] On Behalf Of Mark McFarlane Sent: Saturday, 16 April 2005 5:31 AM To: rai...@li... Subject: [Rainbowportal-devel] Porting issuetracker to Rainbow Jonathon: "In your opinion after working with the issue tracker, how long would it take and how much effort would be involved in converting issue tracker to RB module..perhaps this is a worthy task for the recruits and modules groups." I haven't looked very deeply into the code yet, mostly just a few of the UI files. I haven't even opened any data access code but it is supposed to show 'best practices' for ASP.NET 2.0. There are only 5 or 6 pages in the application that could each become a Rainbow module. Filtered Issue List, Submit Issue, Custom Queries and results, Users, Projects, I think it uses user controls. I don't think it would be very hard for someone who has done this type of work before. I certainly would like to see this in Rainbow. Mark ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick _______________________________________________ Rainbowportal-devel mailing list Rai...@li... https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel |