View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003385 | NoesisGUI | Studio | public | 2024-06-11 17:18 | 2024-06-14 20:22 |
| Reporter | dstewart | Assigned To | jsantos | ||
| Priority | normal | Severity | minor | ||
| Status | resolved | Resolution | fixed | ||
| Product Version | Studio_Alpha | ||||
| Target Version | Studio_Alpha | Fixed in Version | Studio_Alpha | ||
| Summary | 0003385: New Noesis Projects Don't have a MainPage or GlobalResources Pre-Made | ||||
| Description | There are very few reasons why someone starting a new project would not a MainPage.xaml pre-made when creating a new project. Likewise, for GlobalResources, which currently does not exist until a first Resource is created. Therefore, we should pre-populate any newly-created .Noesis Studio projects with: | ||||
| Steps To Reproduce | N/A | ||||
| Platform | Any | ||||
|
What if user has an existing folder with XAML files that he wants to create a project for? Then we will add two new files that might be hard to notice if there are lots of files in the folder. |
|
|
That's a good point @Dario |
|
|
If I recall correctly, I think @Sergio in a call mentioned that we should pre-populate only if there are no XAML files already present in the project directory. |
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-06-11 17:18 | dstewart | New Issue | |
| 2024-06-11 21:54 | dfranjic | Note Added: 0009691 | |
| 2024-06-12 10:53 | jsantos | Assigned To | => jsantos |
| 2024-06-12 10:53 | jsantos | Status | new => assigned |
| 2024-06-12 10:53 | jsantos | Target Version | => Studio_Alpha |
| 2024-06-12 10:54 | jsantos | Note Added: 0009693 | |
| 2024-06-12 14:16 | dstewart | Note Added: 0009695 | |
| 2024-06-12 14:16 | dstewart | Note Edited: 0009695 | |
| 2024-06-14 20:22 | jsantos | Status | assigned => resolved |
| 2024-06-14 20:22 | jsantos | Resolution | open => fixed |
| 2024-06-14 20:22 | jsantos | Fixed in Version | => Studio_Alpha |