Hello! We could make several demos with different purposes. One to demonstrate the basics and then one or more focusing on a special use or purpose (code generation, reverse engineering, AndroMDA, any other specific profile, statechart diagrams, creating profiles, ...).
Should this be structured around the Tours? What about improving the Tour to partition it in this way and then have (on each Tour page) a link to "see a demo of this"? /Linus 2008/3/27, "Andreas Rückert" <[EMAIL PROTECTED]>: > > Hi! > > -------- Original-Nachricht -------- > > Datum: Wed, 26 Mar 2008 12:58:29 -0400 > > Von: "Tom Morris" <[EMAIL PROTECTED]> > > An: dev@argouml.tigris.org > > Betreff: Re: [argouml-dev] ArgoUML-users website > > > As Andreas points out, improving the user experience may be a better > > use of time in the short term than recruiting new users. Manuals and > > wikis and other resources are great, but the closer the > > documentation/help is to the point of use, the more effective it will > > be for users. We've got tool tips in a lot of places, but context > > sensitive help would be a very useful addition. Having the app > > include a live link to the online manual or even including the manual > > in the download would be a good interim measure. > > Online manual is already displayed within Argo here. :-) > There are some minor issues left to resolve (ShortCut, Localize the menu > item etc). > I don't have much idea, what a help window should look like at the end. > My current proposal might be a tabbed pane with tabs for: > manual, cookbook, Wiki(?), users-website(?) > I'm not sure, if a HTML manual is the best way to go in the long run. With > some > XML, we could add some meta information, that could be used to organize > the help > a bit. Like a separated index in a second pane (like OpenOffice does it as > an > example). > > Suggestions? > > > Doing a good demo involves a lot more than speaking English (or any > > other language) well. If you've ever seen a really good demo and a > > really bad demo, you know what a big difference there can be. A > > screencast is basically just a recorded demo, so you need a good demo > > and a good demoer to start with. Of course, you can use editing to > > allow for multiple takes which can make things a little easier than > > doing it live, but editing is more work too, so it's a tradeoff. > > I agree 100%... > > > For a great demo, which includes ArgoUML by the way, check out Sean > > Kelly's "Getting Your Feet Wet With Plone" where he starts with a bare > > operating system, then downloads, builds, and installs Python, Zope, > > Plone, Archetypes, ArchGenXML, and ArgoUML, then uses those to build a > > time tracker web application and deploys it all *live* in under 20 > > minutes. > > http://www.archive.org/details/SeanKellyGettingYourFeetWetwithPlone > > (The ArgoUML part starts at about 11:15) > > This is actually great! But I have 2 very minor issues with it: > - The resolution of the video is a bit too poor for my shortsighted eyes. > I don't expect HDTV, but it would be great, if one could read the menus on > the > screen etc. > - Sean is a bit too quick for me. If the presentation would take 25 or 30 > mins > (with the same content), I'd understand it a bit better (I'm too slow, I > know). > > > The key thing about good demos is that they tell a story. The types of > > people who are interested in reverse engineering may be the same as > > people who are just learning UML or modeling, which implies multiple > > demos to highlight different uses of the tool. Just going through > > the various features one by one will be boring and make for a poor > > demo. > > Of course! The demo shouldn't just demonstrate features, but what you can > do with them... > > --<snip>-- > > Ciao, > Andreas > > -- > Psssst! Schon vom neuen GMX MultiMessenger gehört? > Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >