v/vlib/vweb
Alexander Medvednikov 7adda3b71a vweb: fix get_cookie() 2019-12-08 01:48:49 +03:00
..
assets os: replace dir_exists with is_dir; file_exists() => exists() 2019-12-04 23:17:45 +03:00
tmpl check unused and unmodified vars in all modules, not just main 2019-12-06 18:43:56 +03:00
README.md readme: fix link to vweb example 2019-11-16 19:58:55 +03:00
vweb.v vweb: fix get_cookie() 2019-12-08 01:48:49 +03:00

README.md

This is pre-alpha software.

Lots of things are broken and not implemented yet in V and vweb.

There's no documentation yet, have a look at a simple example:

https://github.com/vlang/v/tree/master/examples/vweb/test_vweb_app.v

There's also the V forum: https://github.com/vlang/vorum

vorum.v contains all GET and POST actions.

pub fn (app mut App) index() {
	posts := app.find_all_posts()
	$vweb.html()
}

// TODO ['/post/:id/:title'] 
// TODO `fn (app App) post(id int)` 
pub fn (app App) post() {
	id := app.get_post_id() 
	post := app.retrieve_post(id) or {
		app.vweb.redirect('/') 
		return 
	}
	comments := app.find_comments(id)
	show_form := true 
	$vweb.html()
}

index.html is an example of the V template language:

@for post in posts 
	<div class=post>
		<a class=topic href="@post.url">@post.title</a> 
		<img class=comment-img> 
		<span class=nr-comments>@post.nr_comments</span> 
		<span class=time>@post.time</span>
	</div>
@end

$vweb.html() compiles an HTML template into V during compilation, and embeds the resulting code in current action.

That means that the template automatically has access to that action's entire environment.

Deploying vweb apps

Everything, including HTML templates, is in one binary file. That's all you need to deploy.