Jump to content

Show your latest WPI.....


 Share

Recommended Posts


@asta

right about that. did you know that VAIO means Video Audio Integrated Operation. Well I think sony's behind state of the art when speaking of notebooks. I wonder why my GRX has a brilliant display of 1600x1200, but lacks of an IR port and USB 2.0 !? Also where's video, when there's no Video-in ? So much for Vaio. But they're optically superb, I think..

Someone asked me to publish the psd-soucres for the vaio.theme. download them here. Takes its time (approx. 2 MB). And it's only these 2 files I use - the other gifs are already included in the WPI download.

Link to comment
Share on other sites

Someone asked me to publish the psd-soucres for the vaio.theme. download them here. Takes its time (approx. 2 MB). And it's only these 2 files I use - the other gifs are already included in the WPI download.

that would be me. thanks, hasi!

So here is my modified version of yours. :P

th_20f09_screenshot.jpg

I should point out a few errors I found with v3.3.0:

- Selecting themes doesn't work. The VIAO theme is always displayed. The only way to change it is to change the actual files (I replaced background.jpg for this screenshot)

- For some reason part of the programs (bottom line) are cut off. [see under Graphics, it's only one program, and under Tweaks, the second program.] The only way around this is to enable the scroll bar. But I don't want a scroll bar - why cant the whole screen just move up a little? If they ar egetting cut off, shouldn't they move to the next line?

PS- I still think VIAO's are overpriced. Nice to know what it stands for, though. I'm still a Toshiba guy through-and-through.

Link to comment
Share on other sites

For the cut-off proble, edit boxes.js and search for

switch (winheight)
{
 case '480': maxentries=14; break;
 case '600': maxentries=20; break;
 case '768': maxentries=26; break;
 case '1024': maxentries=33; break;
 case '1200': maxentries=44; break;
 default: maxentries=31;  
}

lower the maxentries value for 1024 (your resolution ?) and try again.

As to the problem with selecting the theme - it works on my comp, whatever I do. Dumb question: did you save the changes in options wizard? - BTW my vaio theme doesn't use the background-picture value from the options wizard.

Another question: I see another font than the one I supplied with the theme. Didn't it get installed, or did you change the css ? It should've been installed on opening WPI with the vaio theme.

Therefore the vaio htm calls InstallFont('CybertronMetals.TTF'); on load.

If there's an error in installfont, it will be suppressed, but you could edit generate.js in the folowing way to get an alert on error:

function InstallFont(fontFileName)
{
try {
 if (!FileExists(WshShell.SpecialFolders.Item("Fonts")+ "\\" + fontFileName))
 WshShell.Run("cmd /C copy /Y .\\themes\\" + theme + "\\" + fontFileName + " " + WshShell.SpecialFolders.Item("Fonts"),10,false);
} catch (b) { alert(b.message);}
}

Link to comment
Share on other sites

As to the problem with selecting the theme - it works on my comp, whatever I do. Dumb question: did you save the changes in options wizard? - BTW my vaio theme doesn't use the background-picture value from the options wizard.
I created a new folder in themes called 'a06', and edited useroptions.js to the folder name: a06.

That didn't work, so I tried seleting it from the options menu. Still, the viao theme was used (even after 'saving' and reopening).

As for the bg pic, what I was trying to say is that the only way I was able to change the bg pic while using themes (and not use your viao bg pic) was to go into the viao theme folder, and manually replace the background.jpg with my own.

Another question: I see another font than the one I supplied with the theme. Didn't it get installed, or did you change the css ? It should've been installed on opening WPI with the vaio theme.

Please specify which font you mean. if it's the font of "a.06", that is correct, because I did that myself. If it's something else, then I guess there is a problem. which text are you referring to?

[edit] after re-looking, i assume you are talking about the text of "being install" "select all" etc.

You are correct, and I do not know why the font isnt working. I did not change the css file.

Link to comment
Share on other sites

also, the debug doesn't show a scrollbar in the viao theme mode. so i cannot see anything about the font.

ps - i AM able to switch between default and viao themes. it's when i try to install my own theme (adding my "a06" folder in "themes" with all the viao theme files, except a different background.jpg) that it doesn't work. it selects it just fine, but it doesn't apply the replaced bg. am i doing something wrong? how exactly does one go about 'creating' a theme?

[edit] all these errors still apply on version 3.3.1 downloaded 01-05-05 @ 11:30 EST

[edit 2] further evaluation: i probably don't know how to correctly apply a theme. i looked at the code for wpi.htm in the "viao" theme folder, which i simply copied to my "a06" folder, and i see lots of refs to the "viao" folder, so I am probably making a mistake by simply copying and pasting the theme files. i will await a better tutorial on how to make a theme.

however, this still doesn't fix the font problem, nor the debug problem...

[edit 3] :sigh: also, the debug words are in white, which is extremely hard to read against the viao theme. maybe make the debug text the same settings as the theme itself?

lots of bugs here.. :whistle:

Edited by a06lp
Link to comment
Share on other sites

No no. Edit the wpi.htm in your a06 folder and replace all occurrences of vaio with a06. so if there's a tag <img src="./themes/vaio/background.jpg"> it should be <img src="./themes/a06/background.jpg"> after the replacements. if you just replaces the background.jpg in the a06 folder and didn't edit wpi.htm, then it would still use the one from the vaio folder. that's how html works.

to have debug another bg-color, edit wpi.css. The same to have it another forecolor. try that

.debug
{
font-family: tahoma,verdana,arial;
font-weight: bold;
color : #FFFFFF;
font-size  : 8pt;
margin-left:0px;
background-color: #5A7EDC;
}

Link to comment
Share on other sites

the 2 fixes you posted above work perfectly.

theme switcher now works.

however, there is still no scroll / auto-scroll in the debug menu, so i cannot see anything past "Winheight", so I can't check about the font.

[edit] i managed to fix the scroll thing. (i changed the CLASS of debug to "txt" instead of "debug") however, there is nothing even mention (even on debug level 5) about the font...

[edit 2] also, i think there is an error in your .css file in the vaio theme - under ".txt", it said "mo-margin"...i think its supposed to be "no-margin" ?? Or are you going for a gangsta "mo money mo problems" kinda thing? ;)

