Development Roadmap |
||
 CinC snarkles Most of the work done to this point has been planning-related: Figuring out the overall class structure, creating documentation for developers, etc. which is for the most part done now. It appears there's been a bit of confusion regarding the overall scope/direction of this project, so here is some clarification (in terms of what I have in mind, at least): Iteration 1 This will essentially be a reformulating of the current SNEAK script in Java. This is both to satisfy the requirement of creating an "offline" version of the script, and is also intended to help "newbies" get their feet wet in the development process, as most of the methods in the current script shouldn't give people too much trouble. There will be two "phases" of this development: 1. The class library (this is what we're working on now) 2. After that's finished, the GUI (probably written in Swing for cross-platform compatibility, but developers would be welcome to create native GUIs on their own platform if they want as "unofficial" builds) Iteration 2 Expansion of SNEAK with additional crypt methods, such as RSA, Blowfish, Morse Code, Atbash, and whatever else we can think of (will spec this out more specifically as the time draws nearer) Iteration 3 This will introduce the ability to do more advanced things such as file/network stream encryption, PGP key generation & encryption/decryption, maybe a "Cryptographer's workbench" which has tools for things like finding incidene etc. (this will have to be specced out A LOT more thoroughly by the time we get here ;)) And from there, we'll see where we go, based on user input, etc. --------------------------------------------------------------------- There's also been frequent discussion on the Desktop vs. Web issue. At first, Java really seemed like the "do everything" language, as we could create both a web version and desktop version from the same code base, thus avoiding having to maintain multiple copies of the source. However, it's my firm belief that the reason the current SNEAK script has gained as much popularity as it has is because: a) It's been written in a language that every Tom, Dick, and Harry has on their free/low-cost web host. b) It's dead-simple to install. Just upload one file and it's done. c) It's very bare-bones so it has almost immediate response time for doing one-off "quick and dirty" translations This is definitely not the case for something like JSP or Applets. The compiled binary solution proposed below initially caught my attention, but we'd have to compile binaries for every platform under the sun, and now users are going to have to mess around with chmod, paths, etc. No longer is installation a simple matter that a beginner user could accomplish. Therefore, my feeling is that we should leave SNEAK in two development branches: the desktop version (Java) and the "light" web version (PHP). The desktop and web versions will have similar functionality in terms of the basic "change this text into something else" stuff (so, essentially, the stuff in iterations 1 and 2), but any "advanced" features such as file encryption, or having to do with PGP, etc. will be a desktop feature only. This only makes sense, as if you care about a file enough to encrypt it with PGP, you surely don't want to upload it to some stranger's web server and trust that they won't intercept the contents of it. :P It will create a bit more work, but in the end neither sacrifices the power and cross-platform compatibility that will be in the Java version, nor the ease of installation and use of the current PHP version. Comments/ideas/thoughts? Replies:
|
||
| CyberArmy::Forum v0.6 Generated In 0.00547 seconds |