Looking at some of the site statistics at The VG Press, it shows 82% of users reporting Java support enabled. One must then ask, WHY? Why do you have Java enabled? Java is a cross-platform language that in terms of what it provides as a browser is Java applet support.

Here are some examples of Java applets from Sun’s website:

http://java.sun.com/applets/jdk/1.4/index.html

If you can see those, you ought to go and disable Java now. For the most part, Java has disappeared from the web. A few uses remain in some web-based games, and speedtests as an alternative to flash, but that’s pretty much it. There is no reason to have it enabled by default.

I frequent ChessGames.com which uses an applet to allow to view games, so I have it selectively enabled for that singular site. This is what I would suggest to do with Java, if you need it at all in your web browser.

To do this in Firefox, you’ll require the NoScript extension. NoScript disables JavaScript, Java and other plug-ins and dynamic content by default, and allows you to selectively enable them.

If you just need to disable Java entirely, that’s an options in your preferences (Edit->Preferences) under the Content tab.

To do this in Opera you’ll need to go to your preferences (Toos->Preferences) then under the advanced tab go down to Content. Disable Java system wide is an option there, which you’ll want to do. Then click Manage Site Preferences in order to selectively enable it.

To do this in Internet Explorer, I only have the option to globally disable Java, and no way to selectively enable it, as it’s not an option for Trusted Zones. For disabling Java, you’ll go to Internet Options (Tools->Internet Options), then under the Advanced tab scroll down until you see “Use JRE 1.X.X for applet” and uncheck it.

Java has had a long history of security issues, and even that notwithstanding, the more plugins you have running, the more possibility there is for something to go wrong, as well as the more that has to be loaded. For the majority of cases, I’d suspect Java goes completely unused, so letting any old site make it available is wasteful and potentially harmful.

A few events and ideas kind of converged, serendipitously, to make me write this post.

Yesterday, I had posted about FrontPage 2003 quirks a lady was having when running it on Windows 7.

Two days ago I posted that I finally got a Windows 7 driver for my HP P1006 LaserJet.

The other day I was thinking about the overall issue of ‘Windows’ compatibility. My background , and abiding passion, is in IBM mainframes. The core S/370 hardware architecture dates back to 1971 (or thereabouts). Software compatibility, across the decades and generations, is a hallmark of mainframe computing. The various operating systems, from OS/VS 1 to today’s z/OS, has bent over backwards to ensure this.

So, my thought process was, why is it so difficult to have ‘Windows’ compatibility.

Though I have now used Windows, daily, for 12 years, I am not a Windows expert. I can get most things done, but I have never really tried to understand how Windows work. Yes, I kind of know what a ‘DLL’ is but I cannot honestly say how it all fits together. Whereas, I used to pour over S/370 and OS/VS ‘x’ architecture documents, I can honestly say I have never read anything about the internals of Windows. So, I don’t know ‘why,’ but it bothers me that an application or driver written for XP will just stop working in a newer version of Windows, in this case Windows 7.

I was going to write today about the elusive Windows Defender. That I actually ran it the other day. But, I, for a change, wanted to find out a bit more about it before I wrote my post. So I visited Microsoft’s Windows Defender page (which, of course, I found via Google).

I was kind of looking for a ‘FAQ,’ and the nearest I found was ‘Help & How-to.’ So tried that to discover that it has a ‘drop-down’ for the various versions of Windows … my attention, of course, being caught by Windows 7.

Clicked on that. It wasn’t about Windows Defender! But, my eyes were drawn to a BIG HEADING that said “Top Solutions.”

#5 and #6 in that list were about Windows 7 compatibility. Some good information there. Even a video about how to try and run older programs on Windows 7. So here is the link, try it.

In the process, I discovered that my FireFox 3.5.5 (on Windows 7, obviously) requires a Windows Media Player 11 PLUG-IN from Microsoft no less, so that I can play Media Player videos in FireFox. I thought one of the built-in features of FireFox 3 was that it could play any video inside a tab. Hhhhmmm. I guess you still need plug-ins.

Anura Guruge
www.guruge.com

Tjohoo!!!

Jaha, då har det tydligen dykt upp ett par invites till Google Wave på mitt konto, och jag tänkte nu att jag kanske skulle ta och dela ut dessa. Liten tävling igen kanske, hoppas att Spotify-vinnarna blev glada för övrigt, även om Spotify är rätt lätt att få tag på numera. Vad ska man göra för att få en invite till Google Wave då?? Jo förstår du, den här gången tänkte jag att ni kunde erbjuda mig en invite till någonting, Voddler kanske, hehe =)…

Nä men torrent-sidor som exempelvis hd-bits eller liknande, byter jag gärna.

Så kom med förslag, så ska du se att du snart har “vågen” du också =)

Vet du inte vad “vågen” innebär?? Kolla in länken nedan.

Hola a todos, hoy os muestro un Plug-in para los amantes de Front Row y YouTube. Se trata de un Plug-in para añadir a Front Row la opción de ver los vídeos más destacados o recientes de YouTube.

Para instalarlo tan solo tenéis que descargaros el archivo que os dejo al final del post, y una vez lo descomprimís la carpeta que tiene el nombre “frUnderstudy.frappliance” teneis que copiarla dentro de los Plug-ins de Front Row, para ello tenemos que ir a la ruta “/System/Library/CoreServices/” y dentro de este directorio buscar el archivo “Front Row.app” encima de este archivo haremos click con el botón derecho y le darmos a “Mostrar contenido del paquete” seguido abrimos “Contents/PlugIns/” y copiamos la carpeta en este directorio.

Os dejo un video para que veáis el resultado

Espero que os resulte interesante y útil.

Enlace de descarga: Understudy

Salu2 y gracias!

Every Monday I highlight free plugins new and old that are worth checking out. See all posts in the Free Plugin Of The Week Series.

Blue Cat Audio has been around for a few years, I’ve used some of their free plugins in the past and I would recommend them over some of the included DAW plugins. Blue Cat came back on my radar when they announced RTAS (Mac + PC) Beta versions for their Freeware Plugins Pack.

All Blue Cat Audio freeware audio plug-ins gathered together in a bundle. It’s here! Save download time and get them all in a single package.

The bundle contains a wide range of modulation effects, an EQ and analysis tools to get you started with your favorite Digital Audio Workstation, for free! This bundle is available for Mac and PC, in VST, RTAS (beta), Audio Unit and DirectX plugin formats. Enjoy!

More from Audio Geek Zine

Today, I found this website that provides several WP tips that can be very useful if you are blogging using a WordPress platform and does not just sub-domaining in WordPress.com. The said oes tsetnoc blog site guide you to on how to make a a WP blog that could serve visitors well. It discusses some updates about the platform, themes and plug-ins to use to make a very nice website.

Why is it that it is important for you to have an idea on this things. Well, if you want to build a great presence of the web, you should think of your visitors and not only how the website will looks like. Through the oes tsetnoc site, it gives you idea on how to go through this stage of building presence online.

Some of the plug-ins recommend by the site was Super Cache, DB Cache, Page-Navi and YARP (yet another related plug-in). You can implement these plug-ins  on this site because it is just hosting under WordPress.com and they are not allowing custom scripts like those plug-ins to be installed and implemented on the site.

I am using all of the plug-ins and reading the rest of the site now and these changes really cause an impressive improvement on my blog. You might also want to read: Web Design Idea from CDesign.

How To Optimize Your Internet Settings

Search for “CS4 optional plug-ins” in Adobe’s website to get all the missing plug-ins such as contact sheet, and extract, and pattern maker.

Hola a todos, posteando desde el MacBook blanquito de mi chica Eunate, hoy os presento Glims, esta aplicación no es más que una extension para terminar de completar las preferencias de Safari, completas con esta aplicación bajo mi punto de vista.

Una de las cosas que más me ha gusta y que me di cuenta hablando con iHache de Maquecitos por iChat es la inclusión de miniaturas en los resultados de las búsquedas en los diferentes buscadores de la red.

Con Glims puedes añadir favicons a las pestañas, añadir infinidad de motores de búsqueda, modo de pantalla completa, etc…

Glims también incluye buscadores específicos para Facebook, MTV y más!

Espero que os guste y que os animeis a completar el navegador por excelencia en nuestros Macs

Enlace de descarga: Glims

Salu2 y gracias!

After installation of an OEM Agent on the Sybase Server, we succesfully deployed the Sybase Plug-in.

Both the Sybase Host and Sybase Database show up nicely in OEM. We do however have a Metric Collection error I need to sort out.

All too often photographers engage with Photoshop and come away over-awed, frustrated and disappointed. The blame, if there is any, can be laid at the feet of the application’s complexity.

One way of dealing with the software is to work initially with the multitude of plug-ins available and deal with specific tasks to gain confidence.

