January 2014 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Pharo private develoment

by Benjamin

Smalltalkhub private project or bitbucket And I deployed my own Jenkins. Itâs as complicated as `sudo apt-get install jenkins` Ben On 01 Jan 2014, at 19:26, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Pharo as a community has support to use its CI server, among other > goodies such as SmalltalkHub. > > But what if your code is not public and you want to have a central > repository and continuous builds? > > Has anybody ever wrote a guide to develop with Pharo in the context of > private development? > > So far I managed to work with a file based repo and a set of > workspaces to create a new working image or to prepare it for > deployment. But I want to automate it as much as I can. > > Regards! > > Esteban A. Maringolo >

Jan. 2, 2014

Re: [Pharo-users] Pharo private develoment

by Esteban Lorenzano

On 02 Jan 2014, at 13:42, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 02.01.2014 um 13:22 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > >> >> On 02 Jan 2014, at 12:25, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> >>> Am 02.01.2014 um 11:57 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >>> >>>> >>>> On 02 Jan 2014, at 11:49, Norbert Hartl <norbert(a)hartl.name> wrote: >>>> >>>>> >>>>> Am 01.01.2014 um 19:26 schrieb Esteban A. Maringolo <emaringolo(a)gmail.com>: >>>>> >>>>>> Pharo as a community has support to use its CI server, among other >>>>>> goodies such as SmalltalkHub. >>>>>> >>>>>> But what if your code is not public and you want to have a central >>>>>> repository and continuous builds? >>>>>> >>>>>> Has anybody ever wrote a guide to develop with Pharo in the context of >>>>>> private development? >>>>>> >>>>>> So far I managed to work with a file based repo and a set of >>>>>> workspaces to create a new working image or to prepare it for >>>>>> deployment. But I want to automate it as much as I can. >>>>>> >>>>> I do what you want to do. I have a central server that I use for code storage and for the CI builds. Have a look at [1]. There you can read how you can easily create a http repository for monticello. I just create sub directories for every project on my server and the rest just works. >>>>> The next step would be to install jenkins and add [2]. The jenkins server then just uses the http repository you created before. >>>>> If you need help on this just ask. >>>> >>>> I use filetree and bitbucket for my private projects, and I use also metacello to build with them. >>> >>> I still didnât find the time to look into filetree. It is yet another thing to learn. Can you commit to bitbucket from within pharo? And I use metacello, too, for building my projects. >> >> is just another mc repository type, so no need to learn much. >> but you have a second step, because you do your âcommitsâ to a local repository, then you do the actual commit/push using source tree or command line. Is a bit annoying, but wellâ¦ at least all the authorisation stuff is made by others :) >> also, Thierry is doing gitfiletree so it will be better soon :) > > So, good to wait and use other stuff, hehe :) > >> >>> >>>> if you do not want to use file tree format, you can use ftp or even dropbox :) >>> >>> That might raise some difficulties integrating that into a jenkins setup. And to be honest I would avoid FTP where possible, there are other caveates with it and it has no advantage over http. >> >> I worked with ftp without any problem. Anyway, itâs your choice :) >> >>> >>>> there is no need to make anything different on your private development than you do in your public ones. >>>> >>> It would be good if that would be the case. But all things that are public accessible are not necessarily accessible in a private context. You chose bitbucket which offers private repos. I chose to install my own WebDAV server for mimicking the same. But that doesnât work in all the contextes someone might work in. >> >> like what? using filetree you delegate the authentication problemsâ¦ so if you can reach the place from command line, you avoid the problem at zero cost. >> > How do you give your jenkins server permission to get the sources from bitbucket. Having passwords for bitbucket or store the key somewhere on a server? you generate a credential in jenkins, and upload it to bitbucket >>> >>>> ah, and scripts from Lukas are very outdated (I mean, a LOT). >>>> is a lot easier to take http://ci.inria.fr/pharo-contribution (any job there) as an example on how to configure a jenkins job in few lines. >>>> >>> Well, then I want to let you know that Iâm using those scripts happily for years. What do I get from upgrading? I donât care about a few lines because I have my workflow. Having the doubled amount of lines doesnât make it worse. >> >> Maybe. People was using happily lots of things for years, yet things change. Improvement does not means always âold does not workâ, sometimes is ânewer is betterâ. >> New process is a lot simpler and does not require any external scriptâ¦ >> >> New process you just need to do: >> >> wget --quiet -O - get.pharo.org/30+vm | bash >> ./pharo Pharo.image config http://www.smalltalkhub.com/mc/Pier/Pier3/main ConfigurationOfPier3 --install=$VERSION --group=Tests >> ./pharo $JOB_NAME.image test --junit-xml-output "Pier.*" >> >> to install a configuration and run the testsâ¦ you cannot tell me that this is not an improvement, even if you already know how to use the older scripts. >> > I canât see what it does different to my approach. Donât get me wrong I like it when things become easier. But Iâm also in the need to plan the time to invest. I have a workflow and I cannot see anything that is better in your approach. So why invest the time and risk something not working? To me this is more like "if it ain't broke don't fix itâ. > But you are right, taking Estebans view it wouldnât be a good idea to learn an older workflow if a newer and easier is in place. thatâs my point :) > > Norbert > >>> >>> So I read his inquiry that he is willing to build his on stuff. The apache config in my post is nearly a drop-in solution. Having that you just use monticello as you (most likely) always did. Having an CI server on your own machine (easy to install) gives you the control you need and you can skip authorization settings between http repo and jenkins server which makes not only building easier but also publishing results without having the need to go over them and remove all sensible data. I would be glad if you would describe a private development workflow in detail. Without that it is hard to spot the drawbacks in your approach ;) >>> >>> Norbert >>> >>> >>>>> >>>>> Norbert >>>>> >>>>> [1] http://norbert.hartl.name/blog/2009/06/08/public-monticello-repository/ >>>>> [2] https://github.com/renggli/builder

