Does front end developer need to know anything except of __HIS_FAVORITE_FRAMEWORK_HERE__ ?
Nicholas Zakas is talking about basic principles of scalable [Web] application architectures:
While this talk was made in 2013 it is still 100% applicable to modern Web and Sciter (desktop) applications.
Practical investigation on effectiveness of Virtual DOM (React) updates versus direct DOM updates (Vue).
Clearly React takes significantly more CPU time for the task of updating 100 items list.
That proves once again that there is no silver bullet in Web Front End design. Each task has its own optimal framework/architecture.
“Ideal framework” should allow to use multiple paradigms – list-of-items view should use virtual list, it could be one-way bound with data [model] and item-details may or may not be data bound – depends on its structure.
What if just start from our old friend jQuery with its system of plugins and/or components/modules architecture of Twitter’s Flight.
Where you can add view routing, data bound lists and other plugins of your choice? Only when and where they are needed …
Is it close to that optimal, flexible and stable architecture web applications we are dreaming of?
I have found Maintainable CSS site exceptionally useful for designing maintainable CSS systems.
Modular and encapsulated: Styles don’t bleed or cascade without your permission.
Any design requirements: Completely flexible to your needs.
No tooling required: But you can use tooling if you want to.
Easy to learn: Read the guides and see.
Any size project: Whatever size project you have, MaintainableCSS will help.
Upgrade in your own time: You can start applying the approach today, bit by bit. You don’t need to upgrade the whole
Disclaimer: the game is quite dangerous and may lead to alcoholism of participants even after first game. Play responsibly!
Idea of the game:
Players, in their turn, name random English word. To this word they add “JS” or “.JS” suffix and go google for it.
If google will give JS library or framework with that name – you won and drink one Vodka shot.
You’ll be surprised… and read disclaimer above.
25 or so years ago we were designing one accounting application that required intensive input of numbers by operators.
That was in Russia at the time when personal computers were just appearing in offices massively.
Amount of numeric data that operators needed to input was enormous and as in any financial institution the requirement for correct input was very high.
Operators were quite professional and were doing very fast blind input by hands at the time when their eyes were focused on paper sheets with data.
In order to help them to verify their input I invented and implemented “musical” verification. When focus lefts numeric field, the application is playing melody where each digit has its own tone. I was surprises how effective it happened to be. At the end of first day operators were able to determine at least number of digits filled and after some time some of girls were even able to tell exact number by only hearing the melody.
After 6 years Sciter Engine finally got its own home : sciter.com.
The site is not complete though, I am still working on content, documentation in particular. The plan is to combine in one place stuff that was spread across many sites and blog articles.
Forum users are advised to re-register on Sciter’s new forum at sciter.com/forums/ hope you will find it more comfortable.
Note #1: we have changed Sciter prices.
Note #2: Sciter’s versions RSS channel is here, please update your links.
Mr Ramon F. Mendes have published his Omni tools that allow to use Microsoft Visual Studio to design markup and Sciter specific code:
I’d recommend to give a try to this great tools, you will love them!
Never tried acrylic paints before, and here we go:
It’s naïve of course but reflects my mood at that sunny day on Westcoast.
I am adding zip resource packaging support to Sciter v. 18.104.22.168.
Imagine that you have some folder where your app files are located:
content images img1.png img2.png scripts script1.tis styles style1.css index.htm view1.htm dialog.htm
then you can load it into the Sciter using …/content/index.htm path. Nothing new up to this moment.
But with ZIP packaging support you can compress that folder into single content.zip file and load that zip into the engine as a whole using …/content.zip url.
Sciter will unzip that archive on the fly and will try to find and load either one of following files at its root: index.htm, index.html, main.htm or main.html.
All relative links inside that file will be resolved against content of the zip. So if you have <img src=”images/img1.png”> then its URl will be resolved to artificial
…/content.zip/images/img1.png and the image will be loaded from the zip.
Given schema allows to use same content in a folder or as packaged into zip file without any changes.
Among other use cases consider zip packaging for downloading applications over the wire – it will minimize bandwidth and eliminate multiple http connection requests for resources of the application.