git.s-ol.nu mmm / 38ae5b2
section intros s-ol 1 year, 9 months ago
6 changed file(s) with 42 addition(s) and 25 deletion(s). Raw diff Collapse all Expand all
00 # 7. conclusion
11
22 <div class="well well-warning">[section under construction]</div>
3
4 In the beginning of this thesis multiple downsides of the most widely used end-user computing systems have been
5 demonstrated and attributed to an over-reliance on a set of design paradigms that do not align well with the goal of
6 empowering users. On the other hand, it has been shown that many well-recognized historic systems were designed with
7 this goal in mind.
8
9 Based on the aspirations and appraoches of these historic systems, a framework for the evaluation of empowering end-user
10 computing systems was developed alongside one such system itself. While the proposed system has been shown to have many
11 flaws and limitations of its own, and is not currently viable as a tool for end-users, it serves to demonstrate the
12 feasiblity of type coercion and the file system as a focus point for new end-user computing systems, and provides a
13 reference point for further research.
00 # 6. evaluation
1 In this section I will first take a look at the implementations of the examples for the use cases outlined above,
2 and evaluate them with regard to the framework derived in the corresponding section above. After that, some general
3 concerns and insights that have become apparent while developing the system and working with it will be reviewed.
14
25 ## 6.1 examples
3 In this section I will take a look at the implementations of the example for the use cases outlined above,
4 and evaluate them with regard to the framework derived in the corresponding section above.
5
66 ### 6.1.1 publishing and blogging
7 Since mmmfs has grown out of the need for a versatile CMS for a personal publishing website, it is not surprising to
8 see that it is still up to that job. Nevertheless it is worth taking a look at its strengths and weaknesses in this
9 context:
7 Since mmmfs has grown out of the need for a versatile content-management system for a personal website and blog, it is
8 not surprising to see that it is still up to that job. Nevertheless it is worth taking a look at its strengths and
9 weaknesses in this context:
1010
1111 The system has proven itself perfect for publishing small- and medium-size articles and blog posts, especially for its
1212 ability to flexibly transclude content from any source. This includes diagrams (such as in this thesis),
1313 videos (as in the documentation in the appendix), but also less conventional media such as
1414 interactive diagrams<mmm-embed path="../references/aspect-ratios" wrap="sidenote"></mmm-embed> or twitter postings.
1515
16 <!-- @TODO -->
1716 On the other hand, the development of the technical framework for this thesis has posed greater challenges.
18 In particular, the implementation of the reference and sidenote systems are brittle and uninspiring.
19
17 While the reference and sidenote systems integrated well with the rest of the system, some features like automated
18 table-of-contents and section numbering were less obvious to tackle and finally completed manually.
2019 This is mostly due to the approach of splitting up the thesis into a multitude of fileders, and the current lack of
21 mechanisms to re-capture information spread throughout the resulting history effectively.
22 Another issue is that the system is currently based on the presumption that content can and should be interpreted
23 separately from its parent and context in most cases. This has made the implementation of sidenotes less idiomatic
24 than initially anticipated.
20 mechanisms to re-capture information spread throughout the resulting hierarchy effectively.
2521
2622 ### 6.1.2 pinwall
2723 The pinwall example shows some strengths of the mmmfs system pretty convincingly.
7268 ## 6.2 general concerns
7369 While the system has proven pretty successful and moldable to the different use-cases that it has been tested in,
7470 there are also limitations in the proposed system that have become obvious in developing and working with the system.
75 Some of these have been anticipated for some time and concrete research directions for solutions are apparent,
76 while others may be intrinsic limitations in the approach taken.
71 In this section these limitations will be discussed individually, and directions for further research and solutions will
72 be given where apparent.
7773
7874 ### 6.2.1 global set of converts
7975 In the current system, there is only a single, global set of *converts* that can be potentially applied to facets
00 # 3. evaluation framework
11
2 In the following section, I will collect approaches and reviews of different end-user software systems from current
3 literature, as well as derive and present my own requirements and guiding principles for the development of a new
4 system.
2 In this section, I will collect approaches and reviews of different end-user software systems from current literature,
3 as well as derive and present my own requirements and guiding principles for the development of a new system.
4
5 Firstly, I will take a look at a framework for evaluating end-user computing systems from literature, before presenting
6 three concrete design principles and components for a new system.
57
68 3.1 qualities of successful end-user computing
79 ----------------------------------------------
00 # 4. system description
11
2 `mmmfs` is a newly developed personal data storage and processing system. It was developed first as a tool for
3 generating static websites, but has been extended with live interaction and introspection, as well as embedded
4 editing capabilities as part of this work.
2 Alongside this thesis a new end-user computing system has been developed together with the framework presented above.
3 The system, `mmmfs`, is a personal data storage and processing system that was initially developed as a tool for
4 generating static websites, but has now been extended with capabilities for live interaction and introspection, as well
5 as embedded editing, as part of this work.
56
67 mmmfs has been designed with a focus on data ownership for users. One of the main driving ideas is to unlock data
78 from external data silos and file formats by making data available uniformly across different storage systems and
8 formats. Secondly, computation and interactive elements are also integrated in the paradigm, so that mmmfs can be
9 seamlessly extended and molded to the users needs.
9 formats. Secondly, computation and interactive elements are also integrated in this paradigm, so that mmmfs can be
10 seamlessly extended and molded to the user's needs.
1011
1112 The abstraction of data types is accomplished using two major components, the *Type System and Coercion Engine* and
12 the *Fileder Unified Data Model* for unified data storage and access.
13 the *Fileder Unified Data Model* for unified data storage and access. In the next sections the design and implementation
14 of these two components will be described in detail.
1315
1416 ## 4.1 data storage model
1517 The Fileder Model is the underlying unified data storage model.
00 # 1. motivation
1
2 The project that this thesis accompanies was created out of a frustration with the computing systems that are currently
3 popular and widely available to end-users. The following sections document and exemplify the perceived shortcomings that
4 these systems exhibit, as attributed to specific concepts or paradigms that the systems seem to be designed around.
15
26 1.1 application-centric design
37 ------------------------------
812 <mmm-embed path="app-types" wrap="marginnote"></mmm-embed>
913 All of these operating systems share the concept of *Applications* (or *Apps*) as one of the core pieces of their
1014 interaction model. Functionality and capabilities of the digital devices are bundled in, marketed, sold and distributed
11 as applications. This focus on applications as the primary unit of systems can be seen as the root cause of multiple problems.
15 as applications. This focus on applications as the primary unit of systems can be seen as the root cause of multiple
16 problems.
1217
1318 For one, since applications are produced by private companies on the software market,
1419 developers compete on features integrated into their applications. To stay relevant, monolithic software or software
3333 <ol style="list-style: none;">
3434 <li><a href="#abstract">abstract</a></li>
3535 <li><a href="#table-of-contents">table of contents</a></li>
36 <li><a href="#overview">overview</a></li>
3637 <li><a href="#1-motivation">1. motivation</a></li>
3738 <ol style="list-style: none;">
3839 <li><a href="#11-application-centric-design">1.1 application-centric design</a></li>