If any one is interested in adding the BBSLink scores as a drop down menu in webv4
I have created the files for each game score that can be viewed from a drop down menu.
you can get the file here->
http://halopc.ddns.net/files/bbslink.zip
just create a folder called bbslink in your \sbbs\webv4\pages\ and drop all the .txt files in the bbslink folder
\sbbs\webv4\pages\bbslink <-should look like that.
thats it you'll now have a drop down menu in webv4 that will show you all bbslink score's individually in a nice centered format.
you can checkout this drop down menu on my website
outwestbbs.com
What if some are still using the stock /sbbs/web themes or webv3, or have made a custom web theme? Are these BBSLink Scores only compatible with webv4?
What if some are still using the stock /sbbs/web themes or webv3, or have
I must say, you're web interface is very concise ... I am very impressed ... I must also say that the way SBBS has progressed in it's use of JS is considerably more advanced that anything else appearing ... anywhere ...
I, personally wish there was a mention of you on the wiki, though. I do
I may be wrong to say that Synchronet is fairly unique in this way, but it's rare in this space to see a project with such extensive scripting hooks that are also so well documented. Part of that is down to the devs' foresight in using documentation-generating code & comments.
Re: Re: BBSLink Scores - Drop down menu
By: Mortifis to Denn on Wed Mar 06 2019 12:56:42
What if some are still using the stock /sbbs/web themes or webv3, or have
The answer to "What if I'm still using ecweb v3" is always "switch to webv4". I will not ever assist anyone in troubleshooting v3 or commit any fixes to it. It's dead.
If you're using the Runemaster UI or your own concoction, here's the info I can give you:
A "Page" in webv4 is just an HTML snippet. It shouldn't have <html>, <head>, or <body> tags in it. It's meant to be included within another HTML document. So just read the file from disk and include it inline in a page from your own UI.
The first *comment* line of a Page is its title and control line. Details on the wiki at my github repo:
https://github.com/echicken/synchronet-web-v4/wiki/Customization#pages
important, but I often feel like code comments aren't the right
place for customer/user-facing documentation (for coders who will
use the library). I usually feel that code comments are for
developers, so it seems weird to me to generate API documentation
from code comments. There are some places
It's a pretty common practice; JSDoc and ESDoc are widely used. It's no weirder than writing markup/markdown, really, even if you're not accustomed to including comments that must follow a certain structure. It's something you do in addition to whatever other comments you might normally add to a file.
At some point I'd like to start adding this self-documentation to various JS libraries included with Synchronet, and see about maybe publishing them somewhere (the wiki perhaps). I imagine there are folks out there who might use some of this stuff if it were easier to figure out how, or if they knew it existed.
important, but I often feel like code comments aren't the right place for customer/user-facing documentation (for coders who will use the library). I usually feel that code comments are for developers, so it seems weird to me to generate API documentation from code comments. There are some places
me to generate API documentation from code comments. There are some places where I think it's convenient though, such as taking comments from function declarations (which developers need anyway) and creating a document from that.
The first *comment* line of a Page is its title and control line. Details on the wiki at my github repo:
https://github.com/echicken/synchronet-web-v4/wiki/Customization#pages
Re: Re: BBSLink Scores - Drop down menu
By: Mortifis to echicken on Thu Mar 07 2019 15:49:36
I haven't added myself to any wiki pages because it feels a bit masturbatory to do so. I'm not sure what there would be to say about me that's of any real interest to anyone. :)
I haven't added myself to any wiki pages because it feels a bit masturbatory to do so.
I like Mystic, but I found that MPL was either underdocumented or overly constrained. I think its Python integration is promising, but it either
constrained. I think its Python integration is promising, but it either doesn't hook into the BBS very much, or where it does, it isn't
documented - or I haven't looked hard enough.
If you're comparing MPL to C++ then sure its constrained. But more realistically it compares to BAJA and in that sense its not constrained.
(MPL is to BAJA, as Python is to JavaScript).
Documentation for MPL and Python is hot garbage! Feel free to help me! ;)
You can access msg groups, msg bases, msg reading, file groups, file bases, themes, users, etc with Python functions. And Python has a strong community and usable package manager that works with Mystic Python.
I think Python's a fine choice. Mainly I'm not sure I'd be able to make the most of its integration with Mystic based on, say, this:
http://wiki.mysticbbs.com/doku.php?id=python_functions
Re: Re: BBSLink Scores - Drop down menu
By: echicken to Mortifis on Thu Mar 07 2019 03:37 pm
I haven't added myself to any wiki pages because it feels a bit masturbatory to do so.
Which is the best reason to do so! :-)
digital manI'm just sayin :-) I mean, I have good reason to not go and add anything since I haven't contributed anything but a reason for developers to occasionally require prozac or a few stiff drinks :)
Re: Re: BBSLink Scores - Drop down menu
By: James Coyle to echicken on Sat Mar 09 2019 09:52:14
There are only like 70 functions on that page but they are all specific to BBS access. You have full access to users, syscfg, groups, file lists/areas, msg reading/areas, menus, doors, themes, prompts, access evaluation, etc.
What I see is a list of function names, no details about parameters they take or values they return. Maybe I'm just missing something or have the wrong idea. Those are the sorts of details I expect in an API doc. Maybe they aren't needed here for whatever reason, and maybe if I actually tried to do something it would become clear. Maybe I'm reading the wrong page.
That list does not include the stuff brought in from Python itself which covers strings, datetime, file I/O, sockets, servers, ZIP compression,
I wouldn't expect it to document anything outside of what Mystic brings to the environment. That is very far from what I was trying to suggest and would be way out of scope.
I know I said I wasn't going to reply here again, but you're kind of doubling down on this without really telling me anything. :P For the
I made an offhand comment and inadvertently started this. I can't be super specific because I haven't made an honest effort at doing anything with MPL in many years, and I've really only glanced at Python+Mystic a few times. I'm not coming into this with certainty or a very strong opinion, or even thinking that I'm right. :D
I know I said I wasn't going to reply here again, but you're kind of
Not intending to drag this on, I just tend to reply if I have something to say, whether the other guy wants to keep it up. (I also *try* not to reply if I have nothing new to add, but often fail.)
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 28 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 189:38:59 |
| Calls: | 2,004 |
| Calls today: | 1 |
| Files: | 11,114 |
| Messages: | 942,271 |