Movatterモバイル変換

[0]ホーム
URL:

Wayback Machine
18 captures
18 Oct 2019 - 02 Feb 2026
OctNOVDec
14
201920202021
success
fail
COLLECTED BY
Organization:Archive Team
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.

The main site for Archive Team is atarchiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.

This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by theWayback Machine, providing a path back to lost websites and work.

Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.

The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.

TIMESTAMPS
loading
The Wayback Machine - https://web.archive.org/web/20201114111935/https://github.com/lxqt/lxqt/wiki/History
Skip to content
Sign up
Sign in Sign up
rgm edited this pageJul 30, 2018 · 7 revisions

Even though some people often confuse LXQt as arewrite of LXDE in Qt, this is not true.PCMan, the original author of LXDE, startedexperimenting with Qt, first by implementing a GUI for PCManFM in Qt. While doing so he wrote upA Guide for Migrating from GTK+ to Qt where he sums up his experiences.

When he released apreview, some people feared that a Qt-based desktop environment would be too heavy and bloated, so heposted about this too. LXDE was written in GTK+2, but times change and GTK+3 came out. Some people thought that GTK+3 was not good, and that a port to GTK+3 would have been rather bloated, but a Qt version wouldn't be.

Short notice: for those interested in numbers, PCMan later created another post about the usage and performance, which you can findhere.

At the same time another group of people were working on a Qt-based desktop environment called razor-qt, and eventually the LXDE-Qt and razor-qt peopledecided to work together and createLXQt. So instead of being a rewrite of LXDE in Qt, LXQt is rather alightweight desktop environment heavily based on the razor-qt code base and a team consisting of LXDE and ex-razor-qt developers. This same information is stated in a post calledIn memory of Razor-Qt.

Some distributions still have it categorized under the name LXDE-Qt, for historical reasons that should be now clear. Inthis post you can still see the name mentioned asLXDE-Qt or LXQt, but now the official name is settled, and it'sLXQt

Initially it was developed in Qt4. In June 2014 it gotfull Qt5 support and since version 0.9.0 only supports Qt5.

Recently it has beenswitching from using many individually developed libraries to instead use the KFrameworks5 library. Again, some people where afraid of introducingbloat because they thought it would mean including all KDE libraries and dependencies, but once again this has not been the case. KFrameworks5 was actually introduced in an attempt to split the basic functionality from KDE specific libraries and thus make it usable in other projects than just KDE.

Clone this wiki locally
You can’t perform that action at this time.
[8]ページ先頭
©2009-2026 Movatter.jp