A must for a serious PHP developer; a bar for documenting PHP functions. You can set it display results either in widget or in a new web page. Also click on the PHP icon to set it to it's thumbnail form.
Version 1.2 is a very big update to phpManual. Features listed on my blog. Version 1.21 makes the widget remember it's skin setting. Also fixes the problem on styling the text input field. This widget has had a broken link but it seems to be fixed now
I'm fully aware of that and there is little I can do for it as there seems to be something wrong in this site; Opera doesn't upload the widget onto the site.
Haha, I've been hardly working on this... first the spin.gif issue (i've got a very cool one) and then some bugs to be fixed. But don't worry, I'll get it as soon as I can. Order my blog's RSS feed (or widgetize) to know when it's out as I recently got the habit of blogging my releases.
Sometimes you lose the control of the output port, you can't use the scroll bar or click an internal link... research it and it should work.
Version tracker - DONE Alternate skin - DONE Used johnnysaucepn's icon generator to make new control icons - DONE Search - A link is given to the search page in the window
More nice features: Added some nice up->down and down->up sliding of the viewport using the Opera Animation Library. Also the background is thrown away and the minimize link is now inside the viewport.
Added a name 'banner' between the search and the other controls
Well these things have been bonging my head currently:
1. (form elements not inline) This is hard as the widget relys on a table which has a tbody element not shown in it's 'normal' state. As it's maximized the table is expanded. If I made them inline the viewport element would push the icons so left they wouldn't be reachable. Looks like a mistake in the colspans. -DONE (fixed with relative values)
2. (text input bg) This I think I'll fix as it is just changing one CSS file. -DONE
3. (buttons) I spent some time on those buttons but if they are making it too long perhaps I should replace them. -DONE
4. (logo) OK I'll use that image. I had no idea of the logo being so big! -DONE
5. (capturing) Perhaps I should use the Screen Ruler for this case. -DONE
6. (viewport) Yeah I really should use padding and borders for this one, you're right. It is again just changing one CSS file. -DONE
7. (minimize button) I thought if the minimize button would be below it would be easy to find. This I need to consider. -CHANGED (it's now a button next to the search button)
8. (buttons to the top right corner) This one I'll definately do as this widget was originally made for the style guide 'ch
Second, the input element background is black text on a dark purple background, which makes it quite hard to read, especially if one has bad eyesight. This should be changed to a lighter background colour, like the search input field on the actual php.net site.
Next, to conserve horizontal space, you should really be using thinner close and options buttons. The circular ones offered by Opera on the templates page would be ideal, IMHO.
The PHP logo is definitely not compressed very well. It is all pixelated, as it if were compressed in a 256 colour-space. I quickly made a replacement image for you which is a 24bit PNG resized to 34 pixels high, the same height as the logo in your widget: http://files.myopera.com/GreyWyvern/files/phpwidgetlogo.png
Finally, when you actually open a page, the viewport does not fill all the horizontal space, making the widget look lopsided: http://files.
Version checking is done but there seems to be something wrong with the Internet connection checker... perhaps I'll leave it out for now to throw this in
All right, the widget's code is now valid and the bmps are replaced by PNGs
I've also been thinking about a preloading script but it doesn't seem to work. Perhaps I should convert the SVG files into PNGs with Batik/Squiggle and try it out then.
It's almost ready, I just need to the SVG/PNG comparasion and version checking and maybe a warning-like alert if the Internet connection isn't on, I've got a very nice way for that.
Glad to hear that the suggestions I made are helping out. 8% on those image files is awful impressive but bmp files are known to be hugh, haha. Good luck and I'm looking forward to updates! Keep up the good widgeting!
Oooh, I really didn't realize my code didn't validate! While in early development I validated it and it worked but when I got to the end of releasing I forgot to validate I quess I need to fall back to XHTML Transitional because I need the IFrame attributes
I tried out the PNGGauntlet, the files came only 8% of original Perhaps I should use it for the Calculator widget as well
And also version tracking might come in handy, as I left it out because I thought that I would release it all in one. But before that I ask you to keep coming back for updates... tho I will do the update soon
I like the widget so far. Good idea. I will me using it a lot, but I notice the buttons jumping around a little when you do the follow...
Open the widget Mouse over the text box Then mouse over the Search button
...It looks like the code needs to be cleaned out a little. I did a quick validation and found 9 errors in the HTML file. I think correcting these will eliminate the buggy jumpy buttons. I see that this is an initial build (1.0), but I just wanted to suggest using PNGGauntlet from http://brh.numbera.com/software/pnggauntlet/ which will convert your image files to PNG which is a much more suggested format than bmp and this program will compress to the lowest possible png filesize. Just set it to save gamma and brute force compression. Small filesize widgets with validated code = faster and guaranteed to perform well.
By login4040, # Feb 23, 2008 5:42:13 PM
By foddski, # Dec 1, 2007 8:06:12 PM
By aleksanteri, # Oct 22, 2006 8:26:13 AM
By zomg, # Oct 22, 2006 0:39:40 AM
I wish this would be fixed soon.
EDIT: Fixed now
By aleksanteri, # Oct 20, 2006 5:34:50 PM
By hanspflugshaupt, # Oct 20, 2006 10:51:55 AM
By aleksanteri, # Oct 18, 2006 8:10:41 PM
By GreyWyvern, # Oct 18, 2006 7:36:42 PM
Sometimes you lose the control of the output port, you can't use the scroll bar or click an internal link... research it and it should work.
Also some internal links don't work.
But it will be soon
EDIT: Perhaps even tomorrow, at wednesday.
By aleksanteri, # Oct 17, 2006 7:24:45 PM
By GreyWyvern, # Oct 17, 2006 5:04:05 PM
Alternate skin - DONE
Used johnnysaucepn's icon generator to make new control icons
Search - A link is given to the search page in the window
More nice features:
Added some nice up->down and down->up sliding of the viewport using the Opera Animation Library. Also the background is thrown away and the minimize link is now inside the viewport.
Added a name 'banner' between the search and the other controls
Added internal function links (at last
By aleksanteri, # Oct 13, 2006 10:26:41 PM
By GreyWyvern, # Oct 12, 2006 11:11:07 PM
1. (form elements not inline) This is hard as the widget relys on a table which has a tbody element not shown in it's 'normal' state. As it's maximized the table is expanded. If I made them inline the viewport element would push the icons so left they wouldn't be reachable. Looks like a mistake in the colspans. -DONE (fixed with relative values)
2. (text input bg) This I think I'll fix as it is just changing one CSS file. -DONE
3. (buttons) I spent some time on those buttons but if they are making it too long perhaps I should replace them. -DONE
4. (logo) OK I'll use that image. I had no idea of the logo being so big! -DONE
5. (capturing) Perhaps I should use the Screen Ruler for this case. -DONE
6. (viewport) Yeah I really should use padding and borders for this one, you're right. It is again just changing one CSS file. -DONE
7. (minimize button) I thought if the minimize button would be below it would be easy to find. This I need to consider. -CHANGED (it's now a button next to the search button)
8. (buttons to the top right corner) This one I'll definately do as this widget was originally made for the style guide 'ch
By aleksanteri, # Oct 12, 2006 7:39:22 PM
First up, the form elements are all out of line when it first appears (WinXP / Opera 9.02):
http://files.myopera.com/GreyWyvern/files/phpwidget01.png
Second, the input element background is black text on a dark purple background, which makes it quite hard to read, especially if one has bad eyesight. This should be changed to a lighter background colour, like the search input field on the actual php.net site.
Next, to conserve horizontal space, you should really be using thinner close and options buttons. The circular ones offered by Opera on the templates page would be ideal, IMHO.
The PHP logo is definitely not compressed very well. It is all pixelated, as it if were compressed in a 256 colour-space. I quickly made a replacement image for you which is a 24bit PNG resized to 34 pixels high, the same height as the logo in your widget:
http://files.myopera.com/GreyWyvern/files/phpwidgetlogo.png
Finally, when you actually open a page, the viewport does not fill all the horizontal space, making the widget look lopsided:
http://files.
By GreyWyvern, # Oct 10, 2006 11:28:07 PM
Download and post a comment!
By aleksanteri, # Oct 9, 2006 0:09:11 AM
By aleksanteri, # Oct 1, 2006 0:25:18 AM
I've also been thinking about a preloading script but it doesn't seem to work. Perhaps I should convert the SVG files into PNGs with Batik/Squiggle and try it out then.
It's almost ready, I just need to the SVG/PNG comparasion and version checking and maybe a warning-like alert if the Internet connection isn't on, I've got a very nice way for that.
By aleksanteri, # Sep 30, 2006 7:49:16 AM
By kyleabaker, # Sep 30, 2006 0:23:21 AM
I tried out the PNGGauntlet, the files came only 8% of original
And also version tracking might come in handy, as I left it out because I thought that I would release it all in one. But before that I ask you to keep coming back for updates... tho I will do the update soon
By aleksanteri, # Sep 29, 2006 6:49:50 PM
Open the widget
Mouse over the text box
Then mouse over the Search button
...It looks like the code needs to be cleaned out a little. I did a quick validation and found 9 errors in the HTML file. I think correcting these will eliminate the buggy jumpy buttons. I see that this is an initial build (1.0), but I just wanted to suggest using PNGGauntlet from http://brh.numbera.com/software/pnggauntlet/ which will convert your image files to PNG which is a much more suggested format than bmp and this program will compress to the lowest possible png filesize. Just set it to save gamma and brute force compression. Small filesize widgets with validated code = faster and guaranteed to perform well.
Great work tho!
By kyleabaker, # Sep 28, 2006 5:43:04 AM