Jan. 2, 2014

Re: [Pharo-users] Pharo private develoment

by Norbert Hartl

Am 02.01.2014 um 13:22 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > On 02 Jan 2014, at 12:25, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> Am 02.01.2014 um 11:57 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> >>> On 02 Jan 2014, at 11:49, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>>> >>>> Am 01.01.2014 um 19:26 schrieb Esteban A. Maringolo <emaringolo(a)gmail.com>: >>>> >>>>> Pharo as a community has support to use its CI server, among other >>>>> goodies such as SmalltalkHub. >>>>> >>>>> But what if your code is not public and you want to have a central >>>>> repository and continuous builds? >>>>> >>>>> Has anybody ever wrote a guide to develop with Pharo in the context of >>>>> private development? >>>>> >>>>> So far I managed to work with a file based repo and a set of >>>>> workspaces to create a new working image or to prepare it for >>>>> deployment. But I want to automate it as much as I can. >>>>> >>>> I do what you want to do. I have a central server that I use for code storage and for the CI builds. Have a look at [1]. There you can read how you can easily create a http repository for monticello. I just create sub directories for every project on my server and the rest just works. >>>> The next step would be to install jenkins and add [2]. The jenkins server then just uses the http repository you created before. >>>> If you need help on this just ask. >>> >>> I use filetree and bitbucket for my private projects, and I use also metacello to build with them. >> >> I still didnât find the time to look into filetree. It is yet another thing to learn. Can you commit to bitbucket from within pharo? And I use metacello, too, for building my projects. > > is just another mc repository type, so no need to learn much. > but you have a second step, because you do your âcommitsâ to a local repository, then you do the actual commit/push using source tree or command line. Is a bit annoying, but wellâ¦ at least all the authorisation stuff is made by others :) > also, Thierry is doing gitfiletree so it will be better soon :) So, good to wait and use other stuff, hehe :) > >> >>> if you do not want to use file tree format, you can use ftp or even dropbox :) >> >> That might raise some difficulties integrating that into a jenkins setup. And to be honest I would avoid FTP where possible, there are other caveates with it and it has no advantage over http. > > I worked with ftp without any problem. Anyway, itâs your choice :) > >> >>> there is no need to make anything different on your private development than you do in your public ones. >>> >> It would be good if that would be the case. But all things that are public accessible are not necessarily accessible in a private context. You chose bitbucket which offers private repos. I chose to install my own WebDAV server for mimicking the same. But that doesnât work in all the contextes someone might work in. > > like what? using filetree you delegate the authentication problemsâ¦ so if you can reach the place from command line, you avoid the problem at zero cost. > How do you give your jenkins server permission to get the sources from bitbucket. Having passwords for bitbucket or store the key somewhere on a server? >> >>> ah, and scripts from Lukas are very outdated (I mean, a LOT). >>> is a lot easier to take http://ci.inria.fr/pharo-contribution (any job there) as an example on how to configure a jenkins job in few lines. >>> >> Well, then I want to let you know that Iâm using those scripts happily for years. What do I get from upgrading? I donât care about a few lines because I have my workflow. Having the doubled amount of lines doesnât make it worse. > > Maybe. People was using happily lots of things for years, yet things change. Improvement does not means always âold does not workâ, sometimes is ânewer is betterâ. > New process is a lot simpler and does not require any external scriptâ¦ > > New process you just need to do: > > wget --quiet -O - get.pharo.org/30+vm | bash > ./pharo Pharo.image config http://www.smalltalkhub.com/mc/Pier/Pier3/main ConfigurationOfPier3 --install=$VERSION --group=Tests > ./pharo $JOB_NAME.image test --junit-xml-output "Pier.*" > > to install a configuration and run the testsâ¦ you cannot tell me that this is not an improvement, even if you already know how to use the older scripts. > I canât see what it does different to my approach. Donât get me wrong I like it when things become easier. But Iâm also in the need to plan the time to invest. I have a workflow and I cannot see anything that is better in your approach. So why invest the time and risk something not working? To me this is more like "if it ain't broke don't fix itâ. But you are right, taking Estebans view it wouldnât be a good idea to learn an older workflow if a newer and easier is in place. Norbert >> >> So I read his inquiry that he is willing to build his on stuff. The apache config in my post is nearly a drop-in solution. Having that you just use monticello as you (most likely) always did. Having an CI server on your own machine (easy to install) gives you the control you need and you can skip authorization settings between http repo and jenkins server which makes not only building easier but also publishing results without having the need to go over them and remove all sensible data. I would be glad if you would describe a private development workflow in detail. Without that it is hard to spot the drawbacks in your approach ;) >> >> Norbert >> >> >>>> >>>> Norbert >>>> >>>> [1] http://norbert.hartl.name/blog/2009/06/08/public-monticello-repository/ >>>> [2] https://github.com/renggli/builder

