...and so dark in here.

I love the PostXING tool and the ability to integrate the playing music. Feature wise they are all about the same though. So it will interesting to see the evolution of the tool. One positive out of the project is that I learned a lot about Subversion and how to work with it. Share this post: Email it! | bookmark it! | digg it! | reddit! [Via It's my life... And I live it...] Well, this post has been a long time coming. What about...

http://postxing.net/gemini/issue/ViewIssue.aspx?id=32 I'm about to start cracking on this issue, but I'd love to get a little feedback on it before I put it into code. If either of you have an extra minute, shoot to the url above and leave a comment. I normally don't solicit feedback like this, but I kind of feel like I'm missing something. Although I could just be thinking about it too much. Either way, help a code munkey out if ya can :) [ Currently Playing : This Could Be Love - Alkaline Trio - Good Mourning (3:47) ]

This looks interesting. I thought Mr. "Just finished my last chapter of Beginning AJAX" would have for sure created this as an asp.net control...guess I should have read closer the first time ;) Could be useful in PostXING, ifn we ever put some real security innit. Since there has been so much interest in the SecurePasswordTextBox control (see my previous post http://weblogs.asp.net/pglavich/archive/2006/02/26/439077.aspx and http://weblogs.asp.net/pglavich/archive/2006/03/12/440052.aspx ), I thought I would take the time to iron out the bugs. When I first released it, I performed minimal testing (i.e. about 15 minutes worth) and just...

For the adventurous among you, we've decided to release beta 1 of PostXING available for download at ProjectDistributor! There are a few known issues, but as far as I know there aren't any showstopper bugs. I've been running the development build for quite some time now, and for PostXING v1.1 users, I think this release is a big step up in terms of usability. Since the only working provider at this time is the MetaBlogProvider, the functionality remains basically the same, i.e. you can manage a MetaWeblog enabled weblog using PostXING from your desktop. If you find any issues, bugs, or you just...

This is the end result after setting up SubText and importing my old blog (now moved to here). I had created a blogML exporter for cs11 and ran into some initial problems because the version of BlogML I had used was a smidge older (v0.9) and therefore had a different schema. Kinda makes me wish there were a way to clear out all the content and start over like subv2 allows me to. So why didn't I go with subv2? (Sorry, Darren) The admin interface and WebParts' silly requirement of IE. I basically live in FireFox and although it's been quite some time since I've...

Well, it turns out that PostXING's mystery plugin author is none other than Taras Naumtsev, and Taras is on fire! Check out the new MetaPinger plugin: MetaPinger is a PostXING plugin that notifies a number of services that keep track of weblogs and publish them. By pinging, you let the services know that your blog has been updated , they crawl your blog, publishing your site contents, thus increasing your blog's popularity. SetupExtract the ZIP archive into the "plugins" subdirectory of PostXING's install directory ConfigurationYou will...

Holy Schnikeys! Someone has actually built a plugin for PostXING! Ladies and gentlemen, Allow me to introduce the TechnoratiTagger plugin for PostXING! Unfortunately, I'm not 100% sure who wrote it (well, it's not obvious from the site). The good news is...it works! :) It even works with the spankin new, begging to be released v2 beta I have on my machine, and it works well! Technorati Tags:  PostXING  Technorati Tags  Plugins 

I've been wanting to setup subversion for PostXING for a while so I can have more control over who has commit access and various adminy tasks that are only available thru emailing the already busy staff of sourcegear when hosting code on vaultpub. Thankfully, I'm not the only person who has had this idea. To that end, this blog post was instrumental in outlining the steps to take to get subversion up and running on a windows box. The only issue that I had which was rather annoying was I kept getting an error stating that svn was "unable to open an ra_local session...

RssBandit has been a big inspiration for some of the specific features of PostXING. As a matter of fact, where possible I've used code from RssBandit directly. At least half of proxy support, most of the plugin loading logic, and most recently (like you don't have it unless you monitor the branches for postxing) a little-used, very useful interface: IMessageFilter. IMessageFilter is only implemented by the splitter control in the framework (according to reflector) but was extremely helpful in the quest to better handle the keyboard. There is only one method defined on the interface://CF: thanks, rssbandit :) public bool PreFilterMessage(ref Message...

