#ClientSide

[oivoodoo]

html5 offline application

2 days ago I've lost my internet connection at home. But I had very important emails for me on the gmail. But I thought I have offline application for gmail developed by google.

I've installed this chrome app just for checking possible implementation for offline apps. because on my current work we are working on the creation with the same functionnality application. Offline gmail is using web sqlite storage for saving cached / synced data.

it looks like

Time to completely client side applications. Yeah, it's really awesome. But for less complex applications it's pretty simple to use localStorage for saving synced data.

Also as I see guys in google added syncing process on the background and refresh button for manually syncing by user action. 

For opening application they are using html5 application manifest for caching resources like css/js/images. In Rails we are using rack-offline for generating same manifest file choosing files for caching.

[justphilll]

Most Client side would be better done server side?

Favouring jQuery over server side programming

jQuery is for web designers turned developer vs. Server side programming

.net used to have a heavy view state footprint but has a much smaller one but for speed it could be less memory intensive for high traffic websites

some jQuery is used out of habit creating a massive client dependency when a trip to the server could increase performance and security (especially with scraping that activates Javascript)? Also, there are server side cases if in increasing performance through caching.

[devalias]

MDwiki (and how to get started)

(Note: Original gist can be found here)

If you haven't already heard about it, MDwiki is a cool little CMS/Wiki that runs entirely clientside (HTML5/Javascript) and uses Markdown

Since it's all clientside, we can do really cool things like track our changes in git and then host it all on GitHub Pages. That means super simple forking, contributing and sharing. Yay for open source!

Setting up MDwiki with GitHub

There is an official guide available on the MDwiki site, but I kind of like to do things my own way, so below is how I go about setting up a new site. (I'll assume you're already setup on GitHub and know vaguely how to use it, if not, maybe checkout the guide above)

On GitHub

Create a new repository and name it what you want (eg. my-mdwiki)

Setup initial MDwiki bits

Download the latest MDwiki release

Extract it to a folder (eg. my-mdwiki)

Here you have a choice:

mdwiki.html will give you MDwiki and all of it's libraries packaged as a single file

mdwiki-slim.html (my preference) will give you MDwiki, but load it's libraries from a CDN (content delivery network)

Choose the option you want to use and rename it to index.html

Next we'll need to create a config.json file. You can read about how this works or just use something similar to mine:

{ "useSideMenu": true, "lineBreaks": "gfm", "additionalFooterText": "By <a href='http://www.devalias.net/'>Glenn '/dev/alias' Grant</a><br />", "anchorCharacter": "¶", "title": "My Shiny New MDwiki" }

Almost there, create a quick navigation.md (docs) that looks something like

# Your wiki name [Home](index.md) [About](about.md) [Download](download.md)

