Skip to main content

SW Fox: Why NOT Show your own apps?

One of the sessions that I didn't get to attend last night was the "Show us your apps". I think that session would have been really interesting.

Many of the attendees I spoke to were fairly shy about their own FoxPro applications. They would talk about it (as it is their "baby" so to speak) but when asked about specific features that they should show, they seemed to shy away.

That's unfortunate - because I don't think I've ever seen a single FoxPro app (with the possible exception of some purely framework-based apps) that hasn't included a unique feature or hook.

That's one of the reasons I'm particularly excited about Cathy Pountney's session about customization vertical market apps.  Only problem is that it's on right when I've got to get ready to leave. I think I'll have to corner her separately for a quick interview.

But back to my point, one my client apps is an application that was ported from DOS and brought kicking and screaming up to Windows and now finally over to SQL. It has TONS of Bad features (filtered grids, etc). BUT...it also includes some great features: built-in alerts, custom business rule validation.

So when asked to show my apps, I wouldn't show the bad stuff (well, I might to show that it exists everywhere) but the really cool stuff.

Everyone's got some kind of cool in their applications somewhere...why not show it?

Comments

Cathy Pountney said…
It's interesting that you mention my session in reference to showing an app. The concept for my "customizing a vertical market application" session came about after seeing two other people show their apps at user groups. I took ideas from both of those apps, combined with some new ones of my own, and came up with the conept I showed at SWFox. Seeing what other people do in their apps can trigger great ideas for you to implement in your app, even if you do it differently.

Popular posts from this blog

FoxInCloud Stats

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

http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html



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…