WECPOF
(Automatically adding template at the end of the page.) |
(Adding message template to the top of the page) |
||
| Line 1: | Line 1: | ||
{{message|Write the content here to display this box}} | |||
'''WECPOF:''' This is what we call the prototyping motor. The motor is part of MDriven Designer and can be used to quickly execute the model, including ViewModel UIâs and actions. The WECPOF engine got its name from mixing ECO with WPF. Since then, ECO has changed its name to MDriven Framework â and the WECPOF motor is used for WPF, MVC, and AngularJS. The name is still used to denote the prototyping ability and the runtime assembly MDriven Framework users can use to get the Prototyping engine inside their own applications (WECPOFLogic.dll). | '''WECPOF:''' This is what we call the prototyping motor. The motor is part of MDriven Designer and can be used to quickly execute the model, including ViewModel UIâs and actions. The WECPOF engine got its name from mixing ECO with WPF. Since then, ECO has changed its name to MDriven Framework â and the WECPOF motor is used for WPF, MVC, and AngularJS. The name is still used to denote the prototyping ability and the runtime assembly MDriven Framework users can use to get the Prototyping engine inside their own applications (WECPOFLogic.dll). | ||
Revision as of 22:40, 16 June 2024
This page was created by Alexandra on 2018-11-07. Last edited by Stephanie on 2025-02-24.
Write the content here to display this box
WECPOF: This is what we call the prototyping motor. The motor is part of MDriven Designer and can be used to quickly execute the model, including ViewModel UIâs and actions. The WECPOF engine got its name from mixing ECO with WPF. Since then, ECO has changed its name to MDriven Framework â and the WECPOF motor is used for WPF, MVC, and AngularJS. The name is still used to denote the prototyping ability and the runtime assembly MDriven Framework users can use to get the Prototyping engine inside their own applications (WECPOFLogic.dll).
See: