HTML 5 - efecte vizuale uimitoare

Se pare ca zilele in care se folosea Photoshop la greu pentru a crea efecte pe paginile HTML incep sa apuna. Java Script impreuna cu HTML 5 ofera posibilitatea de a face efecte vizuale pe care acu 2-3 ani doar le puteam visa.
Hai sa va dau si un exemplu: http://www.nevermindthebullets.com/
Este un site de benzi desenate. Nimic deosebit pana acuma. Dar daca ne uitam in codul HTML o sa observam ca foarte multe efecte vizuale la imagini sunt facute prin intermediul la Java Script.
Cum s-a ajuns la aceasta performanta? S-a inceput de la niste imagini in format PNG, care pot sa fie transparente sau "decupate". Prin acest mecanism se permite suprapunerea de imagini ca si in Photoshop( layer). Fiecare element din imagine este o imagine separata. Dar pe langa atributele normale care le putem gasi pentru tagurile HTML precum img sau p o sa observat niste atribute noi precum: cp:x, cp:ballon sau cp:text. Aceste atribute custom, prefixate cu cp pe care le-a introdus creatorul sitului nu sunt procesate de catre brower deoare nu sunt valide. Dar reprezinta un mod inedit de a pastra meta-date precum pozitie pe o anumita axa, fond type, efectul care sa existe pe tagul respectiv.

<p class="Balloon" cp:text="Little" cp:balloon="Tell" style="left: 74px; top: 35px; width: 280px; position: absolute">
   He's come to the west; the land of opportunity.
</p>
<img class="Layer" style="left:-444px; top:-75px" src="soif-2.png"  cp:y="100" cp:x="600" />

Dar fiecare din aceste atribute sunt prelucrate de catre Java Script care adauga anumite efecte speciale. Toate aceste efecte speciale le puteti gasii in parallax.js.
Daca vreti sa aflati mai multe puteti sa intrati aici.

Comments

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users. This information might be useful in the future when we need to decide where we want to keep and manage our users. Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

Cloud as a Story - Vunvulea Radu

Search This Blog