In ShellView.xaml the 'MARKPAD' title text block is doubled up which causes it to appear aliased. I will fix this terrible problem.

I get a dialog with this message:

Title -> MarkPad.exe - Fatal error
Content -> CLR error:80004005. The program will now terminate.

And nothing happens after close the dialog.

There are a few places... disk I/O (IsoStorage stuff), web publish... all need to go onto a worker thread.

The default MarkPad output directory ($(MSBuildProjectDirectory)\bin\Release) has the following files

Themes
MarkPad.exe
MarkPad.exe.config
MarkPad.pdb

However, if I run the build from the command line and override the OutputPath or OutDir parameters (from browsing some of the custom MSBuild tasks, it seems one or both is necessary)

cmd> msbuild Markpad.sln /p:configuration=Release /p:OutputPath=$pwd\bin\Release\ /p:OutDir=$pwd\bin\Release\

I get the all of the dependent libraries, configs, and pdbs (autofac, mahapps, awesomium, etc). This is making it hard to develop cmd line scripts for build/package/publish tasks :)

Any YAML front matter in a document should not be shown in the final render of the page.

Also, if we could include out own settings in the front matter (document type, metaweblog publish location, etc) that could be useful. Nice to have here would be some sort of YAML parser.

The document should have a context menu so you can set various document level settings, like theme, author, title, etc.

This should then manipulate the document header to include the changes.

Whenever the user clicks "New", and a new document is opened, the cursor should focus into that new document so the user can just start typing their new document.

The awesomium scrollbar has some odd behaviour that means sometimes it gets in a state where it jumps around seemingly at random.

I'm logging this issue here just so it can be tracked, but the issue isn't in the DownmarkerWPF codebase.

Mentioned by @distantcam on the jabbr chat that the current build has some UX problems.

"ok, first bug. I can't move the window. :P"
"hmmm, second "feature", can't close the window.10:56:48 AM"

string[] filenames - not used anywhere. I think that there is a misprint and should be filenames.Length> 0. I am right?

using (IsolatedStorageFile isoStore = IsolatedStorageFile.GetStore(scope, null, null))
 {
                string[] filenames = isoStore.GetFileNames(Filename);
                if (Filename.Length > 0)
                {
                    LoadStorage(isoStore);
                }
}

When a user clicks "New" and they already have a post open that has a massive title, the "New Document" tab appears off screen.

Expected Outcome

Clicking the New button;

• Creates a new document
• Creates a new tab
• Scrolls the navigation bar to bring the new tab into view

The default themes should be embedded into the app, and on startup they should be dumped into the directory that Markpad is in.

Some things to keep in mind:

• If the file already exists, don't overwrite it. That way, the user can modify the theme themselves.
• If the file fails to save, possibly due to permissions, don't crash, or tell the user. This is a fail silently and try next startup scenario.

Hi folks,

