> > this clarified a lot. Basically I was worried about how to express > > 'ordering' of content, and it is only now I get that your idea here is > > to express the ordering by having a filename specification. > > > or by having xpath lookups ;-) > (the or is exclusive at your own coice) > > in every case ordering based on xpath would be mostly not a good idea > better use : > - labeling: getting the caption for the menu from the file itself (more > expressive then the filename often: eg for faq the full question) > - filtering based on e.g. an attribute value priority="high" etc etc > > (you'll even start to love xpath when we're done :-))
Truth be told I know quite a bit about xpath. It's just that its syntax can get so horridly complex...it needs to be optional. > > we've got two weeks to get something working (one of our developers has > > set a fair 'deadline'; see it as a challenge =); otherwise we'll likely > > use anakia for the next 6 months or so.... > > > > I don't know anakia, and can't expect you to dislike it as a solution anakia is coupling xml with velocity. It is neat in concept =) > I'll do a serious effort the coming week is the only thing I can say cool. > If you can still evaluate then ? the 'two week deadline' is not solid as a rock =) This is still OSS dev, which is supposed to be somewhat fun at times...that deadline would be two weeks from last friday or somethin'. I just find having deadlines means stuff gets done...or you'll know when to abandon something when you miss it by a month. > Also, I'll be asking stupid questions to get around faster, so bear with me > please... no prob =) > > once again, start simple. Most cocoon guys I know have the general > > tendency to implement everything at once. Might be their one flaw =) > > there must be more wrong with them ;-) sssht! (they're listening...) > > we're definately on the same page. It's just the tone of the forrest > > website suffers from the same problems as the avalon one: way too > > technical without getting enough examples, context, and general idea > > first. > > hey, blame yourself, you're in a 4.1 release, we're just starting 0.1, > remember ;-) we do blame ourselves, all the time =) It's just most of avalon is best explained in a computer science master class tone, and it is hard for some of us not to.............. > > I understand Nicola is active on forrest, which is why I mentioned the > > project files. Integration with ant is instant added value; as is > > integration with forrest. > > I don't get this fully yet, but someone just told me I shouldn't try doing > all at once :-) hmm. Basically everyone uses and loves ant, so if there is a jar file you can drop into your ant ext directory and then you have an easy-to-use <forrest/> task, that is neat. However, if forrest is worthy, someone will no doubt contribute that task... > > the thing I want most. Doc tools change, DTDs should stay the same. > > question was: are you using the forrest (cocoonbased) generation process? > or are you using ant and <style> instead? part of our site is cocoon (framework, excalibur, apps), while other parts (logkit, phoenix) use anakia (the <anakia/> task). We used to be completely cocoon but parts were converted to anakia because our cocoon-based setup was broken (and slow when it did work). Some of us are now going to put in time (though none of us ever has any =) to get the cocoon-based setup work. When that fails it is likely we will convert everything to anakia. Either way, we will probably convert to the forrest DTDs. > > yup. I look forward to having a neat system to use; problem is ours has > > been broken there is not so much patience left. But don't let that rush > > you into bad releases though =) > > patience is a virtue, as is working hard I guess... so if it comes from both > sides we'll get there I don't doubt it. Just a matter of time, it is. > and euh, we already had one bad release :-) > this time it feels like I could have a *user* which will (no doubt) make it > infinitaly better I will not dig into development then =) If you get everyone on the avalon-dev to be happy about forrest, you're going to get loads of users. Avalon is one of the big projects around here, documentation-wise. > regards, and be ready for some dull questions flying around tomorrow =) Keeps me from actual work, so its welcome... cheers, - Leo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
