WebSupport |
Edit this page |
Libraries to support web applications should be a high level of abstraction. Rather than support cookies and session ids, Wheat's libraries for web applications should be at the level of user accounts, persistent session data, user preferences, web calendars, etc.
Blocks of functionality in Wheat must come not only as class libraries but with full web based UI components (via the TemplateEngine). For example, rather than just supply a Date/Time class that handles date calculations, the Date/Time library must include reusable templates for calendars, date & time forms, and date/time indexed data storage (events in a calendar.).
Blocks of functionality in Wheat must come not only as class libraries but with full web based UI components (via the TemplateEngine). For example, rather than just supply a Date/Time class that handles date calculations, the Date/Time library must include reusable templates for calendars, date & time forms, and date/time indexed data storage (events in a calendar.).
There is no comment on this page.
[Display comments/form]
