Nachdem immer weniger Browser unverschlüsselte Websites akzeptieren, habe ich nun diesen Blog auf https und damit auf eine verschlüsselte Verbindung umgestellt.
Hierzu hilft die folgende Anleitung, da Let’s Encrypt zwar offene Protokolle, aber keinen Windows Server unterstützt.
Die Umstellung hat grob 10 Minuten gedauert. Offen ist noch meine Nextcloud Instanz… Diese folgt in den nächsten Tagen.
Das Modul für URL Rewrite muss mich sich über den Web Platform Installer nachinstallieren:
Just uploaded one WPF custom control: The resizeable splitter…
What does it do?
- It divides a control into two parts separated by a splitter
- The splitter is draggable and the controls within are resized according position of the splitter
- The splitter can be horizontal (Top/Down separation) or vertical (Left/Right separation)
- The splitter can have a color… Yeahaa….
The XAML at the container looks like the following:
The result looks like the window:
Where can I get the source code?
As always… GitHub with MIT License.
WPF has the annoying property, that the width of the combobox is not related to the largest element in the view:
Thanks to a blog post, which I cannot find anymore, you can the Popup child item of the combobox can be queried to figure out the width of the element:
Source code can be found on Github: ComboBoxEx.cs
and corresponding Commit: Github Commit
Since I’m using OwnCloud instead of OneDrive or Google Drive for my private photo storage, I’m also obliged to keep care of updates…
You may choose:
- Trust yourself and update owncloud and hope that you can make it
- Trust Microsoft/Google that they will handle it and will not give away your data voluntarily or unvoluntarily via security holes.
I made myself trusting myself… nevertheless, I believe the risk of making a fault and losing the data is higher as using OneDrive or other cloud-based services…
Back to the original topic:
- The Owncloud Client notified my that an update is available.
- Owncloud Server does not support automatic updates like WordPress…. So reading through the manual.
- Connect to server
- Switch on maintenance mode
- Move all to backup directory
- Download and extract latest version
- Copy config/config.php to new directory
- Copy data/ to new directory
- Run Update Script
- Leave maintenance mode
In total about 15 minutes which is ‚waste of time‘ compared to the scenario OneDrive.
A minor new update for SlideMeister is now published. You can create animations and export them as .png files for fast reuse in Powerpoints.
- Copy to Clipboard via right-click or Ribbon Butten
- Improved layout for sequences. Number of tab controls is reduced
- Minor bugfixing and minor refactoring.
Just some screenshots… After losing two of my wisdom teeth, I have some time to work on DatenMeister. I hope to have a version ready within this year which can be used in a productive meaning.
GUI Development is currently very rough…
1) The Workspaces
2) The Extents
3) The List View
4) The DetailView
SlideMeister 1.2 is now released… Source Code available under GitHub (by the way: Another US-driven service, I would like to get rid off):
The Download of the application is given under:
What has changed?
- Images are now created by factory methods instead being directly correlated in the main view
- A step for transition sequence can now set several transition sets
- Initialization of a transition is now working correctly
- Filenames for exports include an ordinal number (ofor better sorting)
- Minor layout improvements
Finally, SlideMeister is released on GitHub:
Until further notification, the application is released under GPL v3 licence, which means that you have to open up your source code to whomever you provide a compiled version of the application or a derivative.
Just as a small training for implementing specifications, I implemented the Base64 part of the RFC 4648 completely.
By importing the complete PDF into Microsoft Word and marking requirement-relevant information with background color, I created a unit tests for the necessary chapters.
Each unit test is green and code coverage for unit tests is about 100%.
Why did I create such a library, even though Base64 is directly supported by .Net Standard 1.0 and therefore each .Net implementation like .Net Framework or .Net Core?
As mentioned: I wanted to implement the RFC as strict as possible, which is not given by the .Net Framework (some exception handling deviates) and in addition it was given as a training how to implement RFC requirement documents and somehow get a tracing between the specification and implementation. More work will follow!
And… because I can!
The complete source code is available at GitHub: