tikiwiki: 03chealer * r31665 10/trunk/lib/smarty_tiki/block.title.php: [FIX] HTML (space in HREF attribute when documentation page has several words) hello! what is a quick way to check whether my tikiwiki is using a database or not? i need to make backups of my wiki :) hi all :) when i pg_dumpall, i get a file without any data in it so it appears to me that the wiki on this server is not saved in a database is it possible to use files for storage? if that's the case, where might i find them? quick question - anyone have webdav working on 6.1 on a windows client? @talin: u can store uploads, attachments, etc. in file instead of db. config the location on the appropriate admin page. See docs for details Hey guys, chealer: what do you think of using codemirror as the default editor in tiki? chealer: polom by the way polom hi robertplummer. I haven't use codemirror much yet. it looks good, but how much time do you think it would take to make codemirror a preference? chealer, it is already on by default and viewed under the editable page, but to integrate I'm not sure, it may take some time, but I feel if we are going to be using it in 7, it is a vital move. robertplummer: is your plan to have 2 non-WYSIWYG editors, the plain textarea and codemirror plus a WYSIWYG editor, codemirror being the default non-WYSIWYG (which is the default) editor? 1 text 1 wysiwyg textarea may be on the page, but not viewable, only there to send data through form. then syntax highlighting will be an option through codemirror. robertplummer: so compared to the current trunk (for editpage) you're asking if we should remove the plain textarea for non-WYSIWYG edition? more or less, the UI won't change much, just stability and overall integration. The syntax highlighting doesn't always need to be on if we use codemirror, codemirror is just a really powerful text editor. robertplummer: sorry, I don't really understand, what did you mean by "to integrate [I'm not sure]"? The toolbar above provides some functionality to the textarea, I want to replace that functionality witht that of codemirror. that is all Then give the ability to use syntax highlighting in other parts of tiki. like custom code in your skin robertplummer: oh, so you were saying your proposition to use codemirror as the default editor may take some time (because of toolbars)? right but it's API I think will save us much time in future... so i think it is win win. robertplummer: what I was asking is how much time it would take to make a preference allowing to choose having codemirror or a plain textarea for non-WYSIWYG edition. I don't think we should do that. To much work. Right now it is currently like that, but I haven't worked in codemirror into the toolbars, but if we were to do it that way we'd have to support textarea + codemirror.... to much to support. I think we should make codemirror on, no option, but the syntax highlighting will be optional. codemirror is a very powerful text editor, syntax highlighting is a feature of it, but not required. understand? robertplummer: yes you think it is the way to go? To the end user, they will not know the diference when it is integrated with syntax highlighting off, only when it is on will they know. robertplummer: I would like to see codemirror more before making it the default, but I don't anticipate any significant drawback, at worst we can always rollback. ok Perhaps I can start on the integration and if a concern comes up, then we can address it at that time. robertplummer: yes, if you think it's too much work to make it a preference, feel free to make it the default, for my part. thanks chealer, your input is always valuable. robertplummer: that was nothing. your output is incomparably valuable :-) Have you seen the new tiki syntax highlighting? It is very cool! robertplummer: yes. I haven't used it much but at first sight it's working very well. yea, working on error detection and better end of line support. Eventually I'd like to have nested tiki syntax selection, but we'll see. I don't understand "nested tiki syntax selection" tikiwiki: 03robertplummer * r31666 10/trunk/lib/codemirror_tiki/ (docs.css js/parsetikisyntax.js): [FIX[ More fixes to tiki parser, getting much closer to perfection with this one. tikiwiki: 03robertplummer * r31667 10/trunk/lib/codemirror_tiki/js/parsetikisyntax.js: [FIX] Forgot underscore in the normalTWMatches tikiwiki: 03chealer * r31668 10/trunk/templates/ (9 files): tikiwiki: [FIX] HTML special characters encoding (from r9146) tikiwiki: [FIX] colons inside tr blocks tikiwiki: 03robertplummer * r31669 10/trunk/lib/codemirror_tiki/js/parsetikisyntax.js: [FIX] Added better new line detection in tiki syntax parser. my personal opinion is new new lines are a wasted effort I mean, we're in the 3D era, why do we still work in a single dimension? tikiwiki: 03robertplummer * r31670 10/trunk/lib/codemirror_tiki/js/parsetikisyntax.js: [MOD] Dropped much of the new line support, it is very difficult to enforce. tikiwiki: 03robertplummer * r31671 10/trunk/lib/codemirror_tiki/css/tikiwikisyntaxcolors.css: [MOD] colors Hi, I begin to make some enhancements on categ. As I discover the code, after quite a time I have not yet how are managed $params. I need to introduce new ones, on their properties and for display. The first should be in categobjects.tpl to be able to have defined from prefs a "$params.catdisp" with various values... Thanks to you to put me aware of this part of code, some keys to... ...begin well.