You are refering to my point b), which is largely dependent on a), as much as on c), which again depends largely on d).


There has been no decision made, on what kind of sub to use (again matching my point a)), but the xoops.org team has always signaled support, and a possible later adoption, once it is clear, what and how a Theme Forge would work, look like, etc...


So all is in the works, though as Depeche Mode stated in a song of theirs "It's a question of time..."


Oh, BTW some historic background:

There had been work done by a few members of xoops.org a while back, to create themes.xoops.org. Unfortunatly, and to me, for no apparent reason, activities halted, a theme repository opened on xoops.org, and the idea of a separate site dealing with themes for XOOPS was dropped.

Then the discussion started once again on xoops.org (please search for this, if interested, haven't got a link handy), at which community members again expressed desire for something like a theme forge.

There were many ideas, but never did a excepeted concept arise/evolve. As the need and desire was there, and also members claiming their interest and willingness to work and contribute towards the idea, Herko launched a mailing list.

The mailing list proved none efficient to get anywhere, so StudioC and I just created a site, to host a pre-XOOPS Theme Forge, IOW providing cyber space, to grow what we want. Once XTF members feel happy with what they have built, organisation efforts will concentrate on the going public of XTF.

There was the idea of having a public opening being accompanied by a contest, but that is just more work, which at this stage, is better not even contemplated....never the less, still in the back of our minds


Hope this info is of interest.....

Well, we also have an icon repository, where we hope to collect differnt language buttons, as well as alternatives.


We wont open to the public, until

a) internal organisation is up to scratch
b) we have moved to an official domain
c) there is enough content to entertain new visitors and members
d) MyXoopsForge modules are set up and running, so that projects can be set up (no good in having a forge, where nothing can be forged )

While there is much more work, the above four points need to be cleared first. Never the less, if you are interested in contributing, you surely are welcome. As mentioned above though, you unfortunatly will not be able to set up a project just yet. I've posted for help on dev.xoops.org, and I'm still waiting for help, which I'm sure will arive, as soon as the apropriate people have time.


XTF will still take some time, but the more people chip in, contribute, and help wher help is needed, the quicker we will be able to open XTF



On another note: themes can, and according to current planning, will still be submited to xoops.org, where the theme repository is at. We might need to rediscuss this point though, but not at this stage. Though, I did want to have this mentioned to you, as you stated something about wanting to submit a theme. If you have any themes you would like to offer others, please do so with xoops.org

Though, just reread your posting, and it might be, that you have a project in mind, that I have not understood. If you want to talk about your theme ideas, XTF is definetly the place, so I will set you up again, and send you the details.


Regards and Thanks
JasonMR

This is with a problem that we are trying to address with the XOOPS Theme Forge.

The problem is this: Theme designers either design for their or a clients needs, meaning, a well designed theme, will only be adapted for a specific set of modules, explicitly those, they or their clients use.

Currently if you download a theme, you will most likely need to edit the templates of modules you have installed, due to the above.


One can't expect designers to develop template addaption for their themes, for every existing module out there. Never the less, people do adapt templates for their needs, so what we need is a cental template repository.

Now the sturucture of this repository seems overwhelming at first, but its outcome is largely dependent on community support, IOW member contributions.

Currently we already have a nice theme collection together. Never the less, as stated above, the look and feel is not only governed by themes, but also by templates. This has been a negleted side, when talking about themeing XOOPS powered sites.

XTF will organize projects, that have set as their goal, to develop different sets of templates, with a concern for layout and interface design, IOW how best to present, give access to, and collect data.

A good idea would be, to have different teams, that take upon them, to collect template sets of modules, which are addaptions for specific themes.


To display the organisation a little clearer, let me try myself with an example. You Dan have just released hypertheme. As this is your theme, you would start of the project, asking users of your theme, to send to you their template modifications. Some you will like, others you wont. Never the less, on your project page, just as we have a file repository on dev.xoops.org, there will be a file repository for projects hosted on XTF.

So all template files sent to you, you upload to ths file reository. Which should grow with module template sets, that you don't use, and never have bothered with, but are addapted for your theme, so that more people can use your theme now, without having to worry about template addaption.

