Skip to content

Commit

Permalink
Prep for release
Browse files Browse the repository at this point in the history
  • Loading branch information
jhgarner committed Apr 2, 2020
1 parent ed1042f commit bff202f
Show file tree
Hide file tree
Showing 4 changed files with 161 additions and 168 deletions.
63 changes: 0 additions & 63 deletions config/config.dhall.99

This file was deleted.

4 changes: 0 additions & 4 deletions config/startup.sh
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,3 @@ compton &
dunst &
/home/jack/.fehbg &
(sleep 1 && polybar example &> /home/jack/polybar.txt) &

# echo $DISPLAY > /home/jack/5.txt
# /home/jack/.local/bin/neXtWM-exe 1 &> /home/jack/.xtest.txt
#echo 6 > /home/jack/5.txt
41 changes: 25 additions & 16 deletions xest-site/home.rst
Original file line number Diff line number Diff line change
Expand Up @@ -21,44 +21,53 @@ Imagine you have two projects you're working on. One of them is a
research paper and the other is some kind of coding project. Normally, these two
projects will be hard to organize on your desktop.

For the research papaer, maybe you have a workspace designated to finding
For the research paper, maybe you have a workspace designated to finding
sources in your web browser and a workspace with LibreOffice open.

For the programming project, you might need a workspace with your browser open with documentation,
a workspace with you text editor, and a workspace with a couple of terminals for
compiling or testing.
compiling and testing.

The question quickly becomes how to organize the two projects. Do you put the
research workspaces before or after the project workspaces? What do you do if
you need another workspace for one of them? Is moving between everything easy?
Is it easier just to close everything related to one project while you work on
another?

Xest's solution to this problem is nested workspaces. At the top level, you have
two workspaces open: one for the research paper and one for the programming. Inside
of those, you have workspaces for each project. You can now pretend like only
one of them exists at a time making it easier to work without distractions. You
can also make better use of muscle memory. Your web browser can always be on the
first workspace no matter what you're working on.
A solution to this problem is nested workspaces. At the top level, you have
two workspaces open: one for the research paper and one for the programming.
Inside of those, you have workspaces for each project. You can now pretend like
only one of the projects exists at a time making it easier to work without
distractions. You can also make better use of muscle memory. Your web browser
can always be on the first workspace no matter what you're working on.

Although desktop environments like Plasma offer nested workspaces built in, Xest
offers something more generic with its tree structure. In theory, you can nest
workspaces as deep as you want in Xest and you can easily move entire desktops
around.

How stable is Xest?
===================

Although I am currently using it pretty much full time, there are still bugs and
changes to be made. I am still not sold on the primitive operations currently
available for moving around the desktop so those are likely to change. If you
have ideas, I would be excited to hear them.
changes to be made.

I try to fix as many bugs as I can, but I can't hit every possible use
case. If Xest crashes, every program you had running will crash as well which
could mean losing work. Make sure to save often!
could mean losing work. Make sure to save often! If Xest crashes, check out the
various files with "xest" in the name in your "/tmp/" directory.

I want to try it out!
=====================

You can clone Xest from https://github.com/jhgarner/Xest-Window-Manager and run
the install.sh file to get going. You will need to install Haskell's Stack build
tool before installing since I have now idea how universal the precompiled files
are.
If you're using arch, check out the package in the release section of the Github
project. You can install it using "pacman -U <path to tar.gz file>" Once you do
that, follow the instructions in the user guide.

If you want to run Xest from source, clone
https://github.com/jhgarner/Xest-Window-Manager and install nix. The stack build
tool should make the binary. For actually creating the menus in your display
manager, more work will be needed. Look at the Arch package and try to get the
non-binary files into the right places.

Check out the other pages on this site for information on using Xest.
Loading

0 comments on commit bff202f

Please sign in to comment.