Zuckerman and Stulberg’s book, ‘Digital Photographer’s New Guide to Photoshop Plug-Ins (A Lark Photography Book)‘, suggests you revisit your earlier images and revitalise them with the aid of specific plug-ins.

The book opens with a novel one in Instant Mirror, which allows you to duplicate sections of your image and reposition them into appealing and wonderful ways. [read]

Hace muy poco que existe Wave y somos pocos los que podemos utilizar esta herramienta, pero ya estan las extensiones para Firefox y Chrome

NOTA: Para el uso en Google Chrome se necesita estar en el canal DEV (version 4+).

En Chrome:

y en Firefox:

__

Fuentes (desarrolladores):

http://www.jeremyselier.com/fr

http://thatsmith.com/

Sure, I wouldn’t be able to do what I do without Pro Tools for recording and mixing; Peak to batch convert WAV files into mp3s; Dreamweaver to post them to a custom website I create for the artist; and Mac Mail to let them know the mixes are posted. And iChat quickly connects me to a missing session file, sends out a mix, or circumvents FTP altogether. I use Toast to compile the mastered mixes and create a Red Book CD, and the iTunes to check the burn. The iTunes Store provides unlimited sonic references in 30-second chunks.

But get ready for a cliché: The most important piece of software operates between your ears. Think about this elementary example: We were born with the same ears we have now, yet those ears learn over time to make totally different decisions than they would have years before. I’m not just talking about mix decisions.

