**D. Moonfire** @dmoonfire · Jun 18, 2018, 23:15

**D. Moonfire** @dmoonfire · Jun 18, 2018, 23:15

D. Moonfire @dmoonfire

Jun 18, 2018, 23:15

Author Intrusion Show more

So, not much work done because of picking up a kid, but I got some AI work done. Right now, it handles loading typesafe settings from the project YAML file and running plugins against files as they are loaded.

**D. Moonfire** @dmoonfire · Jun 19, 2018, 03:45

**D. Moonfire** @dmoonfire · Jun 19, 2018, 03:45

Jun 19, 2018, 03:45

D. Moonfire @dmoonfire

Author Intrusion Show more

I find it interesting trying to get a typesafe collection of objects. For AI, I wanted to have each plugin be able to define its own properties.

I got that working this evening, which means I'm closer to producing something usable.

It also can pull out YAML metadata from the Markdown files, which is something I use rather heavily in my own writing.

**D. Moonfire** @dmoonfire · 2018-06-19T06:04:52Z

D. Moonfire @dmoonfire

Author Intrusion Show more

And the final bit of coding today. I started working on the XPath-based splitter. This is what is going to break apart a chapter into paragraphs, lines, and tokens/words.

That way, an echo plugin can search for `//token[length() > 3]` to get all tokens over three characters long.

`//para//token[index() = 1]` for the first word of every paragraph. I want to use that to make sure no paragraph starts with the same word.

I figured I'm 2-4 days from seeing if this POC works.

Jun 19, 2018, 06:04 · Web · 0 · 0

**D. Moonfire** @dmoonfire · Jun 19, 2018, 06:08

**D. Moonfire** @dmoonfire · Jun 19, 2018, 06:08

Jun 19, 2018, 06:08

D. Moonfire @dmoonfire

Author Intrusion Show more

Most of these plugins will have a "scope" which says how to break up the code. The default will be "content" which is actually `//file[has-class('content']` to only analyze chapters.

So, the echo plugins would only process per chapter.

If one used `/project` for the scope, then the echo would consider the last paragraphs of the previous chapter instead of only per-file checking.

This will also let the frequency plugins look for overuse of a word per file or per project.

**D. Moonfire** @dmoonfire · Jun 19, 2018, 06:10

**D. Moonfire** @dmoonfire · Jun 19, 2018, 06:10

Jun 19, 2018, 06:10

D. Moonfire @dmoonfire

Author Intrusion Show more

I'll admit, I don't have hopes of getting past certain milestones on this iteration of AI. I think I've written and rewritten this at least nine times over the last eight years, each time find a new and interesting way it failed.

I have hopes it will finally get to be usable and extendable, but it also means I have to not get distracted for another 1-2 months. Otherwise I'll lose it and end up starting over again.

Getting to a point where others can ooh and aah over it helps.