[Jaws-project-developers] Some tasks for this Week

[Pablo F. <pa...@pa...>]

Hello,

As most of we know we are at some weeks to finish this month, and one of
our goals are to release Jaws at the end of February. So, I have been
looking in Jaws of what tasks we neede to finish so we can release Jaws
to a test phase and then.. the final release.=20

We are five developers and I know that must of us are busy at work or
some other projects, but I think that each one of us can take one task
and try to finish it.

Please, prepare your coffee before start flying with my ideas...

1. Documentation:

Most of the gadgets that we have are lack of documentation. So, anybody
that wants to hack the documentation (PHPDOC)? I know this is a pain in
the ass, but we need to doc. the gadgets. Also, JawsTemplate.php is lack
of phpdoc.

2. One Jaws to rule them all=20

I've been thinking of how can we deal with multiple host/user
installations. So I decided to take a look to Drupal. I decided Drupal
cause I considered it a nice product.

So, searching in google how to do that in Drupal I found a interesting
link [1] that explains how to do that. How does Drupal manages it?.
Well, in order to install it, the user (admin) needs to create a file
inside the include's directory. The config needs to be named:
mydomain.com.php.=20

So for example, if I have www.mydomain.com.php and
www.myotherdomain.com.php then if someone tries to access
www.mydomain.com Drupal will read the config file (DB params)
www.mydomain.com.php and if other visitor goes to www.myotherdomain.com,
then Drupal will use the DB params for that site.

I think we should have that with the addition that our JawsCommonLoader
(or whatever) should look for a config file site
(myotherdomain.com.php), if it exists.. then use it, if not, it should
use the config.php (the original one).

So, having one config like that we can keep an easy installation per
user?. How?, lets suppose that we have our original Jaws installation
in /usr/share/jaws and we want to install it to Sarah and Michael. Also
we have our domain: mycoolblog.com. So, after we create their users
profiles (adduser) and configure their virtualhosts (if its required) we
can do:

cd /home/michael/public_html
ln -s /usr/share/jaws/*
rm -rf resources
mkdir resources/phoo resources/gadgets resources/xml resources/...

Why we removed the resources/ directory?. Easy, we want each user to
have their own resources (phoo images, xml files, banners, etc). In the
next task I will explain the resources.

3. JDD  - Jaws Directory Distribution (No, the J is not Java).

ion sent an email few weeks ago about creating a new Jaws Directory
Distribution. And while I was thinking about how to keep running point 2
and taking some ideas of ion, Jellybob and imcsk8 I have this schema:

.
|-- admin.php
|-- gadgets
|   |-- Banner
|   |   |-- Images
|   |   |-- Model.php
|   |   |-- Templates
|   |   `-- Views
|   |       |-- Gadget.php
|   |       `-- WebService.php
|-- include
|-- index.php
|-- resources
|   `-- xml
|   `-- files=20
|-- themes
`-- wsadmin.php

You are asking: WTF is resources?!. Well, to separate and keep multiple
installations so each user can have their own resources (that is what we
are looking for).

So for example, if we want to update Jaws for all the users, we simply
update the files, without updating resources.

4. Translation

Although, I was looking the work that Jon has done in languages/. I just
have two suggestions:

* What is better, to have just one .po file for ALL gadgets? (maybe one
big .po file for all gadgets and each non-jaws gadget can have their
own .po file).
* There are some string we also need to translate, in include/ we have
more strings to translate.=20

Thats all folks ;-).

I will split this mail and paste each part in the Wiki.

Regards,
Pablo

[1] http://drupal.org/node/275
--=20
Pablo Fischer Sandoval (pablo [arroba/at] pablo.com.mx)
Cel: (044-55) 2689-6351
Fingerprint:  5973 0F10 543F 54AE 1E41  EC81 0840 A10A 74A4 E5C0
http://www.pablo.com.mx
http://www.debianmexico.org