Tiki-KGB: 03redflo r52559 10branches/12.x/lib/userslib.php * [SEC] Prevent null byte poisioning (thanks Matthew Daley)
03redflo r52560 10branches/9.x/lib/userslib.php * [SEC] Prevent null byte poisioning (thanks Matthew Daley)
03redflo r52561 10branches/6.x/lib/userslib.php * [SEC] Prevent null byte poisioning (thanks Matthew Daley)
Tiki|bot: New Forum Posts: Tracker field category no initial value (crossposting) - http://tiki.org/tiki-view_forum_thread.php?forumId=26&comments_parentId=53499
chibaguy: joined #tikiwiki
aalex: How to apply a custom CSS class on the items in a menu?
TomJarvis: joined #tikiwiki
chibaguy: joined #tikiwiki
joined #tikiwiki
joined #tikiwiki
aalex: oh well, edit a template file !
:(
chibaguy_: joined #tikiwiki
chibaguy: joined #tikiwiki
joined #tikiwiki
Bsfez: joined #tikiwiki
Bsfez1: joined #tikiwiki
Justeco: joined #tikiwiki
Hi! I didn´t find a theme with a good-looking forum yet. Can you recommend me one?
Tiki-KGB: 03chibaguy r52562 10trunk/ 10(94 files in 61 dirs)
[ENH] Replace Glyphicons with Font Awesome. Work in progress. (Eventually icon sets will be selectable; this is an interim change.)
chibaguy: Justeco, what version of Tiki are you using?
fabricius: joined #tikiwiki
Justeco: 13.0
chibaguy: Well, I think the forums all use about the same HTML and pretty similar styling because they are mostly based on Bootstrap elements now, so far.
What do you have in mind by "good looking"? Any examples on the web?
Justeco: Here is a good example: http://forum.astor.ws/
chibaguy: I see. Pretty nice.
Yeah, currently Tiki's forums look pretty bland because we just integrated Bootstrap and so the forums are kind of default Bootstrap elements.
And Bootstrap default seems kind of vanilla modern. Your example is a little bit retro or classic forum, you might say, with more use of background colors, etc.
I think once we get through the Bootstrap basics, there'll be more expanding beyond it, visually.
So far we've focussed on the overall page, with not too much work on specific feature appearance.
okeedokee
fabricius, are you around?
I need to find a place in trunk for the former layout.css (now tiki.css) etc and other files that themes use. It needs to be in tikiroot/themes or tikiroot/css. Which is best?
I'm thinking maybe tikiroot/themes/general/ or /global or /shared or /common etc.
fabricius: chibaguy, yes, just arrived
chibaguy: There needs to be a directory for files shared by all themes, the tiki/less files, etc.
fabricius: sorry, that I did not make it yesterday - I did not have my laptop with me and came home only more than 3 hours after the start of the webinar
ok
*thinking*
chibaguy: Is it important for tikiroot/themes to contain only theme directories as direct children?
Or can there be a "shared_files" directory in there?
fabricius: what you mean as "direct children?"
chibaguy: If it disturbs the purity, it could go in tikiroot/css instead.
fabricius: ah
chibaguy: I mean like themes/fivealive, themes/jqui, etc.
This folder would be themes/shared_files or something.
Would that be a problem? I wouldn't think so.
fabricius: actually, I can tell you my opinion and support a consensus, but the idea of purity comes from LPH ... and he said, that therer would be no tiki shared css loaded before loading themes/mythemes/tiki.css
as far as I understand it is his idea to reduce the number of loaded files massively - actually ideally to one
chibaguy: No, these files aren't to be loaded; they're the less files that are used to create the theme css files.
fabricius: ahhh
I understand
chibaguy: They just need to be somewhere, and not in styles anymore.
fabricius: by the way: that is a task for me for the next week ... I need to understand the less thingi in a way to be able to use and to explain .. my rough idea is not enough anymore
but for this it might be enough
I think, it might make sense to have them in a folder in themes with a readme file
you do not want to have them in every theme I guess?
Jesse___: joined #tikiwiki
hello
fabricius: chibaguy: maybe themes/shared_files would not the perfect name, but the right idea of a place
chibaguy: imagine, you are a new theme designer, capable of less or willing to learn
Jesse___: I have a question how do I change the picture that shows up on the website when you login on the tab by the name
fabricius: and you want to create a theme
Tiki|bot: Welcome to the official Tiki Wiki CMS Groupware channel. Please ask your question directly. Don't ask to ask. Someone will reply if and when they know the answer. Welcome again and please stay a while. Thank you!
Welcome to the official Tiki Wiki CMS Groupware channel. Please ask your question directly. Don't ask to ask. Someone will reply if and when they know the answer. Welcome again and please stay a while. Thank you!
fabricius: where you would look for the files you need to create the themes?
chibaguy: on the phone - just a minute please
fabricius: answering thi question might give us half of the answer of your previous question
ok
Hi Jesse___
Jesse___: hi fabricius
fabricius: I do not understand this Jesse___: when you login on the tab by the name
Jesse___: I have a picture of Tiki on the tab of my website when i load it in the browser
chibaguy: ok, back.
fabricius: what is the tab of your website Jesse___ ?
sorry, I am German, it might be a language problem
oh left
chibaguy: fabricius, if I were a guy wanting to make a tiki theme, I'd look for docs and look at existing themes.
fabricius: chibaguy: hehehe OBVIOUSLY a good idea :-D
-: fabricius laughing
fabricius: so that is right
chibaguy: I guess also having all the theme related files fairly close in the file tree is good, too, so probably not so good to use tikiroot/css. Actually I would like to merge the files in css into the shared theme files.
and get rid of tikiroot/css
fabricius: but honestly, don't we want a logical, easy to understand and to maintain structure?
chibaguy: I wonder if Jesse___ meant the avatar image.
Sure
Maybe themes/base_files ?
fabricius: so I tend to support your idea of themes/shared_files, whilst I am unsure about the naming ... ah base_files maybe bette ... continue thinking pls ;-)
chibaguy: I'll use that as a working title for now. It can be changed easily enough.
fabricius: base files means, that there are files (less for css creatin mainly) that affect tiki over all and that have to be used for all themes independantly from the themes itself?
like for Tiki specific selectors or css for integrated stuff from othe projects?
chibaguy: No, these files have the function that layout.css and design.css had previously; they give CSS for Tiki things that bootstrap isn't aware of.
fabricius: yeah, I did not express that in the right words
chibaguy: I suggest having a look at the files in styles/layout
fabricius: sure - Tiki things, that bootstrap isn't aware of - meant exactly this
so themes/base_files ... sound like giving the right impression
I think, LPH did put that into themes/mytheme/less
but the base files seem to make sense aswell
chibaguy: tell me something for better understanding
when you want to create a css from less, are you then kind of collecting different less files together with different files alike "his less, that less and another less" and then convert them into one single css file?
it looks to me about this way, when I see te difference of old and new css paths etc.
heh I might need to try to better express what I mean - checking dictionalry
chibaguy: Yes, there is a main less file that has import statements; when compiled, all of the files are merged into one .css file.
fabricius: ah that was what I was expecting
so you can process less files from different paths
so for example getting a free raw bootstrap theme - wrapping it together into kind of a themes-structure template and process the less including the themes/base_files/less
ready
and as the themes structure is basically the same as bootstrap, there should not be so much of a problem to integrate a rwa bootstrap theme into Tiki
chibaguy: So the theme stylesheet is now supposed to have a path like themes/jqui/css/tiki.css , for example?
fabricius: exactly
chibaguy: ok, setting up the compiler to put it in the right place.
fabricius: chibaguy: I am still thinking about the options
chibaguy: I am 100% on your side that we want to keep them
but the same time, I think they might have to work a bit differently
chibaguy: Well, there are some things that Tiki has that Bootstrap themes don't know about, an outside theme either needs to be created with Less so that it can compile Tiki's "native" less files, or more than one CSS file is needed - the external one plus a tiki one to cover the non-bootstrap rules.
Now our Bootswatch themes are almost all compiled by us again from less files, so they can include some overrides.
A few of the Bootswatch themes were only offerred as CSS files, I believe.
redflo: joined #tikiwiki
fabricius: humm - the question if eventually there will be only one single css file loaded or maybe two, would have to be discussed with Louis-Philippe and others, but not with me ...
chibaguy: To tell you the truth, the options like fivealive's were a lot of trouble to make because there are two parent themes to avoide problems with. In general I'm not sure if making a theme option makes sense any more, when you can easily accomplish the same thing by just editing some variables in the parent theme's less file.
I kind of like theme options because of the "packaging" of them in a subdirectory. It's neater than just adding more names to a long list of themes in the dropdown.
fabricius: chibaguy: indeed - I see a theme option more for the following:
chibaguy: I like how the relationship is evident.
But from a css-making standpoint, it's probably obsolete now.
fabricius: having an alternative css file in the same themes/ folder, using the same themes/mytheme/images etc.
but to create an option we now could just change variables in less and process, getting a "replacement" of the full tiki.css
I like theme options for example for accessibility funcionality
chibaguy: for people who don't want to or don't know how to use Less, the .css option files are a good solution still.
fabricius: why not something tike themes/mytheme/options/optionname.css to be loaded instead of the main theme css?
right now it is the way, that we load styles/mytheme.css and on top of it (to overwrite) styles/mytheme/options/option.css
chibaguy: Hmm, if it's going to replace the theme, why not put it in its own directory?
fabricius: the idea I am talking about is:
we load themes/mytheme/css/tiki.css
and if we chose an option, one of the following alternatives (NOT loading tiki.css
themes/mytheme/css/option.css
or
themes/mythemes/options/option.css
chibaguy: because it should use the same font, images (or most of them), js, etc and should not cause an extra workload for managing several nearly identical folders themes/mythemeoptionone/blabla themes/mythemeoptiontwo/blabla
Tiki|bot: New Forum Posts: Tracker field category no initial value (crossposting) - http://suite.tiki.org/tiki-view_forum_thread.php?forumId=26&comments_parentId=53499
New Forum Posts: Search module to search text on a specific page - http://suite.tiki.org/tiki-view_forum_thread.php?forumId=4&comments_parentId=53494
New Forum Posts: 18/09/14, Webinar - Tiki 14 release webinar (T12 and T13 version cycle) REMINDER - http://suite.tiki.org/tiki-view_forum_thread.php?forumId=26&comments_parentId=53493
fabricius: it is, when everything is nearly exactly the same, but only the tiki.css has slight differences
as far as I understand, the problem is not the idea of options as the user experiences it, but the row of Äşoading and overwritng one css after anothe
right?
chibaguy: Hmm, does this new directory structure (with font, image, etc. directories) have a lot of overhead that now you're looking for ways to work around? ;-)
fabricius: chibaguy: maybe not, if I create it by myself ... that would be quite easy and I could just name the themes /themes/theme themes/highcontrast etc. ... for a custom theme for my self abolutely no problem indeed
chibaguy: Yes, I think there's probably a way to let the theme option share the theme's directories pretty smoothly.
Tiki|bot: New Forum Posts: Tracker field category no initial value (crossposting) - http://tiki.org/tiki-view_forum_thread.php?forumId=26&comments_parentId=53499
New Forum Posts: Search module to search text on a specific page - http://tiki.org/tiki-view_forum_thread.php?forumId=4&comments_parentId=53494
New Forum Posts: 18/09/14, Webinar - Tiki 14 release webinar (T12 and T13 version cycle) REMINDER - http://tiki.org/tiki-view_forum_thread.php?forumId=26&comments_parentId=53493
fabricius: BUT what if a designer wants to ship a theme from his git account and he wants to include alternatives for certain accessibility situations or for spcific features/section/products .. like including a shop.css option, an admin dashboard, but all based on his set of files? Shall he provide 7 or 11 or 12 full themes?
AND ... all these themes folders would have to be kept in sync by either the external designer or by the Tiki devteam, whils 90% or more of the folder are meant to have the same content anyway
chibaguy: I need to think about that when I'm not so sleepy ;-) .
fabricius: what you think? Am I on a complete wrong route with my thoughts?
ok
you are right, when you think about me as a regular Tiki user - I could just copy the desired theme 20 times, slightly rename and use that as option
but we want to attract external designers and developers
chibaguy: Of course there should be as little duplication as possible. But if he is making a shop.css, is it a complete theme? or just covering one Tiki feature, and is meant to be used alongside the parent theme? He could just add the shop.css rules to the parent stylesheet.
fabricius: and make it easy to provide themes for Tiki
chibaguy: could you please specify your idea/question?
... He could just add the shop.css rules to the parent stylesheet. ... means what technically?
chibaguy: I don't know what LP has in mind for theme options. Seems like the choice is multiple files (parent stylesheet plus small option stylesheet) or multiple files (original parent stylesheet and new full-size stylesheet that was formerly an option).
fabricius: LP has in mind to seize theme options I tell you
chibaguy: I mean shop.css has some number of lines of code: CSS rules. Just put these in the parent css file instead of having a separate file.
seize: delete?
fabricius: so we want theme option and he has seized ... meaning, if we find a different way to get them, which is not conflicting his - actually right - ideas and just convince him that we need the functionality, then everything should be fine
seize = delete yes
that was the reason, why I asked Alexandre to discuss with me and explain me things ... there the idea above is coming from
and that is why I discuss so much in detail with you
chibaguy: Well, from the distribution standpoint, he's right. Why not just have a separate full stylesheet instead of a pair parent and option stylesheets to accomplish the same thing.
But from a site admin or user or non-technical person's standpoint, probably theme options still makes sense.
fabricius: do we want and need theme options and how do we get this together with LP's applicable ideas?
but chibaguy why the two perspectives must be opposing?
chibaguy: Well, I don't like the idea of themes/fivealive-orange, themes/fivealive-kiwi, etc. when almost all the contents are identical.
fabricius: why we should ship options instead of expecting site admins to process the less files themselves?
yeahh!
chibaguy: So I hope there's a way to have themes/fivealive containing the option files' components and then compiling to perhaps produce themes/fivealive/css/fivealive-orange.css etc.
Well, from the beginning I think we had in mind that not everyone would work with Less. Site admins should be able to add a theme by creating the folder in themes/
fabricius: there is one question for options: would you think it would be better to have themes/fivealive/css/fivealive-orange.css (replacing ...tiki.css) or themes/fivealive/options/fivealive-orange.css ?
chibaguy: So they'd make themes/mynewtheme/css/tiki.css with no touching of less.
fabricius: absolutely!
I mean I see that I have to learn LESS quite asap now ... really, as I must understand that to better be able to contribute in the whole process
chibaguy: or sorry, I meant maybe themes/fivealive/css/options/orange/tiki.css if that works ok to produce the right theme name in the selector.
fabricius: BUT at the same time I 100% support the idea of not punishing anybody of our existing or future users to any having to use LESS)
chibaguy: Sure, that should be an option. It's hard enough to get/make themes for tiki without putting another barrier up.
fabricius: themes/fivealive/css/options/orange/tiki.css would be maybe the best variant ... never mentioned before
actually then: themes/fivealive/css/options/orange/css/tiki.css
chibaguy: Well, there'd be a themes/fivealive/less/options/orange/tiki.less file to edit and compile, I imagine.
fabricius: yes
themes/fivealive/css/options/orange/less/tiki.css
chibaguy: Um, I don't like the repitition of css directories in that path you wrote.
fabricius: I would leave that with you ... you are the specialist on that
chibaguy: (at 18:24:28)
fabricius: ah and I looked above ... no need anyway
got your idea
chibaguy: anyway now I'm working on the paths in themes and will commit soon, so no more need for styles/
I'll leave options for a bit in the future.
fabricius: no repetition necessary, as it is inside ../less/options ../css/options .. ah
what you mean? I'll leave options for a bit in the future.
chibaguy: I mean for now I'm correcting the paths for the parent stylesheets
fabricius: ahh leave it for later
chibaguy: just a moment please - got to carry in groceries
fabricius: ok
greetings to your wife
chibaguy: She says hi
Tiki-KGB: 03chibaguy r52563 10trunk/ 10(5 files in 4 dirs)
[FIX] Move and rename former styles/layout directory and point to it in lib/setup/theme.php
03chibaguy r52564 10trunk/themes/ohia/ 10(29 files) * [KIL] Remove files incorrectly moved here.
03chibaguy r52565 10trunk/themes/ 10(19 files in 16 dirs)
[FIX] Correct paths in Less files of legacy themes and rename some for consistency.
jonnyb: joined #tikiwiki
polom for the weekend?
Tiki-KGB: 03jonnybradley r52566 10trunk/lib/userslib.php 10trunk 10trunk/lib/trackers/trackerlib.php * [MRG] Automatic merge, branches/13.x 52548 to 52558
fabricius: joined #tikiwiki
Tiki-KGB: 03chibaguy r52567 10trunk/themes/amelia/ 10css/tiki.css 10less/tiki.less * [FIX] Correct paths in Less files of Bootswatch themes.
fabricius: Hi chibaguy ... have been disconnected, sry .. anything said to me?
chibaguy: No, nothing new I think.
Bsfez: joined #tikiwiki
chibaguy: Well, Font Awesome is active by default now in trunk.
jonnyb: polom chibaguy and fabricius (and all)
chibaguy: hey jonnyb
survive the pub ok?
jonnyb: :)
actually we were in a restuarant by that stage - London pubs are too busy to even think about getting a laptop out!
really annoying it didn't connect properly, and then when it did Flash decided the webcam was being used by something else (which it wasn't) - ah well
we talked about TableSorter a lot :)
Tiki-KGB: 03chibaguy r52568 10trunk/tiki-admin.php * [FIX] Replace more glyphicons.
chibaguy: ah
Tiki-KGB: 03chibaguy r52569 10trunk/tiki-admin.php * [FIX] Replace more glyphicons.
fabricius: hi jonnyb
Tiki-KGB: 03chibaguy r52570 10trunk/lib/smarty_tiki/block.remarksbox.php * [FIX] Replace more glyphicons.
fabricius: chibaguy and jonnyb, how do you think, that mapping icons could be done in a good way (looking for a development in Tiki14 or in pre-15 trunk, if possible, so that we would get icon mapping into the 15 release)
Tiki-KGB: 03chibaguy r52571 10trunk/themes/darkroom/less/tiki-selectors.less * [FIX] Correct image path variable (testing).
jonnyb: i'm not too sure, have only been partly following the discussions i'm afraid
fabricius: there was the idea of a mapping file mentioned, but I have no clue, if that would be appropriate in respect of loading times
jonnyb: wouldn't it just be a question of adding a pref or two and modifying the {icon} smarty function?
chibaguy: fabricius, did you check the page on dev ?
um....
fabricius: jonnyb the idea was to be able to use kind of icon sets and to be free to choose svg or glyphs on a per theme base (or even more detailed)
chibaguy: I did not yet have seen news on it .. I will have a look now, it seems, that I missed recent updates on it
chibaguy: dev.tiki.org/Icons
fabricius: yes chibaguy I am on the page and realise, that I missed a lot, as I was focussing on SVG vs Fonts ... just had a (too) qick look at Icons this morning, sorry
so some of what I am bringing up now is already in discussion or even pre-desided
Tiki-KGB: 03chibaguy r52572 10trunk/themes/darkroom/less/tiki-selectors.less * [FIX] Correct image path variable (testing again, sorry).
fabricius: what do you think about that what is written on dev.t.o/Icons? I think most of the ideas have been added by gezza (edits in May from Luci and in Feb from marc)
chibaguy: Yeah, I don't know. I need to study it more.
No time today.
Tiki-KGB: 03chibaguy r52573 10trunk/ 03themes/lumen/less/lumen.less 10themes/darkroom/css/tiki.css 10themes/darkroom/less/tiki-selectors.less 10composer.lock * [FIX] Correct image path variable (testing again, sorry).
jonnyb: chibaguy: did you see Alex Q committed a console.php command less:compile?
fabricius: no problem ... just to mention: I find most of the ideas quite good. Some questions are brought up in a remarksbox, I cannot really answer. One thing I do not like so much: "- Local iconset customizations can be put to 2 places: /styles/ folder if you want it to be applied to all your themes or into the themes folder to use it only for the given theme "
jonnyb: that doesn't sound so good, fabricius - i think we should start thinking of the styles directory as deprecated and not add new stuff to it
perhaps we should have a themes/custom dir for local tweaks?
chibaguy: Right, the page info was written before styles directory became deprecated.
fabricius: exactly jonnyb, but I assume, that gezza just does not know about that and does not want to deside. I think, as how I consider him thinking, he will be supporting the idea of deprecting /styles/ in favor of /themes/ - we must give him update
but again, them the same question: 2 places for icon sets a) in themes/iconsets b) in themes/mytheme/iconset ?
does that make sense?
chibaguy: I'm sure he doesn't care if it's styles or themes directory.
fabricius: me aswell
chibaguy: Seems to me you only want one copy of an icon set.
fabricius: there is one thing, where I assume an additional /themes/iconset(s) made sense:
chibaguy: just point to it from whatever theme.
I'm not sure why every theme folder has an icons folder.
jonnyb: is there a "standard" bootstrap way of doing this?
chibaguy: yes, bootstrap has a variable that's the path the the directory.
fabricius: In case a designer wants to use an iconset that is published with a free licence, but not compatible with Tiki's LGPL, he should have the opportunity to ship the iconset from his git account included in his themes/mytheme and no need for the user to move the iconset after unzipping to /themes/
chibaguy: and also a variable for the font name, for icon font.
jonnyb: i would have thought that individual themes wouldn't all need an iconset dir, only if they want to oveerride the default ones surely?
(but actually i'm not sure what i'm talking about ;) )
chibaguy: I understand that, fabricius, but what if he wants to use it with more than one theme?
No problem, jonnyb. that never stops us ;-) .
fabricius: chibaguy: then he still can copy it to themes/iconsets
chibaguy: rrr
jonnyb: :D
fabricius: self-contained-themes does not mean that every theme supports all other themes with it's content as default for everything
it just means, that all is included that is needed for this single one
download - unzip one folder into /themes/ works
but to use parts of one extenal non-lagacy (pre-shipped) theme for other themes might always be an advanced task for an admin with server access, meaning the necessity of copying one or few files from one custom folder to an existing default folder
jonnyb: have to go for a while, bbl (and will read http://dev.tiki.org/Icons#Iconset_specification again properly when i return, looks a bit overcomplicated currently to me...)
Tiki-KGB: 03chibaguy r52574 10trunk/themes/ 10(12 files in 12 dirs) * [FIX] Correct image path variable.
chibaguy: fabricius, I understand that about self-contained themes. You might be interested that it's been possible already for a long time.
The themes at mods.tiki.org are .gz archives that, when expanded, put the files in the right places in templates and styles. Just an interesting factoid.
fabricius: really chibaguy! ... maybe some lack on information or documentation or communication ... anyway I feel, that the actual way we approach this functionality seems more obvious and more easy to handly for non-Tiki-enlighted external newbies ... and maybe less risk for wrecking stuff by this target group!?
chibaguy: Well, as far as I know, there hasn't been much interest by that target group or anyone similar.
There aren't many inquiries about doing Tiki themes, or people having technical questions about theme-making or problems understanding the file structure, etc.
So I think it's fine for us to improve the intuitiveness of the file structure, but I don't think it'll have much practical impact, really.
Just a feeling based on the little interest expressed from new people.
But I'm an optimist so am hoping that the various improvements and modernization will help make some good things happen.
Jyhem_laptop: joined #tikiwiki
chibaguy: I wonder why a theme change takes an extra page refresh in trunk.
fabricius: yes .. you need an extra page refresh to get the theme working
no idea aswell
chibaguy: the idea is to proactively getting theme designers attracted to Tiki by mentioning how easy and intuitive it is to implement themes to Tiki ... most of them might not even know about Tiki and so never come to the idea to ask about how to implement themes for our beast.
chibaguy: that's right
Tiki|bot: Recent Bug: - http://dev.tiki.org/item5468
fabricius: one of the next tasks - at least for me, but maybe to others aswell - is to find free and nice bootstrap themes and to get in contact with the designers for options to get there themes implemented to Tiki
and then we have frequent topics for annoncements and one or the other press release
but I do not yet see the development at a stage we could start this phase ... near by, but not yet there
you are one of the core people making this possible
LP aswell
another idea I have is to write some documentation about how to create a theme with LESS using Tiki as a use case
as you know, I have learned most of what I know by using Tiki as a use case and even the old system with /styles/ and options helped me a lot
it did need a LOOONG time for me to get any clue about templates, but the bootstrap approach made it necessary for me to understand the concept and some details ... I love that
actually I do not know if I would understand today without dev.t.o/Template+Tricks
so using these bits of smarty syntax in custom modules, my left-flip admin area and then the bootstrap implementation opened my eyes about templates
Tiki-KGB: 03chibaguy r52575 10trunk/ 10(5 files in 4 dirs) * [FIX] Correct path to tiki_base.css.
fabricius: if designers who are not yet using LESS, but would be interested in using it would be able to learn it with Tiki, cause we have a good documentation for it ... I think, we could attract some of them to Tiki so much, that they might stay with us
and then talking about ...
spreading the word
what you think?
Tiki|bot: Recent Bug: - http://dev.tiki.org/item5469
chibaguy: Well, one of the main reasons to be compatible with Bootstrap was that many designers already know Bootstrap and already know Less and/or Sass precompilers. So we shouldn't have to instruct them. We just need to document what is additional in Tiki. Bootstrap lifts the weight from us since there is a lot of documentation about Bootstrap themes and methods, etc. already out there.
If we have to write up lots of docs, then we're doing something wrong.
(that is, implementing Bootstrap wrong.)
What needs promoting, of course, is Tiki itself. Making themes shouldn't be an issue now.
Tiki-KGB: 03chibaguy r52576 10trunk/lib/setup/theme.php * [FIX] Correct file name in path.
chibaguy: Choosing to make them for Tiki is what people need to be convinced about.
Not only theme makers, but all kinds of developers.
Why is it so hard for someone to find a dev to make a custom plugin for their site? Everyone who knows how to do Tiki coding on that level is already busy with projects.
ah great, "base_files" shows up in the theme selector >:^/
that's the reason "themes" needs to be "pure".
nelsonko: joined #tikiwiki
fabricius: chibaguy: what about a directory /basefiles/ in Tiki root instead? there could be /basefiles/less for that you are working on and /basefiles/readme.txt with some basic documentation and links to the Tiki docs on doc.t.o and themes.t.o ?
chibaguy: I think, that right now the designers are the crucial target group ... the more interesting design we have, the more sexy websites, the more web-projects and customers could be attracted and thus more devs could be made aware about business options with Tiki - then starting to do projects with Tiki and releave the existing team ...
chibaguy: If it's in tikiroot, then it needs a more descriptive name, like theme_base_files, or css_base or something
fabricius: yes, if we need only base files for less
I believe you will figure out the right way ;-)
Tiki-KGB: 03chibaguy r52577 03trunk/themes/feb12/css/tiki.css * [NEW] Relocated compiled Feb12 theme stylesheet.
jonnyb: joined #tikiwiki
repolom
PrezKennedy: joined #tikiwiki
chibaguy_: joined #tikiwiki
nelsonko_: joined #tikiwiki
fabricius1: joined #tikiwiki
WhiteCalf: joined #tikiwiki
Tiki-KGB: 03luciash r52578 10branches/13.x/ 10templates/tiki-view_tracker_item.tpl 10tiki-view_tracker_item.php
[FIX] Tracker Comments tab doesn’t show number in parenthesis as Attachments do (ref. http://dev.tiki.org/bug5056)
luciash: polom
jonnyb: pompom luciash
luciash: hey jonny, avoiding skype today ? ;)
aalex: joined #tikiwiki
jonnyb: oops, thought it was a bit quiet! :)
SkiNut: joined #tikiwiki
olinuxx: joined #tikiwiki
ricks99: joined #tikiwiki
left #tikiwiki
Tiki-KGB: 03luciash r52579 10trunk/tiki-view_tracker_item.php 10trunk/templates/tiki-view_tracker_item.tpl 10trunk * [MRG] Automatic merge, branches/13.x 52558 to 52578
Jyhem: polom
jonnyb: hi Jyhem
-: Jyhem tries to find how to style the help pop-ups. No way I can select them with firebug :-(
jonnyb: Jyhem: try finding the div in the DOM inspector and setting the display: block
Jyhem: it looks related to class pref_dependency
Tiki|bot: New Forum Posts: Where is the auto-toc on dev.t.o? - http://tiki.org/tiki-view_forum_thread.php?forumId=26&comments_parentId=53508
Jyhem: hmm, no, maybe tikihelp
which leads to .cluetip
anyone knows what may enlarge the size of the cluetip pop-ups ?
Ahaahhh, changing var ctOptions = {…} in lib/jquery_tiki/tiki-jquery.js works as a workaround!
Strange that I found no way of doing this in CSS
Caarrie: joined #tikiwiki
chibaguy: joined #tikiwiki
Jyhem: jonnyb: I missed your message but the whole issue is, the pop-up is never under the mouse, so there was no way of "catching" it with the DOM inspector. I still don't know what DOM object it is
jonnyb: think it's just div.cluetips?
close - div#cluetip
Jyhem: Hmmm, div#cluetip{width: 800px} makes no difference. Nevermind, I can read the cluetips now, and I went ahead to the real issue I was tasked to solve
It's amazing how many people actually ask to have some object types removed from the search
jonnyb: :)
Jyhem: do you know about the github repo?
Jyhem: But «only search articles, pages wiki & blog unless in groups admin or subadmin, who search for all» is kind of non-generic :-)
jonnyb: yes and no. I heard about its existence but I never went to look
jonnyb: ok, it's actually a phpstorm thing i think, it doesn't seem to have noticed 13.x is there upstream...
Jyhem: You mean the github repo is missing Tiki13 ?
Telesight: joined #tikiwiki
jonnyb: sorry Jyhem - no, github has it ok but it's not showing up in my phpstorm project... not to worry, but thanks for asking :)
going to go get food etc now, see you later/tomorrow/whenever
jonnyb_: joined #tikiwiki
fabricius: joined #tikiwiki
fcpd: joined #tikiwiki
tikiwiki 12.2: Would like to hire someone to make my existing tracker automatically create a wiki page from the first field item entered. Also need to get an explanation of the multiselect feature. $50USD via Paypal. I have other small stuff as well if anyone on here is interested.
Telesight: joined #tikiwiki
redflo: joined #tikiwiki
chibaguy: joined #tikiwiki
rob____: joined #tikiwiki
I have a question before downloading installing and learning tiki
Tiki|bot: Welcome to the official Tiki Wiki CMS Groupware channel. Please ask your question directly. Don't ask to ask. Someone will reply if and when they know the answer. Welcome again and please stay a while. Thank you!
Welcome to the official Tiki Wiki CMS Groupware channel. Please ask your question directly. Don't ask to ask. Someone will reply if and when they know the answer. Welcome again and please stay a while. Thank you!
fcpd: @Rob: If I can answer it I will. I am not a programmer but have played around since the 3.x days
AFK 2minutes
luciash: Jyhem: I can confirm that... client wanted all removed from search, categories and freetags except wiki, blogs and forum results here too
Jyhem: I guess making it preferences in Search admin panel would make sense at some point
fabricius: Hello, I have an important question to you devs. And on that base I will deside, if I will use your software. I will disappear in less than 120 seconds, so hurry up to convince me. GO!
luciash: LOL
Jyhem: luciash: just found time for watching yesterday's BBC video on former president Klaus. Too late, I know, but thanks all the same. Still interesting.