Heh, oops. This is what happens when the tool that you are building is the same tool you are using to make tech notes to yourself.* Really, there should be a bugtracker in place so that I can have a central organized spot to have bug reports, feedback, etc. Anyone have any suggestions? I've used (and liked) gemini, but delusions of granduer aside the 10 user limit gives me pause. I want PostXING to remain free, so any supporting items like this need to be free as well. *yes, most of my notes do look like this.

I'd like to apologize if any users of PostXING have to go thru proxies...I've been bugchasing this evening and it occurred to me that specifying a proxy for a new blog is kind of...well, weird. First, it's a wizard-style dialog, so you expect the next/back buttons to work like it would in say an installer (well, I would anyways). Instead, you've got to specify at least a host, "page", and port, click on a special linkbutton (not next), click back to specify now the rest of the properties (including re-typing what you've already typed) and then you can go to select which...

And now I can post there with PostXING (v2). Dare has put up a couple of tutorials on how to setup Metablog support for w.bloggar and BlogJet. Since I "borrowed" ideas from both of these fine applications, the setup for w.bloggar is nearly identical to what you need to do in PostXING v2. Sorry for those v1 folks, I don't think it'll work in that version. Maybe I can put out a patch so that v1 will work too. I'd also like to thank Dare for being so helpful in the beta stage. He personally replied to my questions and gave insight on a...

Peter, bro, you must be inspirin' or something. I hope I didn't miss anything (it was one of those "it can't be that easy©" deals), but I'll just let the screenshot do the talking: [ Currently Playing : Precious - Depeche Mode ]

Peter gives me some awesome feedback: Hey man. Glad to know you're listening. I really think that PostXING could rock with a little more TLC. You're doing great. A few comments on your comments: 1. I don't think you understand my request. Assume for a second that I know that I want to open post ID 117, I should be able to "Open 117" instead of "open, browse, wait, wait, 117, OK". I know this can be done with MWAPI 'cause I wrote one. metaWeblog.getPost takes postid, username...

..the idea for PostXING began. Wow. I still hack it every now and then, but I don't devote nearly as much time as I used to. I'm hoping that the new Settings goop in v2 will allow me to improve the options story: the last incomplete feature before PostXING v2!

NEW: "PostXING" in about page now links to postxing.net. NEW: FTP Settings page now is labeled as such. This was confusing in the new user wizard. FIX: Plugin ToolStripButtons now actually do something. These are a couple of the things that I've fixed this morning based on some really great feedback from a few really brave souls. The most work it looks like is still going to be the options story. I knew this was going to be the case when I announced the alpha, so thanks everyone for your input!

In an attempt to work on steps 7 and 8 in Grant Holliday's Blog, I've started a community server site for PostXING. It's lite on content at the moment, (and also may not work everywhere for the next couple of days thanks to DNS) but hopefully this will let me address number 7 via the forums and number 8 via the gallery. 6 is done - actually using the default browser for the view blog function. I think I'm doing pretty well for number 5, and number 4 should probably be implemented in a couple of more places. Number 1 is a big duh...

And I know it. I haven't updated the binaries on ProjectDistributor for a long time because I've been taking my time writing v2. Thing is, it's starting to catch up to me. PostXING v1 is far from polished. It works well enough for my needs and I made it available for download in the hopes that it would be useful to someone else, nothing more. But I do want to make it a better application, and that's where you, dear reader, can help me out a little bit. I've decided to release an early alpha of PostXING v2 in the hopes...

Since announcing that we've started the beta of our implementation of the MetaWeblog API for MSN Spaces, I've received a bunch of positive responses from a couple of blogging tool developers. So far it looks like there'll be at least six blogging tools users will be able to use to manage the blog on their space after we launch the API. [Via Dare Obasanjo aka Carnage4Life] Add at least one more - PostXING v2 will work with MSN Spaces via the MetaWeblog API. I don't think that it will work...

Ah! It's been a while since I've gotten some good PostXING feedback. Guess the current version isn't very keyboard-friendly. I'm probably not going to upgrade the v1 code in v1 of .net, but I've been working for the past couple of weeks on getting PostXING to v2 under .net v2, so none of these requests are out of the question. As a matter of fact, I welcome all criticism in the hopes of making PostXING a product that works really well for more than just myself. Anyways, Peter has some good feedback for PostXING in general, my responses follow his post: ...

One or more errors encountered while loading the designer. The errors are listed below. Some errors can be fixed by rebuilding your project, while others may require code changes. The designer loader did not provide a root component but has not indicated why. Hide     at System.ComponentModel.Design.DesignSurface.get_View()at Microsoft.VisualStudio.Shell.Design.WindowPaneProviderService.CreateWindowPane(DesignSurface surface)at Microsoft.VisualStudio.Design.Serialization.CodeDom.DeferrableWindowPaneProviderService.CreateWindowPane(DesignSurface surface)at Microsoft.VisualStudio.Design.VSDesignSurface.Microsoft.VisualStudio.Designer.Interfaces.IVSMDDesigner.get_View()  It looks like there are a lot of people that got this error when going from beta2 -> RC1, but this was on the RTM version. The thing that's tricky is that now the designer is so nice for us, it adds default values to public properties. Well, since the code...

I'm using xml-rpc.net as the library that supports xml-rpc for the MetaWeblog api in PostXING. I recently ran into a service endpoint that included a Byte Order Mark in the payload of the response. Something I haven't run into yet basically because the few blog engines that I have tested px with have not included this. It turns out that the XmlDocument.Load method that accepts a stream doesn't take this into account (or something:). So this is what I did to workaround the problem: basically, if the first character is not <, the second must be otherwise the content is invalid anyways.//...the DeserializeResponse method...

Ah, the joys of writing open source software I had been working hard on v2 of PostXING, but somehow development has stagnated on my end quite a bit. I brought it about 90% of the way towards the direction I was hoping to go. I even got an offer of help from a fellow Houstonian, but it seems I've dropped the ball. My bad. Fortunately, as I said I've completed most of the grunt work, now it's just a matter of gluing everything together and creating a different provider than the Metablog API. It was still evolving when I last hacked...

This has probably been done a hundred times already, but I couldn't find one in the first few pages of google results, so I wrote my own in ~40 lines of C#:using System;using System.ComponentModel;using System.Drawing;using System.Drawing.Drawing2D;using System.Windows.Forms;namespace PostXING.Controls{ /// <summary> /// GradientPanel is just like a regular panel except it optionally /// shows a gradient. /// </summary> [ToolboxBitmap(typeof(Panel))] public class GradientPanel : Panel { /// <summary> /// Property GradientColor (Color) /// </summary> private Color _gradientColor; public Color GradientColor { get { return this._gradientColor;} set { this._gradientColor = value;} } /// <summary> /// Property Rotation (float) /// </summary> private float _rotation; public float Rotation { get { return this._rotation;} set { this._rotation = value;} } protected override void OnPaint(PaintEventArgs e) { ...

Earlier I said: call them "labels" or "tags" but give me a way to categorize my thoughts. Please. Thanks, Atom 1.0  [ Currently Playing : A Message - Coldplay - X&Y (04:45) ]

Darren's looking for ideas on how to migrate data from one blog engine to the next. This has been discussed before a lot, I'm sure, but it's not a bad conversation to have. So what's the answer? Sorry, I don't have that. I know that it would have been nice when developing PostXING to have an api that gives you more control or gives better querying ability, and I also know that none of the APIs that Darren talks about are it. For all of the metablog api's shortcomings, I find it at least decent enough to not have made a post...

You're Welcome!   [ Currently Playing : Suite-Pee - System of a Down - System of a Down (2:32) ]

Was just released. In the newsletter, it said that you can use a DocumentContainer (tabs) outside of a SandDockManager - simple tabbing with the same interface that is all over PostXING. Sounds promising! Well, the "document" tabs only render at the top, and I need tabs at the bottom to keep the interface at least a little similar to what it always has been. Plus, with the interface that I have in PostXING, I just like the way the tabs look at the bottom better. So I have two choices: keep the interface that is already in place (using the older...

This was the error that was biting me on PostXING v2 for almost a week (I usually only get insomnia hours to debug. That can be frustrating.) The first thing that I noticed was that the wonderful interfaces that I was using would end up null after my first visit to a particular configuration page. It's something about the way that a "Page" is saved and loaded - it requires ViewState! Forreal! I'd gotten so used to having state within my smart clients that I had almost forgot about reconstructing state. Now that I had that taken care of, I was...

...to having something that actually works :) Do you think I'm going a little nuts with the logo?

I saw that Jeff got things up and running with PostXING (sorry again about the whole BlogInfo[0] thing) when I looked at the url. What's this? dasBlog? I never knew that dasBlog supported the Metablog API, although I did see the methods exposed from its blogger.aspx page. I thought they were just place holders, but I fired up my local copy of dasBlog and, sure enough, PostXING can post to it. WordPress also supports the metablog API - hopefully subText will retain that feature of dotText so there will be at least a few blogging engines (I know of) that you...

I feel like I'm going nuts with interfaces in the next version of PostXING. Interfaces are a language feature that is really powerful - you don't really start to appreciate it until you are faced with situations that would otherwise be impossible to deal with. PostXING already uses interfaces to load plugins like the NetSpellPlugin for spell checking. So I thought hey, go with what you know for this plugin/provider idea that I've had stewing in my head for a while. I've already included MikeDub's awesome IUI library (modified with - you guessed it, interfaces!) so I figured I might as well...

Here is some of the common ground I can see between the metaweblog api and CS::Blogs BlogService asmx. Blog/Authentication: UserName Password BlogID/BlogName Post/Entry: DateCreated/Date Description/Body Title string[] Categories (nice!) PostID Non-Conformities (for Posts): Metablog API Enclosure (although this is not used by CS::Blogs or .Text) link permalink Source (name and url, was supported by .Text, not so sure about CS::Blogs) userid BlogService.asmx Excerpt Name...

Yex sez:  Nice. So where's the Categories, Post, Post and Publish and Crosspost buttons at? Where's the post editing toolbar? When can we get our grubby little hands on it? Since it appears you've decided to go with the whole sidebar idea, why not use that to list the cateogories checkboxes? Seems logical to me anyway. Yex Good questions! I've actually created a sidebar for the categories, and am currently studying a couple of the API's I want to support right away - it looks like I...

I didn't go too too far, I think. It's definitely a step in the right direction, tho: I don't know why I've opted to start at the top and go down...probably because I'm just procrastinating on getting to the meat & potatoes (!) problems. I also had to go into a different program to upload the file above...I'll be checking that as well.

I've been working a little on my plugin/provider idea on PostXING. Currently, I have it building, but I've had to disable some of the post-build commands because although it builds, it doesn't do anything currently and I don't want it to overwrite the working copy that I have on my computer. Interesting aside: I didn't actually remove the commands, but since they are all written to a .bat file, you can use normal batch commands - like rem - to effectively disable the commands. An example that is currently disabled in the branch .csproj file but not in the main trunk:rem...

Not what I know now, but what I'm learning now. I recently picked up a copy of the src to FlexWikiPad. I just wanted to see how things were wired together in there: I only have a very old installation of FlexWiki sitting around that still looks like crap in FireFox. To his credit, Craig has done an awesome job of making FlexWikiPad very testable - something I didn't think was all that easy to do in winforms. Apparently, his dialogs are very humble. He's using a pretty strict Model View Presenter (or controller, whatever) pattern throughout the application. I thought...

I.e. Both of you...I've changed the repository structure of PostXING on vaultpub to better facilitate branching. These crazy new ideas I've been having are so different from the current architecture of PostXING that I have to branch it just in case someone comes to me with a nasty bug they found that I just overlooked (this has happened a few times already, although not for a while). I don't like having broken software with my name on it out in the wild. Anyways, I thought I would keep tabs on my progress for this on my blog. I feel like there is...

Who else out there likes a dock better than the standard windows taskbar? I have been using StarDock's ObjectDock for a few weeks now and I think I'm sold. I have hidden my taskbar and I only run a single visible dock at the bottom center of my screen. <snip/> [Via Wes' Puzzling Blog] Big smile on my face from this one - I recognize the plainer looking icon in the picture above. I knew that Wes was running PostXING (heck, his CodeHTMLer is a big part of it) but it's really...

I've added a small usability feature based on some recent feedback. Now, from the Tools -> Options dialog, you can optionally set whether you would like to automatically create a new post when you hit Post or Post & Publish. I also made some minor UI consistency changes, and removed a superfluous message that showed up in the options dialog in the last release (oops :) So, go grab the new PostXING. Enjoy.

...but I've decided based on some recent feedback to release the latest version of PostXING! This version of PostXING will optionally support Http Proxies if you need that functionality - I had been waiting on some feedback from a couple of folks who could real-world test this functionality before releasing it to the wild. Thanks Chris, Keith, and Laurent for helping me track down some of the issues that this release addresses. You're still reading this? Go get it! :) [ Currently Playing : Paranoid Android - Radiohead - OK Computer (6:23) ]

...at a time when people are actually leaving comments. Balls. Josh - I'm checking the vaultpub repository on a clean directory right now, I probably forgot to add all of the files to the repository. Genius, Chris. update: I'm such a jerk. I have this repository set up all bass ackwards. I'll fix it up lickety split. [ Currently Playing : Born of a Broken Man - Rage Against the Machine - The Battle of Los Angeles (4:40) ]

Teirnan asked for a few features for PostXING. I started to write a comment, but it got too long-winded for a comment. You get a post Sir: Can I help you? I think maybe so :) In order: I did this in a very early build of PostXING, but got some feedback that asked to be able to immediately edit the post that was just, erm, posted - in case of typos or whatever. I guess I could make it configurable, that shouldn't be too hard. Since you are literally the first person to...

