Quantcast
Channel: patterns & practices: Prism
Viewing all 1878 articles
Browse latest View live
↧

New Post: Navigation to Dynamic Modules

March 31, 2014, 11:18 am
$
0
0
Hello DRAirey1,

Based on my understanding, Prism's RequestNavigate() method would not register or load type names. It actually works with View key names which would be registered before in the container.
Therefore, adding the capabillity you described it would be causing for this method to handle a new different behavior, without considering the Single Responsibility Principle and possibly generating confusion on its complete job.

However, you could add this suggestion into the Issues section so the P&P Team would consider this feature for implementing it on future releases.

Regards.

Gabriel Ostrowsky.
https://blogs.southworks.net/gostrowsky
↧
Search

New Post: UI Validation for multiple views in a region does not work

March 31, 2014, 7:05 pm
$
0
0
Apologies for this late reply.

I have tried your suggestion earlier but here each time I navigate, I get the adorners. On the first time navigate without initiating any data capture, I should not validate. Only on click of Save I should validate before submit. For this reason, tried creating a bool value in the application context to identify Save click but does look like it helps since resetting the validation is a bigger pain. :(

Any thoughts or suggestions?

Regards,
Jeevan
↧
↧

Reviewed: Prism 4 - November 2010 (Apr 01, 2014)

April 1, 2014, 3:30 am
$
0
0
Rated 5 Stars (out of 5) - Excellent feature
↧

Released: Prism 4 Documentation (Nov 12, 2010)

April 2, 2014, 1:18 pm
$
0
0
This release contains the Prism 4 documentation in Help 1.0 (CHM) format and PDF format. The documentation is also included with the full download of the guidance.

Note: If you cannot view the content of the CHM, using Windows Explorer, select the properties for the file and then clickUnblock on the General tab.

Note: The PDF version of the guidance is provided for printing and reading in book format.

The online version of the Prism 4 documentation can be read here.

This title is also available from Microsoft Press in both printed and ebook forms. Order ithere.
↧

Updated Release: Prism 4 Documentation (Nov 12, 2010)

April 2, 2014, 1:18 pm
$
0
0
This release contains the Prism 4 documentation in Help 1.0 (CHM) format and PDF format. The documentation is also included with the full download of the guidance.

Note: If you cannot view the content of the CHM, using Windows Explorer, select the properties for the file and then click Unblock on the General tab.

Note: The PDF version of the guidance is provided for printing and reading in book format.

The online version of the Prism 4 documentation can be read here.

This title is also available from Microsoft Press in both printed and ebook forms. Order it here.
↧
↧

New Post: Prism 4.2 - WPF popup window customization

April 3, 2014, 1:52 am
$
0
0
I am just wondering whether it is possible to customize more a Popup window (PopupWindowAction) beyond setting the IsModal and CenterOverAssociatedObject properties of it. For example:
  • It would be great if the Minimize and Maximize button of the displayed view can be enabled/disabled
  • The view will always be shown in the the taskbar. A similar property like the ShowInTaskbar would be very useful.
For a relevant example, please open the <Quickstart>\Interactivity.

Thanks.
↧

New Post: Docking Extension for Prism

April 3, 2014, 8:18 pm
↧

New Post: WPF Ribbon control and commands to bind to the ribbon buttons inside each tab.

April 3, 2014, 8:22 pm
↧
Search

New Post: Docking Extension for Prism

April 4, 2014, 2:02 am
↧
↧

New Post: Prism 4.2 - WPF popup window customization

April 4, 2014, 10:46 am
$
0
0
Hi,

You would be able to extend the Customizable Window Properties by modifying the Interactivity project from the Prism Library.

Both properties you mentioned may be configured from the corresponding InteractionRequestViewModel raise methods according to each popup view desire Style. In order to accomplish this, you would need to implement the desired Properties into the INotification (and also Notification) class, and generate the Bindings into them from the DefaultNotificationWindow.xaml class. You could also extend more Window properties in the same way than these ones described.

The following code shows how the CustomPopupView would have the Maximize and Minimize buttons disabled. And the DefaultNotification popup would have configured not to be shown in the TaskBar:
InteractionRequestViewModel.cs
...
privatevoid RaiseCustomPopupView()
{
     // In this case we are passing a simple notification as a parameter.// The custom popup view we are using for this interaction request does not have a DataContext of its own// so it will inherit the DataContext of the window, which will be this same notification.this.InteractionResultMessage = "";
     this.CustomPopupViewRequest.Raise(
         new Notification { Content = "Message for the CustomPopupView", Title = "Custom Popup", ResizeMode = ResizeMode.NoResize, TaskBar = true });
}
...
privatevoid RaiseNotification()
{
     // By invoking the Raise method we are raising the Raised event and triggering any InteractionRequestTrigger that// is subscribed to it.// As parameters we are passing a Notification, which is a default implementation of INotification provided by Prism// and a callback that is executed when the interaction finishes.this.NotificationRequest.Raise(
        new Notification { Content = "Notification Message", Title = "Notification", ResizeMode = ResizeMode.CanResize, TaskBar = false },
        n => { InteractionResultMessage = "The user was notified."; });
}
publicinterface INotification
{
    ///<summary>/// Gets or sets the title to use for the notification.///</summary>string Title { get; set; }

    ///<summary>/// Gets or sets the content of the notification.///</summary>object Content { get; set; }

    ///<summary>/// Gets or sets the resize mode of the notification window.///</summary>
    System.Windows.ResizeMode ResizeMode { get; set; }
        
    ///<summary>/// Gets or sets the a boolean for being the Notification Window visible on the task bar.///</summary>bool TaskBar { get; set; }
}
I hope this helped,
Regards.

