Adapt to refactoring of nimib

[HugoGranstrom]

@pietroppeter It's long due but I have managed to rewrite a large part of nimiSlides to use the new nimib version. The ones we were most interested in was slide and fragmentCore as they are now container blocks.

Everything is not ported yet, there is still a lot of nbRawHtml sprinkled around everywhere. And for good reason, it's so damn easy and convenient 😅. So I'm not sure if it's worth the effort to define a new block type for each one. Take for example:

template column*(bodyInner: untyped) =
  nbRawHtml: "<div>"
  bodyInner
  nbRawHtml: "</div>"

It would translate to this code roughly:

newNbBlock(NbColumn of NbContainer):
  toHtml:
    withNewLines:
      "<div>"
      nbContainerToHtml(blk, nb)
      "</div>"

template column*(bodyInner: untyped) =
  let blk = newNbColumn()
  nb.add blk

It is not that much code, but there are a few of them. I mean, I should port them over but I'm just lazy. Can you remind me of a good reason why I should do it and then I'll do it? 🤣

[pietroppeter]

Great news!

I do not think I have many good reasons and I think it is fine if you keep some of them sprinkled around.

One weak reason is that with nbRawHtml you increase the number of templates and blocks used (wrapping the container is a +1 over n contained, wrapping a standard block is a +2 on top of 1).

On the specific of that column template, it seems it could be an alias for a NbDiv that could be part of nimib itself (with maybe also class and style fields that you can customize in the body with `non.blk.class = "my class" or similar?).

[HugoGranstrom]

One weak reason is that with nbRawHtml you increase the number of templates and blocks used (wrapping the container is a +1 over n contained, wrapping a standard block is a +2 on top of 1).

That's a fair point. The reason we wanted to reduce them was that we were hitting the maximum global variables limit with large presentations. But that shouldn't be a problem anymore as most blocks have a func implementation and doesn't define any global variables:

func rawHtml*(nb: var Nb, content: string) =
  let blk = newNbRawHtml(html = content)
  nb.add blk

template nbRawHtml*(content: string) =
  nb.rawHtml(content)

Previously all blocks defined multiple global variables. So we should be much better off now. It would still be a bit slower to build more blocks, but the most important ones that are used everywhere (slide, fragment) have been ported so it should be less noticeable now.

On the specific of that column template, it seems it could be an alias for a NbDiv that could be part of nimib itself (with maybe also class and style fields that you can customize in the body with `non.blk.class = "my class" or similar?).

That is a great idea! I'll implement it right away! That could be useful in all sorts of situations :O

[HugoGranstrom]

After a long fight with the new nimble workflow I have finally made the CI work again! 🥳 So unless the CI goes red for some reason I'll merge this and announce it on the forum (along with a link to the NimConf slides in the correct thread)

[pietroppeter]

Wow that sequence of CI fighting commits looks intense. Thanks for the persistence!