Go to file
kts 54c657aa60 Began implementing a centralized CSS file for colors and the like. Modules should not define major styles on their own, but rather extend the CSS defined in main.css with positional data and similar. The largest problem, however, is that elements such as input are multifunctional via their type property and cannot be easily defined in a simple and cross-browser manner. It may be prudent to generalize input elements' style, but add particular classes for types for the Module to use if need be. It may also be wise to enhance(hopefully not bloat) the rendering system so as to allow for module organization and the like. This may be as simple as allowing Modules to be added to other Modules as Submodules. Rendering - and likely processing - would then be called within the context of another Module, thereby allowing greater finesse in element positioning. 2014-05-24 18:35:02 -07:00
conf Began implementing a centralized CSS file for colors and the like. Modules should not define major styles on their own, but rather extend the CSS defined in main.css with positional data and similar. The largest problem, however, is that elements such as input are multifunctional via their type property and cannot be easily defined in a simple and cross-browser manner. It may be prudent to generalize input elements' style, but add particular classes for types for the Module to use if need be. It may also be wise to enhance(hopefully not bloat) the rendering system so as to allow for module organization and the like. This may be as simple as allowing Modules to be added to other Modules as Submodules. Rendering - and likely processing - would then be called within the context of another Module, thereby allowing greater finesse in element positioning. 2014-05-24 18:35:02 -07:00
modules Began implementing a centralized CSS file for colors and the like. Modules should not define major styles on their own, but rather extend the CSS defined in main.css with positional data and similar. The largest problem, however, is that elements such as input are multifunctional via their type property and cannot be easily defined in a simple and cross-browser manner. It may be prudent to generalize input elements' style, but add particular classes for types for the Module to use if need be. It may also be wise to enhance(hopefully not bloat) the rendering system so as to allow for module organization and the like. This may be as simple as allowing Modules to be added to other Modules as Submodules. Rendering - and likely processing - would then be called within the context of another Module, thereby allowing greater finesse in element positioning. 2014-05-24 18:35:02 -07:00
MediaServe.php Began implementing a centralized CSS file for colors and the like. Modules should not define major styles on their own, but rather extend the CSS defined in main.css with positional data and similar. The largest problem, however, is that elements such as input are multifunctional via their type property and cannot be easily defined in a simple and cross-browser manner. It may be prudent to generalize input elements' style, but add particular classes for types for the Module to use if need be. It may also be wise to enhance(hopefully not bloat) the rendering system so as to allow for module organization and the like. This may be as simple as allowing Modules to be added to other Modules as Submodules. Rendering - and likely processing - would then be called within the context of another Module, thereby allowing greater finesse in element positioning. 2014-05-24 18:35:02 -07:00
index.php Began implementing a centralized CSS file for colors and the like. Modules should not define major styles on their own, but rather extend the CSS defined in main.css with positional data and similar. The largest problem, however, is that elements such as input are multifunctional via their type property and cannot be easily defined in a simple and cross-browser manner. It may be prudent to generalize input elements' style, but add particular classes for types for the Module to use if need be. It may also be wise to enhance(hopefully not bloat) the rendering system so as to allow for module organization and the like. This may be as simple as allowing Modules to be added to other Modules as Submodules. Rendering - and likely processing - would then be called within the context of another Module, thereby allowing greater finesse in element positioning. 2014-05-24 18:35:02 -07:00
main.css Began implementing a centralized CSS file for colors and the like. Modules should not define major styles on their own, but rather extend the CSS defined in main.css with positional data and similar. The largest problem, however, is that elements such as input are multifunctional via their type property and cannot be easily defined in a simple and cross-browser manner. It may be prudent to generalize input elements' style, but add particular classes for types for the Module to use if need be. It may also be wise to enhance(hopefully not bloat) the rendering system so as to allow for module organization and the like. This may be as simple as allowing Modules to be added to other Modules as Submodules. Rendering - and likely processing - would then be called within the context of another Module, thereby allowing greater finesse in element positioning. 2014-05-24 18:35:02 -07:00
media Initial commit of kettek MediaServe. Contains basic framework and implementation. FileBrowser module fairly complete, much more to be added, including Playlist module and Player module. 2014-05-17 16:52:48 -07:00
sdb.ini Initial commit of kettek MediaServe. Contains basic framework and implementation. FileBrowser module fairly complete, much more to be added, including Playlist module and Player module. 2014-05-17 16:52:48 -07:00