We also need to standardise file extensions. .mod for modules, .dat or .log for log files, .sav for save games. The module browser should default to only showing files with these extensions to force users to stick to the convention.
--- In [email protected], "Brent Easton" <[EMAIL PROTECTED]> wrote: > > I think there is room for a bit of both. > > I want to bring a lot of information together into a cohesive front-end package and bring some structure to the whole shebang. > > At the momement, modules can be downloaded and dumped anywhere, and it is not necessarily easy to find information about what you have installed. > > I want to add additional fields into the module definition component: > > - Author > - Genre > - Number of Players > - Brief description > > that can be displayed in the front end, plus add tools for downloading modules, managing log files etc. Perhaps notification of module updates as well? > > Sort of a 'Module Browser' application. > > We can include a legacy File/Edit menu as well. > > Cheers, > Brent. > > >*********** REPLY SEPARATOR *********** > > > >On 12/09/2007 at 5:25 AM b5mith wrote: > >Nice work Brent; I'm glad you guys are thinking about this. > > > >My personal preference is for intuitive over funky. The Steam > >interface looks good but breaks a few UI design rules. I would > >personally go for a menu system with the typical File|Edit|View style > >over a custom tab and button look. > >I'm not a huge fan of re-inventing the wheel; There are good reasons > >why high end commercial apps all stick to tried and tested simple layouts. > > > >Just my 0.02! > > > >Ben > > ____________________________________________________________ > Brent Easton > Analyst/Programmer > University of Western Sydney > Email: [EMAIL PROTECTED] >
