John David

John David

1611502920

Creative Z-Index Transition Icon Hover Effects | Glassmorphism

Creative Z-Index Transition Icon Hover Effects | Glassmorphism

#web-development #html #css #javascript

What is GEEK

Buddha Community

Creative Z-Index Transition Icon Hover Effects | Glassmorphism
Dylan Iqbal

Dylan Iqbal

1630996646

A Look at an ES2022 Feature: Class Static Initialization Blocks

ECMAScript class static initialization blocks

Class static blocks provide a mechanism to perform additional static initialization during class definition evaluation.

This is not intended as a replacement for public fields, as they provide useful information for static analysis tools and are a valid target for decorators. Rather, this is intended to augment existing use cases and enable new use cases not currently handled by that proposal.

Status

Stage: 4
Champion: Ron Buckton (@rbuckton)

For detailed status of this proposal see TODO, below.

Authors

  • Ron Buckton (@rbuckton)

Motivations

The current proposals for static fields and static private fields provide a mechanism to perform per-field initialization of the static-side of a class during ClassDefinitionEvaluation, however there are some cases that cannot be covered easily. For example, if you need to evaluate statements during initialization (such as try..catch), or set two fields from a single value, you have to perform that logic outside of the class definition.

// without static blocks:
class C {
  static x = ...;
  static y;
  static z;
}

try {
  const obj = doSomethingWith(C.x);
  C.y = obj.y
  C.z = obj.z;
}
catch {
  C.y = ...;
  C.z = ...;
}

// with static blocks:
class C {
  static x = ...;
  static y;
  static z;
  static {
    try {
      const obj = doSomethingWith(this.x);
      this.y = obj.y;
      this.z = obj.z;
    }
    catch {
      this.y = ...;
      this.z = ...;
    }
  }
}

In addition, there are cases where information sharing needs to occur between a class with an instance private field and another class or function declared in the same scope.

Static blocks provide an opportunity to evaluate statements in the context of the current class declaration, with privileged access to private state (be they instance-private or static-private):

let getX;

export class C {
  #x
  constructor(x) {
    this.#x = { data: x };
  }

  static {
    // getX has privileged access to #x
    getX = (obj) => obj.#x;
  }
}

export function readXData(obj) {
  return getX(obj).data;
}

Relation to "Private Declarations"

The Private Declarations proposal also intends to address the issue of privileged access between two classes, by lifting the private name out of the class declaration and into the enclosing scope. While there is some overlap in that respect, private declarations do not solve the issue of multi-step static initialization without potentially exposing a private name to the outer scope purely for initialization purposes:

// with private declarations
private #z; // exposed purely for post-declaration initialization
class C {
  static y;
  static outer #z;
}
const obj = ...;
C.y = obj.y;
C.#z = obj.z;

// with static block
class C {
  static y;
  static #z; // not exposed outside of class
  static {
    const obj = ...;
    this.y = obj.y;
    this.#z = obj.z;
  }
}

In addition, Private Declarations expose a private name that potentially allows both read and write access to shared private state when read-only access might be desireable. To work around this with private declarations requires additional complexity (though there is a similar cost for static{} as well):

// with private declarations
private #zRead;
class C {
  #z = ...; // only writable inside of the class
  get #zRead() { return this.#z; } // wrapper needed to ensure read-only access
}

// with static
let zRead;
class C {
  #z = ...; // only writable inside of the class
  static { zRead = obj => obj.#z; } // callback needed to ensure read-only access
}

In the long run, however, there is nothing that prevents these two proposals from working side-by-side:

private #shared;
class C {
  static outer #shared;
  static #local;
  static {
    const obj = ...;
    this.#shared = obj.shared;
    this.#local = obj.local;
  }
}
class D {
  method() {
    C.#shared; // ok
    C.#local; // no access
  }
}

Prior Art

Syntax

class C {
  static {
    // statements
  }
}

Semantics

