urlysses
4d08c23f27
Add views + very basic templating support.
2017-02-20 17:16:05 -05:00
urlysses
f0cac5c8f2
Fix bug where repeat invocations of sourcedir returned different results (due to abuse of sourcefilename memore address)
2017-02-18 09:46:33 -05:00
urlysses
6310938b54
Add sourcedir for more reliable file paths
2017-02-17 22:46:43 -05:00
urlysses
1571064535
Add multi-file example
2017-02-17 09:10:35 -05:00
urlysses
a32c43b989
Basic query string handling.
2017-02-17 09:10:06 -05:00
urlysses
888cf5ba77
Put todo list somewhere easily accessed
2017-02-17 07:52:59 -05:00
urlysses
299eef6ecc
Add filetype syntax (register and find).
2017-02-16 23:03:37 -05:00
urlysses
11a53a7d14
Generalize header words and start implementing content-types based on extensions
2017-02-15 23:13:46 -05:00
urlysses
a9c21097b8
Move app demo to an examples dir
2017-02-15 12:23:28 -05:00
urlysses
2eef80dd5d
Implement basic file serving from public/
...
TODO:
+ set appropriate MIME types
2017-02-15 12:22:50 -05:00
urlysses
3a8b715b7b
Ignore .DS_Store
2017-02-15 12:21:34 -05:00
urlysses
b2926d10c2
Handle 404s more appropriately if a requested route fails
2017-02-14 21:50:02 -05:00
urlysses
a4e3aa169e
Add very basic GET support (route either resolves or doesn't)
...
TODO:
+ file-serving if no user-defined routes match. Search "public/" dir
unless otherwise specified by user.
+ query arguments
+ PUT, POST, DELETE
+ templating
+ fuzzy-/pattern-match-enabled user routes (e.g., /something/*/wildcard)?
2017-02-14 21:36:22 -05:00
urlysses
31311ee91c
Save user routing in a wordlist.
...
The aim is to try to avoid polluting the global wordlist with routing
functions.
The alternative would be to have users simply define words that match
their routes, e.g.:
```
: 1991/hi
( some definition of hi's handler )
;
```
I'm still not entirely convinced that the above method isn't a better
solution.
2017-02-13 22:34:57 -05:00
urlysses
f40f2d5630
Gotta start somewhere:
...
First, define a user-facing word that takes a port and subsequently
starts the server (using gforth's unix/socket.fs).
Second, start defining a user-facing word for specifing routes and their
handlers.
2017-02-11 22:16:52 -05:00
urlysses
1f528fa8f6
1991
2017-02-01 22:26:33 -05:00
