The video is interesting in that it makes me wonder about what makes a language great for instruction - however, can it be said that pedagogical programming languages are like training wheels for bikes, in that they aren't strictly necessary to learn? Taking the example of "method" (as discussed in the video around 14 minutes in) - if a student is having trouble recognising what a method is, even if an alternative syntax helps them learn, will they just keep on having similar difficulties (i.e. that person just isn't cut-out for CS)?
I would like to learn what the duo in the video think of teaching OOP through tooling (e.g. BlueJ / Object Test Bench) as opposed to using a different language.
Web Access software isn't of much use to people who don't control their own servers. Enterprises will eat this up, but home users can't really sync Outlook Web Access with Desktop Outlook unless they use their OWA provider's Exchange servers. Similarly people
who want to use Office Web Access will need to trust their provider's SharePoint servers.
....otherwise, the idea of having to upload a 40MB word document to WWA just to make a few changes and then have to redownload it again does not appeal.
I'm of the opinion that screenshot of Excel Web Access is using Silverlight. It's a screenshot of IE7, not 8 which lacks a fair few useful CSS2 features, and the screenshot shows some things that would be
very hard (if not impossible) to implement using plain XHTML/CSS/DOM Scripting, like client-side conditional formatting for bar-charts: note how the bars differ by scale rather than by scrolling (or simply being clipped). CSS2 has no support for background
image scaling and making them inline images would just mess the layout up. It has to be Siverlight.
It's nice to see a "native" ribbon that sticks to the Windows UI scheme in a conservative, yet aesthetic way.
I do have a few questions and opinions though:
I'm not sure that using the Ribbon with Paint was the best of ideas. Painting programs are best suited to pallettes, even if they're docked, than toolbars. Adobe's (and formerly Macromedia's) software demonstrate this. I cannot see Photoshop working with a
ribbon (despite having probably more options and features than Word 2007). With the old-style version of Paint pretty much everything was one click away. Whilst with the ribbon some features are now one click away, other tools aren't: consider the Brush options.
Now you need to click three times to select the brush tool, and then select a brush type. If you want to change views you need to open the View tab and then fiddle with the tools there, and then click back to the main tools tab.
Whilst I welcome moving the "File" tools over to a button that's in the tab row (rather than an "Office button"-style widget) I don't believe that programs should be painting to the non-client area at all. What alternatives are there for highlighting context
sensitive tabs than painting above them in the titlebar?
Finally, you mentioned this would be available for Vista, but there was no mention of the still-supported Windows XP (and I might say Windows 2000 too). What would happen if I tried running the ribbonised paint on XP, for example?