VidzBigger.com (beta).  YouTube for the extra wide screen!
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
esc
cancel

Latest Updates: features RSS

  • admin 2:35 am on June 8, 2009 | 0 Permalink | Reply
    Tags: features

    Updated VidzBigger with a new feature that allows for even larger video. I like to imagine it like some sort of bubble of increased video gravity. Its still kind of beta, but its enabled by default for some. If you scroll up or down the page will return to the usual layout. There are 16 total pixels defined by vbfoldRadius in source, around the initial scroll point that engage this feature. To skip it scroll past quickly. The bubble is either on or off, but there is more work to be done. Version 0.046 Available on the Downloads page <^ The feature is called Auto Snap Fullscreen on Scroll under Layout preferences

    In the future I imagine I will require a pause during scrolling to engage the feature. Also possibly an adjustable bubble size, along with the idea of having some sort of bubble indicator where the scroll should go to engage it show up to make it easier to use.

    When you are using VidzBigger, if you want to scroll while the mouse is over the video, simply enable double click fullscreen under JSAPI in preferences or disable the JSAPI and use the alternate player. This sets the flash mode to transparent which also slows down everything but its nice on a powerful system.



  • admin 8:02 pm on June 4, 2009 | 2 Permalink | Reply
    Tags: features

    This post relates to userscript pattern matching. @match @include @exclude and how they determine which page URLs VidzBigger runs on (even if its in an iframe) and when it does not.  http://vidzbigger.com mathes anywhere in the URL… so that something like the digg button which as

    ...digg.com/tools/ect?site=http://vidzbigger*

    still contains the URL even though its not at the beginning, should not be matched by VidzBigger and I’ll be finding some way to fix this for ALL iframes that load URLs of this nature in a coming update.  My gut was to just put the carrot at the beginning to match from the begging of the string, and amazingly enough it (does not) works (in greasemonkey) [but its no longer necessary see update].  So if you are getting extra VidzBigger Flags showing up in all the completely wrong places, all you need to do is update your includes to start with a carrot (^http) instead of (http).  This can be done under Manage User Scripts from the monkey itself or otherwise.  I’ll be including this in the script once I can confirm my suspicions that support for carrot in GM goes way back to FF2.  Luckily I found I’m not the only one with this question and as I expand to other platforms this may be a problem again:

    User script ‘URL Includes’ should not match query part of URL. Right now, the URL ‘Includes’ of a userscript are matched against the entire URL of the … http://forum.ie7pro.com/viewtopic.php?id=4184

    Unfortunately it won’t necessarily fix every last extra flag that shows up, but it will fix flags showing up in iframes that belong to the wrong domain!  Which is a big plus, and sorry for any inconvenience caused by having the flag show up in the wrong places sometimes :)  I appreciate that other people have included compatibility code in their scripts to hide the flag when its in the way, when I should have accounted for it all along.  Thanks for understanding!  If the domain match is correct than some other exclude may be necessary, or to make more specific includes, as usual please report any annoying interactions!

    I was trying and trying to find a way to detect if a particular “window” IS an iframe or NOT, just a simple Boolean test, no security risk of any kind, but just enough to know not to run VidzBigger since its in a iframe, would be an even better solution I’m curious to find.

    Oddly enough the carrot is not mentioned at all here as possible or allowed or even recommended… http://wiki.greasespot.net/Include_and_exclude_rules but its not necessary to bother them about it since they fixed it so that to reproduce this bug you need to add a * to the beginning of the include before the http

    Susceptibility Test: I can turn on the VidzBigger flag on any page right now by modifying the querystring: to include ?var=val&site=http://vidzbigger.com/

    UPDATE: Any matching that does not explicit start with a * should ONLY match from the beginning of the URL. A recent update to GreaseMonkey does just this!



  • admin 9:28 pm on May 31, 2009 | 0 Permalink | Reply
    Tags: features, html5

    I installed the FireFox 3.5 Beta to try out the new HTML5 Video Tag. dailymotion open video demo (source)

    I like how it says “this will never work in internet explorer”

    Too early to really evaluate compared with flash, although I expect both performance and quality will be better without the extra bubble of flash running. I would like to get an early start supporting this feature.

    Just tested firebug-1.4.0a30.xpi available At top of this list works fine in FireFox 3.5 Beta

    Here is a Cool Post Explaining Using the HTML5 <video> tag with a Flash fallback

    I just tested fixed position performance of HTML5 video, and Its far from stellar right now. I think this is because of two things: the large number of elements being rendered, and some code that is not realizing that the elements do not move or go off the screen but moves them each time to keep up with the current scroll? Its slightly more complex to grab the entire element now, because you cannot simply grab the video tag, because the controls are up one level, and the container is up two levels. As long as its predictably up two levels like this then its going to be simple to automate grabbing the entire player, although since sometimes that div has a size and the video also has a size, and the controls could potentially have a size, resizing the video and accounting for the controller size automatically isn’t so simple as it was before. Please donate to support continued development!

    Each fixed position element ought to be rendered like a completely separate logical webpage that is then stacked at some level in the draw stack for the current page, but merely as far as ordering goes, no repositioning should be necessary since the fixed position element is rendered at its own offset from 0,0 the effect is simply an overlay, the absence of any additional transformation while scrolling… I mean I guess position-fixed unfortunately and almost uselessly needs support for z-index, although I can imagine one or two futuristic applications that might like to overlay another fixed position element, the stacking of position relative or position absolute on top of a position fixed element seems less likely to be useful in any serious way, it makes sense to keep that possible, even if it should be handled as a separate case which is almost certainly slower to render, where when it can simply be drawn last, then it should be the fastest solution. A fixed position element with the largest z-index can always be rendered last and on top of whatever else was there before, without doing anything besides reset the “world transform” leaving the “object transform” intact. Its possible to encode the offset distance in the first pixel of the texture or otherwise and pull off with a pixel shader. If there is enough memory it makes complete sense when dealing with position fixed to create a texture out of the web page itself and merely snap rectangles from it to the screen while scrolling, so that rendering performance of fixed position elements can stay at one hundred percent. I mean any vector sketching or redundant stamping operations need to be cached and reused while generating content while scrolling however… and any buffer that is generated while scrolling should be saved until you stop scrolling… the word the for instance… and small rectangles on the texture may need to be updated due to interaction or script. Ideally all fixed position elements should create textures which are then merely unlocked and stamped to the screen at the correct time, and updated via thread that handles rendering user interface updates for that element as stamped regions of texture (2 stamps, for video and play head). Automatic recognition of duplicate elements large enough in size composed of enough smaller draw calls but used frequently enough to cache ought to be cached, and ideally other textures are a simple texture transformation away from the last one and undoing changes is as instantaneous as playing back the transformation map in reverse for a particular quad, and the most interesting thing is that the transformation maps can theoretically operate at much lower resolution than screen space and still achieve crisp results since the distance between the data is almost certainly less than the resultant data itself, and rarely involves all color channels. I’m not sure why its not like this already unless we are waiting on some new type of hardware that in effect looks like memory, but its really a memory stacking unit that generates data comprised of various pieces of system memory logically operated on and stacked in real time… as fast as if accessing out of memory itself, but that sounds a lot like an LCD screen to me… but picture two blocks of memory being access simultaneously and you receive the logical AND of each as fast as you could receive either block independently, like some sort of zipper… except it doesn’t stop at logical AND… plus sections of memory containing zero or one, could have additional memory mapped right on top of the same memory space at a different scale and maintain one hundred percent of all data, in which case storing a black object as an inverted white object or vice versa makes perfect sense and can simply be logically NOT on the way out, meanwhile memory at a different scale (say 512 on a 2048) seems technically feasible however scary it might seem. I mean theoretically its possible to stack as many transformation on the same memory space as your capable or indexing, and there aren’t any rules saying that you can’t stack on the index space as well but the consequence of doing any of this stuff would be horrible parasitically increasing slowness… that is unless any number of memory quadrants of any shape could be stacked instantaneously, which sounds a bit too much like quantum computing for today.

    Please donate to support continued development!



  • admin 8:51 pm on May 7, 2009 | 0 Permalink | Reply
    Tags: features

    Right now the easiest way to disable VidzBigger for a particular site is to go under Greasemonkey Script Management and remove the include for that site after clicking VidzBigger, or add an exclude for that site. That will stick until you update. I agree there should be a simple way to “disable for this site” checkbox. I plan on including that in a future release for some time.

    For the inverted color scheme, some people like certain other pages such as their search results, the homepage, ect dimmed. I agree it makes some pages annoying though, since some have bugs that need to be fixed, and some things are unreadable unless selected. You can exclude any user account pages using excludes as above but if you do anything elaborate you’ll want to back up your excludes before upgrading! * matches anything so you might exclude something like http://www.youtube.com/my*

    If you find a particular exclude fixes a ton of pages without disrupting the homepage/search result/video pages being inverted then I’ll definitely include it in updates myself! Just let me know. Thanks for your suggestions!



  • admin 7:44 pm on May 4, 2009 | 1 Permalink | Reply
    Tags: features

    Site submission tool very close now. I was able to submit a site using it, and I set up VidzBigger to automatically load the basic site configuration from the database. A few minor additions will be necessary to allow the user to define elements based on class name along with additional style strings to apply. I hope to release the tool soon, or at least a version of VidzBigger capable of displaying sites that have been submitted using the tool.



  • admin 9:49 pm on May 1, 2009 | 0 Permalink | Reply
    Tags: features

    VB New Site Definition Tool and other things I normally wouldn’t talk about…. are in the works… to make it easier to bring VidzBigger to more sites. Also I have elaborate schemes involving fitting various sized rectangles within a fixed area circle if you like math problems… the rectangles must appear at their maximum possible scale while preserving aspect ratio according to the ration of their relative sizes to one another without overstepping the circle bounds or overlapping (except possibly the corners)



  • admin 4:45 pm on May 1, 2009 | 1 Permalink | Reply
    Tags: features

    Upcoming Feature: Browse top videos (or any website or widget you wish) directly from VidzBigger Preferences!