I recently added Tabbing functionality for indenting/outdenting (hey, it's a trident term :) in my dogfood version of PostXING. Quoting has just become 100 times easier for me. I prefer to use the keyboard when posting/changing text attributes when possible, and this whole no tabbing business finally got me a little fed up. Wanna know the funny part? It ended up being about 8 lines of code, give or take for whitespace: 1 protected override bool ProcessCmdKey(ref Message msg, Keys keyData) { 2 if(keyData == Keys.Tab){ 3 this._designEditor.TextFormatting.Indent(); 4 }else if(keyData == (Keys.Tab |...

With the help of Laurent Kempé, I've traced down a bug in the PostXING FTP library (or rather my handling of it) and ended up changing the underlying FTP library code to the open source edtFTPnet library. This is a more complete library than the sample socket code that I was using before, and since it's LGPL licensed, I can link it into my code without affecting the license that PostXING is released under (which is zlib/libpng). I also plan to add proxy support soon - the only hold up right now is that I like to at least dry run...

I've gone ahead and uploaded a new build of PostXING. I extended the plugin architecture a little bit to allow for posting to non-.Text blog engines using IBlogExtension plugins, of which there are a few out there already. Everything else is pretty much the same, but I had to give out some credit for the plugin architecture - I didn't come up with that stuff on my own and I'm all about giving credit where credit is due. To test this IBlogExtension plugin architecture (really all you have to do is drop the IBlogExtension dll/exe into PostXING's plugins subdirectory) I created...

