DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=39182>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39182 ------- Additional Comments From [EMAIL PROTECTED] 2006-04-12 07:16 ------- I like the idea for the Layout class. But I see two problems with the fact that the Layout object is initialized from a configuration file. First, it requires the application developer to create a layout configuration file, in addition to default properties file (and, of course, to make sure the two are compliant with each other). This is a small issue but I suspect that this requirement might discourage 99% of the potential users of this feature. Second, since the layout of the file is not derived from the layout it had before being parsed, re-saving it may result in re-ordering of the lines in the file, thus making it harder to review the changes using diff (or CVS, for that matter). On the other hand, using a layout configuration file will enable formatting of properties added by the user, and accurate formatting of complex properties (lists, multi-lines etc). Perhaps you know of applications that make a more sophisticated use of properties files than I do, but in the applications I've seen, it is rare for an end user to make a big change to the properties file. Usually an end user would only modify a couple of properties that are specified in the file (or commented out). Same goes for configuration changes made via software. Maybe the way to go is to create the Layout class, and have it initialized from analyzing the parsed properties file. Such layout class would not be complete, but in time we can add all kinds of heuristics for it to detect things like multiline layout configuration, property groups etc. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
