On Wed, Mar 11, 2009 at 8:20 AM, Edward K. Ream <[email protected]> wrote:
>
>
> On Tue, Mar 10, 2009 at 3:48 PM, Ville M. Vainio <[email protected]> wrote:
>>
>> Perhaps this would be the time to move my 'select()' proposal forward:
>>
>>
>> http://groups.google.com/group/leo-editor/browse_thread/thread/d8362a15c05697ff
>>
>> The code is already done, all it needs is adding c.find_h() to controller.
>>
>> So basically, you would find nodes by:
>>
>> c.find_h('Gui wrap.*').select(".*Qt").select('Font')
>>
>> I can add it to trunk if it's ok for Edward / others.
>
> Please go ahead.
>>
>>
>> Let's avoid function names like findNodeAnywhere_iter... they are an
>> absolute nightmare to remember.
>
> I am not so sure.  I do think this is an important topic.
>
> As I get older, my memory for certain kinds of things has suffered.  In
> particular, I don't "see" the difference between a_b and aB unless I pay
> attention, and even then it's hard to remember.  OTOH, my memory for
> generalities ( things based on principles) seems pretty much as it has
> always been.
>
> So I find it easy to remember the names of all the iterators (they follow a
> common pattern), and if I'm not sure, I use typing completion.
>
> As I write this, I wonder whether the name c.find_iter() might be a better
> clue.  It doesn't actually return a proper iter, but does that matter?  In
> other words, find_h doesn't fit a pattern, so it's not going to so easy (for
> me) to remember.
>
> Comments?

I interpreted find_h as establishing a new family of functions.
...
Ah, I just updated the thread with Edward's latest comment, he
said better and sooner what I was writing.

>
> Edward
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to