Notices


Reply
Thread Tools
fgs's Avatar
Posts: 77 | Thanked: 85 times | Joined on Feb 2008 @ Italy
#41
Originally Posted by pillar View Post
Dexter wiki page created. All the information should be gathered there from now on. You are more than welcome to point out what needs to be added. Also, you can edit the page and add your own teletext site to the listing.

http://wiki.maemo.org/Dexter
Two things.

1. An idea. Dexter could extract configurations from the Wiki page automatically. The source code of the Wiki page is quite simple to parse, IMO.

2. A problem. I could not make Dexter work with the site for Italian television RAI, because it has a different pattern for URLs. In a nutshell, if the subpage is 1, the number must not appear in the URL; if it is not 1, it must appear in the URL. Can Dexter handle this situation?
 
Posts: 49 | Thanked: 23 times | Joined on Oct 2009 @ Oulu, Finland
#42
Nelonen added to wiki. Only subpages 1 and 2 can be used. Dexter doesn't seem to handle different padding for imageUrl and predictionUrl at the moment. ImageUrl is ex. 100_0001 and subPredictionUrl has ?page=100&subpage=3
 
Posts: 49 | Thanked: 23 times | Joined on Oct 2009 @ Oulu, Finland
#43
Few ideas:

1) Are you planning to put your tool to bugs.maemo.org so that found bugs could be reported there?
2) Would it be possible to populate the available providers directly in menu instead of having button in menu to go to list where to choose?

Last edited by jakoleh; 2010-02-03 at 09:03. Reason: Added second question.
 
pillar's Avatar
Posts: 154 | Thanked: 124 times | Joined on Mar 2007
#44
@fgs @ruskie

Good feedback about what is needed for the url's. I will try to incorporate the needed changes. fgs: can you give the link to RAI teletext so I can take a look as well.

@jakoleh

1) Bugzilla, sure, if someone tells me how to create it.
2) Right now that would make send and I think it's doable. Why it is the way it is now, is that I thought there might be other options (set as default etc) that could be in the menu as well. Will have to think about the UI more when the application matures. Thanks for the feedback.

Prediction seems to be a hit or miss for some reason at the moment, I need to debug it more with the sites that it is not working. It worked beautifully for the two sites I chose to test with..
 
Posts: 353 | Thanked: 263 times | Joined on Dec 2009 @ Finland
#45
Originally Posted by pillar View Post
1) Bugzilla, sure, if someone tells me how to create it.
http://wiki.maemo.org/Bugs:Adding_Extra_products
 

The Following User Says Thank You to TNiga For This Useful Post:
Posts: 123 | Thanked: 33 times | Joined on Jan 2010 @ Stockholm
#46
 
Posts: 49 | Thanked: 23 times | Joined on Oct 2009 @ Oulu, Finland
#47
Originally Posted by pillar View Post
Prediction seems to be a hit or miss for some reason at the moment, I need to debug it more with the sites that it is not working. It worked beautifully for the two sites I chose to test with..
How the subpage is handled with prediction, is it using the padding or some other way to know whether subpage is using 1, 2 or x numbers (1, 01, 0001)?

If it using padding then the problem lies there. Nelonen for example is using 4 numbers in images, but only one in subpages.
 
pillar's Avatar
Posts: 154 | Thanked: 124 times | Joined on Mar 2007
#48
Yeah, padding is used for the subpage. As a workaround for Nelonen, the url part of subpage could be as 000[subpage] and then pad=1 .. that could work, except if the page has more than 9 subpages (not so often).

I guess the solution would be to have some kind of additional variable. I would like to keep it as simple and clean as possible though.
 
Posts: 49 | Thanked: 23 times | Joined on Oct 2009 @ Oulu, Finland
#49
Originally Posted by pillar View Post
Yeah, padding is used for the subpage. As a workaround for Nelonen, the url part of subpage could be as 000[subpage] and then pad=1 .. that could work, except if the page has more than 9 subpages (not so often).

I guess the solution would be to have some kind of additional variable. I would like to keep it as simple and clean as possible though.
That worked. I corrected the information to wiki.

Could it be so that if second parameter is not given then the current one is used for both?
 
benny1967's Avatar
Posts: 3,790 | Thanked: 5,718 times | Joined on Mar 2006 @ Vienna, Austria
#50
I'm trying to set up ORF Teletext and got it working only partially:

I think it should look something like this:

2\siteName=ORF Teletext
2\imageUrl=http://teletext.orf.at/[topicpage]/[page]_[subpage].png
2\predictionUrl=http://teletext.orf.at/[topicpage]/[page]_[subpage].htm
2\subPredictionUrl=http://teletext.orf.at/[topicpage]/[page]_[subpage].htm
2\previousPrediction="<a href=\"(\\d+)_\\d+.htm\" accesskey=\"1\">"
2\nextPrediction="<a href=\"(\\d+)_\\d+.htm\" accesskey=\"2\">"
2\previousSubPrediction="<a href=\"\\d+_(\\d+).htm\" accesskey=\"3\">"
2\nextSubPrediction="<a href=\"\\d+_(\\d+).htm\" accesskey=\"4\">"
2\pad=4


Problem:

[topicpage] isn't treated as expected.

When [page] is "101", [topicpage] gets translated to "[100]" instead of "100". - The brackets [ and ] are included in the URL. Doesn't work.
I removed [topicpage] now and replaced it with "100"; this at least allows me to test the first pages between 100 and 199. Looks good. I'm not gonna add it to the Wiki, though, as long as it cannot really be used for the full range.

Is there something I did wrong with [topicpage] or is it really a bug?
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 18:09.