Feature Requests item #1452792, was opened at 2006-03-17 14:16 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684978&aid=1452792&group_id=119783
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: all projects Group: 1.2 Status: Open Priority: 5 Submitted By: Jonathan Locke (jonathanlocke) Assigned to: Nobody/Anonymous (nobody) Summary: Member grouping and public API readability Initial Comment: I think we should sort class members on access visibility. If we do this, a user can just scroll through the public API in the source code and read it like a book. I would prefer that the methods in each access level were sorted alphabetically, but that's not so important if people want to manually maintain some other scheme. What doesn't work for me right now is that a method like Component.isEnableAllowed() is stuck way at the bottom of Component where someone scrolling through the public methods at the top will never find it. I'd like us to adopt some kind of automated method grouping strategy at least for 1.3, but preferrably for 1.2. It's really quite hard to see the API in the source code right now. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684978&aid=1452792&group_id=119783 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
