x4js 2.3.9 → 2.3.11

package/src/components/textedit/textedit.ts

@@ -15,10 +15,10 @@
  **/
 
 //import { EventCallback } from '../../core/core_events';
-import { Component, makeUniqueComponentId } from '../../core/component';
+import { Component, ComponentEvents, makeUniqueComponentId } from '../../core/component';
 import { class_ns, UnsafeHtml } from '../../core/core_tools';
 
-import { HBox } from '../boxes/boxes';
+import { BoxProps, HBox } from '../boxes/boxes';
 import { DateProps, Input, InputProps, NumberProps, TextInputProps, TimeProps } from "../input/input"
 import { Label } from '../label/label';
 
@@ -32,7 +32,7 @@ import "./textedit.module.scss";
 
 type TextEditInputs = TextInputProps | NumberProps | DateProps | TimeProps;
 
-interface TextEditBase {
+export interface TextEditBase {
 	label: string | UnsafeHtml;
 	labelWidth?: number;
 	inputWidth?: number;		
@@ -82,7 +82,7 @@ interface TextEditProps extends InputProps {
  */
 
 @class_ns( "x4" )
-export class TextEdit extends HBox {
+export class TextEdit<E extends ComponentEvents = ComponentEvents> extends HBox<BoxProps,E> {
 
 	private input: Input;
 

package/src/core/core_application.ts

@@ -130,6 +130,7 @@ export class Application<E extends ApplicationEvents = ApplicationEvents> extend
 			const ev = document.querySelector( mountPoint );
 			if( ev ) {
 				ev.appendChild( this.mainview.dom );
+				this.mounted = true;
 			}
 		}
 	}

package/src/core/core_svg.ts

@@ -14,7 +14,7 @@
  * that can be found in the LICENSE file or at https://opensource.org/licenses/MIT.
  **/
 
-import { Component, ComponentProps } from './component';
+import { Component, ComponentEvents, ComponentProps } from './component';
 import { isUnitLess } from "./core_styles";
 import { DOMEventHandler, GlobalDOMEvents, addEvent } from './core_dom';
 import { isNumber, isString, sanitizeHtml } from './core_tools';
@@ -1004,7 +1004,7 @@ export interface SvgProps extends ComponentProps {
  * It extends `Component` and provides methods for setting SVG content.
  */
 
-export class SvgComponent<P extends SvgProps = SvgProps> extends Component<P> {
+export class SvgComponent<P extends SvgProps = SvgProps, E extends ComponentEvents = ComponentEvents> extends Component<P,E> {
 
 	/**
 	 * Creates an instance of `SvgComponent`.

package/readme.npm.md

@@ -1,248 +0,0 @@
-# x4js
-
-**A TypeScript framework for building applications, not markup.**
-
-x4js is designed for rich web and desktop applications: business software, industrial interfaces, dashboards, data-heavy tools and desktop-like applications.
-
-It uses persistent TypeScript objects associated with the real DOM. No virtual DOM, no reconciliation layer, and no application architecture imposed by JSX.
-
-**TypeScript objects. JSX when it helps. Real DOM.**
-
-## Install
-
-```bash
-npm install x4js
-```
-
-## Quick start
-
-Create a project:
-
-```bash
-npx x4build create demo --type=html
-cd demo
-npm install
-```
-
-Run it in development mode with HMR:
-
-```bash
-npx x4build --watch --hmr --serve
-```
-
-## More than 50 UI components
-
-x4 includes a complete UI toolkit for building real applications.
-
-Among the available components:
-
-`Button`, `Input`, `TextEdit`, `TextArea`, `Checkbox`, `Radio`, `Switch`, `Select`, `Combobox`, `Slider`, `ColorPicker`, `Form`, `Dialog`, `Popup`, `Menu`, `Tabs`, `Gridview`, `Treeview`, `PropertyGrid`, `Spreadsheet`, `Calendar`, `Gauge`, `Progress`, `FileDrop`, `MonacoEditor`, layouts and more.
-
-The framework also provides:
-
-* drag & drop
-* SVG primitives and builder
-* routing
-* PDF generation
-* internationalization
-* data stores and views
-* application-wide events
-* persistence helpers
-* CSS infrastructure and theming
-
-## Easy to extend
-
-x4 components are ordinary TypeScript classes.
-
-```ts
-import { Component, ComponentProps } from 'x4js'
-
-interface StatusBadgeProps extends ComponentProps {
-    text: string
-}
-
-class StatusBadge extends Component<StatusBadgeProps> {
-    constructor(props: StatusBadgeProps) {
-        super(props)
-
-        this.setContent(props.text)
-    }
-}
-```
-
-Your own components use the same DOM, lifecycle and event model as the components provided by x4.
-
-Because x4 works with the real browser DOM, third-party UI libraries can also be integrated where they make sense. There is no separate plugin architecture to satisfy.
-
-## Real DOM
-
-A `Component` is a persistent TypeScript object associated with an actual DOM element.
-
-```ts
-const button = new Button({
-    label: 'Restart'
-})
-
-button.on('click', () => restartMachine())
-```
-
-The object remains alive for the lifetime of the component. You can keep references, call methods and listen to events directly.
-
-There is no virtual tree to rebuild or reconcile.
-
-## JSX is optional
-
-x4 supports JSX, but JSX is syntax — not the application architecture.
-
-Object API:
-
-```ts
-this.setContent([
-    new Label({
-        text: 'Temperature'
-    }),
-
-    new Gauge({
-        min: 0,
-        max: 100
-    })
-])
-```
-
-JSX:
-
-```tsx
-this.setContent(
-    <VBox>
-        <Label text="Temperature" />
-        <Gauge min={0} max={100} />
-    </VBox>
-)
-```
-
-Both create the same x4 Components and the same real DOM.
-
-Use whichever makes the code clearer.
-
-## Data-heavy applications
-
-x4 treats grids, trees, forms and structured data as first-class application concerns.
-
-`DataStore`, `DataView` and `Gridview` are designed to work together for tabular data:
-
-```ts
-const store = new DataStore({
-    model,
-    data
-})
-
-const grid = new Gridview({
-    store,
-    columns: [
-        { id: 'name', title: 'Name', width: 200 },
-        { id: 'age', title: 'Age', width: 80 }
-    ]
-})
-```
-
-Changes to the data are reflected by the components using it.
-
-## Routing
-
-```ts
-const router = new Router(true)
-
-router.get('/home', () => showHome())
-router.get('/device/:id', p => showDevice(p.id))
-
-router.init()
-```
-
-## Internationalization
-
-Internationalization support is built in.
-
-```ts
-createLanguage('de', 'en')
-addTranslation('de', translations)
-
-selectLanguage('de')
-```
-
-x4 includes French and English translations by default and allows applications to add their own languages.
-
-## SVG and PDF
-
-SVG is part of the framework surface through `SvgComponent` and `SvgBuilder`.
-
-PDF documents can be generated programmatically with `X4PDFBuilder`:
-
-```ts
-const pdf = new X4PDFBuilder()
-
-pdf.page(595, 842, page => {
-    // draw page
-})
-
-const data = pdf.build()
-```
-
-## CSS and themes
-
-x4 includes the CSS foundation used by its components.
-
-Applications can use the default styling, adapt it to their product, or provide their own CSS. Components expose their real DOM and CSS classes, so standard browser styling techniques remain available.
-
-No CSS-in-JS runtime is required.
-
-## HMR and development workflow
-
-The standard x4 build workflow supports watch mode, development serving and HMR:
-
-```bash
-x4build --watch --hmr --serve
-```
-
-Edit the application, save, see the result.
-
-## Ship only what you use
-
-The `x4js` npm package ships its TypeScript sources directly.
-
-Your application and x4 therefore participate in the same module graph, allowing the bundler to tree-shake unused code.
-
-Import a small part of x4 and the rest of the component library does not need to become part of your application bundle.
-
-## Web and desktop
-
-x4 targets both browser and desktop applications.
-
-The same component model can be used in the browser or inside a desktop wrapper such as Electron, Tauri or NW.js.
-
-## AI-friendly documentation
-
-x4 provides a generated `aicontext.md` containing the actual TypeScript API signatures.
-
-AI coding agents can also inspect the framework sources directly because they are distributed with the npm package:
-
-```text
-node_modules/x4js/src/
-```
-
-The goal is not to make x4 an “AI framework”.
-
-The goal is simpler: an explicit architecture and an API that are readable by humans and predictable for machines.
-
-## Philosophy
-
-x4 deliberately keeps its conceptual model small.
-
-Use TypeScript when TypeScript is enough.
-Use the browser when the browser is enough.
-Add an abstraction only when it solves a real problem.
-
-**Use the simplest tool that fits.**
-
----
-
-MIT License