Nice effort brett & thanks for adding the source code. If you push the dates out to 2034, first of Jan differs b/w tracksruns & gnome clock 2.2 But considering the lack of libs I can't complain.
"... I'm running Linux, and so date was broken and thus so was the web server, I looked in the repository and was happy to see someone had a fix, and I didn't even have to read the date man page ..."
Yes. When projectileboy said "the Git repo that's been created", I assumed he meant the one you just linked to (I don't know of any other), which is where I found the date fix.
The idea was to have five pixels forming an arc with their trajectory. To make the logo stand out better you can change the colors or the size of the whole thing. I have added an alternative with text and in black/white.
uvl 8-)
"... To make the logo stand out better you can change the colors or the size of the whole thing. I have added an alternative with text and in black/white. uvl 8-) ..."
"... The idea isn't to have a single standard repository, of course. It's to take advantage of the purpose of distributed revision-control systems - to provide a standard way of publishing and exchanging patches. ..."
Hey nex3 that is such a neat solution, using git is smart.
"... Or maybe a title and description is enough. ..."
As little as possible. Filling in fields is a pain. I think the description field could be optional if the code is commented. The bit I think would boost the understanding of the language is concrete examples. The pattern of reading the source code, writing a bit of code, posting it to arclanguage works for people who read the post.
Snippets scale better which is what you want. Quick failure with bad ideas. Good ideas expressed in code will then have to stand the test of time.
"... My super fantasy includes small examples with their outputs. If the Arc team hates this idea, maybe an Arc Wiki is the way to go? ..."
Damn I missed this thread. The examples are exactly the way to go. My idea was something along the lines of a snippets collection by user, title plus code and unique url. [0] This means the good code rises to the top, is stored at arclanguage for all to see and read. Sorted by hacker. At some time in the future it could also be run server-side - something pg has hinted in the past.
"... maybe an Arc Wiki is the way to go? ..."
But this idea is more focussed on describing the code. Is there anyway a code document generator could be written extracting
- filename
- function name
- description
to auto generate the documentation much like Python? [1] This one thing Guido got right - documentation: A tutorial (already exists) and the module index (does not). [2] By having a PyDoc equivalent running over the latest version of Arc you can have a arclanguage.org/doc url with a module index plus the tutorial.
This is how python became so damn useful. You could find how to solve a problem reading both the tutorial, then check the module index to read the details. Sure beats having to do a wiki which arclanguage pretty much covers sans the markup.
Same here on a ubuntu 7.10 gutsy 64amd. There's no (easy) way to do an install for v352 w/o doing a source compile (works) and manually installing the files (can't be stuffed).