Jan. 2, 2014

Re: [Pharo-users] Pharo private develoment

by Esteban Lorenzano

On 02 Jan 2014, at 12:25, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 02.01.2014 um 11:57 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > >> >> On 02 Jan 2014, at 11:49, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> >>> Am 01.01.2014 um 19:26 schrieb Esteban A. Maringolo <emaringolo(a)gmail.com>: >>> >>>> Pharo as a community has support to use its CI server, among other >>>> goodies such as SmalltalkHub. >>>> >>>> But what if your code is not public and you want to have a central >>>> repository and continuous builds? >>>> >>>> Has anybody ever wrote a guide to develop with Pharo in the context of >>>> private development? >>>> >>>> So far I managed to work with a file based repo and a set of >>>> workspaces to create a new working image or to prepare it for >>>> deployment. But I want to automate it as much as I can. >>>> >>> I do what you want to do. I have a central server that I use for code storage and for the CI builds. Have a look at [1]. There you can read how you can easily create a http repository for monticello. I just create sub directories for every project on my server and the rest just works. >>> The next step would be to install jenkins and add [2]. The jenkins server then just uses the http repository you created before. >>> If you need help on this just ask. >> >> I use filetree and bitbucket for my private projects, and I use also metacello to build with them. > > I still didnât find the time to look into filetree. It is yet another thing to learn. Can you commit to bitbucket from within pharo? And I use metacello, too, for building my projects. is just another mc repository type, so no need to learn much. but you have a second step, because you do your âcommitsâ to a local repository, then you do the actual commit/push using source tree or command line. Is a bit annoying, but wellâ¦ at least all the authorisation stuff is made by others :) also, Thierry is doing gitfiletree so it will be better soon :) > >> if you do not want to use file tree format, you can use ftp or even dropbox :) > > That might raise some difficulties integrating that into a jenkins setup. And to be honest I would avoid FTP where possible, there are other caveates with it and it has no advantage over http. I worked with ftp without any problem. Anyway, itâs your choice :) > >> there is no need to make anything different on your private development than you do in your public ones. >> > It would be good if that would be the case. But all things that are public accessible are not necessarily accessible in a private context. You chose bitbucket which offers private repos. I chose to install my own WebDAV server for mimicking the same. But that doesnât work in all the contextes someone might work in. like what? using filetree you delegate the authentication problemsâ¦ so if you can reach the place from command line, you avoid the problem at zero cost. > >> ah, and scripts from Lukas are very outdated (I mean, a LOT). >> is a lot easier to take http://ci.inria.fr/pharo-contribution (any job there) as an example on how to configure a jenkins job in few lines. >> > Well, then I want to let you know that Iâm using those scripts happily for years. What do I get from upgrading? I donât care about a few lines because I have my workflow. Having the doubled amount of lines doesnât make it worse. Maybe. People was using happily lots of things for years, yet things change. Improvement does not means always âold does not workâ, sometimes is ânewer is betterâ. New process is a lot simpler and does not require any external scriptâ¦ New process you just need to do: wget --quiet -O - get.pharo.org/30+vm | bash ./pharo Pharo.image config http://www.smalltalkhub.com/mc/Pier/Pier3/main ConfigurationOfPier3 --install=$VERSION --group=Tests ./pharo $JOB_NAME.image test --junit-xml-output "Pier.*" to install a configuration and run the testsâ¦ you cannot tell me that this is not an improvement, even if you already know how to use the older scripts. > > So I read his inquiry that he is willing to build his on stuff. The apache config in my post is nearly a drop-in solution. Having that you just use monticello as you (most likely) always did. Having an CI server on your own machine (easy to install) gives you the control you need and you can skip authorization settings between http repo and jenkins server which makes not only building easier but also publishing results without having the need to go over them and remove all sensible data. I would be glad if you would describe a private development workflow in detail. Without that it is hard to spot the drawbacks in your approach ;) > > Norbert > > >>> >>> Norbert >>> >>> [1] http://norbert.hartl.name/blog/2009/06/08/public-monticello-repository/ >>> [2] https://github.com/renggli/builder

