content now changed to be one page per file
Tim Menzies
1) the content is now divided into content/Area/Pages (see the list,
below)
2) i've divided up the current pages into two reviewing piles: one for
MichaelR and one for Lorance (see the "owners" at http://code.google.com/p/awk/issues/list).
can mikeR and Lorance have a look at that list? if it is too long,
then scream and we'll divide it up further
enjoy!
:-)
t
.
|-- Admin
| |-- 0index.txt
| |-- 404.txt
| |-- about.txt
| |-- currentTestResults.txt
| |-- examplePage.txt
| |-- legal.txt
| |-- reviewing.awk
| |-- testSuite.awk
| |-- tinytim.txt
| `-- write.txt
|-- Agents
| `-- 0agents.awk
|-- Arrays
| |-- 0arrays.txt
| |-- arrayHTML.awk
| |-- checkArrayIdx.awk
| |-- checkArrayVal.awk
| |-- deleteArray.awk
| |-- hiloArray.awk
| |-- median.awk
| |-- o.awk
| |-- printArrayCsv.awk
| |-- reverseArray.awk
| |-- s2a.awk
| `-- shuffleDeck.awk
|-- DataMine
| `-- 0datamining.txt
|-- DateTime
| |-- 0dateTime.txt
| `-- currentDateTime .awk
|-- Directories
| `-- 0directories.txt
|-- Files
| |-- 0files.txt
| |-- appendFile.awk
| |-- basename.awk
| |-- createFile.awk
| |-- deShell.awk
| |-- options.awk
| `-- readNthLineInfile.awk
|-- Functions
| `-- 0functions.txt
|-- Hashes
| `-- 0hashes.txt
|-- Numbers
| |-- 0numbers.txt
| |-- abs.awk
| |-- factorial.awk
| |-- isNum.awk
| |-- numbersIntro.awk
| |-- oddp.awk
| |-- rFloat.awk
| |-- rInt.awk
| `-- seed.awk
|-- RegularExpressions
| `-- 0regx.txt
|-- Statistics
| |-- 0stats.txt
| |-- mwu.awk
| |-- normal.awk
| |-- normalPdf.awk
| |-- normalSample.awk
| |-- rank.awk
| `-- wilcoxon.awk
|-- Strings
| |-- 0strings.txt
| |-- a2s.awk
| |-- accessingSubstrings.awk
| |-- barph.awk
| |-- controllingCase.awk
| |-- isNumString.awk
| |-- no.awk
| |-- string2num.awk
| |-- stringsIntro.awk
| |-- takingStringsApart.awk
| `-- trimmingBlanks.awk
|-- Variables
| |-- 0variables.txt
| |-- constants.awk
| |-- globals.awk
| |-- namingGlobals.awk
| `-- staticVars.awk
|-- Web
| |-- 0web.txt
| `-- plugIns.txt
|-- Who
| |-- 0who.txt
| |-- mahesh.txt
| |-- michs.txt
| |-- panosp.txt
| `-- timm.txt
|-- XML
| `-- 0xml.txt
`-- config.txt
Michael Richter
--
To unsubscribe, reply using "remove me" as the subject.
--
"Perhaps people don't believe this, but throughout all of the discussions of entering China our focus has really been what's best for the Chinese people. It's not been about our revenue or profit or whatnot."
--Sergey Brin, demonstrating the emptiness of the "don't be evil" mantra.
Michael Richter
The only scream I'm making is "how do I get to the files themselves"? I get the list. I click on the "start reviewing" link and get ... the list again. Nothing clickable past that point that goes anywhere I recognize.
<rhetorical>When will Google learn that developers need self-documenting UIs as well, not video blogs.</rhetorical>
On 4 April 2010 10:52, Tim Menzies <menzi...@gmail.com> wrote:
i've made two large changes:
1) the content is now divided into content/Area/Pages (see the list,
below)
2) i've divided up the current pages into two reviewing piles: one for
MichaelR and one for Lorance (see the "owners" at http://code.goog;le.;com/p/awk/issues/list).
Panos
First of all, I believe that using GoogleCode was a good decision;
it's a marvelous tool.
About the Subversion choice I doubt that it's better than mercurial.
In fact, it's not (read http://hginit.com/ by Joel Spolsky), but
that's not matters too much. The thing is that the use of a Version
Control System (any VCS) is MANDATORY. Btw, the VCS is not the right
tool to make changes on the files; it's about REVIEW the changes and
make sure that alla files are up to date. Not using a VCS will lead to
chaos quickly. Let's not argue on this anyway. I believe that all of
you people are doing magnificent job and I'm very happy that the
project is alive and active. Tim has made great job and continues to
change things for making our lifes easier. But that's a large project
and all these issues are expected to be there, eh? I'll rejoin
(propably) in a few weeks. Bravo to all of you!!!
On 4 Απρ, 08:46, Michael Richter <ttmrich...@gmail.com> wrote:
> You know, I'm beginning to think that doing this by printing off the code
> and mailing it by surface mail would be more self-explanatory and quicker
> than using Google Code's tools. :( With all the bright people over at
> Google you'd think a user interface designer (one that understands concepts
> like "principle of least surprise" and "self-explanatory labels") would be
> among them somewhere.
>
> Is there any actual documentation for Google Code's web site somewhere? Or
> would figuring out SVN be time better spent?
>
> On 4 April 2010 13:40, Michael Richter <ttmrich...@gmail.com> wrote:
>
>
>
>
>
> > The only scream I'm making is "how do I get to the files themselves"? I
> > get the list. I click on the "start reviewing" link and get ... the list
> > again. Nothing clickable past that point that goes anywhere I recognize.
>
> > <rhetorical>When will Google learn that developers need self-documenting
> > UIs as well, not video blogs.</rhetorical>
>
> > On 4 April 2010 10:52, Tim Menzies <menzies....@gmail.com> wrote:
>
> >> i've made two large changes:
>
> >> 1) the content is now divided into content/Area/Pages (see the list,
> >> below)
>
> >> 2) i've divided up the current pages into two reviewing piles: one for
> >> MichaelR and one for Lorance (see the "owners" at
> >>http://code.goog;le.;com/p/awk/issues/list<http://code.google.com/p/awk/issues/list>
Michael Richter
Panos I. Papadopoulos
I'll give you an example:
Enter the Awk Cook Book's repo in Google Code and click on "Source"
tab. Then click on "Changes" and then click on, let's say r278 (means
revision 278). You'll see a log message of the commiter and a list of
changed/modified files. If you like to check the modifications in that
commit (revision), then just click on the "diff" link and you'll get a
very nice side by side projection of the file before and after the
modifications. That's one thing. The other is to make your own
corrections and modifications, after you've checked the last
modifications made by others. To do so, update your local working copy
(using svn in your local machine; if in PC and windows, the use the
"tortoiseSVN" "update") and then edit the file, or add new files. When
finish your changes make a "commit" using your svn (or tortoiseSVN)
and the revised copy will be put as new revision in the repo. Great,
don't you think?
On 5 Απρ, 09:25, Michael Richter <ttmrich...@gmail.com> wrote:
> So no actual answer to the questions of how to USE the reviewing
> functionality then? Like, say, how to actually comment on files instead of
> lists?
>
> On 5 April 2010 13:43, Panos <panos1...@gmail.com> wrote:
>
>
>
>
>
> > Hi all!
> > First of all, I believe that using GoogleCode was a good decision;
> > it's a marvelous tool.
> > About the Subversion choice I doubt that it's better than mercurial.
> > In fact, it's not (readhttp://hginit.com/by Joel Spolsky), but
Michael Richter
Let's see if I'm getting this. After Tim's split of one page per topic
I'll give you an example:
Enter the Awk Cook Book's repo in Google Code and click on "Source"
tab. Then click on "Changes" and then click on, let's say r278 (means
revision 278). You'll see a log message of the commiter and a list of
changed/modified files. If you like to check the modifications in that
commit (revision), then just click on the "diff" link and you'll get a
very nice side by side projection of the file before and after the
modifications. That's one thing. The other is to make your own
corrections and modifications, after you've checked the last
modifications made by others. To do so, update your local working copy
(using svn in your local machine; if in PC and windows, the use the
"tortoiseSVN" "update") and then edit the file, or add new files. When
finish your changes make a "commit" using your svn (or tortoiseSVN)
and the revised copy will be put as new revision in the repo. Great,
don't you think?
Panos I. Papadopoulos
be fixed now without initiating a complete "cold restart" in the ACB
project. Maybe you have to solve this with Tim. I'm going to follow
whatever the group say. Happy to work with you. This is an active
group.
On 5 Απρ, 12:24, Michael Richter <ttmrich...@gmail.com> wrote:
> I'm talking about the *web-based* modification system that we'd tested
> before on the *web-based* collaboration site. I really do not feel like
> being forced into learning SVN, given that I think it is the single second
> worst RCS ever created and given that awk is a hobby for me, not a job.
>