Tal Leming

> Please forgive me for piling on to this thread. I'm just wondering more generally about the reason for the Common Value Types definitions in the documentation. Is the idea...

“Tuple” is fine. I don’t remember why I didn’t just use that. Background: the returned lists/tuples are immutable because we were running into situations like this: ```python font.groups[“group1”].append(“aGlyph”) ``` In...

> Also, there seems to be a few discrepancies between the contents of font.py and layer.py. Basically, dir(BaseFont) reveals a few public methods not defined in font.py, but imported from...

> Thanks for clarifying. I gather that the BaseFont.keys method, which is shared with the BaseLayer class, should be documented as being tied to the default layer. Yep.

> Given that the default value of the public method provides the basis for specific, practical logic, is this an oversight, or is it intentional? Do you mean the `**kwargs`?...

> No, sorry for not bing clear. The kwargs is very logical. I'm alluding to name being optional in the public method, but not in the private one. Ah. This...

Hmmm. Yeah, I think we would need to do a lib key.

I was thinking about the file structure last night. Would it be more useful if we stored width and height instead of just a number? That's what I did in...

> Can we agree on a set of keys for stems? **Yes.** I agree that being able to get stem values is crucially important. I think we need to have...

> If we always require a horizontal and vertical value, would it make sense to just store a tuple (10, 23)? This makes things difficult in Laser Measure. If the...