During a recent tracking session at Odds On Recording in Las Vegas [for PAR's inaugural "Facility Review" in our upcoming November issue — Ed.] I walked in on what I thought was a familiar “analog vs digital” debate. But Sean O’Dwyer, a house engineer with a deep discography, altered the slant.

To paraphrase Sean, the problem with digital has nothing to do with inherent sound quality, but that it is easier; everybody’s gotten lazy. All the records I like, the ones that stand the test of time, were made decades ago when there were no quick fixes — no grid, no elastic time, no Auto-Tune — all techniques which create musical blandness. A producer/engineer was forced to engage the artist and their music on some personal, intimate level and learn what he or she needed to perform and make it a memorable piece of work that someone somewhere will love . . . [read]

Happy Halloween! Trick or treat!

Ah! I love the smell of plug-in progress in the morning. Who knows? Somewhere around Part 42 there might be enough done to actually accomplish something.

Speaking of which: our custom project doesn’t do very much at this point. While there is plenty to add to the custom navigator I fear that the customplugin project has been feeling neglected.

I have a few things to add to the customplugin before returning to the navigator; the navigator will continue to burn a significant amount of my attention…unless I decide to go back to my genetic programming examples. Maybe I’ll toss a coin to see which I decide to do next. Or maybe I’ll just check on the cat.

Anyway, for this post we have a few simple things to do:

• Add the schema file type to the Custom Wizards category
• Add the deployment file type to the Custom Wizards category
• Implement the schema file creation code
• Implement the deployment file creation code

Adding A New Schema File Wizard

You know the drill. Follow the yellow brick road:

1. customplugin –> plugin.xml –> Extensions –> org.eclipse.ui.newWizards –> new –> wizard
   • id: customplugin.wizard.file.schema
   • name: Schema File
   • class: customplugin.wizards.CustomProjectNewSchemaFile
   • icon: icons/schema-file_16×16.png [copy another image to your icons folder and point to it here]
   • category: customplugin.category.wizards
   • descriptionImage: icons/schema-file_32×32.png [copy another image to your icons folder and point to it here]
2. Click the class link for CustomProjectNewSchemaFile
3. Everything looks good
4. Click Finish to close the New Java Class Wizard

[If you must: start the runtime workbench, press Ctrl+N and look in the Custom Wizards folder; the Schema File and icon should be visible. Exit the runtime workbench.]

Now that we have a schema file creation wizard defined let’s implement some code.

First the constructor so the wizard window has a title:

CustomProjectNewSchemaFile.java

public class CustomProjectNewSchemaFile extends Wizard implements INewWizard {

    public CustomProjectNewSchemaFile() {
        setWindowTitle("New Schema File");
    }

    ...
}

[Update: In doing the above I remembered that I never got around to doing this for the New Custom Project Wizard. The New Custom Project Wizard post, and the New Custom Project Wizard refactoring post have been updated.]

Next, in init() we save the incoming selection values as we will need them later for the constructor of the file creation page:

    private IWorkbench _workbench;
    private IStructuredSelection _selection;

    ...

    /* (non-Javadoc)
     * @see org.eclipse.ui.IWorkbenchWizard#init(org.eclipse.ui.IWorkbench, org.eclipse.jface.viewers.IStructuredSelection)
     */
    @Override
    public void init(IWorkbench workbench, IStructuredSelection selection) {
        _workbench = workbench;
        _selection = selection;
    }

    ...

In addPages() we call a class we haven’t created yet: WizardSchemaNewFileCreationPage. It subclasses WizardNewFileCreationPage which does exactly what we want: create a file for us. This is just another reason why it is so important to know what pieces are available within Eclipse for your use.

    private WizardNewFileCreationPage _pageOne;

    ...

    @Override
    public void addPages() {
        super.addPages();

        _pageOne = new WizardSchemaNewFileCreationPage(_selection);

        addPage(_pageOne);
    }

    ...

The variable declaration for _pageOne is purposely declared as WizardNewFileCreationPage even though the call in addPages() is to WizardSchemaNewFileCreationPage. We are only overriding method calls to facilitate the initialization of the object. Create the new class: press Ctrl+1 on the line in addPages() and select Create Class WizardSchemaNewFileCreationPage. It should automatically select WizardNewFileCreationPage as the superclass. Click Finish to create the new class.

Implement WizardSchemaNewFileCreationPage with:

public class WizardSchemaNewFileCreationPage extends WizardNewFileCreationPage {

    public WizardSchemaNewFileCreationPage(IStructuredSelection selection) {
        super("Custom Plug-in Schema File Wizard", selection);

        setTitle("Schema File Wizard");
        setDescription("Create a Schema File");
        setFileExtension("xml");
    }

    @Override
    protected InputStream getInitialContents() {
        String xmlTemplate = "<hc-schema>\n"
            + "  <tables></tables>\n"
            + "  <filters></filters>\n"
            + "  <views></views>\n"
            + "</hc-schema>\n";
        return new ByteArrayInputStream(xmlTemplate.getBytes());
    }
}

The constructor above speaks for itself. The getInitialContents() not so much. This method is used by the wizard to find default contents for the new file if one is created. Since this is my schema file I now have a test version of the file to display. Since this will be refactored into another file we are safe hard-coding it for now.

Returning to CustomProjectNewSchemaFile: Add the following to performFinish():

    @Override
    public boolean performFinish() {
        boolean result = false;

        IFile file = _pageOne.createNewFile();
        result = file != null;

        if (result) {
            try {
                IDE.openEditor(_workbench.getActiveWorkbenchWindow().getActivePage(), file);
            } catch (PartInitException e) {
                e.printStackTrace();
            }
        } // else no file created...result == false

        return result;
    }

The code is simple and self explanatory except for the call to openEditor();it automatically opens the editor for our XML file using whatever editor has been configured for XML files or the default editor if an XML editor is not available. The first argument to openEditor() needs a reference to IWorkbenchPage and we get it by asking the workbench for it. A small price to pay to have the editor opened automatically for us.

Go ahead and try the runtime workbench to check out your handiwork. You should be able to create a plain vanilla resource project and create a schema file to go with it. Life is good.

With that test out of the way we are now emboldened to use a template file instead of a hard coded XML string.

Create a folder named templates under your customplugin folder. In the templates folder create a file named schema-template.xml. Insert the following XML into the file.

<hc-schema>
    <tables>
    </tables>
    <views>
    </views>
    <filters>
    </filters>
</hc-schema>

With the above in place update getInitialContents():

WizardSchemaNewFileCreationPage.java
    protected InputStream getInitialContents() {
        String templateFilePath = "/templates/schema-template.xml";
        InputStream inputStream = null;
        try {
            inputStream = Activator.getDefault().getBundle().getEntry(templateFilePath).openStream();
        } catch (IOException e) {
            // send back null
        }

        return inputStream;
    }

Confirm nothing is broken by starting the runtime workbench.

Adding A New Deployment File Wizard

Now let’s do the same for the deployment file:

1. customplugin –> plugin.xml –> Extensions –> org.eclipse.ui.newWizards –> new –> wizard
• id: customplugin.wizard.file.deployment
• name: Deployment File
• class: customplugin.wizards.CustomProjectNewDeploymentFile
• icon: icons/deployment-file_16×16.png [copy another image to your icons folder and point to it here]
• category: customplugin.category.wizards
• descriptionImage: icons/deployment-file_32×32.png [copy another image to your icons folder and point to it here]
• Click the class link for CustomProjectNewSchemaFile
• Everything looks good
• Click Finish to close the New Java Class Wizard

[Again, quick test: start the runtime workbench, press Ctrl+N and look in the Custom Wizards folder; the Deployment File and icon should be visible. Exit the runtime workbench.]

Since we already know that we are using the WizardNewFileCreationPage as a subclass for the page that will create our file let’s create it upfront.

public class WizardDeploymentNewFileCreationPage extends WizardNewFileCreationPage {

    public WizardDeploymentNewFileCreationPage(IStructuredSelection selection) {
        super("Custom Plug-in Deployment File Wizard", selection);

        setTitle("Deployment File Wizard");
        setDescription("Create a Deployment File");
        setFileExtension("xml");
    }

    @Override
    protected InputStream getInitialContents() {
        String templateFilePath = "/templates/deployment-template.xml";
        InputStream inputStream = null;
        try {
            inputStream = Activator.getDefault().getBundle().getEntry(templateFilePath).openStream();
        } catch (IOException e) {
            // send back null
        }

        return inputStream;
    }
}

Create another template file in the templates folder named deployment-schema.xml. Contents follow:

<hc-deployment>
</hc-deployment>

The actual wizard code for the CustomProjectNewDeploymentFile also looks suspiciously like the code for the schema file:

public abstract class CustomProjectNewDeploymentFile extends Wizard implements INewWizard {

    private WizardNewFileCreationPage _pageOne;
    private IWorkbench                _workbench;
    private IStructuredSelection      _selection;

    public CustomProjectNewDeploymentFile() {
        setWindowTitle("New Deployment File");
    }

    @Override
    public void addPages() {
        super.addPages();

        _pageOne = new WizardDeploymentNewFileCreationPage(_selection);

        addPage(_pageOne);
    }
    @Override
    public boolean performFinish() {
        boolean result = false;

        IFile file = _pageOne.createNewFile();
        result = file != null;

        if (result) {
            try {
                IDE.openEditor(_workbench.getActiveWorkbenchWindow().getActivePage(), file);
            } catch (PartInitException e) {
                e.printStackTrace();
            }
        } // else no file created...result == false

        return result;
    }

    @Override
    public void init(IWorkbench workbench, IStructuredSelection selection) {
        _workbench = workbench;
        _selection = selection;
    }
}

After all of the above in the runtime workbench you should be able to create a schema file and a deployment file and the default text editor should open once each file is defined in the New File Wizard.

Run a quick test. From the runtime workbench create a project, create a schema file and deployment file.

Woo hoo! All done!

Oh…wait…time to refactor a few things.

Refactor Strings

Time to wash up!

Once again, go to the plugin.xml Overview tab of the customplugin and run the Externalize String Wizard to externalize the two new strings we added. Change:

• wizard.name.0 to wizard.name.schema
• wizard.name.1 to wizard.name.deployment

In the schema file related files refactor:

• the wizard window title to WIZARD_NAME and add $NON-NLS$ using the Quick Fix functionality.
• the WizardSchemaNewFileCreationPage title to PAGE_NAME.

In WizardSchemaNewFileCreationPage:

• Open the Externalize String wizard (one way: hover over one of the strings to open the wizard)
• Change WizardSchemaNewFileCreationPage_0 to WizardSchemaNewFileCreationPage_Schema_File_Wizard by clicking in the desired field and typing Schema_File_Wizard
• Change WizardSchemaNewFileCreationPage_1 to WizardSchemaNewFileCreationPage_Create_a_Schema_File by clicking in the desired field and typing Create_a_Schema_File
• Change WizardSchemaNewFileCreationPage_2 to WizardSchemaNewFileCreationPage_Schema_File_Extension by clicking in the desired field and typing Schema_File_Extension
• Change WizardSchemaNewFileCreationPage_3 to WizardSchemaNewFileCreationPage_Schema_Template_Location by clicking in the desired field and typing Schema_Template_Location
• Click Configure in the Accessor class section at the bottom of the window.
• Click Browse for Class Name and select NewWizardMessages; might as well put these strings with the others.
• Click OK
• Click Next and take a look at the various changes that are about to take place
• Click Finish

Do the same for the WizardDeploymentNewFileCreationPage only use the word Deployment instead of Schema.

A question I have asked myself is: Should the WIZARD_NAME and PAGE_NAME also be externalized? While these posts have been examples of how to do things, with a mix of useful and useless things, the answer is…it depends. If i18n is important to the ultimate user of the plug-in then yes, externalize everything, otherwise don’t sweat it.

[If I were being paid to do this I would fight tooth-and-nail to externalize every last string. It makes absolutely no sense to have to recompile one or more files just because a string has changed.]


Refactor Code

Both CustomProjectNewSchemaFile and CustomProjectNewDeploymentFile have the same constructor, performFinish() and init() methods. Let’s create a new parent class and move everything, but addPages() into it (it is the only method with custom code).

The following will do the trick:

1. Right click in the editor for CustomProjectNewSchemaFile and select Refactor –> Extract Superclass
   • Superclass Name: CustomProjectNewFile
2. In Types to Extract a Superclass From click Add and add CustomProjectNewDeploymentFile
3. In Specify Actions for Members check:
   • _pageOne
   • _workbench
   • _selection
   • performFinish()
   • init()
4. Click Next
5. In Subtypes of Type select init() and performFinish() to be removed from both subclasses. Notice that the constructors have not been recognized as having common behavior.
6. Click Finish.

Oddly enough, when the refactoring is over the superclass has a compile error! How could that be? Well, CustomProjectNewFile is missing the INewWizard interface that is needed to properly find init(). The refactoring missed it, but the compiler didn’t. Manually (yuck) add it to CustomProjectNewFile and remove it from CustomProjectNewSchemaFile and CustomProjectNewDeploymentFile (if you don’t remove it nothing will happen, but your code might develop cooties).

Let’s change the constructors for CustomProjectNewSchemaFile and CustomProjectNewDeploymentFile. Change:

CustomProjectNewSchemaFile.java

    public CustomProjectNewSchemaFile() {
        setWindowTitle(WIZARD_NAME);
    }

to:

CustomProjectNewSchemaFile.java

    public CustomProjectNewSchemaFile() {
        super(WIZARD_NAME);
    }

Change CustomProjectNewDeploymentFile from:

CustomProjectNewDeploymentFile.java

    public CustomProjectNewDeploymentFile() {
        setWindowTitle(WIZARD_NAME);
    }

to:

CustomProjectNewDeploymentFile.java

    public CustomProjectNewDeploymentFile() {
        super(WIZARD_NAME);
    }

Use quick fix to create the new constructor in the CustomProjectNewFile parent class:

    public CustomProjectNewFile(String wizardName) {
        setWindowTitle(wizardName);
    }

Not too shabby.

Run a quick test if you are so inclined.



What just happened?

Well, this was an interesting visit. We certainly coded more than usual for the customplugin, but it was all pretty trivial.

We created two new wizards based on the built-in file creation page and create two templates so our custom files have a good starting point.

The refactoring will make changing labels and such easier.

The body count so far:
customplugin: 11 classes, one properties file
customnavigator: 13 classes

Next post: back to the Custom Navigator, probably to display the Stored Procedure category with a Java file as an entry. The deployment file is not displayed, but will be found in the deployment-files folder.

Unless I decide to go back to GP for a while.

In celebration of this religious holiday go have some candy.

(Anybody seen a cat?)

References and Thanks

How to create a new File Wizard? for reminding me about bundle functionality.

Code

CustomProjectNewFile.java

/**
 * Coder beware: this code is not warranted to do anything.
 *
 * Copyright Oct 31, 2009 Carlos Valcarcel
 */
package customplugin.wizards;

import org.eclipse.core.resources.IFile;
import org.eclipse.jface.viewers.IStructuredSelection;
import org.eclipse.jface.wizard.Wizard;
import org.eclipse.ui.INewWizard;
import org.eclipse.ui.IWorkbench;
import org.eclipse.ui.PartInitException;
import org.eclipse.ui.dialogs.WizardNewFileCreationPage;
import org.eclipse.ui.ide.IDE;

public abstract class CustomProjectNewFile extends Wizard implements INewWizard {

    protected WizardNewFileCreationPage _pageOne;
    private IWorkbench _workbench;
    protected IStructuredSelection _selection;

    public CustomProjectNewFile() {
        super();
    }

    @Override
    public boolean performFinish() {
        boolean result = false;

        IFile file = _pageOne.createNewFile();
        result = file != null;

        if (result) {
            try {
                IDE.openEditor(_workbench.getActiveWorkbenchWindow().getActivePage(), file);
            } catch (PartInitException e) {
                e.printStackTrace();
            }
        } // else no file created...result == false

        return result;
    }

    @Override
    public void init(IWorkbench workbench, IStructuredSelection selection) {
        _workbench = workbench;
        _selection = selection;
    }

}

CustomProjectNewSchemaFile.java

/**
 * Coder beware: this code is not warranted to do anything.
 *
 * Copyright Oct 31, 2009 Carlos Valcarcel
 */
package customplugin.wizards;

/**
 * @author carlos
 *
 */
public class CustomProjectNewSchemaFile extends CustomProjectNewFile {

    private static final String WIZARD_NAME = "New Schema File"; //$NON-NLS-1$
    /**
     *
     */
    public CustomProjectNewSchemaFile() {
        setWindowTitle(WIZARD_NAME);
    }

    @Override
    public void addPages() {
        super.addPages();

        _pageOne = new WizardSchemaNewFileCreationPage(_selection);

        addPage(_pageOne);
    }
}

CustomProjectNewDeploymentFile.java

/**
 * Coder beware: this code is not warranted to do anything.
 * Copyright Oct 31, 2009 Carlos Valcarcel
 */
package customplugin.wizards;

/**
 * @author carlos
 */
public class CustomProjectNewDeploymentFile extends CustomProjectNewFile {
    private static final String WIZARD_NAME = "New Deployment File"; //$NON-NLS-1$

    public CustomProjectNewDeploymentFile() {
        setWindowTitle(WIZARD_NAME);
    }

    @Override
    public void addPages() {
        super.addPages();

        _pageOne = new WizardDeploymentNewFileCreationPage(_selection);

        addPage(_pageOne);
    }

}

WizardSchemaNewFileCreationPage.java

/**
 * Coder beware: this code is not warranted to do anything.
 *
 * Copyright Oct 31, 2009 Carlos Valcarcel
 */
package customplugin.wizards;

import java.io.IOException;
import java.io.InputStream;

import org.eclipse.jface.viewers.IStructuredSelection;
import org.eclipse.ui.dialogs.WizardNewFileCreationPage;

import customplugin.Activator;

/**
 * @author carlos
 *
 */
public class WizardSchemaNewFileCreationPage extends WizardNewFileCreationPage {

    private static final String PAGE_NAME = "Custom Plug-in Schema File Wizard"; //$NON-NLS-1$

    public WizardSchemaNewFileCreationPage(IStructuredSelection selection) {
        super(PAGE_NAME, selection);

        setTitle(NewWizardMessages.WizardSchemaNewFileCreationPage_Schema_File_Wizard);
        setDescription(NewWizardMessages.WizardSchemaNewFileCreationPage_Create_a_Schema_File);
        setFileExtension(NewWizardMessages.WizardSchemaNewFileCreationPage_Schema_File_Extension);
    }

    @Override
    protected InputStream getInitialContents() {
        String templateFilePath = NewWizardMessages.WizardSchemaNewFileCreationPage_Schema_Template_Location;
        InputStream inputStream = null;
        try {
            inputStream = Activator.getDefault().getBundle().getEntry(templateFilePath).openStream();
        } catch (IOException e) {
            // send back null
        }

        return inputStream;
    }

}

WizardDeploymentNewFileCreationPage.java

/**
 * Coder beware: this code is not warranted to do anything.
 *
 * Copyright Oct 31, 2009 Carlos Valcarcel
 */
package customplugin.wizards;

import java.io.IOException;
import java.io.InputStream;

import org.eclipse.jface.viewers.IStructuredSelection;
import org.eclipse.ui.dialogs.WizardNewFileCreationPage;

import customplugin.Activator;

/**
 * @author carlos
 *
 */
public class WizardDeploymentNewFileCreationPage extends WizardNewFileCreationPage {

    private static final String PAGE_NAME = "Custom Plug-in Deployment File Wizard"; //$NON-NLS-1$

    public WizardDeploymentNewFileCreationPage(IStructuredSelection selection) {
        super(PAGE_NAME, selection);

        setTitle(NewWizardMessages.WizardDeploymentNewFileCreationPage_Deployment_File_Wizard);
        setDescription(NewWizardMessages.WizardDeploymentNewFileCreationPage_Create_a_Deployment_File);
        setFileExtension(NewWizardMessages.WizardDeploymentNewFileCreationPage_Deployment_File_Extension);
    }

    @Override
    protected InputStream getInitialContents() {
        String templateFilePath = NewWizardMessages.WizardDeploymentNewFileCreationPage_Deployment_Template_Location;
        InputStream inputStream = null;
        try {
            inputStream = Activator.getDefault().getBundle().getEntry(templateFilePath).openStream();
        } catch (IOException e) {
            // send back null
        }

        return inputStream;
    }

}

]]> http://kricharddouglas.wordpress.com/2009/10/31/a-writers-dream-blogging-platform-wordpress/ Sat, 31 Oct 2009 04:50:00 +0000 kricharddouglas http://kricharddouglas.wordpress.com/2009/10/31/a-writers-dream-blogging-platform-wordpress/

