Codic Engine.Net:  Objectives

Objectives of the Codic Engine.Net:

1)  Decode any code given to it against the correct code set.

*PROVEN*    This has been accomplished when I added a second code set to the Engine--the more I add, the more solid my proof of accomplishing this becomes.  The Engine works off one base structure, with the actual code sets around it.  I seem to think of this as a decentralized architecture, and this is very beneficial because the Engine has been designed from the beginning not to favor one code set over another.  This means I did not design it to translate one specific code, or customize it; it is perfectly tuned to decode anything I put into it!

2)  Allow for hyperlinks to be made for automatic decoding of a code.

*PROVEN*  This is critical to the Codic Engine.Net's future success and "advertising."  By allowing codes to contain hyperlinks to the Engine, any user can decode a code instantly and with only a single click.  This is a marketing advantage because anyone who uses this hyperlinking feature "advertises" the Codic Engine.Net.  When a user clicks and loads the Engine's page, he or she will be aware of its existence, ability, and would be liable to make his or own code (because it's "cool"), completing the cycle.  I am depending upon this, or the project is a failure.  What is not advertised is not used and fails.

3)  Be able to use any code set online.

*PROVEN*  I have proven this by added the two most difficult code sets I have found to the Engine.  Every time I add a new set, it gets easier because all small bugs that might work on one code set are found and addressed.  Adding code sets is now simple enough, someone familiar with programming will be able to do this.  All code sets inherit a base class, which means the Engine can take in anything.  Most of a code set's metadata is documented within that code set's class file, so the Engine will know how to respond, especially while encoding (or making) a code for someone.  Encoding will be discussed in objective 4.

4)  Provide a UI for users to make a code from any given code set.

*PROVEN*    It's still in alpha, but the encoder works with most codesets.  To make a code, select "View Code Sets" from the Engine's decoder page, select a codeset, and then click the "MAKE A CODE WITH THIS CODESET".  The interface will pose question after question.  Just fill out the form, skipping what you want, and a code will be made for you right in front of your eyes.

5)  Allow users to edit an imputed code.

*PROVEN*    This was a bane of the previous, Windows version, of the Codic Engine.  Once users have a code encoded, or have someone else's entered in the form, I the Engine has the capability of allowing users to go back to the encoder and editing the code; the form is populated with what the user had previously chosen when making the entered code. 

This type of functionality is easy to do when we are talking about a straight one-answer type of code.  However, when we get into modifiers, it becomes a different story.  A simple, straight question may be,  "What state are you from?"  A straight answer would be, "North Carolina."  Modifiers make this complicated by saying, "I am from North Carolina, my uncle is from Texas, and I would like to take a vacation to Wisconsin."  Highlighting the correct choices on the encoder after the first one has proven to be a challenge, but has since been overcome.  In actuality, this was even more difficult a task than the decoder...  Take my advice; I've been through it once with the Windows application version, so I should be an expert on this subject by now.

And guess what; I don't think any other encoder online offers this capability.  Most other encoders you must start from scratch if you want to use the UI to edit the code you made.  This editing feature will work very well with the database of user accounts and codes I plan to make freely available.

6)  Provide the Codic Engine.Net as a Web Service

*PROVEN*  Like it or not, web services are "the next thing."  Once this gets up, people can use the Engine's web service to provide live decoding on their own sites!  How about that?  I believe I will provide two outputs for people--HTML to display and XML to work with as they please.

This has been proven way ahead of schedule.  Please reference the "Web Service" link in the side bar to see how you can use the power of the Codic Engine.Net on your .Net Framework-enabled web site!  We don't forecast any trouble, as this has already been tested on both our servers.

7)  Give users a space to store their completed codes for future retrieval.

*PROVEN* I want users to be able to store their personalized codes on my site so other users can see who has similar interests in the same subculture.  After this, users can email each other and friendships can take place.  It's almost like an online personals column.  However, the entries will be under my direct rule; I will delete porn, advertisements, and junk on sight.  I dislike advertising and have never allowed ads to be placed on any of my sites.  Hence, I don't get money, but I get peace of mind.

Progress:  The site stores user codes in an XML database, retrieves them effectively, adds user codes, and allows users to edit their codes. 

How can I help?

Contact me at Kaine (a) PhoenixPo.com.