specialization in GRML web browsers
Bar Graph MDI (bar graphs, GRML web browsers)Headlines MDI (GRML web browsers)
Pioneer Report MDI (GRML web browsers)
Tree MDI (GRML web browsers)
Bar Graph MDI (bar graphs, GRML web browsers)
Headlines MDI (GRML web browsers)
Pioneer Report MDI (GRML web browsers)
Tree MDI (GRML web browsers)
Bar Graph MDI (bar graphs, GRML web browsers)
Headlines MDI (GRML web browsers)
Pioneer Report MDI (GRML web browsers)
Tree MDI (GRML web browsers)
It appears specializing is a viable strategy for implementing new features of GRML. Existing web browsers are focused on different things. Data-entry, image handling, data viewing, and data manipulation are focus areas of current web browsers.
To handle data-entry, more web browsers will be developed. Trying to maintain business activity using existing web browsers is not the easiest thing to do. Much of this is due to the nature of the controls used for display. When you are doing linking, editing, sorting, deleting, and reordering in the same control, limitations will become evident.
With an understanding of the limitations of trying to do everything using one control, the advantages of specializing become apparent. This not only applies to adding features to a web browser, but also to reading GRML. A consideration is to provide a base level of support for GRML in every web browser, but other features are used in specific web browsers.
Specializing applies to features such as sorting, grouping, and joining dimensions. It is conceivable a web browser not support every feature. Of course, once in development, the consequences of this approach will become clear.
posted by Don Marchand @ 7:06 PM
0 Comments:
Post a Comment
<< Home