Before Google Chrome version 32, obtaining a list of open tab titles was somewhat trivial. Each tab was it’s own “Window” and had it’s own handle. So you could use that handle and obtain the title via the window caption. When Google Chrome updated to version 32, a lot happened behind the scenes with regards to UI rendering. (see here for more details).

With the v32 update, using the method mentioned above you can only obtain the current open tabs title. No good. If we want a list of all open tabs, we have to do something different. In this case, it’s using the somewhat recent UI Automation accessibility framework. This framework allows you to treewalk through an applications UI, find and interact with majority of it’s interface elements.

Finding the tabs

To browse and treewalk through UI elements of an application, you can use the inspect tool by Mirosoft found in the Windows Developer Kit. As you can see from the screenshot below, the main caption of our parent “Google Chrome Window” is the active tab title.

The Code

To get list of open Chrome Tabs and to utilise UI Automation you’ll need to add a couple of references to your project;

UIAutomationClient.dll
UIAutomationTypes.dll

Located in; C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0 (or 3.5)

VB.NET

'//Grab all the Chrome processes
Dim chrome() As Process = Process.GetProcessesByName("chrome")

'//Exit if chrome isn't running
If chrome.Length <= 0 Then Exit Sub

For Each chromeProcess As Process In chrome

	'//If the chrome process doesn't have a window handle then ignore it
	If chromeProcess.MainWindowHandle <> IntPtr.Zero Then

		'//To find the tabs we first need to locate something reliable - the 'New Tab' button
		Dim rootElement As AutomationElement = AutomationElement.FromHandle(chromeProcess.MainWindowHandle)
		Dim condNewTab As Condition = New PropertyCondition(AutomationElement.NameProperty, "New Tab")
		Dim elemNewTab As AutomationElement = rootElement.FindFirst(TreeScope.Descendants, condNewTab)

		'//Get the tabstrip by getting the parent of the 'new tab' button
		Dim tWalker As TreeWalker = TreeWalker.ControlViewWalker
		Dim elemTabStrip As AutomationElement = tWalker.GetParent(elemNewTab)

		'//Loop through all the tabs and get the names which is the page title
		Dim tabItemCondition As Condition = New PropertyCondition(AutomationElement.ControlTypeProperty, ControlType.TabItem)
		For Each tabItem As AutomationElement In elemTabStrip.FindAll(TreeScope.Children, tabItemCondition)
			Debug.WriteLine(tabItem.Current.Name)
		Next

	End If
Next

C# (Thanks to Steve Greene in comments)

Process[] procsChrome = Process.GetProcessesByName("chrome");
if (procsChrome.Length <= 0) {
 Console.WriteLine("Chrome is not running");
 return 0;
}
foreach(Process proc in procsChrome) {
 // the chrome process must have a window 
 if (proc.MainWindowHandle == IntPtr.Zero) {
  continue;
 }
 // to find the tabs we first need to locate something reliable - the 'New Tab' button 
 AutomationElement root = AutomationElement.FromHandle(proc.MainWindowHandle);
 Condition condNewTab = new PropertyCondition(AutomationElement.NameProperty, "New Tab");
 AutomationElement elmNewTab = root.FindFirst(TreeScope.Descendants, condNewTab);
 // get the tabstrip by getting the parent of the 'new tab' button 
 TreeWalker treewalker = TreeWalker.ControlViewWalker;
 AutomationElement elmTabStrip = treewalker.GetParent(elmNewTab);
 // loop through all the tabs and get the names which is the page title 
 Condition condTabItem = new PropertyCondition(AutomationElement.ControlTypeProperty, ControlType.TabItem);
 foreach(AutomationElement tabitem in elmTabStrip.FindAll(TreeScope.Children, condTabItem)) {
  Console.WriteLine(tabitem.Current.Name);
 }
}

Example Project / Github Repo

The code snippet above has one downfall, it only seems to grab a single Chrome window’s tabs. So if you have multiple Chrome windows open, it’ll just grab the last active set of tabs. I’ve uploaded a project to Github that fixes this issue and gets all open Chrome windows tab titles. Github Repo.

Conclusion

UI Automation is pretty neat. Getting the UI element title or caption is only just scratching the surface. For example it’s possible to interact with the elements such as click on buttons, set values and much more. I’ve worked quite a bit with windows and manipulating them via their handles, but being able to drill down deeper to individual UI elements will definitely come in handy.