[edit 3] ok, i edited my theme's css file more completely, and now i removed all references to your font. :)

also, is there any way to control the tooltip settings from the theme folder (as opposed to the ".js" file??)

Updated Screenshot:

th_bd315_a06.jpg

Edited by a06lp
Link to comment
Share on other sites

ad 1) so you do not have a mouse wheel to scroll, is see. well the probs with the debug mode have been solved by a new css delivered with current/future wpi.

ad 2) mo-margin or no-margin ... it's all the same. there are undefined properties. they'd only have effect, if I removed that no- / mo-. I should've deleted them completely, but forgot about that.

ad 3) bad to hear that, since you could've been the one to tell me if font-installation worked or not (and especially, help me find the problem)

tooltip-style is done only via options by now. but you could use the following trick: redefine it in your wpi.htm

just put

<script>Style[0]=....</script>

into the head of yout wpi.htm -> Tooltip-Style by theme.

Link to comment
Share on other sites

so you do not have a mouse wheel to scroll, is see. well the probs with the debug mode have been solved by a new css delivered with current/future wpi.

ok, i guess i'll check that out when the next version is released. By the way, is 3.3.2 stable? all the stuff we've been talking about is 'petty' appearance stuff. is the coding stable enogh to be burned to cd?

mo-margin or no-margin ... it's all the same. there are undefined properties. they'd only have effect, if I removed that no- / mo-. I should've deleted them completely, but forgot about that.

ha, i didn't realize. :)

bad to hear that, since you could've been the one to tell me if font-installation worked or not (and especially, help me find the problem)

i can still help you. ill just select your theme, still no font anyway. what next?

Link to comment
Share on other sites

Is there any message in debug such as 'Problem on installing theme-supplied font ...' ?

This message should come from generate.js, function InstallFont.

If you prefer an alert box, change

debug("Problem on installing theme-supplied font '" + fontFileName + "': " + b.message,1);

to

alert("Problem on installing theme-supplied font '" + fontFileName + "': " + b.message);

Link to comment
Share on other sites

a06 - don't mind. I found the prob. Installation won't work, if the font is not initialised. What I want to say is, that windows doesn't know a new font was installed, as long as you didn't open the font, or had the fonts-folder open in explorer (that was, why it worked for me while testing, cause I always had to delete the font, to force it being copied to the fonts folder)

I'd have to find another way to install fonts by script. Any suggetions, anyone ?

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.


×
×
  • Create New...