By The Power of PHPNG

HardcoderNG is PHPNG based toolset/stack of slowly and carefuly written code for developing various kind of applications. At this time of writing, HardcoderNG is in early (baby) stage of development, and God only knows when first production ready version will come out. Nonetheless, some of the functionalities are already quite ready for playing, testing, production, and as time passes on, there will be more and more of that kind.

Application scripts utilization

Like each and every other similar PHP software aroung the web, this one is broken to smaller pieces. There are three types of groups in which those smaller pieces reside and are called extensions, modules or libraries. For both backend and frontend utilization.

PHP utilization

Extremely powerful templating engine, markup language generator and language extractor. Funcdown brings the process of creating HTML and XML content to an probably yet unexplored dimension of detailed control of every aspect for well known markup languages. Find out more about - Funcdown

Anonymous, independant PHP Object that collects one or more css or javascript files within a single http request, displaying them in a single line fashion or as they are, called Catmice. Find out more about - CatMice

Javascript utilization

Hardcoder related

Vanilla Javascript File is small and effective (around 8kb (gzipped)) based javascript file for every day use. It is a crucial part of HardcoderNG frontend logic and it is responsible for all heavy DOM transformations and all that CSS alone can't accomplish on this very website. It is carefuly crafted, well tested and does it's job correctly. The way of writing and calling it is very similar to Jqery (that one `$`), although, all the similarities ends on how it looks. Find out more about - VFile.js

Foreign ™

ace.js - The high performance code editor for the web. Ace is an embeddable code editor written in JavaScript. It matches the features and performance of native editors such as Sublime, Vim and TextMate. It can be easily embedded in any web page and JavaScript application. Ace is maintained as the primary editor for Cloud9 IDE and is the successor of the Mozilla Skywriter (Bespin) project.

Technical Data

Style

While this website is generally optimized for plethora of different screen sizes, from older smart handled devices to more and more bigger screens, be it portrait or landscape, it is primarely - DESKTOP focused.

This means that I as developer am counting on You to spend Your time on this website from at least some Notebook, prefferably bigger (Desktop PC), normal machine.

This website responsiveness is 100% CSS achieved, with ZERO JS code involvment for that matter. Yes, there's a lot of JS doing various stuff (in fact, only those that should be done with JS), but not - everything .. as it is very common case nowadays, which leads to - overbloat and sloppiness.

If You load it in Your phone, it will all fit nicely, in portrait or landscape, no problem .. hence, some things will be (INTENTIONALLY) smaller or just not perfectly nested, here and there.

INTENTIONALLY because smaller screens are bad for Your eyes, and Your health in general. That's primary reason why one should be using/reading content on websites like a man on a decently big display. Bigger screens are now cheaper and available than ever before, in case You didn't knew. Fact.

The second reason is that there is a lots of documentation on this website. Examples of pseudo source codes, original and working source codes, good old tables and similar content. And if someone finds reading source code on 3.5" display comfortable .. I just can't and won't believe that.

The third reason is: This website is WEBSITE, it is NOT damn APP, nor it will become one, ever. Unless! ... we all get the possibility to view the content on hollographic displays one day, where we can stretch the screen size with our fingers in front of our noses to as much as we need. That would be a game changer.

Copyleft

This website is using Cookies. Indeed. Not grandma' s cookies, but those cookies that are present in a form of digital data since the dawn, wait - since birth of the internet and http protocol. Ok - ALMOST - since than. Look what wikipedia says about cookies ..

.. sick, twisted, throttling, policies and so called standards and similar CRAP, this text is provided to You. It is a better option to have only this kind of explanatory text instead of pop-up elements on page, telling You that There are cold eggs in a functional refridgerator, in case you didn't know., somewhere at the bottom of the page, forcing You to click on Really ?!? Thanks. Stop bugging me !! button somewhere near it.

If we were living in a normal world, this whole text would not be necessary, however, this website is not using cookies for any malicious or similar (tracking, advertising, phishing, spoofing, etc.) purpose.

This website is using OWN cookies (small pieces of data that Your Web Browser Application (Firefox, Chromium, Opera, Chrome, Edge, etc..) is automatically utilizing (default behaviour for any browser)) in order to store info about requests You have made towards this very domain.

To put it out in simpler form, without cookies, this website wouldn't be able to distinguish whether You are here for the first time or You are returning visitor. This website is also using cookies for the sake of the preferred language. English, for example.

In short, without cookies: no checkout, no cart, no online shoppping, no youtube, no gmail, no facebook, no instagram, no pinterest, no twitter login/sign-up - would be possible.

You can delete cookies by Your self, at any time, but they will be recreated again, as soon as possible, automatically. You can disable cookies completely, but in that case, Your experience on this web address would be unknown. Most probably, won't be as I as developer am expecting to be, so don't. Websites MUST use cookies and CAN NOT operate normally without them. Yet.

There are TONS AND TONS of explanations over the internet on the topic: "How can I disable cookies?" for any browser, therefore I have decided NOT to pollute additionally with repeatable `lessons` (I already did, actually, this whole text, right?) so use duckduckgo / yandex / google / bing to find it and read furthermore, wherever you feel it's appropriate.

Local storage

Unlike HTTP COOKIES of which you maybe already read, localStorage is a newer concept, and this website is using it.

It is a browser ( firefox / chromium / opera / edge ) mechanism that stores objects (text-based data) on a client machine (your PC/tablet/uNameIT device in front of you), and nothing on the server.

When the word is about Cookies, both server and client are aware of them, and utilize them. When the word is about localStorage, only client is aware of them and makes some use of them.

Purpose of localStorage is, for example, to persist and to remember the page layout state, so that when You reveal, let' s say aside content via some button on some particular page, next time you visit that page, aside content will remain visible/revealed.

Unlike HTTP Cookies, localStorage has no expiration time limit and server interraction alongside with the client for this purpose is not necessary at all.

In general, localStorage is a very nifty and handy feature which, for example, turns process of building web interfaces (UIX) much more comfortable nowadays. If curious, you can read more about localStorage aka (Web Storage) from wikipedia or from MDN Web API's website.