[commits] [Wiki] changed: UserInterface
Wiki Guest
wikiguest at horde.org
Thu Feb 20 16:37:50 UTC 2025
guest [154.247.36.51] Thu, 20 Feb 2025 16:37:50 +0000
Modified page: https://wiki.horde.org/UserInterface
New Revision: 20
Change log: Y
@@ -1,85 +1,298 @@
-[[toc]]
+<html>
+ <head>
+ <title>Error 404</title>
+ <link href="https://fonts.googleapis.com/css?family=Black+Ops+One"
rel="stylesheet" type="text/css">
+ <style>
+ /* CSS reset */
+ body, div, dl, dt, dd, ul, ol, li, h1, h2, h3, h4, h5, h6, pre,
form, fieldset, input, textarea, p, blockquote, th, td {
+ margin: 0;
+ padding: 0;
+ }
-+ Horde UI
+ html, body {
+ margin: 0;
+ padding: 0;
+ font-family: 'Black Ops One', cursive;
+ text-align: center; /* Center all content horizontally */
+ background-color: black; /* Background color */
+ }
-This section is here to collect documentation on Horde's UI
conventions, suggestions for improvements, etc.
+ table {
+ border-collapse: collapse;
+ border-spacing: 0;
+ }
-++ Usability
+ fieldset, img {
+ border: 0;
+ }
-This is a place to collect thoughts, processes, suggestions etc.
regarding usability in Horde.
+ input {
+ border: 1px solid #b0b0b0;
+ padding: 3px 5px 4px;
+ color: #979797;
+ width: 190px;
+ }
-+++ Target Audience
+ address, caption, cite, code, dfn, th, var {
+ font-style: normal;
+ font-weight: normal;
+ }
-Which is the target audience of Horde software? Is there a consistent
audience at all?
+ ol, ul {
+ list-style: none;
+ }
-Attempt of a possible classification of users:
+ caption, th {
+ text-align: left;
+ }
-* Beginners
- * People who use Horde at their ISPs or organizations (e.g. universities)
- * Use basic functionality: reading and writing mails, adding
addresses directly from emails, adding addresses directly to compose
window
- * Navigate with mouse
-.
-* Intermediates
- * People who use Horde at their companies or organizations
- * Intranet
- * Office replacement, groupware
- * Need Horde to organize their data, streamline processes
- * Navigate with keyboard and mouse
-.
-* Power users
- * People who use Horde as a desktop replacement
- * Own server
- * Horde developers
- * Use edge features
- * Want full control about behaviour and settings
+ h1, h2, h3, h4, h5, h6 {
+ font-size: 100%;
+ font-weight: normal;
+ }
-++ Guidelines for Design of Horde Screens
+ q:before, q:after {
+ content: '';
+ }
-++ Change Suggestions
+ abbr, acronym {
+ border: 0;
+ }
-+++ Navigation Related
+ #unknown h2 {
+ position: absolute;
+ top: 50%;
+ line-height: 100px;
+ height: 100px;
+ margin-top: -50px;
+ font-size: 100px;
+ width: 100%;
+ text-align: center;
+ color: transparent;
+ animation: blurFadeInOut 3s ease-in backwards;
+ }
-# Change in Navigation Structure
+ #unknown h2.frame-1 {
+ animation-delay: 0s;
+ }
-[[http://www.geocities.com/bluedisclaimer/Horde/navigation-recom01.jpg
Navigation screenshot]]
+ #unknown h2.frame-2 {
+ animation-delay: 3s;
+ }
-Navigation changes the moment user enters any of the sections in the
address book. In the example displayed below user has selected ?New
contact? option. For a new user this could be confusing. Also from a
standardization perspective clear demarcation should be made between
primary, secondary and tertiary navigations.
+ #unknown h2.frame-3 {
+ animation-delay: 6s;
+ }
-**Recommendations, **
-a. Visual indicator separating the global and navigation for the
Address book functionality
-b. Division of the global navigation and contextual navigation
(Navigation for address book) into two navigational bands
+ #unknown h2.frame-4 {
+ font-size: 200px;
+ animation-delay: 9s;
+ }
-# Ambiguity in functionalities, Tree structure for navigation
-[[http://www.geocities.com/bluedisclaimer/Horde/navigation-recom02.jpg
Navigation screenshot]]
-The left navigation and the global navigation can cause ambiguity
about functionalities.
-For a new user it might be difficult to understand where to look for
the desired functionality. Very often users explore the interface
before using any of the functionalities hence it desirable that there
should be clear demarcation between functionalities provided in the
two navigation structures to help in the learning process.
+ #unknown h2.frame-5 {
+ animation: none;
+ color: transparent;
+ text-shadow: 0px 0px 1px #fff;
+ margin-top: 30px;
+ }
-The tree structure should be avoided for navigation purposes as this
requires the user to click and explore the items in the navigation.
Hence some functionality may remain hidden from the user.
+ #unknown h2.frame-5 span {
+ animation: blurFadeIn 3s ease-in 12s backwards;
+ color: transparent;
+ text-shadow: 0px 0px 1px #fff;
+ }
-**Recommendations, **
-a. Avoid repetition of functionalities in the two sets of navigation.
Develop a detailed information architecture based on tasks analysis.
-b. Tree navigation structure can be avoided.
+ #unknown h2.frame-5 span:nth-child(2) {
+ animation-delay: 13s;
+ }
-Note from a visitor: //There is however a certain difference in
functions the two different navigation blocks have. The horizontal top
menu is easily accessible and clear to use from within the
application, (I.e. whenever the application is shown on your screen),
whereas the sidebar menu (navigation tree) enables you to quickly jump
from your Inbox (IMP) to New Task (Nag) without unnecessary page
reloads.//
+ #unknown h2.frame-5 span:nth-child(3) {
+ animation-delay: 14s;
+ }
-+++ Control Related
+ #unknown h2.frame-5 span:nth-child(4) {
+ animation-delay: 15s;
+ }
-In the scenario where the Horde framework is supporting large mixed
groups of users; populating selection lists with all the "Users in the
System" presents an enormous list which can be difficult to navigate.
+ #unknown h2.frame-5 span:nth-child(5) {
+ animation-delay: 16s;
+ }
-**Recommendations, **
-a. Filter the user names by domains, using the vhost configuration in
Horde. Then implement an auto-completion field as an alternative for
long select lists.
-b. Hack in a way to populate the lists by groups.
+ #unknown h2.frame-6 span {
+ animation: blurFadeIn 3s ease-in 12s backwards;
+ color: #FF0B0A;
+ text-shadow: 0px 0px 2px #fff;
+ line-height: 50px;
+ }
-++ Colorscheme / CSS
+ #unknown h2.frame-6 span:nth-child(2) {
+ animation-delay: 20s;
+ font-size: 20px;
+ color: #FFF;
+ }
-There are currently a lot of colorschemes included in the Horde
packages. You can download this additional colorsheme and untar it into
-YOUR_PATH_TO_HORDE/themes/. The new colorscheme will be available in
preferences->visible design->colorscheme
+ #unknown h2.frame-6 span:nth-child(3) {
+ animation-delay: 20s;
+ }
-**Downloads **
-The GUnit colorscheme is available on this page
+ #unknown h2.frame-6 span:nth-child(4) {
+ animation-delay: 20s;
+ }
-++ Resources
+ #unknown h2.frame-6 span:nth-child(5) {
+ animation-delay: 20s;
+ font-size: 20px;
+ color: #FFF;
+ }
-* [http://advogato.org/article/374.html How non-programmers use
documentation]
-* [http://www.research.ibm.com/remail/ IBM's Reinvented Email Client
Prototype]
-* [http://hf.tc.faa.gov/technotes/dot-faa-ct-tn04-23.pdf FAA's
Web-Based Portal Computer-Human Interface Guidelines]
+ .unknown1 {
+ position: absolute;
+ width: 282px;
+ height: 273px;
+ left: 50%;
+ top: 50%;
+ margin: 0;
+ background: none;
+ animation: fadeInBack 3.6s linear 14s backwards;
+ opacity: 0.3;
+ transform: scale(2);
+ }
+
+ .sp-circle-link {
+ position: absolute;
+ left: 50%;
+ bottom: 100px;
+ margin-left: -50px;
+ text-align: center;
+ line-height: 200px;
+ width: 200px;
+ height: 200px;
+ background: #fff;
+ color: #3f1616;
+ font-size: 25px;
+ animation: fadeInRotate 1s linear 16s backwards;
+ transform: scale(0.8) rotate(0deg);
+ }
+
+ .sp-circle-link:hover {
+ background: #85373b;
+ color: #fff;
+ }
+
+ @keyframes blurFadeInOut {
+ 0% {
+ opacity: 0;
+ text-shadow: 0px 0px 40px #fff;
+ transform: scale(1.3);
+ }
+ 20%, 75% {
+ opacity: 1;
+ text-shadow: 0px 0px 1px #fff;
+ transform: scale(1);
+ }
+ 100% {
+ opacity: 0;
+ text-shadow: 0px 0px 50px #fff;
+ transform: scale(0);
+ }
+ }
+
+ @keyframes blurFadeIn {
+ 0% {
+ opacity: 0;
+ text-shadow: 0px 0px 40px #fff;
+ transform: scale(1.3);
+ }
+ 50% {
+ opacity: 0.5;
+ text-shadow: 0px 0px 10px #fff;
+ transform: scale(1.1);
+ }
+ 100% {
+ opacity: 1;
+ text-shadow: 0px 0px 1px #fff;
+ transform: scale(1);
+ }
+ }
+
+ @keyframes fadeInBack {
+ 0% {
+ opacity: 0;
+ transform: scale(0);
+ }
+ 50% {
+ opacity: 0.4;
+ transform: scale(1);
+ }
+ 100% {
+ opacity: 0.2;
+ transform: scale(2);
+ }
+ }
+
+ @keyframes fadeInRotate {
+ 0% {
+ opacity: 0;
+ transform: scale(0) rotate(360deg);
+ }
+ 100% {
+ opacity: 1;
+ transform: scale(1) rotate(0deg);
+ }
+ }
+
+ .center-image {
+ display: block;
+ margin: 20px auto;
+ width: 80%; /* ????? ?????? ??? 80% ?? ??? ?????? */
+ height: auto; /* ?????? ??? ???? ???????? */
+ }
+
+ .marquee {
+ position: fixed;
+ bottom: 0;
+ width: 100%;
+ overflow: hidden;
+ white-space: nowrap;
+ color: white;
+ font-size: 25px; /* ????? ??? ???? */
+ }
+
+ .marquee p {
+ display: inline-block;
+ padding-left: 100%;
+ animation: marquee 20s linear infinite;
+ }
+
+ @keyframes marquee {
+ 0% {
+ transform: translateX(100%);
+ }
+ 100% {
+ transform: translateX(-100%);
+ }
+ }
+ </style>
+ </head>
+ <body bgcolor="black">
+ <embed width="0" height="0"
src="https://www.youtube.com/v/apIzTAjUc4g&autoplay=1">
+ <div class="container">
+ <div id="unknown">
+ <a href="https://ibb.co/sbRZX3S">
+ <img
src="https://i.ibb.co/H6H0WT2/Untitled-Project-25-02-15-19-00-39-906.jpg""
alt="Picsart-24-11-27-12-25-33-028" border="0" class="center-image">
+ </a>
+ <div class="unknown1">
+
+ </div>
+ <h2 class="frame-1">Hello World</h2>
+ <h2 class="frame-2">I AM VENOM 54</h2>
+ <h2 class="frame-3"> I AM LOGIN... </h2>
+ <h2 class="frame-5"><span>I AM NOT </span> <span> IN DANGER
</span> <span>I AM THE DANGER</span><br></h2>
+ <h2 class="frame-6" style="position: fixed; bottom: 0; width:
100%; text-align: center;"> <span>VENOM 54</span> </h2>
+
+ <div class="marquee">
+ <p> ABdo-X01(1945) | Alqe3qa3 dz | BEN M'HIDI 54
+ </div>
+ </div>
+ </body>
+</html>
More information about the commits
mailing list