New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"Pages" and "Views" naming #41

Closed

ralarcon opened this issue Mar 21, 2017 · 4 comments

Assignees

Labels

question

Contributor

ralarcon commented Mar 21, 2017

We handle the concept of pages (in the wizard, in the templates and so on). For a certain page, the view part (xaml file) need to be called "xxxxView.xaml", for example, the "Blank Page" selected from the wizard will generate the following files:

Model/
• Blank1Model.cs
ViewModel/
• Blank1ViewModel.cs
View/
• Blank1View.xaml

That is, the "Blank Page" template will generate the Blank1View.xml

We want to double check that it is fine to have the templates called "Page" generating "Views".

Then, for the Code Behind framework, the xaml file will be named "xxxView.xaml" in order to be able to "reuse" as much xaml code as possible. Is that fine as well?

ralarcon assigned mbcrump, crutkas and ralarcon

ralarcon added the question label

Member

crutkas commented Mar 22, 2017

Issue you'll hit is Code behind. Those are called pages. MainPage.

For Views, it would be MainView.

possible to do things like includes to work around to share code?

Contributor Author

ralarcon commented Mar 24, 2017 •

edited

We are going to wait until having a mock app for the Code Behind to evaluate how to implement the naming differentiation using the same source files.

Once we have the final decision on CodeBehind coding style we see if the naming is an issue.

mrlacey mentioned this issue

Code Behind: Page vs View naming #80

Closed

crutkas closed this as completed

crutkas reopened this

Member

crutkas commented Apr 5, 2017

@ralarcon and @mvegaca i see this #80 is fixed in may branch, this should be resolved then as well?

Contributor Author

ralarcon commented Apr 5, 2017 •

edited

Yes, we are making final verifications. I'll close it when changes merged to dev.

crutkas closed this as completed

ghost locked as resolved and limited conversation to collaborators

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.