And create your first page (i'll only show you one, but the process is the same). Create a file called index.md (as specified in your navigation)

# Hello World! This is my first page!

That's it for the basic site setup!

As a little bonus, I like to add a script to run a python SimpleHTTPServer for local testing called run-pyserver.sh (and make sure to make it executable with chmod +x run-pyserver.sh)

#!/bin/bash open http://localhost:8000 python -m SimpleHTTPServer 8000

Now we'll setup our git repo:

Open a terminal window, and navigate to the folder you just created (eg. cd ~/my-mdwiki)

Initialise the git repo: git init

Here we use some magic (from Sean Estabrooks) to tell git to call the initial branch gh-pages instead of master: git symbolic-ref HEAD refs/heads/gh-pages

Add all the files we've created so far: git add .

Commit them: git commit -m "Initial Commit"

Add your GitHub repo as a remote (making sure to replace YOURUSERNAME with your actual username, and my-mdwiki with the name of the repository you created earlier): git remote add origin git@github.com:YOURUSERNAME/my-mdwiki.git

Then push it to github: git push -u origin gh-pages

That's pretty much it! After a short delay, your site should be available at http://YOURUSERNAME.github.io/my-mdwiki

[apponward]

Server-Side vs. Client-Side Rendering: Understanding the Key Differences

In the realm of website development, rendering plays a pivotal role in how content is displayed and interacted with by users. Two fundamental approaches to rendering, namely server-side rendering (SSR) and client-side rendering (CSR), have emerged as cornerstones in the modern web development landscape. 

Each method has its own set of advantages and considerations, making it essential for developers to discern which approach best suits their project’s requirements. This article delves into the intricacies of server-side and client-side rendering, shedding light on their disparities, benefits, and real-world applications.

Read more: https://apponward.com/blogs/server-side-vs-client-side-rendering-understanding-the-key-differences/

[bigscal-technologies]

What is Client side and Server side DataTables processing?

Get complete details by clicking this link

[laravelvuejs]

GoLang,VueJS – WebApp series [010] – Client-Side JWT Authentication Logins, Routing, Basic App In this video, we will be doing client-side JWT! I go kind of fast ... source

[aiksol-blog]

Swipe right to know the magical powers of JavaScript! #javascript #clientside #serverside #development #machinelearning #mobileapps #progressivewebapps #wednesdayvibes #aiksol https://www.instagram.com/p/CBh8Sn1h6eK/?igshid=17l5x7oa9eu30

[fazellnasiri-official]

Client-Side Script VS Server-Side Script. What’s the difference between them? - ☝️Which side do you work?😎 - #client #clientside #server #serverside #php #ruby #python #c #java #ASP #javascript #html #css #development #developer #programming #design #designer https://www.instagram.com/p/B_wXQA9H2Rp/?igshid=1xq5ukii5lyxn

[ronbhatkar]

client-side beside7 #ronbhatkar #rohanbhatkar #clientside #officeoffice #horriblebosses #officefun #firstdayofnewyear #workworkwork (at Labdhi Lifestyle Limited) https://www.instagram.com/p/B6x-X8cnv4U/?igshid=asxe21nd6mqp

[solutelabs]

Client-side rendering vs. server-side rendering based on performance, SEO & caching. Find out the pros and cons of client-side & server-side rendering with examples.

[black-tambourine-au]

React JS.NET - clientside errors with  Webpack

If you are using using React JS.NET versions 3 or 4 in combination with Webpack 4 and Babel you will may come across an error where a serverside rendered component will not have working events on the clientside. In this scenario the @Html.ReactWithInit() function is not rendering the ReactDom.Hydrate clientside script. A workaround is to use script initialisation per component rather than a global one for all components. So rather than using @Html.React() to place a component in a MVC View i'm using @Html.ReactWithInit(). The only other difference is that your React and clientside javascript needs to be declared in your document head (i.e. before your components). A lot of the examples online for ReactJS.Net are out of date and use Webpack 1 (such as https://github.com/reactjs/React.NET/tree/master/src/React.Sample.Webpack), so keep this in mind when setting up a new project.

[anh-dinh]

Hello! #clientside (at BBDO San Francisco)

[health1760-blog]

Adobe Dreamweaver And Client-side Content

Adobe Dreamweaver And Client-side Content

Adobe Dreamweaver is a multi-purpose web development device aimed at inexperienced and experienced users alike. It makes use of standards-compliant web technologies like XHTML and CSS. Site content are brought in into the Dreamweaver at any time without the danger of this program changing your rule. Just as, pages developed in Dreamweaver is shipped from Dreamweaver environment and made use of…

[cool-gadgets-guide]

N Brown Group plc calls in Namogoo to protect customers from new ‘invisible’ threat of Client-Side Injected Malware

N Brown Group plc calls in Namogoo to protect customers from new ‘invisible’ threat of Client-Side Injected Malware

Media enquiries to: Lucy Heather, LHJ Media Limited, lucy@lucyheather.com +44 (0 )7789 485 372 Eric Woollard-White +44 (0) 7584 436 369 N Brown Group plc, the leading multi-channel specialist-fit fashion retailer, has signed a deal with cyber-security start-up Namogooto provide customer protection against the growing threat of Client Side Injected Malware (CSIM). CSIM is a relatively new but…

[didagency]

FROM CLIENT TO AGENCY

I’ve been fortunate throughout my career to have worn many hats. In both my educational and professional aspirations I have tackled many sides within the same industry. I worked client side with Johnson & Johnson as an Associate brand manager which is where I was first exposed to DiD. After a brief hiatus from the pharmaceutical industry, I started back working on contract with The Luminations Group, which was founded by a former Johnson & Johnson marketer. There I did work for Valeant Pharmaceuticals who was also a DiD client, and again was in contact with the DiD team. We worked well together which led me to start working on projects for the strategy department at DiD. Having worked on the client side for various pharmaceutical companies with several brands, and working with DiD as a client, I believe I bring a unique perspective to the team.

Having sat on both sides of the fence, I can say there are some key differences and disconnects that exist between clients and agency partners.

When you are on the client side, you don’t always understand everything that goes into the creative process.  For example, when you are presented a creative brief, you don’t see how many people have touched it, and how many hours have been spent on it before it makes its way to you. Until you are on the agency side working through a project, having hour long conversations, and hashing things out, it is not something that is in the forefront of your mind. Clients may not realize the strategic rigor that goes into every deliverable, how each and every detail is given the utmost consideration.

On the opposite side of that is the client, and working with the agency is just a fraction of their day. The client also has to juggle financial demands, manufacturing logistics, R&D and budget, all of which can create a very high stress environment. This is something which we as an agency don’t see but is important to understand. Another major stress factor is the direction the business may be moving, increasing or decreasing sales can have a great impact on the client’s mindset and stress level. There is a slew of pressures on the client’s side that the agency will never have to deal with—but an agency’s perceptivity in this area can aid in fostering better relationships with clients.

Overall, both the client side and agency side are filled with their own challenges, it is when both sides come together that we are truly able to create something meaningful. At the end of the day, no matter what side of the fence that you are on, it is nice to know that all of the hard work and all of that passion can truly impact a consumer’s life-- that we are able to educate consumers and bring some relief into their lives. 

Nurit Bloom

Strategy Consultant