The LonePenguin Software Project is the fruit realized from countless hours of development effort. My name is Erik Johnson and I have been developing software professionally for 20 years. The products that I create are made available at this site. This is your starting point to gain more information, download evaluation copies, purchase and download registered copies, and get support for the products that I produce.
The easy to use, portable, encryption and decryption program. The latest version 3 represents a full makeover and redesign that retains the best of the version 2 favorite, while adding more capabilities that users have been wanting.Learn more and get it by visiting the LockMaster site: click here
The decision aid that makes constructing Pro and Con lists easy and helpful. ProCon has a simple and intuitive user interface and produces a decisive result. Whether you are at home or in a professional environment, ProCon will be your question resolution tool of choice.Learn more and get it by visiting the ProCon site: click here
When a software developer decides to develop a product, whether a large corporation or single individual, they contribute a design philosophy to the final product. This design philosophy can influence the product in many different ways. Several factors, such as budget, schedule, and development staff familiarity with various platform technologies all play their part in how the design philosophy is shaped.
Each software developer's design philosophy is different and emphasizes different design construction methodologies. Here are the elements of design approach that I find important and value as each product I create is developed:
How many times have you come across a software product that looks like it meets all or most of your functional requirements ... the Web Page for the product outlines the product's capabilities in the most enticing way, complete with screenshots of the product in action ... your curiosity is peeked. The product even comes with a trial version. It's time to download it and give it a try.
Now comes the let down, there's a requirements list ... what's this?
There's a reason why the manufacturer of the product you're looking at would place all these requirements on you, the user. They're leveraging the capabilities of these other products to save development time and resources for themselves. At your expense!
Call me old-fashioned (and I'm trying not to date myself here), however I remember a time when software could be downloaded or copied from a disk, and executed/run without a complicated prerequisite installation and configuration procedure. No mess, no fuss. You just run the program.
The ZTS architecture design concept is one where the user does not need to have an endless list of 3rd party products, undue amount of Operating System upgrade patches, and other excessively pricey hardware owned in order to use it. This means that only reasonably contemporary Operation System elements are necessitated for a products use. The type of Operating System elements would be basic stuff like having a supported Operating System installed on your computer. If networking is a fundamental functional element of the product capabilities, only standard equipment and software device adapters (free of special Operating System patches) should be required. If a Web Browser is utilized, the ZTS product will not require the absolute latest Web Browser of only a specific product vendor be installed, rather any Web Browser of virtually any version be installed. The ZTS designed product will operate with reasonable efficiency and throughput when the Operating System minimum CPU, RAM memory, and disk requirements are available.
A premium is placed on the ZTS architecture design concept in every LonePenguin Software Project product.
One common limitation of many software applications is that they are available on only one Operating System (O/S) platform. In order to prevent this happening to LonePenguin Software Project applications, I've developed a logic library common to all my applications that is specifically designed to be utilized in multiple O/S environments. It has been named: MaPeL (for [M]ulti-[P]latform [L]ibrary). This means that all LonePenguin Software Project applications developed gain the benefit of being available in the O/S platforms that the MaPeL library is compatible for.
Currently for all LonePenguin Software Project applications, the following Operating System environments are available:
There are intermediate plans to add support for the following Operating System platforms:
Don't hesitate to provide feedback indicating that you'd like to see increased priority planning of the above additional O/S platforms. At the moment, it's something planned, however direct user feedback indicating that these platforms are desired sooner rather than later helps me prioritize whether I should place this migration/porting work higher relative to other development tasks.
Whether you'd like to ask a question about a product or would just like to give feedback, there are two methods to do so. You can ...
All LonePenguin Software Project products are supported through the Internet ONLY (via E-Mail and Web Site submitted messages).
You are visitor number 26565.