libvaxis/src/main.zig

const std = @import("std");

pub const Vaxis = @import("vaxis.zig").Vaxis;
pub const Options = @import("Options.zig");

pub const Key = @import("Key.zig");
pub const Cell = @import("Cell.zig");
pub const Image = @import("Image.zig");
pub const Mouse = @import("Mouse.zig");
pub const Winsize = @import("Tty.zig").Winsize;

pub const widgets = @import("widgets.zig");

/// Initialize a Vaxis application.
pub fn init(comptime Event: type, opts: Options) !Vaxis(Event) {
    return Vaxis(Event).init(opts);
}

test {
    std.testing.refAllDecls(@This());
}
refactor: make code more idiomatic - Added standard .gitattributes file for Zig projects. - Reworked build.zig a little, hopefully it's a bit clearer. Also, now zig build will run all steps. - outer: while in examples was redundant since there's only one loop to break from. switch expressions don't allow breaking from them, so breaking is only for loops, i.e. while and for. - When returning a struct instance from a function, the compiler infers the return type from function signature, so instead of return MyType{...}; , it's more idiomatic to write return .{...};. - Logging adds a new line by default, so you don't usually need to write \n like here: log.debug("event: {}\r\n", .{event});. 2024-02-11 19:59:33 +01:00			`const std = @import("std");`

rename project libvaxis This is so similar to my vaxis project for go that we'll retain the name here as well. The two can keep similar APIs and feature sets, but are used in different languages. Maybe someday libvaxis will export a C api for even broader use Signed-off-by: Tim Culverhouse <tim@timculverhouse.com> 2024-01-19 17:13:32 +01:00			`pub const Vaxis = @import("vaxis.zig").Vaxis;`
			`pub const Options = @import("Options.zig");`

chore: refactor build Signed-off-by: Tim Culverhouse <tim@timculverhouse.com> 2024-01-19 03:17:26 +01:00			`pub const Key = @import("Key.zig");`
refactor: make code more idiomatic - Added standard .gitattributes file for Zig projects. - Reworked build.zig a little, hopefully it's a bit clearer. Also, now zig build will run all steps. - outer: while in examples was redundant since there's only one loop to break from. switch expressions don't allow breaking from them, so breaking is only for loops, i.e. while and for. - When returning a struct instance from a function, the compiler infers the return type from function signature, so instead of return MyType{...}; , it's more idiomatic to write return .{...};. - Logging adds a new line by default, so you don't usually need to write \n like here: log.debug("event: {}\r\n", .{event});. 2024-02-11 19:59:33 +01:00			`pub const Cell = @import("Cell.zig");`
			`pub const Image = @import("Image.zig");`
mouse: implement mouse parsing and events Signed-off-by: Tim Culverhouse <tim@timculverhouse.com> 2024-01-31 19:50:00 +01:00			`pub const Mouse = @import("Mouse.zig");`
screen: implement initial screen data structure Signed-off-by: Tim Culverhouse <tim@timculverhouse.com> 2024-01-19 06:17:57 +01:00			`pub const Winsize = @import("Tty.zig").Winsize;`
initial commit Signed-off-by: Tim Culverhouse <tim@timculverhouse.com> 2024-01-18 04:52:33 +01:00
refactor: make code more idiomatic - Added standard .gitattributes file for Zig projects. - Reworked build.zig a little, hopefully it's a bit clearer. Also, now zig build will run all steps. - outer: while in examples was redundant since there's only one loop to break from. switch expressions don't allow breaking from them, so breaking is only for loops, i.e. while and for. - When returning a struct instance from a function, the compiler infers the return type from function signature, so instead of return MyType{...}; , it's more idiomatic to write return .{...};. - Logging adds a new line by default, so you don't usually need to write \n like here: log.debug("event: {}\r\n", .{event});. 2024-02-11 19:59:33 +01:00			`pub const widgets = @import("widgets.zig");`
image: implement transmitting images Signed-off-by: Tim Culverhouse <tim@timculverhouse.com> 2024-01-30 20:30:36 +01:00
rename project libvaxis This is so similar to my vaxis project for go that we'll retain the name here as well. The two can keep similar APIs and feature sets, but are used in different languages. Maybe someday libvaxis will export a C api for even broader use Signed-off-by: Tim Culverhouse <tim@timculverhouse.com> 2024-01-19 17:13:32 +01:00			`/// Initialize a Vaxis application.`
refactor: make code more idiomatic - Added standard .gitattributes file for Zig projects. - Reworked build.zig a little, hopefully it's a bit clearer. Also, now zig build will run all steps. - outer: while in examples was redundant since there's only one loop to break from. switch expressions don't allow breaking from them, so breaking is only for loops, i.e. while and for. - When returning a struct instance from a function, the compiler infers the return type from function signature, so instead of return MyType{...}; , it's more idiomatic to write return .{...};. - Logging adds a new line by default, so you don't usually need to write \n like here: log.debug("event: {}\r\n", .{event});. 2024-02-11 19:59:33 +01:00			`pub fn init(comptime Event: type, opts: Options) !Vaxis(Event) {`
			`return Vaxis(Event).init(opts);`
rename project libvaxis This is so similar to my vaxis project for go that we'll retain the name here as well. The two can keep similar APIs and feature sets, but are used in different languages. Maybe someday libvaxis will export a C api for even broader use Signed-off-by: Tim Culverhouse <tim@timculverhouse.com> 2024-01-19 17:13:32 +01:00			`}`

chore: refactor build Signed-off-by: Tim Culverhouse <tim@timculverhouse.com> 2024-01-19 03:17:26 +01:00			`test {`
refactor: make code more idiomatic - Added standard .gitattributes file for Zig projects. - Reworked build.zig a little, hopefully it's a bit clearer. Also, now zig build will run all steps. - outer: while in examples was redundant since there's only one loop to break from. switch expressions don't allow breaking from them, so breaking is only for loops, i.e. while and for. - When returning a struct instance from a function, the compiler infers the return type from function signature, so instead of return MyType{...}; , it's more idiomatic to write return .{...};. - Logging adds a new line by default, so you don't usually need to write \n like here: log.debug("event: {}\r\n", .{event});. 2024-02-11 19:59:33 +01:00			`std.testing.refAllDecls(@This());`
initial commit Signed-off-by: Tim Culverhouse <tim@timculverhouse.com> 2024-01-18 04:52:33 +01:00			`}`