in

DOMercury Blog & Forums

Everything DOMercury behind the scenes...

DOMercury Blog

March 2008 - Posts

  • Vacation, WPF, and DOMercury Users around the World

    I'm excited about the WPF version of the DOMercury interface.  I’ve been learning how to use Microsoft Expression Blend, and the rudimentary beginnings of a flashy interface for DOMercury are beginning.  Also, I intend to make the interfaces plugin extensible as well, allowing .NET programmers to create their own interfaces (WPF or Windows Forms) for DOMercury.  I’m also working on some Item Prioritization improvements for DOMercury to make it a bit “smarter” on what things show up according to your search keywords.  The file extensions filtering is a start, but I know this definitely doesn’t solve all problems.It has also been brought to my attention that DOMercury isn’t very nice to users of Non English versions of Windows.  My deepest apologies for this.  There will be fixes for many of these issues in the next version of DOMercury.In the meantime, If DOMercury cannot find your Start Menu shortcuts because your Start Menu is named something other than “Start Menu”, you can follow these steps to create a temporary fix for the problem.1.       Create a folder in your user directory called “Start Menu”.  This is to stop DOMercury from yelling at you that it cannot find a Start Menu folder.2.       Create an entry in the FolderIndexorPlugin Options to your actual Start Menu, with the filepattern set to *.lnk

    If there are any other multicultural temporary fixes that you have discovered, please post them in the forums.

     

    Lastly, I am going to be on vacation next week, so while there are a lot of cool things down the pipeline, they may not be released for a while, as even though programming DOMercury is a hobby for me, it is not one I will be able to take with me on vacation.  I will have too much vacationing to do next week for me to be programming.  So Enjoy DOMercury 2.6 at the moment, but the next version will be even sweeter.

     

    Dominick

     

  • Site under redesign

    You may have already noticed the forums are different.  You have also obviously noticed that a blog exists now. These are the first steps in the major redesign of the DOMercury web site. It is going to look very different, hopefully very soon. 

    Also, I am toying with WPF.  The ability to make different skins does not seem interesting enough to many people, who want for more bells and whistles whilst using DOMercury.  There may be a 3.0 release in the near future with DOMercury itself looking radically different.

     

    -Dom 

  • DOMercury 2.6 Released!

     I released DOMercury 2.6 this evening, along with a pile of other updates. (3 new plugins)

    Why should you upgrade to 2.6?  I'll give you a few big reasons, and then a pile of smaller ones.

    First is the index filtering.  Every time I wanted to search for a word document I had to deal with four or five "temp" files that were at the top of the list (the ones that start out with a ~/whatever).  Also if I was looking for a Visual Studio Solution file, I didn't need all the individual .cs, .h, .cpp, .dll etc.  that would show up in the index.  I figured if they were annoying me, they have got to be annoying you guys too.  So I built in the Index Filtering functionality: Options -> Index Filters, which allows you to add file extensions for files that you want to exclude from being indexed.  SImple as that.  Its a great way to prune the index and help you get to the programs and files you want to get to faster.  

     Speaking of the Options form, did I mention that DOMercury no longer freezes if you invoke it while its Options form is displayed?

     Ctrl + T:  You guys are going to love this.  It forces whatever you are typing to text.  Not only will it make it easier for you to run command prompt commands (ipconfig, ping 127.0.0.1, etc) but it will make interacting with the Window Desktop Search plugin (mentioned below) oh so much more fun. 

    DOMercury now lets you know when it is digging for a sub index.  This is nice, especially for plugins that interact with the web (Todoist, Voo2do) and plugins that must search your hard drive (see below) 

    I made some changes to the Plugins screen in the Options Form, so hopefully modifying plugin options will be easier to do now.  A lot of people had told me that they didn't even know advanced functionality options (Such as the FolderIndexor Plugin) existed because it was buried so deep within the Options Form.  I tried to make it easier to understand.

    Append to text file:  Manage your own todo list?  its made even easier now with the Append to Text File action that exists on text files and csv files.

    New Folder action allows you to create a new folder within a selected folder as well.

     

    Now for the plugins:

    Windows Desktop Search Plugin:  I'm real excited about this one.  It has already served me greatly and I've only had it working for about 2 days now.  What it does is it puts a sub index on a text item (which you can create easier with the Ctrl + T keystroke) which gives you back Windows Desktop Search Results based on a search done on the text entered.  You can then perform any DOMercury actions on any of the WDS results.  This is great for finding specific folders to dive into, or sets of solution files or code files.  If my description was hard to understand, you'll have to see the video in the Videos Section.

     Clipboard Plugin BETA:

    The clipboard plugin is another plugin that I have come to love for its usefulness.  It keeps a history of all text you copy to the clipboard, and you can call up the "Clipboard" item in DOMercury, select a clip in the history, and make it the current clip on the clipboard.  It is great for code snippets or multiple pieces of text you have to copy from one place to another.


    This is the first time I've ever released a Beta plugin, and the clipboard plugin has some issues, but its usefulness is too great to hold back. 

    For Vista Users:
        Download this plugin and use it! IIn Vista, this plugin works just fine. 

    For WIndows XP users:  
        This plugin has some issues in XP however.  It functionally works fine in Windows XP, but the Clipboard plugin slowly steals memory as it runs.  This needs to be fixed for it to become stable for users on Windows XP.  My tests on XP show that it works for about 2 days before DOMercury needs to be restarted to save your system performance.  If you never leave DOMercury running for more than a few hours or so, you may have no trouble with this plugin, but if you are someone who leaves your computer running for days, you may want to wait until it becomes more stable for XP users.

    iTunes Plugin BETA:
        People have been asking for an iTunes plugin for a while.  Well here it is!... mostly.  You can call up the "iTunes Controller" to Play, Pause iTunes, move to the next or previous track, or even display current track information.  You can also dive into the iTunes Controller and peruse albums or artists, play them, or play specific tracks.

    Why Beta:  For some reason, if iTunes is not open while DOMercury starts up with this plugin, iTunes gets opened.  Also, the album art is finicky on whether or not it wants to appear.  These are annoyances, not complete failures, so I am releasing the plugin as Beta for Early Adopters and those who want to view and modify the source.


     


     

  • The Beginning of the DOMercury Blog

    As you may or may not have noticed, the phpBB forums no longer exist.  They were especially suseptible to spam, and I really couldn't do alot with them except manage some forums.  I just made the switch to Community Server.  The DOMercury site is under redesign now, and by teh end of this weekend I should have released a few new plugins ( iTunes BETA, Clipboard BETA, and Windows Desktop Search.)  WIth any luck DOMercury 2.6 will be out soon.  Ive been playing with WPF, trying to get over my glaring weekness of making "ugly as sin" front ends, and I'm really enjoying playing around with Expression Blend, so there may be a .NET 3.5 version of DOMercury released.  I am also toying with the idea of releasing the engine-behind as its own separate assembly, so people can make interfaces with basically unrestricted opportunities.  Look for lots of updates in the next few weeks, Ive been putting my time into DOMercury lately...

More Posts
Powered by Community Server (Non-Commercial Edition), by Telligent Systems