There is one thing in common with all of my websites with one exception; all 13 of them. Although some look like custom designed websites, nearly all of them are based on WordPress. Even my main copywriting website, The Great Writer, is based on the WordPress platform.  The reason is because WordPress is a work of genius.

Few open source projects can claim the results and global popularity of WordPress. WordPress has been downloaded millions of time; that’s right MILLIONS. The same can be said of the thousands of themes and the thousands of plug-ins.  For a writer, WordPress is the ultimate whiteboard. 

Unlike this blog and one Blogger blog, all of my WordPress installs are self-hosted.  They run the gamet from my three retail portal sites, The Smiling Bride, Internet Mall and Buy it, Try it to my content development site, Solution Content. The  look of each of these sites is completely different and unique. Each is technically a blog, but none of them look like a blog.

My consumer financial eduction site Considering Money looks a little like a blog, but it uses a popular template that I modified and works perfectly for it’s intended purpose. My site designed for professional advisors, Advisors Friend,  looks very little like a WordPress blog and has a classic look, but at it’s heart is a WordPress blog.

One of my highest traffic blogs is a photo blog called PhotoEscape. I invented the name ten years ago and it has been stolen a half dozen times or more. The template that PhotoEscape uses is a work of art. I use a ‘magazine’ style blog template for my resort review site; The Ideal Resort.

