It is currently May 27th, 2024, 8:20 pm

Rainmeter / WINE / Linux

General topics related to Rainmeter.
User avatar
Caledfwlch
Posts: 20
Joined: April 12th, 2009, 3:33 am
Location: TN

Rainmeter / WINE / Linux

Post by Caledfwlch »

** Update: 4/30/09, see edit.
** Update: 7/28/09, see edit #2.

Before there are massive protests and strikes in regards to mentioning Linux, might I be so bold to say the fact that I am mentioning it within the contents of this post is not a matter of negativity. WINE, a Windows layer (or emulator, the debate is not for this thread), has made Linux operation of Rainmeter nearly possible with ongoing updates. It is nearly achievable - the program installs, the program operates, and skins, while not loaded on the desktop in visible fashion, are "trying" to load their procedures.

Since the last number of months regarding Rainmeter and the most recent release (0.14 by my count), WINE has improved it's usability greatly for several programs I use regularly, Rainmeter being one of them. Already stated in a bland way, I know, but using KDE 4.2.2, Rainmeter 0.14, and WINE 1.1.18 (released March 27th, 2009, WINE 1.1.19 is already released as of April 10th, 2009), Rainmeter installs without issue. Rainmeter loads without issue, even placing the running systray icon within the KDE system tray. Right clicking on the option brings about the menu, and allows configuration for various skins' text files via the WINE'd Notepad.

The problem, as described, presents itself when trying to load a skin. The skin "loads", however no graphic is displayed. As a matter of fact, not much of anything is displayed aside from a portion of the desktop wallpaper copying itself onto the small window. On fumbling around, right clicking the desktop every-so-often in various locations, the skin's operating area can be found if it wasn't visible initially. Once found, you can edit every aspect of the skin you need, even though the skin is loaded, but not "loaded". The program's stability, even though the skin fails to display, is quite secure.

I'd be foolish to say I knew whether or not this means Rainmeter working in WINE is only a few short versions away, if not Rainmeter already working without my knowing of how to accomplish the task. The simple fact of the matter is - I haven't fooled with it that much. I want Rainmeter operational, obviously, but I am understanding of those people involved in it's development: it's a royal pain for conversion, if not even possible for conversion, by the amount of code involved. I remember, when the old forum was active, the mentions in regards to having a native Linux Rainmeter client and the impossible task it was stated to be.

No matter the case, I am glad for Rainmeter's continued success throughout the years - it's been an enjoyable eye candy addition to many a screen shot I've seen. I hope that in time, in the event Rainmeter is still on a Windows-only line of development, WINE can readily handle the process. Nonetheless, thanks for your hard work, and I look forward to future Rainmeter developments.

** edited update:
Rainmeter is working in WINE thanks to those within this thread and the WINE volunteers and fellow bug reporters I've came in contact with over the past number of weeks. However, the process is not flawless, and it doesn't always appear seamlessly on the desktop. Personally speaking, leaving Rainmeter as an object on the desktop without a reboot for days is probably the best method, as there is some effort in getting Rainmeter operational even though this thread aides with the process.

** NEWLY EDITED, SEE NEW UPDATE **

Rainmeter is available on the WINE Application Database, and the entry is looking for your personal experiences. Submitting your time spent with both programs is worthwhile for both applications.

** edited update #2:

It's been awhile since my posting, but I've some new information regarding the install of Rainmeter for a more fluid HOWTO. Here's a better understanding, for all involved, the process of making a working Rainmeter under WINE.

1. Download the new Rainmeter 32-bit executable (suitable for this machine, unsure of the 64-bit version), Rainmeter-0.14.1-r103-32bit-beta.exe

2. Download and install WINE, if not downloaded and installed already.

3. Grab a program in Linux called 'winetricks' and allow it to install the gdiplus library.

4. Install Rainmeter using WINE normally.

5. Enter winecfg and, under Application Settings, add the Rainmeter.exe application.

6. Change the Rainmeter.exe 'Windows version' to Windows 98.

7. From an X prompt, enter the Rainmeter directory (usually under ~/.wine/drive_c/Program\ Files/Rainmeter) and type "wine rainmeter.exe" (no quotes).

8. Rainmeter should now be operational in the system tray. If it is not, post in this thread.

9. If your skins are located under ~/.wine/drive_c/Program\ Files/Rainmeter/Skins, then you'll need to right click on the Rainmeter icon in the system tray and Edit Settings.... Change the "SkinPath=" directory to C:\Program Files\Rainmeter\Skins\.

.. a minor edit: It's notable this change needs to occur because of legit reason. WINE looks for it's files under /home/<username>/.wine/drive_c/, which thereby begins the Windows/DOS C:\ location. However, under the new Rainmeter's skin location (and due to a directory link apparently not evident in Windows), the Rainmeter skin Tranquil is installed to/located at /home/<username>/Rainmeter/Skins/. I recommend the change stated above because it's a suitable fix to a possible problem, however and admittedly, it's another step that may be required regarding a successful and working Rainmeter under Linux and WINE.

10. If you're using Compiz: Enter the CompizConfig Settings Manager and visit the Window Decorations option. Ensure Window Decorations is clicked as enabled, and under Shadow Windows, replace (any) with: "(any) & !class=Wine & !name=rainmeter.exe" (no quotes). If this is somehow incorrect and affects other Wine windows, I am, of course, open to suggestions. If this option is not changed, any loaded Rainmeter skin will appear with a shadowed edge around it's invisible borders.

11. If you're using Compiz: Once your skin is loaded, you may have to click the Rainmeter system tray icon, visiting "Skin Name" -> Position -> Bottom / On Desktop. Clicking either option and then moving the Rainmeter skin just a pixel or two one way or the other will cause the skin to stay on one desktop instead of all active desktops (the Compiz default is 4). Be wary: if you have a window open underneath the skin, it will continue displaying this way until an exit/reload of Rainmeter and the Bottom / On Desktop step is performed again (without a window underneath the skin).

Step 11, unlike other steps, will need to be performed each time Rainmeter is executed under WINE. In most cases, for me, this is every reboot of the system.

After being forced to format recently due to a screwup which I, myself, caused, I'm greatful to be able to add more information here in a way that's sure to help newcomers. If there are any issues presented in your own personal install of Rainmeter under WINE, I would appreciate knowing them within this thread.
Last edited by Caledfwlch on July 29th, 2009, 5:38 pm, edited 6 times in total.
dragonmage
Developer
Posts: 1270
Joined: April 3rd, 2009, 4:31 am
Location: NC, US

Re: Rainmeter / WINE / Linux

Post by dragonmage »

Firstly, welcome to the forum , thank you for your post and for the information. Not being a Linux user myself I was not aware Rainmeter had issues with WINE.

Secondly, we'll see if we can't get a developer to weigh in on this matter.

Just out of curiosity, does Rainlendar display properly in WINE?
User avatar
Caledfwlch
Posts: 20
Joined: April 12th, 2009, 3:33 am
Location: TN

Re: Rainmeter / WINE / Linux

Post by Caledfwlch »

dragonmage wrote:Just out of curiosity, does Rainlendar display properly in WINE?
Upon downloading Rainlendar and giving it a try, I can confirm it does operate (seemingly) well within WINE. The calendar is displayed, the 'To Do' window is displayed, and the Event window is displayed. I can add things to these windows, and the added items do display. The skin does change when selected in the configuration.

There may be a slight problem in regards to transparency, however. The Shadow4 background is nothing but black, and the Chromophore background reveals a black, squared border.

Thank you for responding so quickly, and, if possible, I look forward to helping provide as much information as I can for a workable Rainmeter within WINE, at the least.
User avatar
taneth111
Posts: 10
Joined: April 7th, 2009, 4:21 am
Location: IRC Isles

Re: Rainmeter / WINE / Linux

Post by taneth111 »

WINE has some issues with transparency at the moment, so a lot of different apps have problems. Does someone want to add Rainmeter into the WINE AppDB?
I wouldn't bother adding Rainlendar(2), as you can get a native linux compile anyway.
sgtevmckay

Re: Rainmeter / WINE / Linux

Post by sgtevmckay »

This is an excellent Aticle, and I thank you for it.
I hope that you will be able to keep the community here appraised of the ongoing Wine Updates and the Rainmeter compatibiliuty.

Linux is a fast growing OS, and many, including myself, have come to embrace the multi-OS since the last forums

Being a Ubuntu user, I have yet to try Rainmeter with WINE, Shoot, normally when I use any Linix distro, I am true to it, and it's capabilities, but I do use WINE with my portable Ubuntu distro.

Either way I pose the following question in concern to the initial article:
Are there viewable differences when you change the Rainmeter's viewable layering control.
You have the following options:
Screenshot - 4_12_2009 , 1_54_13 PM.jpg
Will an adjustment in any of these settings improve the visibility of the Configs?

Let us know, I am most curios

Thanks again.
User avatar
Caledfwlch
Posts: 20
Joined: April 12th, 2009, 3:33 am
Location: TN

Re: Rainmeter / WINE / Linux

Post by Caledfwlch »

I'll definitely give a go at attempting to keep the Rainmeter and WINE interested communities abreast of any new developments. WINE is a fluid entity - it's versions ever changing the finalized outcome of the product. Sometimes, a random version of WINE works with a random version of the program you're attempting to try, and other times it fails dramatically. As of late, however, the failing tidbit has been very nil. WINE's operation by comparsion to a year or two ago is simply not comparable, the progress has been far too great.

Thus, with this, there are some things I'd enjoy posting for information purposes regarding Rainmeter, not the least of which involving what occurs when changing the screen positions.

I'm using a random skin called LunaR. Here's the log:
DEBUG: (00:00:00.000) Path: C:\Program Files\Rainmeter\
DEBUG: (00:00:00.000) IniFile: C:\Program Files\Rainmeter\Rainmeter.ini
DEBUG: (00:00:00.001) SkinPath: C:\Program Files\Rainmeter\Skins\
DEBUG: (00:00:00.002) PluginPath: C:\Program Files\Rainmeter\Plugins\
DEBUG: (00:00:00.046) Refreshing (Name: "LunaR" Ini: "Luna_R3.ini")
DEBUG: (00:00:01.213) Initialization successful.
DEBUG: (00:00:10.789) Refreshing (Name: "LunaR" Ini: "Luna_R3.ini")
Per the log, the skin appears to load fine, even though nothing except a faintly-colored, very transparent box appears on the screen.

As I do run Rainmeter from the command line, the following is output from it's execution (ignore Xlib: extension):
.. $ wine Rainmeter
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
fixme:ole:OLEPictureImpl_SaveAsFile (0x19ecf0)->(0x19fff0, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x19ecf0)->(0x1a2a78, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x19ecf0)->(0x1a44c0, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x19fcf8)->(0x1a5fc0, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x19fcf8)->(0x1a8188, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x19fcf8)->(0x1a9bd0, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x19fcf8)->(0x1ab6d0, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x19fcf8)->(0x1ae000, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x19fcf8)->(0x1af3c8, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x804540)->(0x804da0, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x804da0)->(0x805af8, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x804da0)->(0x8069d0, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x8079a0)->(0x8059c0, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x8079a0)->(0x808d10, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x806b30)->(0x809d68, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x809c58)->(0x80b3b0, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x809c58)->(0x80c0a8, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x809c58)->(0x80d0e0, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x80cfb8)->(0x80e720, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x80cfe0)->(0x80f418, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x80cfe0)->(0x2199d0, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x80cfe0)->(0x21a678, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x80cfe0)->(0x21afd8, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x80cfe0)->(0x8114e0, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x8113b8)->(0x812188, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x8113b8)->(0x812ab8, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x8113b8)->(0x21ccf0, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x804a18)->(0x21d998, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x804a40)->(0x21e2c8, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x804a40)->(0x814828, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x8142b0)->(0x21f888, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x814788)->(0x815708, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x814788)->(0x816768, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x814d90)->(0x8155a0, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x816628)->(0x818ab0, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x816628)->(0x819af8, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x814df8)->(0x81b178, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x814df8)->(0x81be50, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x814df8)->(0x81ce98, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x81bd98)->(0x81e010, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x81bd98)->(0x81eed8, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x81bd98)->(0x81fd88, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x820ac0)->(0x8229c0, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x822920)->(0x824270, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x822920)->(0x825eb8, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x81d638)->(0x8265d8, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x81d638)->(0x827ae8, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x81d638)->(0x82cce0, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x825080)->(0x82b838, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x825080)->(0x831858, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x825080)->(0x8338a0, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x820e48)->(0x8322e8, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x820e48)->(0x838420, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x820e48)->(0x83a2e8, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x820e48)->(0x838f30, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x820e48)->(0x83ee68, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x820e48)->(0x840fb0, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x820e48)->(0x841908, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x820e48)->(0x843200, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x820e48)->(0x847d70, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x846e78)->(0x8316d8, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x846e78)->(0x849f48, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x846e78)->(0x84d7a8, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x838db0)->(0x84c6f8, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x838db0)->(0x8514d8, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x838db0)->(0x853028, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x838db0)->(0x854c00, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x84c638)->(0x8570b0, 0, 0x33c72c), hacked stub.
fixme:ole:OLEPictureImpl_SaveAsFile (0x84c638)->(0x858ce0, 0, 0x33c72c), hacked stub.
(.. x 70 more similar lines with different addresses, edited for forum cleanliness)
fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
fixme:gdiplus:GdipCreateHBITMAPFromBitmap stub
fixme:gdiplus:GdipCreateHBITMAPFromBitmap stub
fixme:gdiplus:GdipCreateHBITMAPFromBitmap stub
fixme:gdiplus:GdipCreateHBITMAPFromBitmap stub
Xlib: extension "Generic Event Extension" missing on display ":0.0".
fixme:gdiplus:GdipCreateHBITMAPFromBitmap stub
fixme:gdiplus:GdipCreateHBITMAPFromBitmap stub
fixme:gdiplus:GdipCreateHBITMAPFromBitmap stub
fixme:gdiplus:GdipCreateHBITMAPFromBitmap stub
fixme:gdiplus:GdipCreateHBITMAPFromBitmap stub
fixme:gdiplus:GdipCreateHBITMAPFromBitmap stub
fixme:gdiplus:GdipCreateHBITMAPFromBitmap stub
fixme:gdiplus:GdipCreateHBITMAPFromBitmap stub
For notation purposes, even loading another skin (one of the default provided) offers the same template - a blank, "transparent" box appearing, no skin display nor information provided. If requested, a screenshot I could certainly provide.

In regards to changing what particular layer Rainmeter appears on, there is no change in the program's visibility (via right click on the Rainmeter systray icon -> Skin name -> Position -> Position name). In addition, changing the transparency also appears to have no effect.

If there are any more questions, I'll gladly provide answers if possible.
sgtevmckay

Re: Rainmeter / WINE / Linux

Post by sgtevmckay »

Keep us posted, I am curious to see where this will go, there is a large community of folks that are looking to have Rainmeter on their Linux Distro, by either a WINE solution, or a direct solution.

As the developers are so tied up with correcting current issues, and advancing Rainmeter in it's current state, the chance to program a Linux solution may not be in a foreseeable future.

Another suggestions, for those that come across this post.
If you , or a team of folks you know are willing to tackle a Linux Rainmeter.
If you can get it off the ground and at least get it code line started. i would propose to the admin here that a Linux for Rainmeter forum be started.
Now that is not to say it would be approved. I am one of several voices and all things are approved by majority.

Upon a distribution of the program, at this time, I would be able to offer the download space for free, I would be willing to offer space from my personal web site to a Linux rainmeter, so once it is running, there is a place for Linux folks to go and download it.

Any takers?
User avatar
Caledfwlch
Posts: 20
Joined: April 12th, 2009, 3:33 am
Location: TN

Re: Rainmeter / WINE / Linux

Post by Caledfwlch »

taneth111 wrote:WINE has some issues with transparency at the moment, so a lot of different apps have problems. Does someone want to add Rainmeter into the WINE AppDB?
I wouldn't bother adding Rainlendar(2), as you can get a native linux compile anyway.
As of today, I added Rainmeter to the Wine AppDB. It is currently under authorization. If/when the application is authorized, I'll post the link for others to add their Rainmeter trials.

In addition, adding Rainmeter to the application database is positive in terms of bug reporting regarding WINE. Here again, if/when the application is authorized (and I am available), I will submit a bug report for WINE in regards to Rainmeter and the faulty display currently shown. I may be directed to another bug given WINE's wide array of uses, but it's worth a try in an attempt to solve the issue. Any votes to confirm said bug once submitted would certainly help the cause.

Also, I have applied to be a super maintainer for this particular application within the AppDB. Essentially, a super maintainer allows the power-provided individual to clarify postings, edit said postings, and/or otherwise direct [explain] the ongoings of the application's workability for WINE developers and users viewing the application. Why is this useful? Screenshots can be provided for the product, further explaining the problem (in this instance especially). Other reasons are more simplistic, but base themselves in something relative to order moreso than chaos.

I'll post again when more information is available.
sgtevmckay

Re: Rainmeter / WINE / Linux

Post by sgtevmckay »

Nice.

Let see what pops!?!!
User avatar
Caledfwlch
Posts: 20
Joined: April 12th, 2009, 3:33 am
Location: TN

Re: Rainmeter / WINE / Linux

Post by Caledfwlch »

Rainmeter is now available in the Wine Application Database. [see: http://appdb.winehq.org/ ]

To find Rainmeter, hit 'Browse Apps' on the left table and search for the name 'Rainmeter'. On clicking Update Filter, Rainmeter's link will then display.

The screenshots I've provided, by and large, are random Google searches for Rainmeter displays as I do not have a working Rainmeter to visibly display. Only one of the images provided is of my generic desktop, overlapping the GIMP (an image editor similar to Photoshop), making it visible what exactly is ongoing with the failure of the program.

I have made notations within this particular photograph about what is ongoing. I have also linked to a bug report I've filed regarding the lack of skin display and the errors Rainmeter currently produces.

I can't tell you how well this will be perceived. I know WINE's community to be fruitful and worthwhile, but those stuffing the bugs tend to get annoyed with random bugs being thrown their way. While I wish I could say I knew everything there was to know about being involved with WINE, the truth is this just isn't the case. I have made such an appeal clear in my posting of the bug report, and if another bug is available I'm hoping they'll be generous in allowing me to atleast reference said bug as the issue.

Notwithstanding, the program is added and the bug is filed. If you're interested in joining the effort, the #1 thing for you to do is to log in with Wine's application database and their bugzilla to a.) add your own account with WINE and b.) actually vote for the bug presented and add your own bug (if necessary).

If there are any more developments, I'll certainly post them here. If you have concerns or comments about the bug report and/or the application addition to the AppDB, I'll certainly take those critiques, too.