Just a quick post to share my SourceServer Presentation if anyone’s interested in an overview of what my project this term in DPS909 has entailed.
Tag: mozilla
XPcom Lab II
Well there was an initial kerfuffle trying to get the extension “firstxpcomchrome” working in my Minefield build. Turns out that when I was attempting to connect it up via a text file in the profiles/myprofile/extensions folder, I had put the path as a c:/…. path which, in Unix (ie Mac), is not correct. This was affecting my ability to install the extension through drag n drop because the file for firstxpcomchrome@senecac.on.ca was not being overwritten so even though the extension appeared to install correctly in the add-ons manager window, upon restarting it was nowhere to be seen. Deleting the erroneous flat file and doing a drag and drop installation cleared this up and I was able to continue with the lab.
Aside from crashing the browser every time I called on “Reload All Chrome” from the Extension Developer add-on, the lab went smoothly.
Results:
(please enjoy the File menu behaviour that is happening in the background)
Call
Source Server 0.3 goals
Well, it turns out that my 0.2 release was a little buggy but Ted (luser) was able to hack his srcsrv.ini file to overwrite the URL I had indexed into the pdb files so that he was able to pull code from my server. Instead of hacking the 0.2 and fixing that though, I am moving forward with 0.3 which is to put into symbolstore.py the ability to do the cvs pulls.
This is the most complicated part yet, for me, because I am not too familiar with python and because I still see all this code as a nebulous cloud and finding the path from A to B is difficult.
So my steps toward my 0.3 goal so far have been:
- Reading up on Python and how it works with some: Python Tutorials
- Studying the logic of symbolstore.py
And coming soon, some hacks of symbolstore.py to see what kind of havoc I can wreak.
