Idea: Pharo application scaffold kickstarter

Hi all

I get used to Pharo more and more, and I am using it for all my new
customer projects. So far, all of my (seaside) applications are all
architectured around some of my best practices and architecturally look
all pretty the same.

I was wondering if there is something existing to help me getting
kickstarted with a new customer application in Pharo, instead of
repeatingly copy/pasting manually from another project? Something for
kickstarting a new application scaffold, based on a "best practices
application template" (to be chosen out of many from a repository
locally or even remotely shared from other developers).

Something like a "Pharo application scaffold kickstarter".

I did some research and did not find anything so far. What are your
thoughts around this topic?

Cheers,
Andreas

--
Andreas Brodbeck
www.mindclue.ch

Am 27.05.15 um 14:49 schrieb Damien Pollet:> I have the same itch for
simple images; get.pharo.org and PharoLauncher
 > nearly scratch it, except that I work mostly from the terminal.
 >
 > For instance I'd like to be able to quickly rebuild an image from a
 > configuration, with some workspaces, setting up some MC repositories,
etc.
 > For seaside apps I guess you'd want some standard directories and
files to
 > be created as well. Could you document your best practices?

For me the tool would need to do the following:

- Ask for the template from a local repository (or remote repository).

- The template can be any existing smalltalk project, which has a
metacello configuration.

- Take that template and rename all class prefixes to a new one. For
example TPLObject (template) to ABCObject (in a customer project called
"ABC").

- Create all those classes in their renamed categories (From
"Template-Models" to "ABC-Models")

- Create an entry in monticello

- Create a metacello configuration and load it to load all the
dependencies (i.e. Seaside, etc.)

- Create some static folders and files (for instance CSS files in a
"web_root" folder)

- Run a template specific smalltalk script before and after the
generation. (To show some info or make decisions)


But back to your question: The "best practices" would be in the
templates, actually. Every developer could store his preferred templates
or even share them. For me this would be for example a template named
"Standard web application: Seaside, no database" which would include the
following: a ABCDatabase (holds all persisted collections of model
objects), ABCModelObject (base class for model objects), ABCHelper (misc
tiny utility methods), ABCMailer (sending mails), ABCWaComponent
(seaside component base class), ABCDataMigrator (for storing deployment
migration steps), and so on...

 >
 > On 27 May 2015 at 13:37, Andreas Brodbeck
<[hidden email]> wrote:
 >
 >> Hi all
 >>
 >> [...]

--
Andreas Brodbeck
www.mindclue.ch

Damien Pollet-2 wrote

I have the same itch for simple images; get.pharo.org and PharoLauncher
nearly scratch it, except that I work mostly from the terminal.
...
Could you document your best practices?

Could you use a startup script as a springboard? In the script, simply load class(es) to setup your images and then use --eval from the CL...

Le 27/5/15 13:37, Andreas Brodbeck a écrit :
> Hi all
>
> I get used to Pharo more and more, and I am using it for all my new
> customer projects. So far, all of my (seaside) applications are all
> architectured around some of my best practices and architecturally
> look all pretty the same.

Excellent news!!!
Do you have some success stories for the pharo web site?
an we make some ads for you :)
>
> I was wondering if there is something existing to help me getting
> kickstarted with a new customer application in Pharo, instead of
> repeatingly copy/pasting manually from another project? Something for
> kickstarting a new application scaffold, based on a "best practices
> application template" (to be chosen out of many from a repository
> locally or even remotely shared from other developers).
>
> Something like a "Pharo application scaffold kickstarter".

I do not have the experience you have :)
So if you
     take one of your app
     remove the part that are not generic
     publish it
     then you will have a first version of the scaffold.

other people may
     help
     give you feedback

Stef

BTW Andreas are you attending ESUG? because this is not that far from
Switzerland and you can meet a lot of Pharoers.

Stef

Le 27/5/15 13:37, Andreas Brodbeck a écrit :