The post Get List of Open Chrome Tabs .NET appeared first on Bluelight Dev.

Before getting started you will need the following…

• A WordPress install
• IIS7
• Web Platform Installer (link)

Start by opening your IIS Manager. (Start > Run > inetmgr) Under Sites select your website. If you don’t see the IP Address and Domain Restrictions icon then you will need to install it. If you can see it you can skip ahead.

To install the IP Address and Domain Restrictions feature, double click on the Web Platform Installer icon. If this icon isn’t there either then you will need to install the Web Platform Installer from Microsoft. You can download it here.

Inside the Web Platform Installer, search for IP Address and Domain Restrictions and install it. (It may be called IIS: IP and Domain Restrictions)

Once installed, you will want to select your website on the left hand side under Sites, and then expand it and select your wp-admin directory. Once selected double click on IP Address and Domain Restrictions.

First up you will want to set the Feature Settings (right hand side menu) to deny. This will deny all access to our selected wp-admin directory. We then want to setup our whitelist of IP Addresses. If you wish to use domains in your allow list then you will need to enable it in the Feature Settings window.

To start adding the IP addresses or domains you wish to allow, click on the Add Allow Entry… link on the right hand side. You can add a single IP Address, an IP Address Range or a domain name (if the domain option isn’t there or disabled go back to Feature Settings and enable domains.

Once you’re finished with wp-admin, you might also wish to do the same with wp-login.php. If you can’t see the wp-login.php file on the left hand side under your site, click on the Content View button. Find wp-login.php and then click the Switch to Feature View… option on the right hand side. From there you will see wp-login.php is selected and you can open the IP Address and Domain Restrictions feature.

All done! You should now see a 403 Access Denied error when trying to access the restricted content from an unlisted IP.

The post WordPress IIS restrict access by IP address appeared first on Bluelight Dev.

If you don’t have an Imgur account you can register for one here.

Change log:

+ ADD: Imgur Account support (Aaron)
+ FIX: Drag Screenshot label not centering. (Jason)
+ CHANGE: Drag Screenshot selection area more apparent. (Jason)
+ CHANGE: Crop selection in Viewer now more apparent. (Jason)
+ CHANGE: About form title icon. (Jason)

The post Upload to your Imgur Account with SnagIMG appeared first on Bluelight Dev.

Although the Socialize SDK comes with a great ready made ‘Action Bar’, the appearance of it didn’t quite suit the style of SwiftKit Mobile. So a custom social bar was made to include views, share, like and comment. You can see the new social bar in action in a couple of the screenshots below.

When you first update to the latest version you will automatically have a ‘profile’ created for you. If you wish to you can then link your Facebook and or Twitter account. It’s recommended that you link your profile with Twitter or Facebook as that way if you re-install the app or upgrade to the full version all your likes, comments and views will be kept. To do this simply hit the comment button on the social bar and then hit your menu key and go to settings. From there you can customize your profile.

Currently the social bar is available in the Android version of SwiftKit Mobile. If all goes well we will look into integrating it into the iOS version.

The post Socialize integration – SwiftKit Mobile goes social appeared first on Bluelight Dev.

The day Lion was released every Mac user was complaining about the lag. RuneScape was completely unplayable. Many people thought this was a symptom of SwiftKit, but it happened in any browser. Somebody on the RuneScape forum figured out how to use the .jar from the Windows client and mix it with the .jar loader template app to create a playable executable that would open just an applet. This applet was also plagued with problems, one being if you resized the window the game would crash. The upside was that issues from loading RuneScape in a browser/SwiftKit (which also runs in a ‘browser’, technically) were now gone, with the addition of a few others (such as odd behaviour on Software mode, and graphical glitches

At this point it looked like this was going to be it for RuneScape on the Mac, inside this volatile client. I decided to take a look at tracking another application’s window. This was easier said than done, it’s something there was little to no documentation on. Eventually I used AppleScript, which I admit is definitely not the best and most elegant solution but it’s all I could come up with at the time. It did work, but only managed to get me position and size updates after they had been made, they were not live, meaning if you moved the window around the screen the client would only adjust it’s window’s positions after you let go of your mouse. A feature I am quite proud of is a resize window that sat over the client’s window, allowing you to resize the client without crashing (again, this was done with AppleScript, bridging my resize window’s position and size to the applet window’s position and size).

I played with this for a week or so to test it out, it was good for what I had to work with but I wasn’t 100% happy. Just before we planned to release this, Jagex made yet another update to their game, popping out the applet from the game when loaded in a browser, which was now made the gameplay perfect, there was just one problem, having the game in another window was quite annoying, not to mention if you closed the window that spawned it, the spawned applet would close. I decided the client-based version I had created just wasn’t going to cut it, so I scrapped it. This was the version 0.2.0b nobody ever saw.

The SwiftKit Mac project was becoming quite messy. Previously a lot of things were setup in “Interface Builder”, which is a tool that allows you drag buttons, images and other controls onto a canvas to populate your interface, which I consider to be lazy. Since then I have done all my other interfaces (on other projects) in pure code. Doing it this way makes it very easy to make interfaces dynamic, and being able to reuse custom components, the downside being coding things takes about 3x as long as using IB.

SwiftKit was now going to be completely focused around this pop out applet. There was going to be an immense amount of code to make this experience as seamless as possible for the user. Taking this and the messiness of the current state of the projects into account, I decided to recreate everything from scratch, starting with the hardest part, tracking the applet.

My previous method of doing this using AppleScript no longer worked. It would only work from anything launched from a .app bundle. This pop out applet was different, and launched directly from a process instead. If you open the Activity Monitor while the pop out is running, you will see it under the list identified as ‘Java’. I managed to find another way of getting another process’ window position and size, again very undocumented. This was a lot faster than my previous AppleScript implementation, and now I could get another windows’ frame even when it was being dragged around the screen. With this out of the way I found a way to reposition and resize the applet, which allowed me to restore the applet’s previous frame whenever SwiftKit was opened (by default it opens to a set size in the middle of your screen).

This version was looking to be pretty good, but it needed just one more thing. Because the applet is another process none of my shortcut keys would work outside SwiftKit. I had to register all the shortcuts I wanted the applet to access as global, meaning you could use them anywhere on the Mac, even if SwiftKit was in the background and another program was in the foreground. Of course, I didn’t want Command + S (used for screenshots) overriding save functionality in another program, such as Word, so I have to turn them on when either SwiftKit or the applet are in the foreground, and then turn them off when any other program is moved into the foreground.

Obviously there’s a lot more work involved in all of this, compared to me explaining it in a 2 minute blog post. I also work as a full time developer during the day, and coding when I come home is usually not a priority. I will end this post with a reassuring final note, I have tested v0.3.0b on Mountain Lion, and it’s flawless

(RuneScape on the other hand, not so great, it only works in OpenGL mode, although it could be worse)

The post SwiftKit Mac v0.3.0b appeared first on Bluelight Dev.

We’ve also fixed a few other bugs, mainly one being with dragging a screenshot while using multiple monitors.

Change Log:
+ ADD: Host Redundecy
+ ADD: Remove Icon.
+ ADD: UploadHistory.xml now has a remove value for Imgur Images.
+ ADD: “Remove from web” added to history right click menu for Imgur Images.
+ ADD: Imgur Delete button (undo upload) to upload form
+ ADD: Imgur Host, as well as Host provider option.
+ CHANGE: Copyright info updated.
+ FIX: Bug with Drag Screenshot and multiple monitors.

The post imgur upload now available with SnagIMG appeared first on Bluelight Dev.

For a feature that should have been in the first release of SnagIMG it sure took awhile to get added. Truth be told as the developer of SnagIMG, I never actually had more than the one monitor – so it wasn’t too high on my priority list. Apologies for that. Now that I have a multi monitor setup, I set to work making sure SnagIMG could utilise more than just the primary monitor.

Both the drag screenshot and full screenshot functions will now capture all active monitors in your setup. We’ve also added a new setting in the settings form to disable this and revert it back to the old ways of only screenshotting the primary monitor.

In other news, we’re attempting to get access to the imgur API which seems to be a much more favourable service over ImageShack, but haven’t had much luck as of yet.

The post SnagIMG can now screenshot multiple monitors appeared first on Bluelight Dev.

High-resolution (512 x 512)

I wanted to keep it the same with it’s windows counter-part. Now that it required a much higher resolution I took the time to add a few features to it.

Feel free to use it for promotion or personal use. Just if you modify it or use it for any of your projects please credit me (zpoon.ca).

The post SwiftKit OS X Media appeared first on Bluelight Dev.

Let me take you back roughly 18 months.

<insert crossfade here>

I was exactly the person I described above, looking multiple times for a SwiftKit version for the Mac. Mac users will know what I’m talking about here, but if you have ever tried playing RuneScape through a browser and browse the internet at the same time it is very unstable and the browser sometimes crashes, ending both your RuneScape and web browsing adventures. I had waited long enough and decided to put an end to this myself by creating an Application that was simply a website that loaded the RuneScape homepage – keeping my ‘scaping and web browsing to separate Applications. It worked very well, and if the browser crashed it would no longer take RuneScape with it.

This simple client was pretty much a mimic of the official RuneScape client Jagex released. It was written in Objective-C, which is the standard programming language for all things Mac. At this stage I barely knew anything about Objective-C so it was a stretch for me doing what I actually managed to do.

I used this client privately for 6 months, before somebody from Runescape Community (Maxman) messaged me asking about RuneScape on his newly acquired Mac. I sent him a version of my private client, which a few days later I posted in the programming and web development section and created a SourceForge page for. As it gained popularity the suggestions were always the same, which as you can probably guess was the suggestion of a highscore lookup feature. I ended up teaching myself the bare bones of Objective-C to get this implemented (it was also my most desired feature too). This version remained the same for about 7 months (with a few minor updates when new skills/minigames were released).

There are probably quite a few Mac users reading this right now that actually use that version to play.

Here is the original forum thread that I used

After finishing a unit in mobile development at Uni, my name came up when my lecturer’s friend was looking for a developer. This job was coding for the iPhone – in Objective-C. A few months later I decided to recode my RuneScape client project from scratch, as the older code was horrible compared to what I had learned at work. I recoded it including a price lookup and a custom links section, very similar to SwiftKit… which is what I’m getting to.

Just before I was about to release this new version the SwiftKit team contacted me asking if I would consider joining them to bring SwiftKit officially to the Mac. I accepted of course!

<insert another crossfade here>

In the past few weeks I have been adding some additional features bringing it up to par with the Windows counterpart in terms of basic features – and a few extras (get working Strider, *whip*).

As development is now coming to an end you can prepare to see an open beta released very soon, so keep an eye on www.swiftkit.net!

Don’t get too excited now, but here’s a few pictures.

If you’re a Mac user and you play RuneScape then chances are you have looked at SwiftKit praying for a Mac OS X version, but got delivered that dreaded “SwiftKit is Windows only, there will never be a Mac version” answer.

Let me take you back roughly 18 months.

<insert crossfade here>

I was exactly the person I described above, looking multiple times for a SwiftKit version for the Mac. Mac users will know what I’m talking about here, but if you have ever tried playing RuneScape through a browser and browse the internet at the same time it is very unstable and the browser sometimes crashes, ending both your RuneScape and web browsing adventures. I had waited long enough and decided to put an end to this myself by creating an Application that was simply a website that loaded the RuneScape homepage – keeping my ‘scaping and web browsing to separate Applications. It worked very well, and if the browser crashed it would no longer take RuneScape with it.

This simple client was pretty much a mimic of the official RuneScape client Jagex released. It was written in Objective-C, which is the standard programming language for all things Mac. At this stage I barely knew anything about Objective-C so it was a stretch for me doing what I actually managed to do.

I used this client privately for 6 months, before somebody from Runescape Community (Maxman) messaged me asking about RuneScape on his newly acquired Mac. I sent him a version of my private client, which a few days later I posted in the programming and web development section and created a SourceForge page for. As it gained popularity the suggestions were always the same, which as you can probably guess was the suggestion of a highscore lookup feature. I ended up teaching myself the bare bones of Objective-C to get this implemented (it was also my most desired feature too). This version remained the same for about 7 months (with a few minor updates when new skills/minigames were released).

There are probably quite a few Mac users reading this right now that actually use that version to play.

Here is the forum thread that I used: http://forums.zybez.net/topic/1330565-open-source-mac-runescape-client/

After finishing a unit in mobile development at Uni, my name came up when my lecturer’s friend was looking for a developer. This job was coding for the iPhone – in Objective-C. A few months later I decided to recode my RuneScape client project from scratch, as the older code was horrible compared to what I had learned at work. I recoded it including a price lookup and a custom links section, very similar to SwiftKit… which is what I’m getting to.

Just before I was about to release this new version the SwiftKit team contacted me asking if I would consider joining them to bring SwiftKit officially to the Mac. I accepted of course!

<insert another crossfade here>

In the past few weeks I have been adding some additional features bringing it up to par with the Windows counterpart in terms of basic features – and a few extras (get working Strider, *whip*).

As the development is now coming to an end you can prepare to see the it released very soon, so stay tuned.

Don’t get too excited now, but here’s a few pictures.If you’re a Mac user and you play RuneScape then chances are you have looked at SwiftKit praying for a Mac OS X version, but got delivered that dreaded “SwiftKit is Windows only, there will never be a Mac version” answer.

Let me take you back roughly 18 months.

<insert crossfade here>

I was exactly the person I described above, looking multiple times for a SwiftKit version for the Mac. Mac users will know what I’m talking about here, but if you have ever tried playing RuneScape through a browser and browse the internet at the same time it is very unstable and the browser sometimes crashes, ending both your RuneScape and web browsing adventures. I had waited long enough and decided to put an end to this myself by creating an Application that was simply a website that loaded the RuneScape homepage – keeping my ‘scaping and web browsing to separate Applications. It worked very well, and if the browser crashed it would no longer take RuneScape with it.

This simple client was pretty much a mimic of the official RuneScape client Jagex released. It was written in Objective-C, which is the standard programming language for all things Mac. At this stage I barely knew anything about Objective-C so it was a stretch for me doing what I actually managed to do.

I used this client privately for 6 months, before somebody from Runescape Community (Maxman) messaged me asking about RuneScape on his newly acquired Mac. I sent him a version of my private client, which a few days later I posted in the programming and web development section and created a SourceForge page for. As it gained popularity the suggestions were always the same, which as you can probably guess was the suggestion of a highscore lookup feature. I ended up teaching myself the bare bones of Objective-C to get this implemented (it was also my most desired feature too). This version remained the same for about 7 months (with a few minor updates when new skills/minigames were released).

There are probably quite a few Mac users reading this right now that actually use that version to play.

Here is the forum thread that I used: http://forums.zybez.net/topic/1330565-open-source-mac-runescape-client/

After finishing a unit in mobile development at Uni, my name came up when my lecturer’s friend was looking for a developer. This job was coding for the iPhone – in Objective-C. A few months later I decided to recode my RuneScape client project from scratch, as the older code was horrible compared to what I had learned at work. I recoded it including a price lookup and a custom links section, very similar to SwiftKit… which is what I’m getting to.

Just before I was about to release this new version the SwiftKit team contacted me asking if I would consider joining them to bring SwiftKit officially to the Mac. I accepted of course!

<insert another crossfade here>

In the past few weeks I have been adding some additional features bringing it up to par with the Windows counterpart in terms of basic features – and a few extras (get working Strider, *whip*).

As the development is now coming to an end you can prepare to see the it released very soon, so stay tuned.

Don’t get too excited now, but here’s a few pictures.

The post SwiftKit for Mac! appeared first on Bluelight Dev.

The icons should be pushed with the next update, along with a few other features that we’ve added. The next area I’ll focus on is the main screen, and making that area a bit more pretty. The current brown mess isn’t going to be sticking around for long.

The post New icons for SwiftKit Mobile appeared first on Bluelight Dev.

Version 1.0 at the moment features a highscores lookup. However with future updates we plan to expand on the content to include database lookups (prices, items, monsters, clans), Adventure Log, basic calculators, notifications and much more.

If you do have an Android device we encourage you to install it and let us know how it performs, positively or negatively.

The post SwiftKit Mobile for Android appeared first on Bluelight Dev.

Database Editor
This is a new tool that has been developed to allow SwiftKit staff members to access, modify, add and delete data within the SwiftKit00x.skd files. The SwiftKitData00x.skd files are used for the calculators, quest center, atlas, achievement diary center etc. The tool was written in .NET and connects to a MySQL database on the SwiftKit server. Currently the changes made are not live, in order for the changes to take effect the data needs to be exported, packed and then uploaded. The main benefit of the tool is that it allows other staff members to manage the data instead of just myself.

SwiftKit Control Panel
This is a tool that I wrote for myself back when I was initially developing SwiftKit. The main purpose of this tool is to allow me to manage updates for SwiftKit (including SwiftKit MS). While the tool doesn’t actually do the uploading it more or less does everything else. Including packaging, compressing, signing integrity, version control and placing all the update files in a holding directory ready for upload.

The first screenshot is where I grab the world info for all the RuneScape servers and pack it into a single file. The second screenshot is where I come after I have compiled a new version of SwiftKit. Clicking one of the update buttons increments the version number, compresses the executable and signs its integrity. The last screenshot is where I package and compress all the SwiftKit000x.skd data files into a single .skd file. The SwiftKitData001.skd file has over 670 calculator images compressed into it. This is why you see an unpacking images progress bar in the Calculators utility.

So there’s a quick look the two main tools used for managing the SwiftKit project. Not an ordinary Dev Blog post but hopefully still informative for those who had been wondering – or had asked me about them in the past.

The post Tools Behind Maintaining The SwiftKit Project appeared first on Bluelight Dev.

Changes and Fixes:
+ ADD: The ability to right click upload images in Windows Explorer. (If selecting multiple images they must be same format)
+ ADD: Multi Uploader.
+ ADD: The system tray icon now changes if SnagIMG is disabled.
+ ADD: SnagIMG will now check for updates on startup.
+ ADD: New option in Settings to disable update check on startup.
+ FIX: Panning in the Viewer should now work correctly.
+ FIX: Few glitches fixed with the Drag Screenshot feature.
+ FIX: No longer crashes on startup after reboot/logoff.
+ CHANGE: Update process is now a little more automated.
+ CHANGE: You can now open multiple instances of the Viewer.

To update, either right click the SnagIMG system tray icon and check for updates or go to the downloads section.

The post SnagIMG Update 2.2 – Multi Upload appeared first on Bluelight Dev.

You can also check out the new Screenshot Viewer in the latest SwiftKit MS update. For instructions on how to download SwiftKit MS see here.

The first most noticeable feature is the thumbnails. This was something we wanted to do from the start however when a typical player has hundreds and hundreds of screenshots in a single folder it can get a bit tricky. We overcome this problem by having the thumbnails generate on the fly when they come into view. Originally it would take around 5 seconds to open a folder with a hundred or so screenshots, now it’s opens instantly.

Organising your screenshots will also be a lot easier with the ability to create new folders, drag and drop existing screenshots/folders and also cut,copy and paste.

The above screenshots show you what happens when you double click or ‘View’ a screenshot. The forward and back buttons will navigate you back or forward through the other screenshots in the current directory. With the ‘Stretch to Fit’ button checked the screenshot will stretch or shrink depending on the window size, otherwise with it unchecked the screenshot will remain in it’s original size and you can pan it. The upload feature is not yet finished that will have to wait for the next post.

That’s about it for now, just a quick glimpse at what we’ve been working on. There’s only so much we can do before MechScape is released but so far so good. We encourage you to check out SwiftKit MS and let us know what you think on the forums or in a comment here.

The post SwiftKit MS – Screenshot Viewer appeared first on Bluelight Dev.

A few other changes are you can pan screenshots in the Viewer, ‘Check For Updates’ menu added and an ‘Open in Browser’ button added to the Upload form. See full story for a complete list of changes. To update simply make sure SnagIMG is closed (right click > exit on Camera icon in system tray), download and install over the top of your existing installation.

Changes and Fixes:
+ Threaded the screenshot upload process.
+ CTRL+PrntScr now brings up the Drag Screenshot form.
+ Added ‘Open in Browser’ button to the Upload form.
+ Added a ‘Check For Update’ menu option.
+ You can now pan screenshots in the Viewer.
+ Made ‘Upload Screenshot’ button easier to identify in Viewer.
+ Cross hair should appear correctly when using the blur tool.
+ Adds to registry the installed path on startup.

The post SnagIMG v2 appeared first on Bluelight Dev.