Logo # 20130705'0812

invisible box ;-)

Page 4 of 9   Go to the previous page   Home   Go to the next page

Home   Features   Alternatives   Developing   Issues   Roadmap   History   Authors   License  

QueryPony Home


This chapter is for programmers to speed up orientation in the code. As a user, you may rather shy away from here, otherwise you will onyl be puzzled.

Solution Overview

There are three projects in the solution:

Project Settings

Due to the single-file-delivery feature, the project settings of the three projects are a bit particular. Notably watch out for the following points:

Finally, I am astonished how transparent and smoothly above described project settings work (after they have been worked out once and settled). But you have to have those particularities in the corner of your eye, if you start fiddling with the projects and then experience funny effects.

Learn the Pony New Tricks

Any programmer attempting to chat up to QueryPony, where can she start? First and foremost: bugfix, bugfix, bugfix! But if then she is behind inventing new features, there are two main topics: refine existing database access and implement additional database types.

(1)   Refining Existing Database Access

The lowest common denominator between all database types is viewing tables. This feature is implemented for all addressed database types. But then, each database has more or less it's individual features. The steps to approach a refining task may be like follows.

(2)   Adding New Database Implementations

Providing the implementation of yet another database type, would consist of about the following steps.

Applied Programming Techniques

This is an overview, which programming techniques in general you can find in QueryPony (in case e.g. you are interested in sample code sequences for learning C# or the like). The sophisticated core design techniques (abstract classes, interfaces, threading) date back to Joseph Albahari's Query Express. The rather surface techniques came added with QueryPony.

Commenting Style

If you look into the code indeed, you may be shocked about a weired commenting style with cryptic numbers all over. Don't scare off please, just try to ignore cryptic numbers.

Those numbers are timestamps emitted while coding. They serve multiple purposes, e.g. they are like breadcrumbs to help to find my way back if I got stuck, or to group far apart sequences together. They serve as links between locations in code, documentation, outside files and paper notes. They serve as IDs for various items.

There is a bit hope: timestamps without relevant references have an expiration. From time to time, I thin them out, so they will not totally congest the source code.

More Details

If you want read even more details, considerations and raw ideas about QueryPony development, please inspect file devnotes.txt. A specific developer paper is QueryForm.


Imprint : www.trilo.de/imprint.html.