Re: My wishlist

Hi,

I'm still a newbie to netWindows, but not to DHtml programming.
Well.... I'm a amateur at that too! ;)

>>It's slow to load, and doesn't move well on the screen.
As to moving a window....
I've seen a few examples on the net, display the outline of a window
instead of showing the actual window moving around.
Alternatively, when a user holds the mouse down (whilst moving a
window) on the 'Title Bar', one could hide the 'Contents window'.
Better yet, make it a property of the window widget instead of the
default behaviour(with optional global properties for all windows).

Speaking about windows....
Here's my wish list....well, from what I've seen in the
window_test.html example.

We need a taskbar to show all open windows that have been minimized.
That way windows, can actually disappear...... title bar and all (And
save space to boot).
If the developer doesn't want to use the taskBar (Ie, it takes up too
much realestate) netWindows can always revert to the current
implementation.

I like the current implementation of the windows.
E.g.
Take 2 windows. Click on one. It's pops to the top. Click on the other,
it pops to the top.
That's all well and good in a number of circumstances. But we should
have other behaviours as well.

Take the case we I want to display 4 or 5 little windows on a screen.
One displaying a tree, the others detail screens. Here's how I'd like
to see them behave.
- Windows should know about their own space. If 2 windows are on the
same zOrder, they shouldn't be able to overlap each other.
  In other words, they should be able to move freely in open space, but
not over other windows.
- Maximizing should only maximize to the avaible open space. Minimizing
to the titleBar(or taskBar) is fine.
- Urrmm.... Make them 'stick' to each other ala winamp! ;) (ok...
that's more a nice to have !)

Well, urrm, thats just my R0.02...

Regards
KD

>>> [email protected] 2004/01/29 19:43:18 >>>
Hi everybody!  Alex asked me awhile back to post a wishlist of stuff
for netWindows, and I finally decided to get around to doing it :)

I'll start first with the split pane.  I do like the split pane, but
something that we would like added is the ability to be able to handle
click events so that when you click, it closes, click again it opens (
slides in and out ).  So it would be useful in the td that shows that
shows the actual 'split' in the page, to split that into three sections
so that one section can house an image of some sort that shows you can
click it to hide or show the one pane.  I guess as well you'd have to
also identify which side of the split pane that you want to show/hide,
which you could setup as an attribute on the div of the split pane.

The second would be the window.  I actually think this should be
somewhat higher on the list.  I have found several 'problems' with it,
but can't remember them all :)  My first complaint is that it's quite a
kludgy window.  It's slow to load, and doesn't move well on the screen,
or at least in our app when we move it around it's kind of jerky.  It
would also be nice if there was a way of 'caching' the pages that you
loaded.  This again could be something that you could pass as an
attribute so if you do need to reload the page each and every time you
open it, then it can do that, but I think having the option would
definitely speed up our stuff.  

And finally something that would be definitely on a 'wishlist', would
be to have a calendar of some sort.  We are currently using a calendar
from a third party, but I am not completely happy with it.  I've noticed
that you have a date_picker widget that doesn't really have any code in
it, so I'm guessing it just needs to be completed :).  Some 'nice'
functions to have in there would be a set minimum date, and set maximum
date.  This would then limit the choices of dates that the user has. 
The user would still be allowed to scroll through the list, but they
wouldn't be allowed to choose anything outside the minimum or maximum. 
The minimum/maximum date could also be specified as a number so that you
could specify 5 days prior to today to be the minimum date, or 20 days
from today to be the maximum date.  As well, you should also be able
specify whether this is to be a static calendar, one that is always
visible, or a calendar that is derived as a popup, click on an image and
it pops up.  You should also be able to specify an element ( input box )
that the selected value gets put into.   And with being able to specify
a place for the date to go into, you could then also include the
validator_widget in it, and you could specify the display format.


So that is my current wishlist.  I'm sure that I have forgotten things,
but for now I figured this was a good starting point!


Dee Gould

---------------------------------------------------------------
“All views or opinions expressed in this electronic message 
and its attachments are the view of the sender and do not 
necessarily reflect the views and opinions of the 
Provincial Government Western Cape (“the PGWC”).  
No employee of the PGWC is entitled to conclude a 
binding contract on behalf of the PGWC unless he/she 
is an Accounting Officer of the PGWC, or his or her 
authorised representative.

The information contained in this message and its attachments 
may be confidential or privileged and is for the use of the 
named recipient only, except where the sender specifically 
states otherwise.  If you are not the intended recipient you 
may not copy or deliver this message to anyone.”


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