![]() ![]() Var res = ( "Are you sure to close form?", "Closing Form", ) e.Cancel = res != WebMAP5 uses weaving in order to eliminate those problems, with the surprising result that much of the back end code can look virtually identical to the original C#/Winforms code. Objects had to be instantiated with () syntax instead of the new() keyword. Previous versions of WebMAP created complex code to handle common desktop-to-web problems like modal dialogs. One of the most fundamental changes in the product is the introduction of code weaving to dramatically simplify the server-side code (back end). With WebMAP5 we focused on four primary areas of improvement: WebMAP5 is the single biggest technology leap we’ve made since the release of the original Visual Basic Upgrade Wizard 15 years ago. One of our overarching goals from Day 1 has been to create machine-generated source code that was actually human-friendly. For example, the way we handled promises to deal with modality worked, but it left the source code with more clutter than we liked. We actually solved all these problems, but perhaps not in the most elegant fashion for some of them. And the transformation and engineering necessary to solve the problems above is complex and expensive. Not every app needs to get off the desktop, but many do. ![]() How do you translate one UX paradigm (Windows Forms) into a completely different one (HTML)?. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |