際際滷

際際滷Share a Scribd company logo

What\'s new in the VLF and RAMP

T
thedonn57

The document discusses the VLF framework, RAMP, and recent developments. It summarizes that RAMP allows old 5250 screens to interact with new components by following the same application model. It also announces that support is being added for .NET and additional 5250 screen components to further encourage RAMP-based applications by lowering costs and risk through reuse of existing skills.

1 of 13
What is the VLF? What is RAMP? What have we been doing lately? Why have we been doing this? (all answered in < 10 minutes)
VL Windows Rich Client
L4Web Web Browser
.NET Windows Rich Client/Web Browser
Applications Business Objects or Instruments Filters Instance Lists Commands One Simple Application Model Deployable as: Windows Rich Client Web Browser .NET Application
Commands (and Filters) are coded or generated and then snapped into the framework for execution Command Handler Snap In Component
油
Right now a snap in component may be a: VL Component WEBEVENT Function WAM (Web Application Module) HTML/AJAX Component 5250 Screen (presented by newlook from looksoftware) They all work together and can be intermixed because they all follow the same simple application model (ie: applications, business objects, instance lists, filters and command handlers).
Right now a snap in component may be a: VL Component WEBEVENT Function WAM (Web Application Module) HTML/AJAX Component 5250 Screen (presented by newlook from looksoftware) They all work together and can be intermixed because they all follow the same simple application model (ie: applications, business objects, instance lists, filters and command handlers). Mixing 5250 screens so that that can interact with the other components is what we call RAMP . The old gets mixed in with the new The old gets taught some new tricks The old gets progressively replaced by the new
Right now a snap in component may be a: VL Component WEBEVENT Function WAM (Web Application Module) HTML/AJAX Component 5250 Screen (presented by newlook from looksoftware) Next week we are releasing support for two new types of snap in components: .NET components (typically coded in C# or VB.NET) 5250 Screen (presented by aXes-TS from LANSA) They also can be intermixed with all of the snap in types already supported
Right now a snap in component may be a: VL Component WEBEVENT Function WAM (Web Application Module) HTML/AJAX Component 5250 Screen (presented by newlook from looksoftware) Next week we are releasing support for two new types of snap in components: .NET components (typically coded in C# or VB.NET) 5250 Screen (presented by aXes-TS from LANSA) They also can be intermixed with all of the snap in types already supported Designed to encourage new RAMP based business: Lower initial training costs by reusing existing skills Lowers some customers perception of risk Right now a snap in component may be a: VL Component WEBEVENT Function WAM (Web Application Module) HTML/AJAX Component 5250 Screen (presented by newlook from looksoftware) Designed to encourage new RAMP based business: Lower initial training costs by reusing existing skills Lowers some customers perception of risk Designed to encourage new RAMP based business: Lower initial training costs by reusing existing skills Lower customer perception of risk
Right now a snap in component may be a: VL Component WEBEVENT Function WAM (Web Application Module) HTML/AJAX Component 5250 Screen (presented by newlook from looksoftware) Next week we are releasing support for two new types of snap in components: .NET components (typically coded in C# or VB.NET) 5250 Screen (presented by aXes-TS from LANSA ) They also can be intermixed with all of the snap in types already supported The business case for this is strong: New business revenue Maintenance revenue 油 Pricing and discounting Account control Support Product Architecture and Direction
Questions

More Related Content

What\'s new in the VLF and RAMP

  • 1. What is the VLF? What is RAMP? What have we been doing lately? Why have we been doing this? (all answered in < 10 minutes)
  • 2. VL Windows Rich Client
  • 3. L4Web Web Browser
  • 4. .NET Windows Rich Client/Web Browser
  • 5. Applications Business Objects or Instruments Filters Instance Lists Commands One Simple Application Model Deployable as: Windows Rich Client Web Browser .NET Application
  • 6. Commands (and Filters) are coded or generated and then snapped into the framework for execution Command Handler Snap In Component
  • 7. 油
  • 8. Right now a snap in component may be a: VL Component WEBEVENT Function WAM (Web Application Module) HTML/AJAX Component 5250 Screen (presented by newlook from looksoftware) They all work together and can be intermixed because they all follow the same simple application model (ie: applications, business objects, instance lists, filters and command handlers).
  • 9. Right now a snap in component may be a: VL Component WEBEVENT Function WAM (Web Application Module) HTML/AJAX Component 5250 Screen (presented by newlook from looksoftware) They all work together and can be intermixed because they all follow the same simple application model (ie: applications, business objects, instance lists, filters and command handlers). Mixing 5250 screens so that that can interact with the other components is what we call RAMP . The old gets mixed in with the new The old gets taught some new tricks The old gets progressively replaced by the new
  • 10. Right now a snap in component may be a: VL Component WEBEVENT Function WAM (Web Application Module) HTML/AJAX Component 5250 Screen (presented by newlook from looksoftware) Next week we are releasing support for two new types of snap in components: .NET components (typically coded in C# or VB.NET) 5250 Screen (presented by aXes-TS from LANSA) They also can be intermixed with all of the snap in types already supported
  • 11. Right now a snap in component may be a: VL Component WEBEVENT Function WAM (Web Application Module) HTML/AJAX Component 5250 Screen (presented by newlook from looksoftware) Next week we are releasing support for two new types of snap in components: .NET components (typically coded in C# or VB.NET) 5250 Screen (presented by aXes-TS from LANSA) They also can be intermixed with all of the snap in types already supported Designed to encourage new RAMP based business: Lower initial training costs by reusing existing skills Lowers some customers perception of risk Right now a snap in component may be a: VL Component WEBEVENT Function WAM (Web Application Module) HTML/AJAX Component 5250 Screen (presented by newlook from looksoftware) Designed to encourage new RAMP based business: Lower initial training costs by reusing existing skills Lowers some customers perception of risk Designed to encourage new RAMP based business: Lower initial training costs by reusing existing skills Lower customer perception of risk
  • 12. Right now a snap in component may be a: VL Component WEBEVENT Function WAM (Web Application Module) HTML/AJAX Component 5250 Screen (presented by newlook from looksoftware) Next week we are releasing support for two new types of snap in components: .NET components (typically coded in C# or VB.NET) 5250 Screen (presented by aXes-TS from LANSA ) They also can be intermixed with all of the snap in types already supported The business case for this is strong: New business revenue Maintenance revenue 油 Pricing and discounting Account control Support Product Architecture and Direction