Jan. 2, 2014

Re: [Pharo-users] Pharo private develoment

by Norbert Hartl

Am 02.01.2014 um 11:57 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > On 02 Jan 2014, at 11:49, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> Am 01.01.2014 um 19:26 schrieb Esteban A. Maringolo <emaringolo(a)gmail.com>: >> >>> Pharo as a community has support to use its CI server, among other >>> goodies such as SmalltalkHub. >>> >>> But what if your code is not public and you want to have a central >>> repository and continuous builds? >>> >>> Has anybody ever wrote a guide to develop with Pharo in the context of >>> private development? >>> >>> So far I managed to work with a file based repo and a set of >>> workspaces to create a new working image or to prepare it for >>> deployment. But I want to automate it as much as I can. >>> >> I do what you want to do. I have a central server that I use for code storage and for the CI builds. Have a look at [1]. There you can read how you can easily create a http repository for monticello. I just create sub directories for every project on my server and the rest just works. >> The next step would be to install jenkins and add [2]. The jenkins server then just uses the http repository you created before. >> If you need help on this just ask. > > I use filetree and bitbucket for my private projects, and I use also metacello to build with them. I still didnât find the time to look into filetree. It is yet another thing to learn. Can you commit to bitbucket from within pharo? And I use metacello, too, for building my projects. > if you do not want to use file tree format, you can use ftp or even dropbox :) That might raise some difficulties integrating that into a jenkins setup. And to be honest I would avoid FTP where possible, there are other caveates with it and it has no advantage over http. > there is no need to make anything different on your private development than you do in your public ones. > It would be good if that would be the case. But all things that are public accessible are not necessarily accessible in a private context. You chose bitbucket which offers private repos. I chose to install my own WebDAV server for mimicking the same. But that doesnât work in all the contextes someone might work in. > ah, and scripts from Lukas are very outdated (I mean, a LOT). > is a lot easier to take http://ci.inria.fr/pharo-contribution (any job there) as an example on how to configure a jenkins job in few lines. > Well, then I want to let you know that Iâm using those scripts happily for years. What do I get from upgrading? I donât care about a few lines because I have my workflow. Having the doubled amount of lines doesnât make it worse. So I read his inquiry that he is willing to build his on stuff. The apache config in my post is nearly a drop-in solution. Having that you just use monticello as you (most likely) always did. Having an CI server on your own machine (easy to install) gives you the control you need and you can skip authorization settings between http repo and jenkins server which makes not only building easier but also publishing results without having the need to go over them and remove all sensible data. I would be glad if you would describe a private development workflow in detail. Without that it is hard to spot the drawbacks in your approach ;) Norbert >> >> Norbert >> >> [1] http://norbert.hartl.name/blog/2009/06/08/public-monticello-repository/ >> [2] https://github.com/renggli/builder >> >

Jan. 2, 2014

