hi ukbill,
i remember this was proposed on the forum some tiem ago. I totally agree
with you on this one. example: when firefox or soem KDE apps crash.. we ge=
t
a dialog box which allows you to send any info. if we have an option like
that in vasm, which can collect system diagnostics from time to time or whe=
n
ever you want it. we can have a reference and also it is easy for any one t=
o
flaunch vasm, chose their option and save the file or send it to some
location , if sending email is possible.
while we are at it, is there a "Dashboard" for the next major version of V=
L
? like 6.0 ?
like what are our priorities, when do we know we have a good RC? what are
the major activities in terms of features etc../ who are the people who own
it/ how do we track etc?
i think having an easy diagnostic and feedback tool is essential and shoul=
d
be on the top of such a priority list.
cheers
ram
On 3/15/06, HQX Net <hq...@gm...> wrote:
>
> Hi,
> Thank you inviting me to the list, this is UKBill for those wondering
> about the mail address.
>
> Coders probably will not like this idea, but it has been lurking my
> mind from some time now.
>
> Taking John's request further and looking at making forum support
> easier, how about a little "Help/About" application that would...
>
> * Run in CLI and TUI mode, ala VASM
> * Tell the user which version he/she is running
> * Give a remainder about the included Docs
> * Ask what the problem is related to (cards, services, ??), then
> --> collect some data (lsmod, lspci, chip speed, mem amount, etc),
> --> dump it to a file and instruct the user to post this file to the
> forum.
> * It should also give some help about how to handle that file in a
> b0rked situation, such as no X working, no network, etc. We all now
> that newcomers often dont know how to past from terminals etc.
>
> Regards.
> UKB.
>
>
> > Good morning!
> >
> > With the proliferation of different versions of VL (live, SOHO,
> standard,
> > deluxe and permutations thereof), I would like to request that the
> > /etc/vector-version file clearly state the version as specifically as
> > possible. For example, if the release is VL standard 5.1 Live RC2, we
> could
> > state VectorLinux 5.1 LiveRC2 as the version. For a SOHO release, we
> should
> > state something like this: VectorLinux 5.1 SOHO Live3 or VectorLinux 5.=
1
> > SOHO . Finally, for a Deluxe version we should state the version as
> > VectorLinux 5.1 SOHO Deluxe.
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmdlnk&kid=110944&bid$1720&dat=121642
> _______________________________________________
> Vectorlinux-devel mailing list
> Vec...@li...
> https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel
>
|
