Archive for category Soapbox Core
I’ve just pushed the latest version of SoapBox Core (2010.11.29) and the Pin Ball Demo to the SVN repository. You can download them from the downloads page. This release has a handful of new features. You can read the details at ask.soapboxcore.com.
I’ve just pushed the latest version of SoapBox Core (2010.09.11) and the Pin Ball Demo to the SVN repository. You can download them from the downloads page. This release has a handful of new features. You can read the details at ask.soapboxcore.com.
We’re excited about the response we’ve received about SoapBox Core, mostly over at the CodeProject Article. We decided we needed a better and more dynamic support site for SoapBox Core, so we setup a StackOverflow-like Q&A site specifically dedicated to SoapBox Core questions:ask.soapboxcore.com.
We moved all the content from the wiki over to this new site, so it should be your one-stop-shop for all things SoapBox Core.
I’ve just pushed the latest version of SoapBox Core (2010.05.24) and the Pin Ball Demo to the SVN repository. You can download them from the downloads page. This release has some new features and improvements to existing functionality:
- Added ReverseBooleanToVisibilityConverter to the SoapBox.Utilities assembly (so you can make something visible when a property is false).
- Added a ProgressBar control to the Status Bar controls! (I admit that should have been there from the start.) When you inherit from AbstractStatusBarProgressBar, remember to set the Minimum, Maximum, and Value properties appropriately. You’ll probably want to play with the Width property too.
- Documents and Pads now keep the tab text in sync with the Title/Name property of the IPad or IDocument ViewModel.
- Buttons, buttons, buttons: If you want to create a row of buttons, for instance, across the bottom of your View, then create a property on your ViewModel called Buttons that returns an IEnumerable<IButton>. Then populate that collection with objects that inherit from AbstractButton. Put an ItemsControl in your View that binds its ItemsSource property to the Buttons property, and voila… MVVM buttons anywhere.
- To support this new button functionality, IButton (and AbstractButton) now includes IsCancel and IsDefault properties, along with Margin and Padding properties so you can get them to look the way you want.
I’ve finished updating the SoapBox Core Documentation Wiki for version 2010.03.17. Sorry that took so long. One of the most interesting new features is the ability to have extensible context menus using the Model-View-ViewModel pattern, meaning the IMenuItem object can get a reference to the ViewModel that opened the context menu.
I’ve just pushed the latest version of SoapBox Core (2010.03.17) and the Pin Ball Demo to the SVN repository. You can download them from the downloads page. This release has some new features and improvements to existing functionality:
- Moved NotifyPropertyChangedHelper into a new Assembly: SoapBox.Utilities
- Added SoapBox.Core.Messaging (an implementation of the new IMessagingService interface)
- Added SoapBox.Core.FileDialog (an implementation of the new IFileDialogService interface) which provides ViewModels for Open and Save dialog boxes
- Uses IPartImportsSatisfiedNotification instead of ImportingConstructor, which is a better way to use MEF
- IDocument and AbstractDocument are now document factories. For instance, you can define a text editor document, and it can create new instances of itself every time the user opens a document. The default implementation is to return itself, but that can be overridden. (Thanks to ipeksinan over at the CodeProject Article about SoapBox Core for pointing out the deficiency.)
- Significant changes to LayoutManager (and ILayoutManager):
- LayoutManager now doesn’t save to its own files or auto-restore when you launch, it just gives you a blob on SaveLayout which you can pass back to RestoreLayout. This works much better as you can save the layout in your own user file, and restore it when they open that file, project or solution. Note that the blob is standard base64 encoded, plus a couple of period characters (.) so it’s easy to stuff into other containers, like XML documents.
- Added HidePad(…)
- Added HideAllPads()
- Added CloseDocument(…)
- Added CloseAllDocuments()
- IMenuItem/AbstractMenuItem now supports context menus. I’ll have to post some code on the documentation wiki to explain how it works.
- Added a ShutdownCommands extension point to SoapBox.Core.Host
- Added an Extensions namespace to SoapBox.Core. This is where all the individual extensions within SoapBox Core are defined (like the default menu items, etc.) so they’re now strongly typed instead of being hard coded strings. So if you wanted to insert a menu item before File, you could reference it as SoapBox.Core.Extensions.Workbench.MainMenu.File and use that in your InsertRelativeToID property. I suggest setting up an Extensions namespace the same way in your own application.
I’ve just posted an article over on CodeProject that gives a good introduction to SoapBox Core and how to use it to write an extensible WPF application with the Model-View-ViewModel pattern.
I have modified the SoapBox Core Pin Ball Demo article on CodeProject based on SoapBox Core 2009.11.11. They are minor improvements, but it sets us up for more maintainability in the future.
- All contract names use hierarchical string constants now instead of hard coded strings. Makes finding extension points a lot easier, not to mention finding things that have extended certain extension points.
- Documents and Pads are now Lazy-imported, and only instantiated if necessary.
- Made changes to allow recomposition, in preparation for a planned add-in manager that will add extensions “on the fly”.
I will update the CodeProject article within the next few days to reflect the new version.