Re: [Pharo-users] Pharo private develoment

by Esteban Lorenzano

On 02 Jan 2014, at 11:49, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 01.01.2014 um 19:26 schrieb Esteban A. Maringolo <emaringolo(a)gmail.com>: > >> Pharo as a community has support to use its CI server, among other >> goodies such as SmalltalkHub. >> >> But what if your code is not public and you want to have a central >> repository and continuous builds? >> >> Has anybody ever wrote a guide to develop with Pharo in the context of >> private development? >> >> So far I managed to work with a file based repo and a set of >> workspaces to create a new working image or to prepare it for >> deployment. But I want to automate it as much as I can. >> > I do what you want to do. I have a central server that I use for code storage and for the CI builds. Have a look at [1]. There you can read how you can easily create a http repository for monticello. I just create sub directories for every project on my server and the rest just works. > The next step would be to install jenkins and add [2]. The jenkins server then just uses the http repository you created before. > If you need help on this just ask. I use filetree and bitbucket for my private projects, and I use also metacello to build with them. if you do not want to use file tree format, you can use ftp or even dropbox :) there is no need to make anything different on your private development than you do in your public ones. ah, and scripts from Lukas are very outdated (I mean, a LOT). is a lot easier to take http://ci.inria.fr/pharo-contribution (any job there) as an example on how to configure a jenkins job in few lines. > > Norbert > > [1] http://norbert.hartl.name/blog/2009/06/08/public-monticello-repository/ > [2] https://github.com/renggli/builder >

Jan. 2, 2014

Re: [Pharo-users] Pharo private develoment

by Norbert Hartl

Am 01.01.2014 um 19:26 schrieb Esteban A. Maringolo <emaringolo(a)gmail.com>: > Pharo as a community has support to use its CI server, among other > goodies such as SmalltalkHub. > > But what if your code is not public and you want to have a central > repository and continuous builds? > > Has anybody ever wrote a guide to develop with Pharo in the context of > private development? > > So far I managed to work with a file based repo and a set of > workspaces to create a new working image or to prepare it for > deployment. But I want to automate it as much as I can. > I do what you want to do. I have a central server that I use for code storage and for the CI builds. Have a look at [1]. There you can read how you can easily create a http repository for monticello. I just create sub directories for every project on my server and the rest just works. The next step would be to install jenkins and add [2]. The jenkins server then just uses the http repository you created before. If you need help on this just ask. Norbert [1] http://norbert.hartl.name/blog/2009/06/08/public-monticello-repository/ [2] https://github.com/renggli/builder

Jan. 2, 2014

Re: [Pharo-users] Fwd: Re: Pharo on Android - is it available?

by Esteban A. Maringolo

When you talk about Amber on Android you must think of middle to high end hardware. Even if it's a tablet. On a mid-low end device it will be completely unusable. It is not an Amber only thing, it also applies to any other JS based app. Android's Webview is 3x slower than Chrome, among other quirks that make the interaction unpleasant. One year ago I considered using Amber, then bare JS wrapped with PhoneGap, but ended up using native development, because otherwise the app was going to be unresponsive, and the CPU required would consume the battery in a few hours. Regards, ps: An app like Dr. Geo is a totally different story.

Jan. 1, 2014

Re: [Pharo-users] Fwd: Re: Pharo on Android - is it available?

by kilon alios

