Hi I really like appmap its just fantastic and gives an absolute head start!.
Not sure if in the planning but it would be invaluable if you could add some sort of saving of the plan and reloading of the plan.
This feature will be extremely useful if you want to map a slightly bigger app and save to xml or whatever for later use.
Also notice that if you do not have a big screen it would be nice to have some sort of scrolling.
Many thanks for making this very good tool free of charge
FANTASTIC WORK!
Totally missed out on the release of AppMap. Infragistic baking this UI flow control together with prism is so great. I want to rebuild all my XFORMS apps immediately start using prism again.
After watching all the videos and tried out the template, this was the first thing that came to mind. Why on earth can't I reload the plan and continue working on it until everyone involved is happy with the navigation and flow of the app.
Shouldn't be too hard to parse through the project and show the plan again. Yes if you have done some own stuff/hack in code behind it might not show up in the plan ..but that's ok.
Was also really impressed by infragistics controls that where presented (old video post), so one could say that is was AppMap that made me interested in Infragistics in the first place.
PLEASE ADD IT and you will have a tool that will last and can't be ignored ...and contribute to better coding practises as well :-)
I've looked into this, and it's just not something I want to do. For one, it would be extreme difficult and brittle. Not only would it require parsing all XAML in every view, but we would also need to determine a way to identify what navigation goes where, assuming the developer didn't change any navigation code. This is a very complex problem, and not something I want to even try to introduce.
Just save the plan and overwrite whatever is in the xaml? BettBe than not having a plan att all?
I mean you're using this initially anyways to draw up how the final app will look and most likely will drop the design phase once you're up and running with the project...and have saved tons of work thanks to AppMap.
Just add a dialog "this will overwrite... ;-)
You just need something that identifies whats been added by AppMap and switch those parts in the xaml and leave the rest (if exists) as is. AutomationId?
This is something we managed to do in some way. CNAO (Centro Nazionale di Adroterapia Oncologica) is a National Center in Italy to treat cancers based on high energy physics machines very similar to the machines that have been built at CERN (Geneva – Switzerland) or on your side at Fermilab (Chigaco) or BNL (New York) or SLAC (San Francisco). Only 6 centers in the world are now treating cancers with carbon ions and these kinds of machines.
As a matter of fact, we started our work looking at AppMap and Prism. We noticed that it was a very bright idea but it was difficult to move the stuff in a large production environment. Thus, we proposed a project to the European Union and we received a 3 year grant to develop a toolkit in which you could actually create applications based on Application Models (Enterprise level Application Patterns) and Visual Studio Wizards (at Project and Item level) so that you could add pages to existing applications and undo work. Models were devised on the base of a review of more than 100 applications already running in our environment in view of a remake. We are going to present the work in the next ICALEPCS 2019 conference in October in NY. If you are interested to have a hint about what we did I can send you the paper as soon as it is published. Of course, there is nothing to sell because it is a large work that will finish next year based on a very specific environment (our environment and possibly environments similar to ours): a book will be published aimed to developers and some tutorial videos will be done. The book and the videos will be publicly available.
By the way we have been using Infragistics products for more than 15 years and they are simply great!
Its much more complicated than that. We will never know what changes someone made to their app, or their XAML. Not only that, but the performance would be horrendous because we would have to walk every XAML tree in every view to find buttons that navigate to another view and then also try to determine the structure of that navigation stack (MasterDetail->Detail->NavPage->TabbedPage->SelectedTab->NavigationPage->ContentPage). We can also never overwrite any code that has been written. That is a huge no-no when it comes to code gen.