Re: Other Lisp Frameworks

On Wed, 30 Sep 2009 12:21:14 -0700 (PDT)
nunb <nandan.bagchee@...> wrote:

> > I can only tell you that UCW seems to have been abandoned, but
> > there's another contender called WUI that seems to be similar to
> > Weblocks.

It certainly has not been abandoned.  Recently it has stabilised into
two parts, ucw-core and ucw-standard.  The intent of ucw-core is to
provide a smallish extensible core to extend upon.  ucw-standard
provides extra functionality on top this core.

> UCW afaik has forked. One branch is now LoL (Lisp on Lines) and the
> other is the base for WUI.

LoL isn't so much a fork but an extension constructed on top of
ucw-core.

--

-- 
Daniel White

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "weblocks" group.
To post to this group, send email to weblocks@...
To unsubscribe from this group, send email to weblocks+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: N00B Question

On Sep 30, 10:08 pm, Michael McDermott <mcdermott.micha...@...>
wrote:
> Adding :persistp nil to the form options seems to have done it. Thanks. I
> knew it had to be something so simple, that I'd feel stupid as soon as I
> knew what it was... :)

But do you understand why this is needed?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "weblocks" group.
To post to this group, send email to weblocks@...
To unsubscribe from this group, send email to weblocks+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Navigation, back button and action

On Oct 1, 12:01 am, Tim <tym...@...> wrote:

> I think that after pressing back button and calling the action the
> first widget cannot be found in the navigation. This widget has become
> invalid since the closure was created. Am I right?

The back button should have nothing to do with this, actually.

Have you tried reproducing this in a case where the back button
is not involved at all? It should fail too.

> I wrapped first widget in another widget. This code works:

Interesting. This used to be necessary since the DO-WIDGET code
(which is what the WITH-FLOW expands to) knew only how to
replace widgets in simple parent containers (of 'composite' class
then).

The current code should work with all widgets however, so there's
a bug, probably in MAKE-WIDGET-PLACE-WRITER.

I'm going to fix that.

In the meantime thanks for pointing out; the current dev head
definitely needs more testing of that kind.

  Leslie
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "weblocks" group.

Re: Why is it so slow?

On Sep 28, 2:07 pm, "max.powe...@..." <max.powe... <at> t-
online.de> wrote:
> Dear Leslie,
> I made an observation, two things make it run smooth for me:
> Removing the content from main.css (replaced it with own css code) , or hitting the "Add" button of a
grid-edit table; when the corresponding form view opens, it suddenly runs smooth too.

Looks like a problem in the mentioned browsers' CSS engine. Odd that I
don't experience
that. Can you narrow it down to a specific CSS rule in the file?

> it will tell me, there were no dispatcher-class.

There is no longer, but the new system is pretty similar.
You need to inherit from SELECTOR and specialize GET-WIDGET-FOR-
TOKENS.

Read the documentation for this function (or all the docstrings in src/
widgets/selector.lisp)
to get more information.

Does that help you?

  Leslie
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "weblocks" group.
To post to this group, send email to weblocks@...
To unsubscribe from this group, send email to weblocks+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/weblocks?hl=en

Re: Navigation, back button and action

Related test:

* replace a widget in a nav. New widget gets displayed properly via
AJAX.
* reload the page; the old widget is there again.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "weblocks" group.
To post to this group, send email to weblocks@...
To unsubscribe from this group, send email to weblocks+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Navigation, back button and action

On Oct 1, 9:40 am, "Leslie P. Polzer" <leslie.pol...@...> wrote:
> Related test:
>
> * replace a widget in a nav. New widget gets displayed properly via
> AJAX.
> * reload the page; the old widget is there again.

Fixed in 3d4834d18aa8:

  http://bitbucket.org/S11001001/weblocks-dev/changeset/3d4834d18aa8/

Tim, your original problem was indeed related to the back button and
should
be solved as of 9773e8121f34:

  http://bitbucket.org/S11001001/weblocks-dev/changeset/9773e8121f34/

Cheers,

  Leslie
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "weblocks" group.
To post to this group, send email to weblocks@...
To unsubscribe from this group, send email to weblocks+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---

Re:Why is it so slow?

Re: Why is it so slow?

On Oct 1, 4:42 pm, "max.powe...@..." <max.powe...@...>
wrote:
> Dear Leslie,
> why can't I use static-selector? It already has an get-widget-for-tokens implementation.
> Regards

It depends on what you're trying to do. If your selector will have
some kind of mapping
from tokens to panes instead of or next to some other mechanism (like
relying on the time
of day and similar things) you're probably better off with inheriting
from static-selector.

  Leslie
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "weblocks" group.
To post to this group, send email to weblocks@...
To unsubscribe from this group, send email to weblocks+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---

Re:Why is it so slow?

Re: Why is it so slow?

On Oct 1, 5:58 pm, "max.powe...@..." <max.powe...@...>
wrote:
> Dear Leslie,
> I don't want to to fancy stuff here. All I want is a navigation without the visible menu.

Oh, that's simple. Just inherit from navigation and specialize render-
navigation-menu
to do nothing.

> But when I use static-selector, all that is being rendered is a page-layout
> without content.

Yes, a selector doesn't display anything by itself. The navigation
widget
adds the things you can see (menu and content).

  Leslie
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "weblocks" group.
To post to this group, send email to weblocks@...
To unsubscribe from this group, send email to weblocks+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---