seafarer:

I'm sorry to hear you've had problems, but since this is the first post I see signed by you, I can hardly be of any help. Please, either keep a thread or be more explicit in your messages so people can lend you a hand.

And one more thing. The community here is more than willing to help, but that's a voluntary thing. It's not just a let me send you my logo so you make me a theme thing.

Sorry if this sounds rude. If this bothers you, I apologize, but please understand you need to be more explicit and willing to do your homework in this community.

Cheers.

Nemo1:

The reason you see this alignment appears to be that when there's no specification, an unordered list adopts a style position "inside". It's not an error; it's just the way it is designed to appear. If you want to "correct" this and to align the texts flush left, you need to set a style using the selector list-style-position: outside.

Of course, you also need to play a bit with margins and paddings, but that's another story.

To see a "correct" representation of these kind of things, take a look at the "Titulares" here (right column).

So what you see as an error is just economy of styling in the default theme. Another them, in this case x2t, uses this declaration:



This would appear also with the "wrong" alignment. The selector list-style just needs to be declared as "decimal outside".¨

For more info, please take a look here.

Cheers.

sunsnapper:

Nice of you to say I have the lead. Actually, if you take a look at the thread, it was you who started it all, so we could say you have the lead. Then again, the lead should belong to whoever makes a contribution, and in this sense mikhail has the lead.

It's really good to see the interest in this matter. As I've said many times in the core team's conversations, I see myself more as a catalyst than as a leader, so here are some more thoughts regarding what's been said here.

It's a good idea to build a MyModules module. Even though Herko has a point about the difficulty of having separate repositories, XOOPS users need the choice. What would such a module have? Let's see:

a. An ordered list (MyDownloads). The admin should be able to select a default order. The list could have two versions (Spotlight): single line with linked title and double line (the first one, the linked title; the second one, a delimited number of characters from the description.

b. Blocks for Recent modules, Top modules, maybe Top Authors...

c. Each register would have:

--- The module's name (with link to the download. Or should we use several links for the different archive versions?).
--- The module's author (linked name)
--- The module's version (number and date)
--- What's new (short description of most recent change)
--- The module's description (up to 255 chars)
--- The module's screenshot (should we talk about the possibility of linking to a gallery?)
--- The XOOPS version (if applicable)
--- Link to report broken link
--- Link to send module's link to a friend
--- Link to suggest a feature
--- Rate this module
--- Comment this module
--- Links to the Forums' threads on this module
--- Links to former versions of the module

From all this we can see it's mostly a reconfigured MyDownloads module. Shouldn't be that hard for the daring xoopsers around.

An important matter has to do with multilanguage capacities. I've said elsewhere we're looking at how to solve this in the long term, but in the meantime, I'm not sure about this: should we use the hack in the modules site? This way we could have several languages in the same site. The implications are complex, and one of them has to do with the often neglected issue of maintaining content. It's still an open discussion.

I'd say mikhail's ideas are as good as they are fast. As someone who lived the 8.3 era, I welcome the opportunity to use long names. But I also try to be practical. Names that are too long have also implications. I'd go for a somewhat reduced version, maybe:

m205_modulename_version.tar.gz /.zip

like

m200_addresses_1.5.tar.gz

(Of course, we might include the author's name in the line containing the module's name.)

This stuff about setting standards should not stop here. I like the idea about having inside the archive the real directory name with all relevant stuff. And we should strive to apply the file and block names described in the module kickstart guide (in the Wiki).

One possibility I've been toying with is the use of an expandable tree to list the modules. Something like:

+ Linked category name one
+ Linked category name two
- Linked category name three
.. - Linked module name one
.. - Linked module name two
.. - Linked module name three
+ Linked category name four

We could store an abbreviated description of each category and module in a string of about 80 chars, and on mouseover we could show somewhere either the category description or the module's short description. What do you think of this?

I'd also like to have the whole bunch of modules uploaded and available, but I'd like to suggest another important task before that. Of course this is a personal opinion, and I hope the many authors don't think it a bad idea, but I'd say all the modules need to pass through a process to make them... er... uniform.

What do I mean? I say all the modules need to include (and many don't):

1) A README file with concise installation instructions, including the data that'll be contained in the repository (See above). This should also include a list of the files contained in the archive.

2) A carefully reviewed set of language files. Don't get me wrong, but there are authors that are excellent at handling code, but whose domain of the language isn't at par, so we should check this.

3) A description file, like the .NFO "standard". This should say what the module does. I've installed many modules just to see what they are...

4) Please add here your own ideas.

That's all I can think of at the moment. Excuse the long post, but I do think this is an important matter for the whole community.

LAST MINUTE ADDITION. I just read onokazu's post. Seems like a good idea, and the only additional comment I'd add is that I'd prefer to abbreviate xoops' name. All in all, the relevant point is we need to have a standard and to follow it.

Cheers.

Dear Xoopsers:

At this time, several of us in the core team have had lengthy conversations with onokazu, Xoops' lead developer, about the future of multilanguage in the XOOPS frame. The technical details are too far from my understanding to be able to comment them, but I just wanted to say we're in the process of thinking about the best solution for all.

That said, I'm in the process of building a multilingual version of the XOOPS 2.0.5a package. The idea would be to include in the downloads this hacked version so people needing to publish their sites in several languages don't have to go through the problem of applying the hacks one by one. Of course, it'd be necessary to edit the sanitizer depending on the languages wanted, and to add the language files. All in all, the idea is just to offer a temporal solution that alleviates some of the problems.

Anyway, this thread is very valuable and should continue. Many heads maybe don't think much better that one, but they sure can offer different insights, and multilanguage is an issue where we need all the different insights possible. This comes from somebody who uses spanish as its mother tongue, in a core team lead by a dutch, for a software package developed by a japanese, and... you get the picture.

Cheers.

4mps phpadsnew (manuals)

Cheers.

msimonds:

Visit catzwolf's site here and download WF-Quote.

Cheers.

ivan8r:

I'll answer your specific questions with a generic answer. To do the necessary changes, first take a look at the code generated by each page and search for a class selector.

For instance, in the NEW MEMBERS block, look in the source for the code that generates the username's URL. Does it have a class defined? If it does, then that's the class you need to change. If it doesn't, then you need to change the selector a and whatever variants are present in the CSS (a:link, a:hover, a:visited...).

The same principle applies to every case you ask about.

Cheers.

Thoom:

The reason your cut&paste operations don's give you results is that a block usually has a PHP file behind to make queries, retrieve and process results and assign those results to the relevant variables, so it isn't as straightforward as many would want.

That said, you can get what you want using a french module called TriBlocks or IncBlocks, that allow you to define up to three different content blocks-in-one. You can see the results of this in the bottom half of Punto flotante.

Cheers.

LethZoid:

You need to edit your template. Open Admin > Templates, go for the System Module and look for the template called system_block_search.html. Apply there your alignment stuff. Voilá!

Cheers.

You are correct. In fact, this could be a good moment to ask the XOOPS community about ideas for the registry. So far:

1) All modules available could be stored in a central repository. This would allow translators to provide language constant files in order to make them available with as many languages as possible.

2) The modules would be organized by categories.

3) The registry would show only the latest version of each module.

4) Each module would have maybe a page describing its features and limitations, and also links to historical versions.

And of course, we'll be needing all the help we can get if we want to succeed in taking XOOPS where no other open source CMS has gone before <grin>. Any more ideas?