I’ll definitely take your advice.

One suggestion might be to store some data twice. For example, maybe store each post (all the details about it except for sub objects like comments) as individual files, but then also store different lists of posts in another file like PostsByArea.xml, PostsByTag.xml, etc. It means you have to do a bit more work when saving, but reads will be really fast. This is sort of how Azure storage works.

I’ve written most of the XML provider, but I fear that I won’t have enough time to finish it within reasonable time. I’ll try and post it somewhere so others can contribute.

(Same for the skin).

Your skin looks nice. If you’d like to share it with others, let me know. http://oxite.codeplex.com/Wiki/View.aspx?title=skins Our list is pretty short at the moment.

Thanks again for checking out Oxite and keep the feedback coming. We’re listening.

Let us take an example from the credit card world. Every time you make a new release of a solution, no matter how minute the changes to the code, the entire solution has to go through rigorous testing, and the code has to be reviewed by a third party (to make sure you did not add any rules that make all purchases made with your credit card magically disappear). It would also require that the said third party have a very good understanding of the programming language you are using and can spot security vulnerabilities, SQL injection, buffer overflow issues and so on. This can take weeks, or even months and is very expensive.

Now imagine that the credit card rules change every week. How would you keep up?

By using the approach above, your code remains the same, but the *configuration* can change every week. And therein lies great value.

The new configuration is much easier and a lot less expensive to review and test. It’s highly isolated and doesn’t need to be reviewed by a programmer with security expertise. The process of updating the validation rules could then take as little as a day or two. That’s a lot of time and money saved.

After the initial release, the greasemonkeys and suits can take care of your solution all on their own, and you can move on to other solutions, as opposed to you having to go back to make changes to it every week and spending the rest of your career overseeing test protocols

But the value proposition of using M to validate credit card numbers is that we replace If-Else statements in C#/VB/C/C++/Java/[insert widely used programming language] with If-Else statements in your own defined language?

What am I missing?

Once you’ve started Intellipad with samples enabled, you can hit Ctrl+Shift+T, at which point you’ll be prompted for an existing mgrammar (.mg) file. You can create an empty text document somewhere on your computer and rename it to .mg. Select the file and open and you’re good to go.

I agree this isn’t the most intuitive solution, but it does the trick.

Have a look at this blog post by the Intellipad team blog for more info:

http://blogs.msdn.com/intellipad/archive/2008/10/29/creating-and-editing-mgrammar-files-with-intellipad.aspx

More power is being given to corporations and big business with the general public left with the short end of the stick. I’m rather at a loss of what to do about it. It’s obvious that these governments wont listen to common opinion on the subject, so what does that leave us?

*shakes head*