You will probably be seeing quite a bit of me over the next few months so I figured I'd say hi.
hi.
I've been tasked with customizing the SplendidCRM Outlook Plug-in. We are using it against Sugar.
Most of the changes are around expanding Outlook to mimic Sugar behavior for those who work mostly offline in Outlook. For instance modifying the settings to hide "Admin" settings from the user while storing them upon installation in the Registry, or creating a "SugarContact" specific outlook form allowing a company and role dropdown or restricting the synchronization of Items marked Private (this is just a taste, I'm with a large government like corporation so needless to say they want a lot).
I have a fairly good understanding of what you guys have been doing (considering I've been looking at the code for about a week) and I don't mind working on bugs in exchange for information/support/love (just don't tell my people). I'm sure that some of the things I'm doing here will be beneficial to the codebase over all, but i'm concerned about what I need to do to incorporate your bug fixes while maintaining my seperate branch of the code, and submitting code that you'd find useful. One thing I've been doing is documenting the code for easy use with Sandcastle (Long Live N'Doc). I'd also like to know if any testing has been done on the Outlook 2007 beta.
Any suggestions, ideas or direction would be greatly appreciated. Even something as simple as "should I talk here or in CodePlex".
Thanks.
We have not done any testing with Outlook 2007.
The best way to keep track of our changes is to use a version control system on your end, and compare the differences. We are pretty good a placing a developer date and signature on bug fixes, so a diff should tell you what has happend.
I'm going to try the plug-in with the 2007 beta, so I'll let you know.
Meanwhile how do I hook into your change control process? I see where i can get the Splendid Source from but not the Plug-In source (which we've purchased). Also, how can i see the list of planned changes and bug fixes you have planned so I don't end up reinventing the wheel, or I do invent the wheel and let you roll with me :^).
You should have been sent the source code to the plug-in. We had hoped to us CodePlex to manage the source code, but it has not worked out as planned.
