Hi, Last week I made a super small project to consolidate all projects published in all metarepos. Is very simple, in the style of smalltalkhub repository list, but it shows all projects with the info their owners provided. Yes, it could be a lot better, but we do not want to lose much time with this because not far in the future (but not right now) we will put online a much better service :) You can see the catalog here: http://catalog.pharo.org <http://catalog.pharo.org/> and a JSON variant here: http://catalog.pharo.org/catalog/json <http://catalog.pharo.org/catalog/json> enjoy, Esteban
Cool!
On 01 Apr 2015, at 12:13, Esteban Lorenzano <estebanlm@gmail.com> wrote:
Hi,
Last week I made a super small project to consolidate all projects published in all metarepos. Is very simple, in the style of smalltalkhub repository list, but it shows all projects with the info their owners provided. Yes, it could be a lot better, but we do not want to lose much time with this because not far in the future (but not right now) we will put online a much better service :)
You can see the catalog here:
and a JSON variant here:
http://catalog.pharo.org/catalog/json
enjoy, Esteban
"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.
On 01 Apr 2015, at 12:53, kilon alios <kilon.alios@gmail.com> wrote:
"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.
is because thatâs the description of the version (or baseline), not the project description (thatâs the place of #catalogDescription, and thatâs why it is on class side: is more durable). cheers, Esteban
" 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.
" is because thatâs the description of the version (or baseline), not the project description (thatâs the place of #catalogDescription, and thatâs why it is on class side: is more durable). cheers, Esteban" ah ok makes sense now. Will do thanks.
Cool! At the moment I'm searching where to put a description for the projects :) I was asking myself why the link of a project opens a small project description taken from the metacello config instead just opening the project on smalltalkhub. Or from where are the projects in this list are taken? Norbert
Am 01.04.2015 um 12:13 schrieb Esteban Lorenzano <estebanlm@gmail.com>:
Hi,
Last week I made a super small project to consolidate all projects published in all metarepos. Is very simple, in the style of smalltalkhub repository list, but it shows all projects with the info their owners provided. Yes, it could be a lot better, but we do not want to lose much time with this because not far in the future (but not right now) we will put online a much better service :)
You can see the catalog here:
http://catalog.pharo.org <http://catalog.pharo.org/>
and a JSON variant here:
http://catalog.pharo.org/catalog/json <http://catalog.pharo.org/catalog/json>
enjoy, Esteban
On 01 Apr 2015, at 13:04, Norbert Hartl <norbert@hartl.name> wrote:
Cool! At the moment I'm searching where to put a description for the projects :) I was asking myself why the link of a project opens a small project description taken from the metacello config instead just opening the project on smalltalkhub. Or from where are the projects in this list are taken?
because I have no idea where the project is. I just take the configurations in the meta repos. Esteban
Norbert
Am 01.04.2015 um 12:13 schrieb Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@gmail.com>>:
Hi,
Last week I made a super small project to consolidate all projects published in all metarepos. Is very simple, in the style of smalltalkhub repository list, but it shows all projects with the info their owners provided. Yes, it could be a lot better, but we do not want to lose much time with this because not far in the future (but not right now) we will put online a much better service :)
You can see the catalog here:
http://catalog.pharo.org <http://catalog.pharo.org/>
and a JSON variant here:
http://catalog.pharo.org/catalog/json <http://catalog.pharo.org/catalog/json>
enjoy, Esteban
Very cool! This is something i've read many people saying they wanted to have. I found the quite visibly placed link 'a note to developers' very useful and will add the explained methods to my projects. Seems that the existence of #catalogDescription is not as known as the practice of defining a 'ConfigurationOf' class. On Wed, Apr 1, 2015 at 8:11 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 01 Apr 2015, at 13:04, Norbert Hartl <norbert@hartl.name> wrote:
Cool! At the moment I'm searching where to put a description for the projects :) I was asking myself why the link of a project opens a small project description taken from the metacello config instead just opening the project on smalltalkhub. Or from where are the projects in this list are taken?
because I have no idea where the project is. I just take the configurations in the meta repos.
Esteban
Norbert
Am 01.04.2015 um 12:13 schrieb Esteban Lorenzano <estebanlm@gmail.com>:
Hi,
Last week I made a super small project to consolidate all projects published in all metarepos. Is very simple, in the style of smalltalkhub repository list, but it shows all projects with the info their owners provided. Yes, it could be a lot better, but we do not want to lose much time with this because not far in the future (but not right now) we will put online a much better service :)
You can see the catalog here:
and a JSON variant here:
http://catalog.pharo.org/catalog/json
enjoy, Esteban
Le 1/4/15 18:07, Laura Risani a écrit :
Very cool! This is something i've read many people saying they wanted to have. I found the quite visibly placed link 'a note to developers' very useful and will add the explained methods to my projects. Seems that the existence of #catalogDescription is not as known as the practice of defining a 'ConfigurationOf' class.
Yes because it was an experience I did to understand how/if it was making sense to add metadata to configuration. Else versionner would support it. Now we are changing it so we prefer to invest in the new version. Stef
On Wed, Apr 1, 2015 at 8:11 AM, Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@gmail.com>> wrote:
On 01 Apr 2015, at 13:04, Norbert Hartl <norbert@hartl.name <mailto:norbert@hartl.name>> wrote:
Cool! At the moment I'm searching where to put a description for the projects :) I was asking myself why the link of a project opens a small project description taken from the metacello config instead just opening the project on smalltalkhub. Or from where are the projects in this list are taken?
because I have no idea where the project is. I just take the configurations in the meta repos.
Esteban
Norbert
Am 01.04.2015 um 12:13 schrieb Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@gmail.com>>:
Hi,
Last week I made a super small project to consolidate all projects published in all metarepos. Is very simple, in the style of smalltalkhub repository list, but it shows all projects with the info their owners provided. Yes, it could be a lot better, but we do not want to lose much time with this because not far in the future (but not right now) we will put online a much better service :)
You can see the catalog here:
http://catalog.pharo.org <http://catalog.pharo.org/>
and a JSON variant here:
http://catalog.pharo.org/catalog/json
enjoy, Esteban
Thanks Esteban. Its a worthwhile stopgap until the new service. At a minimum its visibility should encourage developers to supply the required information, so its more complete when the new service arrives. cheers -ben On Thu, Apr 2, 2015 at 12:57 AM, stepharo <stepharo@free.fr> wrote:
Le 1/4/15 18:07, Laura Risani a écrit :
Very cool! This is something i've read many people saying they wanted to have. I found the quite visibly placed link 'a note to developers' very useful and will add the explained methods to my projects. Seems that the existence of #catalogDescription is not as known as the practice of defining a 'ConfigurationOf' class.
Yes because it was an experience I did to understand how/if it was making sense to add metadata to configuration. Else versionner would support it. Now we are changing it so we prefer to invest in the new version.
Stef
On Wed, Apr 1, 2015 at 8:11 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 01 Apr 2015, at 13:04, Norbert Hartl <norbert@hartl.name> wrote:
Cool! At the moment I'm searching where to put a description for the projects :) I was asking myself why the link of a project opens a small project description taken from the metacello config instead just opening the project on smalltalkhub. Or from where are the projects in this list are taken?
because I have no idea where the project is. I just take the configurations in the meta repos.
Esteban
Norbert
Am 01.04.2015 um 12:13 schrieb Esteban Lorenzano <estebanlm@gmail.com>:
Hi,
Last week I made a super small project to consolidate all projects published in all metarepos. Is very simple, in the style of smalltalkhub repository list, but it shows all projects with the info their owners provided. Yes, it could be a lot better, but we do not want to lose much time with this because not far in the future (but not right now) we will put online a much better service :)
You can see the catalog here:
and a JSON variant here:
http://catalog.pharo.org/catalog/json
enjoy, Esteban
Hi!! This an excellent idea. How to provide a description for my project? Alexandre
Le 1 avr. 2015 à 07:13, Esteban Lorenzano <estebanlm@gmail.com> a écrit :
Hi,
Last week I made a super small project to consolidate all projects published in all metarepos. Is very simple, in the style of smalltalkhub repository list, but it shows all projects with the info their owners provided. Yes, it could be a lot better, but we do not want to lose much time with this because not far in the future (but not right now) we will put online a much better service :)
You can see the catalog here:
and a JSON variant here:
http://catalog.pharo.org/catalog/json
enjoy, Esteban
read the page. there is an explanation. Le 4/4/15 14:47, Alexandre Bergel a écrit :
Hi!!
This an excellent idea. How to provide a description for my project?
Alexandre
Le 1 avr. 2015 à 07:13, Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@gmail.com>> a écrit :
Hi,
Last week I made a super small project to consolidate all projects published in all metarepos. Is very simple, in the style of smalltalkhub repository list, but it shows all projects with the info their owners provided. Yes, it could be a lot better, but we do not want to lose much time with this because not far in the future (but not right now) we will put online a much better service :)
You can see the catalog here:
and a JSON variant here:
http://catalog.pharo.org/catalog/json
enjoy, Esteban
participants (8)
-
Alexandre Bergel -
Ben Coman -
Esteban Lorenzano -
kilon alios -
Laura Risani -
Norbert Hartl -
stepharo -
Sven Van Caekenberghe