Gabriel Ostrowsky
https://blogs.southworks.net/gostrowsky
↧

New Post: UI Validation for multiple views in a region does not work

April 4, 2014, 11:10 am
$
0
0
Hi Jeevan,

Based on my understanding you have successfully got the adorners every time you navigate to a View.
Therefore, adding a boolean parameter for the Save action should not affect the validation resetting. It may just enable/disable the adorners from being viewed and submitted.

If I haven't understand correctly I would appreciate if you could describe what action would be difficult to implement, and send a sample from which I could get a better understanding of the problem and find a proper solution to it.

Regards.
Gabriel Ostrowsky
https://blogs.southworks.net/gostrowsky
↧

Reviewed: Prism 4 - November 2010 (4 05, 2014)

April 5, 2014, 4:04 am
$
0
0
Rated 5 Stars (out of 5) - Please release nuget.org.
↧

Reviewed: Prism 4.2 for .NET 4.5 (4 05, 2014)

April 5, 2014, 4:06 am
$
0
0
Rated 5 Stars (out of 5) - It's very good work. I try BasicMVVMQuickstart_Desktop quickstart. but I don't found MainWindowViewModel and QuestionaireViewDesignViewModel classes. -- @blainew thenk you very much. can you release nuget.org? I want to install this at nuget.
↧
↧

Reviewed: Prism 4.2 for .NET 4.5 (4 05, 2014)

April 5, 2014, 4:06 am
$
0
0
Rated 5 Stars (out of 5) - It's very good work. I try BasicMVVMQuickstart_Desktop quickstart. but I don't found MainWindowViewModel and QuestionaireViewDesignViewModel classes. -- @blainew thank you very much. can you release nuget.org? I want to install this at nuget.
↧

New Post: Prism+MEF: using TreeView through Prism & MEF Framework

April 6, 2014, 3:32 am
$
0
0
Hi;
I've been looking around forums but haven't found any satisfying help about using Treeview control within context of MVVM + Prism + MEF.
The most close thing was Josh Smith Article where he implemented Treeview control using ViewModel pattern as per this article at CodeProject .
My concern is to impose the Prism+MEF framework on this example :
1-How to create all the ViewModel Wrapper classes via MEF
2-How each ViewModel can Load & Populate the Child ViewModel using MEF and w/o using [new] operator

