rushilwiz/thesis
1
0
Fork 0
mirror of https://github.com/afkomputer/thesis.git synced 2025-04-03 19:00:17 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

initial commit

Browse Source
This commit is contained in:
Rushil Umaretiya 2023-05-22 09:07:08 -04:00
commit fb6eb3fc8b
No known key found for this signature in database
GPG Key ID: 4E8FAF9C926AF959
7 changed files with 1682 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

976
ieeetr.bst Normal file
View File

@ -0,0 +1,976 @@
% Copyright (C) 1985, 1988, 2010 Howard Trickey and Oren Patashnik.
% Unlimited copying and redistribution of this file are permitted as long as
% it is unmodified. Modifications (and redistribution of modified versions)
% are also permitted, but only if the resulting file is renamed.
%
% IEEE Transactions bibliography style (8-Dec-10 version)
% numeric labels, order-of-reference, IEEE abbreviations,
% quotes around article titles, commas separate all fields
% except after book titles and before "notes". Otherwise,
% much like the "plain" family, from which this is adapted.
%
% History
% 9/30/85 (HWT) Original version, by Howard Trickey.
% 1/29/88 (OP&HWT) Updated for BibTeX version 0.99a, Oren Patashnik;
% THIS `ieeetr' VERSION DOES NOT WORK WITH BIBTEX 0.98i.
% 12/ 8/10 (OP&HWT) Clarify license.
ENTRY
{ address
author
booktitle
chapter
edition
editor
howpublished
institution
journal
key
month
note
number
organization
pages
publisher
school
series
title
type
volume
year
}
{}
{ label }
INTEGERS { output.state before.all mid.sentence after.quote after.sentence
after.quoted.block after.block }
FUNCTION {init.state.consts}
{ #0 'before.all :=
#1 'mid.sentence :=
#2 'after.quote :=
#3 'after.sentence :=
#4 'after.quoted.block :=
#5 'after.block :=
}
STRINGS { s t }
FUNCTION {output.nonnull}
{ 's :=
output.state mid.sentence =
{ ", " * write$ }
{ output.state after.quote =
{ " " * write$ }
{ output.state after.block =
{ add.period$ write$
newline$
"\newblock " write$
}
{ output.state before.all =
'write$
{ output.state after.quoted.block =
{ write$
newline$
"\newblock " write$
}
{ add.period$ " " * write$ }
if$
}
if$
}
if$
}
if$
mid.sentence 'output.state :=
}
if$
s
}
FUNCTION {output}
{ duplicate$ empty$
'pop$
'output.nonnull
if$
}
FUNCTION {output.check}
{ 't :=
duplicate$ empty$
{ pop$ "empty " t * " in " * cite$ * warning$ }
'output.nonnull
if$
}
FUNCTION {output.bibitem}
{ newline$
"\bibitem{" write$
cite$ write$
"}" write$
newline$
""
before.all 'output.state :=
}
FUNCTION {blank.sep}
{ after.quote 'output.state :=
}
FUNCTION {fin.entry}
{ output.state after.quoted.block =
'skip$
'add.period$
if$
write$
newline$
}
FUNCTION {new.block}
{ output.state before.all =
'skip$
{ output.state after.quote =
{ after.quoted.block 'output.state := }
{ after.block 'output.state := }
if$
}
if$
}
FUNCTION {new.sentence}
{ output.state after.block =
'skip$
{ output.state before.all =
'skip$
{ after.sentence 'output.state := }
if$
}
if$
}
FUNCTION {not}
{ { #0 }
{ #1 }
if$
}
FUNCTION {and}
{ 'skip$
{ pop$ #0 }
if$
}
FUNCTION {or}
{ { pop$ #1 }
'skip$
if$
}
FUNCTION {new.block.checka}
{ empty$
'skip$
'new.block
if$
}
FUNCTION {new.block.checkb}
{ empty$
swap$ empty$
and
'skip$
'new.block
if$
}
FUNCTION {new.sentence.checka}
{ empty$
'skip$
'new.sentence
if$
}
FUNCTION {field.or.null}
{ duplicate$ empty$
{ pop$ "" }
'skip$
if$
}
FUNCTION {emphasize}
{ duplicate$ empty$
{ pop$ "" }
{ "{\em " swap$ * "}" * }
if$
}
INTEGERS { nameptr namesleft numnames }
FUNCTION {format.names}
{ 's :=
#1 'nameptr :=
s num.names$ 'numnames :=
numnames 'namesleft :=
{ namesleft #0 > }
{ s nameptr "{f.~}{vv~}{ll}{, jj}" format.name$ 't :=
nameptr #1 >
{ namesleft #1 >
{ ", " * t * }
{ numnames #2 >
{ "," * }
'skip$
if$
t "others" =
{ " {\em et~al.}" * }
{ " and " * t * }
if$
}
if$
}
't
if$
nameptr #1 + 'nameptr :=
namesleft #1 - 'namesleft :=
}
while$
}
FUNCTION {format.authors}
{ author empty$
{ "" }
{ author format.names }
if$
}
FUNCTION {format.editors}
{ editor empty$
{ "" }
{ editor format.names
editor num.names$ #1 >
{ ", eds." * }
{ ", ed." * }
if$
}
if$
}
FUNCTION {format.title}
{ title empty$
{ "" }
{ "``" title "t" change.case$ * ",''" * }
if$
}
FUNCTION {format.title.p}
{ title empty$
{ "" }
{ "``" title "t" change.case$ * ".''" * }
if$
}
FUNCTION {n.dashify}
{ 't :=
""
{ t empty$ not }
{ t #1 #1 substring$ "-" =
{ t #1 #2 substring$ "--" = not
{ "--" *
t #2 global.max$ substring$ 't :=
}
{ { t #1 #1 substring$ "-" = }
{ "-" *
t #2 global.max$ substring$ 't :=
}
while$
}
if$
}
{ t #1 #1 substring$ *
t #2 global.max$ substring$ 't :=
}
if$
}
while$
}
FUNCTION {format.date}
{ year empty$
{ month empty$
{ "" }
{ "there's a month but no year in " cite$ * warning$
month
}
if$
}
{ month empty$
'year
{ month " " * year * }
if$
}
if$
}
FUNCTION {format.btitle}
{ title emphasize
}
FUNCTION {tie.or.space.connect}
{ duplicate$ text.length$ #3 <
{ "~" }
{ " " }
if$
swap$ * *
}
FUNCTION {either.or.check}
{ empty$
'pop$
{ "can't use both " swap$ * " fields in " * cite$ * warning$ }
if$
}
FUNCTION {format.bvolume}
{ volume empty$
{ "" }
{ "vol.~" volume *
series empty$
'skip$
{ " of " * series emphasize * }
if$
"volume and number" number either.or.check
}
if$
}
FUNCTION {format.number.series}
{ volume empty$
{ number empty$
{ series field.or.null }
{ output.state mid.sentence =
{ "no.~" }
{ "No.~" }
if$
number *
series empty$
{ "there's a number but no series in " cite$ * warning$ }
{ " in " * series * }
if$
}
if$
}
{ "" }
if$
}
FUNCTION {format.edition}
{ edition empty$
{ "" }
{ edition "l" change.case$ "~ed." * }
if$
}
INTEGERS { multiresult }
FUNCTION {multi.page.check}
{ 't :=
#0 'multiresult :=
{ multiresult not
t empty$ not
and
}
{ t #1 #1 substring$
duplicate$ "-" =
swap$ duplicate$ "," =
swap$ "+" =
or or
{ #1 'multiresult := }
{ t #2 global.max$ substring$ 't := }
if$
}
while$
multiresult
}
FUNCTION {format.pages}
{ pages empty$
{ "" }
{ pages multi.page.check
{ "pp.~" pages n.dashify * }
{ "p.~" pages * }
if$
}
if$
}
FUNCTION {format.volume}
{ volume empty$
{ "" }
{ "vol.~" volume * }
if$
}
FUNCTION {format.number}
{ number empty$
{ "" }
{ "no.~" number * }
if$
}
FUNCTION {format.chapter.pages}
{ chapter empty$
'format.pages
{ type empty$
{ "ch.~" chapter * }
{ type "l" change.case$ chapter tie.or.space.connect }
if$
pages empty$
'skip$
{ ", " * format.pages * }
if$
}
if$
}
FUNCTION {format.in.ed.booktitle}
{ booktitle empty$
{ "" }
{ "in " booktitle emphasize *
editor empty$
'skip$
{ " (" * format.editors * ")" * }
if$
}
if$
}
FUNCTION {format.thesis.type}
{ type empty$
'skip$
{ pop$
output.state after.block =
{ type "t" change.case$ }
{ type "l" change.case$ }
if$
}
if$
}
FUNCTION {empty.misc.check}
{ author empty$ title empty$ howpublished empty$
month empty$ year empty$ note empty$
and and and and and
{ "all relevant fields are empty in " cite$ * warning$ }
'skip$
if$
}
FUNCTION {format.tr.number}
{ type empty$
{ "Tech. Rep." }
'type
if$
number empty$
{ "l" change.case$ }
{ number tie.or.space.connect }
if$
}
FUNCTION {format.addr.pub}
{ publisher empty$
{ "" }
{ address empty$
{ "" }
{ address ": " * }
if$
publisher *
}
if$
}
FUNCTION {format.paddress}
{ address empty$
{ "" }
{ "(" address * ")" * }
if$
}
FUNCTION {format.article.crossref}
{ key empty$
{ journal empty$
{ "need key or journal for " cite$ * " to crossref " * crossref *
warning$
""
}
{ "in {\em " journal * "\/}" * }
if$
}
{ "in " key * }
if$
" \cite{" * crossref * "}" *
}
FUNCTION {format.crossref.editor}
{ editor #1 "{vv~}{ll}" format.name$
editor num.names$ duplicate$
#2 >
{ pop$ " {\em et~al.}" * }
{ #2 <
'skip$
{ editor #2 "{ff }{vv }{ll}{ jj}" format.name$ "others" =
{ " {\em et~al.}" * }
{ " and " * editor #2 "{vv~}{ll}" format.name$ * }
if$
}
if$
}
if$
}
FUNCTION {format.book.crossref}
{ volume empty$
{ "empty volume in " cite$ * "'s crossref of " * crossref * warning$
"In "
}
{ "Vol.~" volume *
" of " *
}
if$
editor empty$
editor field.or.null author field.or.null =
or
{ key empty$
{ series empty$
{ "need editor, key, or series for " cite$ * " to crossref " *
crossref * warning$
"" *
}
{ "{\em " * series * "\/}" * }
if$
}
{ key * }
if$
}
{ format.crossref.editor * }
if$
" \cite{" * crossref * "}" *
}
FUNCTION {format.incoll.inproc.crossref}
{ editor empty$
editor field.or.null author field.or.null =
or
{ key empty$
{ booktitle empty$
{ "need editor, key, or booktitle for " cite$ * " to crossref " *
crossref * warning$
""
}
{ "in {\em " booktitle * "\/}" * }
if$
}
{ "in " key * }
if$
}
{ "in " format.crossref.editor * }
if$
" \cite{" * crossref * "}" *
}
FUNCTION {article}
{ output.bibitem
format.authors "author" output.check
format.title "title" output.check
blank.sep
crossref missing$
{ journal emphasize "journal" output.check
format.volume output
month empty$
{ format.number output }
'skip$
if$
format.pages output
format.date "year" output.check
}
{ format.article.crossref output.nonnull
format.pages output
}
if$
new.block
note output
fin.entry
}
FUNCTION {book}
{ output.bibitem
author empty$
{ format.editors "author and editor" output.check }
{ format.authors output.nonnull
crossref missing$
{ "author and editor" editor either.or.check }
'skip$
if$
}
if$
format.btitle "title" output.check
crossref missing$
{ format.bvolume output
new.block
format.number.series output
format.addr.pub "publisher" output.check
}
{ new.block
format.book.crossref output.nonnull
}
if$
format.edition output
format.date "year" output.check
new.block
note output
fin.entry
}
FUNCTION {booklet}
{ output.bibitem
format.authors output
title empty$
{ "empty title in " cite$ * warning$
howpublished new.sentence.checka
}
{ howpublished empty$ not
address empty$ month empty$ year empty$ and and
or
{ format.title.p output.nonnull }
{ format.title output.nonnull }
if$
blank.sep
}
if$
howpublished output
address output
format.date output
new.block
note output
fin.entry
}
FUNCTION {inbook}
{ output.bibitem
author empty$
{ format.editors "author and editor" output.check }
{ format.authors output.nonnull
crossref missing$
{ "author and editor" editor either.or.check }
'skip$
if$
}
if$
format.btitle "title" output.check
crossref missing$
{ format.bvolume output
format.chapter.pages "chapter and pages" output.check
new.block
format.number.series output
format.addr.pub "publisher" output.check
}
{ format.chapter.pages "chapter and pages" output.check
new.block
format.book.crossref output.nonnull
}
if$
format.edition output
format.date "year" output.check
new.block
note output
fin.entry
}
FUNCTION {incollection}
{ output.bibitem
format.authors "author" output.check
format.title "title" output.check
blank.sep
crossref missing$
{ format.in.ed.booktitle "booktitle" output.check
format.bvolume output
format.number.series output
format.chapter.pages output
format.addr.pub "publisher" output.check
format.edition output
format.date "year" output.check
}
{ format.incoll.inproc.crossref output.nonnull
format.chapter.pages output
}
if$
new.block
note output
fin.entry
}
FUNCTION {inproceedings}
{ output.bibitem
format.authors "author" output.check
format.title "title" output.check
blank.sep
crossref missing$
{ format.in.ed.booktitle "booktitle" output.check
format.bvolume output
format.number.series output
format.paddress output
format.pages output
organization output
publisher output
format.date "year" output.check
}
{ format.incoll.inproc.crossref output.nonnull
format.pages output
}
if$
new.block
note output
fin.entry
}
FUNCTION {conference} { inproceedings }
FUNCTION {manual}
{ output.bibitem
author empty$
{ organization empty$
'skip$
{ organization output.nonnull
address output
}
if$
}
{ format.authors output.nonnull }
if$
format.btitle "title" output.check
author empty$
{ organization empty$
{ address new.block.checka
address output
}
'skip$
if$
}
{ organization address new.block.checkb
organization output
address output
}
if$
format.edition output
format.date output
new.block
note output
fin.entry
}
FUNCTION {mastersthesis}
{ output.bibitem
format.authors "author" output.check
format.title "title" output.check
blank.sep
"Master's thesis" format.thesis.type output.nonnull
school "school" output.check
address output
format.date "year" output.check
new.block
note output
fin.entry
}
FUNCTION {misc}
{ output.bibitem
format.authors output
title empty$
{ howpublished new.sentence.checka }
{ howpublished empty$ not
month empty$ year empty$ and
or
{ format.title.p output.nonnull }
{ format.title output.nonnull }
if$
blank.sep
}
if$
howpublished output
format.date output
new.block
note output
fin.entry
empty.misc.check
}
FUNCTION {phdthesis}
{ output.bibitem
format.authors "author" output.check
format.btitle "title" output.check
new.block
"PhD thesis" format.thesis.type output.nonnull
school "school" output.check
address output
format.date "year" output.check
new.block
note output
fin.entry
}
FUNCTION {proceedings}
{ output.bibitem
editor empty$
{ organization output }
{ format.editors output.nonnull }
if$
format.btitle "title" output.check
format.bvolume output
format.number.series output
format.paddress output
editor empty$
'skip$
{ organization output }
if$
publisher output
format.date "year" output.check
new.block
note output
fin.entry
}
FUNCTION {techreport}
{ output.bibitem
format.authors "author" output.check
format.title "title" output.check
blank.sep
format.tr.number output.nonnull
institution "institution" output.check
address output
format.date "year" output.check
new.block
note output
fin.entry
}
FUNCTION {unpublished}
{ output.bibitem
format.authors "author" output.check
format.title.p "title" output.check
blank.sep
note "note" output.check
format.date output
fin.entry
}
FUNCTION {default.type} { misc }
MACRO {jan} {"Jan."}
MACRO {feb} {"Feb."}
MACRO {mar} {"Mar."}
MACRO {apr} {"Apr."}
MACRO {may} {"May"}
MACRO {jun} {"June"}
MACRO {jul} {"July"}
MACRO {aug} {"Aug."}
MACRO {sep} {"Sept."}
MACRO {oct} {"Oct."}
MACRO {nov} {"Nov."}
MACRO {dec} {"Dec."}
MACRO {acmcs} {"ACM Computing Surveys"}
MACRO {acta} {"Acta Informatica"}
MACRO {cacm} {"Communications ACM"}
MACRO {ibmjrd} {"IBM J. Research and Development"}
MACRO {ibmsj} {"IBM Systems~J."}
MACRO {ieeese} {"IEEE Trans. Software Engineering"}
MACRO {ieeetc} {"IEEE Trans. Computers"}
MACRO {ieeetcad}
{"IEEE Trans. Computer-Aided Design"}
MACRO {ipl} {"Information Processing Letters"}
MACRO {jacm} {"J.~ACM"}
MACRO {jcss} {"J.~Computer and System Sciences"}
MACRO {scp} {"Science of Computer Programming"}
MACRO {sicomp} {"SIAM J. Computing"}
MACRO {tocs} {"ACM Trans. Computer Systems"}
MACRO {tods} {"ACM Trans. Database Systems"}
MACRO {tog} {"ACM Trans. Graphics"}
MACRO {toms} {"ACM Trans. Mathematical Software"}
MACRO {toois} {"ACM Trans. Office Information Systems"}
MACRO {toplas} {"ACM Trans. Programming Languages and Systems"}
MACRO {tcs} {"Theoretical Computer Science"}
READ
STRINGS { longest.label }
INTEGERS { number.label longest.label.width }
FUNCTION {initialize.longest.label}
{ "" 'longest.label :=
#1 'number.label :=
#0 'longest.label.width :=
}
FUNCTION {longest.label.pass}
{ number.label int.to.str$ 'label :=
number.label #1 + 'number.label :=
label width$ longest.label.width >
{ label 'longest.label :=
label width$ 'longest.label.width :=
}
'skip$
if$
}
EXECUTE {initialize.longest.label}
ITERATE {longest.label.pass}
FUNCTION {begin.bib}
{ preamble$ empty$
'skip$
{ preamble$ write$ newline$ }
if$
"\begin{thebibliography}{" longest.label * "}" * write$ newline$
}
EXECUTE {begin.bib}
EXECUTE {init.state.consts}
ITERATE {call.type$}
FUNCTION {end.bib}
{ newline$
"\end{thebibliography}" write$ newline$
}
EXECUTE {end.bib}

223
mani-station.bib Normal file
View File

@ -0,0 +1,223 @@
@article{e-ink,
author={Jones,Leslie E.},
year={2011},
month={Spring},
title={Spilling the e-Ink},
journal={African Arts},
volume={44},
number={1},
pages={1-1,4},
note={Copyright - Copyright African Studies Center Spring 2011;},
abstract={For electronic book publishing to truly take off, it was necessary to develop a lightweight reading device with a long battery life, comfortable to hold in the hand and easy on the eyes. ...] Google Books, through the settlement agreed upon in November 2009 with the Authors Guild and Association of American Publishers,3 will make an increasing number of incopyright but out-of-print books available, some for free and some for purchase, in electronic format; the free books are readable on Barnes and Nobles ereader, the Nook, and also on computer.4 JSTOR- which archives African Arts- is making an ever-larger number of journals available online, and is also devising ways for those who are not affiliated with a subscribing institution to purchase content piecemeal.'},
keywords={Art; Books; Competition; Reading; African art; New York; Amazon Kindle; Apple iPad},
isbn={00019933},
language={English},
url={https://www.proquest.com/scholarly-journals/spilling-e-ink/docview/858886813/se-2},
}
@book{han_butler_2015, place={Stanford}, title={The Burnout Society}, publisher={Stanford University Press}, author={Han, Byung-Chul and Butler, Erik}, year={2015}}
@misc{remarkable, title={Our remarkable story}, howpublished={https://remarkable.com/about}, journal={reMarkable}}
@article{dementiaux,
author={König,Theresa and Martina,Pigliautile and Águila Oscar and Jon,Arambarri and Christophoros,Christophorou and Matteo,Colombo and Argyris,Constantinides and Rosario,Curia and Kathrina,Dankl and Sten,Hanke and Mayer,Christopher C. and Stefan,Moritsch and Müllner-Rieder,Markus and Fritz,Pernkopf and Schüler,Christian and Stillo,Maria and Patrizia,Mecocci and Stögmann Elisabeth},
year={2022},
month={04},
title={User experience and acceptance of a device assisting persons with dementia in daily life: a multicenter field study},
journal={Aging Clinical and Experimental Research},
volume={34},
number={4},
pages={869-879},
abstract={BackgroundAssistive technologies have the potential to facilitate everyday life of people with dementia and their families. Close collaboration with affected people and interdisciplinary research are essential to understand and address the needs of prospective users. In this study, we present the results of the evaluation of such an assistive system prototype.AimsChallenges from the patient and caregiver side, technical and design problems and acceptance and usability with regard to our special target group were evaluated.MethodsMEMENTO, a system of two e-ink tablets and a smartwatch, was tested in the domestic environment of dementia patients. Thirty participants from Italy, Spain and Austria took part in a 3-month field trial and compared the MEMENTO system to traditional strategies in everyday life. Quantitative and qualitative data were collected and frequency of use of the system was monitored.ResultsThere were no significant changes in quantitative measurements, such as activities of daily living and caregiver burden over the duration of the 3-month field trial. More frequent usage was significantly correlated with positive attitude towards technology (r = 0.723, p < 0.05), but not with age. The design of the system was positively emphasized, reducing fear of the technology on the one hand and stigmatization on the other.ConclusionWe show that a positive attitude towards technology is the essential variable for successful implementation of such systems, regardless of age. Participants showed great interest in digital solutions and agreed that technological systems will help in maintaining independency of persons with cognitive dysfunction in the future.},
keywords={Gerontology And Geriatrics; Dementia; Cognitive impairment; Assistive technologies; Digital device; Usability testing; Independent living; Research; Patients; Usability; Smartwatches; User experience; Aging; Adaptive technology; Activities of daily living; Wearable computers; Industrial design; Gerontology; Cognitive ability; Geriatrics; Caregivers; Field study; Alzheimers disease},
isbn={15940667},
language={English},
url={https://www.proquest.com/scholarly-journals/user-experience-acceptance-device-assisting/docview/2660201073/se-2},
}
@article{multitaskingaddiction,
author={Lin,Trisha T. C. and Kononova,Anastasia and Chiang,Yi-Hsuan},
year={2020},
month={11},
title={Screen Addiction and Media Multitasking among American and Taiwanese Users},
journal={The Journal of Computer Information Systems},
volume={60},
number={6},
pages={583-592},
abstract={This cross-country survey research investigated the relationship between screen addiction and media multitasking and examined factors that mediate and moderate this relationship. The web survey recruited Internet users owning multiple devices in the United States (N = 798) and Taiwan (N = 834). Although American users spent longer time on screen devices and engaged more in media multitasking more, Taiwanese respondents had higher screen addiction. Results showed that media multitasking and screen device use were positively related to screen addiction. Country of respondents’ residence moderated the relationship between media multitasking and screen addiction. Additionally, screen device usage mediated the positive effects of media multitasking on screen addiction. Finally, leisure boredom moderated screen device usage’s mediating effects on the relationship between media multitasking and screen addiction, which differed in two countries. Young people and females tended to have high levels of screen addiction. Implications of screen addiction and media multitasking were discussed.},
keywords={Computers; Screen addiction; media multitasking; leisure boredom; screen device usage; cross-country comparison; Young adults; Boredom; Addictions; Multitasking; Media},
isbn={08874417},
language={English},
url={https://www.proquest.com/scholarly-journals/screen-addiction-media-multitasking-among/docview/2456816249/se-2},
}
@article{screenaddiction,
author={Khalili-Mahani,Najmeh and Smyrnova,Anna and Kakinami,Lisa},
year={2019},
month={04},
title={To Each Stress Its Own Screen: A Cross-Sectional Survey of the Patterns of Stress and Various Screen Uses in Relation to Self-Admitted Screen Addiction},
journal={Journal of Medical Internet Research},
volume={21},
number={4},
abstract={Background: The relationship between stress and screen addiction is often studied by exploring a single aspect of screen-related behavior in terms of maladaptive dependency or the risks associated with the content. Generally, little attention is given to the pattern of using different screens for different types of stressors, and variations arising from the subjective perception of stress and screen addiction are often neglected. Given that both addiction and stress are complex and multidimensional factors, we performed a multivariate analysis of the link between individual’s subjective perceptions of screen addiction, various types of stress, and the pattern of screen usage. Objective: Using the media-repertoires framework to study usage patterns, we explored (1) the relation between subjective and quantitative assessments of stress and screen addiction; and (2) differences in stress types in relation to subjective screen addiction and different types of needs for screens. We hypothesized that interindividual heterogeneity in screen-related behavior would reflect coping differences in dealing with different stressors. Methods: A multifactorial Web-based survey was conducted to gather data about screen-related behaviors (such as screen time, internet addiction, and salience of different types of screens and related activities), and different sources of stress (emotional states, perceptual risks, health problems, and general life domain satisfaction). We performed group comparisons based on whether participants reported themselves as addicted to internet and games (A1) or not (A0), and whether they had experienced a major life stress (S1) or not (S0). Results: Complete responses were obtained in 459 out of 654 survey responders, with the majority in the S1A0 (44.6%, 205/459) group, followed by S0A0 (25.9%, 119/459), S1A1 (19.8%, 91/459), and S0A1 (9.5%, 44/459). The S1A1 group was significantly different from S0A0 in all types of stress, internet overuse, and screen time (P<.001). Groups did not differ in rating screens important for short message service (SMS) or mail, searching information, shopping, and following the news, but a greater majority of A1 depended on screens for entertainment (χ23=20.5; P<.001), gaming (χ23=35.6; P<.001), and social networking (χ23=26.5; P<.001). Those who depended on screens for entertainment and social networking had up to 19% more emotional stress and up to 14% more perceptual stress. In contrast, those who relied on screens for work and professional networking had up to 10% higher levels of life satisfaction. Regression models including age, gender, and 4 stress types explained less than 30% of variation in internet use and less than 24% of the likelihood of being screen addicted. Conclusions: We showed a robust but heterogeneous link between screen dependency and emotional and perceptual stressors that shift the pattern of screen usage toward entertainment and social networking. Our findings underline the potential of using ludic and interactive apps for intervention against stress.},
keywords={Medical Sciences--Computer Applications; psychological stress; addictive behavior; coping behavior; social network; gaming, internet; communications; telemedicine; eHealth; Physiology; Computer & video games; Internet; Shopping; Communication; Coping; Entertainment; Health problems; Social networks; Mental disorders; Occupational stress; Emotional states; Questionnaires; News; Adaptation; Games; Neurosciences; Emotions; Social research; Emotional-Behavioural problems; Screen time; Cellular telephones; Addictions; Stress; Life stress; Mental depression; Life satisfaction; Computer based; Anxiety disorders; Mental health; Polls & surveys; Behavior; Multivariate analysis; Networking; Dependency; Selye, Hans},
language={English},
url={https://www.proquest.com/scholarly-journals/each-stress-own-screen-cross-sectional-survey/docview/2512771245/se-2},
}
@article{kantscreens,
author={Lo Re,Stefano},
year={2022},
month={09},
title={The Glowing Screen Before Me and the Moral Law Within me: A Kantian Duty Against Screen Overexposure},
journal={Res Publica},
volume={28},
number={3},
pages={491-511},
abstract={This paper establishes a Kantian duty against screen overexposure. After defining screen exposure, I adopt a Kantian approach to its morality on the ground that Kant’s notion of duties to oneself easily captures wrongdoing in absence of harm or wrong to others. Then, I draw specifically on Kant’s ‘duties to oneself as an animal being’ to introduce a duty of self-government. This duty is based on the negative causal impact of the activities it regulates on a human being’s mental and physical powers, and, ultimately, on the moral employment of these powers. After doing so, I argue that the duty against screen overexposure is an instance of the duty of self-government. Finally, I consider some objections.},
keywords={Philosophy; Kant; Duties to oneself; Screen addiction; Internet addiction; Morality; Employment; Public opinion; Internet; Smartphones; Blood & organ donations; Contemporary problems; Addictions; Ethics; Social networks},
isbn={13564765},
language={English},
url={https://www.proquest.com/scholarly-journals/glowing-screen-before-me-moral-law-within-kantian/docview/2713129266/se-2},
}
@phdthesis{readability,
author={Baker,Rebecca D.},
year={2010},
title={Comparing the readability of text displays on paper, e-book readers, and small screen devices},
journal={ProQuest Dissertations and Theses},
pages={56},
abstract={Science fiction has long promised the digitalization of books. Characters in films and television routinely check their palm-sized (or smaller) electronic displays for fast-scrolling information. However, this very technology, increasingly prevalent in today’s world, has not been embraced universally. While the convenience of pocket-sized information pieces has the techno-savvy entranced, the general public still greets the advent of the e-book with a curious reluctance. This lack of enthusiasm seems strange in the face of the many advantages offered by the new medium—vastly superior storage capacity, searchability, portability, lower cost, and instantaneous access. This dissertation addresses the need for research examining the reading comprehension and the role emotional response plays in the perceived performance on e-document formats as compared to traditional paper format. This study compares the relative reading comprehension on three formats (Kindle, iTouch, and paper) and examines the relationship of subject’s emotional response and relative technology exposure as factors that affect how the subject perceives they have performed on those formats. This study demonstrates that, for basic reading comprehension, the medium does not matter. Furthermore, it shows that, the more uncomfortable a person is with technology and expertise in the requested task (in this case, reading), the more they cling to the belief that they will do better on traditional (paper) media—regardless of how well they actually do.},
keywords={Communication and the arts; E-book reader; E-books; Readability; Reading comprehension; Small screen display; Text display; Library science; Information science; Multimedia communications; 0399:Library science; 0723:Information science; 0558:Multimedia Communications},
isbn={978-1-124-15386-5},
language={English},
url={https://www.proquest.com/dissertations-theses/comparing-readability-text-displays-on-paper-e/docview/746481524/se-2},
}
@article{multitasking,
author={Black,Stephanie C. and Bender,Angela D. and Whitney,Susannah J. and Loft,Shayne and Visser,Troy A. W.},
year={2022},
month={Jul},
title={The effect of multi‐tasking training on performance, situation awareness, and workload in simulated air traffic control},
journal={Applied Cognitive Psychology},
volume={36},
number={4},
pages={874-890},
abstract={Increasingly higher demands are being made on the capacity‐limited cognitive capabilities of human operators as they strive to maintain situation awareness (i.e., understanding “what is going on”) and performance in complex tasks. In the current study we asked whether: (a) training administered via a mobile phone‐based app could improve multitasking and (b) improved multitasking in the app would generalize to improved performance and situation awareness in a simulated air traffic control task (ATC). Participants completed the ATC task before and after multiple sessions of app‐based multitasking training or control training. Multitasking on the app improved across training sessions. However, this did not lead to improved performance or situation awareness, or workload reduction, relative to control training on the ATC task. These outcomes indicate that app‐based multitasking training based on repetition of a single training task will not necessarily yield generalizable benefits to human performance in other complex dynamic tasks.},
keywords={Psychology; multi‐tasking; situation awareness; training; Operators; Task performance; Complex tasks; Cognitive ability; Capabilities; Repetition; Traffic; Mobile phones},
isbn={08884080},
language={English},
url={https://www.proquest.com/scholarly-journals/effect-multi-tasking-training-on-performance/docview/2691596952/se-2},
}
@article{calmcomputing,
author={Kukka,Hannu and Luusua,Anna and Ylipulli,Johanna and Suopajärvi,Tiina and Kostakos,Vassilis and Ojala,Timo},
year={2014},
month={05},
title={From cyberpunk to calm urban computing: Exploring the role of technology in the future cityscape},
journal={Technological Forecasting and Social Change},
volume={84},
pages={29},
abstract={In this paper we will present studies aimed at uncovering the attitudes, needs, and expectations people have towards novel types of urban computing technologies deployed in a city. First, we conducted a storytelling competition to elicit future visions of how people imagined the role of technology. Second, we conducted a rapid ethnographic study using a mock-up prototype device in various public locations to gain a deeper understanding of how people would appropriate a specific technology, namely interactive public displays. Lastly, we collected ethnographic material through a diary study and interviews where people recorded their use of existing technology, and through these experiences, imagine how future technologies might affect their lives. We found that these methods proved useful in engaging a city's community to imagine the city's future. Consequently, we were able to explore the current use of technologies in the city and project their possible future use. Contrary to previous speculation in academic and cyberpunk literature, we conclude that digital technologies will not necessarily induce an abandonment of physical urban spaces. Rather, we project an increased sophistication in the sociable uses of urban spaces and technologies, where people blend their online and offline worlds into a single lived reality. PUBLICATION ABSTRACT]},
keywords={Sociology; Studies; Urban areas; Information technology; Storytelling; Technological planning; Prototypes; Ethnography; 9130:Experiment/theoretical treatment; 2310:Planning; 5220:Information technology management},
isbn={00401625},
language={English},
url={https://www.proquest.com/scholarly-journals/cyberpunk-calm-urban-computing-exploring-role/docview/1519610095/se-2},
}
@techreport{ISO9296,
type = {Standard},
key = {ISO 9296:2017(E)},
month = aug,
year = {2017},
title = {{Acoustics — Declared noise emission values of information technology and telecommunications equipment}},
institution = {International Organization for Standardization},
}
@article{keyboards,
author={Norman,Donald A. and Fisher,Diane},
year={1982},
month={10},
title={Why Alphabetic Keyboards Are Not Easy to Use: Keyboard Layout Doesn't Much Matter},
journal={Human factors},
volume={24},
number={5},
pages={509-519},
keywords={Sciences: Comprehensive Works; Layouts; Computer simulation; Keyboards; Visual perception; Information processing; Typing; Redesign; Simulation},
isbn={00187208},
language={English},
url={https://www.proquest.com/scholarly-journals/why-alphabetic-keyboards-are-not-easy-use/docview/1968159942/se-2},
}
@misc{raspberrypi, title={Raspberry {P}i 4 {M}odel {B}}, howpublished={https://www.raspberrypi.com/products/raspberry-pi-4-model-b/}, journal={Raspberry Pi}, publisher={Raspberry Pi}}
@electronic{monitorconnection, title={Paperlike {R}aspberry {P}i 4}, journal={Github}, author={tommythorn}, url={https://github.com/tommythorn/Paperlike-Raspberry-Pi-4/blob/master/README.md}}
@electronic{vail_2018, title={History of {E-I}nk}, url={https://blog.eink.com/history-of-e-ink}, journal={History of eInk}, publisher={Eink}, author={Vail, Jenn}, year={2018}, month={May}}
@electronic{signage, title={{TJHSST} {S}ignage}, url={https://documentation.tjhsst.edu/services/signage}, journal={TJ CSL Documentation}, publisher={TJCSL}, year={2022}}
@misc{e-ink-hist, title={E-reader}, author={H Li}, howpublished={https://encyclopedia.pub/entry/30626}, publisher={Encyclopedia}}
@misc{computer-history, title={Timeline of Computer History}, howpublished={https://www.computerhistory.org}, publisher={Computer History Museum Pi}}
@misc{win95, title={What is the history of Microsoft Windows?}, howpublished={https://kb.iu.edu/d/abwa}, author={IUTS}}
@misc{i3, title={i3 - improved tiling wm}, howpublished={https://i3wm.org/}, author={Michael Stapelberg}}
@misc{rail-model, title={Measure performance with the RAIL model}, howpublished={https://web.dev/rail/}, author={Google}}
@misc{macos, title={The evolution of macOS}, author={S. Moreau}, howpublished={https://www.computerworld.com/article/3692528/evolution-of-macos-and-mac-os-x.html}}
@misc{vim, title={The Missing Semester of Your CS Education}, howpublished={https://missing.csail.mit.edu/2020/editors}, author={MIT}}
@misc{i3-guide, title={i3 User's Guide}, howpublished={https://i3wm.org/docs/userguide.html}, author={Michael Stapelberg}}
@misc{electron-docs, title={What is Electron?}, howpublished={https://www.electronjs.org/docs/latest/}, author={OpenJS}}
@misc{vuejs, title={Vue.js}, howpublished={https://vuejs.org/about/faq.html}, author={Evan You}}
@article{rust,
author={Ardito,Luca and Barbato,Luca and Coppola,Riccardo and Valsesia,Michele},
year={2021},
month={Feb 26},
title={Evaluation of Rust code verbosity, understandability and complexity},
journal={PeerJ Computer Science},
note={Copyright - © 2021 Ardito et al. This is an open access article distributed under the terms of the Creative Commons Attribution License: https://creativecommons.org/licenses/by/4.0/ (the “License”), which permits unrestricted use, distribution, reproduction and adaptation in any medium and for any purpose provided that it is properly attributed. For attribution, the original author(s), title, publication source (PeerJ Computer Science) and either DOI or URL of the article must be cited. Notwithstanding the ProQuest Terms and Conditions, you may use this content in accordance with the terms of the License; Last updated - 2021-02-27},
abstract={Rust is an innovative programming language initially implemented by Mozilla, developed to ensure high performance, reliability, and productivity. The final purpose of this study consists of applying a set of common static software metrics to programs written in Rust to assess the verbosity, understandability, organization, complexity, and maintainability of the language. To that extent, nine different implementations of algorithms available in different languages were selected. We computed a set of metrics for Rust, comparing them with the ones obtained from C and a set of object-oriented languages: C++, Python, JavaScript, TypeScript. To parse the software artifacts and compute the metrics, it was leveraged a tool called rust-code-analysis that was extended with a software module, written in Python, with the aim of uniforming and comparing the results. The Rust code had an average verbosity in terms of the raw size of the code. It exposed the most structured source organization in terms of the number of methods. Rust code had a better Cyclomatic Complexity, Halstead Metrics, and Maintainability Indexes than C and C++ but performed worse than the other considered object-oriented languages. Lastly, the Rust code exhibited the lowest COGNITIVE complexity of all languages. The collected measures prove that the Rust language has average complexity and maintainability compared to a set of popular languages. It is more easily maintainable and less complex than the C and C++ languages, which can be considered syntactically similar. These results, paired with the memory safety and safe concurrency characteristics of the language, can encourage wider adoption of the language of Rust in substitution of the C language in both the open-source and industrial environments.},
keywords={Computers; Software maintainability; Software quality; Software metrics; Language; Maintainability; Java; Programming languages; Java (programming language); Source code; ISO standards; Experiments; Maintenance costs; C++ (programming language); Algorithms; Complexity; Integrated software; Performance indices; Concurrency; Software; Efficiency},
language={English},
url={https://www.proquest.com/scholarly-journals/evaluation-rust-code-verbosity-understandability/docview/2493708744/se-2},
}
@article{rust-performance,
author={Plauska,Ignas and Liutkevičius,Agnius and Janavičiūtė,Audronė},
year={2023},
title={Performance Evaluation of C/C++, MicroPython, Rust and TinyGo Programming Languages on ESP32 Microcontroller},
journal={Electronics},
volume={12},
number={1},
pages={143},
note={Copyright - © 2022 by the authors. Licensee MDPI, Basel, Switzerland. This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution (CC BY) license (https://creativecommons.org/licenses/by/4.0/). Notwithstanding the ProQuest Terms and Conditions, you may use this content in accordance with the terms of the License; Last updated - 2023-01-06},
abstract={The rapid growth of the Internet of Things (IoT) and its applications requires high computational efficiency, low-cost, and low-power solutions for various IoT devices. These include a wide range of microcontrollers that are used to collect, process, and transmit IoT data. ESP32 is a microcontroller with built-in wireless connectivity, suitable for various IoT applications. The ESP32 chip is gaining more popularity, both in academia and in the developer community, supported by a number of software libraries and programming languages. While low- and middle-level languages, such as C/C++ and Rust, are believed to be the most efficient, TinyGo and MicroPython are more developer-friendly low-complexity languages, suitable for beginners and allowing more rapid coding. This paper evaluates the efficiency of the available ESP32 programming languages, namely C/C++, MicroPython, Rust, and TinyGo, by comparing their execution performance. Several popular data and signal processing algorithms were implemented in these languages, and their execution times were compared: Fast Fourier Transform (FFT), Cyclic Redundancy Check (CRC), Secure Hash Algorithm (SHA), Infinite Impulse Response (IIR), and Finite Impulse Response (FIR) filters. The results show that the C/C++ implementations were fastest in most cases, closely followed by TinyGo and Rust, while MicroPython programs were many times slower than implementations in other programming languages. Therefore, the C/C++, TinyGo, and Rust languages are more suitable when execution and response time are the key factors, while Python can be used for less strict system requirements, enabling a faster and less complicated development process.},
keywords={Electronics; performance evaluation; microcontroller; ESP32; C/C++; MicroPython; TinyGo; Rust; Microcontrollers; Indoor air quality; Internet of Things; C plus plus; Fast Fourier transformations; Signal processing; C++ (programming language); Monitoring systems; Interpreters; JavaScript; Redundancy; Operating systems; Sanitation services; Programming languages; Embedded systems; Building automation; Sensors; Neural networks; FIR filters; Algorithms; Response time; Digital signatures},
language={English},
url={https://www.proquest.com/scholarly-journals/performance-evaluation-c-micropython-rust-tinygo/docview/2761121938/se-2},
}
@misc{deb11-performance, howpublished={https://www.neowin.net/news/debian-11-bullseye-offers-more-than-2x-performance-in-certain-applications/}, title={Debian 11 "bullseye" offers more than ~2X performance in certain applications}, author={Sayan Sen}, date={8-18-2021}}
@misc{deb11-preseed, howpublished={https://wiki.debian.org/DebianInstaller/Preseed}, title={DebianInstaller Preseed}, author={Debian}}
@misc{surf, howpublished={https://surf.suckless.org/}, title={surf}, author={Suckless}}
@misc{qutebrowser, howpublished={https://qutebrowser.org/doc/faq.html}, title={About Qutebrowser}, author={The-Compiler}}
@article{writing-in-linux,
author={Tchantchaleishvili,Vakhtang and Schmitto,Jan D.},
year={2011},
title={Preparing a scientific manuscript in Linux: Today's possibilities and limitations},
journal={BMC Research Notes},
volume={4},
pages={434},
note={Copyright - © 2011 Tchantchaleishvili et al; licensee BioMed Central Ltd. This is an open access article distributed under the terms of the Creative Commons Attribution License (http://creativecommons.org/licenses/by/2.0), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited; Last updated - 2015-09-09},
abstract={Abstract Background: Increasing number of scientists are enthusiastic about using free, open source software for their research purposes. Authors' specific goal was to examine whether a Linux-based operating system with open source software packages would allow to prepare a submission-ready scientific manuscript without the need to use the proprietary software. Findings: Preparation and editing of scientific manuscripts is possible using Linux and open source software. This letter to the editor describes key steps for preparation of a publication-ready scientific manuscript in a Linux-based operating system, as well as discusses the necessary software components. This manuscript was created using Linux and open source programs for Linux.},
keywords={Biology},
language={English},
url={https://www.proquest.com/scholarly-journals/preparing-scientific-manuscript-linux-todays/docview/906644559/se-2},
}
@misc{sublime, title={Sublime Text}, author={Sublime}, howpublished={https://www.sublimetext.com/}}
@misc{geary, title={Geary: a beautiful modern open-source email client}, author={Jim Nelson}, howpublished={\verb|https://www.youtube.com/watch?v=_frbzj7nj2w|}}
@misc{todo-electron, author={CodeDraken}, title={Build a Todo App with Electron}, howpublished={https://codeburst.io/build-a-todo-app-with-electron-d6c61f58b55a}}
@misc{todoist, title={Developing with Todoist}, author={Todoist}, howpublished={https://developer.todoist.com/guides}}
@misc{eink-def, title={Electronic Ink}, author={Margaret Rouse}, publisher={techopedia}, howpublished={techopedia.com/definition/15216/electronic-ink-e-ink}}

354
mani-station.tex Normal file
View File

@ -0,0 +1,354 @@
\documentclass[letterpaper,twocolumn,10pt]{article}
\usepackage[table]{xcolor}
\usepackage{usenix,epsfig,endnotes}
\usepackage{titlesec}
\begin{document}
\titlespacing*{\subsection}{0pt}{1\baselineskip}{1\baselineskip}
\titlespacing*{\subsubsection}{0pt}{1\baselineskip}{0.25\baselineskip}
\graphicspath{{res/}}
%don't want date printed
\date{}
%make title bold and 14 pt font (Latex default is non-bold, 16 pt)
\title{\Large \bf Mani Station: A Modern Paradigm Shift Towards Calm Computing}
\author{
{\rm Rushil Umaretiya}\\
Thomas Jefferson High School for Science and Technology
}
\maketitle
\subsection*{Abstract}
In today's digital landscape, technology has become an integral part of our daily lives. However, when these technologies become barriers to entry and sources of discomfort for users, it leads to widespread distress. This research focuses on the development of a calm computing device, the \emph{Mani Station}, designed to minimize user stress and foster a more harmonious relationship with technology for productivity, connection, and overall well-being. Through the integration of an e-ink display, silent hardware components, and a bespoke desktop environment, the Mani Station will serve as a pioneering exploration into creating a more tranquil and user-friendly computing experience.
\section{Introduction}
Byung-Chul Han writes about the current state of the modern technological society in his book \emph{The Burnout Society}~\cite{han_butler_2015}.
\begin{quote}
From a pathological standpoint, the incipient twenty-first century is determined neither by bacteria nor by viruses, but by neurons. Neurological illnesses such as depression, attention deficit hyperactivity disorder (ADHD), borderline personality disorder (BPD), and burnout syndrome mark the landscape of pathology at the beginning of the twenty-first century. They are not infections, but infarctions; they do not follow from the negativity of what is immunologically foreign, but from an excess of positivity. Therefore, they elude all technologies and techniques that seek to combat what is alien.
\end{quote}
The contemporary landscape of technology reveals a void in the realm of calm computing. Since the advent of personal computers in the 1970s, these devices have revolutionized the way people work, communicate, and access information. Initially, personal computers such as the Apple II (1977) and IBM PC (1981) were mainly used for business applications, programming, and educational purposes \cite{computer-history}. As technology advanced, personal computers became more powerful and versatile, and their applications expanded to encompass multimedia, gaming, and internet browsing.
However, despite the numerous advancements in personal computing, the concept of calm computing has not been fully explored. Personal computers were initially designed to facilitate and empower users by allowing them to accomplish their tasks efficiently, free from distracting colors and intrusive notifications. A calm computer, characterized by its unobtrusive responsiveness, delivers precisely what users need without haste or unnecessary distractions. The present research aims to fill this gap by creating a solution rooted in the principles of calm computing \cite{dementiaux} \cite{calmcomputing}.
Our project focuses on the development of a serene personal computer named Mani Station, which encompasses a tower, an e-ink monitor, peripherals, and a custom operating system designed to prioritize non-obtrusiveness. The usability, responsiveness, comfort, and capability to replace conventional devices of the Mani Station will be evaluated across various age groups. Ultimately, this project seeks to pioneer the invention and exploration of one of the first calm computers in the modern technological arena.
\section{Background}
\subsection{E-ink}
The core inspiration for this research originates from the understatement and underuse of E-ink technology. E-ink defines a class of display often printing to grayscale that drives images to a screen without the use of an external light \cite{eink-def}. Current display technologies generate light that directly hits the retina, a situation that some authors argue may contribute to screen overexposure and its associated health concerns among various demographics. It has been suggested that efforts should be made to protect users from potential harm due to excessive screen brightness and coloration \cite{screenaddiction}. One author actually writes that it is our Kantian duty to protect the self from screen overexposure \cite{kantscreens}.
The advancement of digital technology has fostered a highly connected world, leading to increased screen time for many individuals. In response to these concerns, e-ink devices, such as e-readers and monitors, have been proposed as alternatives that might help reduce screen dependence. As a relatively new technology, e-ink has undergone substantial commercial development, propelling it into an era where it has the potential to entirely replace traditional screen technologies \cite{e-ink}.
E-ink technology traces its origins back to the 1990s, when researchers at the MIT Media Lab first developed the concept of electronic ink. The first commercially available e-ink devices, such as the Sony Librie (2004) and Amazon Kindle (2007), focused primarily on providing a comfortable reading experience for users, mimicking the look of printed text on paper \cite{e-ink-hist}. These early devices laid the groundwork for the expansion of e-ink technology into various applications, including signage, smartwatches, and even smartphones.
The ReMarkable 2, a cutting-edge e-ink device, is a prime example of the advancements made in this field. Functioning as both a writer and reader, it is equipped to process handwriting, store documents, sync files to the cloud, and annotate PDFs. With near real-time performance and a display that has significantly improved since the early days of e-ink devices, the ReMarkable 2 demonstrates the potential of e-ink technology to supplant smaller personal computers \cite{remarkable}. The present research can be considered an extension of the foundation laid by the ReMarkable 2, seeking to further explore and expand upon the capabilities of e-ink devices.
As e-ink technology continues to develop and gain adoption, the potential exists to utilize this technology to create computing experiences that may be perceived as more serene and focused. The integration of e-ink technology into the design of the Mani Station aims to provide a calm computing environment, reducing digital distractions, and improving overall user well-being.
\subsection{Desktop Environments}
Another large component of this project that has a deep and influential history is that of the desktop environment (DE). DE’s have played a critical role in shaping the user experience of personal computers since their creation. The advent of graphical interfaces facilitated a transformation in the user base of computing devices, eliminating the need for technical expertise for basic computing tasks. DE’s have evolved significantly over time, and with the further development of operating systems and window managers, HCI has come to the forefront of almost every large tech company today.
One of the earliest desktop environments was the Xerox Alto's interface, developed in the 1970s, which introduced the concept of a desktop metaphor, complete with icons, windows, and folders. However, it was Apple's Macintosh operating system (MacOS), released in 1984, that brought these innovations to a wider audience. MacOS pioneered the use of graphical user interfaces (GUIs) for personal computers, featuring a menu bar, overlapping windows, and the iconic "trash" icon for file deletion \cite{macos}. These innovations paved the way for future desktop environments and set the standard for graphical user interfaces.
When MacOS was released, Microsoft also debuted its own GUI at the same time. Windows 1.0 has experienced multiple revisions throughout the years, with each one improving the user interface and experience. With the introduction of the Start menu, taskbar, and the concept of plug-and-play peripherals, Windows 95's debut represented a key turning point. This made personal computing more accessible and user-friendly for a broader audience, and Windows quickly became the dominant operating system for personal computers worldwide. \cite{win95}
Alongside these proprietary systems, the open-source community has also contributed to the development of these graphical interfaces, with the Linux operating system offering a strong platform for these interfaces to live on. While full offering desktop environments like GNOME and KDE Plasma are among the most popular desktop environments in the *nix ecosystem, tiling window managers such as i3 have gained popularity for their minimalist and efficient approach to managing windows on the screen. Unlike its predecessors, i3 returns to a simpler system of displaying windows as a grid across its screen, and uses a binary tree in order to represent the order of windows \cite{i3}.
The development of desktop environments—from the early versions of MacOS and Windows to contemporary tiling window managers like i3—shows how the user experience in personal computing is constantly being improved. As technology advances, there is a chance to investigate and create new desktop environments that place user well-being, concentration, and the concepts of quiet computing first, like the operating system designed for the Mani Station.
\newpage
\subsection{RAIL Model}
One of the key objectives during the development of the Mani Station was to meet Google's RAIL model for latency and performance measurement. RAIL stands for Response, Animation, Idle, and Load, and serves as a user-centric performance model that outlines performance goals and guidelines for a seamless user experience. The design spec provides the following insight on how user retention falls off over time \cite{rail-model}
\begin{figure}[h]
\caption{RAIL Model Breakpoints}
\centering
\rowcolors{1}{gray!25}{white}
\begin{tabular}{ |p{1.5in}|p{1.5in}| }\hline
0 to 16 ms & Users are exceptionally good at tracking motion, and they dislike it when animations aren't smooth. They perceive animations as smooth so long as 60 new frames are rendered every second. That's 16 ms per frame, including the time it takes for the browser to paint the new frame to the screen, leaving an app about 10 ms to produce a frame. \\
0 to 100 ms & Respond to user actions within this time window and users feel like the result is immediate. Any longer, and the connection between action and reaction is broken. \\
100 to 1000 ms & Within this window, things feel part of a natural and continuous progression of tasks. For most users on the web, loading pages or changing views represents a task. \\
1000 ms or more & Beyond 1000 milliseconds (1 second), users lose focus on the task they are performing. \\
10000 ms or more & Beyond 10000 milliseconds (10 seconds), users are frustrated and are likely to abandon tasks. They may or may not come back later.
&\hline
\end{tabular}
\newline
\end{figure}
However, adhering to the RAIL model proved challenging due to the inherent limitations of the low refresh rate e-ink display employed in the Mani Station. The e-ink display was chosen for its calm computing properties, such as reduced eye strain and minimized distractions, but it also introduced unique obstacles in meeting the performance criteria set by the RAIL model:
\begin{itemize}
\item \emph{Response:} The RAIL model suggests that a response to user input should occur within 100 milliseconds. However, the low refresh rate of the e-ink display made it difficult to consistently achieve this target, as the screen's refresh latency could potentially exceed the 100-millisecond threshold. To mitigate this issue, we optimized the software to respond as quickly as possible and implemented visual indicators to assure users that their input was registered, even if the screen update was slightly delayed.
\item \emph{Animation:} RAIL recommends animations to run at 60 frames per second (fps), which translates to a 16-millisecond window for each frame. Given the e-ink display's low refresh rate, achieving smooth animations at 60 fps was not feasible. To address this constraint, we focused on creating simple, minimalistic animations and transitions that prioritized clarity and readability over fluid motion, ensuring that the user experience remained intuitive and responsive despite the display's limitations.
\item \emph{Idle and Load:} The Idle and Load aspects of the RAIL model were less impacted by the low refresh rate display. We concentrated on optimizing background tasks and resource management to minimize load times and ensure that the system remained responsive during periods of inactivity.
\end{itemize}
In conclusion, while meeting Google's RAIL model presented significant challenges due to the low refresh rate e-ink display, the Mani Station project successfully navigated these obstacles by prioritizing user experience and implementing creative solutions. By striking a balance between calm computing principles and performance standards, the project delivers a unique and satisfying user experience that remains both responsive and tranquil.
\section{Fundamental Technology}
\subsection{Hardware}
The hardware behind the Mani Station will rely on minimalism, silence, and facility.
\subsubsection{Tower}
The development of the tower for the Mani Station drew inspiration from the history of personal computers, spanning from the first Macintosh to contemporary models. Numerous computer components were evaluated and combined to create a balanced, cost-effective design that met the project's criteria. The final iteration needed to be functional enough to drive the image to the screen and support the custom operating system while also being spacious enough to house the necessary components.
Throughout the project's development, prototypes primarily utilized the Raspberry Pi 4 Model B. This compact yet powerful platform was equipped with a 1.5GHz processor and up to 8GB of RAM, meeting the specifications for both the system and the e-ink monitor \cite{raspberrypi}. The successful implementation of the Raspberry Pi 4 Model B in the Mani Station demonstrated the feasibility of creating a calm, focused computing experience using accessible and affordable technology.
\subsubsection{E-ink display}
The initial Mani Station was constructed using a Dasung 253 Paperlike monitor. This large 25.3" retina display offered a 3200x1800 resolution without any backlight, providing a comfortable viewing experience in line with the principles of calm computing. The Paperlike monitor also featured anti-glare and high-definition qualities, as well as adjustable contrast settings. Its compatibility with HDMI input ensured seamless integration with the Raspberry Pi, as confirmed by published guides on connecting the two components \cite{raspberrypi}.
However, the Paperlike monitor's price tag of \$1,899.00 USD (at the time of development) posed a challenge for the project. In order to make the Mani Station more accessible, future iterations aimed to lower costs and devise a solution that offered an affordable replacement for traditional personal computer setups. By refining the design and exploring alternative components, the Mani Station strove to deliver a serene computing experience to a wider audience, without compromising on performance or functionality.
\begin{figure}[!ht]
\caption{DASUNG Paperlike 253}
\centering
\includegraphics[width=0.4\textwidth]{paperlike.jpg}
\end{figure}
\subsubsection{Peripherals}
One of the core implementations of the Mani Station is the distinct lack of the computer mouse. Inspiration for this decision comes from the philosophy of the text editor Vim.
The Vim ideology encourages avoiding the usage of a mouse when text editing and places an emphasis on efficiency and minimalism. This method encourages a keyboard-centric workflow, allowing users to quickly and precisely explore and change text using only keystrokes. The Vim concept seeks to eliminate hand movement and context switching between the keyboard and mouse by doing away with the necessity for a mouse, thus increasing productivity and encouraging a more concentrated and streamlined user experience \cite{vim}.
This improvement to the text editor is something extended in the design of the Mani Station by removing the use of the mouse. Instead, the desktop is shortcut-based and utilizes tab rotations in order to give the user the ability to interact with all parts of the computer without taking their hands off the home row.
\subsection{Software}
\subsubsection{i3 Window Manager}
i3 is a dynamic tiling window manager designed for X11, a windowing system commonly used on Unix and Unix-like operating systems. Its primary goal is to enable users to manage application windows efficiently, utilizing a tree-like structure to arrange windows within various workspaces. Keyboard-driven controls allow users to quickly and effortlessly navigate through windows and workspaces, making the most of the available screen real estate while minimizing the need for the mouse. This focus on efficient window management, along with its lightweight resource footprint, makes i3 an ideal window manager for hosting the Electron instance in the Mani Station project. Additionally, i3's straightforward and highly configurable nature allows developers to easily tailor the window manager to suit the specific requirements of the Mani Station's desktop environment, ensuring a cohesive and streamlined user experience that aligns with the calm computing principles \cite{i3-guide}.
\subsubsection{Electron}
The primary prototyping platform for the desktop environment was the Electron native application framework. Electron is an open-source framework that enables developers to create cross-platform desktop applications using front-end web code such as HTML, CSS, and JavaScript. It packages the Chromium rendering engine and uses the Node.js runtime to keep the app’s process alive. This integration with the modern Javascript ecosystem allows developers to leverage a vast ecosystem of libraries and packages, while ensuring that the app ships seamlessly to Linux \cite{electron-docs}.
\subsubsection{Vue.js}
In order to build out the application with Electron, we employed Vue.js. With a strong background in Django, we were extremely familiar with the MVC (Model-View-Controller) paradigm of Vue. Vue offered a flexible, modular approach to the desktop, which is exactly what we required, enabling the creation of maintainable and scalable applications. It also hosts a reactive data-binding system and component-based architecture that allows for aesthetic similarity across the entire desktop environment, making it an ideal choice for the Mani Station's desktop environment \cite{vuejs}.
The combination of Vue.js and Electron facilitated rapid prototyping and seamless communication between different components of the desktop environment. Vue.js's comprehensive documentation and active community support proved invaluable during the development process, ensuring that the final product adhered to calm computing principles while maintaining a high level of usability and adaptability.
\subsubsection{RustyHermit}
The ultimate goal for the software implementation of the Mani Station was to write it in Rust and utilize the RustyHermit framework, a lightweight unikernel, as the core of its operating system. RustyHermit offers several key advantages that align with the calm computing principles guiding the project.
As a unikernel, RustyHermit provides a minimalistic, single-address-space operating system, specifically tailored to run a single application, the desktop environment. This approach eliminates the complexity of traditional multi-process operating systems, resulting in reduced overhead and improved performance. Consequently, the Mani Station can focus solely on delivering a calm computing experience without unnecessary distractions or resource consumption, which also allows for more power to be allocated to graphics output and removing a performance bottleneck in the low-spec system \cite{rust-performance}.
Furthermore, RustyHermit leverages the Rust programming language, known for its emphasis on safety, reliability, and efficiency. Rust's unique features, such as its ownership system and strong typing, minimize the likelihood of memory-related bugs and security vulnerabilities. This ensures that the Mani Station offers a stable, secure, and responsive user experience, in line with the project's goals of fostering a more harmonious relationship with technology \cite{rust}.
Unfortunately, due to our lack of Rust knowledge and prowess, and limited time and resources for development, RustyHermit was not implemented in the final prototype. It is a future aspiration for the project and should be the next step when moving away from Electron.
\section{Methodology}
\subsection{Planning}
\subsubsection{Goals}
The axioms behind the design of the Mani Station were laid out initially in prose, allowing room for interpretation, but still requiring that the developer adhere to a set of strict values.
\begin{quote}
A generation is coming to age \\within their poison garden.\\
We do away with all that.\\
Our computer does not run on attention.\\
Our computer waits patiently\\
for your decision and calmly responds.\\
Not only does it not contribute to the deficit;\\
no, it even will (used rightly) grow the supply.\\
This is accomplished simultaneously and \\synergistically
at the levels of software\\ and hardware.
\end{quote}
Success, in terms of the Mani Station, is not solely defined by technical achievements or broad user adoption, although these are certainly significant. Instead, we consider success as the creation of a technological tool that genuinely assists users in their digital activities, without contributing to attention deficit or encouraging unproductive behavior. This entails developing a computer that respectfully waits for user input, responds efficiently, and ultimately enhances the user's cognitive supply, rather than draining it.
In more concrete terms, we may define success as the creation of a standalone personal computer that is able to replace a user’s home machine that is able to complete fundamental computing tasks (see \ref{appendix:tjhsst}), follow the principles of calm computing, while still being performant and practical.
\subsubsection{Project Roadmap}
The development of this project went through many planning phases, the first of which was the vision. A lot of design and research into functional aesthetics went into the design of the project before development even began. We wanted to ensure that the Mani Station had a strong set of principles that laid its foundation which was realized in the first pamphlet (available at \url{https://github.com/afkomputer/ads/blob/main/manistation.pdf})
\begin{figure}[h!]
\centering
\includegraphics[scale=0.25]{res/pamphlet.png}
\caption{Cover of advertising pamphlet for the Mani Station}
\end{figure}
This pamphlet also doubled as the first iteration of many design guides for the desktop environment; the reader may notice that the same fonts chosen for the initial pamphlet are the fonts that makeup the sans-serif/serif pairings for the dashboard. Granted, while we may have spent too much time on this pamphlet, it lays out a strong foundation for the proliferation of the original calm design principles in the final product.
This meticulous planning and attention to detail during the initial stages of the project ensured that the Mani Station remained true to its purpose of providing a calm computing experience. By maintaining a steadfast focus on these guiding principles, the project was able to create a harmonious blend of software and hardware components that prioritize tranquility, efficiency, and user-centered design.
\subsection{System Design}
When laying out a roadmap for the project, we needed to get a good understanding of how the system would be built out and designed. Starting from the bottom, considering what kernel, distro, and compositor the Mani Station would host brought about a few criteria. What would be the easiest to spin up for prototyping, what was the most customizable, and most importantly, what was the lightest. The Mani Station ought to be a low-spec device in order to limit noise and disturbance, but it also had to be performant in order to not add any additional lag time to the already slow render rate on the monitor.
\subsubsection{System-level architecture}
These considerations brought about the choice of a custom Debian 11 server instance that was to be stripped of redundant processes in order to maximize screen output. The other consideration was that use of the system should not require the terminal in any situation. This meant that the operating system had to hide all loading and diagnostic information, and transition between screens with the least amount of pixels being printed to the screen \cite{deb11-performance}.
Continuing on, upon first load, the user is walked through a simple onboarding process, and should not have to access the terminal at all. TTY’s are also made harder to access so that the user doesn’t have the opportunity to get lost within the system. Connecting to WiFi and updating services were rendered simply using the nmcli interface.
To further streamline the installation process and enhance the user experience, we employed preseeding techniques with the installation script. Preseeding allows for the customization and automation of the operating system installation by preconfiguring various settings and options, thereby eliminating the need for manual user input during the process. By using a preseed file in conjunction with the installation script, we were able to define the desired system configuration, package selection, and other preferences, ensuring a consistent and optimized setup for each Mani Station deployment \cite{deb11-preseed}. This approach not only facilitated a faster and more efficient installation experience but also contributed to the overall goal of providing a calm computing environment by reducing potential frustrations and time-consuming interactions for the end user.
\subsection{Electron Integration}
By utilizing Electron, the development process of the Mani Station's desktop environment was streamlined and efficient, enabling rapid iteration and testing of various user interface elements and functionalities. This was the case because building a page of the desktop was as simple as writing a website. The framework's support for web technologies facilitated the creation of a highly customizable and responsive user experience, in line with the calm computing principles that guide the project. Additionally, the comprehensive documentation and extensive community resources surrounding Electron further expedited the prototyping phase, ensuring a robust and reliable foundation for the Mani Station's desktop environment. Specifically, to make it best emulate the desktop environment, a few lines of code within the configuration of the window allowed it to seamlessly replace the i3 default.
\begin{verbatim}
movable: false,
resizable: false,
maximizable: false,
minimizable: false,
titleBarStyle: 'hidden'
\end{verbatim}
\subsubsection{Dashboard}
When researching different methods for laying out the experience, we returned to the original ideology of minimizing multitasking. This meant that the desktop environment shouldn’t window applications, and it should be difficult to switch between tasks/applications. Since Electron was the platform for the prototype, this meant that we would ideally ship the environment as a single Electron app that would handle context switching and maintain state. Unfortunately, due to performance issues and logistical issues of running sub processes within one Electron instance, the implementation of the final prototype consisted of a separate application for the dashboard and each of the applications.
The dashboard serves as the central hub, hosting essential desktop information, a greeter, an application launcher, a fuzzy search bar for tasks, and the ability to display context from other applications. To ensure a calming and visually appealing user experience, the dashboard was meticulously designed with a streamlined and aesthetically pleasing layout. The initial design was created using Figma design software, enabling rapid iteration and fine-tuning of the interface.
\begin{figure}[!h]
\centering
\includegraphics[scale=0.2]{res/dashboard.png}
\caption{Screenshot of the Mani Station Dashboard}
\end{figure}
The layout features a minimal application launcher in the top right corner, a drop-in terminal in the bottom right, a calendar and to-do list widget in the bottom left, and a centrally located action search bar at the bottom-middle of the screen. The action search bar employs fuzzy search capabilities to assist users in completing tasks on the device, catering to older audiences who may be less familiar with traditional icons.
The primary goal of the search bar is to guide users towards the appropriate application or methodology for accomplishing their entered task. To achieve this, each application is associated with a set of search terms and strings that can be used by the \verb|fzf| algorithm to match the user's input text to the desired application.
\subsection{Core Applications}
Development of the Mani Station’s applications probably took the longest time as each application came with its own implementation challenges. In order to best prioritize what applications would be best for development, we conducted a survey using a randomly sampled group of highschool seniors from Thomas Jefferson High School for Science and Technology (see Appendix A1).
Based on these answers, we can consider the different ways that this sample puts their technology to use, and we come up with the following applications that are necessary for the prototype:
\begin{itemize}
\item \emph{Web Browser:} A lightweight browser that efficiently renders web pages while adhering to the calm computing principles, focusing on simplified navigation, reduced visual clutter, and resource-conscious operation.
\item \emph{Document Editor:} A streamlined document editor application that prioritizes ease of use, minimalist design, and essential formatting options to facilitate focused writing and editing without distractions.
\item \emph{Mail Client:} An intuitive email application that simplifies communication and inbox management, offering a clean interface, straightforward organization, and essential features that align with the principles of calm computing.
\end{itemize}
Finally, a fourth addition, would link the entire operating system together:
\begin{itemize}
\item \emph{To-Do Manager:} A task management application designed to help users stay organized and on track with their daily tasks and long-term goals. The todo client emphasizes a minimalist interface, intuitive categorization, and easy-to-use input methods, all in line with the calm computing principles, to reduce stress and promote a sense of accomplishment.
\end{itemize}
\subsubsection{Web Browser}
The development of the web browser for the Mani Station posed several challenges and required careful consideration with respect to balancing user safety and user experience. Initially, the idea of developing our own browser was contemplated. However, building a browser from scratch would be an extremely time-consuming task that may have extended to the entire length of the project. It would require handling complex functionality like HTML rendering, JS sandboxing, runtimes, and execution, and CSS interpretation, amongst an array of other tasks.
In this context, \verb|surf| emerged as an interesting alternative. Surf is a simple web client based on GTK+ which has only the ability to display sites and follow links. It was a lightweight, straightforward, and minimalist surfer, focusing primarily on the core functionality of a browser. The XEmbed protocol support made it possible to embed surf into another application which extended its flexibility and possibilities. Moreover, surf’s capability to navigate to different URI by setting its XProperties provided a certain level of control over the browsing experience \cite{surf}. Despite these advantages, surf's simplicity also meant it lacked some of the essential features expected in a modern web browser, such as tabbed browsing, built-in search functionality, and security features. This potential limitation to the user experience led us to explore other alternatives.
Electron's BrowserWindow functionality emerged as a potential solution during our exploration. This module allows for the creation of a new renderer process, which essentially could handle the webpage rendering. It seemed promising as it allowed leveraging web technologies like JavaScript, HTML, and CSS. However, while BrowserWindow handles page rendering, the rest of the browser functionality would still need to be implemented. Basic features such as tabbing, history management, and link following would require custom development. Furthermore, this would create a rather piecemeal browser structure, which could lead to potential stability and compatibility issues down the line. Just like surf, Electron's BrowserWindow started to show similar limitations in terms of comprehensive features and user experience.
Given these considerations, our attention shifted towards pre-existing, feature-rich, and secure open-source browsers. After careful evaluation, we decided on using Qutebrowser. Qutebrowser is a keyboard-focused browser with a minimal GUI, which provides advanced features while maintaining a simple user interface. It also has a robust security model, which is paramount when dealing with web content. Another crucial factor that favored the selection of Qutebrowser was its alignment with our peripheral philosophy, particularly the Vim-like mode of operation that emphasizes keyboard-only use. Qutebrowser incorporates a Vim-inspired interface, supporting a range of keyboard shortcuts for intuitive and efficient navigation. This feature seamlessly complements our focus on keyboard-centric computing, promoting a more focused and efficient interaction paradigm \cite{qutebrowser}.
The integration of Qutebrowser into the Mani Station was a considerable success. It provided users with a full-featured web browsing experience without compromising the calm and focused computing environment we aimed to create. This choice demonstrated that the appropriate selection and adaptation of existing open-source software could meet our specific needs, eliminating the need for impractical development from scratch or potentially insecure solutions.
\subsubsection{Document Editor}
The Document Editor forms a significant part of our application suite, providing tools for both text processing and code editing. In today’s age, both applications are usually a requirement for workflows which is what led us to split the Document Editor into two sub-applications. This decision allows us to tailor each component to its specific use case, optimizing for the unique needs of general text editing and programming respectively.
\paragraph{Word Processor}
In developing the word processor for the Mani Station, we sought a solution that would offer comprehensive functionality while adhering to the principles of calm computing. We found that answer in LibreOffice Writer, an open-source word processor that has earned a strong reputation for its powerful features and compatibility with various document formats \cite{writing-in-linux}.
Given that LibreOffice Writer is open source, we were able to create a fork of the project in order to tweak the feature and look to our specifications. A key aspect of calm computing is reducing screen clutter and visual distractions. To this end, we streamlined the interface of LibreOffice Writer, simplifying toolbars and removing non-essential elements.This came about through a combination of theming and preference editing to reduce animations and forcing pagination rather than scrolling. We wanted to edit application code as well, but LibreOffice Writer has its UI laid out in C++ which was a language that I was less familiar with for this application.
\paragraph{Code Editor}
The code editor is another crucial component of the Mani Station, providing a tool for users to write and debug code efficiently. For this task, we chose Sublime Text 4, a highly customizable and versatile text editor that is widely praised for its speed, ease of use, and powerful features. Much like our approach with LibreOffice Writer, we took advantage of Sublime Text's plasticity to align it with the principles of calm computing \cite{sublime}.
In our initial customization efforts, we implemented a minimalist theme with subdued colors and simplified icons to reduce visual clutter. We further streamlined the interface by removing seldom-used elements such as certain toolbars and panels. In parallel, we addressed animations and transitions, disabling or toning down features like smooth scrolling and highlight animations, considered superfluous for our calm computing environment. This resulted in a tranquil, focused workspace conducive to productivity.
Users can write, debug, and understand code with greater focus, benefiting from the full suite of Sublime Text's features without unnecessary distractions.
\subsubsection{Mail Client}
For the Mani Station's mail client, we elected to utilize the Geary mail client, an application developed in GTK for the GNOME operating system. Our selection of Geary was grounded in its inherent simplicity and the customization opportunities it affords, allowing us to align the application with our calm computing principles \cite{geary}.
Geary's straightforward interface and user-friendly functionality made it a suitable starting point for our project. We leveraged its customizability to strip back extraneous elements, reducing visual clutter and promoting a serene, focused user experience. This involved re-skinning the client, removing rarely used toolbars and panels, and muting colors to create a tranquil, distraction-free workspace.
Despite the success of the Geary-based mail client, we are always open to exploring new possibilities for enhancement. One such avenue for future development is the implementation of "mutt," a small but very powerful text-based mail client. Its use could provide an even more streamlined and keyboard-centric user experience, aligning with our overarching goal of creating a calm computing environment on the Mani Station.
\subsubsection{To-Do Manager}
The development of the to-do app for the Mani Station was initiated by following an online tutorial titled "Build a Todo App with Electron." This provided the basic framework for the application. To enhance functionality, we integrated the app with the Todoist API, enabling synchronization with cloud-based tasks \cite{todo-electron}\cite{todoist}.
A key aspect of this development was the use of Datastore.js, a JavaScript database library. This allowed the to-do app to interact seamlessly with other applications on the Mani Station, such as the dashboard, which could display to-do information contextually, enhancing the user's overview of their tasks.
This approach of inter-application communication was fundamental in our goal to create a harmonious, integrated software ecosystem. By enabling applications to access and present shared data, we could build a more user-friendly, cohesive experience, with the to-do app serving as an example of this philosophy. The integration fostered by Datastore.js is a significant step towards developing applications that are specifically tailored for the Mani Station, promoting a calm computing environment.
\section{Results}
\subsection{Introduction}
The results section aims to evaluate the success of the Mani Station based on the goals outlined in 4.1.1. It should be noted that the current iteration of the device as of publication is a prototype intended for proof-of-concept.
\subsection{User Experience Feedback}
The design approach and careful consideration of our values shaped the Mani Station’s user experience. From the omission of the mouse, to the lack of a typical large computer tower, to the lack of backlight and low refresh rate, users took notice to a slew of changes that the Mani Station presented.
Users were asked to respond to an email from a professor asking for further research on a topic of their choice by finding information online, typing up a paragraph response, and formulating an email response using the Mani Station. They were then tasked with doing the same on their personal device of choice.
Surprisingly, during first trials, users reported an average increase in stress when asked to complete these tasks within a time limit. When asked for further comments, users reported a high initial learning curve and difficulty of use as the layout was slightly foreign. This was expected as standard personal computer users would have trouble understanding other types of computing systems and feel comfort when doing the same task on their own machines.
Each of the subjects were asked to do same set of tasks again between 1-3 days later, and while some users still found the machine slightly difficult to use due to lack of familiarity, across the board we noticed that users actually felt more calm and less distracted when completing tasks on the second go around. One user, whose control device was their mobile phone, actually paused during the second experiment to respond to a text that they had received.
Feedback on the customizations and simplifications of the applications were also well received. The minimalist themes in the Document Editor and the Web Browser we noted for reducing visual clutter and distractions.
In conclusion, despite an initial learning curve and stress increase observed in first-time users, the Mani Station's unique approach to user experience marked by a departure from conventional computing methods led to more focused and calm user interactions in subsequent uses.
\subsection{Performance}
In terms of raw hardware performance, the Mani Station is not intended to compete directly with traditional Windows machines or other personal computers. The low refresh rate e-ink display and minimalistic hardware setup deliberately step away from the typical power-centric approach. While this might have resulted in slower load times or less dynamic animations when compared to a Windows PC, it's important to note that these are intentional design decisions aimed at reducing distractions and fostering a calmer computing environment.
Nevertheless when base loads were compared between a Dell Latitude 3300, This machine was one of many provided by Fairfax County Public Schools to all current highschool students, running Windows 10 Education, we noticed a 249.2\% decrease in CPU usage and a 132\% decrease in RAM usage. This was mainly due to the fact that Windows OS includes a myriad of background services, telemetry, and startup applications unbeknownst to the user. Our operating system sustains a majority of its load from the Xorg compositor as observed using the htop utility.
The refresh rate of the monitor is not provided by the manufacturer, and we did not have proper tools or methodology for testing a base refresh rate. Along with this, the monitor does not refresh the entire screen in the standard fashion as one might expect, instead portions of the screen are refreshed when it is changed. Therefore, we do not have a firm quantitative analysis for the comparison of our monitor compared to a typical 60Hz computer monitor.
\subsection{Implementation Analysis}
In developing the Mani Station, we chose to adapt established applications—web browser, document editor, mail client, and to-do app—to suit our calm computing environment. This approach enabled us to utilize their proven functionality while customizing their user interfaces to match our design ethos. Additionally, the integration of these applications via Datastore.js showcases the potential for a cohesive software ecosystem, vital for Mani Station's future development.
\subsection{Conclusion}
The Mani Station's trial results indicate its potential as an effective tool for calm computing. While initial usage yielded reports of a steep learning curve and heightened stress, repeated exposure demonstrated a significant shift towards a calmer and less distracted user experience. It's noteworthy that the station's design elements, such as the keyboard-only navigation, minimalistic themes, and lack of visual clutter, were positively received. This highlights the user's adaptability and the potential benefits of breaking away from traditional PC paradigms in favor of an environment conducive to productivity and tranquility.
\section{Final Remarks}
As we reflect on the journey of creating the Mani Station, we are deeply grateful for the opportunity to have been a part of this unique project. It has truly been a labor of love, brought to life by the integration of diverse skills, viewpoints, and relentless dedication from everyone who helped along the way. We were not just developers or engineers; but designers, psychologists, and philosophers, wearing each hat interchangeably as we manifested the vision of calm computing.
The multiple dimensions of knowledge and skill required for this project provided a holistic perspective, considering not only the technological facets but also the sociological, psychological, and aesthetic aspects of the design decisions. This unique intersectional approach greatly influenced the Mani Station's design, grounding it in principles that prioritize user experience and wellbeing.
As I envision the future trajectory of the Mani Station, a few key objectives stand out. A prominent goal is to build and develop our core applications from scratch. While we have currently adapted and customized existing applications, creating applications that are natively designed for calm computing will enhance the authenticity and efficacy of the Mani Station experience.
The endeavor to develop our own E-ink monitor represents a significant technological challenge but is vital to maintain the integrity of our design philosophy. An E-ink monitor designed specifically for the Mani Station will be optimized to work with our unique hardware-software ecosystem, improving the overall user experience.
Beyond just the technological developments, I believe that the Mani Station holds immense potential for customization and adaptation to specific applications. For instance, deploying customized Mani Stations in libraries could potentially revolutionize the library experience, aligning the calm computing principles with the inherent tranquility and focus required in such environments.
Similarly, designing a version of the Mani Station specifically for elderly homes could drastically improve their interaction with technology, offering a calm, straightforward, and less distracting computing experience.
In essence, the future of the Mani Station presents a multifaceted approach that merges technological advancements, user-centric designs, and adaptive deployments. This endeavor to continue pushing the boundaries of calm computing holds immense promise for shaping the landscape of human-computer interaction.
\section*{Appendix}
\appendix
\section{TJHSST Technology Use Survey Results}\label{appendix:tjhsst}
Every student was asked, “If you could only have one application on your computer, what would it be?” Here are the results of that survey:
\begin{figure}[h!]
\centering
\caption{Survey for Single Application}
\rowcolors{2}{gray!25}{white}
\begin{tabular}{lc}
\rowcolor{gray!50}
Total(n) & 42 \\
Web Browser & 17 \\
File / Task Manager / Utilities & 9 \\
Video Games / Other & 11 \\
Word Processor / Code Editor & 5
\end{tabular}
\end{figure}
In the initial survey, the responses from the high school seniors at Thomas Jefferson High School for Science and Technology were diverse. While a significant portion of the responses included various video games, these cannot be discounted as they reflect a genuine interest among this age group. Further analysis revealed three main categories of responses: web browsers, operating system utilities, and code editors. Interestingly, "Task Manager" was mentioned by three distinct individuals, demonstrating the importance of system monitoring tools even among younger users.
Given the versatile nature of web browsers, a follow-up survey was conducted with a different group of seniors from the same school. The results were as follows:
\begin{figure}[h!]
\centering
\caption{Survey for Single Website}
\rowcolors{2}{gray!25}{white}
\begin{tabular}{lc}
\rowcolor{gray!50}
Total(n) & 14 \\
YouTube / Social Media / Web Games & 6 \\
Email & 3 \\
Learning Management System & 1 \\
Search Engine & 4
\end{tabular}
\end{figure}
The responses indicate a significant interest in social media sites and web games, once again highlighting their importance to this age group. However, focusing on more productivity-oriented applications, we can categorize these responses into three main groups: email, learning management or work platform, and search engines.
These findings suggest that while recreational use of technology is prevalent among younger users, there is also a strong need for more task-oriented applications. Further research would be necessary to fully understand these preferences and to avoid any potential bias in the interpretation of the data.
{\footnotesize \bibliographystyle{ieeetr}
\bibliography{proposal}}
\end{document}

BIN
res/dashboard.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 185 KiB

BIN
res/pamphlet.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 115 KiB

BIN
res/paperlike.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 37 KiB

129
usenix.sty Normal file
View File

@ -0,0 +1,129 @@
% usenix.sty - to be used with latex2e for USENIX.
% To use this style file, look at the template usenix2019_v3.1.tex
%
% $Id: usenix.sty,v 1.2 2005/02/16 22:30:47 maniatis Exp $
%
% The following definitions are modifications of standard article.sty
% definitions, arranged to do a better job of matching the USENIX
% guidelines.
% It will automatically select two-column mode and the Times-Roman
% font.
%
% 2018-12-19 [for ATC'19]: add packages to help embed all fonts in
% pdf; to improve appearance (hopefully); to make refs and citations
% clickable in pdf
%
% 2020-09-21 file updated to comment out flushend and make it optional
%
% USENIX papers are two-column.
% Times-Roman font is nice if you can get it (requires NFSS,
% which is in latex2e.
\if@twocolumn\else\input twocolumn.sty\fi
\usepackage{mathptmx} % times roman, including math (where possible)
% hopefully embeds all fonts in pdf
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage{pslatex}
% appearance
\usepackage[kerning,spacing]{microtype} % more compact and arguably nicer
% Uncomment the following line if you want the columns of the last page
% equal in size. But note that doing so may cause issues with some
% document-generating tools.
% \usepackage{flushend}
% refs and bib
\usepackage{cite} % order multiple entries in \cite{...}
\usepackage{breakurl} % break too-long urls in refs
\usepackage{url} % allow \url in bibtex for clickable links
\usepackage{xcolor} % color definitions, to be use for...
\usepackage[]{hyperref} % ...clickable refs within pdf...
\hypersetup{ % ...like so
colorlinks,
linkcolor={green!80!black},
citecolor={red!70!black},
urlcolor={blue!70!black}
}
%
% USENIX wants margins of: 0.75" sides, 1" bottom, and 1" top.
% 0.33" gutter between columns.
% Gives active areas of 7" x 9"
%
\setlength{\textheight}{9.0in}
\setlength{\columnsep}{0.33in}
\setlength{\textwidth}{7.00in}
\setlength{\topmargin}{0.0in}
\setlength{\headheight}{0.0in}
\setlength{\headsep}{0.0in}
\addtolength{\oddsidemargin}{-0.25in}
\addtolength{\evensidemargin}{-0.25in}
% USENIX wants no page numbers for camera-ready papers, so that they can
% number them themselves. But submitted papers should have page numbers
% for the reviewers' convenience.
%
%
% \pagestyle{empty}
%
% USENIX titles are in 14-point bold type, with no date, and with no
% change in the empty page headers. The whole author section is 12 point
% italic--- you must use {\rm } around the actual author names to get
% them in roman.
%
\def\maketitle{\par
\begingroup
\renewcommand\thefootnote{\fnsymbol{footnote}}%
\def\@makefnmark{\hbox to\z@{$\m@th^{\@thefnmark}$\hss}}%
\long\def\@makefntext##1{\parindent 1em\noindent
\hbox to1.8em{\hss$\m@th^{\@thefnmark}$}##1}%
\if@twocolumn
\twocolumn[\@maketitle]%
\else \newpage
\global\@topnum\z@
\@maketitle \fi\@thanks
\endgroup
\setcounter{footnote}{0}%
\let\maketitle\relax
\let\@maketitle\relax
\gdef\@thanks{}\gdef\@author{}\gdef\@title{}\let\thanks\relax}
\def\@maketitle{\newpage
\vbox to 2.5in{
\vspace*{\fill}
\vskip 2em
\begin{center}%
{\Large\bf \@title \par}%
\vskip 0.375in minus 0.300in
{\large\it
\lineskip .5em
\begin{tabular}[t]{c}\@author
\end{tabular}\par}%
\end{center}%
\par
\vspace*{\fill}
% \vskip 1.5em
}
}
%
% The abstract is preceded by a 12-pt bold centered heading
\def\abstract{\begin{center}%
{\large\bf \abstractname\vspace{-.5em}\vspace{\z@}}%
\end{center}}
\def\endabstract{}
%
% Main section titles are 12-pt bold. Others can be same or smaller.
%
\def\section{\@startsection {section}{1}{\z@}{-3.5ex plus-1ex minus
-.2ex}{2.3ex plus.2ex}{\reset@font\large\bf}}