Hello fellow lisper. 
You have faced one of the main Weblocks problems. And you can help to solve 
it.
Yes, ask about the problems and I will be glad to help you when I have time.
I have updated documentation recently but it is not enogh I think.
Another advice - don't use navigation widget, it has much bugs. If you use 
it then don't expect continuations to work properly.
I have replacement for navigation which does not change urls but works with 
continuations well. Navigation is one of the largest problems to solve.
At this moment i suggest use Weblocks for admin interfaces and some other 
framework (or just some code without widgets etc.) for other site part for 
which urls are important.

среда, 2 октября 2013 г., 1:04:06 UTC+3 пользователь André Miranda Moreira 
написал:
>
> Hello, felow Lispers =]
>
> I'm trying to learn this wonderful piece of software that is Weblocks.
> I became fascinated with it not only because it uses Common Lisp, but
> also because I find the idea of using continuations to deal with stateless 
> HTTP
> very good.
>
> I've done web development before (Ruby on Rails, obviously =] ) and
> I've been trying to make a nice app with weblocks, but after trying
> for almost two months I'm still unable develop much beyond the basics
> in the tutorials and examples.
>
> After reading the tutorials and the quickdocs API, I'd like to ask for
> a piece of advice: how could I become a (better) Weblocks developer?
>
> After this time with the framework I see that it's been carefully built, 
> and I want to become proeficient using it. What would you suggest?
> Should I stick to try and error, and post here any problem I face?
>
> Thanks in advance,
>
> André.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weblocks" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/weblocks.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to