To refine the clonability from the admin/developer side.

Rather than get to fine-grained on the 'dirname' internally, wouldn't it make sene to use it where it is clear there would be a conflict with another module, such as table names, etc?

But as for function names (and I am not yet clear on the scope of function names) do they have to be different module to module?

And on this point, where I look to undertand scope? is this dictated by the PHP language?

In plain english, can two different modules have a class with the same name?
Or from the example above can "myMOD_search" be define in different modules without conflict?

krayc

Not that I fully understand all the code posted so far, but isn't there two issues here?

How to make the modules almost effortlessly cloneable, and naming the module?

I mean from an admin point of view there is simply using the dirname or at least just one line in the xoops_version file (or whereever one names the module). So that achives cloneablity, assuming one writes it accordingly.

The second question is from a user standpoint, i.e. how does the 'module', and it's elements (entries, lists, categories) present themselves on the screen?

For my 'very' limited experience in adapting modules, I simply use the language file to achieve the modules' 'user side' functional/appearance. For instance I wanted a simple directory that users could submit a 'statement' about some project they are involved in. So I worked on adapting 'myguestbook' by narga. I fould I could do a lot by using the 'language' file to do a 'makeover' of a module.

that's my thoughts for the moment.

krayc

Is there a common problem with some modules written for x2.05? or is it something else?

Is it something I can tweak in the module?

I mean the modules in question are pretty current, xDirectory for instance.

krayc

tjnemez, is your soapbox clone cloneable? :)

Id luv to use a few copies of it in a site im working on.

How is it working for you ?

krayc

Since the site in question is for the most part private, ie anonymous users can only see one TinyContent home page and that's about it.

I would like to have a semi-anonymous user group that have to logon but they would not be able comment or post topics or submit any data? Is that possible within the current group permissions structure?

If it is, I can't see how to do it?

krayc

martin, where did you get Content Relations? I just downloaded it and put it into a 2.0.6 test site, and it doesn't show up in my installable modules sections of the module/admin page? Did you have to tweak it?

krayc

still looking for help on the above post!!

I've spent 2 years looking at every open-source CMS I could find. I spent months working with ZOPE/Plone. And finally switched to XOOPs, why? First your interface out of the box was easy to understand, So I could tolerate the lack of documenation.

Second, it was OO (i've yet to confirm that by writing a module)
Third most of the functionality I needed is already written by the core team and enthusiastic other users.

But for me to invest my time in module dev. I need what I state below. Yes you will get a lot done by tenacious hackers, but I believe more world-class modules will be developed when there is 'world-class' support for those developers.

(and yes I've joined the DOCS team)

The only real thing holding back XOOPs is documentation.

And I say this again, and again.

The software is easy to use, more or less, so user docs are nice to have....

BUT... clear concise documentation, with best practices promoted in each of these: Recipes, and how-tos, examples, examples, example. Most programmers learn by example, not by studying the theory of an api, or browsing lists of variables available. Speaking for myself, I can learn quicker by example. Also a plain english/french/etc... overview of why things are done the way they are in the CORE of XOOPs. Ie for other module developers to succeed in keeping with the CORE Teams thinking, we have to know what that thinking is.

krayc

Ok, I upgraded to .06... it now works.

A refinement? How do I also send a copy to the admin of the site?


by the way thanks for that code. just what I needed.


krayc

2.05 is what im testing it on.

I haven't had the nerve to upgrade my site yet until I can figure out how to copy it.

krayc