| ../irclogs/#mantishelp.2010-06-09.log | ||
| --- scribe started --- | 00:00 | |
| WaterRatj | Anyone online right now? | 01:15 |
|---|---|---|
| daryn | nuclear_eclipse around? | 04:41 |
| dhx_m | daryn: hi :) | 04:42 |
| daryn | hello | 04:42 |
| daryn | filters are almost done | 04:42 |
| daryn | :) | 04:42 |
| dhx_m | what is changing this time? :) | 04:43 |
| daryn | everything | 04:43 |
| dhx_m | I haven't been following discussions here for ~2 weeks | 04:43 |
| daryn | actually there haven't been many discussions | 04:43 |
| daryn | mostly quiet | 04:43 |
| dhx_m | so it's a rewrite? | 04:44 |
| daryn | ya | 04:44 |
| daryn | classes | 04:44 |
| dhx_m | nice :) | 04:44 |
| daryn | each field has it's own class | 04:44 |
| dhx_m | ohhhh yes :) | 04:44 |
| dhx_m | that is something I really wanted to see happen | 04:44 |
| daryn | filter api is gone | 04:44 |
| dhx_m | so built-in fields use the same classes as custom fields? | 04:44 |
| daryn | mmm...sort of yeah | 04:45 |
| daryn | i guess so | 04:45 |
| dhx_m | do field classes extend each other? | 04:45 |
| daryn | yes | 04:45 |
| dhx_m | and I guess plugins could extend a field class to create new types? | 04:45 |
| daryn | yep | 04:45 |
| dhx_m | is custom_field_api redone? | 04:46 |
| dhx_m | *hopes so... it sucked :p* | 04:46 |
| daryn | no, that's later | 04:46 |
| daryn | but i do have ideas for it | 04:46 |
| daryn | these field classes are strictly filter right now | 04:47 |
| dhx_m | so the plan isn't for the Bug class to contain a number of Field subclasses just yet? | 04:48 |
| dhx_m | I guess that would require a rewrite of the entire app | 04:48 |
| daryn | no | 04:48 |
| daryn | right. just trying to get filters done | 04:49 |
| daryn | was unbelievable really | 04:49 |
| daryn | so ridiculously complex and redundant | 04:49 |
| dhx_m | 168kb | 04:52 |
| daryn | filter api? | 04:52 |
| dhx_m | the old one, yeah | 04:52 |
| daryn | 0 now :) | 04:53 |
| dhx_m | where did it all go? :p | 04:53 |
| daryn | of course it's spread over multiple files now | 04:53 |
| dhx_m | yep | 04:53 |
| daryn | MantisBugFilter, and then field classes | 04:53 |
| dhx_m | let me know if you push it to mantisforge :) | 04:53 |
| dhx_m | (if mforge is even working :p) | 04:53 |
| daryn | yeah, i keep telling john just another couple of days...heh | 04:53 |
| daryn | but it really is almost there now | 04:54 |
| daryn | plus jquery datepicker's | 04:54 |
| dhx_m | what is the fallback? | 04:55 |
| daryn | just textbox | 04:55 |
| daryn | removed the stupid Filter by date checkbox | 04:55 |
| dhx_m | yep | 04:56 |
| dhx_m | the "Sort by" fields are currently stupid too | 04:57 |
| daryn | oh you'll love my fixes for that | 04:57 |
| daryn | well...maybe | 04:57 |
| dhx_m | :) | 04:57 |
| daryn | actually...i just made them work and removed the limit of two | 04:57 |
| dhx_m | nice | 04:57 |
| daryn | did you have a thought for sort ui? | 04:58 |
| dhx_m | I sort of like the Mantis approach because it's so simple and fast to use | 04:58 |
| dhx_m | but I guess the most commonly used UI for filtering is one where you click a button to add a new filter to the list | 04:59 |
| dhx_m | so in effect you're chaining conditions together | 04:59 |
| dhx_m | afaik Redmine does that | 04:59 |
| dhx_m | Trac too | 04:59 |
| dhx_m | but I imagine they all rely upon Javascript | 05:00 |
| daryn | yeah, the filters rely on javascript alot anyway | 05:00 |
| daryn | i mean, they'll work without but it's really ugly | 05:00 |
| dhx_m | yep | 05:01 |
| daryn | i'm going to commit with the current layout initially but i've separated the logic and template and i'm working on a couple of possibilities for nicer layout | 05:02 |
| daryn | customizable too | 05:02 |
| daryn | include only the fields you want, etc. | 05:02 |
| dhx_m | yep | 05:03 |
| dhx_m | I was looking into WebSockets recently as a replacement to AJAX | 05:03 |
| daryn | yeah? | 05:03 |
| daryn | jquery ajax is so easy though... | 05:04 |
| dhx_m | yep I think we should stick with jQuery as much as possible | 05:04 |
| dhx_m | although WebSockets is different AFAIK because it allows push notifications | 05:04 |
| daryn | all the filter stuff is moved over to jquery | 05:05 |
| daryn | working on collapse too | 05:05 |
| daryn | mainly because it affects filters | 05:05 |
| daryn | and is fairly esy | 05:05 |
| daryn | easy | 05:05 |
| dhx_m | actually now I think about it, WebSockets push notifications aren't going to be very useful :) | 05:06 |
| daryn | i don't know anything about it | 05:07 |
| dhx_m | and it's hard to create a usable UI when things are changing/being inserted on the screen in real time | 05:07 |
| daryn | yeah that could be annoying | 05:07 |
| daryn | depends though | 05:07 |
| dhx_m | well I think the idea is that if you're using gmail and you're viewing your inbox, new emails are inserted at the top of the list as they arrive | 05:07 |
| daryn | right, that would maybe be nice for bugs as long as they fit the current filter | 05:08 |
| dhx_m | basically people are reinventing the wheel and trying to create native desktop apps within the browser :p | 05:08 |
| daryn | yeah, cuz desktops are going away heh | 05:08 |
| dhx_m | perhaps... but if you were just about to click on an issue in the list and suddenly another one appeared, dropping them all down the screen... so your click misses the mark... ugh | 05:08 |
| daryn | ya | 05:09 |
| dhx_m | I just find sites relying upon JS very hard to use from a usability standpoint | 05:14 |
| dhx_m | I guess using jQuery fixes many of those issues | 05:14 |
| daryn | yeah, it's all in the design. javascript should enhance only | 05:15 |
| bruno_bruno | is there any way to disable the roadmap and change log links? | 18:02 |
| bruno_bruno | i don`t want them to be shown | 18:02 |
| nuclear_eclipse | bruno_bruno: set the view_roadmap_threshold|view_changelog_threshold config settings to NOBODY | 19:01 |
| bruno_bruno | thanks | 19:07 |
| bruno_bruno | it didn`t work ;/ | 19:10 |
| bruno_bruno | i do it in the config file? | 19:11 |
| bruno_bruno | $view_changelog_threshold = NOBODY; | 19:11 |
| nuclear_eclipse | bruno_bruno: $g_view_changelog_threshold | 19:23 |
| bruno_bruno | the changelog worked | 19:24 |
| bruno_bruno | but the same thing for roadmap didn`t work | 19:24 |
| bruno_bruno | $g_view_roadmap_threshold = NOBODY; | 19:24 |
| nuclear_eclipse | grr, it's $g_roadmap_view_threshold ... =\ | 19:25 |
| nuclear_eclipse | inconsistent | 19:25 |
| bruno_bruno | weird | 19:25 |
| bruno_bruno | thanks, sorry for bothering you | 19:26 |
| nuclear_eclipse | np | 19:26 |
| minimoo | nuclear_eclipse: CMS: drupal, joomla, any others? | 19:28 |
| nuclear_eclipse | there are lots of them | 19:37 |
| minimoo | good ones :P | 19:37 |
| nuclear_eclipse | Wordpress is technically a CMS as well, just focused around a blog | 19:37 |
| nuclear_eclipse | if you're not set on PHP, there are a few good ones in Python and such | 19:38 |
| minimoo | i'm after good atm | 19:38 |
| nuclear_eclipse | but tbh, I wouldn't really consider many of them to be "good" :P | 19:38 |
| minimoo | so dont care what | 19:38 |
| minimoo | it's probably php | 19:38 |
| minimoo | but | 19:38 |
| minimoo | someone wants something for hockey club | 19:38 |
| minimoo | I suggest drupal | 19:38 |
| minimoo | +ed | 19:38 |
| minimoo | (as joomla seemed complicated to use) | 19:38 |
| nuclear_eclipse | drupal is probably the best starting place for anything small | 19:38 |
| minimoo | iirc drupal was easy to use? | 19:39 |
| nuclear_eclipse | more or less | 19:39 |
| nuclear_eclipse | my biggest complaint with Drupal was that it was very resource intensive, and had a bit too much inherent complexity in the database and system design | 19:40 |
| nuclear_eclipse | eg, the "everything is a node" paradigm is a bit frustrating at times | 19:40 |
| nuclear_eclipse | the database quickly becomes a huge bottleneck with drupal installs | 19:41 |
| nuclear_eclipse | enough so that I migrated *back* to wordpress after about 6-8 months on drupal | 19:42 |
| nuclear_eclipse | but I've ditched wordpress these days too | 19:42 |
| nuclear_eclipse | now I just use a static site generator | 19:42 |
| nuclear_eclipse | the only "dynamic" parts of my site are mantis and mail tools | 19:43 |
| minimoo | mmmmmmm | 19:44 |
| minimoo | joomla ? | 19:44 |
| nuclear_eclipse | I agree with you on Joomla, i couldnt ever get past the inital setup phase without getting completely lost and have a big headache | 19:44 |
| minimoo | I'd like to suggest something for work person to use for hockey club | 19:46 |
| minimoo | that's easy to use | 19:46 |
| nuclear_eclipse | well, a real CMS is inherently "not easy" :P | 19:47 |
| nuclear_eclipse | the question is really what do they want from it? a forum? | 19:47 |
| nuclear_eclipse | or just an info board? | 19:48 |
| nuclear_eclipse | it might be best to just give them something like wordpress or phpbb3 and leave it at that | 19:48 |
| minimoo | does debian not havbe build essentials | 19:49 |
| minimoo | more a website | 19:49 |
| nuclear_eclipse | or even something like MediaWiki might be a good solution | 19:49 |
| nuclear_eclipse | if they just want a website that's easy to update, point them at http://weebly.com | 19:49 |
| minimoo | mm | 19:49 |
| minimoo | they've got hosting from a member | 19:50 |
| minimoo | and static pages atm | 19:50 |
| minimoo | but want to allow otheres in club to be able to edit basically | 19:50 |
| nuclear_eclipse | so, mediawikisounds like a good solution | 19:51 |
| nuclear_eclipse | just make the wiki require special access to edit pages | 19:51 |
| nuclear_eclipse | and turn off user registration | 19:51 |
| nuclear_eclipse | and/or | 19:51 |
| minimoo | can you theme it though? | 19:51 |
| nuclear_eclipse | yeah, there should be a decent amount of free themes available, or at least a starting point for someone to customize the skin | 19:53 |
| nuclear_eclipse | wordpress is probably also a decent solution, just configure it to not use the blog portion | 19:54 |
| nuclear_eclipse | that's what I used for my portfolio site | 19:54 |
| nuclear_eclipse | if you're set on needing a full CMS though, I've also heard e107 as an alternative | 19:56 |
| minimoo | someone suggetsed typo3 | 19:56 |
| nuclear_eclipse | yeah, that was my next suggestion | 19:56 |
| minimoo | are either of those fairly 'modern' aka any ajax stuff | 19:57 |
| nuclear_eclipse | but that runs on ruby, so I have no clue how easy it would be to set up or deploy | 19:57 |
| nuclear_eclipse | no clue regarding ajax, but imo that shouldn't really matter | 19:57 |
| minimoo | ruby is typo3 or e106? | 19:58 |
| nuclear_eclipse | typo is ruby, e107 is php | 19:58 |
| minimoo | http://www.php-fusion.co.uk/news.php | 20:01 |
| minimoo | heard of that? | 20:02 |
| nuclear_eclipse | heard of it, never used it | 20:02 |
| nuclear_eclipse | it's a fork of phpnuke iirc, and I never liked that one | 20:02 |
| * minimoo might just try http://ez.no/download | 20:10 | |
| nuclear_eclipse | I still think Weebly would be exactly what they need/want for the site -- if they want multiple editors, then just share a login? | 20:17 |
| minimoo | they have a box for it | 20:17 |
| minimoo | or well | 20:17 |
| minimoo | someone hosts site for them | 20:17 |
| nuclear_eclipse | well, I'm thinking more the interface on weebly is extremely simplified for those who don't understand anything about web development or cms design | 20:18 |
| nuclear_eclipse | I set up my father's site to use weebly, and he likes it a lot because he doesn't have to use some crappy TinyMCE-like editor, or worry about dealing with images and such, like when I tried setting him up with Wordpress or other similar apps | 20:19 |
| WaterRatj | Anyone here? | 22:38 |
Generated by irclog2html.py