ocsigen / old.ocsigen.org Goto Github PK

• Async_kernel yields the error

Error: Corrupted compiled interface
/cmis/core_kernel.cmi

• Graphics: Draw chars yields a Syntax erroron the use of loop
• Graphics: Draw yields a Syntax erroron the use of loop

Dear all,
I gave a shot to the Graffiti tutorial and wanted to get back to you with a few various remarks, I hope it fits here.

• http://ocsigen.org/ : on the left, there is still a news from 2013 announcing a now tutorial. However, the link leads to a non existent page. The following remarks will be with respect to the tutorial itself, here: http://ocsigen.org/tuto/4.2/manual/application
• Unless I missed something, the final eliom code provided at the very beginning does not compile with a complete installation as provided on the site. Indeed, it requires ocsigen-widgets which does not seem to be distributed. At least it is not reffered to here: http://ocsigen.org/install . Note also that on this last page, there is a small bug at the end: the list of packages goes out of the box, and a «>> syntax error in wikisyntax» appears.
• In chapter Collaborative Drawing Application, we are to «add» the iteration over the bus at the end of function init_client. However we cannot add the line directly, since we still need to react to mouse clicks. I probably am quite stupid here, but the way to combine both events seems non trivial to me for people discovering the language and would suggest to make it more explicit.
• The final version of the code at the bottom of the page is a dead link. A working, minimal version of the project here would be welcome.

Best,
Yannick

Seeing

Internal Server Error

Error 500

Unix.Unix_error(Unix.EPIPE, "write", "")
(Ocsigen running in debug mode)

Originally reported by @keyansol in ocsigen/lwt#331.

ttps://ci.inria.fr/ocsigen/

I recommend renaming the repo to ocsigen.org. It is common practice for the name of a repo, which implements a website, to be the URL of that website. For example: ocaml.org and biocaml.org. The name site is too generic.

Is there an RSS or Atom feed for the news on ocsigen.org? I think Ocsigen could benefit a lot from more blog posts. There is currently too little material to help people get started or to even know what it is all about.

Bonjour,

Tous les tests du manuel sur le site ocsigen pointent vers le serveur http://tests.ocsigen.org qui ne répond même pas aux pings...

