Posted on 2008-07-10 14:38 By
Axel Vogt (
948)
I am missing the F1-help to work properly after highlighting words
at least for the following
invfourier ---> completely missing (it is in inttrans)
invlaplace ---> completely missing
invmellin ---> completely missing
fourier ---> MTM[fourier], but not inttrans
Parts ---> completely missing (expect it in IntegrationTools)
Flip ---> ImageTools[Flip], but not to IntegrationTools
Change ---> selection, but no IntegrationTools
dchange ---> completely missing (it is in PDETools)
changevar ---> IntegrationTools[Change], but not to student
(this is an old package, but usefull for changing summations)
codegen[split] and horner are only seen indirectly through prep2trans
Hopefully it will be repaired soon, even if I have the impression
that user of the real interface are somewhat ignored in their needs.
Comments
lots of help problems in 12 Classic
It seems to me that the help system is severely broken in Maple 12 Classic [from your reports and several others that I have seen]. Have you filed these as SCRs? That is the best way to insure they are 'in the system'.
Since Classic is not really maintained anymore, I wonder what is considered an 'unacceptable' bug. All software products have certain functionality deemed so essential that any problems with it would be considered a 'showstopper' to shipping the product to (paying) customers. Since Classic is a 'shipping product', there must be such a treshold?
SCR
I sent a short SCR by refering to this thread the same day, that should be enough
If they do not really maintain that and it is the only one I am interested in, then I am only one in a crowd of idiots ... sorry, but that makes me angry (not on you, of course) ... what is a customers treshold?
At least I would expect them to have those things in test routines ... and I would be astonished if such things would never have been seen in beta tests ...
Treshold
At some point, you get so aggravated that you do something about it. First, you might complain loudly. Then, you might not upgrade (and tell many not to either) since you don't feel the upgrade is worth the money. Eventually, you switch products (if there is a competitor that seems worth it).
Not upgrading is easy enough to do - and is real lost $$$ to a company. Switching is much harder. This 'lock in' is what allows makers of software to continue shipping product riddled with bugs and yet still make money.
true - but a risky game
True - but a risky strategy, even if it will work for some years ...
actually it is somewhat idiotic in this case - at least I do not
see, that the company actually has an extra profit in ignoring
demands for a reasonable interface (there is nothing speaking
against a JAVA GUI per se - it is more the anti-productive handling
and the destgusting speed) ... so I guess, it is based on some
ideological/political paradigma, may be even concatenated to some
few persons, unable to revise decision due to market demands (not
talking about some possible technical design errors and the certain
need to let the stuff work with JAVA without being deeply used to
it - I have seen consequences for such in our own shop).
Why risky? There are lots of examples, here are just 2. One is
Software AG (I think they started as spin off from IBM), which
had a superior development system for database application, highly
productive, especially for user dialogs and program maintenance.
They started in times of (IBM based) mainframe computers - and
ignored the UNIX world. Meanwhile they are negligible at the
market - while formerly even SAP was forced to provide special
versions for this database system. The other is Adidas, they for
a long time ignored the 'younger generation' - and narrowly got
killed by Nike.
Even if these are different as they ignored new demands vs the
complains about new ways they have something in common: there
will be no way back for user who switched.
BTW: searching in historical corners of the www there has been
lot of Maple stuff from INRIA - not much to find todays ...
I did not even receive a notification for SCR - so feel no need to
send one in future, just expect Maple to check this forum. If I had
send it to my distributor I never faced such.
Enough, I feel just as one of a crowd of stupids ...
Topic Search
Topic Search... and Full Text Search... in Help menu seem to be working though.
Alec
Known bugs
Also, some bugs are clearly known when new version is released. It would be helpful if in addition to New features help page there was also a Known bugs help page.
Alec
Very funny
You will not find sellers of commercial math software jumping on that particular bandwagon anytime soon! Sure, some open source software has their bug database 'public'. But how many closed-source, for-profit software companies do you know who have such an enlightened policy?
Microsoft
Microsoft, for once - Release notes for latest Visual Studio, or SDKs, for example, contain long lists of bugs, some with workarounds, and others - without. I think, in some countries all public companies are required doing that by law. Maplesoft is not public though.
Beside the law - knowingly selling a defective product (such as a table or a chair with a brocken leg) to somebody without telling him (or her) that it is defective, is highly unethical.
Alec
EULA and Lemon Laws
Most EULAs (End-User License Agreements) for software basically say that the company makes no warranty whatsoever about the fitness of the product for any task. Furthermore, the so-called 'lemon laws' (in the US as well as in other countries) generally have explicit exceptions for software.
It is we, the consumers, who are stupid enough to purchase any software under those conditions.
Known and unknown
Yes, EULA doesn't make any warranties - but it is for "unknown" bugs. "Known" bugs is a different law category. I think, a company can be sued for not disclosing them independently of EULA.
Alec
Not True
This doesn't seem to be true at all about the Maple EULA, or even EULAs in general. These are all very standard phrases:
Just ask any lawyer
Just ask any lawyer - obviously, you are not one.
If it is for self education - read UCITA, for example.
The first precedent (won by a customer) was in 1961.
Alec