  • A static {} initialization block creates a new lexical scope (e.g. var, function, and block-scoped declarations are local to the static {} initialization block. This lexical scope is nested within the lexical scope of the class body (granting privileged access to instance private state for the class).
  • A class may have any number of static {} initialization blocks in its class body.
  • static {} initialization blocks are evaluated in document order interleaved with static field initializers.
  • A static {} initialization block may not have decorators (instead you would decorate the class itself).
  • When evaluated, a static {} initialization block's this receiver is the constructor object of the class (as with static field initializers).
  • It is a Syntax Error to reference arguments from within a static {} initialization block.
  • It is a Syntax Error to include a SuperCall (i.e., super()) from within a static {} initialization block.
  • A static {} initialization block may contain SuperProperty references as a means to access or invoke static members on a base class that may have been overridden by the derived class containing the static {} initialization block.
  • A static {} initialization block should be represented as an independent stack frame in debuggers and exception traces.

Examples

// "friend" access (same module)
let A, B;
{
  let friendA;

  A = class A {
    #x;

    static {
        friendA = {
          getX(obj) { return obj.#x },
          setX(obj, value) { obj.#x = value }
        };
    }
  };

  B = class B {
    constructor(a) {
      const x = friendA.getX(a); // ok
      friendA.setX(a, x); // ok
    }
  };
}

References

TODO

The following is a high-level list of tasks to progress through each stage of the TC39 proposal process:

Stage 1 Entrance Criteria

  • Identified a "champion" who will advance the addition.
  • Prose outlining the problem or need and the general shape of a solution.
  • Illustrative examples of usage.
  • High-level API.

Stage 2 Entrance Criteria

Stage 3 Entrance Criteria

Stage 4 Entrance Criteria

For up-to-date information on Stage 4 criteria, check: #48

  • Test262 acceptance tests have been written for mainline usage scenarios and merged.
  • Two compatible implementations which pass the acceptance tests:
  • A pull request has been sent to tc39/ecma262 with the integrated spec text.
  • The ECMAScript editor has signed off on the pull request.

Download Details:
Author: tc39
The Demo/Documentation: View The Demo/Documentation
Download Link: Download The Source Code
Official Website: https://github.com/tc39/proposal-class-static-block 
License: BSD-3
#javascript #es2022 #ecmascript 

Florida Feeney

Florida Feeney

1625820120

Top Creative Buttons Animation & Hover Effects | Button Hover & Animation Effects

Top Creative Buttons Animation & Hover Effects Button Hover & Animation Effects| Button UI Design

==============================
source code
https://github.com/animationbro/Top-Creative-Buttons-Animation-Hover-Effects01.git

==============================
source code
https://www.youtube.com/watch?v=AXV1wvHXaI8&list=PLeTwji2eGZDrptQ5c1-kA-JRnnYyt3Q59&index=41

https://www.youtube.com/watch?v=A-A8wzpCvuo&list=PLeTwji2eGZDrptQ5c1-kA-JRnnYyt3Q59&index=28

https://www.youtube.com/watch?v=RB1QClYzAbQ&list=PLeTwji2eGZDrptQ5c1-kA-JRnnYyt3Q59&index=24

https://www.youtube.com/watch?v=-16M09DZR5E&list=PLeTwji2eGZDrptQ5c1-kA-JRnnYyt3Q59&index=14

==============================

==============================
contact:
https://www.facebook.com/animation.coding

#animationcoding #webdesign_ac

#hover effects | #creative

John David

John David

1611502920

Creative Z-Index Transition Icon Hover Effects | Glassmorphism

Creative Z-Index Transition Icon Hover Effects | Glassmorphism

#web-development #html #css #javascript

davis mike

1624874259

Generate an Appealing Site Icon for Your WordPress Website

Site icons are not logos. A logo simply represents a brand and could also be used as a site icon sometimes but a site icon could not be converted into a logo. A brand logo is always recognizable even from a notable distance but a site icon can sometimes be complicated and need not represent your business identity essentially. Instead, it represents your business nature most of the time. For example an hourglass icon for a time-based website, a graduation icon for an educational website, a notes icon for a reminder website or program. You can make use of your coding skills to showcase the site icons you’ve selected for your site. You can then add corresponding codes to your site’s header. That’s it, you’re ready with your WordPress website icons. Read more on https://bit.ly/3x0VllD

#site icon #site icon designing #site icon design #wordpress website #website icon design #wordpress website icon design

DCODE SHOW

DCODE SHOW

1597918433

Social Icon Hover Effect in CSS | Floating Social Media Icons CSS

https://youtu.be/qOdMZeOVbQA

#social media icons html #css #html #how to create floating social media icons in html