It would be very generous if you could build the same example using Prism+MEF as it would be a standard way to using such very important and hierarchical control in our Prism based applications.
Thanks for your valuable support.
↧
Search

New Post: Navigation to Dynamic Modules

April 6, 2014, 5:19 pm
$
0
0
Gabriel,

A URI is a "UNIVERSAL" resource identifier, meaning it contains all the information needed to locate a resource in your application. In the .NET world, that includes the assembly in which a type resides. If I have loosely coupled modules, then I need to know which module contains a given type before I can navigate to it.

What astounds me is that this is baked into WPF and Silverlight navigation. Why would you make your framework less functional than the one it's supposed to be replacing?

Don
↧

New Post: OMG - Where is the Journal Back Stack?

April 6, 2014, 5:26 pm
$
0
0
I'm coming down the home stretch of converting my substantial WPF application into Prism and I've just hit a major wall. Where is the access to the navigation stack? WPF and Silverlight have a concept of RemoveBackEntry which is critical in any real-life application. Let's say I've just navigated to:

pack://application:,,,;/Customers?path=\Customer\JohnSmith

Which is a maintenance page for customers. Now I change the name to 'JohnSmythe'. The URI that I used to navigate to this page is no longer useful and will actually corrupt the navigation because we can't find this resource any more (because the name has changed). Unfortunately, it's still on the navigation stack.

So where is the 'RemoveBackEntry' function and/or access to the journal stack? You can't possibly build a real-life application without being able to remove entries that have been made obsolete.
↧
↧

New Post: Determining the Uri for NavigationJournal.GoBack()

April 6, 2014, 6:01 pm
$
0
0
Damian,

Thank you as well. I was really starting to doubt how well my investment in Prism was when I wasn't able to access the Back Stack. This is a pretty basic operation and I was just dumbfounded that it wasn't part of the architecture. I'm a little less negative because this suggestion worked out pretty well. I was able to replace the Journal with a custom one that provided the needed access to the stacks.

Still, I don't understand the design decision. Yes, you guys did good making it extensible, but every other navigation system allows you to at least modify the previous back journal entry. Why was this left out of the default Prism library?
↧

New Post: OMG - Where is the Journal Back Stack?

April 6, 2014, 6:08 pm
$
0
0
OK. Since they don't allow these posts to be deleted, I'll answer my own question. I'm not sure why they left the 'RemoveBackEntry' feature out of the default library, but they have made it rather trivial to override the existing classes. I was able to basically just cut and paste the 'default' version of the RegionNavigationJournal and as long as I gave it an 'IRegionNavigationJournal' alias, the navigation system was able to find it and us it. I simply exposed the Back stack and I was in business.

Again, this is a basic feature. I greatly appreciate the 'lean and mean' consideration, but any real-life application is going to need to examine the forward and backward stacks and remove at least the most recent entry on the back stack. I'd like to hear what the design consideration was to make it private.
↧

New Post: OMG - Where is the Journal Back Stack?

April 7, 2014, 10:29 am
$
0
0
Hi Don,

Thank you for replying the solution you could accomplish. Instead of removing your initial question, it is much better to reply and post your solution because your work would be helpful for users that may go through the same or similar problem.

I think the right anwswer regarding your design question would only be done by the P&P Team. However, based on my understanding I would think that default apps would not need to remove a specific View manually. Furthermore, you would be adding the related responsibility to someone that would not be appropiate.

Regarding the scenario you described, I am afraid I don't completely understand how you would change the View name with the Application running. Any available View that you would be able to Navigate to would have been already loaded and registered in a specific Region. That is why I don't see the problem you mentioned. Plus, I understand that if a View source name is modified, then a rebuild would be needed. Please, let me know if there is something that I missunderstood.

Maybe you could find helpful the Navigation chapter on MSDN Prism's Guide:

I hope I could provide some better understanding about the Region/NavigationPrism design.
Regards,
Gabriel Ostrowsky.
https://blogs.southworks.net/gostrowsky
↧
Viewing all 1878 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>