plympton;540813 Wrote: 
> 
> Only need to do the icon URL code in CustomClock.  Probably need a
> TimeIcon item as well as TimeText.  This would fetch the current icon
> number to fetch and display - it's just an integer 1-45, and it fetches
> a PNG from a URL (local or internet)  I'm going to put that in unless
> you have a preferred way.
> 
> You can handle the web UI part for these additions, right? :-)
> 
> I added this to the cliQuery of SuperDateTime.  This will automagically
> take standard SDT setting strings (as seem from the web UI), and parse
> them it.  Pretty neat.  Only for weather (all I care about).  Could do
> sports, not sure how, probably using a similar method.
> 
Hmm, looks like it works a bit different than I thought, I thought the
JSON response was like the sample wetdata structure you attatched to an
earlier post.

So if I understand you correctly, SDT will take a formatting string
with these %* keywords as input in the JSON request and return the
string expanded to real values ?

Notifications from the plugin when something changes could be tricky if
this is the case as the plugin has no idea which formatting string the
applet uses. So with this solution, we probably need to use polling.

I think I'd like to have a separate item type for SDT, probably two of
them:
- sdttext (which will be configured with a formatting strings as the
one in your sample code)
- sdticon (which will return the url, not sure if it needs to take any
input data)
(I'm not sure if it's going to be sdticon or sdtimage yet, need to look
a bit more how they are handled in the Custom Clock code to know what's
suitable)

How are icons handled ? 
If I understand you correctly I can create an url based on a ID ?
Does the icon need to be rescaled or does it already have the
appropriate size ?

I think I'd like to take a look at how sports are handled before
deciding how to do in the generic Custom Clock applet, you can still
continue your version if you like to but I like to analyze the sport
data to make sure we can handle it the same way, at least if it uses
similar structures.

I wonder what should be displayed in the combobox in the web ui ?
The %* keywords are pretty cryptical without any documentation that the
end user can use to know what they means.

Would be kind of nice if there was a CLI/JSON command which Custom
Clock Helper could call to get SDT to return a set of predefined
formatting strings together with the corresponding expanded values,
this way I could show these in a list box making it a bit easier for
the user to configure it.
Or are all SDT users used to these %* keywords so this isn't a big
issue ?
How does it work for the Classic/Boom/Transporter, does it come with
preconfigured formatting strings ? Does the user also have to enter
these %* keywords ?

plympton;540813 Wrote: 
> 
> I also have a 120x120 pixel set of icons I'm going to use.  The current
> customclock crashes with local (port 9000) urls, just FYI.  I bricked my
> Touch about a dozen times trying to figure out the damn LUA non-regular
> expression syntax, to no avail.  Anyway, it is what it is - should get
> fixed.
> 
Do you have some error messages from the log ?


-- 
erland

Erland Isaksson
'My homepage' (http://erland.isaksson.info) (Install my plugins through
Extension Downloader)
(Developer of 'TrackStat, SQLPlayList, DynamicPlayList, Custom Browse,
Custom Scan,  Custom Skip, Multi Library, Title Switcher and Database
Query plugins'
(http://wiki.erland.isaksson.info/index.php/Category:SlimServer))
------------------------------------------------------------------------
erland's Profile: http://forums.slimdevices.com/member.php?userid=3124
View this thread: http://forums.slimdevices.com/showthread.php?t=77864

_______________________________________________
jive mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/jive

Reply via email to