I can now use the great IBlogExtension plugins for NewsGator to post with PostXING. (with my built about 10 minutes ago dogfood version, that is :) Thanks for that idea, Joel. The only problem with this method is that it's "push only" - I can only publish with these plugins. No history management, and strictly speaking, not manageable on the same level as using the Metablog API. So, I can't set an account for IBlogExtension blogs - no navigating to the site without manually opening a browser, basically no integration with the current UI. Categories seem to be up to the plugin as...

I've uploaded a new release of PostXING to ProjectDistributor. This release adds the ability to Load or Save a post as a .htm file, as well as managing your blog (Categories, Post, Post & Publish, Cross-Post, Delete, and plugins) from the Preview page. How ya like that, Bob? :) I went ahead and included a couple of bugfixes that slipped into this release, so the latest version of PostXING is now uploaded and reflected on ProjectDistributor. Sorry I let a couple of bugs slip in there. Thanks for the...

I've uploaded a new release of PostXING to ProjectDistributor. This release adds the ability to Load or Save a post as a .htm file, as well as managing your blog (Categories, Post, Post & Publish, Cross-Post, Delete, and plugins) from the Preview page. How ya like that, Bob? :) [ Currently Playing : God (Interlude) - Andre 3000 - Speakerboxxx/The Love Below (2:19) ]

