Difference between revisions of "User:TsT"
(first shot) |
|||
| Line 5: | Line 5: | ||
The complet list : | The complet list : | ||
| − | - jailfunc lib | + | - jailfunc (lib) |
Goal: be able to allow/deny access of library or function (like os, io, require ...) | Goal: be able to allow/deny access of library or function (like os, io, require ...) | ||
| − | - jailfs lib / jailnet lib | + | - jailfs (lib) / jailnet (lib) |
Goal: be able to filter that is allowed to read (and write) on file system access, but maybe also over the network connection (filter the ip:port like simple firewall) | Goal: be able to filter that is allowed to read (and write) on file system access, but maybe also over the network connection (filter the ip:port like simple firewall) | ||
| − | - gameconf lib | + | - gameconf (lib) |
Goal: having easy function to manage game settings | Goal: having easy function to manage game settings | ||
(FIXME: I don't remember what exactly but I have part of code about that...) | (FIXME: I don't remember what exactly but I have part of code about that...) | ||
| Line 18: | Line 18: | ||
Goal: always keep control! be able to choose and enforce my user settings, | Goal: always keep control! be able to choose and enforce my user settings, | ||
allow or deny change on resolution/input grabbing/window-or-full-screen mode/no sound/etc. | allow or deny change on resolution/input grabbing/window-or-full-screen mode/no sound/etc. | ||
| + | |||
| + | - keyboard layout | ||
| + | |||
| + | - input layer (lib) | ||
| + | Goal: be able to | ||
| + | |||
| + | - love-master | ||
| + | Goal: have a magic key (or sequence) to pause the game and got back to a safe environnement (like the love console?) to be able do ... what you want. | ||
| + | For exemple: | ||
| + | - debugging (see memory usage, variable values, ...) | ||
| + | - profiling (see stats about most called function) | ||
| + | - access to the safe menu to configure (simple-firewall, jailfs or others settings) | ||
| + | |||
| + | |||
| + | Others idea projects : | ||
| + | - multilove (lib) | ||
| + | Goal: be able to run multiple (windowed) love program and link them together. | ||
| + | Goal: be able to link (over network/LUBE?) multiple love program and share actions. | ||
Revision as of 12:13, 1 April 2011
Start playing with löve in 2009 (v0.5.0) Is back in 2011 on löve 0.7.1.
Projects is to rewrite my "jail" project (see [love-master project (jail, ...)]) The complet list :
- jailfunc (lib) Goal: be able to allow/deny access of library or function (like os, io, require ...)
- jailfs (lib) / jailnet (lib) Goal: be able to filter that is allowed to read (and write) on file system access, but maybe also over the network connection (filter the ip:port like simple firewall)
- gameconf (lib) Goal: having easy function to manage game settings (FIXME: I don't remember what exactly but I have part of code about that...)
- settings enforcer (lib) Goal: always keep control! be able to choose and enforce my user settings, allow or deny change on resolution/input grabbing/window-or-full-screen mode/no sound/etc.
- keyboard layout
- input layer (lib) Goal: be able to
- love-master Goal: have a magic key (or sequence) to pause the game and got back to a safe environnement (like the love console?) to be able do ... what you want. For exemple: - debugging (see memory usage, variable values, ...) - profiling (see stats about most called function) - access to the safe menu to configure (simple-firewall, jailfs or others settings)
Others idea projects :
- multilove (lib)
Goal: be able to run multiple (windowed) love program and link them together.
Goal: be able to link (over network/LUBE?) multiple love program and share actions.
