NextPVR Forums
  • ______
  • Home
  • New Posts
  • Wiki
  • Members
  • Help
  • Search
  • Register
  • Login
  • Home
  • Wiki
  • Members
  • Help
  • Search
NextPVR Forums Information NextPVR Announcements v
« Previous 1 … 3 4 5 6 7 … 11 Next »
Plugin developers read

 
  • 0 Vote(s) - 0 Average
Plugin developers read
Fatman_do
Offline

Posting Freak

Posts: 3,482
Threads: 95
Joined: Nov 2005
#51
2006-07-26, 07:01 PM
daphatty Wrote:Oh. I guess I didn't interpret his comment that way. I've seen him make that same suggestion before and I am all for it. I'm still trying to figure out you derived that meaning though.

I took Old Dog's comments the same way Jeff did. It is a plugin display related request.

Quote:"could we get them to refresh their skin related settings each time they are activated"

Bold emphasis is mine.
Fatman_do
[SIZE="1"]
HTPC: AMD XP+2500, 512MB DDR (400) ~ Capture Device: Hauppage PVR-150
Storage: 30GB OS & Recording, 160GB Post Processing & Archive
Video Output: HD 32" TV via eVGA Geforce 6200le 256MB AGP DVI-HDMI cable out
Audio Output: Turtle Beach Riviera S/PDIF Optic Output (Digital pass thru only) to Home Theater Receiver[/SIZE]

[SIZE="2"]
Moderator | Tutorials | Community Skin | CommunitySkin-SVN[/SIZE]
Old Dog
Offline

Posting Freak

Posts: 1,083
Threads: 99
Joined: Jul 2005
#52
2006-07-26, 07:57 PM
So far, everybody's right!

Basically, whenever the skin for a plug-in is changed, by the end-user or by the skinner, it would be good if the changes were reflected by the display the very next time the plug-in is selected.

There are two possible triggers for this:
  • The plug-in's activate method is called
  • Sub tells them (he actually is planning a software mechanism for this)

I would suggest that the plug-in incorporate an Initialize method that rereads the skin.xml among other things. This method could be called from Activate() or as a result of Sub new mechanism.

Regards All,
Old Dog
Learning new tricks!
Visit Plain Jane's Collection
psycik
Offline

Posting Freak

Posts: 5,210
Threads: 424
Joined: Sep 2005
#53
2006-07-26, 08:10 PM
Old Dog Wrote:So far, everybody's right!

Basically, whenever the skin for a plug-in is changed, by the end-user or by the skinner, it would be good if the changes were reflected by the display the very next time the plug-in is selected.

There are two possible triggers for this:
  • The plug-in's activate method is called
  • Sub tells them (he actually is planning a software mechanism for this)

I would suggest that the plug-in incorporate an Initialize method that rereads the skin.xml among other things. This method could be called from Activate() or as a result of Sub new mechanism.

Regards All,
Old Dog

It's just as easy to store the date modified of the skin.xml file and test it easy time a render is done - you only test it once for the plugin BTW, not for each screen that would be too much IO.. Only one plugin at a time has focus at a time so it shouldn't really cause any problems.

But if later on i could be integrated into that settings area that sub started a couple of versions back, then he could worry about the skin file/config.xml etc being updated and it would be more consistent across plugins.

I'm going to have to look at my plugins at what i can get from baseSkin.xml rather then defining it all myself in my skin file.
sub
Offline

Administrator

NextPVR HQ, New Zealand
Posts: 106,724
Threads: 767
Joined: Nov 2003
#54
2006-07-26, 08:15 PM
Quote:It's just as easy to store the date modified of the skin.xml file...
You do realize that if you had this, users would soon start asking about why changes to baseskin.xml or any image files used are not automatically detected. It all gets pretty messy pretty quickly.
Fatman_do
Offline

Posting Freak

Posts: 3,482
Threads: 95
Joined: Nov 2005
#55
2006-07-26, 08:30 PM
psycik Wrote:I'm going to have to look at my plugins at what i can get from baseSkin.xml rather then defining it all myself in my skin file.

Not much right now. (SelectedButtonImage, NormalButtonImage, PopupNormalButtonImage and PopupSelectedButtonImage composite images and Default, ButtonText and ScreenName textstyles.)

I listed everything that currently is in baseskin.xml

