First, one thing I would suggest is that you can create pull requests
for anything right from the GitHub UI, although that doesn't let you
test them. Especially for small documentation changes where there's no
chance you're breaking something, I find that to be very effective and
lightweight.
Seco
It feels like much of the information needed to make some of the sign posts
for easy contribution are available either 1) automatically available at
time of documentation build, or 2) could be added to the info file.
Would someone in the Racket team be able to recommend or suggest some
concrete wa
I think your point is totally valid, and I feel that I already saw such
discussion in the mail list.
You can simplify the process by searching a piece of the documentation in
github. For example, I search for a piece of the docs from rackjure (1)
which is the second result in my search.
(1)
htt
For the record, my big concern with the documentation is that it's
extremely hard to contribute to. I would be delighted to contribute
documentation if the process was easy, but it's just not. For a language
as amazing as Racket and a documentation set as high-quality as Racket's,
the difficulty
On Nov 25, 2019, at 1:29 PM, Stephen De Gabrielle wrote:
> Many packages contain an /examples folder, and adding examples is an easy way
> to contribute.
I did not know that. So, I guess the strategy is to find the git repository
for the package and look there? In any case, I haven't been f
Many packages contain an /examples folder, and adding examples is an easy way
to contribute.
There is also https://github.com/racket/racket/wiki/Artifacts
> This page captures useful code snippets that are too small to be a package.
>
> Please contribute your own!
Though these might be better
There may be some examples on Rosetta code, or at least Racket snippets
could be added:
https://rosettacode.org/wiki/Category:GUI
On Sat, Nov 23, 2019, 00:23 Martin DeMello wrote:
> One helpful thing to do is expand the GUI section of awesome-racket
> https://github.com/avelino/awesome-racket
>
One helpful thing to do is expand the GUI section of awesome-racket
https://github.com/avelino/awesome-racket
I just sent them a PR for GUI-helpers.
martin
On Thu, Nov 21, 2019 at 9:21 AM James Platt wrote:
>
> On Nov 20, 2019, at 3:31 AM, Jack Firth wrote:
>
> > Would it have helped if the ge
On Nov 20, 2019, at 3:31 AM, Jack Firth wrote:
> Would it have helped if the get-directory documentation had included
> examples? Many parts of Racket's documentation are lacking in example code,
> especially the less-commonly-encountered parts.
Indeed, I have previously mentioned the lack of
I can't speak for others but for me I feel it would have helped a great
deal in enabling me to quickly figure out how it was supposed to actually
be used. What was tripping me up the most I guess was 1) it appeared to me
I needed to use the brackets like shown in the documentation, and 2) that
Would it have helped if the get-directory documentation had included
examples? Many parts of Racket's documentation are lacking in example code,
especially the less-commonly-encountered parts.
On Tuesday, November 19, 2019 at 10:52:14 PM UTC-8, pow bam wrote:
>
> Indeed I would have likely never
Indeed I would have likely never even known that section existed - and
looking at it now I see that it is very dense reading material. I turns my
mind to mush trying to interpret what's being said there. I also happen to
be, by and large, a self-learning lone wolf type. I am a complete novice to
On 11/19/2019 2:04 PM, pow bam wrote:
Ah thank you very much Hadi.. that indeed worked out nicely and now
makes alot more sense to me. The documentation structure can be a bit
confusing/misleading on points like this and I rather wish that they
would display "real world" usage examples more i
Ah thank you very much Hadi.. that indeed worked out nicely and now makes
alot more sense to me. The documentation structure can be a bit
confusing/misleading on points like this and I rather wish that they would
display "real world" usage examples more in-depth in the docs for clarity.
Again t
14 matches
Mail list logo