...for PostXING that I should have added a long time ago. It only took roughly 40 lines of code (including gratuitous whitespace). I'll give you a hint on what it is: There are a couple of other things that I would like to implement before uploading a new release, tho. For example - I don't see a good reason why you shouldn't be able to post/publish/cross post from the preview pane. Also, Joel Ross gave me the spectacular idea of using existing IBlogExtension plugins to make posting to blogs other than .Text or some other Metablog API enabled blog engine not only...

 Couple of feature requests posted by Bob Yexley on 1/7/2005 12:02:04 PM : Hey nice work on the latest version. Spell checking works very nicely. There are a couple of things that I've noticed about the application that I thought would make it nicer that I wanted to mention. Fairly simple I'm pretty sure.First off, especially with all of the different version releases you've had lately, I've wanted to check the "About" box to make sure that the correct new version was running after...

Royo asks: I'm interested to know whether you found my Extensibility application block useful, or if you had to make many changes to it to make it workable. The short answer to this question is: yes and that depends on your definition of 'many'. The EAP was useful to me: without the ideas and articles supporting it, it would have taken me at least twice as long to implement a spell checking plugin for PostXING. That said, there were some hurdles I had to overcome in order to get it working consistently for me. First, let me say that I...

With the latest release of PostXING, a plugin architecture has been added to allow for external extensions such as the new NetSpellPlugin that adds spell checking to PostXING. All that is required to install the plugin is to add the .dll file to the plugins subdirectory of PostXING's install directory, for me that's C:\bin\PostXING\plugins. When you start PostXING, you should see a new button in the toolbar: as well as a couple of entries in the plugins menu under the Tools main menu: I really wish that was all there was to it, but unfortunately there's more that needs to be done. As I've...