yes sorry for forgetting about the link. One nice thing about amber is that pharo libraries are being ported to it, like Athens and Roassal and also it specifically focus on pharo. It also shows the level of compatibility between pharo and amber. The disadvantage of amber is that you have to learn javascript and hmtl because this is where everything is based. But then making browser based apps without knowing javascript / hmtl / css is generally not advisable. But in the end of the day, there is no such thing as ideal solution you just pick the choice that fits your needs and wants better and dive into it. Personally I am still in a bit of dilema for my project do I go full pharo or do i use amber for front end and pharo for backend, or just amber etc. But the thing is that unless you explore your options thoroughly you cant draw definite conclusion and you cannot even rely on other people's opinion too much because they have different priorities from you. So I would say have it a go and decide for yourself. Coding like everything else is an exploration and continuous learning experience. On Wed, Jan 1, 2014 at 8:12 PM, PBK Research <peter(a)pbkresearch.co.uk>wrote: > Hilaire (and Dmitry) > > Many thanks for your efforts on my behalf. I have looked at the CogDroid > page, but was discouraged by the prominent warning that "This project is > currently disabled." I am not an expert in combining VM files and images; > if > it involves anything more complicated than downloading a one-click image, > it > is beyond my ability. I think the comments on the SqueakVM-tablet site are > unduly optimistic. > > For the time being I shall follow up the helpful comments from kilon alios > and others that Amber Smalltalk may be the way to go. > > Thanks again > > Peter Kenny > > -----Original Message----- > From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf > Of > Hilaire Fernandes > Sent: 01 January 2014 16:26 > To: pharo-users(a)lists.pharo.org > Subject: [Pharo-users] Fwd: Re: Pharo on Android - is it available? > > Forwarding this message from Dmitry. > > Hilaire > > > -------- Message original -------- > Sujet: Re: Pharo on Android - is it available? > Date : Wed, 1 Jan 2014 10:15:07 -0500 > De : Dmitry Golubovsky <golubovsky(a)gmail.com> > Pour : Hilaire Fernandes <hilaire.fernandes(a)gmail.com> > > > > Hilaire, > > I see the question asked by Peter, but all mail links are completely > mangled, so I am replying to you; in case you have a correct email for > Peter > please forward my response to him. > > I believe that the latest binary builds are at > https://ci.inria.fr/pharo-contribution/job/CogDroid/ which are bare VMs > (need an image). PharoDroid (with integrated image) was indeed never ported > properly from the old INRIA build site. > > I think that information at > http://code.google.com/p/squeakvm-tablet/w/list still applies more or > less, > also how to integrate an image into an apk if thats needed. > > The source repo is at > > https://gitorious.org/cogvm/dmg-blessed/ > > and I haven't done any commits to it recently (the latest was at Thursday > October 04 2012). So images at Inria should be fine to start with although > build from sources is always preferred. It's worh mentionig that Pharo 1.x > may be needed to perform the build, and given that Pharo downloading > methods > have changed since the last time I was working on this project some extra > effort may be needed. Also, if serious development is planned, platform > codes in the said gitorious repo need to be merged with the current > platform > codes in other repos (which?), and the whole build procedure needs more > attention. > > Also worth mentioning that only features of Android up to 2.x are used in > this build. I have no idea whether recent NDK is compatible, so if the > older > versions are no longer available, some more effort may be needed to bring > this all up to date. > > Hope this helps. > > Happy New Year! > > Thanks. > > On Wed, Jan 1, 2014 at 9:01 AM, Hilaire Fernandes > <hilaire.fernandes(a)gmail.com> wrote: > >> On 31 Dec 2013, at 17:44, PBK Research <peter(a)pbkresearch.co.uk > >> <mailto:peter@pbkresearch.co.uk>> wrote: > >> > >>> I would like to experiment with Pharo on Android - I have just > >>> acquired an Android tablet, and I do not want to learn another > >>> development language to produce my own simple apps. After a Google > >>> search, I have found http://code.google.com/p/squeakvm-tablet/, > >>> which says it is available, at least as a beta. The site says that > >>> downloads from there are deprecated, and gives a link to > >>> https://ci.lille.inria.fr/pharo/job/PharoDroid/ for the download. > >>> This link seems to be dead, however. Is there any source of a > >>> download of Pharo for Android (on an ARM-designed processor)? And > >>> does it make sense to try to develop apps using Pharo (I know about > >>> Dr Geo, so I suppose the answer is yes)? > >>> > >>> Many thanks for help > >>> > >>> Peter Kenny > >> > > > > > > -- > > Dr. Geo http://drgeo.eu > > > > -- > Dmitry Golubovsky > > Anywhere on the Web > > > > > > >

Jan. 1, 2014

Re: [Pharo-users] Pharo private develoment

by StÃ©phane Ducasse

On 01 Jan 2014, at 19:26, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Pharo as a community has support to use its CI server, among other > goodies such as SmalltalkHub. > > But what if your code is not public and you want to have a central > repository and continuous builds? You have private projects in SmalltalkHub. For the continuous integration I would love to see a company/org offering a service like that. How much are you ready to pay for such service? > Has anybody ever wrote a guide to develop with Pharo in the context of > private development? > > So far I managed to work with a file based repo and a set of > workspaces to create a new working image or to prepare it for > deployment. But I want to automate it as much as I can. What we can do is offer to you access to our continuous integration so that you get started and after you can fly by your own. You can use also travis (but I do not have experience with it). > > Regards! > > Esteban A. Maringolo >

Jan. 1, 2014