> Phil said:
> > we know it's being worked on. I suppose it might be better
> > to collect url and pages of test when possible
>
> Well that wouldn't work for me, unless I told Olli et al
> my Windows 2000 login password (and NO you aren't getting it!)
Ok but storing informations and/or routines in a frame is quite common on
the net. if parent is not implemented, well, no need to detail more no ?
>
> > cause reporting that or that site doesn't work ok or crashes
> >
> > 1) might not be true on their current version
>
> In which case they can say "it's fixed and will be released
> soon". It's not like they'll have to RE-fix it :)
Shouldn't they finish Js before coping with bugs ? And should they check
all the urls that were reported not to work in the previous version to
make sure it is corrected as soon as a routine is modified or a feature
implemented ? And check if nothing is broken in a more
complete list of url ? it's not the finalization part, it's still
development time :) (I can't imagine the time it would take to Olli
to follow a complete V development cycle at each phase for every line of code)
Do you think the next pre-release will be complete and bugless ? I don't.
I think pre-release 2 will be even better than pre1, and for the rest it'll
be a matter of pre-release3. In fact I hope they won't walk towards a stable
version as long as not everything is in, I would fear for the future of V.
V's feature list makes it potentially the ultimate browser on the amiga,
and that's what I'd like it to be, not an incomplete rock solid sequel of pre1
that will be up to date in V4 :)
> > 2) doesn't help 'bugs' to be grouped together (imagine you
> > have to debug a browser and have hundreds of url reported
> > not to work ) - anyway jserrorlogs must be better for this
>
> The JSERROR.LOG is as informative as a book with no pages for
> the parent classes :) It just says "invalid" which obviously
> means "not implemented yet".
>
So..
> > When there is a more complete version things might turn
> > different...
>
> What's the point of having a beta browser with a beta
> JS compiler if nobody reports bugs 'til the full release?
>
Well... I'm not behind their brain actually. I just suggested it
was no need flooding vapor with tons of bug reports at this stage, where
the development is obviously not finished...
When I second ran V3, I ran cyberguard, took a sheet of paper and began to
write down urls and series of hits (the first time I ran it, it crashed too fast
:)... just to realize it was no use doing that.
I thought I would write down a long bug list in this ml,but finally,
when I got back here on monday and began to read what had already been
posted, I felt it useless and drop it.
In its current incarnation, V3 is a kind of interactive
snapshot (better than Ib2 that - except for the lucky ones
who went to woa and the !%$@ ones who got a cracked version - is just a
non-interactive series of snapshot).
At this point I think remarks like 'where is this feature'
that are more or less design related are more useful than
reporting endless lists of js problems...
The issues that've been answered so far are more often suggestions than
bugs (bookmark, navbar...). Basically we're at the same point as before pre-1
when Olli published a list of new features in V3, but we had the luck to
be able to download a snapshot to see by ourselves... I dunna how long
the NYI list in V3 is, and posting 'my tree.js site doesn't show the tree,
when will layers be implemented' is not very useful... If it's nyi, well,
vapor gang knows it. I think Yam doesn't work with V3 is better cause it
eventually can be an unknown problem. Not to forget the people who check
the V3 version before they are released to beta-users like us, and who
have more recent versions, are better than us at finding bugs, and know
(I suppose :) what to check and what not to test.
I'm not saying it's no use reporting bugs, I just suggest some of these bug
reports are too early, V3's been released for our pleasure and for the WOA
more than for beta testing.
It's just my point of view, but personnaly I'll wait a few releases before
sending a hit, an url or a piece of code on something new to V3.
Phil
____________________________________________________________
Voyager Mailing List - Info & Archive: http://www.vapor.com/
For Listserver Help: <[EMAIL PROTECTED]>, "HELP"
To Unsubscribe: <[EMAIL PROTECTED]>, "UNSUBSCRIBE"
