I need an Maxthon alpha tester or two…

I need a Maxthon user (and if you are not one you should be – it is an alterenative browser based around IE) to test a new browser plug in.

The newest version of the Google tool bar does not work in Maxthon. I use search Site ALL the times and search images ALMOST as much. Without those two items in Maxthon, it is missing some major features.

So, I’ve written a toll bar that will take the text in the search field and use it to do those extra searches that the Google Tool bar does. It even EXTENDS the google functionality because it will search the news page for info you type in there.

So, this is it at a barely functional level. Please try it and tell me if you come up with any flaws major or minor. I already have in the about box a list of 8 or 9 things I want to do before it reaches a beta level. Any feedback would be appreciated.

Thanks…

Here is the Zip: http://www.thecodecave.com/downloads/GoggleAlpha1.zip
Just extract it with paths to the Maxthon directory, the built in paths will put it where it belongs. Then just open a webpage in Maxthon and the tool bar will appear. (you have to be at a page for the tool bar to appear, if you’ve chosen not to have any page open on startup, the toolbar will appear when you open a page.

Here’s my recommended Gogglebar positioning:
Alpha 1

ADDENDUM:

So if you have a web page open and look for Goggle in the toolbar menu it is not there? Well, for the same reason it requires a page to be open, it likewise requires the Goggle DLL to be registered. You should be able to do clicking Start>Run and pasting in a modified version of this:
regsvr32 “c:\program files\Maxthon\Plugin\Goggle\Goggle.dll”
That will of course have to point to the right director for Maxthon…

See unfortunately this is an IE plugin that works in Maxthon. Ideally, the IE dependency will be removed but i’m not sure how to do that ATM. That may not be fixible befor a beta release, but it is not a big deal if it comes with an installer…

What is this Category?

What is this Category?

The WordPress-list-heirarchical-categories feature has a bug that means that parent categories must have at least one post or the categories underneath won’t be displayed.  SOOOOO….. Here’s the obligatory post for this category…

Here I will write about stuff I want to do – and maybe I’ll add a category specifically for stuff I’ve said I’ll do…

Feature: Category choices.

It would be neat if a browser could only see the categories on a blog that they are interested in.  If the theme could save a cookie with a bitmap of the blogs themes, the user could ignore stuff like  this that they do not care about.  Why would a delphi programmer care about a possible feature I intend to maybe someday include in a theme May or May Not ever get around to writing.

Feature: TRUE blog pages.

The theme must be able to support pages with internal HTML.

This should be done in a way that can be made a standard for other themes and this should be relayed to the other people in the competition prior to the theme releases.  This REALLY should be a standard for WordPress in general.

 In order for me to create a new page at www.KnitChat.com that fits in with the current blog, all I need to do is wrap PHP or HTML in these two lines:

<?php require(dirname(__FILE__).’/includes/custompage_top_yar.php’); ?>

<?php require(dirname(__FILE__).’/includes/custompage_btm_yar.php’); ?>

If I do that, then I can put ANYTHING in there.  Under the current WordPress pages lay out, you are restricted to the type of content allowed in WordPress posts.  That’s insufficient if you want to create true webpages like: www.knitchat.com\fleet.php or www.knitchat.com\subscribetome.php or www.knitchat.com\useronline.php

An option would be to allow the theme options tab to do it by itself…

Code Cave:The Theme – Feature #1

These are ideas I will be putting in a theme I plan to release for the next BIG Word Press theme competition.  I’m not going to be able to do anything about the 2.0 release competitions, but maybe 2.5 or 3.0 in a year.  If you take these ideas and build them into your new theme, please just point a link back to this blog in the read me or preferably in the header code.

Feature one: Optional handling of the blog description and keyword metatags.

The Description meta tag should  done through a check box and an entry field on the theme options tab. 

Keywords should be, if enabled, automatically generated for each post by the category descriptions linked to the post.  Duplicate words would have to be filtered.  If the category description is a bad idea, code the theme add a field to that table or would that be a VERY bad idea?