Re: Collab code impact

On Sun, 2014-03-02 at 21:45 +0000, Reuben Thomas wrote:
> In my recent wide-ranging work on the FF codebase, I've come across
> the impact of the experimental collab work at various points.
> 
> 
> I'm wondering whether something can be done to reduce this;
> specifically, whether there need be any mention of collab in Fontforge
> proper at all? The question is naturally addressed mainly to Ben
> Martin! Essentially, I'm wondering whether it could be based around a
> plugin…so that if you're not actually working on the collab code, you
> don't see any of it, or have to worry about it.
> 
> Thoughts?

Hi,
  I'm always happy to try to minimize the impact of this code on the
wider codebase. I've tried to minimize the current impact by making the
function shells available as empty shells on non collab builds to avoid
preprocessor guards and the like. The main area this has to have some
hook into is the undo/redo stuff, but that should be fairly narrow.

  I'll take another look at some stage to see if things can be narrowed
down. Specific suggestions are always welcome :)



------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Fontforge-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel