Navds

ATELIER DU LIBRE 31/08/19: d2d developer tools

What any developer needs in his life:

• an awesome OS: I recommend Ubuntu, Fedora, Arch Linux. Calm down! I just want you to have a dev environment fast. Personalize it.
• A terminal, a real terminal: use either tmux or screen, have guake running in the background.
• a text editor: vim, emacs, gedit, vscode, Atom, etc.. Did I mention VIM already ? PS: Checkout these vim distributions spf13, space-vim, webvim
• an IDE: Eclipse, NetBeans, Anjuta, Code::Blocks,
• search and diff

Navds

<VirtualHost *:80>
    ServerName jenkins.navds.intra
    ProxyPass         /         http://localhost:8080/   nocanon
    ProxyPassReverse  /         http://localhost:8080/

    ProxyRequests     Off
    AllowEncodedSlashes NoDecode

    <Proxy http://localhost:8080*>
      Order deny,allow

Navds

set noautofocus
set nativelinkorder
set showtabindices
let mapleader=','
let hintcharacters="asdgqwertzxcvb"

Navds

Export query result to csv

mysql -hhost -uuser -ppassword database -e "select query" | sed "s/'/\'/;s/\t/\",\"/g;s/^/\"/;s/$/\"/;s/\n//g" > output_file.csv

Navds

Writing Magento Modules

All custom modules should have a Namespace and Module Name. These are used below as {Namespace} and {Module}.

Caution: The Magento autoloader is known to have problems with CamelCase namespaces and/or modules between Windows and *nix systems. If your module requires more than one word for either of these, it is best to just concatenate them to avoid any issues (Example: {Namespace}_{Examplemodule}).

Index

• Directory Structure

Navds

Source: https://magento.stackexchange.com/questions/8344/magento-1-how-to-write-a-custom-extension

• Always develop with error_reporting on.
• Always develop with isDeveloperMode set to true. Just add SetEnv MAGE_IS_DEVELOPER_MODE 1 to your httpd.conf file (or corresponding file for Nginx or something else)
• If the extension is linked to a core functionality add the dependency in the declaration file <Mage_Catalog />
• If the module is for community use, use community as codepool to give the developers the chance to override some classes without modifying the code directly
• Put your frontend design files in app/design/frontend/base/default to make them available for all themes.
• Put your admin design files in app/design/adminhtml/default/default and do not change the admin theme. I may want to change it in one of my modules.
• Prefix your layout file names and template folder name with the company name to make it easier to isolate them. easylife_articles.xml and app/design/.../easylife_a

Navds

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

Navds

// XPath CheatSheet
// To test XPath in your Chrome Debugger: $x('/html/body')
// http://www.jittuu.com/2012/2/14/Testing-XPath-In-Chrome/


// 0. XPath Examples.
// More: http://xpath.alephzarro.com/content/cheatsheet.html


'//hr[@class="edge" and position()=1]'                // every first hr of 'edge' class

Navds

Title: Subversion Cheatsheet CSS : css/cheaters.css

Subversion Cheatsheet

Permalink to Subversion Cheatsheet

| Subversion Resources ||

Navds

Git Workflow

Initial Setup

Initialize a repo

Create an empty git repo or reinitialize an existing one

$ git init