"yes, check “a note to developers” link :)"
>
yeap thats an obvious one, should have clicked that in the first place.
Question: I see you ask for dedicate methods. In this case
catalogDescription . Is it really necessary , metacello spec already offers
sped description: which my project already takes advantage of for example
-----------------------------------------------------------------------------
<version: '0.1' imports: #('0.2-baseline' )>
spec for: #'common' do: [
spec blessing: #'stable'.
spec description: 'version 0.1
This is 0.1 the first stable release of Ephestos. This release contains the
following
-a socket client bridge for sending and receiving messages from Blender
which acts as a socket server
- a sendMessage: message to send python command as string to Blender to be
executed
- a python parser that allows the pharo syntax to be used to parse to a
python command for simple things like calling instance and class method and
assigning class and instance variables
- a getValue: message for reading python values from variables
- support for triggering the pharo dedugger on python error
- support for sending multiple lines of python code in a single message'.
spec author: 'kilonAlios'.
spec timestamp: '9/20/2014 20:15'.
spec package: 'Ephestos' with: 'Ephestos-kilonAlios.16'. ].
----------------------------------------------------------------------------------------------------
I dont mind defining a separate method, I am just curious.
" they will think I suck at design"
good Design , is like good code, needs time. Loads of time. Time you dont
have and is understandable. Still its a very useful to have a project
catalogue and thank you.
