i have one problem
.conkyrc files have to be placed into /home folder
where are other files supposed to go?
lua, fonts and other scripts etc??
Printable View
i have one problem
.conkyrc files have to be placed into /home folder
where are other files supposed to go?
lua, fonts and other scripts etc??
Place fonts in ~/.fonts
Create the ~/.fonts folder if you don't have one.
~ is short for /home/username
Eg ...for me "~" equals /home/glen
Lua scripts etc can be placed anywhere.
Just make sure to check the paths in the conky config.
Eg I keep everything in ~/conky with sub folders for
configs, Lua and scripts.
Then just alter any downloaded config to reflect these locations.
Saving configs with a descriptive name and then loading with conky -c /path/to/config also aids
in keeping things organized.
Eg I have a Gmail conky @ ~/conky/configs/Gmail.conkyrc
and to load use...
Code:conky -c ~/conky/configs/Gmail.conkyrc
And as for me, I install fonts system wide by double clicking it, which opens font viewer, where is "install" option.
As for conkyrc, I put everything Conky in ~/.conky directory, LUA scripts for conky in ~/.conky/lua , other scripts in ~/.conky/conkyparts and so on, as I need.
I load Conky by
for example, if I test something,[advertisement] but overall, I load Conky by One4All project, byCode:conky -c ~/.conky/conkyrc-test45
script, which loads One4All Conky project with desired configuration.[/advertisement]Code:~/.conky/one4all/one4all-start.sh
Wait, what's that I see in your sig::lolflag:Quote:
I'm a super power user.
Yea, we must be in the same boat. I have to admit I've tried and two things happen, in no particular order:
1. ](*,)
2. :cry:
Been a long time ago though as I've had some pretty pressing life stuff going on lately.
I'll have to try again, I have everything here.
Ok.
Well start form basics.
Make sure, that one4all/flibs/active have 2 files inside (it should by default, but lets check):
Now, check, that one4all/modules/active is empty.Code:one4all_cairo.flib
one4all_main.flib
If it is empty, then copy londonali1010_airclock.module from one4all/modules/available to one4all/modules/active.
Now, run one4all/one4all-start.sh
Ok ... here we go...
First I extracted 'One4all-0.2.7.tar.gz' over an older one at /home/sector11/one4all
... and started:
Done!Code:/home/sector11/one4all/flibs/active/one4all_main.flib
/home/sector11/one4all/flibs/active/one4all_cairo.flib
EMPTY!Code:/home/sector11/one4all/modules/active
Copied a different one - no idea why :lolflag:
Done!Code:/home/sector11/one4all/modules/active/s11_cronograph_dk75mod.module
running one4all/one4all-start.sh ... and:
http://t.imgbox.com/adscwaDG.jpg
That's pretty slick dk75! Thanks!
So what are these for:
Also is there and easy way to make a LUA script into an all4one module or does one have to be a LUA programmer to do that?Code:/home/sector11/one4all/active
/home/sector11/one4all/active/airclock.module
/home/sector11/one4all/available
/home/sector11/one4all/available/test2.module
/home/sector11/one4all/available/test1.module
/home/sector11/one4all/available/date_box.module
/home/sector11/one4all/available/analog_clock.module
/home/sector11/one4all/available/[wolfur]_bargraph_small.module
/home/sector11/one4all/available/[londonali1010]_rings.module
/home/sector11/one4all/available/[londonali1010]_photo_album.module-edit_in_progress
/home/sector11/one4all/available/[londonali1010]_clock_hands.module
/home/sector11/one4all/available/[londonali1010]_cairo_pie.module
/home/sector11/one4all/available/[londonali1010]_airclock.module
/home/sector11/one4all/data
Can they be reversed - back to a straight LUA?
These are old modules, from alpha stage, probably buggy, though might work with no problem.
But better delete it and download new one.
Yeah, why not...
Look at the test modules, they are reeeeeeaaaaaaly simply, mostly prints to terminal only.
After you play with them, then look at londonali1010 airclock and at dk75 background module - these are simpler one to understand (AFAIK).
PS: one more thing: in module names only alphanumerics are allowed with addition of underscore and dot, and filename should begin with letter - otherwise it will not be loaded
That's my experience from pushing it from alpha to beta stage
Well, I did say:
:DQuote:
First I extracted 'One4all-0.2.7.tar.gz' over an older one at /home/sector11/one4all
I'll add an -old-DO_NOT_USE to the directory name just so I have 'even more samples'
reeeeeeeeeeeeeeeeeeaaaaaaaaaaaaaaaly simple: How many apples is:
((3x9)-7)/2 to a 6 year old. :D
But if you know what you're doing! :guitar:
OH!!! That's something for the 'README', it's the first 3 of the 3 threes that are there. I do the same thing at times. :lolflag:
OK. Lets walk through test01.module:
it's comment, you know? :guitar:Code:-- test01.module
this part is for module definition - without it, it won't be loaded as module, but it will be simple included to main LUA script.Code:local modname = ...
local M = {}
_G[modname] = M
package.loaded[modname] = M
It's that same in every module, just copy&paste.
Some functions printing meaningless text to terminalCode:function M.test1()
print()
print("Welcome") end
function M.test2()
print("Name loaded module:", modname) end
more comments :guitar:Code:--[[
###############################################################################
### MODULE MAIN LOOP ###
###############################################################################
--]]
MAIN function of every module - it's run by main LUA script after module is loaded so it need to be a "function M.main() ... end" in every modules.Code:function M.main()
M.test1()
M.test2()
end
And why every function is preceded by "M." you could ask?
Ah, it's special properties of modules - "M" variable stores module name ("M" as this variable was defined at the beginning in module definition) and indexes every function inside of that module which was connected to it.
Every function inside of module is local and private but with this, it's name is available globally and function might be called from outside of module, but then it needs to be called by it's full name. Like "M.test1()" function from "test01.module" could be called inside other module by it's full name "test01.test1()".
That's how functions from "flibs" are called, so developer can use some predefined functions from "flibs" without need for inventing wheel again.
For example, if one need to know (x,y) position of point at 37 degree angle, at 78px radius circle with it's center at (230,117), then one invoke function from one4all_main.flib by:
(there is "M.pointATcircle()" function in one4all_main.flib)Code:local pointX, pointY = one4all_main.pointATcircle(230, 117, 37, 78)
No need to make calculations themselves. Simple and clean.
Of course, one4all_main.flib must be in active directory, but at least that functions library is mandatory to be in active - without it, whole project won't work.