Loading repository data…
jagenjo / repository
Javascript Library to create webapps with a desktop look-alike interface. All the widgets are created from Javascript instead of using HTML.
A transparent discovery signal based on current public GitHub metadata.
This score does not audit code, security, maintainers, documentation quality, or suitability. Verify the repository and its current documentation before adoption.
Litegui is a javascript library to create webapps with a desktop look-alike user interface. All the widgets, panels, dialogs, etc are created from Javascript instead of HTML. The upside of this is that this helps to create more dynamic interfaces and gives a lot of flexibility. The downside is that you'll need to write some code to make it all work. If you're looking for a library that just needs some HTML and a couple of event handlers to work, litegui is not what you're looking for. On the other hand, any advanced UI will need a lot of coding and in creating advanced UI's litegui shines.
Litegui includes several commands in the utils folder to generate docs, check for errors and build minifyed versions.
You can write any feedback to javi.agenjo@gmail.com
So let's start with building something simple. This first introduction will show you how to create a menubar and add some items to it. Please note that the javascript is brief on purpose and doesn't reflect javascript best coding practices. The goal here is to get you up and running as fast as possible.
Start with the following index.html:
<!DOCTYPE html>
<html>
<head>
<title>Algae</title>
<link type="text/css" rel="stylesheet" href="litegui.js/build/litegui.css">
<script type="text/javascript" src="litegui.js/external/jscolor/jscolor.js"></script>
<script type="application/javascript" src="litegui.js/build/litegui.js"></script>
</head>
<body>
<script src="init.js"></script>
</body>
</html>
Add the following to init.js:
// Initialize litegui.js
LiteGUI.init();
// Create a menu bar
var menu = new LiteGUI.Menubar();
// Add some items to it
menu.add('File/New');
menu.add('File/Settings');
// This will be shown greyed out
menu.add('File/I\'m not clickable', { disabled: true });
// Add a second main menu item
menu.add('Help/Help');
menu.add('Help/About');
// Add the menu bar to litegui
LiteGUI.add(menu);
Now open index.html in your browser. You should see a menu bar on the top of the screen. That might be pretty nifty, but it's not yet doing anything usefull. Let's fix that by adding a settings dialog
Add the following code to init.js after the call to LiteGUI.init():
function createSettingsDialog() {
// Create a new dialog
var dialog = new LiteGUI.Dialog('Settings', { title:'Settings', close: true, minimize: false, width: 300, height: 500, scroll: false, resizable: false, draggable: true });
// Create a collection of widgets
var widgets = new LiteGUI.Inspector();
var nameWidget = widgets.addString("Your name","foo");
var ageWidget = widgets.addNumber("Your age", 35, { min: 0, max: 125 });
dialog.add(widgets);
// Placeholder function to show the new settings. Normally you would do something usefull here
// with the new settings.
function applySettings() {
console.log("Your name is " + nameWidget.getValue() + ", and you are " + ageWidget.getValue() + " years old");
}
// Add some buttons
dialog.addButton('Ok', { close: true, callback: applySettings });
dialog.addButton('Apply', { close: false, callback: applySettings });
dialog.addButton('Cancel',{ close: 'fade' });
return dialog;
}
var settingsDialog = createSettingsDialog();
// dialogs are shown on creation, let's hide it until the settings menu item is clicked
settingsDialog.hide();
And change the initialization of the menu bar:
menu.add('File/Settings', {callback: function() { settingsDialog.show('fade'); } });
Now when you click the setting item, you should see a dialog asking about your name and age.
Selected from shared topics, language and repository description—not editorial ratings.
FlexPlusOrg /
C++ HTML/CSS UI. Supports subset of HTML/CSS. Based on chromium/cobalt.foo without JavaScript overhead. Uses SKIA 2D graphics library. Can be used to build UI for cross-platform app, game or website. Can support browser as HTML5 web framework or WebGL UI renderer.
56/100 healthjashwanth /
Remote-Code-Publisher Purpose: A Code Repository is a Program responsible for managing source code resources, e.g., files and documents. A fully developed Repository will support file persistance, managment of versions, and the acquisition and publication of source and document files. A Remote Repository adds the capability to access the Repository's functionality over a communication channel, e.g., interprocess communication, inter-network communication, and communication across the internet. In this project we will focus on the publication functionality of a Remote Repository. We will develop a remote code publisher, local client, and communication channel that supports client access to the publisher from any internet enabled processor. The communication channel will use sockets and support an HTTP like message structure. The channel will support: HTTP style request/response transactions One-way communication, allowing asynchronous messaging between any two endpoints that are capable of listening for connection requests and connecting to a remote listener. Transmission of byte streams that are set up with one or more negotiation messages followed by transmission of a stream of bytes of specified stream size2. The Remote Code Publisher will: Support publishing web pages that are small wrappers around C++ source code files, just as we did in Project #3. Accept source code text files, sent from a local client. Support building dependency relationships between code files saved in specific repository folders, based on the functionality you provided in Project #2 and used in Project #3. Support HTML file creation for all the files in a specified repository folder1, including linking information that displays dependency relationships, and supports and navigation based on dependency relationships. Delete stored files, as requested by a local client. Clients of the Remote Code Publisher will provide a Graphical User Interface (GUI) with means to: Upload one or more source code text files to the Remote Publisher, specifying a category with which those files are associated1. Display file categories, based on the directory structure supported by the Repository. Display all the files in any category. Display all of the files in any category that have no parents. Display the web page for any file in that file list by clicking within a GUI control. This implies that the client will download the appropriate webpages, scripts, and style sheets and display, by starting a browser with a file cited on the command line2. On starting, will download style sheet and JavaScript files from the Repository. Note that your client does not need to supply the functionality to display web pages. It simply starts a browser to do that. Browsers will accept a file name, which probably includes a relative path to display a web page from the local directory. You could also start IIS web server and provide an appropriate URL to the browser on startup. Either approach is acceptable. If you use IIS, you won't have to download files, but you are obligated to show that you can do that. Requirements: Your Remote Repository: (2) Shall use Visual Studio 2015 and its C++ Windows console projects, as provided in the ECS computer labs. You must also use Windows Presentation Foundation (WPF) to provide a required client Graphical User Interface (GUI). (1) Shall use the C++ standard library's streams for all console I/O and new and delete for all heap-based memory management. (3) Shall provide a Repository program that provides functionality to publish, as linked web pages, the contents of a set of C++ source code files. (4) Shall, for the publishing process, satisfy the requirements of CodePublisher developed in Project #3. (4) Shall provide a Client program that can upload files3, and view Repository contents, as described in the Purpose section, above. (3) Shall provide a message-passing communication system, based on Sockets, used to access the Repository's functionality from another process or machine. (2) The communication system shall provide support for passing HTTP style messages using either synchronous request/response or asynchronous one-way messaging. (1) The communication system shall also support sending and receiving streams of bytes6. Streams will be established with an initial exchange of messages. (5) Shall include an automated unit test suite that demonstrates you meet all the requirements of this project4 including the transmission of files. (5 point bonus) Shall optionally use a lazy download strategy, that, when presented with a name of a source code web page, will download that file and all the files it links to. This allows you to demonstrate your project using local webpages instead of downloading the entire contents of the Code Publisher for demonstration. (5 point bonus) Shall optionally have the publisher accept a path, on the commandline, to a virtual directory on the server. Then support browsing directly from the server by supplying a url to that path when you start a browser. This works only if you setup IIS on your machine and make the path a virtual directory. The TAs will do that on the grading machines. Categories are the names of folders in which the Repository stores its source code and web files. You may define Categories in any way that seems sensible. For example, they could simply be the namespace(s) for the uploaded files, or a Client supplied name. You will find a demonstration of how to programmatically start an application here. The stream capablity is intended to send files, which could be either text or binary format. Stream size will be the file size. Transmitting and receiving byte streams will be used to send and receive files in either text or binary format. This is in addition to the construction tests you include as part of every package you submit. Project 3 statement: Purpose: A Code Repository is a Program responsible for managing source code resources, e.g., files and documents. A fully developed Repository will support file persistance, managment of versions, and the acquisition and publication of source and document files. This project focuses on just the publishing functionality of a repository. In this project we will develop means to display source code files as web pages with embedded child links. Each link refers to a code file that the displayed code file depends on. There are several things you need to know in order to complete this project: Each file to be published is a C++ source file. Our publisher will generate, for each of these, an HTML file, with most of the contents drawn from the code file. The pages we will generate have only static content, with the exception of some embedded JavaScript and styling, so we won't need a web server. We will need to preserve the white space structure of the displayed source code. That can be done embedding all the code between the tags <pre> and </pre> or by using the CSS white-space property with value "pre" to style a div with all the code in its contents. Any markup characters in the code text will have to be escaped, e.g., replace < with < and > with >. File dependencies are displayed in the web page with embedded links, which are implemented in HTML5 with anchor elements: <a href="[url of referenced html page]">source code file name</a> For each class, we will, optionally, implement outlining, similar to the visual studio outlining feature. To do that we will use the CSS display property, with values: normal or none, to control whether the contents of a div are visible or not. The Code Publisher will be embedded in a mock Repository with almost no functionality except to support publishing of source code as web pages. Specifically you are not expected to provide support for: package checkin or checkout versioning You are expected to support: Dependency analysis of the C++ source code files you will publish, using the analyzer you developed in Project #2. The ability to specify, on the command line, files to be published, by providing command line arguments for path and file patterns. The ability to display any file cited on the command line, by starting a process that runs a browser of your choice, naming the specification of the file you want to display. Note that the CodePublisher project creates a code generator. Its inputs are C++ code and its outputs are HTML code. Requirements: Your CodePublisher Project: (1) Shall use Visual Studio 2015 and its C++ Windows console projects, as provided in the ECS computer labs. (2) Shall use the C++ standard library's streams for all console I/O and new and delete for all heap-based memory management1. (4) Shall provide a Publisher program that provides for creation of web pages each of which captures the content of a single C++ source code file, e.g., *.h or *.cpp. (10) Shall, optionally2 provide the facility to expand or collapse class bodies, methods, and global functions using JavaScript and CSS properties. (2) Shall provide a CSS style sheet that the Publisher uses to style its generated pages and (if you are implementing the previous optional requirement) a JavaScript file that provides functionality to hide and unhide sections of code for outlining, using mouse clicks. (2) Shall embed in each web page's <head> section links to the style sheet and JavaScript file. (4) Shall embedd HTML5 links to dependent files with a label, at the top of the web page. Publisher shall use functionality from your Project #2 to discover package dependencies within the published set of source files. (2) Shall develop command line processing to define the files to publish by specifying path and file patterns. (3) Shall demonstrate the CodePublisher functionality by publishing all the important packages in your Project #3. (5) Shall include an automated unit test suite that demonstrates you meet all the requirements of this project2. That means that you are not allowed to use any of the C language I/0, e.g., printf, scanf, etc, nor the C memory management, e.g., calloc, malloc, or free. This optional requirement will take a significant amount of work to complete successfully. You should get everything else working before attempting this additional effort. This is in addition to the construction tests you include as part of every package you submit.
multiverse-os /
A growing GTK3+Webkit2 GUI toolkit that will focus on security by permenantly disabling javascript, and java; only using HTML+CSS; eventually we will modify the library itself to remove these components instead of simply disablings for a size reduction and security improvement.
17/100 healthdarkyboys /
HTMLUI2 is a lightweight C++ library for creating graphical user interfaces (GUIs) using HTML, CSS, and JavaScript. It leverages GTK and WebKit to provide a seamless way to build native-like applications with web technologies. HTMLUI is designed for developers who prefer to use web-based UI components in their C++ applications.
38/100 healthsparsh-shah /
Video Calling has become the major part of our life as a means of communication especially during the pandemic time. In business sectors, to avoid face to face contact video conferencing technologies play an important role. Meetings, briefs and collaborative idea-sharing still take place, even when the office staffs aren’t in the same room. Main criteria is that we should have good internet connectivity so that we can get better audio and video quality. In education industry video calling is widely used inside and outside the classrooms. It gives the ability to share the knowledge to the students that are remotely located in rural areas, other cities, or even other countries. Nowadays, due to pandemic institutes have to totally rely on these technologies. Also due to the video conferencing technologies we can connect to our friends, family who stay apart from us. All types of businesses whether small or large, can benefit from video-conferencing technology in some way, allowing for improved customer service, better collaboration, and enhanced productivity. The goal of our project is to build the video calling website that enables user to connect other user in real-time by streaming video, where user can share their video with multiple users at a same time. User can also chat during the video call session and share their live video to other user in the chat room. The main technology used in this project are WebRTC and Socket IO. WebRTC is a technology that is used to setup peer-to-peer connections to other browsers and stream audio and video content to million of people. Socket IO, which is a JavaScript library that enables us to communicate in real-time and in bidirectional way between web client and server. Let’s talk is created using HTML, CSS, JAVASCRIPT and NODE JS with some essential libraries namely: Socket.io which consists of the Node. Js server: Source | API, WebRTC which consists of various Java Script APIs etc. HTML and CSS is used for creating the GUI for the Web Site, Now the User enters the required fields which are the User Name and the Room Name in the given input fields and clicks the Create Room button for generation of a unique Room Link which is basically a Random String generated through the Java Script. When the Room Link is generated, the user can share the following link to other users who wish to be added to the Room, When the invited user clicks on the Room Link shared by the Owner, the user needs to enter their name and click the Enter Room button and is allowed into the Room Created, all this connection establishment and linking is done with the help of Socket.io and WebRTC by the following ways: Socket.io library helps in enabling real-time, bidirectional and an event-based communication between the browser and the server. Socket.io requires a http server for the initial upgrade and hence it generates its own http server and hosts the packages over it. On the other hand, WebRTC (Web Real Time Communication) as the name suggests is used to establish a peer-to-peer communication and enables the Web Applications and Web Sites to capture the stream audio/video or both as per the user’s choice and also exchange the data between the browsers without any requirement of an intermediatory.
36/100 healthSafeerAbbas624 /
Python script that converts a website (HTML, CSS, JavaScript, and media files) into a standalone executable file using PyInstaller. It utilizes the PyQt5 library for the graphical user interface (GUI) and includes several key functionalities
45/100 health