For external links in the tutorials there is an icon (https://ocsigen.org/resources/icons/external_link-ocsigen.png). In my browser (Firefox 45.3.0) it is displayed with a size of 1600x1124 pixels. I don't understand why though.

When I visit the https://ocsigen.org/js_of_ocaml/ page, I think understand that Tyxml_js depends reactiveData is quite complex.
Perhaps ReactiveData should be documented on the page (instead of github.io) and ReactiveData an js_of_ocaml.tyxml dependency.

Thank you for your work!

Waiting for a HTTP response forever on http://ocsigen.org/

http://ocsigen.org/install

• Link to mailing list doesn't work, is https://sympa.inria.fr/sympa/arc/ocsigen elsewhere on the site
• Ubuntu support seems to be identical to Debian now https://launchpad.net/ubuntu/+source/eliom
• Should https://registry.hub.docker.com/u/ocsigen/ocsigen/ be listed as an easy install option?

Common to all /install and other sub-pages:

• The 'Je Suis Charlie' banner overflows into the main content area -- compare with oscigen.org home page (tried Firefox and Chromium)

To make pull requests on documentation easier to do.

See text This is client API (go to server) on there. It has white font color on yellow background. My eyes are flowed out and can't flow in back.

Not sure what's the issue is .... http://ocsigen.org/

Ocamldoc section titles are in rather small font, smaller even than the main body font. They are barely visible. I recommend increasing the font size.

Sur ce tuto : https://ocsigen.org/eliom/manual/server-links , il est écrit "Eliom_content.​Html5.​D.​a takes as first parameter the service you want to link to. The third parameter is the text of the link. The last parameter is for GET parameters you want to put in the link."
Le libellé du lien devrait être le second paramètre, et non pas le troisième !

Hi, just want to notify that currently the ocsigen.org site cannot be accessed, returning ERR_CONNECTION_REFUSED on Chrome. Sorry if you're already aware of it! :)

The design of the website is very outdated (not responsive, information is hard to find, etc).

It's crucial to attract people. People may think the project is outdated as the website design is outdated.

https://ocsigen.org/lwt/dev/api/Ppx_lwt :

Error
Ocaml_lexer.Error(_, _)
Ocisgen running in debug mode

on the left panel.

Broken link to opam file at http://ocsigen.org/js_of_ocaml/2.8.4/manual/overview

http://ocsigen.org/howto is partially out of date, repeats parts of the items of the "howto" list of http://ocsigen.org/tuto/6.1/manual/ , and (@Drup tells me) is not versionned.

In page https://ocsigen.org/howto/compile there is a link toward https://ocsigen.org/eliom/manual/client-compiling#h5o-2 and this ends up with a page not found error...

In multiple function description the string Error a_api: "bounded_push" is not a valid module name is used instead of a correct type/value.

https://ocsigen.org/lwt/2.5.2/api/Lwt_stream.bounded_push-c

It's not obvious enough, when one is on https://ocsigen.org/tuto/, that they have to click on manual to go to the more interesting page https://ocsigen.org/tuto/manual/ !

The current site infrastructure is hard to maintain. It would be nice to migrate to mostly static content.

I think our discussions converge on a modern Bootstrap-style homepage that points to the relevant places. We can take ocaml.org as an inspiration. I personally think that we should just point ocsigen.org to what is now ocsigen.github.io, and use GitHub Pages (basically Jekyll) for almost everything. If we decide to do so, it will be trivial to integrate the blog posts and hence ensure that ocsigen.org feels active.

The big obstacle is the current manual/tutorial/API documentation that use wikidoc syntax. In principle, we could implement static infrastructure for these that retains the existing functionality (e.g., trans-project links). But that would involve maintaining a new tool with questionable usefulness outside Ocsigen. In the spirit of simplifying our workflow, I would personally prefer just using Ocamldoc/odoc functionality for the API doc (with manual strategically-placed links where needed), and an one-off translation of the manuals and the more important tutorials to a simpler format (e.g., markdown). Given static docs, we can either put them in GitHub pages or in dedicated docs infrastructure like Read the Docs.

The hello world howto was not updated wrt to Eliom 4. I'll gladly do it if someone tell me in which project the change should be done!

Opam switch beta does not work.
Do you know why? What did you expect to do with this version?
Is it using cohttp? Is it dur to a change in cohttp or a bug in ocsigenserver/cohttp?
@dinosaure @hhugo

The html title tag for pages is always the main project name, e.g. Lwt or Js_of_ocaml. It would be helpful to make the title unique for each page, especially API doc pages. For example, the http://ocsigen.org/lwt/api/Lwt_stream page should be titled "Lwt_stream" instead of "Lwt".

Most browsers provide this title in their tabs. This change would make it easier to keep multiple tabs open to different documentation pages. Right now I just have lots of tabs all named "Lwt".

See for instance on http://ocsigen.org/lwt/2.5.1/api/Lwt_unix the documentation for the async_method type:

type async_method =  
| Async_none
(* <<div class="odocwiki_info"|~System calls are made synchronously~, and may block the entire program~. >> *)
| Async_detach
(* <<div class="odocwiki_info"|~System calls are made in another system thread~, thus without blocking other ~Lwt threads~. ~The drawback is that it may degrade performance in some cases~. ~This is the default~. >> *)
| Async_switch
(* <<div class="odocwiki_info"|~System calls are made in the main thread~, and if one blocks the execution continue in another system thread~. ~This method is the most efficient~, also you will get better performance if you force all threads to run on the same cpu~. ~On linux this can be done by using the command <<span class="odocwiki_inlinecode"|taskset>>~. ~Note that this method is still experimental~. >> *)

Dans la page du tuto client server ( https://ocsigen.org/tuto/manual/tutowidgets ), le fait que les boîtes avec écrit "click me" soient une capture d'écran ( https://ocsigen.org/tuto/files/tutorial/tutowidgets/ex-final.png ) n'est pas clair du tout. Il faudrait soit mettre avant un titre explicitant qu'il s'agit d'un exemple du résultat final, soit directement mettre l'exemple que le tuto va s'évertuer à expliquer !

If you go to this page : https://ocsigen.org/howto/img and click on "external service" (at the end, just before "download full code") the page will say "not found". I guess the "manual" and "howto" are not handled by the same ocsigen server, but why so? It would be good for the ocsigen website to have no internal broken links in order to demonstrate the usefulness of eliom services! This is but one example of broken links within ocsigen.org website... :(