Re: embracing the future

On Tue, Oct 21, 2003 at 04:29:07PM -0400, Luis M wrote:
> 
> Hello,
> 
> After seeing the phpslash-dev module lag (and the -ft also) for a few 
> days/weeks, I gave careful thought to improving at least the -dev 
> dramatically and then use that to do new releases. Here are few of the new 
> dramatic ideas (which are not new per se, but needed in order to keep the 
> project current with what other projects are offering):
> (NOTE: order matters)
> 
> 1. xml-rpc support: for things like transfering files from one computer to 
> the server and for posting stories in a "blog" kind of way using nifty 
> tools like gnome-blog and/or whatever other xml-rpc-compliant software the 
> user might choose. It's a matter of deciding:
>    a. what protocol to use
>    b. how to implement it in a way that can be easily turned on or off
>    c. having volunteers to work on this (Joe?, myself... etc...)
>    d. try not to reinvent the wheel (copy other GPL projects' ideas if 
> possible)
> 

Sounds good.  I've had test xmlrpc servers and clients that could talk to
a few phpSlash methods, but no general wrapper to all functionality.

I think blogger-api, possibly wasabii.  I don't know enough about
phpgroupware's except I think their xml-rpca uth mechanism is something we need to look into.

We may also want to provide a xml-rpc API tailored especially for
phpSlash.

> 2. a consistent way to input text when creating new entries for stories, or 
> posting comments, etc... We talked about using Phorum-like syntax: 
> [url][/url] and the like, since that's very common nowadays on the internet.
> 

I'd like to have some kind of plug-in filters either at rendering time or
publishing to do this as well as other kinds of things like add annotation
to links showing the site like slashdot.

> 3. having a way to input data by using JavaScript or whatever is standard 
> nowadays for all main browsers. again, we will need a way to turn this off 
> for those who don't care, but for those of us who do, it's just a good 
> thing to have. it works for Phorum...
> 
> 

is htmlArea3 released?  If so, we should probably have this as an option
or installed in one of the distributed skins.

> Comments anybody? Features I'm missing?
> 
> Some research should go into finding why to use certain protocols for 
> blogging over the others, but, aside from that, I think these should be 
> just one baby step towards keeping phpslash future-proof (for now that is).
> 

Need to investigate use of SOAP too.  Maybe WebDAV down the line.


> P.S. as a side note, I will try to implement all of these and whatever else 
> in phpslash-dev and either commit them to a special area, say "contrib" or 
> allow it to be turned off by using the config file (turned off by default 
> of course). However, with help it will be done faster and we can just move 
> on to do a new release with these features.
> 
> 

I'm going to be working to install memcached (
http://www.danga.com/memcached/) support into jpcache and slashDB.class.

I also need to test a backport of the PEAR phplib changes into
slashTemplate.class ( and then maybe to phplib template.inc).


thanks,

Joe

> ----)(-----
> Luis Mondesi
> System Administrator
> LatinoMixed.com
> 
> [email protected]
> 
> "...The Mac does this so smoothly, it feels like an extension of your 
> mind." - Paula Speer, MacWorld Magazine 2003-04
> 
> Public signature: http://www.latinomixed.com/lems1/public-a.asc
> 


-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community?  Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/