Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.soft-sys.math.mathematica > #12531 > unrolled thread
| Started by | John Fultz <jfultz@wolfram.com> |
|---|---|
| First post | 2012-12-03 08:30 +0000 |
| Last post | 2012-12-06 09:57 +0000 |
| Articles | 7 — 5 participants |
Back to article view | Back to comp.soft-sys.math.mathematica
Mathematica 9 for Windows John Fultz <jfultz@wolfram.com> - 2012-12-03 08:30 +0000
Re: Mathematica 9 for Windows Arne Eide <arne.eide@gmail.com> - 2012-12-04 09:08 +0000
Re: Mathematica 9 for Windows Murray Eisenberg <murray@math.umass.edu> - 2012-12-05 08:10 +0000
Re: Mathematica 9 for Windows "djmpark" <djmpark@comcast.net> - 2012-12-05 08:10 +0000
Re: Mathematica 9 for Windows "Nasser M. Abbasi" <nma@12000.org> - 2012-12-06 09:56 +0000
Re: Mathematica 9 for Windows Murray Eisenberg <murray@math.umass.edu> - 2012-12-06 09:56 +0000
Re: Mathematica 9 for Windows "djmpark" <djmpark@comcast.net> - 2012-12-06 09:57 +0000
| From | John Fultz <jfultz@wolfram.com> |
|---|---|
| Date | 2012-12-03 08:30 +0000 |
| Subject | Mathematica 9 for Windows |
| Message-ID | <k9hnvo$pi$1@smc.vnet.net> |
Some users who upgraded to Mathematica 9 for Windows have reported encountering blue-screen system crashes. The system crashes seem to be caused by a Windows bug in handling how we update fonts, and can potentially happen even when not running Mathematica (for example, opening the Fonts control panel might cause a blue screen). The issue only affects Windows machines which had older versions of Mathematica installed. The issue is rare and was not found during extensive internal and external prerelease testing. However, we're taking the issue very seriously, and we recommend that you don't install Mathematica 9 for Windows until we can provide you with a patched installer, which should be available for download from http://user.wolfram.com in the next few days. If you have already installed Mathematica 9 for Windows and have not encountered this issue there is nothing you need to do. If you have installed Mathematica 9 for Windows and have encountered the issue, you can find a solution for the problem here: http://support.wolfram.com/kb/11160 Or, feel free to contact Technical Support and they can help you walk through deploying the fix. We apologize for any inconvenience this may cause you. Sincerely, John Fultz, Director of User Interface Technology Arnoud Buzing, Director of Quality Assurance Wolfram Research, Inc.
[toc] | [next] | [standalone]
| From | Arne Eide <arne.eide@gmail.com> |
|---|---|
| Date | 2012-12-04 09:08 +0000 |
| Message-ID | <k9kei5$66k$1@smc.vnet.net> |
| In reply to | #12531 |
I'll give credit to Wolfram for quick response and precise guidance to solve the problems with the blue screens. Thanks a lot. I don't know however, how you can claim that this "issue is rare", actually to me it seems like most of the 64 bits Windows user with previous version 8 installations, have been affected. But the fix worked fine, at least for my two PCs. Both of them went down with blue screen after installing version 9. Not even safe mode could wake them. The Mathematica fonts had to be deleted from a DOS shell before windows could be loaded again. But the manual work worked and I am grateful for the advise. (Who would guess Windows was killed by a font issue!). So much about the (rare?) blue screens. Now I am more concerned about the route Wolfram indicates with the new Mathematica version. Each previous version of Mathematica has represented important steps forward, improving well-known features and adding others. Even those versions that gave us loads of work to do, rewriting older notebooks, have been appreciated, increasing the net benefit of the software. I am not equally enthusiastic about version 9 (up to now). Does it represent a turning point in the development of the Mathematica software? It seems to me that the integration of the Wolfram-Alpha ideas into the Mathematica environment is changing the simple and attractive structure of Mathematica. Do we have to move into the Math kernel shell to get back to the original Mathematica experience? I hope you will maintain Mathematica as the unique tool it was and still is and let Wolfram-Alpha develop alongside, maybe also as a first Mathematica experience. Co-existence instead of a predator-prey relation. Best regards, Arne On Monday, 3 December 2012 09:30:48 UTC+1, John Fultz wrote: > Some users who upgraded to Mathematica 9 for Windows have reported > > encountering blue-screen system crashes. The system crashes seem to be > > caused by a Windows bug in handling how we update fonts, and can > > potentially happen even when not running Mathematica (for example, > > opening the Fonts control panel might cause a blue screen). The issue > > only affects Windows machines which had older versions of Mathematica > > installed. > > > > The issue is rare and was not found during extensive internal and > > external prerelease testing. However, we're taking the issue very > > seriously, and we recommend that you don't install Mathematica 9 for > > Windows until we can provide you with a patched installer, which should > > be available for download from http://user.wolfram.com in the next few > > days. > > > > If you have already installed Mathematica 9 for Windows and have not > > encountered this issue there is nothing you need to do. > > > > If you have installed Mathematica 9 for Windows and have encountered the > > issue, you can find a solution for the problem here: > > > > http://support.wolfram.com/kb/11160 > > > > Or, feel free to contact Technical Support and they can help you walk > > through deploying the fix. > > > > We apologize for any inconvenience this may cause you. > > > > Sincerely, > > > > John Fultz, Director of User Interface Technology > > Arnoud Buzing, Director of Quality Assurance > > Wolfram Research, Inc.
[toc] | [prev] | [next] | [standalone]
| From | Murray Eisenberg <murray@math.umass.edu> |
|---|---|
| Date | 2012-12-05 08:10 +0000 |
| Message-ID | <k9mvgt$b8p$1@smc.vnet.net> |
| In reply to | #12531 |
Nothing whatsoever forces you to use the link to Wolfram|Alpha. On Dec 4, 2012, at 4:09 AM, Arne Eide <arne.eide@gmail.com> wrote: > So much about the (rare?) blue screens. Now I am more concerned about the route Wolfram indicates with the new Mathematica version. Each previous version of Mathematica has represented important steps forward, improving well-known features and adding others. Even those versions that gave us loads of work to do, rewriting older notebooks, have been appreciated, increasing the net benefit of the software. I am not equally enthusiastic about version 9 (up to now). Does it represent a turning point in the development of the Mathematica software? It seems to me that the integration of the Wolfram-Alpha ideas into the Mathematica environment is changing the simple and attractive structure of Mathematica. Do we have to move into the Math kernel shell to get back to the original Mathematica experience? I hope you will maintain Mathematica as the unique tool it was and still is and let Wolfram-Alpha develop alongside, maybe also as a first Mathematica experience. Co-existence instead of a predator-prey relation. --- Murray Eisenberg murray@math.umass.edu Mathematics & Statistics Dept. Lederle Graduate Research Tower phone 413 549-1020 (H) University of Massachusetts 413 545-2838 (W) 710 North Pleasant Street fax 413 545-1801 Amherst, MA 01003-9305
[toc] | [prev] | [next] | [standalone]
| From | "djmpark" <djmpark@comcast.net> |
|---|---|
| Date | 2012-12-05 08:10 +0000 |
| Message-ID | <k9mvii$b9t$1@smc.vnet.net> |
| In reply to | #12531 |
I'm concerned too. I think WRI is mashing and corrupting one of their primary assets, a clean notebook interface. The principle here is that a user should be able to obtain help WHEN AND WHERE HE ASKS FOR IT and not otherwise. The primary point in the interface is the new cell insertion point. This should be completely unadorned. There should be nothing there until the writer asks for it or types something. Similarly as a user types there should be nothing else unless and until he asks for it. The writer should not be constantly presented with "in your face" requests for which the answers are overwhelmingly no. WolframAlpha is a nice feature but I think it would be only occasionally used in most notebooks. It can be obtained by using "=" as a shortcut, or by typing WolframAlpha[...]. I don't see why it couldn't be added to the context menu. We don't need a constant little advertisement for it at the primary point of interface. It's like walking into a store when you know exactly what you want but first having to fend off a sales person offering you various items of information or specials and reappearing before each new purchase. The Input Assistant at first seems like a good idea but it has a way of turning into a huge dynamic distraction. I also find some difficulty in completing the symbol entry, sometimes getting the wrong symbol and sometimes having to grab the mouse and click in the notebook. You may complete the command you want but the list will still be there needing to be dealt with. Also, in the instructions when WRI says "Tab" I'm not certain if they mean the arrow keys instead. Also the command completion sometimes does not appear to work and other times does. The entire thing is a bit more complex than is convenient. I think the pre-Mathematica 9 method was better. It only appeared by request, using Ctrl+K, and then often completed at that point. If M9 gives a better context sensitive list of completions then that could still be incorporated. Templates should be obtained only if one uses Ctrl+Shift+K. It is just as easy to type that as it is to grab the mouse and click a temporary button. It appears now that in M9 WRI is obtaining the templates from the multiple entries in the Function page Usage cell, with perhaps some method to add additional ones. But they use this only in their in-house Build process and don't yet make it available to developers. WRI really has to work on updating Workbench. I don't think it's been updated for over two years. Many of these things, including the Predictive interface, might be better if they were on a context menu, always available but otherwise invisible. Or they might be buttons in the docked Toolbar at the top of the notebook. There seems to be plenty of room there and they might be more useful than the justification buttons. One of the problems with Mathematica is the great number of commands. Rather than writing code, I would think a more useful Predictive interface feature would be to give direct links to Guide pages that had routines related to the context of one's work. Keep the notebook interface clean, like a blank piece of paper, and leave beginners` aids to tutorials, context menus, optional Toolbars or palettes. David Park djmpark@comcast.net http://home.comcast.net/~djmpark/index.html From: Arne Eide [mailto:arne.eide@gmail.com] So much about the (rare?) blue screens. Now I am more concerned about the route Wolfram indicates with the new Mathematica version. Each previous version of Mathematica has represented important steps forward, improving well-known features and adding others. Even those versions that gave us loads of work to do, rewriting older notebooks, have been appreciated, increasing the net benefit of the software. I am not equally enthusiastic about version 9 (up to now). Does it represent a turning point in the development of the Mathematica software? It seems to me that the integration of the Wolfram-Alpha ideas into the Mathematica environment is changing the simple and attractive structure of Mathematica. Do we have to move into the Math kernel shell to get back to the original Mathematica experience? I hope you will maintain Mathematica as the unique tool it was and still is and let Wolfram-Alpha develop alongside, maybe also as a first Mathematica experience. Co-existence instead of a pre dator-prey relation. Best regards, Arne On Monday, 3 December 2012 09:30:48 UTC+1, John Fultz wrote: > Some users who upgraded to Mathematica 9 for Windows have reported > > encountering blue-screen system crashes. The system crashes seem to > be > > caused by a Windows bug in handling how we update fonts, and can > > potentially happen even when not running Mathematica (for example, > > opening the Fonts control panel might cause a blue screen). The issue > > only affects Windows machines which had older versions of Mathematica > > installed. > > > > The issue is rare and was not found during extensive internal and > > external prerelease testing. However, we're taking the issue very > > seriously, and we recommend that you don't install Mathematica 9 for > > Windows until we can provide you with a patched installer, which > should > > be available for download from http://user.wolfram.com in the next few > > days. > > > > If you have already installed Mathematica 9 for Windows and have not > > encountered this issue there is nothing you need to do. > > > > If you have installed Mathematica 9 for Windows and have encountered > the > > issue, you can find a solution for the problem here: > > > > http://support.wolfram.com/kb/11160 > > > > Or, feel free to contact Technical Support and they can help you walk > > through deploying the fix. > > > > We apologize for any inconvenience this may cause you. > > > > Sincerely, > > > > John Fultz, Director of User Interface Technology > > Arnoud Buzing, Director of Quality Assurance > > Wolfram Research, Inc.
[toc] | [prev] | [next] | [standalone]
| From | "Nasser M. Abbasi" <nma@12000.org> |
|---|---|
| Date | 2012-12-06 09:56 +0000 |
| Message-ID | <k9pq3u$hni$1@smc.vnet.net> |
| In reply to | #12625 |
On 12/5/2012 2:10 AM, djmpark wrote: > WRI really has to work on > updating Workbench. I don't think it's been updated for over two years. > I think the effort should be to make a simple to use debugger integrated in the notebook interface itself. One should not have to use 2 different and separate programs to debug some code. A simple and easy to use but powerful debugger with line numbers! like that which exist in a product called M____B will go a long way to making Mathematica easier to use for common users. Most students do not like to use Mathematica because it is hard to debug code in it. All what WRI needs to do, is just look at the M____B debugger, and make one like it which is build-into the notebook. Not a new and separate program. That is all. I have been waiting for such a debugger for years. I do not think WRI really understand this issue much and how important it is. I still use Print[] to debug my Mathematica code, which is so 1970's thing to do now. --Nasser
[toc] | [prev] | [next] | [standalone]
| From | Murray Eisenberg <murray@math.umass.edu> |
|---|---|
| Date | 2012-12-06 09:56 +0000 |
| Message-ID | <k9pq4u$ho5$1@smc.vnet.net> |
| In reply to | #12531 |
Let the user choose! By default, the new interface doodads -- autocompletion, Suggestions Bar, and dynamic highlighting -- are enabled. And this is probably a good thing for the new Mathematica user who just wants to start using the system as quickly as possible without a long learning period. The experienced user need only open Preferences/Options and on the Interface tab uncheck the corresponding items. In the case of autocompletion, there's even the option to leave it enabled but set a popup delay. For the new cell insertion point, the little + icon is hardly distracting. In fact, to the unknowing eye, it merely suggests this is a place where you can add some input. It's not until you click the + sign that you see the choices, including free-form/WolframAlpha input. And the + icons gives those who want it another way to insert a Text cell without having to revert to the main menu or the keyboard shortcut equivalent. Perhaps there's a way to use the Option Inspector to turn off, too, the + icon at the new cell insertion point; I haven't discovered it yet. I agree that it would be useful to have the choice of these interface doodads readily available to unset or reset on a menu or a palette. On Dec 5, 2012, at 3:13 AM, djmpark <djmpark@comcast.net> wrote: > I'm concerned too. I think WRI is mashing and corrupting one of their > primary assets, a clean notebook interface. > > The principle here is that a user should be able to obtain help WHEN AND > WHERE HE ASKS FOR IT and not otherwise. > > The primary point in the interface is the new cell insertion point. This > should be completely unadorned. There should be nothing there until the > writer asks for it or types something. Similarly as a user types there > should be nothing else unless and until he asks for it. The writer should > not be constantly presented with "in your face" requests for which the > answers are overwhelmingly no. > > WolframAlpha is a nice feature but I think it would be only occasionally > used in most notebooks. It can be obtained by using "=" as a shortcut, or by > typing WolframAlpha[...]. I don't see why it couldn't be added to the > context menu. We don't need a constant little advertisement for it at the > primary point of interface. It's like walking into a store when you know > exactly what you want but first having to fend off a sales person offering > you various items of information or specials and reappearing before each new > purchase. > > The Input Assistant at first seems like a good idea but it has a way of > turning into a huge dynamic distraction. I also find some difficulty in > completing the symbol entry, sometimes getting the wrong symbol and > sometimes having to grab the mouse and click in the notebook. You may > complete the command you want but the list will still be there needing to be > dealt with. Also, in the instructions when WRI says "Tab" I'm not certain if > they mean the arrow keys instead. Also the command completion sometimes does > not appear to work and other times does. The entire thing is a bit more > complex than is convenient. I think the pre-Mathematica 9 method was better. > It only appeared by request, using Ctrl+K, and then often completed at that > point. If M9 gives a better context sensitive list of completions then that > could still be incorporated. > > Templates should be obtained only if one uses Ctrl+Shift+K. It is just as > easy to type that as it is to grab the mouse and click a temporary button. > It appears now that in M9 WRI is obtaining the templates from the multiple > entries in the Function page Usage cell, with perhaps some method to add > additional ones. But they use this only in their in-house Build process and > don't yet make it available to developers. WRI really has to work on > updating Workbench. I don't think it's been updated for over two years. > > Many of these things, including the Predictive interface, might be better if > they were on a context menu, always available but otherwise invisible. Or > they might be buttons in the docked Toolbar at the top of the notebook. > There seems to be plenty of room there and they might be more useful than > the justification buttons. One of the problems with Mathematica is the great > number of commands. Rather than writing code, I would think a more useful > Predictive interface feature would be to give direct links to Guide pages > that had routines related to the context of one's work. > > Keep the notebook interface clean, like a blank piece of paper, and leave > beginners` aids to tutorials, context menus, optional Toolbars or palettes. > > > David Park > djmpark@comcast.net > http://home.comcast.net/~djmpark/index.html > > > > From: Arne Eide [mailto:arne.eide@gmail.com] > > So much about the (rare?) blue screens. Now I am more concerned about the > route Wolfram indicates with the new Mathematica version. Each previous > version of Mathematica has represented important steps forward, improving > well-known features and adding others. Even those versions that gave us > loads of work to do, rewriting older notebooks, have been appreciated, > increasing the net benefit of the software. I am not equally enthusiastic > about version 9 (up to now). Does it represent a turning point in the > development of the Mathematica software? It seems to me that the integration > of the Wolfram-Alpha ideas into the Mathematica environment is changing the > simple and attractive structure of Mathematica. Do we have to move into the > Math kernel shell to get back to the original Mathematica experience? I hope > you will maintain Mathematica as the unique tool it was and still is and let > Wolfram-Alpha develop alongside, maybe also as a first Mathematica > experience. Co-existence instead of a pre dator-prey relation. > > Best regards, > Arne > > > On Monday, 3 December 2012 09:30:48 UTC+1, John Fultz wrote: >> Some users who upgraded to Mathematica 9 for Windows have reported >> >> encountering blue-screen system crashes. The system crashes seem to >> be >> >> caused by a Windows bug in handling how we update fonts, and can >> >> potentially happen even when not running Mathematica (for example, >> >> opening the Fonts control panel might cause a blue screen). The issue >> >> only affects Windows machines which had older versions of Mathematica >> >> installed. >> >> >> >> The issue is rare and was not found during extensive internal and >> >> external prerelease testing. However, we're taking the issue very >> >> seriously, and we recommend that you don't install Mathematica 9 for >> >> Windows until we can provide you with a patched installer, which >> should >> >> be available for download from http://user.wolfram.com in the next few >> >> days. >> >> >> >> If you have already installed Mathematica 9 for Windows and have not >> >> encountered this issue there is nothing you need to do. >> >> >> >> If you have installed Mathematica 9 for Windows and have encountered >> the >> >> issue, you can find a solution for the problem here: >> >> >> >> http://support.wolfram.com/kb/11160 >> >> >> >> Or, feel free to contact Technical Support and they can help you walk >> >> through deploying the fix. >> >> >> >> We apologize for any inconvenience this may cause you. >> >> >> >> Sincerely, >> >> >> >> John Fultz, Director of User Interface Technology >> >> Arnoud Buzing, Director of Quality Assurance >> >> Wolfram Research, Inc. > > --- Murray Eisenberg murray@math.umass.edu Mathematics & Statistics Dept. Lederle Graduate Research Tower phone 413 549-1020 (H) University of Massachusetts 413 545-2838 (W) 710 North Pleasant Street fax 413 545-1801 Amherst, MA 01003-9305
[toc] | [prev] | [next] | [standalone]
| From | "djmpark" <djmpark@comcast.net> |
|---|---|
| Date | 2012-12-06 09:57 +0000 |
| Message-ID | <k9pq5e$hog$1@smc.vnet.net> |
| In reply to | #12531 |
The new cell insertion point icon can be suppressed by using the option CellInsertionPointCell->None, in a notebook, style sheet or a CreateDocument statement. I hadn't noticed the "Enable autocompletion..." option in Interface preferences. Thanks for bringing it to my attention. But instead of a popup delay, or as an alternative, I would much prefer a choice to enable autocompletion by using Ctrl+K. Then I could get it as fast as I want, or not at all. I would still like to see the notebook interface optimized for the experienced user and not for na=EFve beginners. That means as clean as possible and to me that means a blank sheet of paper. Beginners can learn from tutorials, or perhaps there could be a "training wheels" option in Preferences (normally off). Nevertheless, there is a problem with Mathematica even for experienced users. That is getting information on the existence and nature of the large number of routines available, and selecting those that might be useful at some point in your work. I think this is probably part of the objective in the Suggestion Bar and Predictive Interface. But I think they aimed it in the wrong direction. Instead of writing code for you, they should be directing you to information that will help you better write your own code. I don't know what is behind the "predictive interface", maybe cellular automaton agents?, but perhaps a user could select a cell and on the context menu bring up a temporary menu with direct links to relevant Guide pages (and Tutorials). This would be a shortcut rather than having to drill down (and around) from the DC Home page. Being able to go directly to relevant Guide or Tutorial pages based on context would be a great help. It should also be noted that Function and Guide pages have a toolbar at the top that gives the various paths to the page. Starting from a lower level you can work back up the structure by clicking on the links. It would also be really nice to have a tabbed Documentation Center as an adjunct to multiple windows. David Park djmpark@comcast.net http://home.comcast.net/~djmpark/index.html From: Murray Eisenberg [mailto:murray@math.umass.edu] Let the user choose! By default, the new interface doodads -- autocompletion, Suggestions Bar, and dynamic highlighting -- are enabled. And this is probably a good thing for the new Mathematica user who just wants to start using the system as quickly as possible without a long learning period. The experienced user need only open Preferences/Options and on the Interface tab uncheck the corresponding items. In the case of autocompletion, there's even the option to leave it enabled but set a popup delay. For the new cell insertion point, the little + icon is hardly distracting. In fact, to the unknowing eye, it merely suggests this is a place where you can add some input. It's not until you click the + sign that you see the choices, including free-form/WolframAlpha input. And the + icons gives those who want it another way to insert a Text cell without having to revert to the main menu or the keyboard shortcut equivalent. Perhaps there's a way to use the Option Inspector to turn off, too, the + icon at the new cell insertion point; I haven't discovered it yet. I agree that it would be useful to have the choice of these interface doodads readily available to unset or reset on a menu or a palette.
[toc] | [prev] | [standalone]
Back to top | Article view | comp.soft-sys.math.mathematica
csiph-web