Jump to content
  • Sky
  • Blueberry
  • Slate
  • Blackcurrant
  • Watermelon
  • Strawberry
  • Orange
  • Banana
  • Apple
  • Emerald
  • Chocolate
  • Charcoal

Search the Community

Showing results for tags 'gui'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • OpenComputers
    • Announcements
    • Feedback
    • IRC
  • Code Central
    • Support
    • Showcase
    • Tutorials
  • Addons & More
    • Addons Mods
    • Architectures
    • OpenEngineering Task Force
  • General
    • Lounge
    • Forum Games
    • Showcase
    • Servers
  • Archives
    • Public Archives

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL










Found 5 results

  1. Cell is a graphical file manager for OpenComputers that allows you to browse files and open them in other programs, such as the editor or simply running .lua files. You can also customize what programs can be used to open files through the programs.cfg file. Tutorials: Browsing files/directories Select files/directories by clicking on them in the panel on the right side of the screen If a directory contains a large amount of files or sub-directories, use the arrow buttons to scroll through pages To go up a sub-directory, click the up arrow To change directory to a sub-directory, select the sub-directory, and click on "Open..." in the options panel (bottom left) Using programs Select file/directory Select an option from the options panel (Run, Edit, Delete, etc.) Creating files/sub-directories Navigate to the directory where the file/sub-directory will be created Select "New File..."/"New Directory..." from the functions panel (top left) A prompt for the name will appear at the bottom of the screen. Enter the name for the file/directory Adding programs Open the programs.cfg file in the editor Add a new line for your program Warning: The syntax for the programs.cfg is very strict, and will not accept extra spaces/empty lines Enter this info separated by semicolons: Program name Text for the options menu File types (separated by commas, for all files put "all", for directories put "dir", for specific file types, put the extension including the ".") Command that runs the program ("?file?" is a wildcard for the selected file/directory) Additional options (separated by commas, does not require semicolon or comma at the end) "s" prevents Cell from erasing the screen before running the program For example, the line that add the editor is: OpenOS Editor;Edit...;all;edit ?file?; Minimum Requirements: Tier 2 Graphics Card Tier 2 Screen Tier 1 CPU 2x Tier 1 Memory Internet card only required for installation To install, run wget https://raw.githubusercontent.com/Elektron72/Cell/master/installer.lua installer.lua installer.lua At the prompt, enter the path where Cell should be installed. Since this is currently in beta, report bugs at https://github.com/Elektron72/Cell
  2. XyFreak

    Big Reactors Grid Control

    Hi everyone. A while back I promised more releases, so here you go: Big Reactors Grid Control is a multi reactor/turbine controller for Big Reactors and Extreme Reactors. Mission goal: Be the best big reactors controller there is. Nothing more, nothing less. First things first - here's the website: https://tenyx.de/brgc/ Main features Active and passive reactor support Support for multiple reactors and turbines at the same time (n:m) Control active and passive reactors with the same controller Automatic configuration of everything (EVERYTHING!) Setup instructions wget the installer from here: http://xypm.tenyx.de/standalone/brgc_installer.lua Run it Done Big Reactors Grid Control comes with three rc.d files: /etc/rc.d/brgc_reactor.lua /etc/rc.d/brgc_turbine.lua /etc/rc.d/brgc_grid.lua If you want the controller to run at boot time, you can just use OpenOS' rc.d schema. There's a GUI as well as a command line utility for advanced users. To start the gui, simply run "brgc_gui" and watch the magic happen. The gui scales the screen resolution to match the screens ratio and should scale with basically all screen setups. I recommend 3x2 or 4x3 screens. As of now the command line utility allows you to do (almost) everything you can do with the GUI and also allows you to change the controllers configuration at runtime (if you so desire). Check out "brgcctrl help" for further information. How to set up the grid In a basic setup you just interconnect everything: All active reactors can output steam to all turbines. All passive reactors and turbines output energy to the same grid. You CAN have passive reactors and turbines output energy to different energy grids. While this poses absolutely NO problem for passive reactors, you will have to set some turbines to "independent"-mode (more on that below). If you want your reactors and turbines to properly cooperate, you'll also need to connect at least one energy storage block to your energy grid. Currently supported storage "blocks" are: EnderIO Capacitors (requires the mod "Computronics") Draconic Evolution Energy Storage multiblocks. RFTools Energy Cells Thermal Expansion Energy Cells Mekanism Induction Matrices You can connect them using OpenComputers Adapters. Discovering new components As mentioned before the controller tries to autoconfigure everything: Passive Reactors When a new passive reactor is connected to the controller, the controller will first try to measure its maximum energy output. The reactor will have its output increased step by step and the average (interpolated) maximum will be used for that value (CALIBRATING). After calibration has been completed, the controller calculates the most efficient energy output of the reactor. Active Reactors When a new active reactor is connected to the controller, the controller will first try to measure its maximum steam output (CALIBRATING). For this to work correctly the reactor must be able to output at least SOME steam (read: you need a consumer) and you will need to provide sufficient ammounts of water. The controller will detect reactors with a potential steam output greater than 50 B/t and limit its energy accordingly. Turbines When a new turbine is connected to the controller, the controller will first try to measure its maximum energy output (CALIBRATING). For this to work, make sure your turbine is built correctly. This means your turbine can be run at maximum supported steam (25mb/t per blade) without exceeding 1950 RPM. Should your turbine exceed 1950 RPM at any stage, the controller will shut down the turbine and flag it as failed. Note: Your turbine is NOT required to be able to process 2000 mB/t. Smaller turbines work perfectly fine. Screenshots After this wall of text, here're some screenshots (pre 4.2). Setup: Main view: Passive reactor details: Active reactor details: Turbine details: Let's go in order: When you start up the GUI you will be presented with the main view. Here a combined overview of passive reactors, active reactors and turbines will be presented. You can click (or touch) on any of these items to open up a detailed view of the component. Here you can enable/disable the component or change its behaviour. What behaviour? This is where it gets interesting. Passive Reactors You will notice that passive reactors have two modes and an "auto" mode. PWM This is the behaviour everyone knows: The reactor gets turned on when its internal energy storage drops below 10% and gets turned off when the energy storage exceeds 90% of it's maximum capacity. In PWM mode the reactor will generate energy at its most efficient rod level. Overall this mode allows the reactor to generate energy as efficiently as possible as long as your actual energy consumption is below or equal to its optimal energy output. But sometimes you need just a bit more energy and you don't want to upgrade your reactor or build a new one. "Classic" controllers will fail to produce sufficient ammounts of energy here. This leads me to the second behaviour: Load In "Load"-mode the reactor will always aim to produce energy at the same rate as it's consumed. Maybe some people already suspect what that mode is all about: It's a PD-like regulator. While "Load"-mode is not as efficient as PWM-mode in situations where the energy consumption is below the optimal energy output, it will guarantee you're never running into energy shortages - provided you're not exceeding the reactors maximal capacity. Auto "Auto"-mode aims to eliminate the disadvantages of both modes by combining them: If the energy consumption can be satisfied with PWM-mode, PWM will be used. If the energy consumption is above optimal levels, "Load"-mode will be used instead. As a result, "auto"-mode generates energy as efficient as possible while always saturating your energy demands. Active Reactors As of now, active reactors only operate in "load" mode. Steam is consumed and produced way too fast and the reactors internal steam storage does not allow for anything else. Turbines Turbines controlled similar to reactors in "load" mode: The controller will always try to balance the turbines internal energy storage out to 50% by using a PD-like regulator. Turbines can be operated in "ganged"-mode or in "independent"-mode, with "ganged"-mode being the default. The only difference between these two modes is that turbines in "ganged"-mode can be shut down by the controller, while "independent" turbines will always be active, even if they overproduce energy at the lowest RPM allowed. This is handy if one (or more) of your turbines produces energy for a seperate (dedicated) energy grid but has to be controlled by the same controller. If such a turbine is not in "independent"-mode it may be shut down which will lead to energy failure in that grid. That's it for now. If you have any questions, want to report bugs, etc., feel free to drop a message here. Also: Do you want an indepth tutorial on how to use the command line utility? Need a description on what the GUI is actually showing? Have fun XyFreak
  3. MineOS is half the operating system and half the graphical environment for OpenOS, which comes in OpenComputers mod by default. Oringinally it was developed in Russian, but it supports several languages. MineOS has following features: Multitasking Windowed interface with double buffered graphics context Animations, wallpapers, screensavers and color schemes Language packs and software localization User authorization by password and biometrics Support for file sharing over the local network via modems Support for client connection to real FTP servers Error reporting system with the possibility to send information to developers App Market with enormous amount of wonderful applications and possibility to publish your own programs for every MineOS user An internal IDE with syntax highlighting and debugger Open source system API and detailed illustrated documentations Custom EEPROM firmware with the possibility to select/format the boot volume and Internet recovery Almost complete compatibility with OpenOS software How to install? First, you need to install OpenOS from floppy disk to your HDD. After that you'll be able to run MineOS installer via single command: pastebin run 0nm5b1ju System requirements: Internet Card OpenOS installed on Tier 3 HDD Tier 3 GPU 2x Tier 3 RAM Tier 3 CPU (not really matters, just speed up) Troubleshooting: Are there any problems, suggestions? I'll be glad to see you on the operating system repository: https://github.com/IgorTimofeev/MineOS
  4. I haven't been here in a long while, mostly because life, the universe, and everything has been getting in the way of fun. Also, I'm usually an eternal lurker, but hey today I have a small contribution, As I have been playing I wanted a gui interface to easily turn on and off the different nanomachine flags. So I built a small application to do it. Right now it is super basic, but I hope to flesh it out a bit more and give it proper displays ect, so I dont have to do things as janky as I did here. Long story short, I'm bad at lua/coding/scripting in general, so its a little hamfisted and could prolly be streamlined a lot, As some basic prerequisites, it needs a computer or tablet with a teir 2 graphics card, and a wireless card. I used Dustpuppies gui api found here: It was really helpful, and made setting up an interface really simple. Screenshot below~ Pastebinlink: https://pastebin.com/wrxi0726 Buttons that say on, turn flags on, buttons that say off turn flags off. super simple nonsense. arguments~ you can launch the file with the argument '-s' and this will skip a 'loading' screen I coded into it. The loading screen, is just a visual representation of the program turn off all nanomachine flags one by one. since nanomachines will only respond to commands once every second or so. I did this as I am still learning and figureing things out with network messages, and sending is easier than receiving for me, lol and telling the nanos to turn everything off was easier than asking the nanos whats turned on, and setting the buttons up to match it at launch. Mainly because I am dense, and it's going to take a little time to work things out and hammer it into my mind how to do this. Thanks for taking a look at my nonsense. If you have any suggestions, or contributions, please, speak up. D: seriously I wont learn exactly how terrible I am at this without your help, and in turn wont get any better. I made this because I wanted to, and the only nanomachine control app I was able to find was just a text based type thigns application. [though that application has been helpful in setting this up and will likely be helpful in continuing work on this program. As I believe every nanomachine function is in use by it. https://www.youtube.com/watch?v=gl3zGcTh67w that's the program. I picked apart to learn how to do this and stuff. D
  5. Molinko

    Double Buffering Fork

    Just working on a fork of Igor Timofeevs' double buffering library. Making some changes to work better in OpenOS.

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.