So I came up with some ideas (and stole some from various other threads), and after some debate with myself, I determined that this thread was probably the best fit for this.
For creating the Microchip/Interated Cicuit itself it should be a (somewhat) expensive recipe, as this is providing a HUGE convenience.
So the chip would start out with crafting a wafer
Or
and it would give between 2 and 4 wafers (depending on the final recipe)
These wafers are essentially a silicon "base" for the final chip (using sand as it is a natural silison source IRL)
The second part of the chip would be the IC (integrated circuit) itself = Redstone Dust
and it would give 1-4 ICs, but the recipe and output will be changed to better match the final recipe and output for the wafer
Finally, the two items would be combined to make the final, programmable, placeable, chip = IC = Wafer
This recipe would (and should) yield 1 microchip.
My next thought was to use a "programmer" workbench that would use a GUI similar to the one in OP, this would allow you to "plug in" your newly crafted chip and supply the materials (redstone dust and sand/dirt) used to make the circuit.
Borrowing from TheEvilM in this thread, I decided the following.
The gui should provide redstone wires, although, instead of what was suggested in the aforementioned thread, only have one wire option, but have the wire directionality be toggleable, AKA, right click on it to cycle through all the various connection options (straight, corners, three-way junctions, and four-way junctions, all rotateable), this would allow every space on the board to be used, without needing to make a bunch of extra buttons. These wires would be converted from redstone dusts in a 1:1 ratio, and (ideally) can be converted back (whether they can be stored in inventory is up for debate, if so, they will NOT be placeable in the world , at least, not at first).
In order to facilitate logic gates, there has to be some form of redstone torch, possibly called "pins" what these will look like is open to discussion, but they will function EXACTLY like normal redstone torches, and will be converted from redstone torches in a 1:1 ratio. In terms of converting back and inventory storage, it will be the same as the redstone wires.
There would also be an block (possibly called an insulator, open to debate) crafted from sand/dirt (something cheap) which would be used to make various gates, I.E, placing a redstone wire, then a block, then a "pin", it will function as a "not" gate, just like if you did it in the world. Again, the conversion back and inventory storage will be just like the "pins" and wires.
I modified the image you posted to include my ideas, and I think it works fairly well (I might need some help on the graphic design portions).
The recipe for the bench itself i'm not sure about yet, but i think it should include redstone dust and possibly iron/gold (as these are excellent conductors IRL).
A debateable item would be a "replicator" bench, which would copy the design inside a chip into another chip. The design for this gui would be similar to that of the furnace, a set of spaces for raw materials (redstone dust, dirt/sand, and redstone torches), a space for unprogrammed chips, a space for the "master" programmed chip, and an output slot. If this is implemented, unprogrammed chips might end up being stackable so that you can mass produce that adder chip you built for your 128-bit calculator.
Possible restrictions/features:
Chips:
2 inputs, 2 outputs (at first), labeled on the tile itself when placed 4 I/O "ports" on the four sides of the tile, labeled by number (will also be labeled inside the programming GUI).
cannot contain other chips, the (real life)resources it would take to recursively place chips inside each other so you can have a "computer" chip (no pun intended), is far too much for this to be viable
a chip is limited to 8x8x2 spaces, this will allow you to build some of the more complex circuits, but not all of them (A D Flip Flop will fit, but not much else, however, a JK Flip Flop, will not fit on one chip). (On further though, this may be increased to 8x8x3, to allow for redstone to be run on top of a layer 2 block)
Chips cannot be stacked, but two chips placed next to each other (input to output) will work properly (tenatively, may require 1 redstone dust in between, at least in early versions)
Chips will need to be collected with a pickaxe, or they may get "wiped" (open to debate)
unprogrammed chips can be stacked (open to debate), but chips that have been programmed will only be stackable if they have been created by a replicator (to prevent chips with the same names but different programming from being stacked)
Programmer Bench:
Chips can be reprogrammed, AKA, placed back on the board to be modified/finished. This way, if a user runs out of a material, they don't have to craft a whole new chip to finish it.
Users will be able to label their chips, otherwise, there will be no way to tell which chip is your 5 clock and which is your RS NOR Latch.
Replicator Bench:
It will require fuel of some kind, possibly pulsing redstone(?) or some other form of non-fossil (preferably electricity-based) fuel (AKA, the fuel used here can't also be used in the furnace).
Replication will stop as soon as any of the materials/fuel run out, however, a check is done before each chip is started to ensure that it doesn't run out mid-replication.
All replicated chips will have the same name/label as the master chip, which (may) allow them to be stacked.
Any and all feedback is appreciated.
I am planning on making this!!! So please provide me with all the feedback that you can!
pfft this is a taster of what i do C++
#include<iostream>
#include<string>
#include <cstdlib>
#include<direct.h>
#include<fstream>
using namespace std;
string Commands;
int main()
{
cout << "What would you like to do?" << endl;
cout << "Enter a command" << endl;
cin >> Commands;
{
string WebAd;
cout << "What web address do you want to open?" << endl << "If you want to go to the default Adress (www.google.com) then just type DEF" << endl;
if (Commands == "CNF" || Commands == "cnf")
{
string FolderName;
string SaveLocation;
cout << "What do you want the folder to be called?" << endl;
cin >> FolderName;
cout << "Where do you want the folder to be created at?" << endl << endl;
cout << "Example C:\\users\\Jake\\Newfile, You must have // insted of /" << endl;
cin >> SaveLocation;
int _mkdir(
const char *SaveLocation
cout << "Sorry but that is not a reconised command" << endl << endl;
cout << "Type 'Help' for command assistance" << endl;
cin >> Commands;
if (Commands == "Help" || Commands == "help")
{
cout << "Commands" << endl;
cout << "Help" << endl << "Minecraft" << endl << "Internet" << endl;
Commands = "";
cin >> Commands;
}
system("pause");
}
Nice little script, however, you don't give the user the opportunity to type in the address they want, even though you reference that they can. (Just helping emphasize how difficult coding can be, even for something this simple.)
I personally prefer coding in Java, though I'm fairly proficient in C++ also. I once had to write a program for C++ (no gui, thank God) that would play the game "War"... 1000+ lines of code. half a dozen arrays, and about the same number of lists (variable length arrays). Pain. In. The. Butt. But it worked, LOTS of debugging, had to rewrite the whole thing once because I missed a semicolon and couldn't find it. Not Happy.
0
For creating the Microchip/Interated Cicuit itself it should be a (somewhat) expensive recipe, as this is providing a HUGE convenience.
So the chip would start out with crafting a wafer
Or
and it would give between 2 and 4 wafers (depending on the final recipe)
These wafers are essentially a silicon "base" for the final chip (using sand as it is a natural silison source IRL)
The second part of the chip would be the IC (integrated circuit) itself
and it would give 1-4 ICs, but the recipe and output will be changed to better match the final recipe and output for the wafer
Finally, the two items would be combined to make the final, programmable, placeable, chip
This recipe would (and should) yield 1 microchip.
My next thought was to use a "programmer" workbench that would use a GUI similar to the one in OP, this would allow you to "plug in" your newly crafted chip and supply the materials (redstone dust and sand/dirt) used to make the circuit.
Borrowing from TheEvilM in this thread, I decided the following.
I modified the image you posted to include my ideas, and I think it works fairly well (I might need some help on the graphic design portions).
The recipe for the bench itself i'm not sure about yet, but i think it should include redstone dust and possibly iron/gold (as these are excellent conductors IRL).
A debateable item would be a "replicator" bench, which would copy the design inside a chip into another chip. The design for this gui would be similar to that of the furnace, a set of spaces for raw materials (redstone dust, dirt/sand, and redstone torches), a space for unprogrammed chips, a space for the "master" programmed chip, and an output slot. If this is implemented, unprogrammed chips might end up being stackable so that you can mass produce that adder chip you built for your 128-bit calculator.
Possible restrictions/features:
2 inputs, 2 outputs (at first), labeled on the tile itself when placed4 I/O "ports" on the four sides of the tile, labeled by number (will also be labeled inside the programming GUI).Any and all feedback is appreciated.
I am planning on making this!!! So please provide me with all the feedback that you can!
0
Nice little script, however, you don't give the user the opportunity to type in the address they want, even though you reference that they can. (Just helping emphasize how difficult coding can be, even for something this simple.)
I personally prefer coding in Java, though I'm fairly proficient in C++ also. I once had to write a program for C++ (no gui, thank God) that would play the game "War"... 1000+ lines of code. half a dozen arrays, and about the same number of lists (variable length arrays). Pain. In. The. Butt. But it worked, LOTS of debugging, had to rewrite the whole thing once because I missed a semicolon and couldn't find it. Not Happy.