Skip to main content

Putting Your Best FoxFace On

I've always been a bit troubled by "skins", the way that many consumer or hard-core geeky tools (WinAmp was one of the more popular ones) allow users to apply skins. Not to say I don't like them ( I like a good Star Trek Skin- but I can certainly understand how they can confuse other users.

That said, I'm intrigued by this new tool for Visual FoxPro 7 through 9.
FoxFace - skin VisualFoxPro (VFP) applications with our VCX class, VFP skin, Visual FoxPro skin, skin Visual FoxPro, skin VFP - the downloadable demo is unfortunately terrible (it only shows one skin and doesn't size properly on a 1024x800 resolution) - but they do have a nice presentation on how to use it here

For $59 US, if you wanted to let your users "skin" your app themselves, they can do so. Has anyone tried this out in a real application yet?

In looking at the demo, there appears to be a FOXFACE table that contains the skin ID, name, author and email and then a variety of fields that look like they point to image types and the actual binary file.

Adding skins to a project looks pretty easy. Add the FoxFace class library to the project and drop it onto a form (or base class).

Specify the path to the class (it defaults to LIB) and then specify the Skin ID. Then compile and run.

There is also a class to let you skin the FoxPro desktop.

Whoops? Does that mean I can't change skins on the fly? That's too bad. It's hard to tell from the demo because the Skin IDs are built in - but since it's a class, I'm sure you could simply recall a method.

Now the sample skins they provide only show color and bitmap changes - couldn't users get the same effect through Windows Themes? I suppose - although this way, you could offer it specifically for your application, a nice way of letting users add their own personal touch.

Hmmm...skins in business applications- is it a good idea? Personal expression aside, I'm still deciding...but it's good to know there's a VFP tool out there for it.


Popular posts from this blog

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"...people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own …

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…