I would wait to see how baseskin.xml changes comming up will effect it.

That pretty much goes for any plugin right now. (I have looked at them lately for some reason...Rolleyes )
Fatman_do
[SIZE="1"]
HTPC: AMD XP+2500, 512MB DDR (400) ~ Capture Device: Hauppage PVR-150
Storage: 30GB OS & Recording, 160GB Post Processing & Archive
Video Output: HD 32" TV via eVGA Geforce 6200le 256MB AGP DVI-HDMI cable out
Audio Output: Turtle Beach Riviera S/PDIF Optic Output (Digital pass thru only) to Home Theater Receiver[/SIZE]

[SIZE="2"]
Moderator | Tutorials | Community Skin | CommunitySkin-SVN[/SIZE]
sub
Offline

Administrator

NextPVR HQ, New Zealand
Posts: 106,724
Threads: 767
Joined: Nov 2003
#56
2006-07-26, 08:37 PM
Yeah there isnt really much in the current baseskin.xml. Pretty much anything could be put in there, but I think everyone was following my lead in the blue skin, so it wasnt used for much even in other skins. Thats said, even having the buttons and couple of text styles was a big jump forward from when baseskin.xml didnt exist.

I'm going to define a few more things in there for the next release (some standard colours, fonts etc), and adjust the blue skin to use these extra things, which will hopefully encourage its use a bit more.
Old Dog
Offline

Posting Freak

Posts: 1,083
Threads: 99
Joined: Jul 2005
#57
2006-07-26, 08:38 PM
Fatman_do Wrote:Not much right now. (SelectedButtonImage, NormalButtonImage, PopupNormalButtonImage and PopupSelectedButtonImage composite images and Default, ButtonText and ScreenName textstyles.)

I listed everything that currently is in baseskin.xml

I would wait to see how baseskin.xml changes comming up will effect it.

That pretty much goes for any plugin right now. (I have looked at them lately for some reason...Rolleyes )

From a plug-in developer's perspective, what is the correct mechanism for using BaseSkin.xml. Should the plug-in read and process BaseSkin.xml? Is BaseSkin.xml transparent to the plug-in, somehow hidden by other system calls that first check skin.xml then fallback to baseskin.sml? Something else?

Thanks,
Old Dog
Learning new tricks!
Visit Plain Jane's Collection
sub
Offline

Administrator

NextPVR HQ, New Zealand
Posts: 106,724
Threads: 767
Joined: Nov 2003
#58
2006-07-26, 08:43 PM
Quote:Is BaseSkin.xml transparent to the plug-in, somehow hidden by other system calls that first check skin.xml then fallback to baseskin.xml?
yes.
psycik
Offline

Posting Freak

Posts: 5,210
Threads: 424
Joined: Sep 2005
#59
2006-07-26, 10:02 PM
using the baseskin more would certainly help in making wholesale changes to fonts sizes etc - something I have done on my MVP skin since it's on a 14" tv, I can't remember the number of places i had to change it with our "current system'

sub Wrote:You do realize that if you had this, users would soon start asking about why changes to baseskin.xml or any image files used are not automatically detected. It all gets pretty messy pretty quickly.

Hmm, didn't think of that - was trying to spare you having to write something Big Grin guess it'll have to be something that you add to iMenuTask - a skinupdated callback/event.
reven
Offline

Posting Freak

Posts: 5,782
Threads: 396
Joined: Sep 2004
#60
2006-07-29, 02:27 AM
sub if i try select a node,

sk.getNode(".....");

that isnt in the actual skin, but in the "base" skin will it get that node from the base skin automatically? (im in the process of updating all my code to the new skin helper constructor)
« Next Oldest | Next Newest »

Users browsing this thread: 2 Guest(s)

Pages (7): « Previous 1 … 3 4 5 6 7 Next »
Jump to page 


Possibly Related Threads…
Thread Author Replies Views Last Post
  Developers, need a sub-forum supporting your plugins? sub 52 15,948 2007-07-12, 01:37 PM
Last Post: systemshark
  Plugin authors, please read sub 4 4,599 2006-05-07, 02:32 AM
Last Post: sub

  • View a Printable Version
  • Subscribe to this thread
Forum Jump:

© Designed by D&D, modified by NextPVR - Powered by MyBB

Linear Mode
Threaded Mode