On Wed, Nov 5, 2008 at 5:56 PM, Edward K. Ream <[EMAIL PROTECTED]> wrote:
>> I think of a project as a set of files which have relationships with each >> other, > and an associated workflow. A 'project import' definition would not only > import > the files, but provide tools to mitigate the complexity of the workflow. > > I think of a project as a .leo file. I think of "project import" as something that is done via %lshadow in ileo and that one script in the wiki. This is of course trivial to implement - show a "file open" dialog, and create the shadow nodes recursively. Add a file name filter query for good measure. We will probably need the md5 cache before that, otherwise those large projects that are easy to import take ages to load ;-) -- Ville M. Vainio http://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
