Our new customer of Prayog is expecting enhancements in reporting. Currently Prayog generates 'black and white' output; making it colorful is the requested improvement. As per our new customer feedback, we understand that coloring some of the report lines help getting doctor’s attention and achieve ‘non-verbal’ communication. We have seen instance where colors talk’s more than 'good looking' aspects and Prayog is going to use that factor effectively in its next enhancement release.
The team Prayog is now working on providing options for user to create colored reports. Our prototype output was quite impressive and we will soon release the updated version of Prayog.
Saturday, December 1, 2007
Extending Prayog 2007
Sunday, November 4, 2007
Quick Quest - Compact Edition
We see quite good opportunities for Compact Edition as this best suites personal user who can use this for their kid’s studies, private institutes and schools. The Compact Edition will be built using Microsoft’s latest Dot Net technology.
The new polished Compact Edition will be out by May 2008.
Thursday, October 18, 2007
Srushti.Observer
Tuesday, October 16, 2007
Quick Quest Presentation Hosted Online
Monday, October 15, 2007
Welcome, Dear Visitor
After posting few (in fact 2) articles on CodeProject, my web site hit rate has increased a lot. That pushed me to create a new page which briefly and effectively talks on our goals. I just thought of having a corroborative conversation and make an attempt to induce “Srushti” worm in visitor's thoughts, hoping that one day they may ping us and expect some sort of soft solution(s). Its not a strategy to attract my site visitors, In fact I am trying to provoke their thoughts and match that with our passion.
Srushti.Framework
Though I was aware of Microsoft Enterprise Library (EL), I dared to workout on my own framework. Reasons were, I wanted to put theory learnt into code and evaluate myself that how good I am in creating generic, scalable and reliable components. After finishing part of Framework, I downloaded Enterprise Library and did a comparision. There were many differences (naturally) and mine required little more maturity (as expected :).
During the construction cycle of framework, I realized many concepts, discovered many possibilities and it helped me to visualize objects and there collaboration rather simply the dot net code. I was able to clearly see design patterns coming to life and sitting in real time scenarios. I admit, I am in very initial stage and have long way to go.
Skin Design
Flexo is a personal accounting package. Since it is in very initial stage, it tracks only your expenses and generates variety of reports on it. (Recently I included income tracking module which is in alpha stage) In coming years Flexo will extend and mechanize most of money management activities under few button clicks. In parallel to cool features, creating a good and ease of user interface is also a head scratching work. It’s an art too. I don’t want to set more expectation saying that Flexo has very good interface but I feel it has got what it was expected to have.
When you download and check all screens in Flexo, one thing you will sure notice, Consistency. Just open any UI guidelines book, this will be a first statement and there is no way to skip this rule in my software too.
If we think traditionally, the design approach for consistent UI for all forms could be like these,
Create header-footer ActiveX/Custom/User control and place it on all forms or create a static class which has a drawing method to decorate runtime loading forms and thinking further to this, maintain one XML configuration file which will hold all coloring, fonts and size details from which our drawing method gets inspired and brushes it on all forms.
In dot net, we have one cool feature - Visual Inheritance, which allows us to create a master form and inherit this to all child forms. Whatever UI changes you make on a master form will affect all its children. Re-using the idea of above mentioned XML configuration file, use dot net App.config and define all fancy information in it. Associate values from app.config file to master form’s properties popularly known as setting dynamic properties and we are done! Whenever I want to change any color of my Flexo forms I will just update flexo.exe.config file and I don’t have to compile my application to reflect new changes.