pharo-iot@lists.pharo.org

Pharo IoT Developers and Hardcore users

View all threads

Telepharo and PharoThings on Pharo Launcher

AO
Allex Oliveira <allex.oliveira@msn.com>
Thu, May 28, 2020 9:22 PM

Hi everyone,

I was syncing with Christophe how we can put TelePharo and PharoThings on Pharo Launcher, and I created a tool to generate the images of any repository in each commit using Travis CI and release the images on Github. So now it's easy to do that.

But there are some questions:

"Then, you should think under which category we should put Telepharo? Official templates? A dedicated category? If it is the official one, we should have max 2 entries for Telepharo I think. If you want to have all combinations, a dedicated category? Also one thing that could be annoying is that it is a continuous build, no stable (reproducible) version."

I think we could have 2 entries in official one (Full Telepharo and PharoThings to Pharo 8 64)

and to have an IoT category with telepharo and pharothings to pharo 7/8/9 32/64 client and server, minimal image, etc

About the continuous build, maybe we can use the tag releases to PharoLaucher. But I think we need to think about a better way to see which version is running on the server, to download the same specific version of the client.

Maybe when the client connects, it realizes some kind of test and shows a popup saying it's the same version or not, and which one is supposed to use...

What do you think guys?

Allex Oliveira

Hi everyone, I was syncing with Christophe how we can put TelePharo and PharoThings on Pharo Launcher, and I created a tool to generate the images of any repository in each commit using Travis CI and release the images on Github. So now it's easy to do that. But there are some questions: "Then, you should think under which category we should put Telepharo? Official templates? A dedicated category? If it is the official one, we should have max 2 entries for Telepharo I think. If you want to have all combinations, a dedicated category? Also one thing that could be annoying is that it is a continuous build, no stable (reproducible) version." I think we could have 2 entries in official one (Full Telepharo and PharoThings to Pharo 8 64) and to have an IoT category with telepharo and pharothings to pharo 7/8/9 32/64 client and server, minimal image, etc About the continuous build, maybe we can use the tag releases to PharoLaucher. But I think we need to think about a better way to see which version is running on the server, to download the same specific version of the client. Maybe when the client connects, it realizes some kind of test and shows a popup saying it's the same version or not, and which one is supposed to use... What do you think guys? Allex Oliveira
MD
Marcus Denker <marcus.denker@inria.fr>
Thu, Jun 4, 2020 12:25 PM

On 28 May 2020, at 23:22, Allex Oliveira allex.oliveira@msn.com wrote:

Hi everyone,

I was syncing with Christophe how we can put TelePharo and PharoThings on Pharo Launcher, and I created a tool to generate the images of any repository in each commit using Travis CI and release the images on Github. So now it's easy to do that.

But there are some questions:

"Then, you should think under which category we should put Telepharo? Official templates? A dedicated category? If it is the official one, we should have max 2 entries for Telepharo I think. If you want to have all combinations, a dedicated category? Also one thing that could be annoying is that it is a continuous build, no stable (reproducible) version."

I think we could have 2 entries in official one (Full Telepharo and PharoThings to Pharo 8 64)

and to have an IoT category with telepharo and pharothings to pharo 7/8/9 32/64 client and server, minimal image, etc

I would now just put a dedicated Category. Then we can later see if it makes sense to have some in official or not.

About the continuous build, maybe we can use the tag releases to PharoLaucher. But I think we need to think about a better way to see which version is running on the server, to download the same specific version of the client.

Maybe when the client connects, it realizes some kind of test and shows a popup saying it's the same version or not, and which one is supposed to use...

Yes, that might be an idea… an explicit version check.

Marcus
> On 28 May 2020, at 23:22, Allex Oliveira <allex.oliveira@msn.com> wrote: > > Hi everyone, > > I was syncing with Christophe how we can put TelePharo and PharoThings on Pharo Launcher, and I created a tool to generate the images of any repository in each commit using Travis CI and release the images on Github. So now it's easy to do that. > > But there are some questions: > > "Then, you should think under which category we should put Telepharo? Official templates? A dedicated category? > If it is the official one, we should have max 2 entries for Telepharo I think. > If you want to have all combinations, a dedicated category? > Also one thing that could be annoying is that it is a continuous build, no stable (reproducible) version." > > I think we could have 2 entries in official one (Full Telepharo and PharoThings to Pharo 8 64) > > and to have an IoT category with telepharo and pharothings to pharo 7/8/9 32/64 client and server, minimal image, etc > I would now just put a dedicated Category. Then we can later see if it makes sense to have some in official or not. > About the continuous build, maybe we can use the tag releases to PharoLaucher. But I think we need to think about a better way to see which version is running on the server, to download the same specific version of the client. > > Maybe when the client connects, it realizes some kind of test and shows a popup saying it's the same version or not, and which one is supposed to use... > Yes, that might be an idea… an explicit version check. Marcus