studio42gmbh / dl Goto Github PK

Currently the annotation export does not throw an exception when used on attributes in the module. This should not be possible

i.e.:

//... in module
int width @export : 640;
int height @export : 400;
//...

Allow to define a default attribute within a type that can then be used within assignments.

Needs to extend DLInstance to have a default attribute, add an annotation @default and extend the assignment handling in parser.

something like:

type H1 extends HTMLElement 
{
	String text @default: "";
}

Div myContent {
	H1 heading : "Welcome"; // <- Creates a new instance of H1 and assigns its text
	P description : "Little text \nwith multiple lines"; // <- Creates a new instance of P and assigns its text
}

This in combination with expressions & and | makes using masks easier.

There shall be data types like String which are "simple" types. And there are types having attributes, containing other elements, ... which are called "complex" types

This allows to create own DLType implementations and map them using extern type ...

It could be interesting to add namespaces for scoping types, instances, etc. in modules or across modules)

This is a fundamental extension and might not be in the scope of a Beta release.

something like:

namespace mqrc {

	type A 
	{
		String test;
	}
}

// ...

use mqrc;

A test { test : "aha"; }

unuse mqrc;

// or:

namespace mqrc {

	A test { test : "aha"; }

}

Currently the data types are not properly converted into the given generic target type see test:

Allow to define alternative types for an attribute within a complex type (sort of like a union)

something like:

type GPImage extends Image { 
	Material|Shader|Texture material; // <- material can be one of the types Material, Shader or Texture
}

Use DLType.write, Use Stringhelper

It would be great to allow querying instances/attributes from a DLModule in a flexible and performant way a little like CSS.

This new keyword transform would allow to define an internal and external conversion between two types

It might be interesting to allow primitive typecasts in expressions.
like:

Integer t : 5 / ((int) 8.4 / 3.2 );

Analogous to disallowing to define types or annotations it should be possible to disallow requiring contents

The DefaultCore shall provide a DLType for maps. Best would be with generics support to allow filling lists from dl directly.

Analogous to type and annotation it would be good to allow definition of enums from an integration using:

extern enum <integration>;

The DefaultCore shall provide a DLType for lists. Best would be with generics support to allow filling lists from dl directly.

This might make working with DL in manual files much more convenient. On the other side it makes the whol DL more complex and error prone ...

// new - shorter and results in "native" boolean - also consider stativ vs. dynamic (with $refs) terms
boolean b : ($state & $state2) | (true != !$state3);
boolean b2 : 7 != 6;
boolean b3 : 7 != $val;
int i : 5 * 3 + 2;
int i2 : 5 * $val2 - 2;

// currently possible with DL - own type tree BoolT, Or, And, Bool, Not, Xor, True, False
BoolT b : Or {
And {
Bool { value : $state; }
Bool { value : $state2; }
}
Xor {
True {}
Not { value : $state3; }
}
};

// Or special Eval with subparser ... might also use ANTLR ...
Eval var : Eval { expr : "$0 != $1", data : $a, $b; };
Eval var : Eval { expr : "7 != $ref"; };

Finalize, test and create a release package 1.01

It would be cool if it was possible to combine annotations into a new annotation with boolean operations and parameter presets

something like:

annotation myKeyword(maxLength) (required & length(4, maxLength)) & !upperCase;

by that you could use annotations to build contracts from it.