One of my early blogs was a consumer electronics review site. Another WordPress based site, this one has the most unusual name of all; Shnarkel. This has always been one of my favorites and I still believe the developer of the template is brilliant. This one is based on the Box Tube theme by Dezzain Studio and comes closest to looking like a blog.  I used to use Shnarkel to show examples of my ability to write product reviews. Later, I added some affiliate ads, but it has always been primarily a site about consumer electronics.

One thing that all of these sites illustrate is that WordPress is diverse and adaptable to nearly any topic or style. As a copywriter and content developer, WordPress is the ultimate method to display my writing. Best of all, even with all of the incredible coding, templates and plug-ins, WordPress remains free and most themes remain free.

With an enormous amount of WordPress expertise, I have offered clients the chance to create an online presense for very little money. All they need to do is get a hosting account with WordPress capabilities. The hosting service ideally offers an easy WordPress install with Simple Scripts or Fantastico. Then, if they don’t already have a domain name, they just need to make the small investment in a domain name. I offer a service that develops a great domain name and handles moving the domain name to the new name server and installing WordPress.

This is an easy way for a small business to get online and get a good looking site at the same time. The search engines like WordPress a lot and my SEO services offers the new WordPress site owner the opportunity to max out their SEO potential.  WordPress can do it all and I am a big fan.

]]> http://xollothnews.wordpress.com/2009/10/31/mypocotoolbar-%ce%b7-%ce%ba%ce%b1%ce%bb%cf%8d%cf%84%ce%b5%cf%81%ce%b7-%ce%b5%ce%bb%ce%bb%ce%b7%ce%bd%ce%b9%ce%ba%ce%ae-toolbar/ Sat, 31 Oct 2009 04:05:52 +0000 xollothnews http://xollothnews.wordpress.com/2009/10/31/mypocotoolbar-%ce%b7-%ce%ba%ce%b1%ce%bb%cf%8d%cf%84%ce%b5%cf%81%ce%b7-%ce%b5%ce%bb%ce%bb%ce%b7%ce%bd%ce%b9%ce%ba%ce%ae-toolbar/
myPocoToolbar – Η καλύτερη Ελληνική toolbar! | Techcloud.gr

Όλα όσα ψάχνετε από μια toolbar είναι εκεί! Χωρίς να χρησιμοποιείτε καν το πληκτρολόγιο σας μπορείτε να περιηγηθείτε στα πιο δημοφιλή sites, να ακούσετε από Heavy Metal μέχρι και RnB ξένη ή ελληνική μουσική, να παρακολουθήσετε τηλεόραση live, να παίξετε online παιχνίδια ή να ενημερωθείτε ακόμα και για τον καιρό.[next]

 


]]>