![]() Can be touchscreen friendly with a few tweaks (see wiki page here). Lightweight and touch-friendly web browser based on qt (source ).įrontend for emulators, game engines and media players. Peer-to-peer (Tox) messaging client ( other FOSS clients also available) Todo.txt GUI, not mobile optimized, but scales well Originally a fork of Shotwell.Ĭomic book reader with touch support, for plasma mobile (in development) Photo gallery and editor for Elementary OS. Not touch-optimised but can display most mobile websites well (no HTML5 support). Uses OSM, Garmin and other map sources.Įxtremely lightweight web browser, using very little RAM. Open source GTK+ and SDL based car navigation software. ![]() Lightweight touchscreen Qt-based map application (using OSM). Their source link is broken, but the code can be found here.) Lightweight, touch-friendly email client designed for Nokia Maemo devices. It can display websites well, with HTML5 support. Touch-capable but not touch-optimised and not hardware-accelerated. Resizes well to a phone's aspect ratio although a few dialog boxes may not be accessible easily.įairly lightweight web browser, using very little RAM. GTK3 based calendar application from Elementary OS. Simple Qt5 text and code editor using Material Design, with touch support Simple Qt5 calculator using Material Design, with touch support QtWebEngine-based browser built with complete touch (including smartphone) support, Material Design, and support for coloured-site windows Can be resized to a phone's aspect ratio when running in graphical mode. Simple web browser for saving on data consumption. Made for desktop but also suitable for touchscreen use. Touchscreen file manager for Plasma Mobile Purism made a mobile config for the Librem 5. Scales perfectly and is very touch-friendly. GTK3-based simple maps application with routing. Peer-to-peer messaging client and protocol. Supports highlighting and is touch-friendly.Īn XMPP client written in Python with Gtk+3.0 GTK3 document viewer (for PDFs and other formats). Purism is working on making it phone-friendly for their Librem 5 phone. VoIP and video conferencing application for GNOME Modern Jabber/XMPP Client using GTK+/Vala īasic image editor for the GNOME desktop. Not touch-optimised but can display most mobile websites well (no HTML5 support), and hence may be the only usable browser on older devices, besides Netsurf. Part of the KDE Calligra suite.Įxtremely lightweight web browser, using very little RAM. Word processor and presentation application designed for touchscreen devices. Simple retro-themed touch UI written in vala Touch-friendly.Ĭomplete cross-platform Signal client, compatible with the Ubuntu Phone and more. These are applications which already exist for Linux and could be reused in postmarketOS with little to no adjustment. I could see a “is dirty” lister that gives you a top down view of all the ops that have changed and what changes you might want to keep / discard… on my long todo list, but hasn’t been enough of a deal breaker yet to spend a few days getting it right. Since the member needs to be evaluated / is non-updating it’s a little more work to check to see what might need saving. The comp class does have a member for this. This means that anymore more than start / stop can be a significant effort to work around.įor me, a solid starting point would be a dependable dirty indicator for ops that are externalized. It’s also the case that I often work on a machines that I don’t have keyboard and mouse access to… I can see an output, but I might not have an easy way to point, click, or other wise manipulate a given machine. Said another way, I rely on the fact that by default I want to overwrite an existing tox with a new one on disk. I often swap TOX components and any pop-ups or blocking dialogues would break my ability to work with externalized tox files - especially as I currently rely on delivering sub components in the form of tox files that complete a larger system. I’m probably overlooking some technical details but, if we had something like that, I would be fully content. If it does not work, notify user and exit process. If it is, ask the user if he wants to overwrite the external. If there is a path and it is valid, check if the modification time of the component is greater than that of the external. If there is a path but it’s invalid (the file does not have to exist, it just needs to be an invalid path), notify user and exit process. Recursively work its way up through all components in the network.įor each component, check if a valid path is present in the “External. However, my main concern is not so much about myself being able to work it out but more about my students who are learning the tool…īasically, the only thing I would like from Derivative is an option I can tick in the preferences that does this upon quitting the app: Thanks for the idea It’s certainly something to consider.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |