https://wiki.cdot.senecacollege.ca/w/api.php?action=feedcontributions&user=Djhamp-g&feedformat=atomCDOT Wiki - User contributions [en]2024-03-29T00:47:38ZUser contributionsMediaWiki 1.30.0https://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=15478Bug Triage Extension2008-04-21T15:07:29Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]][[Image:buggybar-plus.png | ]][[Image:buggybar-minus.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [https://addons.mozilla.org/firefox/4117/ Firefox add-ons page]. New design first draft completed. Received first suggestion questions.<br />
===5/01/2007===<br />
hit over 1000 downloads and got a mention on the mozillazine QA blog thanks to robcee: <br />
[http://weblogs.mozillazine.org/qa/archives/2007/01/buggy_bar_extension.html#comments weblogs.mozillazine.org/qa]<br />
===31/01/2007===<br />
Release 0.2 is out and about and will be on the add-ons site soon as user testing has been finished<br />
===21/04/2008===<br />
Release 0.3 is out and will be on the add-ons site soon, other then that the project is done<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
*release 0.2<br />
*release 0.3<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
*completed user input phase and completed new paper design. now its back into the code. started by putting totalField in bugSpecs. more to come<br />
*rewrote preferences section into much nicer object. Now instances have their own login information as well as can read an XML file to determine the status options or can use the default mozilla one. Also moved options to its own section. Next I'll be working on fields which will be a big part. I wont be releasing until I get a version that works, currently some portions don't work with other portions and it will break if you don't know how to use it. I've also been talking to the QA guys about writing a similar extension for litmus and test day. <br />
*more work on ver 0.2. Integrated new Pref management system with rest of code. Fixed some bugs in Pref management system and its now at the point it was in ver 0.1 from a functional stand point. Next I'll be setting up the bug list options in the preference management system. I'll post a work in progress by the end of the weekend.<br />
*implemented new feature using new pref management system so remember current instance when buggy bar is closed or Firefox is shutdown. A small one but a good one, now I'll start on the new bugList options. Also fixed some bugs, end of weekend release still pending.<br />
*ok I was a bit late on this development release but here it is : [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi buggybar-dev-0.1.2.xpi]. This version has the newer preference system although still incomplete. This allows a user name and passwrd to be set for each instance as well as the buglist parameters to be set by instance. the preferences for this version can be found on the add-ons window and then click the options button for buggy bar. <br />
* fixed some little bugs after some questions from current users as well as changed the pref manager so that passwords are stored in the password manager. Also you can set up many of the same instances so you can have different accounts with different bug list settings. I'm also trying to figure out how those settings should be set for both search and buglist as most of the fields (ie: product, status, etc.) are instance specific so I may have to pull them from the xml file. Right now you have to manually create the url fields.<br />
*more progress with the xml file portions implemented, specific search almost done, bug access cleaned up some and some more fixes. Next I'm going to finish the specific search and the xml file portion and then I'll post a dev release. I'm hoping to have a full public release in the near future.<br />
*Had a sick day from school so I got some more done. This dev release is looking much better with the search working along with the removal of the old preference code and some other small additions such as being able to load each area (bug list, bug search, and bug details) into the main browser window. Next I'm going to finish the status and knob stuff which ties into the instance specific xml file. [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi buggybar-dev-0.1.3.xpi]<br />
*Finished bugzilla login and it works pretty well, just one last feature and its release time!<br />
*Finished bugzilla instance specific commit options XML parsing. This completes the the feature list for ver 0.2 and once I finish documenting and setting up the add-ons pages this version will be posted.<br />
* BuggyBar 0.2 Release! <br />
**supports login and storing of user name and passwords using the pref manager<br />
**completely redone preference manager which allows:<br />
***setting up multiple profiles for each instance each with user name, password and custom XML specs file<br />
***able to set the buglist url parameters used for each instance for customization<br />
***in its own window which is under buggybar options in the add-ons window<br />
**Instance spesific information can be set by creating new instance files in XML: [http://cs1.senecac.on.ca/~b6001a07/bugzilla_instance_Data-mozilla.xml example file]<br />
***you can set product list for search and status and know actions<br />
**Specific bug search is now available for fast finding of bugs<br />
**all areas can be transfered into main window at any time<br />
**instance selector is always availiable<br />
**download it [http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi here] and try it out!<br />
* ver 0.2.1 Modified bugAccess to be less picky about bugList syntax to support some other Bugzilla instances. Download ver 0.2 above for changes<br />
* ver [http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi 0.2.2] made some more small changes to bug list so it has actual columns and modified some back end code. Change log will be coming soon as I get a chance.<br />
* I have a cast on my foot for the next two weeks without much to do so I updated this to work on FF3<br />
**ver [http://cs1.senecac.on.ca/~b6001a07/buggybar-0.3.xpi 0.3] <br />
<br />
==Example XML Bugzilla Instance File==<br />
This file is the default bug instance file which is meant for the Mozilla instance. It can be used for reference when designing a new file for another instance. This file defines three main things. First the product list which is used by the specific search. Second the bug statuses and what statuses each one can be changed to. Finally it defines the "Knob" for each status which is the parameter used by Bugzilla to change these statuses. <br />
<br />
*This file can be downloaded [http://cs1.senecac.on.ca/~b6001a07/bugzilla_instance_Data-mozilla.xml here]<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
*small addition to version 0.1 just changed the XUL as part of a user request so that it would remain functional even at a smaller size. This was only done in this version because it doesn't affect the actual code and is essential for many users. 0.2 is on the way and I'm in the design phase with some draft diagrams already completed. <br />
**[http://cs1.senecac.on.ca/~b6001a07/buggybar0.1.1.xpi 0.1.1]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi 0.1.2]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi 0.1.3]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi 0.2] <br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-0.3.xpi 0.3] <br />
<br />
<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi buggybar 0.1]<br/><br />
31/01/2007 - [http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi buggybar 0.2]<br />
21/04/2008 - [http://cs1.senecac.on.ca/~b6001a07/buggybar-0.3.xpi buggybar 0.3]<br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*<s>control bug list search parameters</s><br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object (will not be done)<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*<s>incorporate user input</s><br />
*<s>code overhaul</s><br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*<s>allow setting buglist search parameters</s><br />
*<s>allow searches with full search parameters</s><br />
*<s>move preferences to own window</s><br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
==To Do 0.3(striked out means complete)==<br />
*<s>code conditional password management to support ff2 and ff3</s><br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Club_Moz&diff=10144Club Moz2007-02-09T01:23:26Z<p>Djhamp-g: /* Club Moz Promotional Booth */</p>
<hr />
<div>=Purpose=<br />
<b>To help students get involved in the Mozilla community through its future endeavors in development, testing, support and hacking</b><br />
<br />
This club is open to technical and also non-technical people. If you don't know anything about open source or Mozilla, don't worry, we're here to help you get involved and we promise a good time :)<br />
<br />
<br />
=Committee=<br />
'''President:''' [[User:Themystic|Tom Aratyn]] (mystic)<br />
<br />
'''Vice President:''' Tiago Moreira (Tiago)<br />
<br />
'''Financial Officer:''' [[User:Elichak|Liz Chak]] (elichak)<br />
<br />
'''Events Coordinator:''' [[User:Pcvitori|Philip Vitorino]] (philly)<br />
<br />
'''Promotions Coordinator:''' [[User:Vpmirand|Vanessa Miranda]] (vanessa)<br />
<br />
'''Faculty Advisor:''' [[User:David.humphrey|Dave Humphrey]] (dave or humph)<br />
<br />
<br />
'''Email:''' clubmoz@gmail.com<br />
<br />
=Announcements=<br />
==<b>Want to work on some cool stuff? There are some cool projects waiting for you..</b>==<br />
*<b>If you're interested in any of these projects, speak to [[User:elichak | Liz Chak]] about getting involved</b><br />
*QA Site for more QA details: http://wiki.mozilla.org/Mozilla_QA_Community<br />
<br />
<br />
*<b>Talkback Report Challenge 1</b><br />
**Check out this link for detail: http://wiki.mozilla.org/Mozilla_QA_Community:Talkback_Report_Challenge_1<br />
<br />
*<b>Data mining of Hendrix data for creating reports of user feedback</b><br />
**To better understand major issues being reported and converting them into new bugs or finding and updating existing ones<br />
<br />
*<b>Litmus Extension</b> <br />
**We wanted to have an extension that would be able to serve users testcases to try and allow them to submit results to http://litmus.mozilla.org. We could expand the feature set of the extension to do a lot of other cool things with Bugzilla and Website Reporter integration... so we need some ideas there. <br />
**If you're interested, you could collaborate with [[User:Djhamp-g | David Hamp-Gonsalves]] to work on this together.<br />
<br />
*<b>QMO Help</b><br />
**Help needed in getting QMO together. If anyone is interested in website design, php hacking, or general graphics work, we can use some help getting QMO into better shape.<br />
**Link here: http://wiki.mozilla.org/Mozilla_QA_Community#QMO_Design_.26_Planning<br />
<br />
*<b>We are getting ready to ship Firefox 2.0.0.2 and 1.5.0.10</b><br />
**If you're interested in testing, you can run test cases through http://litmus.mozilla.org.<br />
<br />
==<b>Test Days</b>==<br />
* For Calendar, 13:00 UTC on February 9th 2007 to 01:00 UTC on February 10th 2007. http://wiki.mozilla.org/Calendar:Current_QA_TestDay<br />
*For Firefox 1.510 & 2.002 RC1 builds,Friday, February 9, 2007, from 7am - 5pm PST. http://wiki.mozilla.org/Mozilla_QA_Community:Firefox_1510_2002_Community_Test_Day<br />
<br />
==Other==<br />
*<big><b>Super Fun Hack Days are moved to T3073</b></big><br />
<br />
<br />
*<big><b>Firefox 2 is offically released!!</b></big> - Oct 24 2006<br />
<br />
=Events=<br />
One of the most fun aspects of Club Moz is the fact that we run events (like Super Fun Hack Day)! Come by and get involved!<br />
<br />
Due to some unfortunate events we have had to develop a policy regarding our [[Club Moz:Events:Policy| event policy]]. By attending you accept the policy.<br />
<br />
For a complete list of upcoming Club Moz events, check out our [http://www.google.com/calendar/embed?src=clubmoz%40gmail.com calendar]!<br />
<br />
<br />
==Super Fun Hack Day==<br />
<br />
===Event Agenda===<br />
<br />
'''February 8 '''<br />
* Make sure your User Page is up under "People". This is a place for you to list the projects you're working on and your progress. Other people may use this as a point of reference to who you are. Feel free to take ownership of your user page and the projects you're working on. <br />
* [[Club_Moz#Want_to_work_on_some_cool_stuff.3F_There_are_some_cool_projects_waiting_for_you.. | Wanna work on some cool stuff? There are some projects waiting for you..]]<br />
<br />
<br />
'''February 1''' - Calendar Test Day. Details [http://wiki.mozilla.org/Calendar:Current_QA_TestDay Here]<br />
<br />
===Event Details===<br />
'''Super Fun Hack Day every Thursday'''<br />
*Open to all students no matter your technical background or level. <br />
*Bring your energy and interest and we will help turn that into new abilities and new friends.<br />
*Come by T3073 on the third floor of the TEL building. <br />
*Food and Drinks will be provided after the event. We expect to be starting at around 3:20 pm going until... :)<br />
<br />
<br />
===Super Fun Hack Day Stuff===<br />
* Proposed Flyer ([[User:elichak | Liz Chak]] (elichak) and [[User:moe|Mohammad Tirtashi]] (moe))<br />
<gallery><br />
Image:Flyer.jpg|Hack Day Flyer<br />
</gallery><br />
*[[Hack day Issues|Notes on Hack Day Issues]]<br />
*[http://elichak.wordpress.com/ elichak's log about Super Fun Hack Day]<br />
<br />
<br />
===Issues With Hack day===<br />
<br />
* [[ Hack_day_Issues]]<br />
<br />
==Club Moz planning meetings==<br />
*Open to members of the club - everyone's voice matters<br />
*Date/Time: TBA<br />
*Location: T2091 - Linux Club<br />
<br />
== Club Moz Promotional Booth ==<br />
Please feel free to alter this schedule to reflect the actual times you will be available for the booth. If you can't make it during these times, you may remove your name:<br />
<br />
*'''Monday: 11:40 - 1:30'''<br />
**Tom<br />
**Tiago<br />
**Mike O<br />
**Vanessa<br />
**Liz (11:40 - 12:40) <br />
*'''Tuesday: 1:30 - whenever'''<br />
**Vanessa<br />
**Mike O<br />
**Tom<br />
*'''Wednesday: 1:30 - whenever '''<br />
**Vanessa<br />
**Dave<br />
*'''Thursday: '''<br />
**'''9:50 - 11:40'''<br />
***Tiago<br />
**'''11:40 - 1:30'''<br />
***Mike O<br />
***Tom<br />
***Vanessa<br />
***Moe<br />
*'''Friday: 11:40 - 1:30'''<br />
**Tiago<br />
**Mike O<br />
**Tom<br />
<br />
===Meeting Minutes===<br />
<br />
* [[Club Moz:Meetings/November 9, 2006|November 9, 2006]]<br />
* [[Club Moz:Meetings/November 15, 2006|November 15, 2006]]<br />
* [[Club Moz:Meetings/November 22, 2006|November 22, 2006]]<br />
* [[Club Moz:Meetings/November 29, 2006|November 29, 2006]]<br />
* [[Club Moz:Meetings/January 9, 2006|January 9, 2006]]<br />
<br />
=News=<br />
*The Firefox2 party was a success. <br />
**Here are some [http://www.flickr.com/photos/moebt/sets/72157594346279843/ pictures].<br />
**More [http://www.flickr.com/photos/14311671@N00/ pictures]!<br />
<br />
*Club hangout on irc: irc://irc.mozilla.org/#clubmoz<br />
<br />
<br />
=Members=<br />
List of members still in progress<br />
<br />
Add your name here if you would like to be a member of Club Moz :)<br />
<br />
* [[User:dtolj|Dejan Tolj]] (dtolj)<br />
* [[User:Eldavey|Erin Davey]] (davey_girl)<br />
* [[User:Eor|Eva Or]] (eor)<br />
* [[User:jbmossop|Jeff Mossop]] (JBmossop)<br />
* [[User:Mdsouza|Mark D'Souza]] (mdsouza)<br />
* [[User:melz|Melissa Peh]] (melz)<br />
* [[User:mylau|Michael Lau]] (mylau)<br />
* [[User:moe|Mohammad Tirtashi]] (moe)<br />
* [[User:Paul|Paul Yanchun Gu]] (gpaul)<br />
* [[User:PStD|Paul St-Denis]] (pstdenis)<br />
* [[User:John64|John Ford]] (john64)<br />
* Tiago Moreira (Tiago)<br />
* Sid Kalra (crulshorukh)<br />
* [[User:djhamp-g| david hamp]] (inveigle)<br />
* [[User:jp| justin pacheco]] (jp)<br />
* [[User:robcee|Rob Campbell]], aka robcee, QA Engineer, Mozilla Corp.<br />
* [[User:Gavin|Gavin Sharp]]<br />
* [[User:Shaver|shaver]]<br />
* [[User:backinblakk|Lukas Blakk]] (lsblakk)<br />
* [[User:Saba Naqvi|Saba]] (snaqvi3)</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=10119Bug Triage Extension2007-02-08T17:51:00Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]][[Image:buggybar-plus.png | ]][[Image:buggybar-minus.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [https://addons.mozilla.org/firefox/4117/ Firefox add-ons page]. New design first draft completed. Received first suggestion questions.<br />
===5/01/2007===<br />
hit over 1000 downloads and got a mention on the mozillazine QA blog thanks to robcee: <br />
[http://weblogs.mozillazine.org/qa/archives/2007/01/buggy_bar_extension.html#comments weblogs.mozillazine.org/qa]<br />
===31/01/2007===<br />
Release 0.2 is out and about and will be on the add-ons site soon as user testing has been finished<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
*release 0.2<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
*completed user input phase and completed new paper design. now its back into the code. started by putting totalField in bugSpecs. more to come<br />
*rewrote preferences section into much nicer object. Now instances have their own login information as well as can read an XML file to determine the status options or can use the default mozilla one. Also moved options to its own section. Next I'll be working on fields which will be a big part. I wont be releasing until I get a version that works, currently some portions don't work with other portions and it will break if you don't know how to use it. I've also been talking to the QA guys about writing a similar extension for litmus and test day. <br />
*more work on ver 0.2. Integrated new Pref management system with rest of code. Fixed some bugs in Pref management system and its now at the point it was in ver 0.1 from a functional stand point. Next I'll be setting up the bug list options in the preference management system. I'll post a work in progress by the end of the weekend.<br />
*implemented new feature using new pref management system so remember current instance when buggy bar is closed or Firefox is shutdown. A small one but a good one, now I'll start on the new bugList options. Also fixed some bugs, end of weekend release still pending.<br />
*ok I was a bit late on this development release but here it is : [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi buggybar-dev-0.1.2.xpi]. This version has the newer preference system although still incomplete. This allows a user name and passwrd to be set for each instance as well as the buglist parameters to be set by instance. the preferences for this version can be found on the add-ons window and then click the options button for buggy bar. <br />
* fixed some little bugs after some questions from current users as well as changed the pref manager so that passwords are stored in the password manager. Also you can set up many of the same instances so you can have different accounts with different bug list settings. I'm also trying to figure out how those settings should be set for both search and buglist as most of the fields (ie: product, status, etc.) are instance specific so I may have to pull them from the xml file. Right now you have to manually create the url fields.<br />
*more progress with the xml file portions implemented, specific search almost done, bug access cleaned up some and some more fixes. Next I'm going to finish the specific search and the xml file portion and then I'll post a dev release. I'm hoping to have a full public release in the near future.<br />
*Had a sick day from school so I got some more done. This dev release is looking much better with the search working along with the removal of the old preference code and some other small additions such as being able to load each area (bug list, bug search, and bug details) into the main browser window. Next I'm going to finish the status and knob stuff which ties into the instance specific xml file. [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi buggybar-dev-0.1.3.xpi]<br />
*Finished bugzilla login and it works pretty well, just one last feature and its release time!<br />
*Finished bugzilla instance specific commit options XML parsing. This completes the the feature list for ver 0.2 and once I finish documenting and setting up the add-ons pages this version will be posted.<br />
* BuggyBar 0.2 Release! <br />
**supports login and storing of user name and passwords using the pref manager<br />
**completely redone preference manager which allows:<br />
***setting up multiple profiles for each instance each with user name, password and custom XML specs file<br />
***able to set the buglist url parameters used for each instance for customization<br />
***in its own window which is under buggybar options in the add-ons window<br />
**Instance spesific information can be set by creating new instance files in XML: [http://cs1.senecac.on.ca/~b6001a07/bugzilla_instance_Data-mozilla.xml example file]<br />
***you can set product list for search and status and know actions<br />
**Specific bug search is now available for fast finding of bugs<br />
**all areas can be transfered into main window at any time<br />
**instance selector is always availiable<br />
**download it [http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi here] and try it out!<br />
* ver 0.2.1 Modified bugAccess to be less picky about bugList syntax to support some other Bugzilla instances. Download ver 0.2 above for changes<br />
* ver [http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi 0.2.2] made some more small changes to bug list so it has actual columns and modified some back end code. Change log will be coming soon as I get a chance. <br />
<br />
==Example XML Bugzilla Instance File==<br />
This file is the default bug instance file which is meant for the Mozilla instance. It can be used for reference when designing a new file for another instance. This file defines three main things. First the product list which is used by the specific search. Second the bug statuses and what statuses each one can be changed to. Finally it defines the "Knob" for each status which is the parameter used by Bugzilla to change these statuses. <br />
<br />
*This file can be downloaded [http://cs1.senecac.on.ca/~b6001a07/bugzilla_instance_Data-mozilla.xml here]<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
*small addition to version 0.1 just changed the XUL as part of a user request so that it would remain functional even at a smaller size. This was only done in this version because it doesn't affect the actual code and is essential for many users. 0.2 is on the way and I'm in the design phase with some draft diagrams already completed. <br />
**[http://cs1.senecac.on.ca/~b6001a07/buggybar0.1.1.xpi 0.1.1]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi 0.1.2]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi 0.1.3]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi 0.2] <br />
<br />
<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi buggybar 0.1]<br/><br />
31/01/2007 - [http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi buggybar 0.2]<br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*<s>control bug list search parameters</s><br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object (will not be done)<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*<s>incorporate user input</s><br />
*<s>code overhaul</s><br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*<s>allow setting buglist search parameters</s><br />
*<s>allow searches with full search parameters</s><br />
*<s>move preferences to own window</s><br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=10056Bug Triage Extension2007-02-03T02:46:28Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]][[Image:buggybar-plus.png | ]][[Image:buggybar-minus.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [https://addons.mozilla.org/firefox/4117/ Firefox add-ons page]. New design first draft completed. Received first suggestion questions.<br />
===5/01/2007===<br />
hit over 1000 downloads and got a mention on the mozillazine QA blog thanks to robcee: <br />
[http://weblogs.mozillazine.org/qa/archives/2007/01/buggy_bar_extension.html#comments weblogs.mozillazine.org/qa]<br />
===31/01/2007===<br />
Release 0.2 is out and about and will be on the add-ons site soon as user testing has been finished<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
*release 0.2<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
*completed user input phase and completed new paper design. now its back into the code. started by putting totalField in bugSpecs. more to come<br />
*rewrote preferences section into much nicer object. Now instances have their own login information as well as can read an XML file to determine the status options or can use the default mozilla one. Also moved options to its own section. Next I'll be working on fields which will be a big part. I wont be releasing until I get a version that works, currently some portions don't work with other portions and it will break if you don't know how to use it. I've also been talking to the QA guys about writing a similar extension for litmus and test day. <br />
*more work on ver 0.2. Integrated new Pref management system with rest of code. Fixed some bugs in Pref management system and its now at the point it was in ver 0.1 from a functional stand point. Next I'll be setting up the bug list options in the preference management system. I'll post a work in progress by the end of the weekend.<br />
*implemented new feature using new pref management system so remember current instance when buggy bar is closed or Firefox is shutdown. A small one but a good one, now I'll start on the new bugList options. Also fixed some bugs, end of weekend release still pending.<br />
*ok I was a bit late on this development release but here it is : [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi buggybar-dev-0.1.2.xpi]. This version has the newer preference system although still incomplete. This allows a user name and passwrd to be set for each instance as well as the buglist parameters to be set by instance. the preferences for this version can be found on the add-ons window and then click the options button for buggy bar. <br />
* fixed some little bugs after some questions from current users as well as changed the pref manager so that passwords are stored in the password manager. Also you can set up many of the same instances so you can have different accounts with different bug list settings. I'm also trying to figure out how those settings should be set for both search and buglist as most of the fields (ie: product, status, etc.) are instance specific so I may have to pull them from the xml file. Right now you have to manually create the url fields.<br />
*more progress with the xml file portions implemented, specific search almost done, bug access cleaned up some and some more fixes. Next I'm going to finish the specific search and the xml file portion and then I'll post a dev release. I'm hoping to have a full public release in the near future.<br />
*Had a sick day from school so I got some more done. This dev release is looking much better with the search working along with the removal of the old preference code and some other small additions such as being able to load each area (bug list, bug search, and bug details) into the main browser window. Next I'm going to finish the status and knob stuff which ties into the instance specific xml file. [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi buggybar-dev-0.1.3.xpi]<br />
*Finished bugzilla login and it works pretty well, just one last feature and its release time!<br />
*Finished bugzilla instance specific commit options XML parsing. This completes the the feature list for ver 0.2 and once I finish documenting and setting up the add-ons pages this version will be posted.<br />
* BuggyBar 0.2 Release! <br />
**supports login and storing of user name and passwords using the pref manager<br />
**completely redone preference manager which allows:<br />
***setting up multiple profiles for each instance each with user name, password and custom XML specs file<br />
***able to set the buglist url parameters used for each instance for customization<br />
***in its own window which is under buggybar options in the add-ons window<br />
**Instance spesific information can be set by creating new instance files in XML: [http://cs1.senecac.on.ca/~b6001a07/bugzilla_instance_Data-mozilla.xml example file]<br />
***you can set product list for search and status and know actions<br />
**Specific bug search is now available for fast finding of bugs<br />
**all areas can be transfered into main window at any time<br />
**instance selector is always availiable<br />
**download it [http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi here] and try it out!<br />
*Modified bugAccess to be less picky about bugList syntax to support some other Bugzilla instances. Download ver 0.2 above for changes<br />
<br />
==Example XML Bugzilla Instance File==<br />
This file is the default bug instance file which is meant for the Mozilla instance. It can be used for reference when designing a new file for another instance. This file defines three main things. First the product list which is used by the specific search. Second the bug statuses and what statuses each one can be changed to. Finally it defines the "Knob" for each status which is the parameter used by Bugzilla to change these statuses. <br />
<br />
*This file can be downloaded [http://cs1.senecac.on.ca/~b6001a07/bugzilla_instance_Data-mozilla.xml here]<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
*small addition to version 0.1 just changed the XUL as part of a user request so that it would remain functional even at a smaller size. This was only done in this version because it doesn't affect the actual code and is essential for many users. 0.2 is on the way and I'm in the design phase with some draft diagrams already completed. <br />
**[http://cs1.senecac.on.ca/~b6001a07/buggybar0.1.1.xpi 0.1.1]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi 0.1.2]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi 0.1.3]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi 0.2] <br />
<br />
<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi buggybar 0.1]<br/><br />
31/01/2007 - [http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi buggybar 0.2]<br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*<s>control bug list search parameters</s><br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object (will not be done)<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*<s>incorporate user input</s><br />
*<s>code overhaul</s><br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*<s>allow setting buglist search parameters</s><br />
*<s>allow searches with full search parameters</s><br />
*<s>move preferences to own window</s><br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9983Bug Triage Extension2007-02-01T19:20:37Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]][[Image:buggybar-plus.png | ]][[Image:buggybar-minus.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [https://addons.mozilla.org/firefox/4117/ Firefox add-ons page]. New design first draft completed. Received first suggestion questions.<br />
===5/01/2007===<br />
hit over 1000 downloads and got a mention on the mozillazine QA blog thanks to robcee: <br />
[http://weblogs.mozillazine.org/qa/archives/2007/01/buggy_bar_extension.html#comments weblogs.mozillazine.org/qa]<br />
===31/01/2007===<br />
Release 0.2 is out and about and will be on the add-ons site soon as user testing has been finished<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
*release 0.2<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
*completed user input phase and completed new paper design. now its back into the code. started by putting totalField in bugSpecs. more to come<br />
*rewrote preferences section into much nicer object. Now instances have their own login information as well as can read an XML file to determine the status options or can use the default mozilla one. Also moved options to its own section. Next I'll be working on fields which will be a big part. I wont be releasing until I get a version that works, currently some portions don't work with other portions and it will break if you don't know how to use it. I've also been talking to the QA guys about writing a similar extension for litmus and test day. <br />
*more work on ver 0.2. Integrated new Pref management system with rest of code. Fixed some bugs in Pref management system and its now at the point it was in ver 0.1 from a functional stand point. Next I'll be setting up the bug list options in the preference management system. I'll post a work in progress by the end of the weekend.<br />
*implemented new feature using new pref management system so remember current instance when buggy bar is closed or Firefox is shutdown. A small one but a good one, now I'll start on the new bugList options. Also fixed some bugs, end of weekend release still pending.<br />
*ok I was a bit late on this development release but here it is : [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi buggybar-dev-0.1.2.xpi]. This version has the newer preference system although still incomplete. This allows a user name and passwrd to be set for each instance as well as the buglist parameters to be set by instance. the preferences for this version can be found on the add-ons window and then click the options button for buggy bar. <br />
* fixed some little bugs after some questions from current users as well as changed the pref manager so that passwords are stored in the password manager. Also you can set up many of the same instances so you can have different accounts with different bug list settings. I'm also trying to figure out how those settings should be set for both search and buglist as most of the fields (ie: product, status, etc.) are instance specific so I may have to pull them from the xml file. Right now you have to manually create the url fields.<br />
*more progress with the xml file portions implemented, specific search almost done, bug access cleaned up some and some more fixes. Next I'm going to finish the specific search and the xml file portion and then I'll post a dev release. I'm hoping to have a full public release in the near future.<br />
*Had a sick day from school so I got some more done. This dev release is looking much better with the search working along with the removal of the old preference code and some other small additions such as being able to load each area (bug list, bug search, and bug details) into the main browser window. Next I'm going to finish the status and knob stuff which ties into the instance specific xml file. [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi buggybar-dev-0.1.3.xpi]<br />
*Finished bugzilla login and it works pretty well, just one last feature and its release time!<br />
*Finished bugzilla instance specific commit options XML parsing. This completes the the feature list for ver 0.2 and once I finish documenting and setting up the add-ons pages this version will be posted.<br />
* BuggyBar 0.2 Release! <br />
**supports login and storing of user name and passwords using the pref manager<br />
**completely redone preference manager which allows:<br />
***setting up multiple profiles for each instance each with user name, password and custom XML specs file<br />
***able to set the buglist url parameters used for each instance for customization<br />
***in its own window which is under buggybar options in the add-ons window<br />
**Instance spesific information can be set by creating new instance files in XML: [http://cs1.senecac.on.ca/~b6001a07/bugzilla_instance_Data-mozilla.xml example file]<br />
***you can set product list for search and status and know actions<br />
**Specific bug search is now available for fast finding of bugs<br />
**all areas can be transfered into main window at any time<br />
**instance selector is always availiable<br />
**download it [http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi here] and try it out!<br />
<br />
<br />
==Example XML Bugzilla Instance File==<br />
This file is the default bug instance file which is meant for the Mozilla instance. It can be used for reference when designing a new file for another instance. This file defines three main things. First the product list which is used by the specific search. Second the bug statuses and what statuses each one can be changed to. Finally it defines the "Knob" for each status which is the parameter used by Bugzilla to change these statuses. <br />
<br />
*This file can be downloaded [http://cs1.senecac.on.ca/~b6001a07/bugzilla_instance_Data-mozilla.xml here]<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
*small addition to version 0.1 just changed the XUL as part of a user request so that it would remain functional even at a smaller size. This was only done in this version because it doesn't affect the actual code and is essential for many users. 0.2 is on the way and I'm in the design phase with some draft diagrams already completed. <br />
**[http://cs1.senecac.on.ca/~b6001a07/buggybar0.1.1.xpi 0.1.1]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi 0.1.2]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi 0.1.3]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi 0.2] <br />
<br />
<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi buggybar 0.1]<br/><br />
31/01/2007 - [http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi buggybar 0.2]<br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*<s>control bug list search parameters</s><br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object (will not be done)<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*<s>incorporate user input</s><br />
*<s>code overhaul</s><br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*<s>allow setting buglist search parameters</s><br />
*<s>allow searches with full search parameters</s><br />
*<s>move preferences to own window</s><br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9960Bug Triage Extension2007-01-31T14:57:51Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]][[Image:buggybar-plus.png | ]][[Image:buggybar-minus.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [https://addons.mozilla.org/firefox/4117/ Firefox add-ons page]. New design first draft completed. Received first suggestion questions.<br />
===5/01/2007===<br />
hit over 1000 downloads and got a mention on the mozillazine QA blog thanks to robcee: <br />
[http://weblogs.mozillazine.org/qa/archives/2007/01/buggy_bar_extension.html#comments weblogs.mozillazine.org/qa]<br />
===31/01/2007===<br />
Release 0.2 is out and about and will be on the add-ons site soon as user testing has been finished<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
*release 0.2<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
*completed user input phase and completed new paper design. now its back into the code. started by putting totalField in bugSpecs. more to come<br />
*rewrote preferences section into much nicer object. Now instances have their own login information as well as can read an XML file to determine the status options or can use the default mozilla one. Also moved options to its own section. Next I'll be working on fields which will be a big part. I wont be releasing until I get a version that works, currently some portions don't work with other portions and it will break if you don't know how to use it. I've also been talking to the QA guys about writing a similar extension for litmus and test day. <br />
*more work on ver 0.2. Integrated new Pref management system with rest of code. Fixed some bugs in Pref management system and its now at the point it was in ver 0.1 from a functional stand point. Next I'll be setting up the bug list options in the preference management system. I'll post a work in progress by the end of the weekend.<br />
*implemented new feature using new pref management system so remember current instance when buggy bar is closed or Firefox is shutdown. A small one but a good one, now I'll start on the new bugList options. Also fixed some bugs, end of weekend release still pending.<br />
*ok I was a bit late on this development release but here it is : [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi buggybar-dev-0.1.2.xpi]. This version has the newer preference system although still incomplete. This allows a user name and passwrd to be set for each instance as well as the buglist parameters to be set by instance. the preferences for this version can be found on the add-ons window and then click the options button for buggy bar. <br />
* fixed some little bugs after some questions from current users as well as changed the pref manager so that passwords are stored in the password manager. Also you can set up many of the same instances so you can have different accounts with different bug list settings. I'm also trying to figure out how those settings should be set for both search and buglist as most of the fields (ie: product, status, etc.) are instance specific so I may have to pull them from the xml file. Right now you have to manually create the url fields.<br />
*more progress with the xml file portions implemented, specific search almost done, bug access cleaned up some and some more fixes. Next I'm going to finish the specific search and the xml file portion and then I'll post a dev release. I'm hoping to have a full public release in the near future.<br />
*Had a sick day from school so I got some more done. This dev release is looking much better with the search working along with the removal of the old preference code and some other small additions such as being able to load each area (bug list, bug search, and bug details) into the main browser window. Next I'm going to finish the status and knob stuff which ties into the instance specific xml file. [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi buggybar-dev-0.1.3.xpi]<br />
*Finished bugzilla login and it works pretty well, just one last feature and its release time!<br />
*Finished bugzilla instance specific commit options XML parsing. This completes the the feature list for ver 0.2 and once I finish documenting and setting up the add-ons pages this version will be posted.<br />
* BuggyBar 0.2 Release! <br />
**supports login and storing of user name and passwords using the pref manager<br />
**completely redone preference manager which allows:<br />
***setting up multiple profiles for each instance each with user name, password and custom XML specs file<br />
***able to set the buglist url parameters used for each instance for customization<br />
***in its own window which is under buggybar options in the add-ons window<br />
**Instance spesific information can be set by creating new instance files in XML: [http://cs1.senecac.on.ca/~b6001a07/bugzilla_instance_Data-mozilla.xml example file]<br />
***you can set product list for search and status and know actions<br />
**Specific bug search is now available for fast finding of bugs<br />
**all areas can be transfered into main window at any time<br />
**instance selector is always availiable<br />
**download it [http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi here] and try it out!<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
*small addition to version 0.1 just changed the XUL as part of a user request so that it would remain functional even at a smaller size. This was only done in this version because it doesn't affect the actual code and is essential for many users. 0.2 is on the way and I'm in the design phase with some draft diagrams already completed. <br />
**[http://cs1.senecac.on.ca/~b6001a07/buggybar0.1.1.xpi 0.1.1]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi 0.1.2]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi 0.1.3]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi 0.2] <br />
<br />
<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi buggybar 0.1]<br/><br />
31/01/2007 - [http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi buggybar 0.2]<br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*<s>control bug list search parameters</s><br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object (will not be done)<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*<s>incorporate user input</s><br />
*<s>code overhaul</s><br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*<s>allow setting buglist search parameters</s><br />
*<s>allow searches with full search parameters</s><br />
*<s>move preferences to own window</s><br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9959Bug Triage Extension2007-01-31T14:47:32Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]][[Image:buggybar-plus.png | ]][[Image:buggybar-minus.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [https://addons.mozilla.org/firefox/4117/ Firefox add-ons page]. New design first draft completed. Received first suggestion questions.<br />
===5/01/2007===<br />
hit over 1000 downloads and got a mention on the mozillazine QA blog thanks to robcee: <br />
[http://weblogs.mozillazine.org/qa/archives/2007/01/buggy_bar_extension.html#comments weblogs.mozillazine.org/qa]<br />
===31/01/2007===<br />
Release 0.2 is out and about and will be on the add-ons site soon as user testing has been finished<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
*release 0.2<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
*completed user input phase and completed new paper design. now its back into the code. started by putting totalField in bugSpecs. more to come<br />
*rewrote preferences section into much nicer object. Now instances have their own login information as well as can read an XML file to determine the status options or can use the default mozilla one. Also moved options to its own section. Next I'll be working on fields which will be a big part. I wont be releasing until I get a version that works, currently some portions don't work with other portions and it will break if you don't know how to use it. I've also been talking to the QA guys about writing a similar extension for litmus and test day. <br />
*more work on ver 0.2. Integrated new Pref management system with rest of code. Fixed some bugs in Pref management system and its now at the point it was in ver 0.1 from a functional stand point. Next I'll be setting up the bug list options in the preference management system. I'll post a work in progress by the end of the weekend.<br />
*implemented new feature using new pref management system so remember current instance when buggy bar is closed or Firefox is shutdown. A small one but a good one, now I'll start on the new bugList options. Also fixed some bugs, end of weekend release still pending.<br />
*ok I was a bit late on this development release but here it is : [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi buggybar-dev-0.1.2.xpi]. This version has the newer preference system although still incomplete. This allows a user name and passwrd to be set for each instance as well as the buglist parameters to be set by instance. the preferences for this version can be found on the add-ons window and then click the options button for buggy bar. <br />
* fixed some little bugs after some questions from current users as well as changed the pref manager so that passwords are stored in the password manager. Also you can set up many of the same instances so you can have different accounts with different bug list settings. I'm also trying to figure out how those settings should be set for both search and buglist as most of the fields (ie: product, status, etc.) are instance specific so I may have to pull them from the xml file. Right now you have to manually create the url fields.<br />
*more progress with the xml file portions implemented, specific search almost done, bug access cleaned up some and some more fixes. Next I'm going to finish the specific search and the xml file portion and then I'll post a dev release. I'm hoping to have a full public release in the near future.<br />
*Had a sick day from school so I got some more done. This dev release is looking much better with the search working along with the removal of the old preference code and some other small additions such as being able to load each area (bug list, bug search, and bug details) into the main browser window. Next I'm going to finish the status and knob stuff which ties into the instance specific xml file. [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi buggybar-dev-0.1.3.xpi]<br />
*Finished bugzilla login and it works pretty well, just one last feature and its release time!<br />
*Finished bugzilla instance specific commit options XML parsing. This completes the the feature list for ver 0.2 and once I finish documenting and setting up the add-ons pages this version will be posted.<br />
* BuggyBar 0.2 Release! <br />
**supports login and storing of user name and passwords using the pref manager<br />
**completely redone preference manager which allows:<br />
***setting up multiple profiles for each instance each with user name, password and custom XML specs file<br />
***able to set the buglist url parameters used for each instance for customization<br />
***in its own window which is under buggybar options in the add-ons window<br />
**Instance spesific information can be set by creating new instance files in XML<br />
***you can set product list for search and status and know actions<br />
**Specific bug search is now available for fast finding of bugs<br />
**all areas can be transfered into main window at any time<br />
**instance selector is always availiable<br />
**download it [http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi here] and try it out!<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
*small addition to version 0.1 just changed the XUL as part of a user request so that it would remain functional even at a smaller size. This was only done in this version because it doesn't affect the actual code and is essential for many users. 0.2 is on the way and I'm in the design phase with some draft diagrams already completed. <br />
**[http://cs1.senecac.on.ca/~b6001a07/buggybar0.1.1.xpi 0.1.1]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi 0.1.2]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi 0.1.3]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi 0.2] <br />
<br />
<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi buggybar 0.1]<br/><br />
31/01/2007 - [http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi buggybar 0.2]<br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*<s>control bug list search parameters</s><br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object (will not be done)<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*<s>incorporate user input</s><br />
*<s>code overhaul</s><br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*<s>allow setting buglist search parameters</s><br />
*<s>allow searches with full search parameters</s><br />
*<s>move preferences to own window</s><br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9958Bug Triage Extension2007-01-31T14:46:29Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]][[Image:buggybar-plus.png | ]][[Image:buggybar-minus.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [https://addons.mozilla.org/firefox/4117/ Firefox add-ons page]. New design first draft completed. Received first suggestion questions.<br />
===5/01/2007===<br />
hit over 1000 downloads and got a mention on the mozillazine QA blog thanks to robcee: <br />
[http://weblogs.mozillazine.org/qa/archives/2007/01/buggy_bar_extension.html#comments weblogs.mozillazine.org/qa]<br />
===31/01/2007===<br />
Release 0.2 is out and about and will be on the add-ons site soon as user testing has been finished<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
*release 0.2<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
*completed user input phase and completed new paper design. now its back into the code. started by putting totalField in bugSpecs. more to come<br />
*rewrote preferences section into much nicer object. Now instances have their own login information as well as can read an XML file to determine the status options or can use the default mozilla one. Also moved options to its own section. Next I'll be working on fields which will be a big part. I wont be releasing until I get a version that works, currently some portions don't work with other portions and it will break if you don't know how to use it. I've also been talking to the QA guys about writing a similar extension for litmus and test day. <br />
*more work on ver 0.2. Integrated new Pref management system with rest of code. Fixed some bugs in Pref management system and its now at the point it was in ver 0.1 from a functional stand point. Next I'll be setting up the bug list options in the preference management system. I'll post a work in progress by the end of the weekend.<br />
*implemented new feature using new pref management system so remember current instance when buggy bar is closed or Firefox is shutdown. A small one but a good one, now I'll start on the new bugList options. Also fixed some bugs, end of weekend release still pending.<br />
*ok I was a bit late on this development release but here it is : [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi buggybar-dev-0.1.2.xpi]. This version has the newer preference system although still incomplete. This allows a user name and passwrd to be set for each instance as well as the buglist parameters to be set by instance. the preferences for this version can be found on the add-ons window and then click the options button for buggy bar. <br />
* fixed some little bugs after some questions from current users as well as changed the pref manager so that passwords are stored in the password manager. Also you can set up many of the same instances so you can have different accounts with different bug list settings. I'm also trying to figure out how those settings should be set for both search and buglist as most of the fields (ie: product, status, etc.) are instance specific so I may have to pull them from the xml file. Right now you have to manually create the url fields.<br />
*more progress with the xml file portions implemented, specific search almost done, bug access cleaned up some and some more fixes. Next I'm going to finish the specific search and the xml file portion and then I'll post a dev release. I'm hoping to have a full public release in the near future.<br />
*Had a sick day from school so I got some more done. This dev release is looking much better with the search working along with the removal of the old preference code and some other small additions such as being able to load each area (bug list, bug search, and bug details) into the main browser window. Next I'm going to finish the status and knob stuff which ties into the instance specific xml file. [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi buggybar-dev-0.1.3.xpi]<br />
*Finished bugzilla login and it works pretty well, just one last feature and its release time!<br />
*Finished bugzilla instance specific commit options XML parsing. This completes the the feature list for ver 0.2 and once I finish documenting and setting up the add-ons pages this version will be posted.<br />
* BuggyBar 0.2 Release! <br />
**supports login and storing of user name and passwords using the pref manager<br />
**completely redone preference manager which allows:<br />
***setting up multiple profiles for each instance each with user name, password and custom XML specs file<br />
***able to set the buglist url parameters used for each instance for customization<br />
***in its own window which is under buggybar options in the add-ons window<br />
**Instance spesific information can be set by creating new instance files in XML<br />
***you can set product list for search and status and know actions<br />
**Specific bug search is now available for fast finding of bugs<br />
**all areas can be transfered into main window at any time<br />
**instance selector is always availiable<br />
**download it and try it out [http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi here]<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
*small addition to version 0.1 just changed the XUL as part of a user request so that it would remain functional even at a smaller size. This was only done in this version because it doesn't affect the actual code and is essential for many users. 0.2 is on the way and I'm in the design phase with some draft diagrams already completed. <br />
**[http://cs1.senecac.on.ca/~b6001a07/buggybar0.1.1.xpi 0.1.1]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi 0.1.2]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi 0.1.3]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi 0.2] <br />
<br />
<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi buggybar 0.1]<br/><br />
31/01/2007 - [http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi buggybar 0.2]<br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*<s>control bug list search parameters</s><br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object (will not be done)<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*<s>incorporate user input</s><br />
*<s>code overhaul</s><br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*<s>allow setting buglist search parameters</s><br />
*<s>allow searches with full search parameters</s><br />
*<s>move preferences to own window</s><br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9957Bug Triage Extension2007-01-31T14:44:37Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]][[Image:buggybar-plus.png | ]][[Image:buggybar-minus.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [https://addons.mozilla.org/firefox/4117/ Firefox add-ons page]. New design first draft completed. Received first suggestion questions.<br />
===5/01/2007===<br />
hit over 1000 downloads and got a mention on the mozillazine QA blog thanks to robcee: <br />
[http://weblogs.mozillazine.org/qa/archives/2007/01/buggy_bar_extension.html#comments weblogs.mozillazine.org/qa]<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
*completed user input phase and completed new paper design. now its back into the code. started by putting totalField in bugSpecs. more to come<br />
*rewrote preferences section into much nicer object. Now instances have their own login information as well as can read an XML file to determine the status options or can use the default mozilla one. Also moved options to its own section. Next I'll be working on fields which will be a big part. I wont be releasing until I get a version that works, currently some portions don't work with other portions and it will break if you don't know how to use it. I've also been talking to the QA guys about writing a similar extension for litmus and test day. <br />
*more work on ver 0.2. Integrated new Pref management system with rest of code. Fixed some bugs in Pref management system and its now at the point it was in ver 0.1 from a functional stand point. Next I'll be setting up the bug list options in the preference management system. I'll post a work in progress by the end of the weekend.<br />
*implemented new feature using new pref management system so remember current instance when buggy bar is closed or Firefox is shutdown. A small one but a good one, now I'll start on the new bugList options. Also fixed some bugs, end of weekend release still pending.<br />
*ok I was a bit late on this development release but here it is : [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi buggybar-dev-0.1.2.xpi]. This version has the newer preference system although still incomplete. This allows a user name and passwrd to be set for each instance as well as the buglist parameters to be set by instance. the preferences for this version can be found on the add-ons window and then click the options button for buggy bar. <br />
* fixed some little bugs after some questions from current users as well as changed the pref manager so that passwords are stored in the password manager. Also you can set up many of the same instances so you can have different accounts with different bug list settings. I'm also trying to figure out how those settings should be set for both search and buglist as most of the fields (ie: product, status, etc.) are instance specific so I may have to pull them from the xml file. Right now you have to manually create the url fields.<br />
*more progress with the xml file portions implemented, specific search almost done, bug access cleaned up some and some more fixes. Next I'm going to finish the specific search and the xml file portion and then I'll post a dev release. I'm hoping to have a full public release in the near future.<br />
*Had a sick day from school so I got some more done. This dev release is looking much better with the search working along with the removal of the old preference code and some other small additions such as being able to load each area (bug list, bug search, and bug details) into the main browser window. Next I'm going to finish the status and knob stuff which ties into the instance specific xml file. [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi buggybar-dev-0.1.3.xpi]<br />
*Finished bugzilla login and it works pretty well, just one last feature and its release time!<br />
*Finished bugzilla instance specific commit options XML parsing. This completes the the feature list for ver 0.2 and once I finish documenting and setting up the add-ons pages this version will be posted.<br />
* BuggyBar 0.2 Release! <br />
**supports login and storing of user name and passwords using the pref manager<br />
**completely redone preference manager which allows:<br />
***setting up multiple profiles for each instance each with user name, password and custom XML specs file<br />
***able to set the buglist url parameters used for each instance for customization<br />
***in its own window which is under buggybar options in the add-ons window<br />
**Instance spesific information can be set by creating new instance files in XML<br />
***you can set product list for search and status and know actions<br />
**Specific bug search is now available for fast finding of bugs<br />
**all areas can be transfered into main window at any time<br />
**instance selector is always availiable<br />
**download it and try it out [http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi here]<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
*small addition to version 0.1 just changed the XUL as part of a user request so that it would remain functional even at a smaller size. This was only done in this version because it doesn't affect the actual code and is essential for many users. 0.2 is on the way and I'm in the design phase with some draft diagrams already completed. <br />
**[http://cs1.senecac.on.ca/~b6001a07/buggybar0.1.1.xpi 0.1.1]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi 0.1.2]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi 0.1.3]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi 0.2] <br />
<br />
<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi buggybar 0.1]<br />
31/01/2007 - [http://cs1.senecac.on.ca/~b6001a07/buggybar-0.2.xpi buggybar 0.2]<br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*<s>control bug list search parameters</s><br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object (will not be done)<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*<s>incorporate user input</s><br />
*<s>code overhaul</s><br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*<s>allow setting buglist search parameters</s><br />
*<s>allow searches with full search parameters</s><br />
*<s>move preferences to own window</s><br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9951Bug Triage Extension2007-01-30T04:45:03Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]][[Image:buggybar-plus.png | ]][[Image:buggybar-minus.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [https://addons.mozilla.org/firefox/4117/ Firefox add-ons page]. New design first draft completed. Received first suggestion questions.<br />
===5/01/2007===<br />
hit over 1000 downloads and got a mention on the mozillazine QA blog thanks to robcee: <br />
[http://weblogs.mozillazine.org/qa/archives/2007/01/buggy_bar_extension.html#comments weblogs.mozillazine.org/qa]<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
*completed user input phase and completed new paper design. now its back into the code. started by putting totalField in bugSpecs. more to come<br />
*rewrote preferences section into much nicer object. Now instances have their own login information as well as can read an XML file to determine the status options or can use the default mozilla one. Also moved options to its own section. Next I'll be working on fields which will be a big part. I wont be releasing until I get a version that works, currently some portions don't work with other portions and it will break if you don't know how to use it. I've also been talking to the QA guys about writing a similar extension for litmus and test day. <br />
*more work on ver 0.2. Integrated new Pref management system with rest of code. Fixed some bugs in Pref management system and its now at the point it was in ver 0.1 from a functional stand point. Next I'll be setting up the bug list options in the preference management system. I'll post a work in progress by the end of the weekend.<br />
*implemented new feature using new pref management system so remember current instance when buggy bar is closed or Firefox is shutdown. A small one but a good one, now I'll start on the new bugList options. Also fixed some bugs, end of weekend release still pending.<br />
*ok I was a bit late on this development release but here it is : [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi buggybar-dev-0.1.2.xpi]. This version has the newer preference system although still incomplete. This allows a user name and passwrd to be set for each instance as well as the buglist parameters to be set by instance. the preferences for this version can be found on the add-ons window and then click the options button for buggy bar. <br />
* fixed some little bugs after some questions from current users as well as changed the pref manager so that passwords are stored in the password manager. Also you can set up many of the same instances so you can have different accounts with different bug list settings. I'm also trying to figure out how those settings should be set for both search and buglist as most of the fields (ie: product, status, etc.) are instance specific so I may have to pull them from the xml file. Right now you have to manually create the url fields.<br />
*more progress with the xml file portions implemented, specific search almost done, bug access cleaned up some and some more fixes. Next I'm going to finish the specific search and the xml file portion and then I'll post a dev release. I'm hoping to have a full public release in the near future.<br />
*Had a sick day from school so I got some more done. This dev release is looking much better with the search working along with the removal of the old preference code and some other small additions such as being able to load each area (bug list, bug search, and bug details) into the main browser window. Next I'm going to finish the status and knob stuff which ties into the instance specific xml file. [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi buggybar-dev-0.1.3.xpi]<br />
*Finished bugzilla login and it works pretty well, just one last feature and its release time!<br />
*Finished bugzilla instance specific commit options XML parsing. This completes the the feature list for ver 0.2 and once I finish documenting and setting up the add-ons pages this version will be posted.<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
*small addition to version 0.1 just changed the XUL as part of a user request so that it would remain functional even at a smaller size. This was only done in this version because it doesn't affect the actual code and is essential for many users. 0.2 is on the way and I'm in the design phase with some draft diagrams already completed. <br />
**[http://cs1.senecac.on.ca/~b6001a07/buggybar0.1.1.xpi 0.1.1]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi 0.1.2]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi 0.1.3]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1]<br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*<s>control bug list search parameters</s><br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object (will not be done)<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*<s>incorporate user input</s><br />
*<s>code overhaul</s><br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*<s>allow setting buglist search parameters</s><br />
*<s>allow searches with full search parameters</s><br />
*<s>move preferences to own window</s><br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9945Bug Triage Extension2007-01-29T18:35:39Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]][[Image:buggybar-plus.png | ]][[Image:buggybar-minus.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [https://addons.mozilla.org/firefox/4117/ Firefox add-ons page]. New design first draft completed. Received first suggestion questions.<br />
===5/01/2007===<br />
hit over 1000 downloads and got a mention on the mozillazine QA blog thanks to robcee: <br />
[http://weblogs.mozillazine.org/qa/archives/2007/01/buggy_bar_extension.html#comments weblogs.mozillazine.org/qa]<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
*completed user input phase and completed new paper design. now its back into the code. started by putting totalField in bugSpecs. more to come<br />
*rewrote preferences section into much nicer object. Now instances have their own login information as well as can read an XML file to determine the status options or can use the default mozilla one. Also moved options to its own section. Next I'll be working on fields which will be a big part. I wont be releasing until I get a version that works, currently some portions don't work with other portions and it will break if you don't know how to use it. I've also been talking to the QA guys about writing a similar extension for litmus and test day. <br />
*more work on ver 0.2. Integrated new Pref management system with rest of code. Fixed some bugs in Pref management system and its now at the point it was in ver 0.1 from a functional stand point. Next I'll be setting up the bug list options in the preference management system. I'll post a work in progress by the end of the weekend.<br />
*implemented new feature using new pref management system so remember current instance when buggy bar is closed or Firefox is shutdown. A small one but a good one, now I'll start on the new bugList options. Also fixed some bugs, end of weekend release still pending.<br />
*ok I was a bit late on this development release but here it is : [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi buggybar-dev-0.1.2.xpi]. This version has the newer preference system although still incomplete. This allows a user name and passwrd to be set for each instance as well as the buglist parameters to be set by instance. the preferences for this version can be found on the add-ons window and then click the options button for buggy bar. <br />
* fixed some little bugs after some questions from current users as well as changed the pref manager so that passwords are stored in the password manager. Also you can set up many of the same instances so you can have different accounts with different bug list settings. I'm also trying to figure out how those settings should be set for both search and buglist as most of the fields (ie: product, status, etc.) are instance specific so I may have to pull them from the xml file. Right now you have to manually create the url fields.<br />
*more progress with the xml file portions implemented, specific search almost done, bug access cleaned up some and some more fixes. Next I'm going to finish the specific search and the xml file portion and then I'll post a dev release. I'm hoping to have a full public release in the near future.<br />
*Had a sick day from school so I got some more done. This dev release is looking much better with the search working along with the removal of the old preference code and some other small additions such as being able to load each area (bug list, bug search, and bug details) into the main browser window. Next I'm going to finish the status and knob stuff which ties into the instance specific xml file. [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi buggybar-dev-0.1.3.xpi]<br />
*Finished bugzilla login and it works pretty well, just one last feature and its release time! <br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
*small addition to version 0.1 just changed the XUL as part of a user request so that it would remain functional even at a smaller size. This was only done in this version because it doesn't affect the actual code and is essential for many users. 0.2 is on the way and I'm in the design phase with some draft diagrams already completed. <br />
**[http://cs1.senecac.on.ca/~b6001a07/buggybar0.1.1.xpi 0.1.1]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi 0.1.2]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi 0.1.3]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1]<br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*<s>control bug list search parameters</s><br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object (will not be done)<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*<s>incorporate user input</s><br />
*<s>code overhaul</s><br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*<s>allow setting buglist search parameters</s><br />
*<s>allow searches with full search parameters</s><br />
*<s>move preferences to own window</s><br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9862Bug Triage Extension2007-01-24T03:04:45Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]][[Image:buggybar-plus.png | ]][[Image:buggybar-minus.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [https://addons.mozilla.org/firefox/4117/ Firefox add-ons page]. New design first draft completed. Received first suggestion questions.<br />
===5/01/2007===<br />
hit over 1000 downloads and got a mention on the mozillazine QA blog thanks to robcee: <br />
[http://weblogs.mozillazine.org/qa/archives/2007/01/buggy_bar_extension.html#comments weblogs.mozillazine.org/qa]<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
*completed user input phase and completed new paper design. now its back into the code. started by putting totalField in bugSpecs. more to come<br />
*rewrote preferences section into much nicer object. Now instances have their own login information as well as can read an XML file to determine the status options or can use the default mozilla one. Also moved options to its own section. Next I'll be working on fields which will be a big part. I wont be releasing until I get a version that works, currently some portions don't work with other portions and it will break if you don't know how to use it. I've also been talking to the QA guys about writing a similar extension for litmus and test day. <br />
*more work on ver 0.2. Integrated new Pref management system with rest of code. Fixed some bugs in Pref management system and its now at the point it was in ver 0.1 from a functional stand point. Next I'll be setting up the bug list options in the preference management system. I'll post a work in progress by the end of the weekend.<br />
*implemented new feature using new pref management system so remember current instance when buggy bar is closed or Firefox is shutdown. A small one but a good one, now I'll start on the new bugList options. Also fixed some bugs, end of weekend release still pending.<br />
*ok I was a bit late on this development release but here it is : [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi buggybar-dev-0.1.2.xpi]. This version has the newer preference system although still incomplete. This allows a user name and passwrd to be set for each instance as well as the buglist parameters to be set by instance. the preferences for this version can be found on the add-ons window and then click the options button for buggy bar. <br />
* fixed some little bugs after some questions from current users as well as changed the pref manager so that passwords are stored in the password manager. Also you can set up many of the same instances so you can have different accounts with different bug list settings. I'm also trying to figure out how those settings should be set for both search and buglist as most of the fields (ie: product, status, etc.) are instance specific so I may have to pull them from the xml file. Right now you have to manually create the url fields.<br />
*more progress with the xml file portions implemented, specific search almost done, bug access cleaned up some and some more fixes. Next I'm going to finish the specific search and the xml file portion and then I'll post a dev release. I'm hoping to have a full public release in the near future.<br />
*Had a sick day from school so I got some more done. This dev release is looking much better with the search working along with the removal of the old preference code and some other small additions such as being able to load each area (bug list, bug search, and bug details) into the main browser window. Next I'm going to finish the status and knob stuff which ties into the instance specific xml file. [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi buggybar-dev-0.1.3.xpi]<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
*small addition to version 0.1 just changed the XUL as part of a user request so that it would remain functional even at a smaller size. This was only done in this version because it doesn't affect the actual code and is essential for many users. 0.2 is on the way and I'm in the design phase with some draft diagrams already completed. <br />
**[http://cs1.senecac.on.ca/~b6001a07/buggybar0.1.1.xpi 0.1.1]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi 0.1.2]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi 0.1.3]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1]<br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*<s>control bug list search parameters</s><br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object (will not be done)<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*<s>incorporate user input</s><br />
*<s>code overhaul</s><br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*<s>allow setting buglist search parameters</s><br />
*<s>allow searches with full search parameters</s><br />
*<s>move preferences to own window</s><br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9859Bug Triage Extension2007-01-23T21:08:47Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]][[Image:buggybar-plus.png | ]][[Image:buggybar-minus.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [https://addons.mozilla.org/firefox/4117/ Firefox add-ons page]. New design first draft completed. Received first suggestion questions.<br />
===5/01/2007===<br />
hit over 1000 downloads and got a mention on the mozillazine QA blog thanks to robcee: <br />
[http://weblogs.mozillazine.org/qa/archives/2007/01/buggy_bar_extension.html#comments weblogs.mozillazine.org/qa]<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
*completed user input phase and completed new paper design. now its back into the code. started by putting totalField in bugSpecs. more to come<br />
*rewrote preferences section into much nicer object. Now instances have their own login information as well as can read an XML file to determine the status options or can use the default mozilla one. Also moved options to its own section. Next I'll be working on fields which will be a big part. I wont be releasing until I get a version that works, currently some portions don't work with other portions and it will break if you don't know how to use it. I've also been talking to the QA guys about writing a similar extension for litmus and test day. <br />
*more work on ver 0.2. Integrated new Pref management system with rest of code. Fixed some bugs in Pref management system and its now at the point it was in ver 0.1 from a functional stand point. Next I'll be setting up the bug list options in the preference management system. I'll post a work in progress by the end of the weekend.<br />
*implemented new feature using new pref management system so remember current instance when buggy bar is closed or Firefox is shutdown. A small one but a good one, now I'll start on the new bugList options. Also fixed some bugs, end of weekend release still pending.<br />
*ok I was a bit late on this development release but here it is : [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi buggybar-dev-0.1.2.xpi]. This version has the newer preference system although still incomplete. This allows a user name and passwrd to be set for each instance as well as the buglist parameters to be set by instance. the preferences for this version can be found on the add-ons window and then click the options button for buggy bar. <br />
* fixed some little bugs after some questions from current users as well as changed the pref manager so that passwords are stored in the password manager. Also you can set up many of the same instances so you can have different accounts with different bug list settings. I'm also trying to figure out how those settings should be set for both search and buglist as most of the fields (ie: product, status, etc.) are instance specific so I may have to pull them from the xml file. Right now you have to manually create the url fields.<br />
*more progress with the xml file portions implemented, specific search almost done, bug access cleaned up some and some more fixes. Next I'm going to finish the specific search and the xml file portion and then I'll post a dev release. I'm hoping to have a full public release in the near future.<br />
*Had a sick day from school so I got some more done. This dev release is looking much better with the search working along with the removal of the old preference code and some other small additions such as being able to load each area (bug list, bug search, and bug details) into the main browser window. Next I'm going to finish the status and knob stuff which ties into the instance specific xml file. [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi buggybar-dev-0.1.3.xpi]<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
*small addition to version 0.1 just changed the XUL as part of a user request so that it would remain functional even at a smaller size. This was only done in this version because it doesn't affect the actual code and is essential for many users. 0.2 is on the way and I'm in the design phase with some draft diagrams already completed. <br />
**[http://cs1.senecac.on.ca/~b6001a07/buggybar0.1.1.xpi 0.1.1]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi 0.1.2]<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.3.xpi 0.1.3]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1]<br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*<s>control bug list search parameters</s><br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object (will not be done)<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*incorporate user input<br />
*code overhaul<br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*allow setting buglist search parameters<br />
*allow searches with full search parameters<br />
*move preferences to own window<br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9857Bug Triage Extension2007-01-23T03:01:15Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]][[Image:buggybar-plus.png | ]][[Image:buggybar-minus.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [https://addons.mozilla.org/firefox/4117/ Firefox add-ons page]. New design first draft completed. Received first suggestion questions.<br />
===5/01/2007===<br />
hit over 1000 downloads and got a mention on the mozillazine QA blog thanks to robcee: <br />
[http://weblogs.mozillazine.org/qa/archives/2007/01/buggy_bar_extension.html#comments weblogs.mozillazine.org/qa]<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
*completed user input phase and completed new paper design. now its back into the code. started by putting totalField in bugSpecs. more to come<br />
*rewrote preferences section into much nicer object. Now instances have their own login information as well as can read an XML file to determine the status options or can use the default mozilla one. Also moved options to its own section. Next I'll be working on fields which will be a big part. I wont be releasing until I get a version that works, currently some portions don't work with other portions and it will break if you don't know how to use it. I've also been talking to the QA guys about writing a similar extension for litmus and test day. <br />
*more work on ver 0.2. Integrated new Pref management system with rest of code. Fixed some bugs in Pref management system and its now at the point it was in ver 0.1 from a functional stand point. Next I'll be setting up the bug list options in the preference management system. I'll post a work in progress by the end of the weekend.<br />
*implemented new feature using new pref management system so remember current instance when buggy bar is closed or Firefox is shutdown. A small one but a good one, now I'll start on the new bugList options. Also fixed some bugs, end of weekend release still pending.<br />
*ok I was a bit late on this development release but here it is : [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi buggybar-dev-0.1.2.xpi]. This version has the newer preference system although still incomplete. This allows a user name and passwrd to be set for each instance as well as the buglist parameters to be set by instance. the preferences for this version can be found on the add-ons window and then click the options button for buggy bar. <br />
* fixed some little bugs after some questions from current users as well as changed the pref manager so that passwords are stored in the password manager. Also you can set up many of the same instances so you can have different accounts with different bug list settings. I'm also trying to figure out how those settings should be set for both search and buglist as most of the fields (ie: product, status, etc.) are instance specific so I may have to pull them from the xml file. Right now you have to manually create the url fields.<br />
*more progress with the xml file portions implemented, specific search almost done, bug access cleaned up some and some more fixes. Next I'm going to finish the specific search and the xml file portion and then I'll post a dev release. I'm hoping to have a full public release in the near future.<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
*small addition to version 0.1 just changed the XUL as part of a user request so that it would remain functional even at a smaller size. This was only done in this version because it doesn't affect the actual code and is essential for many users. 0.2 is on the way and I'm in the design phase with some draft diagrams already completed. <br />
**[http://cs1.senecac.on.ca/~b6001a07/buggybar0.1.1.xpi 0.1.1]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1]<br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*<s>control bug list search parameters</s><br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*incorporate user input<br />
*code overhaul<br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*allow setting buglist search parameters<br />
*allow searches with full search parameters<br />
*move preferences to own window<br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9293Bug Triage Extension2007-01-11T19:45:17Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]][[Image:buggybar-plus.png | ]][[Image:buggybar-minus.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [https://addons.mozilla.org/firefox/4117/ Firefox add-ons page]. New design first draft completed. Received first suggestion questions.<br />
===5/01/2007===<br />
hit over 1000 downloads and got a mention on the mozillazine QA blog thanks to robcee: <br />
[http://weblogs.mozillazine.org/qa/archives/2007/01/buggy_bar_extension.html#comments weblogs.mozillazine.org/qa]<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
*completed user input phase and completed new paper design. now its back into the code. started by putting totalField in bugSpecs. more to come<br />
*rewrote preferences section into much nicer object. Now instances have their own login information as well as can read an XML file to determine the status options or can use the default mozilla one. Also moved options to its own section. Next I'll be working on fields which will be a big part. I wont be releasing until I get a version that works, currently some portions don't work with other portions and it will break if you don't know how to use it. I've also been talking to the QA guys about writing a similar extension for litmus and test day. <br />
*more work on ver 0.2. Integrated new Pref management system with rest of code. Fixed some bugs in Pref management system and its now at the point it was in ver 0.1 from a functional stand point. Next I'll be setting up the bug list options in the preference management system. I'll post a work in progress by the end of the weekend.<br />
*implemented new feature using new pref management system so remember current instance when buggy bar is closed or Firefox is shutdown. A small one but a good one, now I'll start on the new bugList options. Also fixed some bugs, end of weekend release still pending.<br />
*ok I was a bit late on this development release but here it is : [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi buggybar-dev-0.1.2.xpi]. This version has the newer preference system although still incomplete. This allows a user name and passwrd to be set for each instance as well as the buglist parameters to be set by instance. the preferences for this version can be found on the add-ons window and then click the options button for buggy bar. <br />
* fixed some little bugs after some questions from current users as well as changed the pref manager so that passwords are stored in the password manager. Also you can set up many of the same instances so you can have different accounts with different bug list settings. I'm also trying to figure out how those settings should be set for both search and buglist as most of the fields (ie: product, status, etc.) are instance specific so I may have to pull them from the xml file. Right now you have to manually create the url fields.<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
*small addition to version 0.1 just changed the XUL as part of a user request so that it would remain functional even at a smaller size. This was only done in this version because it doesn't affect the actual code and is essential for many users. 0.2 is on the way and I'm in the design phase with some draft diagrams already completed. <br />
**[http://cs1.senecac.on.ca/~b6001a07/buggybar0.1.1.xpi 0.1.1]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1]<br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*incorporate user input<br />
*code overhaul<br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*allow setting buglist search parameters<br />
*allow searches with full search parameters<br />
*move preferences to own window<br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9276Bug Triage Extension2007-01-09T22:19:24Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]][[Image:buggybar-plus.png | ]][[Image:buggybar-minus.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [https://addons.mozilla.org/firefox/4117/ Firefox add-ons page]. New design first draft completed. Received first suggestion questions.<br />
===5/01/2007===<br />
hit over 1000 downloads and got a mention on the mozillazine QA blog thanks to robcee: <br />
[http://weblogs.mozillazine.org/qa/archives/2007/01/buggy_bar_extension.html#comments weblogs.mozillazine.org/qa]<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
*completed user input phase and completed new paper design. now its back into the code. started by putting totalField in bugSpecs. more to come<br />
*rewrote preferences section into much nicer object. Now instances have their own login information as well as can read an XML file to determine the status options or can use the default mozilla one. Also moved options to its own section. Next I'll be working on fields which will be a big part. I wont be releasing until I get a version that works, currently some portions don't work with other portions and it will break if you don't know how to use it. I've also been talking to the QA guys about writing a similar extension for litmus and test day. <br />
*more work on ver 0.2. Integrated new Pref management system with rest of code. Fixed some bugs in Pref management system and its now at the point it was in ver 0.1 from a functional stand point. Next I'll be setting up the bug list options in the preference management system. I'll post a work in progress by the end of the weekend.<br />
*implemented new feature using new pref management system so remember current instance when buggy bar is closed or Firefox is shutdown. A small one but a good one, now I'll start on the new bugList options. Also fixed some bugs, end of weekend release still pending.<br />
*ok I was a bit late on this development release but here it is : [http://cs1.senecac.on.ca/~b6001a07/buggybar-dev-0.1.2.xpi buggybar-dev-0.1.2.xpi]. This version has the newer preference system although still incomplete. This allows a user name and passwrd to be set for each instance as well as the buglist parameters to be set by instance. the preferences for this version can be found on the add-ons window and then click the options button for buggy bar. <br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
*small addition to version 0.1 just changed the XUL as part of a user request so that it would remain functional even at a smaller size. This was only done in this version because it doesn't affect the actual code and is essential for many users. 0.2 is on the way and I'm in the design phase with some draft diagrams already completed. <br />
**[http://cs1.senecac.on.ca/~b6001a07/buggybar0.1.1.xpi 0.1.1]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1]<br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*incorporate user input<br />
*code overhaul<br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*allow setting buglist search parameters<br />
*allow searches with full search parameters<br />
*move preferences to own window<br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9249Bug Triage Extension2007-01-07T04:38:46Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]][[Image:buggybar-plus.png | ]][[Image:buggybar-minus.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [https://addons.mozilla.org/firefox/4117/ Firefox add-ons page]. New design first draft completed. Received first suggestion questions.<br />
===5/01/2007===<br />
hit over 1000 downloads and got a mention on the mozillazine QA blog thanks to robcee: <br />
[http://weblogs.mozillazine.org/qa/archives/2007/01/buggy_bar_extension.html#comments weblogs.mozillazine.org/qa]<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
*completed user input phase and completed new paper design. now its back into the code. started by putting totalField in bugSpecs. more to come<br />
*rewrote preferences section into much nicer object. Now instances have their own login information as well as can read an XML file to determine the status options or can use the default mozilla one. Also moved options to its own section. Next I'll be working on fields which will be a big part. I wont be releasing until I get a version that works, currently some portions don't work with other portions and it will break if you don't know how to use it. I've also been talking to the QA guys about writing a similar extension for litmus and test day. <br />
*more work on ver 0.2. Integrated new Pref management system with rest of code. Fixed some bugs in Pref management system and its now at the point it was in ver 0.1 from a functional stand point. Next I'll be setting up the bug list options in the preference management system. I'll post a work in progress by the end of the weekend.<br />
*implemented new feature using new pref management system so remember current instance when buggy bar is closed or Firefox is shutdown. A small one but a good one, now I'll start on the new bugList options. Also fixed some bugs, end of weekend release still pending.<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
*small addition to version 0.1 just changed the XUL as part of a user request so that it would remain functional even at a smaller size. This was only done in this version because it doesn't affect the actual code and is essential for many users. 0.2 is on the way and I'm in the design phase with some draft diagrams already completed. <br />
**[http://cs1.senecac.on.ca/~b6001a07/buggybar0.1.1.xpi 0.1.1]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1]<br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*incorporate user input<br />
*code overhaul<br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*allow setting buglist search parameters<br />
*allow searches with full search parameters<br />
*move preferences to own window<br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9248Bug Triage Extension2007-01-06T03:15:42Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]][[Image:buggybar-plus.png | ]][[Image:buggybar-minus.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [https://addons.mozilla.org/firefox/4117/ Firefox add-ons page]. New design first draft completed. Received first suggestion questions.<br />
===5/01/2007===<br />
hit over 1000 downloads and got a mention on the mozillazine QA blog thanks to robcee: <br />
[http://weblogs.mozillazine.org/qa/archives/2007/01/buggy_bar_extension.html#comments weblogs.mozillazine.org/qa]<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
*completed user input phase and completed new paper design. now its back into the code. started by putting totalField in bugSpecs. more to come<br />
*rewrote preferences section into much nicer object. Now instances have their own login information as well as can read an XML file to determine the status options or can use the default mozilla one. Also moved options to its own section. Next I'll be working on fields which will be a big part. I wont be releasing until I get a version that works, currently some portions don't work with other portions and it will break if you don't know how to use it. I've also been talking to the QA guys about writing a similar extension for litmus and test day. <br />
*more work on ver 0.2. Integrated new Pref management system with rest of code. Fixed some bugs in Pref management system and its now at the point it was in ver 0.1 from a functional stand point. Next I'll be setting up the bug list options in the preference management system. I'll post a work in progress by the end of the weekend. <br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
*small addition to version 0.1 just changed the XUL as part of a user request so that it would remain functional even at a smaller size. This was only done in this version because it doesn't affect the actual code and is essential for many users. 0.2 is on the way and I'm in the design phase with some draft diagrams already completed. <br />
**[http://cs1.senecac.on.ca/~b6001a07/buggybar0.1.1.xpi 0.1.1]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1]<br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*incorporate user input<br />
*code overhaul<br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*allow setting buglist search parameters<br />
*allow searches with full search parameters<br />
*move preferences to own window<br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9245Bug Triage Extension2007-01-04T21:06:44Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]][[Image:buggybar-plus.png | ]][[Image:buggybar-minus.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [https://addons.mozilla.org/firefox/4117/ Firefox add-ons page]. New design first draft completed. Received first suggestion questions.<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
*completed user input phase and completed new paper design. now its back into the code. started by putting totalField in bugSpecs. more to come<br />
*rewrote preferences section into much nicer object. Now instances have their own login information as well as can read an XML file to determine the status options or can use the default mozilla one. Also moved options to its own section. Next I'll be working on fields which will be a big part. I wont be releasing until I get a version that works, currently some portions don't work with other portions and it will break if you don't know how to use it. I've also been talking to the QA guys about writing a similar extension for litmus and test day. <br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
*small addition to version 0.1 just changed the XUL as part of a user request so that it would remain functional even at a smaller size. This was only done in this version because it doesn't affect the actual code and is essential for many users. 0.2 is on the way and I'm in the design phase with some draft diagrams already completed. <br />
**[http://cs1.senecac.on.ca/~b6001a07/buggybar0.1.1.xpi 0.1.1]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1]<br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*incorporate user input<br />
*code overhaul<br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*allow setting buglist search parameters<br />
*allow searches with full search parameters<br />
*move preferences to own window<br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9239Bug Triage Extension2006-12-28T22:48:25Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]][[Image:buggybar-plus.png | ]][[Image:buggybar-minus.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [https://addons.mozilla.org/firefox/4117/ Firefox add-ons page]. New design first draft completed. Received first suggestion questions.<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
**completed user input phase and completed new paper design. now its back into the code. started by putting totalField in bugSpecs. more to come<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
*small addition to version 0.1 just changed the XUL as part of a user request so that it would remain functional even at a smaller size. This was only done in this version because it doesn't affect the actual code and is essential for many users. 0.2 is on the way and I'm in the design phase with some draft diagrams already completed. <br />
**[http://cs1.senecac.on.ca/~b6001a07/buggybar0.1.1.xpi 0.1.1]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1]<br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*incorporate user input<br />
*code overhaul<br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*allow setting buglist search parameters<br />
*allow searches with full search parameters<br />
*move preferences to own window<br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9232Bug Triage Extension2006-12-20T20:49:54Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]][[Image:buggybar-plus.png | ]][[Image:buggybar-minus.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [https://addons.mozilla.org/firefox/4117/ Firefox add-ons page]. New design first draft completed. Received first suggestion questions.<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
*small addition to version 0.1 just changed the XUL as part of a user request so that it would remain functional even at a smaller size. This was only done in this version because it doesn't affect the actual code and is essential for many users. 0.2 is on the way and I'm in the design phase with some draft diagrams already completed. <br />
**[http://cs1.senecac.on.ca/~b6001a07/buggybar0.1.1.xpi 0.1.1]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1]<br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*incorporate user input<br />
*code overhaul<br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*allow setting buglist search parameters<br />
*allow searches with full search parameters<br />
*move preferences to own window<br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=File:Buggybar-minus.png&diff=9231File:Buggybar-minus.png2006-12-20T20:48:55Z<p>Djhamp-g: buggy bar minus sign</p>
<hr />
<div>buggy bar minus sign</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=File:Buggybar-plus.png&diff=9230File:Buggybar-plus.png2006-12-20T20:48:31Z<p>Djhamp-g: plus sign for adding items on buggy bar</p>
<hr />
<div>plus sign for adding items on buggy bar</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9229Bug Triage Extension2006-12-20T20:47:29Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]][[Image:buggybar-plus.png | ]][[Image:buggybar-minus.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [[https://addons.mozilla.org/firefox/4117/ |Firefox add-ons page]]. New design first draft completed. Received first suggestion questions.<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
*small addition to version 0.1 just changed the XUL as part of a user request so that it would remain functional even at a smaller size. This was only done in this version because it doesn't affect the actual code and is essential for many users. 0.2 is on the way and I'm in the design phase with some draft diagrams already completed. <br />
**[http://cs1.senecac.on.ca/~b6001a07/buggybar0.1.1.xpi 0.1.1]]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1]<br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*incorporate user input<br />
*code overhaul<br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*allow setting buglist search parameters<br />
*allow searches with full search parameters<br />
*move preferences to own window<br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9222Bug Triage Extension2006-12-19T03:42:53Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]]<br />
<br />
===18/12/2006===<br />
the buggy bar is now on the [[https://addons.mozilla.org/firefox/4117/ |Firefox add-ons page]]. New design first draft completed. Received first suggestion questions.<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1] <br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*incorporate user input<br />
*code overhaul<br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*allow setting buglist search parameters<br />
*allow searches with full search parameters<br />
*move preferences to own window<br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9221Bug Triage Extension2006-12-19T00:21:15Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]]<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1] <br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*incorporate user input<br />
*code overhaul<br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
*allow setting buglist search parameters<br />
*allow searches with full search parameters<br />
*move preferences to own window<br />
*alert when empty list returns or if a bug doesn't exist<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9216Bug Triage Extension2006-12-18T04:58:37Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
**buggybar@gmail.com<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]]<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1] <br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*incorporate user input<br />
*code overhaul<br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9215Bug Triage Extension2006-12-18T04:58:10Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at buggybar@gmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]]<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1] <br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*incorporate user input<br />
*code overhaul<br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=File:Buggybar-search.png&diff=9214File:Buggybar-search.png2006-12-18T04:50:40Z<p>Djhamp-g: </p>
<hr />
<div></div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=File:Buggybar-email.png&diff=9213File:Buggybar-email.png2006-12-18T04:50:34Z<p>Djhamp-g: </p>
<hr />
<div></div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=File:Buggybar-foward.png&diff=9212File:Buggybar-foward.png2006-12-18T04:50:23Z<p>Djhamp-g: </p>
<hr />
<div></div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=File:Buggybar-reload.png&diff=9211File:Buggybar-reload.png2006-12-18T04:50:12Z<p>Djhamp-g: </p>
<hr />
<div></div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9210Bug Triage Extension2006-12-18T04:49:46Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at invagle@hotmail.com<br />
<br />
===17/12/2006===<br />
waiting for account approval to get buggy bar on the firefox extension page. Rich Lawson finished the buggy bar logo and I did the new buttons: [[Image:buggybar-reload.png | ]][[Image:buggybar-foward.png | ]][[Image:buggybar-email.png | ]][[Image:buggybar-search.png | ]]<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1] <br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*incorporate user input<br />
*code overhaul<br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9209Bug Triage Extension2006-12-18T04:46:32Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
[[Image:buggyBar-logo-bg.png | ]]<br/><br/><br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at invagle@hotmail.com<br />
<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1] <br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*incorporate user input<br />
*code overhaul<br />
*support all bug status changes<br />
*comment code<br />
*<s>create button images</s><br />
*<s>decide on logo</s><br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=File:BuggyBar-logo-bg.png&diff=9208File:BuggyBar-logo-bg.png2006-12-18T04:43:59Z<p>Djhamp-g: </p>
<hr />
<div></div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=9207Bug Triage Extension2006-12-18T04:43:46Z<p>Djhamp-g: </p>
<hr />
<div>[[Image:buggyBar-logo-bg.png | ]]<br />
<br />
== Project Name ==<br />
<br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*[[User:elichak | Liz Chak]] - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at invagle@hotmail.com<br />
<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1] <br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*incorporate user input<br />
*code overhaul<br />
*support all bug status changes<br />
*comment code<br />
*create button images<br />
*decide on logo<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=User_talk:Djhamp-g&diff=8972User talk:Djhamp-g2006-12-14T18:12:41Z<p>Djhamp-g: </p>
<hr />
<div>You should learn to use capital letters..<br />
*i know how to use them i'm just not a big fan of them, i'm just not a capital letter kinda guy. thats why my personal has none.<br />
*Correction: I know how to use them I'm just not a big fan of them, I'm just not a capital letter kinda guy. That's why my personal has none.<br />
*hater ^</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=User_talk:Djhamp-g&diff=8969User talk:Djhamp-g2006-12-14T18:10:50Z<p>Djhamp-g: </p>
<hr />
<div>You should learn to use capital letters..<br />
*i know how to use them i'm just not a big fan of them, i'm just not a capital letter kinda guy. thats why my personal has none.</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=User:Djhamp-g&diff=8946User:Djhamp-g2006-12-14T17:16:18Z<p>Djhamp-g: </p>
<hr />
<div><h3>Bio</h3><br />
'''Name:''' david hamp-gonsalves <br/><br />
'''IRC:''' inveigle <br/><br />
'''Email:''' djhamp-g@learn.senecac.on.ca<br/><br />
<br />
<h3>Projects</h3><br />
*[[Assignment 1(djhamp-g)|Assignment1]] <br />
*[[Bug_Triage_Extension|Assignment 2 - Bug Triage Extension]]<br />
<br />
<h3>Project Contributions</h3><br />
*Generalization of Joga extension<br />
**helped paul with some problems since we were both working on similar projects and both had to deal with javascripts nonsense.<br />
*Firefox Performance Testing<br />
**helped fixing document sentence structure and grammar.<br />
**helped with some coding buffer problems.<br />
**testing the framework<br />
**in-class testing<br />
**final testing, running and evaluation</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=New_Firefox_Performance_Testing_Framework_comments&diff=8943New Firefox Performance Testing Framework comments2006-12-14T17:15:47Z<p>Djhamp-g: </p>
<hr />
<div>==Introduction==<br />
This page is to gather all the testers' thoughts and comments about the New Firefox Performance Testing Framework<br />
<br />
==Tester comments==<br />
*djhamp-g<br />
**Everything ran smoothly<br />
**new config script was a great improvement<br />
**status bar was informative<br />
**very easy to use</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=User:Djhamp-g&diff=8938User:Djhamp-g2006-12-14T15:44:03Z<p>Djhamp-g: </p>
<hr />
<div><h3>Bio</h3><br />
'''Name:''' david hamp-gonsalves <br/><br />
'''IRC:''' inveigle <br/><br />
'''Email:''' djhamp-g@learn.senecac.on.ca<br/><br />
<br />
<h3>Projects</h3><br />
*[[Assignment 1(djhamp-g)|Assignment1]] <br />
*[[Bug_Triage_Extension|Assignment 2 - Bug Triage Extension]]<br />
<br />
<h3>Project Contributions</h3><br />
*Generalization of Joga extension<br />
**helped paul with some problems since we were both working on similar projects and both had to deal with javascripts nonsense.<br />
*Firefox Performance Testing<br />
**helped fixing document sentence structure and grammar.<br />
**helped with some coding buffer problems.<br />
**testing the framework<br />
**in-class testing</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=User:Djhamp-g&diff=8727User:Djhamp-g2006-12-14T00:00:16Z<p>Djhamp-g: </p>
<hr />
<div><h3>Bio</h3><br />
'''Name:''' david hamp-gonsalves <br/><br />
'''IRC:''' inveigle <br/><br />
'''Email:''' djhamp-g@learn.senecac.on.ca<br/><br />
<br />
<h3>Projects</h3><br />
*[[Assignment 1(djhamp-g)|Assignment1]] <br />
*[[Bug_Triage_Extension|Assignment 2 - Bug Triage Extension]]<br />
<br />
<h3>Project Contributions</h3><br />
*Generalization of Joga extension<br />
**helped paul with some problems since we were both working on similar projects and both had to deal with javascripts nonsense.<br />
*Firefox Performance Testing<br />
**helped fixing document sentence structure and grammar.<br />
**helped with some coding buffer problems.</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=8724Bug Triage Extension2006-12-13T23:52:48Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
<br />
Bug Triage Extension - Buggy Bar<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*Liz Chak - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at invagle@hotmail.com<br />
<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1] <br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*incorporate user input<br />
*code overhaul<br />
*support all bug status changes<br />
*comment code<br />
*create button images<br />
*decide on logo<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=8723Bug Triage Extension2006-12-13T23:52:27Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
<br />
Bug Triage Extension<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*Liz Chak - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at invagle@hotmail.com<br />
<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1] <br />
<br />
==Source==<br />
This being a Fire Fox extension you can just rename the "*.xpi" to "*.zip" and unzip the file to view source.<br/><br />
<br />
==To Do 0.1(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*<s>use XML for bug Specs</s><br />
<br />
<br />
<br />
==To Do 0.2(striked out means complete)==<br />
*incorporate user input<br />
*code overhaul<br />
*support all bug status changes<br />
*comment code<br />
*create button images<br />
*decide on logo<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=8722Bug Triage Extension2006-12-13T23:48:48Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
<br />
Bug Triage Extension<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*Liz Chak - logo, testing<br />
<br />
== Project Status ==<br />
===13/12/2006===<br />
Buggy Bars First Release!<br/><br />
With the first release out There are still a long list of things to do. While the first release supports all the initial requested functionality it doesn't have much error checking and other areas are lacking as well. I want to overhaul the back end and fix some areas that were coded poorly because of my inexperience with javascript and also the icons and images for the project which will be done by my friend and graphic designer Rich Lawson. For the next release I'm expecting these areas to be fixed and I hope to release it public use. Currently I am looking for suggestions about changes and improvements and looking for testers and I can be reached at invagle@hotmail.com<br />
<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
*release 0.1<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
***[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1] <br />
<br />
==To Do(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**<s>etc</s><br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*<s>update bug</s><br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*comment code<br />
*create button images<br />
*decide on logo<br />
*<s>use XML for bug Specs</s><br />
<br />
*finish to do list<br />
*allow for multiple searches/bugzilla instances<br />
<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=8718Bug Triage Extension2006-12-13T23:37:03Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
<br />
Bug Triage Extension<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*Liz Chak - logo, testing<br />
<br />
== Project Details ==<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>Break Through< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
*after some more research and some talk on the irc.mozilla.org channel #webtools I found out that the problem with the current(12/12/2006) instance of bugzilla is limited to that one subversion(2.20.0) and in 2 weeks bugzilla will be updated. This being the case I'm not planning on supporting the version currently, later I could but It seams like a small user group so its not a big deal now.<br />
*added better searching for the "steps to reproduce" and now if not found the output label changes to more understandable text<br />
*Buggy Bars first release!<br />
**features<br />
**view hot bug list<br />
**view individual bugs specs<br />
**customize field options<br />
**change bugs from "NEW" or "UNCONFIRMED" status to "CONFIRMED" or "ASSIGNED"<br />
**download [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi here!] and try it out!<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
*[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi 13/12/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-01.PNG screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-02.PNG screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1-03.PNG screen shot3]<br />
<br />
==Releases==<br />
13/12/2006 - [http://cs1.senecac.on.ca/~b6001a07/buggyBar-0.1.xpi Buggy Bar 0.1] <br />
<br />
==To Do(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**etc<br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*update bug(almost done)<br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*comment code<br />
*create button images<br />
*decide on logo<br />
*<s>use XML for bug Specs</s><br />
<br />
*finish to do list<br />
*allow for multiple searches/bugzilla instances<br />
<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=8255Bug Triage Extension2006-12-12T15:30:13Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
<br />
Bug Triage Extension<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*Liz Chak - logo, testing<br />
<br />
== Project Details ==<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>>Break Through<< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
<br />
<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006] -> screen shots coming for next release<br />
<br />
==To Do(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**etc<br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*update bug(almost done)<br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*comment code<br />
*create button images<br />
*decide on logo<br />
*<s>use XML for bug Specs</s><br />
<br />
*finish to do list<br />
*allow for multiple searches/bugzilla instances<br />
<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=8115Bug Triage Extension2006-12-11T23:46:09Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
<br />
Bug Triage Extension<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*Liz Chak - logo, testing<br />
<br />
== Project Details ==<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>>Break Through<< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
**Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
<br />
<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006]<br />
<br />
==To Do(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**etc<br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*update bug(almost done)<br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*comment code<br />
*create button images<br />
*decide on logo<br />
*<s>use XML for bug Specs</s><br />
<br />
*finish to do list<br />
*allow for multiple searches/bugzilla instances<br />
<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=8114Bug Triage Extension2006-12-11T23:45:51Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
<br />
Bug Triage Extension<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*Liz Chak - logo, testing<br />
<br />
== Project Details ==<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
*preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>>Break Through<< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*Save functionality update with some extras<br />
**added new bugaccess class which uses the XML format for bugspecs. <br />
**Save functionality works on bugzilla 2.20.3 and onwards<br />
**Fast bugzilla instance switching from a drop down on buglist tab<br />
*Will make old pure html parsing bugAccess class an option for older bugzilla versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the back end, going to rip out the field handling soon and stick a nice object in there. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
<br />
<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006]<br />
<br />
==To Do(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**etc<br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*update bug(almost done)<br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*comment code<br />
*create button images<br />
*decide on logo<br />
*<s>use XML for bug Specs</s><br />
<br />
*finish to do list<br />
*allow for multiple searches/bugzilla instances<br />
<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-ghttps://wiki.cdot.senecacollege.ca/w/index.php?title=Bug_Triage_Extension&diff=8113Bug Triage Extension2006-12-11T23:42:17Z<p>Djhamp-g: </p>
<hr />
<div>== Project Name ==<br />
<br />
Bug Triage Extension<br />
<br />
== Project Description ==<br />
Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.<br />
<br />
Reference: talk to beltzner. <br />
<br />
== Project Leader(s) ==<br />
*[[User:djhamp-g|David Hamp-Gonsalves]]<br />
<br />
== Project Contributor(s) ==<br />
<br />
*Jeff Mossop - Created Images for the Bug Triage Extension - [[BugPics | Click Here to View]]<br/><br />
*Liz Chak - logo, testing<br />
<br />
== Project Details ==<br />
<br />
== Project News ==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi first try at creating a FF extension]<br />
* emailed beltzner<br />
<br />
* Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)<br />
<br />
* Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.<br />
<br />
* New good link added: http://www.allpeers.com/blog/creating-complex-firefox-extensions<br />
<br />
*possiable answer to database connection stuff: http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html?page=last<br />
*working on installing SQL functionality:<br />
**https://bugzilla.mozilla.org/show_bug.cgi?id=81653<br />
**http://eu.mozdev.org/Brussels2003/talks/jan/index.html<br />
**http://www.mozilla.org/projects/sql/<br />
*rethink...<br />
*talked to [[User:David.humphrey | Dave Humphrey]] and [[User:Reed | Reed]] got some new ideas<br />
*back on track, bugzilla offers a webservice interface... but the api for it is still in the works.<br />
*learning how to connect to webservice through extension<br />
*away from October 14th-19th,2006<br />
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html<br />
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now. This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.<br />
*I finally had more time to work on the extension again. This release actually does something which is nice. <br />
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]<br />
**possible name:buggy bar<br />
**downloads top hottest bugs and displays them in a list<br />
**progress bar for refreshing list<br />
**designed screens and feature list<br />
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier<br />
<br />
*I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.<br />
*I'm also looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.<br />
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.<br />
* new version more features<br />
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.<br />
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.<br />
preferences added, and search and better html tag stripping<br />
*exams so not much time, but I've been fixing things and looking at bugzilla code to overcome final update hurdle will post new version soon.<br />
*>>Break Through<< the buggy bar finally updated its first bug on landfill. finally fixed some bugs after working through some wrong information and finally getting the XmlRequest post methods to work. Will have new version up tonight or tomorrow but I've postponed studying for long enough so I'll have to do that first. <br />
*added new bugaccess class which uses the XML format for bugspecs. Will make old pure html parsing one an option for old versions. Save functionality works on bugzilla 2.20.3 and onwards but the mozilla instance is 2.20 so it has a bug but you can test it on the landfill instances, still waiting for my new account on the 2.18 instance to see if that one works. also fixed some things up in the backend, going to rip out the field handling soon and stick a nice object in there. Added a fast instance switching so you can choose you bugzilla instance from a drop down easily. Oh and the save feature shows the results in the main window I'll finish that up later.<br />
<br />
<br />
<br />
==Extension Progress==<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT6.xpi 27/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]<br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-1.bmp screen shot1]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-2.bmp screen shot2]<br />
**[http://cs1.senecac.on.ca/~b6001a07/buggyBar-9-3.bmp screen shot3] <br />
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT10.xpi 11/12/2006]<br />
<br />
==To Do(striked out means complete)==<br />
*<s>create user preferences feature</s><br />
*<s>switch html special character back to original character</s><br />
*<s>view bug specs feature</s><br />
**<s>steps to reproduce</s><br />
**<s>summary</s><br />
**etc<br />
*login to bugzilla feature<br />
*control bug list search parameters<br />
*update bug(almost done)<br />
*<s>allow for bugxilla instances to be saved and selected</s><br />
*rip field code out and put it in object<br />
*comment code<br />
*create button images<br />
*decide on logo<br />
*<s>use XML for bug Specs</s><br />
<br />
*finish to do list<br />
*allow for multiple searches/bugzilla instances<br />
<br />
<br />
<br />
== Project Resources ==<br />
<br />
*http://www.allpeers.com/blog/creating-complex-firefox-extensions <br />
<br />
*http://www.borngeek.com/firefox/tutorial/<br />
<br/><br />
*http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/<br />
*http://www.orablogs.com/duffblog/archives/000536.html<br />
*http://www.bengoodger.com/software/mb/extensions/howto.html</div>Djhamp-g