Additonaly you can offer different kinds of GUI for exisiting modules. I am hopeing here, that there will evolve special interest groups, that will concentrate on the GUI of certain modules. We do already have one such group, which is trying to develop a new set of templates for newBB forums.



There is another solution to the above problem, which is to standardise template design of modules, but that is something that would take a lot of discussion, and even more work, while I'm not even sure, it is satisfyingly doable.



So, to answer your question, yes it would be best, if templates matching your theme existed for all modules, but no one can expect you to do this work (especially not on your own, and not being paid for). While this would be a great feat, and an admirable contribution, I'm sure you would prefer to work on new modules, than 'playing' around with template sets But get others to send their adaptions to you, and include a modified template set with your theme files. In the end, it all comes down to, how much work you want and can comit to a project.....

The logic/functionality of your block is stored in .php files, which should be located at

XOOPS_ROOT/modules/YOUR_BLOCK_MOD/blocks/block_logicOfYourBlockMod.php

The files related to the presentation (output presented to users/viewers), are your template files, which are .html files, and should be stored at

XOOPS_ROOT/modules/YOUR_BLOCK_MOD/templates/blocks/block_templateOfYourBlockMod.html


Though, not sure I understood your question completely, so I do hope this is what you had been inquiering about....

As far as I understand it (I shall be corrected by those that know better):

acknowledge := taken notice, but not verified
confirm := same as acknowledge, only with the extra step having been taken, and the broken state of the link has been confirmed/verified

XOOPS uses the templates as they come, which is refered to as the Default Template Set.

If you make changes to the template files directly (meaning, you go into a template folder, change a file from within, and save changes), then you have in actuall fact changed the default template of the module. XOOPS doesn't know this! And the only way to make it aware of it, is to update the module (sys admin -> modules -> button to the right in the table listing all installed modules).


The "Official" XOOPS way, of changing templates is the following:

- open Sys Admin -> Template manager
- clone Default Template Set
- edit templates of cloned template set
- open Sys Admin -> Preferences -> General Settings, and change the default template set, to the cloned


HTH

BTW: could you make your templates available? We are just developing a XOOPS Theme Forge (XTF), which will have a template repository, in which I would like to post your creations. Further there has been a project started on XTF specificly addressing the newBB templates, and I'm sure the particpants would appreciate to learn about your efforts.

Please contact me via PM or YIM:pjay_dml

Regards
JasonMR

If any developer ever wants to take up this project, they might want to take a look at this Recipe Markup Language Specification, an XML schema.

All comes down to expectations. What you may think is a great theme, others wont, and vice versa.

We are in the process of developing a XOOPS Theme Forge (which is a lot of work, and not many people contributing), that does have the aim to attract more Theme Designers, as well as offer a place for those interested to organize themselves, as well as their project.

Further (the biggest work load), we will offer an extensive resource collection for anything XOOPS Theme related. There will be an Icon, Image, and Template Repository, tutorials concerning different aspects of XOOPS Theme design, a web guide to sites, we Theme Forge developers find/found to especially helpfull.

You know dilliywilly7, the big problem those people that contribute experience, is the lack of help from others. Here at xoops.org I often feel surrounded by 5 year old "I want, I want, I want, NOW!" (not directed at you!).

Having said that. Developing a theme is currently very work intensive, and unfortunaly, while many business like to use XOOPS and come here asking for help, the fewest contribute!!! A big annoyance to me personaly, but that's just the way life is.

@brash: I agree And thanks for pointing this out, these people deserve the credit...all though, as you mentioned, there are a couple more, but I'm so bad when it comes to name

I'm not sure (as I don't use Multimenu, this is something Solo would know as the creator ), but I believe that Multimenu just doesn't automaticly display said submenues, but that you would have to provide these links by hand. At least that was my experience, when I first tried it (a couple of mth's ago).

But looking at this thread indicates, that the newest version 1.6 should do this.

Here's another thread, started at release.

HTH

It seems to me, that this is happening, due to one of the modules you have installed, but I can't pinpoint it, and don't have the time to drill down into this any further, sorry, but what you could do is (very dedious though, so you might want to leave it, as it's no mayor error):


- one after another, deactivate your modules
- until said error disappears
- then you have the culprit


Sorry I can't be of more help....