The preview build I downloaded (https://github.com/downloads/Code52/DownmarkerWPF/Markpad.1.0rc.zip) doesn't run on XP.

I have downloaded and installed .NET 4.0 so it's not that.

A typical "Send error report" dialog is thrown and my event log contains this error:

Application: MarkPad.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Reflection.TargetInvocationException
Stack:
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(System.String[])
at MarkPad.SingleInstanceManager.Main(System.String[])

Regards,
Phil

When I run the msbuild command line

cmd> msbuild Markpad.sln

I get a couple of warnings about supported configurations

Build started 1/31/2012 4:14:00 PM.
Project "D:\Users\anthony.mastrean\Dropbox\Projects\DownmarkerWPF\MarkPad.sln" on node 1 (default targets).
ValidateSolutionConfiguration:
  Building solution configuration "Debug|x86".
ValidateProjects:
  The project "MarkPad.XAML" is not selected for building in solution configuration "Debug|x86".
  The project "MarkPad.Services" is not selected for building in solution configuration "Debug|x86".

Is that a problem? I'm able to produce Debug and Release builds that appear to run fine.

While I'm not sure what the .NET support for Markdown Extra/MultiMarkdown/markdown supersets, having optional support for markdown rendering engines like Maruku.

There's a ~3-5 second pause when you open a document or create a new document for the first time. I suspect its a recent change when loading Awesomium into the app domain.

Investigating

We should make the settings portable by saving them in the same directory as the app itself.

Not sure if it's a feature of AvalonEditor? Hope so, given that it's available in WPF TextBox natively. Hope it's just a switch we need to flick...

The "AwesomiumProcess" browser-control loaded when creating a new document doesn't unload when the document is closed.
I'll upload a fix for this.

In the spirit of DRY, the Caliburn.Micro.Autofac package on Nuget already provides the autofac wiring for Caliburn.Micro, including the auto-registration of event handlers. It should be used instead of writing or writing new code to do the same.

I have made this change on my fork of the code. The URL for the commit is dbuksbaum@20b4482

To detect which template(s) to use in a preview mode, it should parse the YAML front matter which states which layout file should be used.

This will need to be recursive to work 'up the tree', for where there is post layout, then a master layout, etc.

To provide a "Windows Live Writer" like experience, DownmarkerWPF should implement the Metaweblog API support so it can post to markdown based blog systems like FunnelWeb.

MarkPad does not have feature which allow to open a file by drag-and-drop into MarkPad.

I am willing to implement this feature, however I will appreciate any advice that would help me resolving this problem, AKA where is good spot to place code.

Thanks
-- Soltys

Windows 7 supports Jumplists of recent documents and other commands.

We should track recent documents and display them in the jump list.

Need to replace the standard webbrowser control with Awesomium.

Firstly, great work. Secondly, I cloned this, fired up 2010, but couldn't copy the results, ironically, due to the clipboard error.

Steps to reproduce:

1. Run rc1.
2. New document
3. Write something like:

title

4. Right click in right (awesonium, i think) pane
5. Select all.
6. Right click again, 'Copy HTML', raise COM clipboard exception.

Currently if you make the windows minimum width to small (smaller than the design width) the main menu items are hidden.

It should either have a minimum program width or implement a WrapPanel in place of the StackPanel for the Main Menu items.

Ctrl+K because that's the same as Office
will need some UI to enter the link text and the URL. A popup, I guess...

In the spirit of DRY, the Caliburn.Micro.Logging package on Nuget already provides logging for NLog (and Log4net). It should be used instead of writing a new logging adapter.

I have made this change on my fork of the code. The URL for the commit is dbuksbaum@ce34aaf

The app should have a way of autoupdating itself.

Download/cache themes for services that use Metaweblog API

Spanish dictionary add to the project

Through a number of life tragedies I have standardized on *.mkd for my markdown files. You have not, thus rendering this project useless. Never fear! I shall refactor the code and make this crucial change.

Publish works for new posts, but update duplicates causing a funnelweb ysod..

Can you introduce support for Alex Gorbatchev's SyntaxHighlighter (https://github.com/alexgorbatchev/SyntaxHighlighter) in the preview window?

A floating toolbar (ala Office 2007+ style) that allows you to bold/italic/header/list/etc the selection would help with feature discoverability.

Selecting a link to an external site opens the site within markpad.

Links should probably open outside of markpad.

A preview pane thats backed by a webbrowser rendering the markdown.

This could use Awesomium or using the WPF/WinForms webbrowser control (which is just IE). Or both could be used, with a switch to compare in two browsers at once.

The Preview pane should detect if the page has been written within a Jekyll/Octopress application, and render the DOM around the post correctly.

How to detect if the markdown file is within a Jekyll/Octopress application:

• the _config.yml file is found at the current folder or the folder above - do we really need to support further recursion?

When this is successful:

• ... from the folder containing the _config.yml
• look inside the _layouts folder for all *.html files - these are your layout templates
• these will need to be parsed (with potentially other templates involved) to create the full page.
• find the CSS stylesheets referenced on the page and load those files into memory
• apply those styles to the live preview

What can we get OOTB by using MahApps.Metro?

"New Jekyll Markdown" file should insert blank (?) YAML front matter

Other than 'blank markdown file', are there other templates that need to be considered?

So far my experiments have shown that I cannot load MarkPad under my corporate account but I can under my regular account. I suspect this has to do with my Roaming Profile and I'm happy to explorer further. Details as recorded in the Event Log are as follows:

Application: MarkPad.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Autofac.Core.DependencyResolutionException
Stack:
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(System.String[])
at MarkPad.SingleInstanceManager.Main(System.String[])

1. If I drag window to the top in my Win7, window maximizes, but icon Maximize/Normal doesn't change.
2. When I try to drag the window from maximize state (Windows 7 feature) I feel that I came back to WinXP, is is not possible. But If I drag the window from normal state to the left or right side, it is docked and undocked perfectly by draging.

Initially, the most of sources have LF line endings instead CRLF.

This causes problems at work. Already there are a lot of commits where it is not clear what exactly has changed in the file.
VS don't like LF ending and always try convert to CRLF.
For example, to avoid a complete change in the file at my first Pull Request I edited the csproj file in Notepad manually.

To fix this issue I suggest process sources with something like this:
https://github.com/ayende/RaccoonBlog/blob/master/normalize-crlf.ps1
(add xaml support) and recommit with CRLF line ending in sources.