<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.cliquesoft.org/index.php?action=history&amp;feed=atom&amp;title=web.ui</id>
		<title>web.ui - Revision history</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.cliquesoft.org/index.php?action=history&amp;feed=atom&amp;title=web.ui"/>
		<link rel="alternate" type="text/html" href="https://wiki.cliquesoft.org/index.php?title=web.ui&amp;action=history"/>
		<updated>2026-11-11T07:09:54Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.24.4</generator>

	<entry>
		<id>https://wiki.cliquesoft.org/index.php?title=web.ui&amp;diff=5613&amp;oldid=prev</id>
		<title>Digitalpipe: Created page with &quot;Similar in scope to the [https://blog.mozilla.org/labs/2011/02/prism-is-now-chromeless/ Mozilla Chromeless] project (formerly [https://en.wikipedia.org/wiki/Mozilla_Prism Prism])...&quot;</title>
		<link rel="alternate" type="text/html" href="https://wiki.cliquesoft.org/index.php?title=web.ui&amp;diff=5613&amp;oldid=prev"/>
				<updated>2015-10-08T16:04:52Z</updated>
		
		<summary type="html">&lt;p&gt;Created page with &amp;quot;Similar in scope to the [https://blog.mozilla.org/labs/2011/02/prism-is-now-chromeless/ Mozilla Chromeless] project (formerly [https://en.wikipedia.org/wiki/Mozilla_Prism Prism])...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Similar in scope to the [https://blog.mozilla.org/labs/2011/02/prism-is-now-chromeless/ Mozilla Chromeless] project (formerly [https://en.wikipedia.org/wiki/Mozilla_Prism Prism]), this software was created to allow web-based services and applications like [http://wiki.cliquesoft.org/index.php?title=webBooks webBooks] to have their own interface free from the clutter and distractions from the other tabs in your web browser.  This can also help protect each of these web-based instances from the effects of the overall browser such as unexpected crashes from a website in one of the tabs causing the loss of any unsaved data.  Mainly used by the web-based [http://wiki.cliquesoft.org/index.php?title=XiniX XiniX operating system] as a way to provide the traditional functionality of an OS for its users, however, any OS can take advantage of this great software!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==License==&lt;br /&gt;
This projects&amp;#039; codebase is licensed under the CPLv2 unless a valid CPLv1 license has been purchased.  More information about both of these licenses can be found under the &amp;quot;[http://www.cliquesoft.org/index.php?page=our_licenses Our Licenses]&amp;quot; link of our [http://www.cliquesoft.org/ homepage].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
No matter which method of installation you choose below, web.ui does not require a lot of complication to get running on your device.  The &amp;#039;Package Management&amp;#039; option will be the easiest since someone will have taken the compilation steps for you, but even if you have to perform the building of the executable on your own, there are only a handful of dependencies required - most of which are already installed on your computer!&lt;br /&gt;
&lt;br /&gt;
===Package Management===&lt;br /&gt;
As noted above, this will be the easiest method of installation for this software.  We will expand the below list to include as many mainstream Linux distros as possible when [http://www.cliquesoft.org/#Contact submissions] are made to our staff for inclusion.&lt;br /&gt;
&lt;br /&gt;
Debian and derivatives (Ubuntu, Linux Mint, Knoppix, ) &lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ sudo apt-get install web.ui&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
TinyCore and derivatives&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
tce-load -iw web.ui.tcz&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Compiling from Source===&lt;br /&gt;
This will the most difficult method of installation, but our staff has tried to make this as painless as possible.  Currently only a handful of tools need to be installed along with a few simple commands and the build process will be completed. The below list will outline what you need to have pre-installed:&lt;br /&gt;
&lt;br /&gt;
:: o Standard tools such as find, grep, cut, etc&lt;br /&gt;
:: o Bash&lt;br /&gt;
:: o a c/c++ compiler such as [https://gcc.gnu.org/ gcc/g++]&lt;br /&gt;
:: o FLTK 1.3 dev package for your distro&lt;br /&gt;
&lt;br /&gt;
After making sure that above requirements are met, we can proceed with building the binary for this web-base user interface. For this example, we will be using [http://www.gnu.org GNU&amp;#039;s] gcc compiler and assumed that the source was downloaded into the /tmp directory.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ tar zxf /tmp/web.ui_x.x.x.x.soft&lt;br /&gt;
$ cd /tmp&lt;br /&gt;
$ ./make install&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It should be noted that if you are a package maintainer, you can optionally include a &amp;#039;PREFIX=/staging/dir/prefix&amp;#039; to the &amp;#039;make&amp;#039; call to have the software install to a staging area where you can package the software for your distro. If you are uncertain what a package maintainer is, then you should not use the &amp;#039;PREFIX&amp;#039; switch!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Post Install&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
To use web.ui after either of the above installation routines have occurred, you simply need to call the binary with the proper command line parameters.  There is no configuration file or other complicated setup involved!  We will cover all the available switches below.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Getting Started==&lt;br /&gt;
Now that we have a working binary installed in your operating system, we need to discuss the various ways this software to your liking.  As stated above, the only configuration presently available is through the user of command line parameters, of which there is only a few.  The syntax of the program is as follows:&lt;br /&gt;
&lt;br /&gt;
: web.ui [OPTION] [URI]&lt;br /&gt;
&lt;br /&gt;
===Switches===&lt;br /&gt;
As a way to provide additional functionality, web.ui can also accept several command line switches. An expanded description of each will be covered below.&lt;br /&gt;
&lt;br /&gt;
Operational switches&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;-d[ownload]&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
This switch enables web.ui to download files through its interface.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;-e[xecute]&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
In some instances, a local web-based application might require some other software to load while running. It is important to remember that this call is NOT backgrounded so if you require control to return, you will need to append the ampersand &amp;#039;&amp;amp;&amp;#039; character to the end of the call.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;-g[eometry] WxH+X+Y&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
When this option has been passed, FXwm will act as though the screen is only as large as the values specified by &amp;#039;W&amp;#039; and &amp;#039;H&amp;#039; (in pixels), and will constrain windows within this area. The &amp;#039;X&amp;#039; and &amp;#039;Y&amp;#039; values correspond to the offset from the upper left-hand corner of the screen designating the top and left boundries where the it begins. Using the -l or -o switches, you can further restrict the size and placement of application windows within the geometry specified. Starting FXwm without this switch will cause it to use the entire screen.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;-h[elp]&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
Shows the help screen and exits the program.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;-i[con] FILE&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
Sets the application icon contained in the titlebar for the web-based service or application to a local graphic.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;-s[torage] DIR&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
Sets the storage directory for system files like &amp;#039;cookies.dat&amp;#039;, browsing cache, and more.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;-t[itle] STRING&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
Used to set the title of the window.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Emergency Browser==&lt;br /&gt;
In some emergency situations you may need to use a very simplistic web browser to gather information or obtain some type of file.  Although not designed as a web browser, web.ui can work in a pinch.  To navigate to the proper site, you would need to call the binary in a fashion like:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
web.ui -d http://www.domain.com&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will enable downloading files over the Internet and will bring up the site located at &amp;#039;www.domain.com&amp;#039; in this example.&lt;/div&gt;</summary>
		<author><name>Digitalpipe</name></author>	</entry>

	</feed>