where to report Telescope bugs?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

where to report Telescope bugs?

Peter Uhnak
Hi,

where do I report Telescope bugs?

I downloaded latest TL via Pharo Launcher (build #192), but any opening/closing interaction doesn't work.

1. run TLDemos>>exampleCompositeExploringHierarchy
2. click on "+"
3. error MNU SubscriptionRegistry>>subscriptionsDo:

mean that someone is actually working on it, or that it is planned someday = I just use the source code for the foreseeable future (or maybe if you have some internal docs available)?

Thanks,
Peter
Reply | Threaded
Open this post in threaded view
|

Re: where to report Telescope bugs?

Peter Uhnak
Btw subscriptionsDo: is added by Roassal2Spec package, which is not loaded into the CI build

Also load script here http://rmod.inria.fr/web/software/telescope says its LeoPerard/Telescope
while the CI loads Moose/Telescope.

Peter

On Mon, Jul 20, 2015 at 6:34 PM, Peter Uhnák <[hidden email]> wrote:
Hi,

where do I report Telescope bugs?

I downloaded latest TL via Pharo Launcher (build #192), but any opening/closing interaction doesn't work.

1. run TLDemos>>exampleCompositeExploringHierarchy
2. click on "+"
3. error MNU SubscriptionRegistry>>subscriptionsDo:

mean that someone is actually working on it, or that it is planned someday = I just use the source code for the foreseeable future (or maybe if you have some internal docs available)?

Thanks,
Peter

Reply | Threaded
Open this post in threaded view
|

Re: where to report Telescope bugs?

Usman Bhatti
In reply to this post by Peter Uhnak
Hi Peter,

On Mon, Jul 20, 2015 at 6:34 PM, Peter Uhnák <[hidden email]> wrote:
Hi,

where do I report Telescope bugs?

Telescope is a part of Moose eco system and during the Moose sprints/dojos, we get to work on Telescope. You can report issues on moose google code:
 

I downloaded latest TL via Pharo Launcher (build #192), but any opening/closing interaction doesn't work.

1. run TLDemos>>exampleCompositeExploringHierarchy
2. click on "+"
3. error MNU SubscriptionRegistry>>subscriptionsDo:

You can get latest image from:

And the example is working in the latest build.


mean that someone is actually working on it, or that it is planned someday = I just use the source code for the foreseeable future (or maybe if you have some internal docs available)?

It is a work that never progressed but we should revisit it.

In the meantime, you can have a look at the ESUG paper (attached here).

regards.
usman
 

Thanks,
Peter


IWST_2015_submission_3.pdf (292K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: where to report Telescope bugs?

Usman Bhatti
In reply to this post by Peter Uhnak


On Mon, Jul 20, 2015 at 6:40 PM, Peter Uhnák <[hidden email]> wrote:
Btw subscriptionsDo: is added by Roassal2Spec package, which is not loaded into the CI build

Also load script here http://rmod.inria.fr/web/software/telescope says its LeoPerard/Telescope
while the CI loads Moose/Telescope.

Moose/Telescope is the correct repo.
We'll update the tutorial.

 


Peter

On Mon, Jul 20, 2015 at 6:34 PM, Peter Uhnák <[hidden email]> wrote:
Hi,

where do I report Telescope bugs?

I downloaded latest TL via Pharo Launcher (build #192), but any opening/closing interaction doesn't work.

1. run TLDemos>>exampleCompositeExploringHierarchy
2. click on "+"
3. error MNU SubscriptionRegistry>>subscriptionsDo:

mean that someone is actually working on it, or that it is planned someday = I just use the source code for the foreseeable future (or maybe if you have some internal docs available)?

Thanks,
Peter


Reply | Threaded
Open this post in threaded view
|

Re: where to report Telescope bugs?

Peter Uhnak
In reply to this post by Usman Bhatti
mean that someone is actually working on it, or that it is planned someday = I just use the source code for the foreseeable future (or maybe if you have some internal docs available)?

It is a work that never progressed but we should revisit it.

In the meantime, you can have a look at the ESUG paper (attached here).

Since I am not familiar with this technology, it's really hard to understand without an overview of the concepts behind it / tutorials / whatever. But the paper looks promising, I'll go through it tomorrow.

Thanks,
Peter