|
|
Status: Accepted
Owner: [hidden email] Labels: Type-Defect Priority-Medium Product-Core New issue 154 by [hidden email]: about blessing: and others http://code.google.com/p/metacello/issues/detail?id=154 Stef has a set of feature requests that he'd like included in Metacello: http://forum.world.st/about-blessing-and-others-td3865700.html |
|
|
Updates:
Labels: -Priority-Medium Priority-Critical Milestone-1.0-beta.32 Comment #1 on issue 154 by [hidden email]: about blessing: and others http://code.google.com/p/metacello/issues/detail?id=154 (No comment was entered for this change.) |
|
|
Comment #2 on issue 154 by [hidden email]: about blessing: and others http://code.google.com/p/metacello/issues/detail?id=154 Highlights of requests: === spec baseline. spec version: #development instead of: spec blessing: #baseline spec blessing: #development or: declareBaseline declareVersion: === version: instead of: versionString: load: instead of: loads: package: instead of: file: giving: spec className: 'ConfigurationOfCoolBrowser'; version: '0.6'; load: #('ALL' ); package: 'CoolBrowser-Metacello'; repository: 'http://www.example.com/CoolBrowser' ]. instead of: spec className: 'ConfigurationOfCoolBrowser'; versionString: '0.6'; loads: #('ALL' ); file: 'CoolBrowser-Metacello'; repository: 'http://www.example.com/CoolBrowser' ]. className: (Issue 161) and file: are redundant (only supplied when defaults aren't used). So the minimal spec could be: spec version: '0.6'; repository: 'http://www.example.com/CoolBrowser' ]. ------------------------------------------------------------------------ I think we can do better with explicit specification of baseline and version, basically deprecating the blessing? And we can get by with the minimal spec as well ... |
|
|
Comment #3 on issue 154 by [hidden email]: about blessing: and others http://code.google.com/p/metacello/issues/detail?id=154 Issue 161 has been merged into this issue. |
|
|
Comment #4 on issue 154 by [hidden email]: about blessing: and others http://code.google.com/p/metacello/issues/detail?id=154 sounds great! |
|
|
In reply to this post by metacello
Issue 154: about blessing: and others
http://code.google.com/p/metacello/issues/detail?id=154 This issue is now blocking issue 148. See http://code.google.com/p/metacello/issues/detail?id=148 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings |
|
|
In reply to this post by metacello
Issue 154: about blessing: and others
http://code.google.com/p/metacello/issues/detail?id=154 This issue is now blocking issue 69. See http://code.google.com/p/metacello/issues/detail?id=69 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings |
|
|
In reply to this post by metacello
Updates:
Status: Started Comment #7 on issue 154 by [hidden email]: about blessing: and others http://code.google.com/p/metacello/issues/detail?id=154 className: made optional in Metacello 1.0-beta.32 (dkh.674) |
|
|
In reply to this post by metacello
Issue 154: about blessing: and others
http://code.google.com/p/metacello/issues/detail?id=154 This issue is now blocking issue 172. See http://code.google.com/p/metacello/issues/detail?id=172 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings |
| Powered by Nabble | See how NAML generates this page |