Smalltalk
›
Frameworks & Tools
›
Monticello, Metacello ...
›
Metacello
Login
Register
Search
everywhere
only in this topic
Advanced Search
Issue 166 in metacello: Convention on platform package naming (FAQ)
‹
Previous Topic
Next Topic
›
Classic
List
Threaded
♦
♦
Locked
2 messages
Options
Loading...
Subscribe via email
Move topic
Pin topic
Unpin topic
Lock topic
Unlock topic
Delete this topic
Delete this topic
Change title and meta tags
Embed post
Permalink
metacello
Reply
|
Threaded
Open this post in threaded view
♦
♦
|
More
Loading...
Reply to author
Edit post
Move post
Delete this post
Delete this post and replies
Change post date
Print post
Permalink
Raw mail
Jan 03, 2012; 7:45pm
Issue 166 in metacello: Convention on platform package naming (FAQ)
Status: Accepted
Owner:
[hidden email]
Labels: Type-Feature Priority-Medium Product-Core
New issue 166 by
[hidden email]
: Convention on platform package
naming (FAQ)
http://code.google.com/p/metacello/issues/detail?id=166
Sean DeNigris is satisifed with the naming convention he describes in this
post[1]. Probably worth documenting this as FAQ ...
[1]
http://forum.world.st/Convention-on-platform-e-g-Pharo1-3-vs-Pharo1-4-package-naming-tp4167422p4170616.html
metacello
Reply
|
Threaded
Open this post in threaded view
♦
♦
|
More
Loading...
Reply to author
Edit post
Move post
Delete this post
Delete this post and replies
Change post date
Print post
Permalink
Raw mail
Jan 18, 2012; 9:06pm
Re: Issue 166 in metacello: Convention on platform package naming (FAQ)
Updates:
Labels: Milestone-1.0-beta.32
Comment #1 on issue 166 by
[hidden email]
: Convention on platform
package naming (FAQ)
http://code.google.com/p/metacello/issues/detail?id=166
(No comment was entered for this change.)
Free forum by Nabble
Edit this page