First implementation

[ngonzalezpazFC]

Summary

• Add ToggleButton component extending AbstractSinglePropertyField<ToggleButton, Boolean>,
  implementing HasSize, HasComponents, HasLabel, HasAriaLabel, HasTooltip, and
  HasThemeVariant<ToggleButtonVariant>
• Add ToggleButtonVariant enum with color variants (PRIMARY, SUCCESS, WARNING,
  ERROR, CONTRAST), size variants (SMALL, MEDIUM, LARGE), and touch variant (LONGSWIPE)
• Implement fc-toggle-button LitElement web component with shadow DOM, Lumo token
  integration, and symmetric active-state animations for all size variants
• Add LONGSWIPE variant producing a wider switch track optimized for touch; combinable with
  size variants (LONGSWIPE + SMALL/MEDIUM/LARGE)
• Add mobile swipe gesture support: horizontal drag moves the slider in real time; releasing
  past the 50% threshold snaps to the new state with a smooth CSS transition
• Expose fluent API: setLeftLabel, setRightLabel, setLeftIcon, setRightIcon,
  setItemLabelGenerator, withHighlightLabel, withoutHighlightLabel, withIconsInside,
  withIconsOutside
• Label highlighting respects the active color variant: the active-side label uses the color
  of the SUCCESS, WARNING, ERROR, or CONTRAST variant instead of always defaulting to
  primary
• withIconsInside() swaps the default layout to [label] [icon] [switch] [icon] [label],
  placing icons adjacent to the switch and labels on the outer edges
• Add tabbed demo with three views: Labels & Icons, Theme Variants, and Events & Accessibility
• Migrate all classes from the template package to com.flowingcode.vaadin.addons.togglebutton
• Update pom.xml name and description per AddonsInternal guidelines
• Update README.md with correct badges, links, features list, and Getting Started examples

Test plan

• Run mvn clean install — build passes
• Run mvn clean install jetty:run and verify all three demo tabs render correctly
• Verify toggle animations are symmetric for all size variants (small, medium, large)
• Verify withHighlightLabel() highlights the active side label
• Verify theme variants apply correct colors and sizes
• Verify disabled and read-only states behave correctly
• Run mvn test
• Integration tests run on CI (require Vaadin TestBench license)

[ngonzalezpazFC]

In the v25 profile, please add the jakarta.servlet-api dependency (as done in AddonStarter24). Vaadin 25 uses Jakarta Servlet, so the javax.servlet:javax.servlet-api declared in the main dependencies won't be compatible when building with -Pv25.

<profile>
    <id>v25</id>
    <dependencies>
        <dependency>
            <groupId>com.vaadin</groupId>
            <artifactId>vaadin-dev</artifactId>
            <optional>true</optional>
        </dependency>
        <dependency>
            <groupId>jakarta.servlet</groupId>
            <artifactId>jakarta.servlet-api</artifactId>
            <version>6.1.0</version>
            <scope>test</scope>
        </dependency>
    </dependencies>
</profile>

411c095

[javier-godoy]

See comments above.

[ngonzalezpazFC]

Some comments about read-only styles:

• border shoud be thinner and use dashed intead of dotted
• background should be transparent not grey (grey gives the impresion of disabled)
  Check how checkbox are styled on read-only mode https://vaadin.com/docs/next/components/checkbox#read-only. This component should be similar.

a451e6a

[javier-godoy]

Agree with #1 (comment)

[ngonzalezpazFC]

Agree with #1 (comment)

Fixed