CIF rewrite
IIRC, Grendel began that.
Right, but as I said many times - I'm not going to be able to finish that alone. It's enough work to fill 8h/day for 6 months for one person.
True, but we may organize for that.
What more feature people want?
I have some ideas I'd like to present during some discussion on the conference. (for example object-oriented approach to HTML/RXML/XML - presentation of the web pages to the caudium modules/scripts as a collection of objects on which operations can be performed to alter their content/properties; Rewriting the Caudium core to separate it from Pike /in C, probably/ so that Pike runs in a separate process as a "script server" accessible either locally via various IPC means or remotely with XML-RPC or whatever protocol seems to fit)
That's beyond the CIF :) But sounds really cool.
I'd change (read: allow to change/make default) the select multiple to checkboxes, since many people aren't familiar with these.
What will you do if you have 100 options? (for example 100 modules) Paging doesn't seem to be a good idea, and a selection page 10 screens long is even worse...
I wasn't thinking about the add module page, but modules in general. 100 checkbox are not worse than the add module page in standard mode :) Off course, each one could choose that.
All in all, the look of the CIF is the smallest concern. The beast sleeps beneath the surface. And it's a huge beast. Enormous.
Yep, but we may be aware of some kind of functionnality before coding things.
Could you explain breifly how you started to recode this?
RXML parser, and the future of RXML
Grendel has a piece of code for the new RXML parser.
Yep, and some (unpublished) code for a new HTML/RXML parser for code that isn't XML-compliant.
Thanx, my webmaster will be happy.
- parser speed (read: Martin's RXML Vs PHP bench)
- enhancement of do_output_tag()
you wanted to say, reimplementation+redesign, I hope? :)
I meant something reliable ;)
Something allready exists on riverweb. Could we steal some code?
I think it's about quite a different thing. The repository should be accessible not only from the web with mouse clicks, it should mainly be a way to organize the modules/extensions to pike/caudium together with their docs so that it's easy to access/find any of those in a canonical way.
_nice_
It should be integrated into caudium's website for people not having CVS write access to share their code.
Yep, I agree. There should be a single Caudium module (probably using another single, Pike, module) that would present a view of the repository.
Could the CIF benefit of these functionalities?
Marketing / popularity enhancement
What kind of people do we want to target? Coders? Web-literate webmasters? Newbies?
The most important target would be the ISPs, I think. Once you get Caudium in there, you will slowly win the others. That's because it's useless to have an army of drooling webmasters/coders without ISP where they could install Caudium.
That's egg and chicken problem. Would ISPs install Caudium if noone care to use it? Is there any hosting service that provides Caudium hosting except kazar.net? (and linkeo, but that's a different thing)
Another target is people that manage their servers.
It's hard for people to hear about Caudium stuff, coz everything is talked into mailing lists you have to subscribe to.
Well, Bertrand, I might surprise you but... this is internet, you know :) - most of discussions take place on mailing lists/usenet forums :)
I may not have been well understood.
The difference between mailing list and usenet forums is that you don't have to subscribe to: you just have to select any group, lurk, easily read past message, make a search on it with google (easy to follow a thread), no more read it if you want w/o unsubscribing... Off course, you have archives for mailing list, but never seen a single one that present threads in a usable way. IIRC, our mailing list archives is protected against spammers, ie no search engine would archive that (trying to verify that since yesterday evening, but listes.oav.net seems down)
That's why i asked some time ago if we couldn't sync the mailing list and a usenet server. Then we talked about which group, coz we wanted a good group. Then the better killed the best and we didn't come to a solution :)
But I guess a web-based forum would be a good thing for Caudium to have (another thing that would have to be written, I guess)
I know people like this kind of stuff. I definitly thinks that this kind of things sux.
If someone wants to write a forum, abstraction interface for data is planned for CAMAS 1.3: it could connect to NNTP (or even a database for a full forum behaviour)
Then, writing tutorials, docs and packaging stuff is mandatory if we want new people to come. For example, i'm very responsible for allmost 0 CAMAS layout docs and darwin packaging.
I guess Caudium needs a rewrite first, docs then. And before you protest, think about it...
[snip]
Why do you think i'll protest? :)
I fully agree, but docs means tutorials or sample code. I was told by a newbie yesterday that caudium website hardly lacks sample code.
Somebody who is willing to inform "press" about events in the Caudium community, somebody to arrange for Caudium articles to be published (s/he wouldn't necessarily write the articles herself, of course),
Press is a good medium. Dunno if that's a coincidence, but look at the unique host visits of caudium.net on march. This was when vida's article made it in the french press.
to contact the various ad companies which work on the link exchange basis (and, yes, linkexchange.com is Microsoft, but they should be interested in exchanging banners with a site that has PR6 in Google);
Is that efficient? I personnaly never nor click nor even look at banner contents.
and the other person would be responsible for, let's call them, milestones in the caudium development, for coordination of various efforts, task assignment - i.e. somebody to fulfill the goals set by the project leader in their greater detail.
That would be a great thing.