Learn and Share

Try in Editor: https://codepen.io/jemirisselvi/pen/YzKQxmw?editors=1010 Vue:   <div id="app">     <v-app id="inspire">       <div>         <v-data-table           :headers="headers"           :items="items"           :search="search"           :loading="isLoading"           hide-default-footer           item-key="name"           class="elevation-1"         >           <template v-slot:body="{ items }">             <tbody>               <tr v-for="(item,index) in items" :key="item.name">                 <td>                   <p @mouseover="item.show = true" @mouseleave="item.show = false">                   {{ item.name }}                   <v-icon v-show="item.show">delete</v-icon>                   </p>                 </td>                 &

Try in Editor: https://codepen.io/jemirisselvi/pen/yLBXoxK?editors=1010 Vue: <div id="app">   <v-app id="inspire">     <div>         <v-data-table           :headers="headers"           :items="items"           :loading="isLoading"           class="elevation-1"         >         <template slot="items" slot-scope"myprops">           <td v-for="header in headers">             {{ myprops.item[header.value] }}           </td>          </template>       </v-data-table>     </div>   </v-app> </div>

Adding an existing project to GitHub using the command line Create a new repository  on GitHub. To avoid errors, do not initialize the new repository with  README , license, or  gitignore  files. You can add these files after your project has been pushed to GitHub. Open  Git Bash . Change the current working directory to your local project. Initialize the local directory as a Git repository. $ git init Add the files in your new local repository. This stages them for the first commit. $ git add . # Adds the files in the local repository and stages them for commit. To unstage a file, use 'git reset HEAD YOUR-FILE '. Commit the files that you've staged in your local repository. $ git commit -m "First commit" # Commits the tracked changes and prepares them to be pushed to a remote repository. To remove this commit and modify the file, use 'git reset --soft HEAD~1' and commit and add the file again. At the top of your GitHub repo

To add html to an EXTJS panel after it has been rendered you can use. Ext.getCmp(''the I.D of your panel'').body.update(''your HTML"); new Ext.Panel({             border: false,             frame: false,             width: 200,             region: 'west',             id: 'panel-id',             bodyStyle: "background: #fff"         } //and I want in another module change panel content... so use this: Ext.getCmp('panel-id').body.update('html content for example'); Example 2: {     xtype: 'panel',     title: 'Testing',     id: 'taskpanel',     html: 'testing' } //to update the panel content. For html use body.update 3 Ways to render HTML inside of a ExtJS container Ext.onReady(function() {     new Ext.Panel({         renderTo: Ext.getBody(),         title: '3 Ways to render HTML inside of a ExtJS container',         items: [{             html: &quo

1. How to rename folders in Linux ============================ mv command syntax form is as follows: ---------------------------------- mv old-name new-name mv [options] old-name new-name mv [options] source target 2. How do I delete multiple lines in nano without affecting the clipboard? ====================================================================== nano of course can delete blocks, see this article😊 use CTRL+Shift+6 to mark the beginning of your block move cursor with arrow keys to the end of your block, the text will be highlighted. use CTRL+K to cut/delete the block. To paste the block to another place, move the cursor to the position and the use of CTRL+U . You can paste the block as often as you want to.

Error : Installation failed, deleting ./composer.json. The following exception is caused by a lack of memory or swap, or not having swap configured Check https://getcomposer.org/doc/articles/troubleshooting.md#proc-open-fork-failed-errors for details Follow Below steps: ====================== Troubleshooting# This is a list of common pitfalls on using Composer, and how to avoid them. General# Before asking anyone, run composer diagnoses to check for common problems. If it all checks out, proceed to the next steps. When facing any kind of problems using Composer, be sure to work with the latest version. See self-update for details. Make sure you have no problems with your setup by running the installer's checks via curl -sS https://getcomposer.org/installer | php -- --check. Ensure you're installing vendors straight from your composer.json via rm -rf vendor && composer update -v when troubleshooting, excluding any possible interferences with ex