Jump to content

GLA Summit 2020/Migrating a mature application and plugin infrastructure to an architecture based on PPLs: Difference between revisions

From LabVIEW Wiki
← Older edit
VisualWikitext
mNo edit summary
m Update with infobox and presentation template
 
Line 1: Line 1:
'''Migrating a Mature Application and Plugin Infrastructure to an Architecture Based on PPL''' by Justin Young, PhD.
{{infobox
|category=presentation
|icon=GLASummitButton.png
|presentation-conference=GLA Summit 2020
|presentation-presenter=Justin Young
}}


''LabVIEW’s Packed Project Libraries (PPLs) offer several advantages for users and developers.  As this build technology has matured, several presentations and white papers on the topic have focused on using PPLs to create plugin infrastructures.  However, their focus is on new development and prototypes/demonstrations. Aside from a few NI/LAVA board posts, little information is available on how strategies and pitfalls related to migrating mature applications with modular plugin-based design.  Here we discuss our experience in doing such a migration including: motivations, key challenges, lessons learned, and outcomes – all of the ingredients needed to answer the question: “Was it worth it?” We will conclude the session with a Q&A / Discussion on related user experiences including best practices on this topic.''
{{presentation
|presenters=Justin Young
|abstract=LabVIEW’s Packed Project Libraries (PPLs) offer several advantages for users and developers.  As this build technology has matured, several presentations and white papers on the topic have focused on using PPLs to create plugin infrastructures.  However, their focus is on new development and prototypes/demonstrations. Aside from a few NI/LAVA board posts, little information is available on how strategies and pitfalls related to migrating mature applications with modular plugin-based design.  Here we discuss our experience in doing such a migration including: motivations, key challenges, lessons learned, and outcomes – all of the ingredients needed to answer the question: “Was it worth it?” We will conclude the session with a Q&A / Discussion on related user experiences including best practices on this topic.
|youtube-id=iesJN8_kuMU
}}


 
==External links==
<div style="text-align:center;"><youtube width="800" height="600">iesJN8_kuMU</youtube></div>
*[https://www.glasummit.org/presentation-list/2020 GLA Summit 2020 Presentations]
 
==Presentation Links==
* [https://youtu.be/iesJN8_kuMU YouTube Video Link]
 
==See Also==
{{ambox|text=Add links to internal wiki pages that would also help.}}
 
==External Links==
{{ambox|text=Add links to external resources that would also help.}}


[[Category:GLA Summit 2020]]
[[Category:GLA Summit 2020]]

Latest revision as of 19:15, 21 August 2024

Migrating a mature application and plugin infrastructure to an architecture based on PPLs
Conference GLA Summit 2020
Presenters Justin Young
Migrating a mature application and plugin infrastructure to an architecture based on PPLs by Justin Young

LabVIEW’s Packed Project Libraries (PPLs) offer several advantages for users and developers. As this build technology has matured, several presentations and white papers on the topic have focused on using PPLs to create plugin infrastructures. However, their focus is on new development and prototypes/demonstrations. Aside from a few NI/LAVA board posts, little information is available on how strategies and pitfalls related to migrating mature applications with modular plugin-based design. Here we discuss our experience in doing such a migration including: motivations, key challenges, lessons learned, and outcomes – all of the ingredients needed to answer the question: “Was it worth it?” We will conclude the session with a Q&A / Discussion on related user experiences including best practices on this topic.



External links

Retrieved from "https://labviewwiki.org/w/index.php?title=GLA_Summit_2020/Migrating_a_mature_application_and_plugin_infrastructure_to_an_architecture_based_on_PPLs&oldid=33937"