google'code fully supporting mercurial repositories

2.7: proj.addn/net.g'code/getting started with hg repository:

booking

. before figuring out that I could use hg instead of svn,
I did try the [Reset This Repository] for the addx project:
"(

Did you just start this project
and do you want to 'svnsync' content
from an existing repository into this project? yes:
Warning:
Resetting the repository will delete
everything in the repository and its history.
This includes project wiki files.
Reset this project's Subversion repository
from revision 1 to revision 0.
A project owner can then use the svnsync tool to upload existing code history.

)
. Mercurial an option for all yet? yes:
"(

Convert your project from Subversion to Mercurial
http://code.google.com/p/support/wiki/ConvertingSvnToHg
1. Go to project/Administer tab/Source tab
[eg, mine is https://code.google.com/p/addx/adminSource]
2. Change the repository type to Mercurial
parameters:
* Root directory: /
* Trunk directory: /trunk
--[ change this to empty because my current repo
is empty so /trunk doesn't exist .]

)
. all projects were converted to hg repo's:
for add* in {addx, adda, adde, addm}:
https://code.google.com/p/add*/adminSource
default: https://add*.googlecode.com/hg/
wiki: https://wiki.add*.googlecode.com/hg/

. now the source page confirms I'm with hg:
get a local copy of the add* repository with this command:
hg clone https://add*.googlecode.com/hg/ add*

easy downloads
. use the Downloads tab to upload compressed files.
(eg, mine is https://code.google.com/p/addx/downloads/entry)
. choose the file names carefully
as you cannot change it later. [except by deletion]
[. the downloads could be
the easiest way for everything:
. doing doc's by wiki is ok on a netbook,
but if you have a prefered html editor,
the best way by far to distribute doc's
is to simply zip the folder structure into
one downloadable book .
. if working alone, then this is the way to
keep your source code in any repo system you want
(eg, you could migrate from hg to git);
however, the problem with monolithic downloads
is not being able to update them incrementally:
it gets expensive on bandwidth
to re-upload the entire thing for each revision .]
todo:
. predefined download labels useage
was a mystery to me for now ...
https://code.google.com/p/addx/adminDownloads
[2.28: perhaps becomes obvious during an upload .]

todo: [2.28: done] uploading to g'code with a gui
. there is a how-to for using TortoiseSVN,
it needs to be adapted for use with Tortoisehg ....
[2.28: done with the help of tortoiseHg tutorial]
"(
. find your google'code ID in your project's home page,
eg, for project addx, home is:
https://code.google.com/p/addx/
at the bottom it tells the owner's name:
-- mine's dr.addn, as seen here:
https://code.google.com/u/dr.addn/
. to find your assigned g'code password
see g'code's "Settings" tab .
. In Windows explorer, [on the mac? try vmware]
right click in your repo' directory's context menu,
and choose TortoiseHg/Repository Settings/Sync.tab/add.button
and then the dialog is obvious about filling in
your g'code hg repo contact details:
( URL: https://addx.googlecode.com/hg/ (for the addx project)
, user: dr.addn
, password: (see http://code.google.com/hosting/settings)
)
. now to do the uploading to your hg repo' at g'code,
right click n your local repo' directory's context menu,
to get TortoiseHg/Synchronize .
. the dialog will have a line that says:
[repo:][bundle:][(repo' pull-down menu)] post pull:[(pull-down menu)]

. when you pull down the [(repo' pull-down menu)]
you will see the contact details you filled in during
context`menu/TortoiseHg/Repository Settings/Sync.tab/add.button
mine looks like this:
https://dr.addn:***@addx.googlecode.com/hg/
(the *** represents the password you entered) .
. select it to make it show in the menu .
. now at the top of the dialog is the push.button;
ie, a button that launches the Push command;
pushing your local repo's state into your g'code repo .

tortoiseSVN is still there
. here's a google-authored page for
using g'code with tortoise svn instead of hg .
. it recommends an svn client for mac too .
(zigversion.com)
[2.28: I'm using tortoiseHg on the mac via vmware
which allows windows to run in a mac window .]

svn on g'code

6.18: g'code/how to add code:

your source repository:

http://code.google.com/p/support/wiki/GettingStarted

1. For instructions on how to check out a project's repository

from the command line, go to the Source tab.

Any user, regardless of whether they have a Google account,

can check out and browse the repository anonymously,

while project owners and members are granted full read and write permissions.

You can add project owners and members at the Administer tab.

2. If you plan on synching from an existing repository,

you must click the Reset This Repository link

at the bottom of the Source tab page

before making any other changes to your project's repository.

This includes creating any new wiki pages

because resetting the repository results in the loss of wiki content.

Do not start a wiki page in your project before you complete this step.

. on the source tab`page it says this:

New project? You can reset this repository

so that svnsync can be used to upload existing code history.

Command-Line Access

If you plan to make changes,

use this command to check out the code as yourself

svn checkout https://addm.googlecode.com/svn/trunk/ addm --username dr.addn

When prompted, enter your generated[*] googlecode.com password.

generated?

http://code.google.com/hosting/settings

. Your googlecode.com password: random

This password is used by project owners and members when

checking out or committing source code changes,

or when using command-line tools to upload files to the project "Downloads" tab.

After you've been working with your project for a while,

the following subtabs on the Source tab will come in handy:

* Browse subtab

-- Allows you to browse the files and directories in your project

as they existed at a point in time.

* Changes subtab

-- Lists changes made to the repository.

You can also use this subtab to start a code review of any change.

Documenting your Project on the Wiki Tab

You can use the functionality under the Wiki tab

to create wiki pages for your project. Our wiki syntax is inspired by the

MoinMoin wiki syntax, and is more or less a subset of it.

We've found that MoinMoin is one of the most popular open source wikis

and provides a clean syntax for users.

Perform the following to create a wiki page:

1. In your project, click the Wiki tab.

2. Click the New page subtab.

3. Type the Page Name. This value must be alphanumeric with no spaces.

You won't be able to change this name later,

so be careful.

4. Enter the text and syntax for the page in the Content field.

Learn more about the wiki syntax.

5. Click a link in one of the Labels fields to see the available list of labels.

Labels help the user determine how relevant the wiki page is to them.

6. Click Preview, Save page, or Discard.

Subversion -- do you use?

http://code.google.com/p/support/wiki/FAQ#Hosting_Your_Open_Source_Project_on_Google_Code

We currently use Subversion 1.5.4, made available via WebDAV.

developers must use authenticated https:// to commit changes.

new to open source... how do I run an open source project?

If you are new, you should plan to

participate in existing open source projects to learn how they work.

You might also want to check out Karl Fogel's book,

Producing Open Source Software.

blogging for addx project

6.12: proj"g'code connected to an active blogger:

todo: [done]

. update the source tabs of g'code

to indicate planning is being shown at blogger .

pos:

. be brave and blogger any addx notes that have been proof read,

and that are you're own ideas;

( corollary: rethink how personal notes are copying others' works )

. it's just a blog, if you have something reusable to say,

put that on knowl's .

6.18: proj"update g'code:

. added a blog to each project {addm, adda, addx, adde}

blog: proj's design notes

and ended the summary with:

"(

. there is no code at this time; just a blog .

) .

6.18: proj.addn/net.g'blog/layout changed:

summary:

. found color variations that were more subtle,

and had to stop using the adsense between each entry

because on those ad's, it wouldn't let me change the colors

(loud green titles) .

proc:

. tough finding colors, here is a dark blue: 0606BB ...

then, no: I can't just take the palate they're giving;

except these grey's:

808080 dark grey

e6e6e6 grey

. here is a list of colors

www.w3schools.com/HTML/html_colors.asp

. they taught me to get a feel for the numbers:

the colors go like

ffffff: white(full color),

00000: black(absent color)

when all 3 bytes are the same, that is colorless shade of grey;

then differences in the bytes have this ordering:

red,green,blue

choices for the 2 sites:

e6e6e6 grey background

555555 dark grey text .

. for links, take the text color and

885555 -- redish it for seen-links

555599 -- bluish it for new-links

. for black background (at doc's) things were inverted like so:

aaaaaa -- text

baaaaa -- redish

aaaabc -- bluish

6.23: mis.addn/net.g'blog/importing html:

. the copy from seamonkey code to blog messed up, adding newlines,

try saving the page and then opening with firefox,

then copying the page normally (not by view-copying code)

and see if it saves the links and other html .

[11.29: I didn't say whether it worked?!]

proj.addn/g'blog/tags are not space-delimited keyword lists:

. after finding gadgets and seeing how they would index your tags

I noticed that [atleast without commas in the list]

all the tag.words were treated as one giant tag;

so, instead of treating it like a keywords list,

I renamed all the tags as I would subj names:

{pol, gear mobi trike, gear security, etc} .

6.24: proj.addn/net.g'blogs/layout and color selection:

. change layout and colors on blogs,

figure how to change text colors

. I was at this page and it had some nice blue in it,

http://picasa.google.com/mac/thanks.html

so I looked in the code, and found the numbers for a blue .

. but then -- after I decided the background was too dark

because it made even greys too glaring --

I got a light blue from the pallet

and then to see it better,

I zeroed the lower nibble of each byte: C0D0F0 .

news.addn/net.g'blogs/picassa-powered graphics:

. my picts uploaded for blogger were put into a picassa site here:

picasaweb.google.com/dr.addn/AmericiumDreamDistractions

sci.addn/{net,mac}.picasa

scm on google`code hosting

scm (source control mgt)
[10.15:
. I've been eagerly preparing to have my code hosted on Google`code,
reading up on svn,
but I was more impressed by Linus Torvald's presentation of Git,
so I was quite interested in Google's adoption of Hg instead of Git . ]