♻️ Improve module naming and directory structure

[Glutexo]

All things Onigumo need to be inside the Onigumo namespace to avoid name clashes. The Mix project itself is Onigumo.MixProject. No submodules should pollute the global namespace. That results in the following steps:

• Move the Downloader module under a new Kernel namespace.
• Move the Hash module too into Onigumo.Kernel.
• Put the HTML module from Add parser of html links #87 into Onigumo.Spider.

[nappex]

There is a link to blog where a guy describes his opinion about files and modules naming conventions.

[Glutexo]

Regarding the Hash module, I am thinking of a Utilities subnamespace. Having the core three pillars (Downloader, Operator, Parser) separated from auxiliary modules seems elegant, but an overly complex structure brings its issues too. It would look like this:

• Onigumo.Kernel.Downloader, Onigumo.Kernel.Operator, Onigumo.Kernel.Parser, Onigumo.Kernel.Utilities.Hash or
• Onigumo.Kernel.Core.Downloader, Onigumo.Kernel.Core.Operator, and Onigumo.Kernel.Core.Parser, Onigumo.Kernel.Utilities.Hash. Kernel.Core sounds fishy: I’d rather see Onigumo.Onigumo.Core or Onigumo.Onigumo.Kernel.

Seeing it live, I find a flat structure less confusing: Onigumo.Kernel.Downloader, Onigumo.Kernel.Operator, Onigumo.Kernel.Parser, Onigumo.Kernel.Hash. We can revisit this when more modules are in place, but even with dozens of modules, a flat structure is still clear enough.

What do you think, @nappex?

[Glutexo]

Thanks for the blog link! It is a good reference, and I find the thoughts on naming the main file for a module with submodules inspiring!