2013/12/19 Damien Cassou <damien.cassou@gmail.com>

On Thu, Dec 19, 2013 at 10:37 AM, Sergi Reyner <sergi.reyner@gmail.com> wrote:
You mean how to write a bot with Chromia?

If you do it with Chromia, many details (such as network stuffs I guess) won't be shown. But this gives you the possibility to implement a great bot.

If you do it without Chromia, you can show all the details so that the reader learns a lot of Pharo.

That�s precisely why I asked, and why I said that first I�d like to modularise it as I mentioned in my original mail. That way I can first explain how the framework is built, so I can transmit the benefits of building it this way instead of mashing it up all together (which is how I began :D).

Then I can explain how to use that framework to write your own bot, which again makes the benefits stand out.

At the moment I�m going over some decisions that I feel can be improved. From the top of my head:

- Class names are awfully chosen. Besides almost every one of them having IRC as a "namespace" prefix, some like IRCUser don�t convey enough meaning.
- IRCConfiguration could be replaced by a dictionary since it�s nothing more than a bunch of data. But the, on the other hand, it could encapsulate validation on the settings to say something.
- Is PetitParser overkill for the time of parsing required? Are regular expressions a better fit for this task?
- Do I keep the Glamour browsers? I�m rather partial to them :D


Both are fine I would say. If you decide to write a tutorial, we could integrate it in the next book:
https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSuccessfulBuild/artifact/
�
Oh. Wow.

Cheers,
Sergi