I understand how columns and rows work but I cant figure out how Spec works with Morphs.

I took a look at CheckBoxExample but it completely jammed my brain how complex it looks.

First of all defaultSpec2 is what ? and whats the diffirence with defaultSpec ?��

Dont know about you but I don't like neither name defaultSpec and defaultSpec2 , I would have chosen a name like layout or something that makes sense.��

also why we need to initializeWidgets when we already define their order in defaultSpec ? Why cant Spec initialise those widgets by itself ?

Is it really necessary for each element of the gui to be defined as a getter method ? Why not just put everything to a dictionary and make a getter for that dictionary ? It would make a complex Spec gui a nightmare to browser and leads to braking it up to more classes which will still make it a mess to browse.��

I see also ��a container defined in there , I assume it has something to do with the morphs.��

I took also a look at documentation at Pharo for the Enterprise and it has a section for building widgets but it looks too much work to add just a few morph to a Spec gui.��

I wanted to make the gui for Nireas with Spec and I like some of its design but overall it has been way more struggle than working with Morphic.��

I know I have complained about Spec before and sorry if I sound like a broken tape but making guis in heavily gui based environment like Pharo should not be so hard.��

I dont have a problem failing back to Morphic but since I see so many people praise Spec I keep wondering if I approach this the wrong way and things are much more elegant and easy than they look.��