293641
Vchat20
Streaming Audio Mod
  • 2002/12/27 5:30

  • Vchat20

  • Just popping in

  • Posts: 2

  • Since: 2002/12/27


Are there any Streaming Audio mod's for Xoops? I know there is one for PHPNuke, but is there one for xoops? If not, It would be nice if one is made. Cuz I am starting a Streaming Radio station called The Sims Online HQ Radio, and the site, The Sims Online HQ, is gonna be made using XOOPS. And the station needs to be played right o the site.



293642
script_fu
Is this possible?

Is it possible to have other domains on the same server share the same database. Would this cause a big problem?

If so how about a seperate database for web links. They take
so much time to do so being able to share them would be a great way to save time...




293643
sunsnapper
Re: Xoops2 Sniffer

onokazu,
Thanks for taking the time to look at that. I think you are right, PHP would be the better choice (for those pesky people who turn off JS... like me ).
Thanks for the link.

I'm sure that some time between Xoops2 and XoopsFinal, I will take the time to re-write this for the Feature Request forum. I know you all have bigger fish to fry at the present time.
Thanks again.



293644
onokazu
Re: Xoops2 Sniffer
  • 2002/12/25 23:41

  • onokazu

  • XOOPS Founder

  • Posts: 617

  • Since: 2001/12/13


No, there still will be no standardized browser sniffing codes in XOOPS2, but only in some parts we try to detect if the client is using IE or not before adding some IE specific http header variables.

I see that those links you've suggested are all javascript codes, so include/xoopsjs.php might be the right file to include the codes, if you need to do a site-wide sniffing.

You can also consider using native PHP functions like get_browser() or simply looking at the values of $HTTP_USER_CLIENT the client sends to the server.

By the way, I have come into the following script when I was searching for a good php sniffer script some time ago, and it looked very good.
phpClientSniffer



293645
sunsnapper
Xoops2 Sniffer

I was reading a story on A List Apart about sniffing browsers to determine what level of PNG support they have. It got me wondering...
1. Will Xoops2 implement a browser sniffer?
2. If so, which file is it in, if someone wants to tweak it?
3. If not, which file would it be best to add it to... perhaps a skin file?

If there are not plans to have a sniffer built-in, it just seemed to me like a nice check-box feature that one could enable if they needed to. If it exposed a standard set of variables in Xoops, then module developers could look to that standard set when features don't work the same in all browsers (such as WYSIWYG editing).

In my case, I am mostly interested in it to be able to know which browsers I can offer transparent PNG, non-transparent PNG, or ancient GIF to.

Anyways, if you have suggestions for which file is best suited for having the sniffer code copied into it, that would be great. Otherwise, I hope the links are interesting and useful.

Browser Detect Lite

Ultimate Client Sniffer

A List Apart: Cross-Browser PNG Transparency



293646
samo
Re: HTML problem in XOOPS and Other CMS?
  • 2002/12/24 9:02

  • samo

  • Just popping in

  • Posts: 16

  • Since: 2002/10/14


Try removing the HEIGHT=xxx in he TABLE tag, making the table only as high as needed... It will save a lot!



293647
npetreley
Re: Theme writing revisited
  • 2002/12/19 17:53

  • npetreley

  • Just popping in

  • Posts: 15

  • Since: 2002/12/9


I'd love to have a look at Xoops2. Is it available in anonymous CVS or anything? I apologize that I haven't looked for it yet, so if it's obvious where to get the code, just say so and I'll find it.



293648
onokazu
Re: Theme writing revisited
  • 2002/12/19 17:33

  • onokazu

  • XOOPS Founder

  • Posts: 617

  • Since: 2001/12/13


Yes, I like your idea about passing an object as the parameter of theme functions. However, in XOOPS2, there will be no theme functions at all, but all the values for presentation are assigned to template variables via the Smarty global object like $smarty->assign('name', $value);.

Yes, the old themes will still work fine in XOOPS2, but since the Smarty template system will be the primary theme system we will be using, it is unlikely that we will be doing any modifications on the current theme system.



293649
npetreley
Theme writing revisited
  • 2002/12/19 15:42

  • npetreley

  • Just popping in

  • Posts: 15

  • Since: 2002/12/9


Here's another thing that occurred to me re: passing the objects to themes. Perhaps there's already such a document (I apologize if I missed it somewhere), but it might be nice to have theme guidelines that require you to test for the existence of a property before using it.

Here's an example problem: Theme 1 uses $story->title, $story->morelink, etc., which are all standard. Theme 2 uses the field I added to the table as $story->storyurl. At this point, only those people who had my modified code could use my theme. If they used my theme with their unhacked Xoops, my theme would barf when it tries to access $story->storyurl and couldn't find it.

But if I wrote the theme with that in mind (and according to the suggested guidelines), the code would test for the existence of $story->storyurl before trying to use it. That would (or should) make my theme compatible with unhacked versions of Xoops.

Obviously, my example is about hacked versions, but this same principle would apply to prior and future official versions.



293650
Boobtoob
Re: Several requests!
  • 2002/12/17 21:30

  • Boobtoob

  • Friend of XOOPS

  • Posts: 202

  • Since: 2001/12/22


Thanks, I've stick'd this for future reference.







Login

Who's Online

378 user(s) are online (300 user(s) are browsing Support Forums)


Members: 0


Guests: 378


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Jul 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits