From: Colin T. <col...@co...> - 2005-07-13 13:43:42
|
Alistair Young wrote: >> Better to fix it now > > it ain't "broken"! True, I just meant better to change it now, before we embark on this (and all the future) template conversion efforts. > I see your point about an editor but that's the editor's problem, not > the properties files' > > Is it worth putting this to the vote as it's a lot of work. Is it a lot of work? Doesn't it just involve renaming the properties files, and the references? (Could have a default behaviour, that if the properties file isn't named at all, it looks for one with the same name as the template -- that's from The Bucket :-) Colin Who will do > it if it's seen as a problem? > > Alistair > > > On 13 Jul 2005, at 14:29, Colin Tatham wrote: > >> > why bother? hasta manyana babe. It looks good to me as is >> >> Better to fix it now rather than try do it later. >> Having 100's of properties files with the same name is *bound* to >> cause confusion at some point (like you have 3 open in your editor at >> once, and they all have the same name in the tag at the top of the >> editor?). >> >> >> Alistair Young wrote: >> >>>> Renaming the properties files? Removing the individual folders for >>>> each template? >>>> >>> why bother? hasta manyana babe. It looks good to me as is >>> Alistair >>> On 13 Jul 2005, at 13:54, Colin Tatham wrote: >>> >>>> >>>> I was actually getting a bit confused there... I didn't mean to >>>> suggest that the properties files all get added to the present >>>> templates folder, although that was what I ended up suggesting... >>>> >>>> Renaming the properties files? Removing the individual folders for >>>> each template? >>>> >>>> >>>> Colin >>>> ____________________________________ >>>> Colin Tatham >>>> VLE Team >>>> Oxford University Computing Services >>>> >>>> http://www.oucs.ox.ac.uk/ltg/vle/ >>>> http://bodington.org >>>> >>>> >>>> Colin Tatham wrote: >>>> >>>> >>>>> Alistair Young wrote: >>>>> >>>>> >>>>>> res/templates/style_default/default >>>>>> -- each template has it's own directory under default, within >>>>>> which, it's >>>>>> strings file resides. >>>>>> >>>>>> >>>>> We had a discussion here, I'll try to summarise. >>>>> (The ideas only came up when we started doing some work on the >>>>> localisation.) >>>>> - All the properties files have the same name, which makes >>>>> editing a collection of them confusing. >>>>> - Having additional folders within the folders makes it slightly >>>>> more difficult to match templates to properties files. >>>>> Would there be any problems if we: >>>>> - name properties files with the same name as the template they >>>>> refer to. >>>>> - have the properties files in the same folder as the templates. >>>>> They would appear in a listing along with the template, and any >>>>> other properties files that relate to that template. >>>>> Admittedly that means the style_default/default folder could have >>>>> loads of files in it, but that's OK innit? >>>>> Colin >>>>> ____________________________________ >>>>> Colin Tatham >>>>> VLE Team >>>>> Oxford University Computing Services >>>>> http://www.oucs.ox.ac.uk/ltg/vle/ >>>>> http://bodington.org >>>>> ------------------------------------------------------- >>>>> This SF.Net email is sponsored by the 'Do More With Dual!' >>>>> webinar happening >>>>> July 14 at 8am PDT/11am EDT. We invite you to explore the latest >>>>> in dual >>>>> core and dual graphics technology at this free one hour event >>>>> hosted by HP, AMD, and NVIDIA. To register visit http:// >>>>> www.hp.com/go/dualwebinar >>>>> _______________________________________________ >>>>> Bodington-developers mailing list >>>>> Bod...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/bodington-developers >>>>> >>>>> >>>> >>>> >>>> ------------------------------------------------------- >>>> This SF.Net email is sponsored by the 'Do More With Dual!' webinar >>>> happening >>>> July 14 at 8am PDT/11am EDT. We invite you to explore the latest >>>> in dual >>>> core and dual graphics technology at this free one hour event >>>> hosted by HP, AMD, and NVIDIA. To register visit http:// >>>> www.hp.com/ go/dualwebinar >>>> _______________________________________________ >>>> Bodington-developers mailing list >>>> Bod...@li... >>>> https://lists.sourceforge.net/lists/listinfo/bodington-developers >>>> >>>> >>> ------------------------------------------------------- >>> This SF.Net email is sponsored by the 'Do More With Dual!' webinar >>> happening >>> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in >>> dual >>> core and dual graphics technology at this free one hour event hosted >>> by HP, AMD, and NVIDIA. To register visit http:// >>> www.hp.com/go/dualwebinar >>> _______________________________________________ >>> Bodington-developers mailing list >>> Bod...@li... >>> https://lists.sourceforge.net/lists/listinfo/bodington-developers >>> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by the 'Do More With Dual!' webinar >> happening >> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual >> core and dual graphics technology at this free one hour event hosted >> by HP, AMD, and NVIDIA. To register visit http://www.hp.com/ >> go/dualwebinar >> _______________________________________________ >> Bodington-developers mailing list >> Bod...@li... >> https://lists.sourceforge.net/lists/listinfo/bodington-developers >> > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar > happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual > core and dual graphics technology at this free one hour event hosted by > HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |