Mithrandir wrote Quote:
Do you mean things like theme and template development in the Mozilla Composer? Making Mozilla Composer an IDE for manipulating the HTML (and Smarty code) in these templates? If so, then it is not so much XOOPS, you should collaborate with, but Smarty as we use their technology for these themes and templates.
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.
SummaryProduce 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?