Have you ever wondered how Rainmeter started? Do you wanna explore the source code files from Rainmeter's earliest days, as well as explore the source code for its brothers and sisters?
Well, that last question is kinda creepy, and I don't know why I phrased the questions the same way they speak in teleshopping/dropshipping, but I have archived the source code and files for some of Rainy's projects from 1999 to 2006, this includes files older than and not present on https://builds.rainmeter.net/older/ or https://github.com/rainmeter/rainmeter-svn-snapshot . As well, I have read some of the files from around that time in order to make an idea of the rough history of Rainmeter. The history is more a list of my observations than an empricial study.
I've archived both the source code and binaries of projects Rainy created very early in the day. Without further ado:
Before we can talk about Rainy's projects, we first have to talk about what Litestep is. Quoting Wikipedia:
Litestep replicated Windows' compoenents inside it, replacing the explorer.exe shell at the Windows level (inside the "C:\Windows\system.ini" file), and allowed users to modularly modify certains aspects, with the users loading their own "modules" (skins+plugins) and "themes" (layouts) to the "C:\LiteStep\step.rc" file. Sadly, as Windows got more and more locked down, and added more to its UI to fill the gap Litestep took advantage of, the Litestep project stalled and had less power to modify/read Windows, with the latest Windows version supported being Win7.
Some concepts from Litestep have carried over to Rainmeter, an nonexaustive list of them being:
As described by the Rainminder manual:This looks absoltuley NOTHING like the Rainmeter syntax we have today, it looks something more like BASIC than what Rainmeter and HTML are, which is a from of a markdown language. Imagine if we programmed HTML like this though.
To describe it using Rainmeter terminology, this is just a Bitmap meter with mouse actions. Back in the day, transparency effects for images and tooltip windows - like what Rainmation offers - were rare. Withn most programs, transparency was done using magic pink (tm) (which existed for a brief period of time in Rainmeter 0.1 too, where Strings with FontColor=FF00FF were invisible), thus you had only fully transparent or fully opaque bitmaps. Ranimation offered per-pixel transparency from 0 to 255. In the 2000s this was very impressive to see.
As for some concepts from Rainmation that have carried over, only the !EnableCommand and !DisableCommand bang terminology carried over (the measures were part of the bang instead of separate, in here, enabling and disabling the bitmap would have pasically stopped the "bound" measure).
Some concepts borrowed from LsBox seem to be:
If we look inside the code, we can find the !LsBoxHook bang and the code executed when the bang is called.
Aaaaaaaaaand there's nothing, not even an easter egg, sad :(
Quoting Rainlendar 0.1's Manual (which is accidentally called "Rainmation Manual" in the header <title>):Starts to look more and more similar to what Rainmeter ended up being, although it seems like you are just limitied to customizing prefabs instead of creating individual sections for everything.
Still not what it is today, looks very similar to Rainlendar, you were only able to modify prefabs and nothing else. It is worth pointing out again that to make stuff invisible, you had to make the color pink (as instructed in the Readme.txt), borrowing from Rainimation (and every other app that did transparency back in the day). You were not able to load more than one skin.
Yup, meters and measures as separate sections didn't exist, Meters (called Types) had their Measures in them, this feels like code you see in your dreams. The concept of a setting file for individual skin(s) window settings being separate from the skin also didn't exist yet. You were also still not able to load more than one skin.
It seems like Rainmeter once had a plugin for Motherboard Monitor 5... it was not documented properly, it's not even on the latest docs. It's most likely not on the docs because the code for the plugin was completly removed from the Rainmeter source code, as compared to today where stuff like the iTunes plugin is just left there...
We're finally starting to reach what we have today, here's an example Rainmeter.ini fileThis looks like something we can even run today, it also shows why Prefix and Postfix exist, Rainy didn't create the Text option yet. Image meters also didn't exist yet, with only Bitmap meters being availiable.
From here on out, everything else is history. Rainmeter was abandoned between 2006-2009 and was picked up by the community (with members from back then still being active today), which brought it up to what it is today. Thanks for everyone who helped with the project, from start to finish.
I also hope it was an interesting read. Have a nice day!
Sources for Litestep info and Rainmeter archived files
https://github.com/lsdev/litestep-/blob/master/docs/manual.txt
https://shellfront.org/
Well, that last question is kinda creepy, and I don't know why I phrased the questions the same way they speak in teleshopping/dropshipping, but I have archived the source code and files for some of Rainy's projects from 1999 to 2006, this includes files older than and not present on https://builds.rainmeter.net/older/ or https://github.com/rainmeter/rainmeter-svn-snapshot . As well, I have read some of the files from around that time in order to make an idea of the rough history of Rainmeter. The history is more a list of my observations than an empricial study.
I've archived both the source code and binaries of projects Rainy created very early in the day. Without further ado:
- Rainminder Source Tree / Rainminder Binaries
- Rainmation Source Tree / Rainmation Binaries
- Rainlendar Source Tree / Rainlendar Binaries
- Rainmeter Source Tree / Rainmeter Binaries
Litestep
As many are aware, Rainmeter originally started as a Litestep LoadModule plugin, however, Rainy has created earlier projects that could also be catalogized as widgets, which can be compared to what Rainmeter eventually became.Before we can talk about Rainy's projects, we first have to talk about what Litestep is. Quoting Wikipedia:
Litestep was first released to the public on 14 December 1997 by Francis "Lonerunnr" Gastellu, which he developed between 1997-1998, until it was abandoned and picked up by the LiteStep Development Team between 1998-2009. (sounds familiar?)LiteStep is a Windows Shell replacement [...] LiteStep replaces the Windows Shell which provides access to the graphical user interface on Windows-based computers.
Litestep replicated Windows' compoenents inside it, replacing the explorer.exe shell at the Windows level (inside the "C:\Windows\system.ini" file), and allowed users to modularly modify certains aspects, with the users loading their own "modules" (skins+plugins) and "themes" (layouts) to the "C:\LiteStep\step.rc" file. Sadly, as Windows got more and more locked down, and added more to its UI to fill the gap Litestep took advantage of, the Litestep project stalled and had less power to modify/read Windows, with the latest Windows version supported being Win7.
Some concepts from Litestep have carried over to Rainmeter, an nonexaustive list of them being:
- The "Bang" terminology
- The "Exclamation Point !" + "Command Name" (!Command) format
- The !ModuleCommand format, in Rainmeter the deprecated !Rainmeter... format (e.g. !RainmeterShow)
- Multiple Bangs being called like [!Command1][!Command2]
- ["C:\path\to\file.exe"]
- The !About, !Quit, !Refresh bangs and the deprecated !Execute bang
- The !Toggle... bang
- Loading themes by calling the .exe and then the file (in Litestep litestep.exe C:\LiteStep\step.rc, in Rainmeter rainmeter.exe C:\path\to\layout.ini, this is undocumented on the forums)
- Layouts (originally called Themes in both apps)
- Comments being deliniate with ; (although in Rainmeter this might have been accidental as the .ini format denotes comments using ; too)
- @Includes (with the exact same name, minus the @)
- The Number datatype, everything in Rainmeter being IEEE 754 double-precision numbers
- Modules needing the loading of a single image file (in Rainmeter you need a single Meter loaded)
Code:
; This is an EXAMPLE step.rc file. This example will NOT work without; downloading the necessary modules (plugins) and placing them in the; same folder as litestep.exe.; First, we need to load the modules (plugins) that we want to use.; You may download these modules from:; http://www.shellfront.org/modules-list.php; Extract these modules into your LiteStep folder.LoadModule $LiteStepDir$hotkey.dll ; hotkey-2.0.zipLoadModule $LiteStepDir$popup2.dll ; popup2-2.1.5.zip; Configure a Hotkey combination to launch Notepad and open this; step.rc configuration file.*Hotkey WIN+CTRL S notepad.exe "$LiteStepDir$step.rc"; Configure a Hotkey to recycle (restart) LiteStep. This will reload; this step.rc configuration file with any changes, and reload all modules.*Hotkey WIN+CTRL R !recycle; Configure a Hotkey to open an explorer window and quit LiteStep.*Hotkey WIN+CTRL Q !execute [explorer.exe /e,/root,,$Drives$][!quit]; Configure a Hotkey to display LiteStep's "About" dialog.*Hotkey WIN+CTRL A !about; Configure a few default hotkeys that emulate Explorer's functionality*Hotkey WIN C explorer.exe /root,,$Controls$*Hotkey WIN E explorer.exe /e,/root,,$Drives$*Hotkey WIN L !logoff*Hotkey WIN M !MinimizeWindows*Hotkey WIN+SHIFT M !RestoreWindows*Hotkey WIN R !run; NOTE: pressing CTRL+ESC or the Windows Key will display the Popup Menu.; The Hotkey module automatically configures those hotkeys by default.; Next, we will configure a basic Popup Menu.HotlistName "LiteStep 0.24.8"PopupIconsPopupAdaptiveWidthPopupMinWidth 125PopupMaxWidth 300PopupNoBevel*Popup "My Computer" !PopupMyComputer*Popup !SeparatorIF Win9x*Popup "Start Menu" !PopupDynamicfolder:"$Startmenu$"ENDIFIF WinNT*Popup "Start Menu" !PopupDynamicfolder:"$Startmenu$|$CommonStartMenu$"ENDIF*Popup !Separator*Popup "Control Panel" !PopupControlPanel*Popup "Recent Documents" !PopupRecentDocuments*Popup !Separator*Popup .icon="$LiteStepDir$litestep.exe,0" "Running Tasks" !PopupTasks1999
Rainminder
The very first project published by Rainy was Rainminder, which was released on 31 July 1999.As described by the Rainminder manual:
So basically, a widget that contains a text box, with values changing based on programmed times. Here is an example widget from inside the Rainminder.cfg fileRainminder is a Litestep plugin which can be used to display messages at desired times. It's useful to remind you about important dates or perhaps just to inform that your favorite TV-show is beginning.
Rainminder uses a very simple script-language for defining the moment when a certain message will be shown. The message can have different fonts and colors and can even display the contents of an ASCII-file. The message window grows/shrinks according to the amount of displayed text.
Rainminder also has a build-in fortunecookie program to display random fortunes/quotes/jokes. Note that to use this feature you need a fortune-file which can be found around the Web (i.e. from a linux distribution).
Rainminder can be used as wharf or as plugin module. When used as wharf it functions as lstime-compatible clock so you can easily replace your old clock with this one.
Code:
## Rainminder Example Config#IF FirstRun() THENFont(Arial, 24, BOLD)Color(244, 255, 200)Align(CENTER)Date("%A")NewLine()NewLine()Align(LEFT)Text("Date: ")Date()NewLine()Text("Time: ")Time()NewLine()Text("Weather: Rainy ;-)")NewLine()ENDIFIF MouseClick() THENFont(Arial, 32, BOLD)Color(255, 255, 0)Text("Fortune")NewLine()Align(LEFT)Color(255, 255, 255)Font(Arial, 20, BOLDITALIC)Fortune("C:\Litestep\Rainminder\AllFortunes.txt")Newline()ENDIFIF Weekday()=3 AND Time()=22:30THENFont(Arial, 48, BOLD)Color(255,255,255)Text("X-Files")NewLine()Font(Arial, 24)Color(250,200,200)NewLine()Text("is starting soon!")Newline()Text("Better drag your butt in front of TV.")NewLine()ENDIFIF QuickAlarm() THENColor(255, 255, 255)Font(Arial, 16)NewLine()Text("R A I N M I N D E R")NewLine()Text("QUICKALARM")Font(Arial, 24, BOLD)NewLine()Text("was activated !")Font(Arial, 16)NewLine()ShowDuration(1000, 0)ENDIFIF AmpSongChanged() THENColor(255, 255, 255)Font(Arial, 24, BOLD)AmpText()ShowDuration(5)ENDIFRainmation
8 days later, 8 August 1999, Rainmation was created. As described by the Rainmation manual:This time everything was done inside the Litestep step.rc file with no external config files.Rainmation is a Litestep plugin for putting small animations on the desktop. This is mostly an eyecandy with ability to act as simple shortcuts.
You can have any number of animations and animations may be any size. But be careful with large animations as the animation frames are stored in memory in bitmap format, so big animations will take quite much memory.
There are three different methods to use transparency in the animations: fake, real and alpha.
The way fake transparency works is that before the animation is started a copy of the background is taken and used as the animation background. Only the desktop image is grapped, not the windows over it. However the system isn't perfect and sometimes also the overlaying windows get to be part of the beckground. Fake- transparency uses pink-color as transparent color.
Real transparency uses window regions and doesn't have the limitations that the fake transparency has, but takes a lot of CPU-time.
Alpha-transparency is similar to fake-transparency, but uses separate alpha-mask to determine the amount of transparency the bitmaps have. Alpha-masks are gray-color bitmaps where black means full transparency and white full opaque. Alpha-transparency is pre-calculated on the frames so it takes the same amount of CPU-time as the fake-transparent frames (after the precalc). You can use Alpha-transparency only in the frames that need it. This way you can reduce the pre-calculation time. Alpha-transparent frames need a second bitmap with -Alpha-postfix in it's filename which defines the alpha-values for the pixels. The Alpha-bitmaps must be same size as the frame-bitmaps.
Animation can be disabled or removed from the popup-menu you'll get if you press right mouse button over the animation. You can also refresh the animation from there and open the config-dialog.
To describe it using Rainmeter terminology, this is just a Bitmap meter with mouse actions. Back in the day, transparency effects for images and tooltip windows - like what Rainmation offers - were rare. Withn most programs, transparency was done using magic pink (tm) (which existed for a brief period of time in Rainmeter 0.1 too, where Strings with FontColor=FF00FF were invisible), thus you had only fully transparent or fully opaque bitmaps. Ranimation offered per-pixel transparency from 0 to 255. In the 2000s this was very impressive to see.
As for some concepts from Rainmation that have carried over, only the !EnableCommand and !DisableCommand bang terminology carried over (the measures were part of the bang instead of separate, in here, enabling and disabling the bitmap would have pasically stopped the "bound" measure).
2000
LsBox
Although not made by Rainy, a very important part of Rainmeter was most likely the existance of the LsBox Litestep LoadModule. As described by Lsbox.txt:Sound very similar to what Rainmeter is. With Lsbox you were able to dock the boxes to the Litestep components, or undock them and have them wherever you wanted them on your desktop, with the position being saved between closing and opening Litestep. Although the term "skin" has been used before to refer to themes, this module - and the quoted line from above - might have been the reason and inspiration for why Skins were eventually called... skins. I need your skin.lsbox is a litestep loadmodule that allows the creation of freefloating and skinnable "Boxes" that other modules can dock to. It has also build-in support for shortcuts and alphatransparency [...] You will need at least Win2k or WinXP to run it.
Some concepts borrowed from LsBox seem to be:
- LsBoxBackGround <Image> (Background and BackgroundMode=0)
- LsBoxBackgroundOffs <LeftOffs> <TopOffs> <RightOffs> <BottomOffs> (BackgroundMargins, with the order of the parameters being the exact same)
- LsBoxStartHidden (StartHidden in Rainmeter.ini)
- LsBoxRememberPosition
- !LsBoxShow <Name of the Box> (and the quivalent !Hide and !Toggle actions)
- Group bangs! (e.g. !LsBoxGroupShow <group> and equivalents)
- !LsBoxSavePosition <Name of the Box>
- Mouse Actions (although they were called LsBoxOnLeftClick instead of LeftMouseUpAction)
- Skins FX (the skin becoming transparent when you hover over with being able to set the transparency when inactive)
If we look inside the code, we can find the !LsBoxHook bang and the code executed when the bang is called.
Aaaaaaaaaand there's nothing, not even an easter egg, sad :(
Rainlendar
On 26 March 2000, Rainy released Rainlendar. Rainlendar is still developed and can be found here https://www.rainlendar.net/ .Quoting Rainlendar 0.1's Manual (which is accidentally called "Rainmation Manual" in the header <title>):
Here is an example skin from the Rainlendar.ini fileRainlendar is a very customizable calendar that resides on your desktop and shows the days of the current month. The application is a Litestep plugin, but it can be used without the Litestep as well. You can use it even with the normal Explorer-shell if you like.
The calendar can be customized to fit your taste (and theme). You can use different fonts and colors, select the background image or just use copy of the current wallpaper. All customization can be made with a GUI, so no hassle with cryptic configuration-files or registry entries.
The program is still a very early beta and is not meant for everybody. There isn't any nice install-script which doesn't bother you with complicated questions. You have to know a little about your system to get it work. But I guess if you are a Litestep-user you should know enough :-)
Code:
[Rainlendar]X=300Y=0StartFromMonday=0StartDelay=0BackgroundBitmapName=BG.bmpDaysEnable=1DaysRasterizer=FONTDaysFont=-17/0/0/0/700/0/0/0/0/3/2/1/34/ArialDaysFontColor=0DaysBitmapName=DaysX=30DaysY=50DaysW=170DaysH=150DaysAlign=2DaysNumOfComponents=10DaysIgnoreToday=0TodayEnable=1TodayBitmapName=Today.bmpTodayAlign=2TodayNumOfComponents=1TodayRasterizer=FONTTodayFont=-17/0/0/0/700/0/0/0/0/3/2/1/34/ArialTodayFontColor=FFFFFFWeekdaysEnable=1WeekdaysBitmapName=Weekdays.bmpWeekdaysAlign=2WeekdaysRasterizer=FONTWeekdaysFontColor=0WeekdaysFont=12/0/0/0/400/0/0/0/0/0/0/0/0/ArialMonthEnable=1MonthBitmapName=Months.bmpMonthX=6MonthY=50MonthAlign=0MonthRasterizer=BITMAPMonthFontColor=AFAFFFMonthFont=24/0/0/0/800/0/0/0/0/0/0/0/0/ArialYearEnable=1YearBitmapName=YearX=190YearY=3YearAlign=1YearRasterizer=FONTYearFontColor=FFFFFFYearFont=-20/0/0/0/700/0/0/0/0/3/2/1/34/Arial2001
Rainmeter
On 22 February 2001, Rainy released Rainmeter as a Litestep module. Since there's nothing else to add since the docs, this forum, the archival repos and Google can be searched, I'll just point out how weird the very first releases were.0.1
Here is the ReadMe.txt for Rainmeter 0.1 (minus contact info)Here's an example file of the very first packed-in skinRainmeter 0.1 for litestep
This is a simple CPU/MEM Meter plugin for Litestep. It is a LoadModule plugin and not a Wharf module as most of the others. This one works only in Windows 2000 (and maybe in NT4). Win9x is not supported.
The configuration is done in the Rainmeter.ini file. The settings should be quite clear, so I'm not going to explain them here. I might implement equivalent step.rc settings later (as well as better documentation).
If you want to get rid of one of the meters (e.g. the MEM), just set its color to pink (255,0,255).
There are also two bangs you can use:
!RainmeterShow
!RainmeterHide
The example configuration's graphics are from the excellent Kgnome3 theme by KanedA.
Code:
[Rainmeter]RainmeterPixmapPath=C:\Litestep\Rainmeter\RainmeterBackground=Background.bmpRainmeterWindowX=12RainmeterWindowY=-72RainmeterClockAlwaysOnTop=1RainmeterClockDraggable=1RainmeterWidth=174RainmeterHeight=50RainmeterLeft=13RainmeterRight=164RainmeterTop=6RainmeterBottom=42RainmeterCPUColor=138,144,152RainmeterMEMColor=202,144,152RainmeterBothColor=178,228,1660.2
Now we're starting to become more like we are today. Here is the introduction from the Rainmeter Manual for version 0.2Here is an example Rainmeter.ini fileRainmeter is a customizable resource meter that can display your CPU load and the amount of allocated memory. Rainmeter can also display how much data is sent and received through the network interface. The values are displayed with a histogram meter.
The application is a Litestep LoadModule plugin, but it can be used without the Litestep as well. You can use it even with the normal Explorer-shell if you like. Rainmeter is developed and tested on Win2k, but it should work on Win9x also. But Win9x is not officially supported.
And no, Rainmeter does not measure how much it rained last night (at least not yet ;-)
Code:
[Rainmeter]Background=Meter.bmpWindowX=-300WindowY=0AlwaysOnTop=1Draggable=1Update=1000HideOnMouseOver=0[CPUMeter]Type=HISTOGRAMX=7Y=7W=97H=25Measure=CPUPrimaryColor=38,144,52[MemMeter]Type=HISTOGRAMX=7Y=46W=97H=25Measure=PhysicalMemorySecondaryMeasure=SwapMemoryBothColor=78,228,66SecondaryColor=102,144,52PrimaryColor=38,144,52[NetMeter]Type=HISTOGRAMX=7Y=85W=97H=25Measure=NetOutSecondaryMeasure=NetInNetInSpeed=256000NetOutSpeed=256000BothColor=78,228,66SecondaryColor=102,144,52PrimaryColor=38,144,520.3, 0.4
Nothing much changed in terms of syntax, you can check the Version History for what changed here, however...0.5
The first plugins were created, the PowerPlugin, AdvancedCPU, SysInfo, PerfMon and MBM5 plugins were made... Wait what the hell is the MBM5 plugin?It seems like Rainmeter once had a plugin for Motherboard Monitor 5... it was not documented properly, it's not even on the latest docs. It's most likely not on the docs because the code for the plugin was completly removed from the Rainmeter source code, as compared to today where stuff like the iTunes plugin is just left there...
We're finally starting to reach what we have today, here's an example Rainmeter.ini file
Code:
[Rainmeter]Background=BigBG.bmpWindowX=-300WindowY=0AlwaysOnTop=1Draggable=1Update=1000HideOnMouseOver=0[MeasureNetIn]Measure=NetInNetInSpeed=256000[MeasureNetOut]Measure=NetOutNetOutSpeed=256000[MeasureCPU]Measure=CPU[MeasureMemory]Measure=Memory[MeasureSwap]Measure=SwapMemory[MeasurePhys]Measure=PhysicalMemory[MeasureDiskC]Measure=FreeDiskSpaceDrive=C:[MeasureDiskD]Measure=FreeDiskSpaceDrive=D:[MeasureDiskE]Measure=FreeDiskSpaceDrive=E:[MeasureDiskF]Measure=FreeDiskSpaceDrive=F:[MeasureDiskNet]Measure=FreeDiskSpaceDrive=\\Rainbox\public\[MeasurePerfMonCPU]Measure=PluginPlugin=PerfMon.dllPerfMonObject="Processor"PerfMonCounter="% Processor Time"PerfMonInstance=_TotalPerfMonMaxValue=10000000PerfMonDifference=1InvertMeasure=1[MeasurePerfMonDisk]Measure=PluginPlugin=PerfMon.dllPerfMonObject=PhysicalDiskPerfMonCounter="Disk Read Bytes/sec"PerfMonInstance=_Total[TextNetInMeter]Meter=STRINGMeasureName=MeasureNetInX=10Y=10W=100H=1FontColor=78,228,66StringStyle=NORMALAutoScale=1FontSize=6StringAlign=LEFTFontFace=Small FontsPostfix="Bps"Prefix="In: "[TextNetOutMeter]Meter=STRINGMeasureName=MeasureNetOutX=10Y=20W=1H=1FontColor=78,228,66StringStyle=NORMALAutoScale=1FontSize=6StringAlign=LEFTFontFace=Small FontsPostfix="Bps"Prefix="Out: "[TextCpuMeter]Meter=STRINGMeasureName=MeasureCPUX=10Y=30W=1H=1FontColor=78,228,66StringStyle=NORMALAutoScale=0FontSize=6StringAlign=LEFTFontFace=Small FontsPostfix="%"Prefix="CPU: "[TextMemMeter]Meter=STRINGMeasureName=MeasureMemoryX=10Y=40W=1H=1FontColor=78,228,66StringStyle=NORMALAutoScale=1FontSize=6StringAlign=LEFTFontFace=Small FontsPostfix="B"Prefix="MEM: "[TextSwapMemMeter]Meter=STRINGMeasureName=MeasureSwapX=10Y=50W=1H=1FontColor=78,228,66StringStyle=NORMALAutoScale=1FontSize=6StringAlign=LEFTFontFace=Small FontsPostfix="B"Prefix="Swap: "[TextPhysMemMeter]Meter=STRINGMeasureName=MeasurePhysX=10Y=60W=1H=1FontColor=78,228,66StringStyle=NORMALAutoScale=1FontSize=6StringAlign=LEFTFontFace=Small FontsPostfix="B"Prefix="Phys: "[TextDiskNetMeter]Meter=STRINGMeasureName=MeasureDiskNetX=10Y=70W=1H=1FontColor=78,228,66StringStyle=NORMALAutoScale=1FontSize=6StringAlign=LEFTFontFace=Small FontsPostfix="B"Prefix="Rainbox: "[TextDiskCMeter]Meter=STRINGMeasureName=MeasureDiskCX=10Y=80W=1H=1FontColor=78,228,66StringStyle=NORMALAutoScale=1FontSize=6StringAlign=LEFTFontFace=Small FontsPostfix="B"Prefix="C: "[TextDiskDMeter]Meter=STRINGMeasureName=MeasureDiskDX=10Y=90W=1H=1FontColor=78,228,66StringStyle=NORMALAutoScale=1FontSize=6StringAlign=LEFTFontFace=Small FontsPostfix="B"Prefix="D: "[TextDiskEMeter]Meter=STRINGMeasureName=MeasureDiskEX=10Y=100W=1H=1FontColor=78,228,66StringStyle=NORMALAutoScale=1FontSize=6StringAlign=LEFTFontFace=Small FontsPostfix=" GB"Prefix="E: "[TextDiskFMeter]Meter=STRINGMeasureName=MeasureDiskFX=10Y=110W=1H=1FontColor=78,228,66StringStyle=NORMALAutoScale=1FontSize=6StringAlign=LEFTFontFace=Small FontsPostfix=" GB"Prefix="F: "[PerfMon]Meter=STRINGMeasureName=MeasurePerfMonCPUX=10Y=120W=1H=1FontColor=78,228,66StringStyle=NORMALAutoScale=0FontSize=6StringAlign=LEFTFontFace=Small FontsPostfix=" %"Prefix="CPU: "Scale=100000.0[PerfMon2]Meter=STRINGMeasureName=MeasurePerfMonDiskX=10Y=130W=1H=1FontColor=78,228,66StringStyle=NORMALAutoScale=1FontSize=6StringAlign=LEFTFontFace=Small FontsPostfix="Bps"Prefix="Disk: "0.8
Rainmeter is no longer dependant on Litestep, it can be loaded as a module in it one, but you can run Rainmeter without it.From here on out, everything else is history. Rainmeter was abandoned between 2006-2009 and was picked up by the community (with members from back then still being active today), which brought it up to what it is today. Thanks for everyone who helped with the project, from start to finish.
I also hope it was an interesting read. Have a nice day!
Sources for Litestep info and Rainmeter archived files
https://github.com/lsdev/litestep-/blob/master/docs/manual.txt
https://shellfront.org/
Statistics: Posted by Jeff — Yesterday, 9:59 am — Replies 0 — Views 56