On Wednesday, September 21, 2016 at 11:11:06 AM UTC-5, tfer wrote:
There are always request for new importers or changes to existing
> importers, few people other than Edward have wrapped their mind around how
> to do this for themselves.
>
The new javascript importer points the way to a simp
On Friday, September 23, 2016 at 12:53:46 PM UTC-5, Edward K. Ream wrote:
>
> On Wednesday, September 21, 2016 at 11:11:06 AM UTC-5, tfer wrote:
>>
>> There are always request for new importers or changes to existing
>> importers, few people other than Edward have wrapped their mind around how
>>
On Wednesday, September 21, 2016 at 11:11:06 AM UTC-5, tfer wrote:
>
> There are always request for new importers or changes to existing
> importers, few people other than Edward have wrapped their mind around how
> to do this for themselves. This is a proposal to make this easier for
> people
On Thursday, September 22, 2016 at 6:30:04 AM UTC-5, Edward K. Ream wrote:
> To summarize, your proposal amounts to a request to redesign or refactor
basescanner.py.
In fact, the BaseScanner code already has three phases, as shown by the
tree structure of the BaseScanner class's code. The top l
On Wed, Sep 21, 2016 at 11:11 AM, 'tfer' via leo-editor <
leo-editor@googlegroups.com> wrote:
There are always request for new importers or changes to existing
> importers, few people other than Edward have wrapped their mind around how
> to do this for themselves. This is a proposal to make
There are always request for new importers or changes to existing
importers, few people other than Edward have wrapped their mind around how
to do this for themselves. This is a proposal to make this easier for
people to create their own importers or easily customize any importer to
create nod
