On Oct 2, 2004, at 8:09 PM, Richard Gaskin wrote:
But if you really want to encourage both efficient work and broad community, why not do it as a Rev stack? After all, sooner or later you'll want to integrate it with your stack files anyway.
I'd be happy to add a new section to RevNet for it if you think that would be helpful. Since RevNet is bundled with Rev your stuff could be instantly available to everyone the moment you post it. Drop me a note offline if that's of interest and we can work out the details.
But whether RevNet or some other stack, ultimately the more useful component of such a project will be a stack rather than a browser page. It's HTTP you're after, not necessarily a separate browser application disconnected from your workflow.
Richard,
this WeCode.org project of mine is stack based, it's like RevNET (yes, I even borrowed the stack rect), it can be installed as a plugin, but it also sports a web interface (thats easy when you own the RevHTTPd where it's running) so that one can check news from remote sites. The Idea is that working users use the stack interface to manage their project, but we left a web interface for possible lurkers and for making announcements for each project.
The idea is pretty dumb, WeCode is made of modules for each project:
* Wiki module, each project got a wiki where team members can post stuff, they own a private wiki for their own discussion and a public one for announcements. (it's a revHTTPd based module)
* File repository for droping stacks and files, I am trying to make a server interface compatible with Magic Carpet here, so that one could use MGC to manage the files. (it's a RevFTPd based module)
* Chat with users, (Based on RevChat by BvG)
Database is old'mySQL running at WeCode.org. Pretty dumb, we own all the tech needed to invent this thing without creating new protocols. I want to leave the wiki and the files available at the web interface so that possible lurkers or people without the plugin or people using dreamcard can see the projects too...
The comunication between client stack and the wecode server is thru simple XML-RPC call, again, RevHTTPd based and 2.5 XML-RPC based.
is now just a matter of glueing everything.
Andre
-- Andre Alves Garzia 2004 Soap Dog Studios - BRAZIL http://studio.soapdog.org
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
