Hi all,
I've been having a discussion with Martin about the new configurator that he
wrote (only in CVS and the tarballs), but we think it would be better here,
so here we go...
> >> I've thought about hiding some of the options instead, so that you
> >> would click on a group to expand it, and then click on it again if
> >> you don't want to see it. If we splitted the options into more
> >> groups, then I think it would remove some of the clutter.
> >
> > this doesn't need to be done by submitting a form. This is the kind
> > of thing that javascript is great for.
>
> Oh, yes that would be super! I really don't know anything except the
> most basic stuff about Java - would you be able to program such a
> tree-thing in Java? (Perhaps we should continue the discussion on
> phpweather-devel - there might just be a great Java-hacker lurking
> there...)
I could probably do it, but I'm very much a javascript hacker rather than
any kind of real programmer :) All layers and visibility and junk.
So here we are on phpweather-devel... The basic idea is that on the
configurator, it would be best if the options for configuring a database
were only visible if a database is chosen. At the moment, there's a kind of
solution where the form is submitted and php sorts it all out server-side,
but it's a mess. javascript is the real way to do this.
any volunteers?
> And now that we're dreaming... it would be extra cool if the form
> could be checked by some Javascript at the client - it would be easy
> to make the pw_validator_range class generate the right Javascript,
> but I don't know about the pw_validator_ereg class.
Max
|
