On 28 févr. 2013, at 12:47, David Kastrup wrote:
> "m...@mikesolomon.org" writes:
>
>> On 28 févr. 2013, at 12:40, Werner LEMBERG wrote:
>>
>>>
> Renaming properties which do something differently is the way to go
> IMHO.
Then the first step is finding all properties that
"m...@mikesolomon.org" writes:
> On 28 févr. 2013, at 12:40, Werner LEMBERG wrote:
>
>>
Renaming properties which do something differently is the way to go
IMHO.
>>>
>>> Then the first step is finding all properties that are defined in
>>> multiple interfaces and changing their names
On 28 févr. 2013, at 12:40, Werner LEMBERG wrote:
>
>>> Renaming properties which do something differently is the way to go
>>> IMHO.
>>
>> Then the first step is finding all properties that are defined in
>> multiple interfaces and changing their names.
>
> Maybe a naïve question: Are there m
>> Renaming properties which do something differently is the way to go
>> IMHO.
>
> Then the first step is finding all properties that are defined in
> multiple interfaces and changing their names.
Maybe a naïve question: Are there many?
Werner
On 28 févr. 2013, at 12:16, Werner LEMBERG wrote:
>
>> I think that at the current point of time, we should try getting
>> along with a flat namespace approach. That might imply renaming
>> properties like "padding" to "side-padding" if we can't achieve
>> reasonable results otherwise. Not su
> I think that at the current point of time, we should try getting
> along with a flat namespace approach. That might imply renaming
> properties like "padding" to "side-padding" if we can't achieve
> reasonable results otherwise. Not sure about that.
I support that. Renaming properties which
"m...@mikesolomon.org" writes:
> Working on eliminating the translate_axis call from
> axis-group-interface, I've found a less-than-ideal situation in the
> naming/using of interfaces and properties that I'd like to clean up,
> but it'd be a major, major change and would take time to implement.
>
Hey all,
Working on eliminating the translate_axis call from axis-group-interface, I've
found a less-than-ideal situation in the naming/using of interfaces and
properties that I'd like to clean up, but it'd be a major, major change and
would take time to implement. So, before starting it as a
