On Sun, Mar 30, 2008 at 1:39 PM, Edward K. Ream <[EMAIL PROTECTED]> wrote:
the decision to ignore, as a matter of policy, how Komodo works, is likely > to be a most useful guide. Another guide presents itself: ignore gui considerations during initial experimentation. In other words, the essence of Komodo consists of: 1. The analysis of program libraries. The results are mostly unchanging .cix files. 2. The analysis of modules (blobs in Komodo terminology) and code fragments. 3. The computation of valid completions at a particular point of the text. Leo's task will be to cause Komodo to analyze text in Leo body text, and then to ask Komodo for possible completions. Test scripts can be do this easily without dealing with the (considerable) complications of presenting the completions to the user. So this is another good simplifying guide. 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 -~----------~----~----~----~------~----~------~--~---
