forked from papyros/papyros.github.io
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathatom.xml
144 lines (94 loc) · 9.61 KB
/
atom.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title><![CDATA[Papyros]]></title>
<link href="http://papyros.io/atom.xml" rel="self"/>
<link href="http://papyros.io/"/>
<updated>2015-01-07T09:36:10-06:00</updated>
<id>http://papyros.io/</id>
<author>
<name><![CDATA[Papyros]]></name>
</author>
<generator uri="http://octopress.org/">Octopress</generator>
<entry>
<title type="html"><![CDATA[Weekly Status Update]]></title>
<link href="http://papyros.io/blog/2014/12/weekly-status-update/"/>
<updated>2014-12-19T19:55:59-06:00</updated>
<id>http://papyros.io/blog/2014/12/weekly-status-update</id>
<content type="html"><![CDATA[<p>We’lll be starting weekly status updates to share progress on the various components of Quantum OS.</p>
<h3>QML Material</h3>
<p>21 commits where made to our Material Design framework during the past week. The following features
were implemented:</p>
<ul>
<li>Implement the Switch control and update the design to match Material Design [<a href="https://github.com/boghison">@boghison</a>, <a href="https://github.com/iBeliever">@iBeliever</a>]</li>
<li>Switch to GitFlow, and set up a CONTRIBUTING.md document [<a href="https://github.com/iBeliever">@iBeliever</a>]</li>
<li>Load more of the Roboto fonts [<a href="https://github.com/glenfordwilliams">@glenfordwilliams</a>]</li>
<li>Initial work on a component demo app [<a href="https://github.com/iBeliever">@iBeliever</a>]
<ul>
<li>Initial demos cover the Button, Switch, Icon, and Progress Bar components</li>
</ul>
</li>
<li>Improvements to the Snackbar component [<a href="https://github.com/boghison">@boghison</a>]</li>
</ul>
<p>Ongoing work includes:</p>
<ul>
<li>Migrating to QtQuick.Controls</li>
<li>Rewriting the PageStack code to use QtQuick.Controls and sort out the way transitions, etc are handled [<a href="https://github.com/quantum-os/qml-material/issues/36">#36</a>, <a href="https://github.com/quantum-os/qml-material/issues/37">#37</a>]</li>
<li>Investigating how to handle the various styles of the Robot font [<a href="https://github.com/quantum-os/qml-material/issues/46">#46</a>]</li>
</ul>
<p>Thanks to all the developers who have contributed code to the project this week and in past weeks!
I’d like to especially mention <a href="https://github.com/geiseri">@geiseri</a> who has been helping us migrate to QtQuick.Controls along
with contributing other great feedback and discussion about how we’re implementing various features.</p>
<h3>Quantum Shell</h3>
<p>No commits landed in the main branch for Quantum Shell, as discussion was ongoing and any work was made
to separate repositories or branches. The following items were discussed or worked on:</p>
<ul>
<li>Implementing the Music indicator [<a href="https://github.com/quantum-os/quantum-shell/issues/14">#14</a>, <a href="https://github.com/quantum-os/quantum-shell/issues/16">#16</a>]</li>
<li>Implementing the Network indicator [<a href="https://github.com/quantum-os/quantum-shell/issues/17">#17</a>]</li>
</ul>
<p>Planning also continues on different designs and layouts and deciding what features to implement.</p>
<h3>SDDM Theme</h3>
<p>Not much happening here, as the focus during the past week has been on other components. However, <a href="https://github.com/boghison">@boghison</a> did turn the initial prototype into a working SDDM theme, which is awesome.</p>
<h3>General OS progress</h3>
<p>A large part of my time this week was spent on the following items:</p>
<ul>
<li>Trying to get QtCompositor compiled and working on Arch Linux, which will be the base for our OS</li>
<li>Studying and learning how to use OSTree, which will be the distribution/release technology used in Quantum OS</li>
</ul>
<p>Other ongoing issues include:</p>
<ul>
<li>Picking a new name. With the majority of my time spent on other tasks, I have not spent much time on this. I have several names to research in the US trademark databases and perform general internet seaches on. Currently, my favorite candidate is Papyros, as a modified version of papyrus, an anchient form of paper, which fits with Material Design and the concept of paper used.</li>
<li>Getting a list of packages we will need to ship together</li>
<li>Designing various aspects of the desktop shell, applications, and OS in general</li>
</ul>
<p>In closing, we’re making good progress towards building an awesome OS! Thanks to everyone interested in the project and who have offered support, ideas and suggestions, design feedback, or code contributions. That’s the power of open source!</p>
<p>Have any suggestions, bug reports, or ideas for what you’d like to see next in the various projects? Comment here or on Google+, or open issues on our GitHub projects at <a href="https://github.com/quantum-os">https://github.com/quantum-os</a>.</p>
<p>Christmas is coming up next week, so I may not do a progress report next Friday and will probably not make a whole lot of progress on Quantum OS work as well. I’ll be back in full force the next week, though!</p>
<p>Have a blessed Christmas and a happy New Year!</p>
]]></content>
</entry>
<entry>
<title type="html"><![CDATA[Introduction and Initial Plans]]></title>
<link href="http://papyros.io/blog/2014/11/introduction-and-initial-plans/"/>
<updated>2014-11-19T18:48:41-06:00</updated>
<id>http://papyros.io/blog/2014/11/introduction-and-initial-plans</id>
<content type="html"><![CDATA[<p>Welcome to Quantum OS! We are working on developing an operating system based upon Linux which conforms to Google’s <a href="http://google.com/design/">Material Design guidelines</a>. The focus will be on creating a stable and easy-to-use operating system with a heavy emphasis on well-thought-out design.</p>
<p><strong>UPDATE</strong>: This project was originally named Quartz OS but has since been renamed to Quantum OS because of conflicts with the OS X graphics technologies.</p>
<h3>The Desktop Shell</h3>
<p>We plan to develop the desktop shell and applications primarily using Qt 5 and QML, which will allow us to build highly polished and dynamic user interfaces and will work well for implementing Material Design. If possible, we will build the desktop shell in as much QML as possible built on top of the QtCompositor API, which provides a Qt framework for building a Wayland compositor.</p>
<p>We already have some working code with an experimental desktop layout:</p>
<p><img src="http://papyros.io/images/desktop_layout_1.png"></p>
<h3>Applications</h3>
<p>Our application framework will be based upon a QML UI toolkit implementing Material Design. It is written completely from scratch, and does not use QtQuick Controls, and is not a fork or theme for the Ubuntu UI toolkit. The reason for this is that we want to be able to focus specifically on implementing Material Design, which has several unique features, such as the concept of elevation. We will most likely have a Qt/Gtk theme for existing apps, but the official recommendation will be writing new applications or porting existing applications to the Material Design framework. The API will be similar to that of other QML frameworks such as the Ubuntu UI toolkit, so it will not be too difficult porting existing apps.</p>
<p>The UI framework itself will be cross-platform, just as Qt itself is, so apps written with it will run on OS X, Windows, or other Linux distributions. This plays well with the concept of Material Design, which aims to be a cross-platform design framework.</p>
<p>We also plan to support web apps and treat them as nicely as possible. This will probably involve a simple wrapper that allows web apps to have their own icon and window with no browser chrome.</p>
<p>The Material Design QML framework is well underway, as can be seen from this sample application:</p>
<p><img src="http://papyros.io/images/blueprint_1.png"></p>
<h3>The Base Operating System</h3>
<p>We plan to initially leverage an existing operating system, most likely Arch or Ubuntu. Arch is a strong possibility because of the simple packaging manager, lightweight base system, and the rolling release concept. Our goal is to base our work on the latest upstream versions available, with no patches or modifications, so our work will run on any base Linux distro that supports Wayland.</p>
<p>We will also need to build a login manager and installer. Our plan is to write a theme for SDDM, which supports themes written in QML. We don’t have any plans for an installer yet, as that will need to wait until a base OS is chosen.</p>
<h3>The Development Team and Code</h3>
<p>Currently the team consists of mainly just myself (<a href="https://plus.google.com/u/0/+MichaelSpencer">Michael Spencer</a>/<a href="https://github.com/iBeliever">@iBeliever</a>), though I am already getting some great design feedback and mockups from <a href="https://plus.google.com/u/0/+AndreaDelSarto88">Andrea Del Sarto</a>. Anyone who is interested in contributing code, design, feedback, or testing is welcome to contribute, though I plan to remain in control of project management to ensure that we stay focused on our goals. I am certainly open to suggestions and feedback, though!</p>
<p>We are hosting our code on GitHub at <a href="https://github.com/quantum-os">https://github.com/quantum-os</a>, with the Material Design QML framework hosted at <a href="https://github.com/quantum-os/qml-material">https://github.com/quantum-os/qml-material</a>. You can also track our mockups <a href="https://github.com/quantum-os/mockups">here</a>, though because of the flexibility and power of QML, we often work directly in code versus designing mockups first.</p>
]]></content>
</entry>
</feed>