I guess I know enough Lisp to understand the code. https://github.com/bigos/Pyrulis/blob/master/Lisp/hyperspec-decorator.user.js
The problem is with the bigger picture. with some frameworks if you start with some kind of kind of main file then you can work your way around and learn the stuff even with poor documentation. Going through the files I have managed to work out what many functions are supposed to do. Still the framework is so different from anything I saw so far, it is going to be hard to understand unless I find something something about the bigger picture in the sparse documentation. On Tuesday, 2 October 2012 20:13:35 UTC+1, Scott L. Burson wrote: > > Oh dear. I don't know if I can recommend Weblocks as a way to learn > Common Lisp. You'll need to read the Weblocks code to understand how to > use it, and that may not be so easy. Well, give it a try if you want, but > be aware you're jumping in to the deep water. > > My fork is not the one installed by Quicklisp. You'll need to clone it > locally and get Quicklisp to load it instead. There are a couple of ways > to do this; I still use the old way: > > % create an "asdf" directory e.g. /path/to/asdf > % in that directory, make a symlink to weblocks.asd (the one in the tree > you cloned) > > (push #p"/path/to/asdf" asdf:*central-registry*) > > (ql:quickload "weblocks") > > -- Scott > > On Tue, Oct 2, 2012 at 4:04 AM, Paulo Geyer <[email protected]<javascript:> > > wrote: > >> cool, just starred the repository, it is the weblocks installed by >> quicklisp? >> >> I have this problem too (I need more documentation), I'm new to emacs and >> common lisp, and want to try weblocks, currently I'm trying to get better >> with emacs and learn more about slime >> >> On Mon, Oct 1, 2012 at 9:57 PM, Jacek Podkanski >> <[email protected]<javascript:> >> > wrote: >> >>> Hi, >>> >>> I have forked your project. Thank you for the prompt answer. It's >>> getting late now. I'll have at it tomorrow. >>> >>> >>> On Tuesday, 2 October 2012 01:30:14 UTC+1, Scott L. Burson wrote: >>>> >>>> For a new project, you might want to take a look at my Weblocks fork, >>>> which has a fair number of bug fixes and new features. (No new >>>> documentation, though.) You can find it at >>>> >>>> >>>> http://github.com/slburson/**weblocks<http://github.com/slburson/weblocks> >>>> >>>> -- Scott >>>> >>>> >>>> -- You received this message because you are subscribed to the Google Groups "weblocks" group. To view this discussion on the web visit https://groups.google.com/d/msg/weblocks/-/Di5KRVoWCtUJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/weblocks?hl=en.
