xoops forums

bushir

Just popping in
Posted on: 2009/7/17 14:02
bushir
bushir (Show more)
Just popping in
Posts: 3
Since: 2008/9/26
#51

Re: XOOPS 2.3.x Translations

Quote:
That's ok, but I'm only user :)

Only? Come on, all of us can make a difference. And you did with your translations before!!! And is good to see you back!!!

DCrussader

Friend of XOOPS
Posted on: 2009/7/17 21:12
DCrussader
DCrussader (Show more)
Friend of XOOPS
Posts: 573
Since: 2005/7/4 7
#52

Re: XOOPS 2.3.x Translations

Thanks :)

So will proceed like in I.m.p.r.e.s.s.CMS forums.
Mamba as language manager, u have to add the following bugs to the tracker with highest priority to the upcoming 2.3.4 of XOOPS.

Cleaning XOOPS Language files of all scrap
and
asking all module developers including Catzwolf to clean all they're works from scrap.

There are tons of doubles in modinfo.php and admin.php.
(in my favorite CMS still, things with the language files are covered in two files max, more clean then define '(something)';
Also even huge applications like Fireboard forum have smaller language files, bcz they track and the changes, not only to add futures to they're modules, but also to maintain and clean the base, which is not a rule here yet.

WF-Downloads 3.2 language files are 60k, while they can be only 30k
X-Torrent and other X-s probably are still full with automated translations
CBB 3.x/4.x .... excuse me, but unClassified Bulletin Board 2.0 have smaller language files.
Some modules are lack of English, D-Transport from EXM, known as RM-Downloads Plus.
Happy Linux Web Links 1.9x.... damn this is bigger then XOOPS itself, compared to imLinks is nothing, except the size.

and feature request, can u port imLinks to XOOPS ?

so far that is.... it's not only, but this was the latest used modules by me on some XOOPS sites.

(I think moderators should split last few posts in another topic)

DJ do not do Skalpa mistakes, censoring Marcan's CMS here is a bad idea !
May The Source Be With You!

trabis

Core Developer
Posted on: 2009/7/18 7:35
trabis
trabis (Show more)
Core Developer
Posts: 2268
Since: 2006/9/1 1
#53

Re: XOOPS 2.3.x Translations

Quote:

DJ do not do Skalpa mistakes, censoring Marcan's CMS here is a bad idea !


-Agree with you.
-I know you from other site.
-I'm also here quite alone(No portuguese around).
- we need more block positions or better designers?

DCrussader

Friend of XOOPS
Posted on: 2009/7/18 10:42
DCrussader
DCrussader (Show more)
Friend of XOOPS
Posts: 573
Since: 2005/7/4 7
#54

Re: XOOPS 2.3.x Translations

Quote:

- we need more block positions or better designers?


Shhh, designers will curse u :)
Better theme engine and yeah, tons of blocks everywhere, like the screenshot I posted above...
May The Source Be With You!

trabis

Core Developer
Posted on: 2009/7/18 12:24
trabis
trabis (Show more)
Core Developer
Posts: 2268
Since: 2006/9/1 1
#55

Re: XOOPS 2.3.x Translations

Quote:

DCrussader wrote:

Better theme engine and yeah, tons of blocks everywhere, like the screenshot I posted above...


Blocks everywhere is not the same as block positions. I don't think we need more than 8 blocks positions, we need ability to place blocks anywhere!

And no, I do not mean smarty plugins to make it possible. Smarty plugins don't go well for blocks that require javascript or css. We need this on core, but not has extra block positions. Solution is quite simple and I implemented in one of my recent modules 'mymenus'. I won't show you code but this is how it works:
- You give ability for blocks to have a unique id (being the 'bid' of the block or any other custom ID you provide like 'myblock_navbar'
- Then you add a selection box to give that block 2 different render methods. This methods are 'assign to block position' and 'assign to template'
- the block function will then look at the choosen method and render the normal way for first choice, for second choice it will assign the block result to a smarty var and deliver block as empty to core(so block is not displayed in his position)
- assign block to template will allow you to place the block anywhere in the theme just by calling the corresponding smarty var, in the case above the var could be <{$myblock_navbar}>

Doing this in core we can add this ability to any exisiting block (adding field for custom id and select box). Theme designers can create places for blocks where they want, the site admin just have to edit a block and give same id used in theme and assign it to render to template.

Practical example:
In 'mymenus' module I want designers to make a place in theme for dropdown menus(top navigation). So designers just have to add <{$xoopsblock_navbar}> in the place they want menu to show.
All I have to do is to edit my mymenus block and give it the id of 'navbar'. Here xoopsblock_ prefix is automatically added to avoid namespace conflict.

You see, we often need to add a search block, a login block, a menu block or any other special/custom block. We do not really need positions where we can drop more than one block.
This 'hack' provides more flexibility cause it allows to use blocks inside any module template/theme and is easy to implement on theme(without using ifs and elses like we would need for extra block positions). This will not affect core performance and will allow code to maintain clean without extra worries that extra block positions give.

---------

Regarding designers:
I read somewhere that XOOPS and all forks together have around 10 designers. I think we have 2 or 3. It depend on the 'designer' meaning. For me a designer is lot more than having lot of brushes in photoshop and know some good css tricks. Creativity is not found on books, it cannot be taught. I am able to make themes but I'll never be a designer no matter how bad I try and how high I scream I am.

PS: 2 or 3 has a lot of space for you to fit in so don't take it personally!

PS: Same can be said for writing, painting, music, XOOPS development or any other kind of art.


DonCurioso

Quite a regular
Posted on: 2009/7/18 14:30
DonCurioso
DonCurioso (Show more)
Quite a regular
Posts: 239
Since: 2009/3/1 1
#56

Re: XOOPS 2.3.x Translations

trabis,

completely agree with you about designers
HispaXoops | Xoops EspaƱa

That's the way i like it! | Nada mejor que una Alhambra bien helada con aceitunas...

DCrussader

Friend of XOOPS
Posted on: 2009/7/18 19:05
DCrussader
DCrussader (Show more)
Friend of XOOPS
Posts: 573
Since: 2005/7/4 7
#57

Re: XOOPS 2.3.x Translations

me too, one is the author of this theme, 2nd is the one of Zetagenesis ...
May The Source Be With You!

zulyunus

Just popping in
Posted on: 2009/8/29 3:44
zulyunus
zulyunus (Show more)
Just popping in
Posts: 10
Since: 2009/7/29
#58

Re: XOOPS 2.3.x Translations

How to enable arabic character in our site?

sailjapan

Moderator
Posted on: 2009/8/29 5:41
sailjapan
sailjapan (Show more)
Moderator
Posts: 1672
Since: 2005/11/16
#59

Re: XOOPS 2.3.x Translations

Quote:
How to enable arabic character in our site?


Best to ask at the arabxoops site, perhaps?

DCrussader

Friend of XOOPS
Posted on: 2011/3/30 6:08
DCrussader
DCrussader (Show more)
Friend of XOOPS
Posts: 573
Since: 2005/7/4 7
#60

Re: XOOPS 2.3.x Translations

Censoring Posts again ?
DJ are u sure u're not Skalpa ?

Deleted - https://xoops.org/modules/newbb/viewto ... &forum=64#forumpost337586

Or I'm just forwarded by a moderator to old thread to read my own positive critics ? :)
May The Source Be With You!