Well, I've implemented it. I figured out a way to have a user-defined dictionary location (very simple implementation), but now I'm still facing the dilemma of where do I point to for the dictionaries? Like I said before, the NetSpell component comes with a few dictionaries by default. OpenOffice has a project called lingucomponent that has a more exhaustive listing of dictionaries, but they are not in the same format that NetSpell uses. (I even tried using the en_US dictionary. Needless to say it was useless as it stopped on every word.) However, there is an article for NetSpell about creating a custom...

When I was working on the latest release of the BlogThisUsingPostXINGPlugin, I kept running into file access issues. The whole thing was an excersize in refactoring - well, really, the whole thing WAS a refactor, since the basic functionality already existed, but I was making additions in how things were going to work. First, I changed the XsltStream to return a FileStream or a ManifestResourceStream, based on the existence of a user-specific file: 1 Stream XsltStream 2 { 3 get 4 { 5 string filePath = Path.Combine(ConfigurationPath, this.BlogType.ToString() + ".xslt"); 6 if(File.Exists(filePath)){ 7 //read from...

This new version of the BlogThisUsingPostXINGPlugin handles customizing the transform used to output into a new Post in PostXING. For example, say I want to have the title of the post referenced in the post body. I would start off with the LinkOnly.xslt option: 1 <?xml version="1.0" ?> 2 <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> 3 <xsl:output method="html" /> 4 <xsl:variable name="feed-title" select="/rss/channel/title" /> 5 6 <xsl:template match="/"> 7 <xsl:apply-templates select="//item" /> 8 </xsl:template> 9 10 <xsl:template match="/rss/channel/item"> 11 <html> 12 <title>RE: <xsl:value-of select="title" /></title> 13 <xsl:choose><xsl:when test="link"><a href="{link}"><xsl:value-of select="$feed-title" /></a></xsl:when><xsl:otherwise><xsl:value-of...

So I ended up working out a method to load plugins - it's a hybrid of Royo's Extensibility Application Block and the method used by RssBandit. Now, I do have rudimentary spell checking in my dogfood version of PostXING (again :), but I'm having trouble figuring out how to handle the dictionary files. By default, NetSpell looks for a culture-sensitive .dic(tionary) file from the Application.StartupPath (I think - when trying to launch PostXING from the BlogThisUsingPostXINGPlugin, it complains that it cannot find the file...\bin\RssBandit\en-US.dic) I manually copied the en-US.dic file to PostXING's root folder and it works when launching the program by itself....

So I released a new version of PostXING , adding support for the new IBlogExtension plugin I was talking about the other day. Oh, I released the BlogThisUsingPostXING plugin, too. I think I mentioned that I got the large part of the source code for that one from haacked, but if I didn't, I am now. The source is in no way original by me, I just hacked the solution from his improved plugin for using w.bloggar with RSS Bandit. To use the plugin, the latest version of PostXING is required - it writes out the location of PostXING so everyone...

Bob wants to see some integration of RssBandit and PostXING. This was an idea I had really early on simply because a lot of the features in PostXING were, ahem, borrowed from w.bloggar, and RssBandit already supports a plugin that starts w.bloggar for posting to a weblog. So, why couldn't I do something similar? Well, I thought that it had something to do with implementing IBlogExtension, for which I couldn't find too much documentation. Maybe it's such a simple thing...

I started to make this a reply in Shawn's comments, but decided it was getting too long-winded to be a comment. You get a post, Shawn. In his comments, someone suggested that he try out PostXING, which is cool (!) but, he seems to have the wrong impression of PostXING's erm...limitations. >I did try PostXing, and it's another tool that assumes that cross-posting is against only one server. It does? That's news to me! :) The real limitation of the current PostXING drop is that it only expects to work with the metablog API. MT has its own API that is very similar, but...

Well, it looks like Darren decided to confuse the hell out of me and make his Project Distributor available for download at guess where? Project Distributor! Okay, maybe it's not that confusing (or maybe I just confuse too easily :) This is great news - ever since I've made PostXING available for download at Project Distributor I've had nothing but great things to say about the service...and now I can have it on a server all my own! Cheers, Darren, for coming up with a great idea and making it available to everyone. You rock. [ Currently Playing : Two Tabs of Mescaline - Glassjaw...

Forreal. I had been using a different, "static" library to do syntax highlighting before...Now, if you don't like how a certain language is configured, change it! CodeHtmler is great. It gives me the option to add or modify language definitions (Generics, anyone?) IF I so desire, and it just dropped right into my app with an interface to edit the definitions already there. That's HOTT. But (in my best Lavar Burton voice) Don't take my word for it. I changed two lines of code (well, Wes did :) in PostXING and it was up and running. I'm not quite ready to release...

Darren went and fixed my Project Distributor blunder...now you can get the latest version of PostXING from the place it was originally released. Thanks, Darren.

Bob wants to see some integration of RssBandit and PostXING. This was an idea I had really early on simply because a lot of the features in PostXING were, ahem, borrowed from w.bloggar, and RssBandit already supports a plugin that starts w.bloggar for posting to a weblog. So, why couldn't I do something similar? Well, I thought that it had something to do with implementing IBlogExtension, for which I couldn't find too much documentation. Maybe it's such a simple thing to implement that only a yutz like me would need documentation. I honestly don't know and haven't looked into it too much simply...

It looks like I created (or rather raised an awareness to) a little snafu on ProjectDistributor :/ The latest release of PostXING didn't upload properly, so I'm putting a temporary download on my server: PostXINGv1.0.4335.1.zip update - it's fixed! I also rolled back the release to the last one that worked as a download over at ProjectDistributor.net. I'll be taking both down as soon as Darren lets me know things are well again. Sorry to both of you that care. [ Currently Playing : Star 69 - Fatboy Slim - Halfway Between the Gutter and the Stars(5:42) ]

I feel like I've hit .net developer's gold. I was searching for a spell checking component and came across this site (with the help of Don Smith). Not only is there a spell checker component there (which looks pretty good at first glance) but there are a bunch of other useful tools ranging from a Windows API file search wrapper to web access for Visual SourceSafe and Draco.NET. Good stuff. P.S. I'm hoping to add spell checking and a couple of other items to PostXING. If you'd like to snag a copy, you can find the latest release here.

It starts off (defaults) using something like the following (newlines added for readability): <html><head><link rel='stylesheet' href='style.css'></link></head><body><div id='main'><div class='post'><h2><a href='[Post Url]'>[Post Title]</a></h2>[Post Body]</div></div></body></html> Basically, I just go to the actual blog (using the 'view blog' button) and view source. The one here is currently using something that I hacked together pretty quickly from a layout that I, ahem, 'borrowed' from Thomas Johansen. It looks like so (again, newlines added): <HTML> <HEAD>  <link type='text/css' rel='stylesheet' href='http://www.chrisfrazier.net/blog/skins/nGalleryBlue/style.css'></link> <link rel="stylesheet" href="http://www.chrisfrazier.net/blog/customcss.aspx" type="text/css" ></HEAD> <BODY> <table border="0" cellpadding="0" cellspacing="0" class="mainTable"><tr><td class='contentCell'><div id='main'> <div class='post'><div class='news'><div class='posttitle'><a href='[Post Url]'>[Post Title]</a></div><div class='postcontent'>[Post Body]</div></div></div></div></td></tr></table></BODY></HTML> This changes the both the Preview Page and the History...

I finally released my little home-hacked tool to the wild, Thanks to Darren and his awesome Project Distributor. PostXING was originally just something that I wanted to use to see what I could successfully do in the world of WindowsForms. I never intended to release it forreal because who needs another desktop blog editor, right? Well, I've been successfully using it for months now, so I figured, why not share the love? A lot of people helped me along the way, and they're indicated in the about dialog. Big shout out goes to ScottWater for showing the way initially - a lot of...

I wanted to ask for your opinion. I've been building this little wysiwyg blog-posting tool for a little bit. I call it PostXING, and I'm using it right now to post this very message. It is inspired by a tool that ScottW wrote called Blogert. For the wysiwyg abilities, it uses an interface to mshtml. Where I could, I tried to keep the default dialogs (like hyperlink, image, etc) for use in the app. So, when adding an image using the default dialog, if you're adding it from your machine you get a path like "C:\myimages\img.gif" when you really want something...

Okay, not everything, but at least www.weblogs.com and blo.gs. I already had some of the code in place, but then I came across an example by Charles Cook, mr. xml-rpc.net hisself, and decided to hack it a little bit. Pretty simple stuff, but this post will tell me if it works :) /me:crosses fingers update: So it looks like it "kinda" worked for weblogs.com - since my blog engine, .Text pings weblogs.com itself, I got a nice little message from weblogs.com saying I should get out more and enjoy life for pinging twice in a row. Well, my friends, it's raining today. blo.gs came back...