<feed xmlns='http://www.w3.org/2005/Atom'>
<title>subsurface.git/qt-mobile/qml/theme/qmldir, branch master</title>
<subtitle>forked from https://github.com/subsurface/subsurface</subtitle>
<id>https://git.tsegers.com/subsurface.git/atom?h=master</id>
<link rel='self' href='https://git.tsegers.com/subsurface.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/subsurface.git/'/>
<updated>2016-04-05T05:33:58Z</updated>
<entry>
<title>Move subsurface-core to core and qt-mobile to mobile-widgets</title>
<updated>2016-04-05T05:33:58Z</updated>
<author>
<name>Dirk Hohndel</name>
<email>dirk@hohndel.org</email>
</author>
<published>2016-04-05T05:02:03Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/subsurface.git/commit/?id=7be962bfc2879a72c32ff67518731347dcdff6de'/>
<id>urn:sha1:7be962bfc2879a72c32ff67518731347dcdff6de</id>
<content type='text'>
Having subsurface-core as a directory name really messes with
autocomplete and is obviously redundant. Simmilarly, qt-mobile caused an
autocomplete conflict and also was inconsistent with the desktop-widget
name for the directory containing the "other" UI.

And while cleaning up the resulting change in the path name for include
files, I decided to clean up those even more to make them consistent
overall.

This could have been handled in more commits, but since this requires a
make clean before the build, it seemed more sensible to do it all in one.

Signed-off-by: Dirk Hohndel &lt;dirk@hohndel.org&gt;
</content>
</entry>
<entry>
<title>organize qml files in subdirectories</title>
<updated>2015-11-07T17:00:59Z</updated>
<author>
<name>Sebastian Kügler</name>
<email>sebas@kde.org</email>
</author>
<published>2015-11-06T23:39:06Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/subsurface.git/commit/?id=aae4a326f4738be368088f0d0f7a91d75b02a9ad'/>
<id>urn:sha1:aae4a326f4738be368088f0d0f7a91d75b02a9ad</id>
<content type='text'>
This makes the organization of the qml files a bit more fine-grained, it
prevents mixing of .cpp and QML files, and also of what's compiled, and
what's included in the app as qrc data.

In particular:
- subsurface specific QML items go into the qml/ subdirectory
- theme and unit definitions to into qml/theme subdirectory (they
  already were located in a theme directory)
- generic components, such as our Label goes into qml/components

This facilitates sharing of functionality and identifying common stuff
better. Ideally, we can pull qml/theme and qml/components from a
standardized set at some point, so we don't have to maintain that code.

Signed-off-by: Sebastian Kügler &lt;sebas@kde.org&gt;
Signed-off-by: Dirk Hohndel &lt;dirk@hohndel.org&gt;
</content>
</entry>
</feed>
