XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. Xoops Development / 
  3. Roadmap 
  4.  / XOOPS 2.1 Core development Roadmap
Register
71
Draven
Re: XOOPS 2.1 Core development Roadmap

  • 2003/11/4 2:28

  • Draven

  • Module Developer

  • Posts: 337

  • Since: 2003/5/28


Quote:

Catzwolf wrote:
We are trying to take everything onboard (even if this is a core thread) about additions you would all like to see within the modules, but we will try to add these over a period of time and not in one go (the other guys would kill me if I said we would! LOL).






72
chapi
Re: XOOPS 2.1 Core development Roadmap

  • 2003/11/4 7:58

  • chapi

  • Theme Designer

  • Posts: 611

  • Since: 2002/1/22


My hack to get a variable for the current module looks as following:

I added this snippet to the header.php

Quote:

if ( is_object($xoopsModule) ) {
$xoopsTpl->assign('xoops_moduledir', $xoopsModule->getVar('dirname')); }
else {
// whatever your want
}


In my theme.html I used

Quote:

<{$xoops_moduledir}>


to display the directory name of the current module. This snippet is a little shorter than yours draven
73
Haruki
Re: preliminary summary of roadmap discussion

  • 2003/11/5 4:21

  • Haruki

  • Just popping in

  • Posts: 4

  • Since: 2002/1/19


for MULTILINGUAL CONTENT, UTF-8 seems to be better as internal character encoding of XOOPS.
But a shortcoming is that encoding convertion will be necessary when upgrading.

And I want to know that all the user of each region can use UTF-8 propery.

In japan? Almost OK, but iso-2022 is commonly used in e-mail.
74
ajaxbr
Re: XOOPS 2.1 Core development Roadmap

  • 2003/11/5 4:47

  • ajaxbr

  • Quite a regular

  • Posts: 276

  • Since: 2003/10/25


Perhaps XOOPS should get a default php file included in header.php to allow easy upgrades of header.php while keeping hacks, counters, anything that usually goes in header.php and makes it CVS unfriendly.

Take a look here for further discussion.
75
PureLuXus
Re: XOOPS 2.1 Core development Roadmap

  • 2003/11/5 6:04

  • PureLuXus

  • Not too shy to talk

  • Posts: 116

  • Since: 2002/1/3 2


Quote:

chapi wrote:
My hack to get a variable for the current module looks as following:

I added this snippet to the header.php

Quote:

if ( is_object($xoopsModule) ) {
$xoopsTpl->assign('xoops_moduledir', $xoopsModule->getVar('dirname')); }
else {
// whatever your want
}


In my theme.html I used

Quote:

<{$xoops_moduledir}>


to display the directory name of the current module. This snippet is a little shorter than yours draven


u allready can get the module name without hacking..
try <{$xoops_pagetitle}>
76
chapi
Re: XOOPS 2.1 Core development Roadmap

  • 2003/11/5 7:57

  • chapi

  • Theme Designer

  • Posts: 611

  • Since: 2002/1/22


But what if I assign a Pagetitle which differs from the modulename to my templates? The dirname is more safe in this situation
77
PureLuXus
Re: XOOPS 2.1 Core development Roadmap

  • 2003/11/5 8:00

  • PureLuXus

  • Not too shy to talk

  • Posts: 116

  • Since: 2002/1/3 2


ok thats right ;D
Quote:

chapi wrote:
But what if I assign a Pagetitle which differs from the modulename to my templates? The dirname is more safe in this situation
78
wammes
Re: XOOPS 2.1 Core development Roadmap

  • 2003/11/5 14:35

  • wammes

  • Not too shy to talk

  • Posts: 101

  • Since: 2002/1/3 1


I dunno I it's metioned before, (it's a real long thread to read.. )

I'd like to see more options to view the blocks:

When you have a lot of usergroups (I have ), it is really difficult to create a new block which not al usergroups can see. You first have to create the block, and then go to groups and change the accesrights for every group seperately. I don't like that because it costs me much time.
I'd like to see in the new core version the ability when I create a new block to immediately be able to set the accesrights by checkboxes. It would be so much easier to create a (temporary) block for a message to my users.

And another option:
More options the views on the blocks. Now we can choose between "all pages" or just "news" or just "forum". But what if I want a block to be viewed on "news" and "forum"? Then I have to create two blocks. It is possible, but not nice. Don't you agree?

I hope you consider my ideas when adding extra features to the core. Esspecially the blocks/groups thing. It would be really useful (at least for me )
79
chapi
Re: XOOPS 2.1 Core development Roadmap

  • 2003/11/5 14:58

  • chapi

  • Theme Designer

  • Posts: 611

  • Since: 2002/1/22


You can already display a block in "news" and "forum" at the same time. You only have to use your STRG Button on your keyboard when clicking on the modules available in the list
80
Herko
Re: XOOPS 2.1 Core development Roadmap

  • 2003/11/5 15:03

  • Herko

  • XOOPS is my life!

  • Posts: 4238

  • Since: 2002/2/4 1


Quote:

chapi wrote:
You can already display a block in "news" and "forum" at the same time. You only have to use your STRG Button on your keyboard when clicking on the modules available in the list

That's CTRL for us windows users with US keyboards

Herko
« 1 ... 5 6 7 (8) 9 10 »

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

210 user(s) are online (150 user(s) are browsing Support Forums)

Members: 0

Guests: 210

more...

Donat-O-Meter

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

Latest GitHub Commits