OK:
1)You can position blocks wherever you want, just change the weight so they line up where you want them. It's not done thru the theme.
2)Yes, the table colors are done thru CSS. In the theme are style.css (For IE) and styleNN.css (for Netscape and Mozilla) You'll have to change BOTH so it looks good in all browsers.
3)I have to map the image where the links are. Then you just find the direct path to whatever you want to link to and make it the link.

Quote:

are you saying you have XOOPS 2 fully working and compatible with PHP 5? if so can u share how?

other than that nice post.. very helpful to those that need it..

this really looks sexy!

3 things id like to have changed :

1st: login should be UNDER menu

2nd: i think the table colors are made via css so i can change them easily? this would be cool. if not could u tell me where to change em?

3rd: the links at the top: can u tell me how i do this? i mean how i link it to blocks from xoops^^

would be really cool! many thanks for this great work by now!

We apologize for any slowdowns anyone may have experienced, but with shared servers it is inevitable. It is not a completely perfect environment due to the different types of sites and the activities performed. We do move sites to different servers as we see any issues reported and evaluate site activity on the server (CPU and memory usage logs). I guess you could call it internal server organization. :)

We immediately check out any problems reported at our helpdesk and resolve them as quickly as possible to retain normal server load. A server can go weeks or even months without any bumps, and one unfortunate day a script can get caught in a loop, or there is MySQL abuse. We have quite a lot of shared servers, and once in a while something is going to come up. We certainly would rather it not as it hurts our customers and us, but we can't put 3 sites on each server. ;)

You can post in our forum, surmunity.com 'Attn Teq' if you have further questions about your account or the server that you are on. I would be happy to help and see if there is anything I can do to improve your service.

Our network uptime has been 100% for the past two months. Any downtime is server downtime: related to one server and an issue with an account on that server.

Sincerely,
Kayla

The answer is yes, as long as you use different prefix for each Xoops.

yes.. during the installation you can change the table prefix..

ie the default prefix is 'xoops'

which means 'xoops_' will be prefixed to the beginning of every table name..

so you can change that prefix on the install screen to anything you like.. which will then mean you can use just 1 database and they won't get mixed up with each other..

for example, I put one XOOPS in /a/ folder, another one in /b/ folder, can it possible to be installed at the same time?

so that both XOOPS system have their own newbb, news, bla bla bla...... and are independent, can it be made??

thanks.

OK have a look at www.bassmanthemes.com and choose ann1 from the theme selector (IE only at the moment) I haven't done the links at the top yet but otherwise should be OK.

Mithrandir wrote Quote:

Absolutely not, the idea is having XOOPS replace Composer. This thinking stems from the reason why Composer is there in the first place – to give the user the ability to create a web page or to import / cut -paste text into a HTML environment without having to understand HTML. HTML coders would not use Composer but instead their favorite editor – although they may quickly validate using Composer.

If Composer is used by the casual or non technical person who wants to create HTML docs, then XOOPS can very well steal the show. This is how I perceive this would work.

XOOPS is the web editor for Mozilla.

a) Based upon practicality and playing to an audience of non-technical content providers, a standard template for XOOPS would be created for the extension. This template would permit the client to enter content, print, preview and post. The client would need the exact template on the server. It completely replaces Composer.

b) Templates are the bases of giving functionality to XOOPS. All the intelligences of how XOOPS’s functions in the backend will be enabled within the template structure. If you allow the client to add flash content, it will be the template that predefines a frame for the flash object. Just as skins are made to give more options for an environment, templates would do the same.

There are two distinct elements of creating an extension they are:

The use of templates to create pre-defined frames
To create special Mozilla enabled components

The object is to create unique functions that blends within the Mozilla culture which will give practicallity and reason to installing these extensions.

Because Mozilla suite has a full integration with its mail client (where Firebird is only the browser) consideration of how these components will function will decide if they can indeed be shared for both Firefox and the Mozilla sute.


Reasons for installing XOOPS extensions

A - If one wanted to Blog, you would not need to have a live connection to the internet, you can write your articles, inssert images - photos, preview the assembled pages and upload them later.

B - A newsletter can be created and then previewed for release by the editor. The local machine would not have to connected to MySQL and would serve as a beta site. You would not need to produce an actual beta site for previewing for local viewing.

C - Media objects within the iframe can now be previewed before uploading. they can be tested for position, html compliancy and overall contextual placement. You will also be able to test the site with others for addressing quality assurance issues before uploading. These files are not connected to a MySQL server for a local machine.

D – Serves as a webpage copier. This locally produced blog or article with images allows the author to make a digital copy for archiving from the local files. All media and images and infrastructure is contained in one main folder. A CD or DVD can be produced from the local publication. Media and text files can be served on your local machine or uploaded to a XOOPS enabled site. It will look and behave the same, rather its on your pc or on the internet. Of course you would need lite version of XOOPS installed.

Summary

Produce a gateway to some key features to XOOPS by integrating elements into the Mozilla browser that will compliment the function of communication and content creation.

The scenarios I have described above may not be practical, but I think there is a place for adding value when you ask not the question, “What do we do when we are on the net, but rather, What do we want to able to do. I look at the internet as – viewing and composing.

"MoXOOPS" lite would act as a lite publishing tool for a local machine and for XOOPS on the net. Although the lite version has limited functions, all files, CSS and templates are fully compatible with XOOPS.

Do I hear a mobile version?

is there a way to just have the mylinks index page display in an iframe without the surrounding menues and banner headers etc