okay, i have a stupid question..
i am reading SBE, and trying to figure out how to to get my current seaside project into my repository..
i made a repository at squeaksource, and that looks okay.. i can log into it..
but i can't figure out how to package up my code classes (it's all in one category) and put it into my monticello package..
any ideas?
thanks!
___ peace, sergio photographer, journalist, visionary www.village-buzz.com
On Oct 31, 2008, at 9:39 AM, sergio wrote:
okay, i have a stupid question..
i am reading SBE, and trying to figure out how to to get my current seaside project into my repository..
i made a repository at squeaksource, and that looks okay.. i can log into it..
but i can't figure out how to package up my code classes (it's all in one category) and put it into my monticello package..
any ideas?
I have notes on doing this here.
http://www.ociweb.com/mark/programming/Smalltalk.html#Monticello
If it's not clear, let me know and I'll improve it.
--- Mark Volkmann
On Oct 31, 2008, at 11:02 AM, Mark Volkmann wrote:
http://www.ociweb.com/mark/programming/Smalltalk.html#Monticello
If it's not clear, let me know and I'll improve it.
okay, i think i am just being dense.
i am not sure how to create a package out of the classes i have just written..
everything else seems to make sense..
___ peace, sergio photographer, journalist, visionary www.village-buzz.com
On Oct 31, 2008, at 12:45 PM, sergio wrote:
On Oct 31, 2008, at 11:02 AM, Mark Volkmann wrote:
http://www.ociweb.com/mark/programming/Smalltalk.html#Monticello
If it's not clear, let me know and I'll improve it.
okay, i think i am just being dense.
i am not sure how to create a package out of the classes i have just written..
everything else seems to make sense..
I am guilty of glossing over that part in my notes. ;-) A good explanation of this is on page 125 in "Squeak By Example". Here's the relevant part. For your case its likely that only the first part matters ... just classes in a given class category that you created.
A package named Foo contains: 1. all class definitions of classes in the category Foo, or in categories with names starting with Foo-, and 2. all method definitions in any class in a protocol named *foo or whose name starts with *foo- (when performing this name comparison, the case of the letters in the names is ignored), and 3. all methods in classes in the category Foo, or in a category whose name starts with Foo-, except for those methods in protocols whose names start with * .
--- Mark Volkmann
On Oct 31, 2008, at 2:24 PM, Mark Volkmann wrote:
A package named Foo contains:
okay, i got it.. this makes sense..
my only other question is.. how do you handle dependencies?
if i have a set of classes that require two or three other sets of classes.. how do i tell that to monticello?
___ peace, sergio photographer, journalist, visionary www.village-buzz.com
On Oct 31, 2008, at 1:28 PM, sergio wrote:
On Oct 31, 2008, at 2:24 PM, Mark Volkmann wrote:
A package named Foo contains:
okay, i got it.. this makes sense..
my only other question is.. how do you handle dependencies?
if i have a set of classes that require two or three other sets of classes.. how do i tell that to monticello?
Do you mean that the classes in one category depend on classes in another? Without using hyphenated names that start with the same prefix, those would be separate packages in Monticello. I don't know how to make one package depend on another, but I'd like to learn. Maybe someone else will tell us.
--- Mark Volkmann
beginners@lists.squeakfoundation.org