I don’t think I’m complaining - I tried to make clear that my issue was I didn’t expect the behavior I got from view. And yes, I disagree - doesn’t mean I’m right.
I’ve been part of UI groups on many different software and I realize you can’t please everyone. One path is chosen that in the judgment of experienced people works best. Plone UI represents a lot of hard work and I think they’ve done a great job. Thanks. Period.
Thanks to you folks for pointing me to solutions - I appreciate that. Let’s let this rest is peace.
I’d only like now to focus on what I think is a bug in Dex. Note: as I remember this was confirmed a long time ago when I spoke with @cewing
On the issue of fieldsets in Dex, I believe it is a bug. If you agree (see below) I’d be glad to file a bug at: https://github.com/plone/plone.dexterity/issues
What I did: in dex: create new CT; create fieldset; click on tab for this new FS and add field. Repeat for second FS. This is the schema: Note both FS are empty. Please let me know if I am missing something or if this is a bug and confirm the above link is proper place to put bug report.
Also, attached is what a new instance of the CT looks like
<?xml version="1.0" encoding="utf-8"?>
<model xmlns:form="http://namespaces.plone.org/supermodel/form" xmlns:i18n="http://xml.zope.org/namespaces/i18n" xmlns:lingua="http://namespaces.plone.org/supermodel/lingua" xmlns:marshal="http://namespaces.plone.org/supermodel/marshal" xmlns:security="http://namespaces.plone.org/supermodel/security" xmlns:users="http://namespaces.plone.org/supermodel/users" xmlns="http://namespaces.plone.org/supermodel/schema">
<field name="field_added_to_fs_1" type="zope.schema.TextLine">
<description>this should be inside FS 1</description>
<title>field added to FS 1</title>
<field name="inside_fs_2" type="zope.schema.TextLine">
<title>inside FS 2</title>
<fieldset name="field_set_one" label="field set one" description="this is a fieldset" />
<fieldset name="fieldset_2" label="fieldset 2" />