Various utility classes/assemblies
Important: Unless noted, NONE of these are guaranteed to be stable. Functions can be change greatly.
Helper/Wrapper class for Win32 dialog windows.
More intuitive Dialogs Factory and some utility functions such as for creating Extension strings.
Stable
Probably should integrate this into a single generic Utils library.
The project only contains 1 class: NonClosableWindow which basically a window that has the X button disabled.
To close the window, CanClose() must be called first.
Stable
A WPF UserControl and framework.
The control has 2 modes:
Shows some text (not that much different from a textbox)
DialogControlOptions.SetTextBoxMessageOptions
Easily create user input windows such as for options or forms.
This class library is subject to major changes as still tweaking the framework. There's a bit of redundancy in setting the values
-
TextBox with data type validation
-
CheckBox
-
DateTime text input
-
ComboBox
-
Path/File Selector
-
Create own components by extending ValueComponent abstract class (not IValueComponent, probably should be removed)
DialogControlOptions.SetDataInputOptions(fields);
Where fields is a List<ValueComponent>:
var fields = new List<ValueComponent>() {
new TextBoxComponent(
new ComponentArgs()
{
DisplayName="Fund Name",
FieldName=FldFundName,
InitialData= IsEdit? lastFund.FundName : null
}),
new TextBoxComponent(
new ComponentArgs()
{
DisplayName="Fund Page (URL)",
FieldName=FldURL,
InitialData= IsEdit? lastFund.URL : null
}),
...
Factory class for creating common MessageBoxes
MessageBox Types
- Show Info
- Show Error Message
- Confirm Action
Stable
Helper class for learning and understanding MVVM from scratch. Currently, all WPF projects use this but eventually would probably move them to an existing framework like PRISM
Likely Stable
Untested: Haven't found a use for it yet
The idea was to replace multi-level Dictionaries (i.e Dictionary<string,Dictionary<string,Dictionary<string, object>>>) with a friendly single object that also abstracts the data retrieval/storage and branch creation logic.
Contains one ResourceDictionary (at this point) that has sensible configurations for many common elements such as TextBox, Button, RadioButton, etc.
The goal is to not have to keep creating similar Setters for each individual project.
The Dictionary also contains the ToggleButton (basically a RadioButton that looks like a Button; the original implementation though is not mine.)
By its nature, changes may be possible but not frequent
Wraps the SQLite Library. Probably not that useful but does provide a more familiar ADO-like class to query with.
Stable
WebClient that allows setting a timeout value.
Stable