Re: CVS broken?

On Wednesday 03 September 2003 07:56, Christian Boulanger wrote:
> Michael Flanagan wrote:
> > now we're just ignoring the issue as we do all development in
> > Moz anyway. You can't beat Venkman for js debugging. This
> > widget will get a feature enhancement in the near future.
>
> Sounds good. We DO need to have at least a working version for internet
> explorer in order to present our project. But probably Alex is working 
> on it...

As soon as I get a spare hour or 2, this will be fixed. Right now, docs are my 
highest priority (at least until the docs for the combo box and the data 
tables are finished).

> > | 2) Tree
> >
> > I can't comment a whole lot on the functionality of this
> > widget as I haven't looked at it, but my recommendation wrt
> > theming is to turn it off and use CSS to get the look you
> > want. We do style assignment with CSS. We've even added
>
> I like the idea of theming because it gives a lot of choice to the user. I
> also want to minimize my work concerning design.

Don't we all = )

> I really have such little
> time that I want to use for the application logic only and leave the rest
> to NW. I don't think that what we need requires a lot of code change. 

My understanding of your needs suggests that this is true.

> If there is a way to add little icons to tree branches via CSS, why not. 

We should be able to effect this both through builtin themes and CSS.

> But it should be done by NW not by extra code that we would have to add.

In the case of CSS themes, it would be a set of extra CSS blocks in your page 
header. Since you're not using CSS themes now, I see no realisitic need to 
suggest it for your use here.

> Otherwise, I could just take the PEAR::HTMLTree Class which does the job
> and send the generated menu to a NW split pane window. I want to avoid
> that.

And I'd prefer to give you a widget you like = )

> > | 4) remove popup does not work
> >
> > The approach that I'm going to take is to modify the body of
> > my pages being sent to the browser so that they look
> > something like the following:
>
> [...]
> <div nwType="page_loader" contentBodyId="divContent">
>
> > ~    <h1>Loading Page...</h1>
> > </div>
> >
> > <div id="divContent" style="display:none">
> > ~    //Actual application HTML goes here.
> > </div>
>
> This seems like a great idea. It would work on any page loaded, not only
> the main one, right? So even windows with external context could display a
> "Loading..." message before the content is there. One could even add a
> little animated GIF with a (fake) progress bar or a sand clock etc.

This is indeed an interesting appraoch. Perhaps something like it should go in 
the FAQ?

-- 
Alex Russell
[email protected]    BD10 7AFC 87F6 63F9 1691 83FA 9884 3A15 AFC9 61B7
[email protected]  F687 1964 1EF6 453E 9BD0 5148 A15D 1D43 AB92 9A46

_______________________________________________
The netWindows developers list: [email protected]
http://netwindows.org/mailman/listinfo/devel_netwindows.org