On Thu, Jul 31, 2003 at 08:21:39PM +0200, Alexander Pohoyda wrote: >David Dawes <[EMAIL PROTECTED]> writes: > >> On Thu, Jul 31, 2003 at 07:15:43AM +0200, Alexander Pohoyda wrote: >> >I believe that this is a correct way to develop geometries for >> >related keyboards and I think that it is logical to combine them into >> >one file. >> >> OK, so if I understand you correctly, we can re-add the old 'hp' file, >> and add the omnibook descriptions to it. New descriptions for other >> vendor keyboards can be added to existing files rather than creating >> new directories. > >If you decide to go this way, please let me know and I will be happy >to prepare new diffs.
I am going to do it this way. New diffs will be welcome -- thanks. >This strategy will require some re-arrangements: instead of accessing >a `hp/omnibook(us)', we'll need to do `hp(omnibook.us)' or whatever. > >Actually, we are trying to fit company/family/model/variant into >2-level structure file/section. If the existing 3-level structure is OK for company/family/model/variant, then a 2-level structure should be OK if family/model are combined into a single parameter. Currently the 'xfree86' rules file selects a geometry based solely on a 'model' name, so a single parameter is converted into a geometry description name. It's conceivable that 'layout' be added as an additional parameter to automatically select us vs intl variants. David -- David Dawes Founder/committer/developer The XFree86 Project www.XFree86.org/~dawes _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
