Difference between revisions of "Working on a Styles Bug"

From Dreamwidth Notes
Jump to: navigation, search
(Selecting a Layout for your Journal)
(Working with the Code Locally)
Line 13: Line 13:
 
= Working with the Code Locally =
 
= Working with the Code Locally =
 
This guide is written assuming you have some basic knowledge and familiarity with Linux/UNIX, shells, file systems, etc. To work on styles bugs, you will also need familiarity with CSS and the S2 language. Knowledge of Perl is a bonus but not required (unless you want to work on S2.pm or other modules). If you only have Windows to work on, don't despair! It's possible to work with the repositories through the Windows Explorer, too.
 
This guide is written assuming you have some basic knowledge and familiarity with Linux/UNIX, shells, file systems, etc. To work on styles bugs, you will also need familiarity with CSS and the S2 language. Knowledge of Perl is a bonus but not required (unless you want to work on S2.pm or other modules). If you only have Windows to work on, don't despair! It's possible to work with the repositories through the Windows Explorer, too.
 +
 +
As an alternative, you can do Styles work using a [[Dreamhack]].
  
 
== Getting the DW Code ==
 
== Getting the DW Code ==
  
Create a main working directory for the Dreamwidth source. Most of the instructions on the wiki are tailored to the source directory being <code>~/dw/cvs/dw-free</code> but you can use anything you like. I happen to use <code>~/projects/dw-free</code> .
+
Create a main working directory for the Dreamwidth source. Most of the instructions on the wiki are tailored to the source directory being <code>~/dw</code> but you can use anything you like.
 
+
"Clone", i.e. download and create the dw-free repository:
+
 
+
$ hg clone http://hg.dwscoalition.org/dw-free
+
$ hg update -C tip
+
 
+
Repeat for the non-free repository, which also contains some of the layouts:
+
 
+
$ hg clone http://hg.dwscoalition.org/dw-nonfree
+
$ hg update -C tip
+
 
+
To begin working with Mercurial Queues, execute these commands in each of your DW repositories to initialize the queue repository. For example, if your working directory is <code>~/dw/cvs/</code>, enter:
+
 
+
$ cd ~/dw/cvs/dw-free
+
$ hg qinit -c
+
  
There is more information on working with Mercurial Queues on the Dreamwidth Wiki [[Version_Control#Working_with_patches|here]].
+
You'll next need to follow a subset of the instructions on [[Moving your Dreamwidth installation to use Github]], specifically steps 4 through 8.
  
The S2 layers are located in <code>dw-[non]free/bin/upgrading/s2layers/$layoutname/layout.s2</code>
+
For more on how to use Git for version control, see [[Git Settings]] and [[Git How To]].
  
 
= Generating and Submitting the Patch =
 
= Generating and Submitting the Patch =

Revision as of 16:46, 7 November 2015

Warning: The following information is obsolete, and may quite possibly be incorrect. Obsolete articles are candidates for deletion. Information posted to official communities should be assumed to be accurate. If you have fresh information, please update this article (and remove this textbox!)

This box was added on July 20, 2019.


Selecting a Layout for your Journal

[info]afuna's notes:

  1. claim an issue
  2. get the source code from layer
  3. copy or set up style as necessary
  4. make changes; compile; check in various browsers, or whatever...

Working with the Code Locally

This guide is written assuming you have some basic knowledge and familiarity with Linux/UNIX, shells, file systems, etc. To work on styles bugs, you will also need familiarity with CSS and the S2 language. Knowledge of Perl is a bonus but not required (unless you want to work on S2.pm or other modules). If you only have Windows to work on, don't despair! It's possible to work with the repositories through the Windows Explorer, too.

As an alternative, you can do Styles work using a Dreamhack.

Getting the DW Code

Create a main working directory for the Dreamwidth source. Most of the instructions on the wiki are tailored to the source directory being ~/dw but you can use anything you like.

You'll next need to follow a subset of the instructions on Moving your Dreamwidth installation to use Github, specifically steps 4 through 8.

For more on how to use Git for version control, see Git Settings and Git How To.

Generating and Submitting the Patch

In part 3 of the tutorial, I'll go through the process of claiming and patching a bug step by step.