a few suggestions

works on pagination as well…
You have to use the “post type” brick and check the “not affected” meaning, not affected by pagination… otherwise it tries to get content for second or what ever page of that Easy settings.. and if it does not find content on the particular page for the Easy setup there will be no output, naturally.

I’m not completely sure what you are talking about, but have you tried the classes in “general” top part of each easy. There you can setup the classes for surrounding divs, for the “wrapper” of the whole easy output and also each loop within the call.. The structure is same as it is common in 95% templates.
(HTML tags doesn’t matter that much as classes which you can define in css.)

check this out
http://2046.cz/easy/general

You can wrap taxonomies in div for sure.

I understand your reasons, but if I let user add this kind of value by them self the result will be highly vulnerable.

Easy is used mainly for people who do not know coding a lot.. and even If highly skilled person will use it, he/she can make simple typo and the result can be wrong right away.
Like you can type idv instead of div.. or you can misunderstand it and write the instead of html tag a class.. and suddenly the result will be completely wrong.

The way it is now is kind of bulletproof. You can’t brake the HTML DOM it self..it is always right. and so the only thing you have to care about is to tune up the css file. Based on the classes you use.

Plus, span, tab, td, and so on are not necessary as you can turn any div to any kind of span like element, or tab like element by CSS.
If you argue that there is no way how to define ID, well you’ll be right, but still it is not necessary in most cases. If you argue about the impossibility to use HTML5 elements such as head, article, section and so on, you’ll be right, but still the vulnerability would be far worst flaw than not being able to use your custom elements.

In cases where it makes sense like titles there is a possibility to choose h1-5. that surely makes sense from the basic SEO point of view

To summarize this topic.
Custom html tag will be highly dangerous to the result, and won’t be applied in Easy for the reasons I mentioned above.
If you need highly tuned up HTML DOMs you should code the result your self.
Easy should be as its name implies – “Easy”.
It is not a complex tool covering all possibilities.. It wouldn’t make sense anyway.. as in highly customized needs you need also highly customized code from many angles which cannot be done with a middle man.

to that custom html tag case.

Pablo Ray is right.. there can be a dropdown menu with possible HTML containers (but only one as there is no need to select before and after, both are the same 😉 and have to be).
.. but then, what types to allow? As “b, i, strong, h*, abbr,” .. makes no sense in the case of rich content, in those cases the “div” is much more on place. .. span makes sense only if the content is not too rich..These rules are not well known to many people, and so the html tags can be quickly misused.

Moreover look on the complete list of html tags http://www.w3schools.com/tags/
Do you really want to have them all there? Do you, really know what are they all for?

And the tables, they are completely out of scope. They are too complicated with all the th, tr, td… Build such structure would not be easy even with Easy. Same applies to ul, ol, li.

Premium or free – I agree, it might be useful in some case but I still it will do more harm then good.