Save Suggestion
(Recommended: Basic knowledge in Visual Studio software.)
- Docking the "Save" feature as an interface to maintain code that worked before tinkering with other features, structure, and form windows may save time, energy, and confusion for us all.
- The "Save As" option provides a different window, an entirely new filepath and memory space needed for its recollection without the ability to compare.
- The history of save (in program), a feature on another platform with textEditors (no longer available, Atom) that allowed the history of change to be recalled without modifying name, but automatically saved it for reference in history to recount steps (undo buttons work in this degree) can be referenced.
Problem: Visual Studio allows multiple forms, 'solution' is a container for file source paths and its "accessory" of directories that can use external sources but has no feature with 'save' to weave code in a preferred order that can build without a problem.
When there is a problem, have the ability to recount steps on what worked - what changed - and the last operable sheet of code to work with as the new base, instead of completely over.
I would like to see a visualized map that handles like a prezi presentation. Trees are formed and you want to see the result of what is being requested. This will probably end up being the business model once its all hashed out. Where's the job security in this rant?
I know many people out there, especially learning VS, have had started - messed up - and need to redo the entire GUI, save path, or code altogether. Time Management is all I am looking for here.
Solution: Expand on the "Undo" button a little bit more and provide a save feature in a flexible memory space that builds in secret (red error lines) and using the Option Statements (Explicit, Strict, and Compare Statements that determine the syntax flexibility when writing code and how to evaluate code by data types) to determine a strong/weak structure to operate GUI declared variables effectively.
- The code directory should be just as useful as the ToolBox. Make it available so we can dissect, familiarize, alphabetically find it with those options. I see the packages that we download, but I do not know what comes with what and why. I have not reached that level of programming knowledge yet - and anticipate not needing it until special projects come around. Holding onto this volatile memory, susceptible to virus? Perhaps trim the software to reveal this in download, offline formats upon need. Presenting the need in example is going to be the change in software design.
- "Save" (besides the menuTask bar that can indicate these settings with a form in visual studio) does snapshots of work thus far, if not complete - so, I want this to snapshot each save that I do and be able to compare. Ex: Orange, Red, Yellow are saved. I can bring them up and the minor changes I did on them, handle like the adobe express layering technique for images, textures, colors, fonts, etc. All the way through the entire image if necessary. These provide me with options on how to proceed, count, limit my program. It is also necessary to consider hacking thoroughly by rejecting these designs or creating them as catchers to prevent it, using that volatile memory as a false loot. The multiple design paths that can be constructed indicate a main path with sub path coordinates to this "false loot" which is either operable - actual running licensed software design or compatible data that is cleaned out and detected. I have not taken a course in data security or cybersecurity but I am interested to see if this is plausible.
Save Me
Object Oriented Programming and the terminology being used are keystone species for online navigation and in the world of cyberspace, there isn't really a structure humans can relate in prior knowledge upon keyboard strokes to invoke any actions.
What is the idea behind internet, what imagery are they using to describe its use?
I imagine a navigational world of words and verbiage that jumbles together to be strung out one at a time and placed in containers to use in a push-shove world. If you get in the way of the push-shove, it collapses. The roads paved are networked in layers and upon the top tier is a breath of fresh air we would consider in new development. Not in foundational development - which is a shame.
I know the buildings in this imagery are contained with pre-developed code that took ancient bone breaking postures the epitome of calculating its working order, but do we all have to suffer at some extent in order for it to be appreciated? The answer will probably shock you, and I half-heartedly agree.
Building atop these monstrous defeats could be recalculated again. We need waves of disciplined programmers to separate by organization of an American system to uphold and maintain job security with core education that revolves around organizing its designers. Obviously, the software would keep improving but the programmer would need to have a base education - depending on its degree of contact with foundation.
It is a cracked code, easily navigational, and improves from the ground up. The stronger we make those experiences and improve from them together - the more work that can be done, effectively. All are equal in importance of an operable system into a network of distributing powers.
I am familiar with the competition in programmers and know we hold each other back much too often than support each other. The structure can support all of us and the job security of ancient programming must persist, be cleaned, and restored for alternative measures in upgrade that define the cyberspace with object-oriented programming obstacles, pathways, and innovation for futuristic models to use. There are so many facets of technological languages - minimalizing protects commercial internet space. That's where the money is though...
*Also - saving comments using the Prezi presentation style and adobe layering techniques - was meant to create the need for it. I want the save and auto-correct to attune to the closest and best work you did on this program for machine efficiency and speed to be something of an autosave and tree-branching an add-on does for us. I suppose artificial intelligence embedding arcs that will be how we develop its neural networking for troubleshooting. What a dangerous thing to invent! Keep it offline and use in national emergencies or something - but every second with it is deathly to be breached or imprinted with its own time - (exasperated breath) - I think I am over paranoid about it now, but, for good reason. We need a security system of allowance for AI, something that will be puzzle/maze/encryption/time/space/barriers of power for something like that. We need to preserve our programming skill and troubleshooting like the gold it is!
