CodePen is a playground for the front end side of the web. It's all about inspiration, education, and sharing.
1) 101 will be maintained to minimize overlap with vanilla JS.
- 101 utils are made to work well with vanilla JS methods.
- 101 will only duplicate vanilla JS to provide functional programming paradigms or if the method is not available in a widely supported JS version (currently ES5).
- Underscore/lodash - duplicates a lot of ES5: forEach, map, reduce, filter, sort, and more.
2) No need for custom builds.
- With 101, import naturally, and what you use will be bundled.
- Each util method is a module that can be required require('101/<util>').
- Currently node/browserify is supported, I will add other module system support on request.
- Underscore/lodash is large, and you have to manually create custom builds when if you're trying to optimize for size.
Here is set of charts demonstrating the paths that you can take and the technologies that you would want to adopt in order to become a frontend, backend or a devops
Overscroll is a jQuery Plugin and polyfill for mobile safari's overflow-scrolling style. It is intended for use on desktop browsers, with the latest version of jQuery. Demo
5 Great Snacks For the Coder’s Brain
Zepto is a minimalist JavaScript library for modern browsers with a largely jQuery-compatible API. If you use jQuery, you already know how to use Zepto.
While 100% jQuery coverage is not a design goal, the APIs provided match their jQuery counterparts. The goal is to have a ~5-10k modular library that downloads and executes fast, with a familiar and versatile API, so you can concentrate on getting stuff done.
npm install zepto
ASP.NET 5 beta7 is now available both on NuGet and as a tooling update to Visual Studio 2015! This release also includes the first public preview of the .NET Execution Environment (DNX) for Mac and Linux based on .NET Core – no Mono required.
Today we are thrilled to announce the release of OpenSilver 1.0
As Silverlight is reaching end of support, OpenSilver is now powerful enough to run complex line-of-business applications of all sizes.
مانند مثال بالا می‌توانید به سطوح جزییات گزارش خود بیافزایید. به طور مثال مدل‌های زیر را در نظر بگیرید:
public class CustomerServiceReport
{
public string ReportTitle { get; set; }
public string ReportDate { get; set; }
//...
public List<CustomerRow> Customers { get; set; } = new List<CustomerRow>();
}
public class CustomerRow
{
public int CustomerId { get; set; }
public string CustomerName { get; set; }
public string Phone { get; set; }
//...
public List<ServiceRow> Services { get; set; } = new List<ServiceRow>();
}
public class ServiceRow
{
public int ServiceId { get; set; }
public string ServiceName { get; set; }
public int Count { get; set; }
public long Price { get; set; }
} که در فایل mrt مربوط به گزارش به صورت زیر پیاده‌سازی می‌شود
در برنامه هم به صورت زیر دیتای مورد نیاز گزارش - به صورت نمونه - ایجاد می‌شود و در انتها با استفاده از RegBusinessObject و SynchronizeBusinessObjects به گزارش ثبت و ارسال می‌گردد.
var data = new CustomerServiceReport
{
ReportDate = "1399/09/04",
ReportTitle = "گزارش سرویس‌های مشتریان"
};
for (int i = 0; i < 5; i++)
{
var customer = new CustomerRow
{
CustomerId = i + 1,
CustomerName = $"مشتری شماره {i + 1}",
Phone = "001122"
};
for (int j = 0; j < 3; j++)
{
var service = new ServiceRow
{
ServiceId = j + 1,
ServiceName = $"سرویس شماره {j + 1}",
Count = (j + 1) * 10,
Price = (j + 1) * 10000
};
customer.Services.Add(service); //اضافه کردن سرویس به هر مشتری
}
data.Customers.Add(customer); // اضافه کردن مشتری به گزارش
}
var report = new StiReport();
report.RegBusinessObject("CustomerServiceReport", data);
report.Dictionary.SynchronizeBusinessObjects(); 
Bridge Network Driver
The bridge networking driver is the first driver on our list. It’s simple to understand, simple to use, and simple to troubleshoot, which makes it a good networking choice for developers and those new to Docker. The bridge driver creates a private network internal to the host so containers on this network can communicate. External access is granted by exposing ports to containers. Docker secures the network by managing rules that block connectivity between different Docker networks.
Overlay Network Driver
The built-in Docker overlay network driver radically simplifies many of the complexities in multi-host networking. It is a swarm scope driver, which means that it operates across an entire Swarm or UCP cluster rather than individual hosts. With the overlay driver, multi-host networks are first-class citizens inside Docker without external provisioning or components. IPAM, service discovery, multi-host connectivity, encryption, and load balancing are built right in. For control, the overlay driver uses the encrypted Swarm control plane to manage large scale clusters at low convergence times.
MACVLAN Driver
The macvlan driver is the newest built-in network driver and offers several unique characteristics. It’s a very lightweight driver, because rather than using any Linux bridging or port mapping, it connects container interfaces directly to host interfaces. Containers are addressed with routable IP addresses that are on the subnet of the external network.
As a result of routable IP addresses, containers communicate directly with resources that exist outside a Swarm cluster without the use of NAT and port mapping. This can aid in network visibility and troubleshooting. Additionally, the direct traffic path between containers and the host interface helps reduce latency. macvlan is a local scope network driver which is configured per-host. As a result, there are stricter dependencies between MACVLAN and external networks, which is both a constraint and an advantage that is different from overlay or bridge.
