Sage Development Environment

[stuckless]

I've been playing with doing some java/stv work and I got thinking... there has to be a better way. Not that the tools aren't good enough, but that I need to be doing this work on my production system is a real problem. I'm restarting sage, which isn't much of an issue to me now, because I don't have recordings, but to other sage developers, how do you manage?

I'm curious how stv/java developers manage to develop with Sage. Do you have a Sage Develolpment Environment, or do you develop on the "production system"?

I'd like to setup and install a separate sage instance for development purposes, but I don't think my license allows me to do so... and I don't want to activate a "development" sage instance only to have it de-activate my production sage instance.

I would think that it would be good if sage provided free developer licenses with sage, that would enable a sage developer to install a second instance for development purposes so that the production sage doesn't get restarted everytime there is a jar file or class update.

[GKusnick]

SageTVClient includes Studio. I have a Client license on my desktop dev machine, and do all my STV dev work there, and roll it out to the server only after it's been well tested on the client.

Plus I can watch recorded programs at my desk while my wife watches something else in the living room.

[stuckless]

It would appear that SageTVClient is only on windows. Is that correct? I run linux on both the client and server.

So it would appear that the SageTVClient is Sage's equivalent to a development environment that I alluded to.

I guess i'm stuck with restarting my production sage for all my changes

Thanks.

[mayamaniac]

Originally Posted by stuckless

I'm curious how stv/java developers manage to develop with Sage. Do you have a Sage Develolpment Environment, or do you develop on the "production system"?

I'd like to setup and install a separate sage instance for development purposes, but I don't think my license allows me to do so... and I don't want to activate a "development" sage instance only to have it de-activate my production sage instance.

I don't think they have a shortage of licenses.

I would think that it would be good if sage provided free developer licenses with sage, that would enable a sage developer to install a second instance for development purposes so that the production sage doesn't get restarted everytime there is a jar file or class update.

Other option is to install development version on a separate machine, or in a virtual OS such as within VMware.

[stuckless]

I don't think they have a shortage of licenses.

Translation: Buy another license you cheap bastard

I don't think I'll opt for the second license. Not that I'm cheap, just that working off the production system doesn't bother me enough to get the second license just to develop some STV enhancements.

Other option is to install development version on a separate machine, or in a virtual OS such as within VMware.

Translation: Buy another license you cheap bastard

Not much of a different answer than my first. I have a separate machine already. Using VMware/Virtualbox doesn't change anything here, unless I opt to get a second license.

Again, I was curious how other people developed STVs for Sage. And I think that Greg summed it up best..... Windows has the SageTVClient. And I would guess that there are not that many linux desktop users developing STVs for sage.