pageear dev progress

New feature. Now besides an image file (JPG, GIF or PNG) you can upload a flash movie (SWF) to use on peel:

• Added SWF files support

Commited to CVS. It is just available if you checkout from CVS and would be available on pageear home page in dev release as soon as the drupal packaging system run again (it runs every 12 hours for dev versions).

After you configure a sound (load, open, close) for a specific pageear there were no posibility to remove it on that pageear. That feature is now included.

It was difficult to know exactly when you were over close button. That is improved now.

Two new features:

• Improved close button
• Added remove sounds feature

If you have more than one pageear configured on same page, the first one in the pageear list is shown.

An example case, first pageear configured with no visibility settings (all pages). Second pageear configured for front page. On front page would be shown the first pageear, second pageear would never be shown. There was no way to change the pageear order so the only way to do it correctly was to first add the pageear configured for front page and then the more generic pageear configured for all pages.

But this was a problem if you first decide you want a pageear for all pages and a week or a month later you decide you want a specific one on front page. To do that first you would need to remove the pageear for all pages (or edit that one to be the one for front page) and start from scratch.

Imagine you have a lot of pageears configured and you find yourself in a problem like that. You need a pageear to be the first of the list and there is no way to reorder them. Would you need to remove all pageears and start from scratch? That would be a pain.

Now that is solved:

• Added order pageears list.

For multi-site drupal installations a new feature is added too:

• Added per site visibility settings.

There were two peel styles till now:

• Added a third peel style.

There was a restriction on SWF support. Only flash movies with no interactivity where supported. The peel had to track the mouse out to unpeel and the mouse click to do the link to the configured URL for the ad. So I worked on it to provide the possibility to include interactive flash on peel (on flag makes no sense, as soon as you enter the flag the peel is opened, you can upload flash for the flag just to provide it with some motion, a flashing new sign, an important flashing sign, and so on...).

So how to support interactive flash. First we need the posibility to disable the link:

• Added enable/disable link feature.

Second we need mouse out disable. But, that is just available, there is not mouse out when the close button is enable. If you want an interactive flash on peel you would like the peel to be totally opened so the user can interact with it so the close button enabled is what you need.

So to use an interactive flash: disable link, enable close button and upload an interactive flash to peel.

Well it needed more flash work to make it work but for the end user is just that.

This is the last change I'm planning to do by now.

The only other issues I could think to include in 2.1 are: more peel styles, drop the no sense per site visibility and save pageear parameters on database serialized (the pageears table has now a lot of columns and I think it would be enough with the index column -peid-, the -weight- column and a column with the -rest of parameters- serialized). But all that can be done after the RC release if needed.

So I think it is prepared to be a 2.1 release candidate. But first it needs some tests to confirm all is working as it should. So if someone would like to test and give me feed back would be very helpful. I would do some more test too.

I have commited to CVS and in a few hours it would be available on the project page to be downloaded.

If you think there is still something that could be useful to include just write a feature request and I'll try. All ideas are welcome.

If someone using the dev version could report how it is working for them it would be very helpful.

I think I tested it myself properly but more opinions would be nice.

I'm going to be without the computer I'm using to code pageear module for a few days. I think it is prepare to be released as 2.1 RC. I'm going to take this oportunity to wait those few days for any comment or any issue reported for dev version.

If any issue appears related to the current version I would be able to try to solve it too.

As soon as I have the computer back and if it seems a good idea I would drop the per site visibility feature and release the 2.1 RC version.

Other things I could work on that version later are:

• Serialization of pageear parameters to reduce the number of columns on pageears table in database.
• A visual preloader with the posibility to enable and disable it.
• More peel styles.

• I changed how the flash are embedded in the page. Now I use swfobject instead of propietary adobe AC_RunActiveContent.
• Added topleft and topright pageear on the same page support. Now you can enable a pageear on topleft and a pageear on topright on the same node.
• The per site visibility settings have been finally dropped.

After copy this module inside my modules directory, nothing is happen on ma modules list in admin. I don't now what is happen.

Please you have to open a new issue with the version you are reporting the problem for and as many information you think it is necessary.

I can then answer there with the installation process. Though it is like any other module but just to confirm you are doing the correct process. If you had a previous version of the module you must not forget update.php.

You can find a howto in: Installing contributed modules.

After it is installed and if you have problems on how to use the module, a howto can be found on the project page. You can find it here, pageear howto.

Sorry but this thread is for information on the development progress and the new features that are being implemented.

I don't know why I haven't added it before. New feature:

• Use CSS position model absolute or fixed.

For those who are familiarized with CSS absolute and fixed would know what this will do. For those who don't know it is simple:

• With absolute position model the pageear will always be at the top of the page and when you scroll the page the pageear would start dissapearing as the rest of the upper piece of the page.
• With fixed position model the pageear will always be at top of the viewport so as you scroll the pageear will scroll and remain always on view.

• Show a wait icon while pageear is loading.

• Bottom left and bottom right positions have been added.

Only fixed position model is available for these bottom positions.

Pageear module changes name, now it is Curlypage. Any newer feature or bug fix would be done there.