the first steps are done.
--> the core has some ew methods, exc. to call another module out of an module, ...
--> the frst two modules file_exists and file_read are developed both used by module tag_parse and at a farmer point by xml_parse
-->then we will be able to start with xml-baes registry
-->now it's really buggy handle with the modules and it was not the intend of this idea in the form exists right now
first module methods are available
--> static class MODULE::xyz()
--> package() --> namespace for current module
--> requiremod() --> module can be only used by being nested into modules stated as attributes --> i.e. package("PRINT")
--> import() --> import classes from other modules into this one and can be used normally
-->visible("FILE") --> the arrangement of this module in the hole module tree, i.e. this module will be placed after module FILE as sub-module
-->version() --> Version info of this module
-->author() --> author
-->description() --> additional infos... read more
i made brainstorming to find a title for the internal language of webdev used to put the modules together to build useable templates or web-applications --> to get a functionality working
--> here is the name --> SHT (Small Helpful Tags)
--> why this name? the name give the answer
--> SHT is a tag-based language similar to XML, HTML, ... . One tag represents one Module, one functionality. It's possible to combine several tags or functionalitys. So you can easily give an input HTML field a javascript functionality... read more
the whole application should to be completely modular even at the starting point. So it's neccessary to develop all features in modules. so we want to start to create a xml module which will be able to interpret and store data in xml format into the internal registry holding the infos for all modules being installed at the system. going this way we will be able to seperate the data logic away from the backend we used. at a farmer time maybe the registry can be simply import into a database based structure that completely differs from our first thought of a xml document.