Hey Andrew, please excuse the late answer. Lots of things to tend to these days.
On Sep 29, 9:08 pm, Andrew <[email protected]> wrote: > I have played around a little, found that build-in simple-blog sample > application doesn't allow to insert posts because lack of author > (where it should appear from?), I can't comment on that since I haven't looked into it, but it's presumably easy to fix. > and it seems that it hard to start for > weblocks newbie in general - many samples and tutorials on the net > does not work with weblocks-dev. Sorry about that. I've always tried to preserve backwards compatibility as much as possible, but it hasn't been possible in all cases. But really diving into the code to adapt the tutorials and samples to the current code (with the help of this group) is a great way to get to know Weblocks. > And I didn't manage to understand why backgrounds in css are > commented. It made my head blow up. It was hard to sleep because of > this. And all are silent on this topic. We've trimmed down the looks of the demo app a couple of months ago and I guess that this is where these lines were commented out. You can use "hg annotate" to find out when a line was changed and by whom. > Is it weblocks user responsibility to make up widget appearance? Yes, in almost all cases you want to customize your CSS. > Or may be it's sneaky design solution, which does not work on > my machine because it was patched by global conspiracy agents? Haha, this time it probably isn't! Leslie -- You received this message because you are subscribed to the Google Groups "weblocks" group. 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.
