Archive for January, 2007

Future is coming

Just finished watching this video, impressive, especially the place where Jeff Han browses Google Earth in 3D.

Based on this I see the following character for the future programmer. This will be a really big man with strong hands, because only strong man can wave with hands all the day. Will go to the athletic club today!

No Comments »

Keep the data clean

Force user to input valid data. If you don’t pay enough attention to this rule when you promote some functionality for the users you will face with need to adjust production data regularly. Here is the couple symptom which may signal you about the functionality review necessity:

  • Free input fields
  • Fields which mean the same but populate data from different sources or not populate it at all

Efforts to organize data during the initial state will be rewarded in future. The more obvious benefits are:

  • User will get better experience with search routines
  • Reporting results will be more clear
  • You will safe time writing ETL procedures when deside to build your Data Warehouse

Of course you will be not able provide full dictionary for every field, because you may be not absolute expert in some areas, but you may provide user with the possibility to fill this dictionary by their own since user is real expert, or at list you may add “Other” option to the list of values.

No Comments »

Fast print


Some time ago I was requested to write custom print functionality for the Webtop. It was necessary to send selected documents to the default user printer. Of course any Applet or ActiveX were not acceptable. After some time of thinking I found quite simple solution for it.

All the client stations were under Windows so I created two Active Script files. The first - “Prepare script” - create folder on the client machine, the second - “Print Script” scan this folder and run shell command ” -print”. After that I create “wsf” - Windows Script Host format in the Docbase and put my two scripts to the Docbase.

The next step requires Export container modification. This was the most complex thing in 5.2.5 and requires couple of lines in 5.3. In general words customized Export container first run View action for the “Prepare script”, then Export selected documents to the given folder on the client machine (the same as configured in scripts) and after that run View action for the “Print Script”. Below is the simple flowchart of the process

So this solution was successfully deployed in two locations . You may download compleate package from here.

No Comments »