Jump to content
  • Articles, Guides and News

    Our website articles, guides and news

    macOS Catalina 10.15.4 is out

    Released March 24th, 2020.
     
    Watch out folks as this update can be problematic on Skylake and later platforms. Update Lilu + WEG kexts to latest available versions and Clover to r5107 before initiating the update. If you cache your kexts from /L/E (or /S/L/E), remember to also update the kexts in the E/C/k/O of your EFI partition as the temporary update partition boots only with kexts injection. Faking a different CPUID should no longer be required but boot parameters -lilubetaall and/or -disablegfxfirmware may be so until the update has fully completed.
     
    I've also noticed that 10.15.4 no longer supports XCPM on my Ivy Bridge laptop (Latitude E6230) so it's back to generated CPU power management SSDT + AICPUPM patch.
     

     

     

     
     
    At the same time Safari 13.1 + Security Update 2020-002 were released for Mojave 10.14.6 and HIgh Sierra 10.13.6.
     
     Warning to all those who run Catalina on officially unsupported graphics platforms (eg: 1st gen Intel HD, Intel HD3000, nVidia Tesla), the patches/tricks previously used to gain OpenGL-only graphics acceleration no longer work in 10.15.4. As such, stick to 10.15.3 for the time being!
     
     
    Edit: April 8th, 2020
    - - - - - - - - - - - - - -
    Unsurprisingly, Apple issue a 10.15.4 Supplemental update today. This brings 10.15.4 to Build 19E287. Looks safe to install on all systems running Clover r5107. Had trouble on Latitude E6230 running with Clover r5108 (and reverted to r5107).
     

     

     

    macOS Catalina 10.15 is out !

    Following the release of GM version a few days ago, Catalina 10.15 was released Monday October 7th, 2019.
    https://www.apple.com/macos/catalina/
     
    Build is 19A583. It is available off the AppStore for download. Those who run on beta versions through the beta enrolment program should probably 1st revert to default mode before attempting to download as the new macOS version may not be otherwise be offered.
     

     

     

     
    Our 1st few guides have just stared to roll in so we invite everyone to bring in their new contributions.
     

    Custom styling your signature on OSXL

    Hey community!
     
    As you all might know we underwent a massive upgrade from our old forum to this new one. After the upgrade you might have noticed that signatures aren't that well visible. They look completely out of the place and are a total mess to look at.
     
    So, after tuning up our site and handling the core things, I have managed to take out some time today and was toying around with the web developer tools in Chrome.
     
    I wanted my signature to look a bit different and more stylish. As you can see, it also has some fancy animation once you hover over it. You can look at the source code for my signature by inspecting the element.
     
    Here's how you can apply custom CSS3 styling to your signature:
    Navigate to "Account Settings" from the user settings drop down menu (top right).  
    Select "Signature" section.  
    Now you need to change to source code mode as default IPS WYSIWYG is a headache when it comes to styling. Plus the CK Editor we get in Signature's section is very slimmed down (features removed).  
    To change to source mode you need to click on the source button on the editor's toolbar. Here's a visual reference: Once you switch to the source code mode, the first thing you wanna do is put your signature in the center of the screen. You can also use css but using a <center> tag of HTML would be more handy. Now, by default IPS uses span element to store your signature and span is not that friendly when it comes to animating it. The first thing you wanna do is use a div tag to store your signature and give it a custom unique ID. Like, <div id="myUniqueID"> This is a sample signature </div>  
    Here the id of our div element is myUniqueID. We will be using this ID in our CSS to style this element.  
    Now, here's the problem, once you use a div tag, your signature will take up the whole place overlapping with some controls in the signature are. Hence, it is a must to use a max-width property to circumvent this issue.  
    So, here's the basic bare bones syntax of a typical custom signature: <center> <style type="text/css"> /** Styling for our custom div element goes here **/ </style> <!-- Declare a div tag with custom ID --> <div id="myUniqueID"> This is a sample signature </div> </center>  
    Now, I'm gonna provide an other copy and paste code that shows how to control your signature's element using CSS (for noobs) <!-- Source code for Nick's signature on OSXL --> <center> <style type="text/css"> /* Styling for the root DIV tag */ #myUniqueID{ /** This will control your signature's text appearance **/ } /* Optional if you wanna do something when cursor is hovered (try hovering my signature) */ #myUniqueID:hover{ /* Code goes here */ } </style> <!-- Now we are just going to create a div element with our custom tag --> <div id="myUniqueID"> Please be kind to others. Help us to help you. </div> </center>  
     
    That's all that you need to know.
     
    Here's an advanced example of how to use custom code for signature.
    This is the current source code for my signature. If you have any doubts you are free to ask me about it.
     
    <center> <style type="text/css"> /** Custom animation to shake an HTML element using CSS **/ @keyframes shakeSign { 0% { transform: translate(1px, 1px) rotate(0deg); } 10% { transform: translate(-1px, -2px) rotate(-1deg); } 20% { transform: translate(-3px, 0px) rotate(1deg); } 30% { transform: translate(3px, 2px) rotate(0deg); } 40% { transform: translate(1px, -1px) rotate(1deg); } 50% { transform: translate(-1px, 2px) rotate(-1deg); } 60% { transform: translate(-3px, 1px) rotate(0deg); } 70% { transform: translate(3px, 1px) rotate(-1deg); } 80% { transform: translate(-1px, -1px) rotate(1deg); } 90% { transform: translate(1px, 2px) rotate(0deg); } 100% { transform: translate(1px, -2px) rotate(-1deg); } } /* Styling for the root DIV tag */ #nicksSign{ color: wheat; font-size: 15px; font-family: monospace; max-width: 500px; margin-bottom: 5px; background: #5f32e5; padding: 2px; -webkit-font-smoothing: subpixel-antialiased; box-shadow: 5px 5px 12px 0px rgba(0,0,0,0.75); cursor: default; /* Prevent cursor from turning into a text selector */ user-select: none; /* Make it non-selectable */ } #nicksSign:before { content: attr(data-hover); opacity: 0; position: absolute; } #nicksSign > span { transition: all 1s; } /* Animate only when hovered */ #nicksSign:hover{ animation: shakeSign 2.5s ease-in-out infinite; } #nicksSign:hover span { opacity: 0; transition: all 1s; } #nicksSign:hover:before { opacity: 1; transition: all 1s; } </style> <div data-hover="Thankyou for being here. Greetings from OSXL!" id="nicksSign"> <span>Please be kind to others. Help us to help you.</span> </div> </center>  
    Lets us know in comments if you have any questions with you custom signature.
     
    Welcome to new new era of Signatures at OSXL!
     
    Regards
    OSXL
     
    Please note: Funky signatures are strictly prohibited and are not allowed.
×
×
  • Create New...