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

[Jon W. <jo...@je...>]

On Tue, 2005-01-18 at 12:07 -0600, Pablo Fischer wrote:
> Hello,
>  
> > Agreed - I'm happy to do some of this, especially since it's something
> > different from bug fixes and minor changes (which I'm currently stuck
> > doing for a client's website).
> 
> Great!. Also we are open for people who would like to help with this (I
> know that no one is going to raise the hand).
> 
> > Should multiple sites have to use a different database completely?
> 
> Cof cof cof.. I forgot to add this point in the mail,  however its
> already in the wiki. Maybe we can have:
> 
> $db_prefix."_blog";
> 
> So, if you maintain other blogs, you can declare the $db_prefix also as
> the db username, so:
> 
> michael_blog 
> 
Doing this you still have to update the schema on every prefixed table
whenever it changes - I know we don't do schema changes often, but I'd
still like it to be as easy as possible to handle it.

> Could be a good idea.
> 
> The only difficult task is how we are going to deal with db prefixes in
> our queries? I have some ideas:
> 
> 1. Change all of our queries, so that all table names in our queries
> will be named to: $GLOBALS["prefix"]."_tablename". This is like having a
> kick in the nuts.
> 
> 2. Don't change nothing in our queries, just edit our DB Drivers. Lets
> look for a nice regexp (don't look at me!) that can replace all the
> table names with other thing ($prefix.\\1, for example). Any geek in
> regexp's around here?
> 
> 3. Stole ideas from other projects, like drupal (they are using
> prefixes).
> > 
> > > 3. JDD  - Jaws Directory Distribution (No, the J is not Java).
> > > 
> > Are you sure... you did seem very keen for us to have *coffee* with this
> > e-mail.
> 
> :-P 
> > > |-- resources
> > > |   `-- xml
> > > |   `-- files 
> >   |   `-- phoo <-- This is likely to be needed ;)
> > > |-- themes
> > > `-- wsadmin.php
> 
> Heh, yes, we need there phoo ;-). Yesterday talking with ion we decided
> to rename resources to data. And do some changes in the JDD. 
> 
> Now, we are going to have all the *.php files inside /gadgets/Blog (for
> example): BlogModel.php (Model), Blog.php (Gadget), BlogWebService.php
> and BlogInfo.php (Information of the gadget). And also have the
> directory Resources inside the directory for images, css, and other
> stuff that the model/gadget needs to run. 
> 
> You can get a better idea if you take a look to the JDD section in the
> wiki [1].
> 
> > Sounds good to me, although I'd still rather any XML stuff that's needed
> > gets generated on demand, and then the results cached until the next
> > change.
> 
> What do you mean by cache? cache for templates.. cache for xml??.. cache
> and other stuff that are per user (per directory installation I mean)
> will need go to 'data' directory.
> 
> > This is a hard one... does anybody know if GetText supports some sort of
> > include system, so that each gadget could have it's own .po, but they
> > all get included into one big one?
> 
> I don't think its so hard to keep all gadgets in one file. You can keep
> all the translations in one file I did that in C and C# long time ago,
> and as you know thats not a PHP dep, its just a shell command.
> 
> The difficult task will be: How to get together one non-official gadget
> translation with our big file?.
> 
> See ya,
> Pablo
> 
> [1]
> http://wiki.jaws.com.mx/doku.php?id=jaws:proposals:new_directory_layout