[openbeosnetteam] Re: Network preflet, the future?

> Van: openbeosnetteam-bounce@xxxxxxxxxxxxx [mailto:openbeosnetteam-
> bounce@xxxxxxxxxxxxx] Namens Axel Dörfler
> "Philippe Houdoin" <philippe.houdoin@xxxxxxx> wrote:
> > BTW, here the latest layout I came off, after Axel give his opinion
> > monday:
> > http://philippe.houdoin.free.fr/phil/beos/openbeos/network_kit/
> > network_gui-04.png
> 
> Looks better although I miss the "Switch To" button a bit; I actually
> thought to have the "Apply" button at the bottom, and the "Switch To"
> button at the top. But do as you want :-)

I have the menu at the top myself as well. However, I think it is bad
to have the New.../Copy.../Delete functions in that same menu. It gives
the menu a 'double function' (selection of a profile and editing), which
I think is a big no-no.

Another thing I'm not to fond of is the way Show listview. I tend to
lean towards tabs, because they give a better overview of all the
options,
it also minimises the amount of mouse activity needed to switch to
another
page. However, I do realise that if there are a lot of add-ins, the
amount
of tabs may become so big that the purpose of having tabs is surpassed.
But
at the moment I lean towards the tab-approach.

> BTW the extended part of the API is not yet fixed; if you don't like
> it, or have ideas to make it better, feel free to shout!
I haven't worked with it yet, but as soon as I do, I will tell you what
I
think of it!

In another mail P.H. wrote:
> However, nice job.
> Now, how come we could continue from both of our work on the subject?
> Do you have time and plan to work fully on this task, in which case
> I'll step down (but keep send advice and critics, that the fun of
being
> team leader :-) ), or
> should will look at code written and decide?

I don't think our main ideas differ very much. And I presume you have
written a lot more code than me. The thing is that we should decide 
on which approach we should take. I personally stick to the General
page.
In a tabview this tab would be first anyway, would be on screen when the
user starts the preflet, and it will contain a general summary (the
status
listview). But I'm leaving this decision to you. As soon as you've
decided,
I am more than willing in involving myself with writing the code.

Niels

Other related posts: