William F. Maddock wrote: > The "Design Concept" part might wind up being the most extensive, >but would only need to be done one time, as it is going into some >detail explaining the "why" of the particular construction of >scribus, so that as things move forward it makes it easier for >users to find and learn the use of new features (because the >developers have sort of let the user into their heads to know what >they are thinking). An added bonus: I'm not sure that there are >currently any manuals that actually try to do that yet. It could >be a scribus first. :-)
I'll second the notion that this is important. Getting your head around the model the designers of software are using from 'how to' instructions, really isn't the beat way round. Cheers, J/. -- John Beardmore, MSc EDM (Open), B.A. Chem (Oxon), CMIOSH, AIEMA, MEI. Managing Director, T4 Sustainability Limited. http://www.T4sLtd.co.uk/ Carbon Trust Consultant - Energy Audit and Design Advice. Energy Efficiency Accreditation Scheme Registered Assessor. P:0845 4561332 F:0870 0522417 M:07785 563116 Skype:t4sustainability
