W3 Systems W3S Incorporated

Building Software

Posted on

On Linux, the typical way to build binaries is by creating and using configure and make scripts.  These sort of work, but  I have never been on a project, or looked at an open source project, where I liked these scripts.  Descriptions like archaic, obscure,  and cryptic come to mind.   There are usually hacks involved to glue the scripts together and make them work properly.  On the W3sea framework, I'm giving up on these old 'venerable' tools.  Python is actually a good language for creating build libraries that I believe will be easier to use, and will be much more transparent and flexible.  So today w3systems is moving to a python based build system.


Posted on

Security is the paramount concern of a web based service offering. The new software stack is being written with a security first imperative. Strong passwords, digital hashes, and email based resets will be used throughout on the new systems. The new database interfaces only allow access to the database through a 'Statement', where data coming from a client is fully vetted.  The strongest encryption for privacy and authentication will be used everywhere. 

Free SSL

Posted on

Having dealt with the different SSL providers, and what they charge, SSL creates a mild barrier of entry for small businesses, especially since Snowden's revelations, and the normalization of the encrypted web.

Now there is a free source of SSL.

I'll be recommending this provider to all of my customers.

I'll also try to support this non profit as much as I can.

Please consider donating.


Posted on

I don't like the current state of 'mobile device'  detection.
Most of the methods I looked at are apt to fail over time.
The W3C or WHATWG really need to do some work on this.
My current method doesn't use user_agent — because the standards committees say it's wrong to do it that way.  I'm currently using the CSS3 selector:
screen and (min-width: 1080px)
This is a simple approach that will work until phone displays have 4K screens.
(Oh no! They already do!) 

I'll be hacking for quite a while on a future proof approach ...

The issue is the relative size of the fonts in comparison to the screen, a font size in points is supposed to be a measure in inches (1pt=1/72 inch) but they are not even close to that size on a mobile device. This is on purpose, because of the screen size. 

So a reasonable approach would be to measure the size of a word against some heuristic standard to determine if the font is too small.  It's not mobile detection we are really after, but point size v.s. screen size.
I don't want to have separate sites for mobile and PC.
(One site to rule them all.)

New Website

Posted on

The new website is up, after several years of pointing to a static page on w3sea.us.

(More on w3sea as the new framework becomes ready, but work is under way. w3sea.us will use the new code, not this hybrid code in use on w3sys.com.)

The code currently behind this website is a refresh of older code that began development in the 90's which was once described by another developer as "a riddle wrapped in an enigma wrapped in a mystery."  I really can't disagree with that assessment, but the code works well, has very low overhead, and is conducive to the development of business systems.  It's a little less mysterious than it was, and bridges the gap to some of the modern features of HTML5 and CSS3.

I'm currently only taking care of existing customers until the new code base is done.
When the new code base is done, I'll be developing SaaS packages for several business domains:

  1. Contact Relationship Management (CRM)
  2. Service Management
  3. Inventory and Sales Management
  4. Shop Floor Management
  5. Automation
  6. Project Management
  7. Code Development Tools
  8. E-Commerce and Auction Management

I'll also be looking for "user experience" (UX) expertise, developers, and partners with domain knowledge in these or other areas W3 Systems might want to grow into.