For The Record - The rule-based scheduling suite (6 Viewers)

[D4bFz3awSRYHKjr3]

next problem, when trying to log in

see picture

 

[dvdfreak]

Looks like an Ajax problem I only tested with IE7 and FireFox. Is this perhaps IE6?

 

[D4bFz3awSRYHKjr3]

yep ie6

 

[dvdfreak]

Hang on, I just realized the Ajax extensions need to be installed on the server, perhaps that is the problem:

http://go.microsoft.com/fwlink/?LinkID=77296

 

[D4bFz3awSRYHKjr3]

dat was het probleem

problem solved, perhaps change the requirements on the first page

 

[dvdfreak]

problem solved, perhaps change the requirements on the first page

I already did that, just now Stupid of me to forgot this very important point.

 

[D4bFz3awSRYHKjr3]

1 feature request: a timeline overview of the epg like the first webinterface for mp0.2

the rest is great

 

[dvdfreak]

Edit: this software is essential for good htpc usage, it should be smack bang on the frontpage!
Why isn't there more attention from the dev team for this, this is every persons dream if you want good (and advanced) recordings in MP, as the current state of scheduling in MP is truly unreliable IMO. Again, thanks so much for all your effort!

You'll have to ask the MP devs for their reasons, I can't really say they have been very enthousiastic so far. I've started a few attempts at getting a constructive dialogue going, to see how this could be integrated, but I'm more or less done with that as this was getting nowhere fast

If I can't convince the devs of the strength of a service-oriented architecture, not even by showing the results here there's really not much more I can do. TV Scheduler has rapidly gone from the core service I always intended it to be, to a usable plugin solution with a full-featured management console, HTTPS remote access and now also with web access.

The reason all this could be accomplished so relatively quickly is largely due to the choice of core architecture, some might say even the simple choice to have an architecture The whole system has been designed to be client/server from the start. And that design is paying off already.

 

[kkendall]

I'm not at all familiar with the architecture behind your fantastic work, but are there any limitations you can imagine your software could have in comparison to the road that is being followed by the devteam for future TVserver and MediaPortal versions?

And the other way round?
Are there any (future) limitations of the TVserver, MediaPortal or TVE3 that you already know will not be possible but are possible for your software?

...I don't see why they are so reluctant to give this some proper attention....

EDIT: Isn't it possible to make a plugin out of it (unofficial or not) that can be implemented in the MP GUI? That way far more people could use this, as it is probeably not very known yet under simple and average MP users... I'm sure that once more users starting to notice this is out there, everybody wants to use this instead of what MP uses now. But for a lot of people the implementation of options and services into one general program/GUI is essential (there's the missis again ).

So...if there would be a GUI for your service...man... I see a bright future for this ahaid

 

[D4bFz3awSRYHKjr3]

I'd like to say that this is by far the greatest thing that could ever happen for MediaPortal,

-Powerful schedules
-Managment interface for creating schedules
-And a webinterface, that is quickly created and looks good and perhaps even better than many other attempts.

The only thing missing is a GUI for MediaPortal itself.

I'm also amazed of how many(not much) bugs there have been.

You've got my vote to get it integrated within tvserver0.3.

Like it is working right now also suits my needs, but everything can be better.