| # | Time | Nick | Message |
|---|
| # | 00:34:05 | www has quit IRC |
| # | 03:37:43 | mrpeters-isl has quit IRC |
| # | 08:12:59 | bjwebb has joined #evergreen |
| # | 08:12:59 | bjwebb has joined #evergreen |
| # | 11:15:25 | bjwebb has quit IRC |
| # | 11:29:54 | artunit has quit IRC |
| # | 11:37:11 | artunit has joined #evergreen |
| # | 12:02:25 | moodaepo_ has joined #evergreen |
| # | 12:51:02 | bjwebb has joined #evergreen |
| # | 12:58:11 | rsinger has quit IRC |
| # | 13:45:40 | bjwebb has quit IRC |
| # | 14:36:57 | chirag has joined #evergreen |
| # | 14:44:44 | tsbere | Anyone around to solicit an opinion from? |
| # | 14:48:47 | phasefx is here |
| # | 14:49:46 | tsbere | Any thoughts on whether I should strive to keep the current toolbar (or close to it) as the default, compared to just doing my "upgrade" to it and calling it the circ toolbar (instead of making a copy and upgrading the copy)? |
| # | 14:50:16 | tsbere | The CSS changes get complicated if I can keeping the original due to the icons over the label bit that needs to be done to the buttons when I start adding mini-menus to them. |
| # | 14:50:38 | yboston has joined #evergreen |
| # | 14:51:03 | tsbere | s/can keeping/am keeping/ |
| # | 14:53:35 | phasefx | if it's easier for you to re-implement things, I say go for it. It was an unmandated feature, an itch I scratched, though folk apparently like it. I'm not beholden to how it works |
| # | 14:54:13 | phasefx | at least, I think that's what you're asking :) |
| # | 14:55:17 | tsbere | Basically, using this as an example: http://bstcon.com/toolbars.jpg Do you think there will be massive outcry at the sudden more vertial label arrangement on the existing toolbar compared to the current one? |
| # | 14:56:07 | tsbere made that by manually applying style= attributes |
| # | 14:56:15 | tsbere doesn't want to do that for the real one |
| # | 14:57:06 | phasefx wouldn't expect an outcry. Can we convert labels to tooltips via a setting? |
| # | 14:57:34 | tsbere | Not easily. But I can make the labels go away without them being tooltips easily, and can add tooltips easily regardless of the labels. |
| # | 14:57:54 | phasefx | (or better, always have tooltips, but just make the labels toggle-able) |
| # | 14:57:55 | phasefx | right |
| # | 14:58:17 | tsbere | I can also make the icons go away |
| # | 14:58:55 | phasefx | you have my vote to carry-forth, fwiw |
| # | 14:59:09 | tsbere | I was planning on icons/label/both options |
| # | 14:59:11 | phasefx | though I do like the text on the right :) |
| # | 14:59:37 | tsbere | The menus with a dropdown auto-vertical the text. I might be able to reverse that, but my first tries didn't work. |
| # | 15:00:48 | tsbere looks at his previous attempts |
| # | 15:00:59 | tsbere | Ok, may be I should try again without a mis-spelled "horizontal" >_> |
| # | 15:01:57 | tsbere | Hey, without a mis-spelling in the CSS it looks to work. Should I make that a toggle option? |
| # | 15:03:33 | phasefx | why not? someone is supposed to be bringing sanity to our config settings :) |
| # | 15:04:56 | tsbere | Half of this I think I am throwing in the general area of workstation level, rather than org unit level. |
| # | 15:05:30 | tsbere | If only because I expect it to be more of a "what do you do with the computer" thing rather than anything else |
| # | 15:06:06 | bshum | Except when folks need to share the same computer. Hmm |
| # | 15:06:31 | phasefx | you'd think a comsetic change like that wouldn't rattle people though |
| # | 15:06:45 | bjwebb has joined #evergreen |
| # | 15:07:09 | bshum | Text alignment? Probably not so long as it brought something new to the table, which this will. |
| # | 15:07:16 | tsbere | I was thinking more "most toolbar options in general, including which one to show (if any), but let the org unit setting decide a default if there is no other setting" |
| # | 15:07:37 | phasefx | there's an alternative... we could have the settings be saved locally, but allow for a "remote settings directory", similar to a feature we use for column settings |
| # | 15:07:56 | phasefx | could be the same feature, just made more generic |
| # | 15:08:23 | tsbere | That done with user settings? |
| # | 15:08:34 | tsbere | Or something else I haven't seen yet? |
| # | 15:08:59 | phasefx | org unit setting, url.remote_column_settings |
| # | 15:09:09 | phasefx | GUI: URL for remote directory containing list column settings. The format and naming convention for the files found in this directory match those in the local settings directory for a given workstation. An administrator could create the desired settings locally and then copy all the tree_columns_for_* files to the remote directory. |
| # | 15:09:57 | tsbere | Yea.....sounds complicated to write up. |
| # | 15:10:05 | phasefx | was a quick & dirty way of getting what they wanted |
| # | 15:10:31 | phasefx | they also lock down their columns so staff can't (permanently) change them |
| # | 15:11:49 | tsbere | Don't suppose we have any way of making an org unit setting an object (easily, anyway)? |
| # | 15:11:57 | bshum | tsbere: Curious, long term strategy with changing the text to underneath the icon is just so that it's easier to add new buttons to the toolbar in customized ways, right? |
| # | 15:12:26 | phasefx | but we could have anything that reads from the local file system (with the exception of anything dealing with offline mode) look for such a remote directory first. If a file isn't there, then proceed to local directory |
| # | 15:12:44 | tsbere | bshum: Since I noted I was mis-spelling "horizontal" I can set text beside and text below regardless of submenu things. |
| # | 15:12:49 | bshum | I *do* worry about the altered direction, people freak out enough at our libraries at the slightest disturbance, it seems. |
| # | 15:13:05 | bshum | tsbere: Oh, well. Okay, then. |
| # | 15:13:18 | phasefx | tsbere: there's at least one case of us using a string containing JSON (and I ended up making a dedicated interface for setting it. no easy object support in Library Settings UI) |
| # | 15:13:34 | tsbere | phasefx: Which one is that? |
| # | 15:13:56 | phasefx | tsbere: circ.staff_client.do_not_auto_attempt_print |
| # | 15:14:21 | tsbere | Ahh, that one. |
| # | 15:14:32 | phasefx | all the printing stuff is horribly complicated now |
| # | 15:15:47 | tsbere | At this point I have the toolbar, the text position (side or bottom), the icon size, whether to show the text, the icons, or both............ |
| # | 15:15:52 | tsbere | Lots of settings if split apart |
| # | 15:16:24 | tsbere | For user setting (if I put it there) I just dump it all in, who cares, and say it isn't opac visible. For org unit setting.... |
| # | 15:18:55 | phasefx | yeah, I say stay away from org unit settings for now. If folks want to specify good defaults, maybe could let it be via custom.js or something. |
| # | 15:19:31 | tsbere | I figure the only org unit setting will be which button bar to show. Which will replace the current true/false setting. |
| # | 15:19:50 | phasefx | or (and this sounds horrible and interesting), maybe an org setting for pointing to a specific user, and use their settings :) |
| # | 15:20:02 | tsbere | horrible yet insteresting....yea. |
| # | 15:20:19 | phasefx | s/stay away from org unit settings/stay away from objects in org unit settings/ |
| # | 15:20:56 | tsbere | I have another project that I don't know how I should implement that would benefit from object in org unit setting too. >_> |
| # | 15:21:12 | phasefx | with Evergreen, we try to stay away from "fake" records.. a "settings" user would probably be another fake record |
| # | 15:22:20 | phasefx | tsbere: maybe a flag to prevent such settings from showing up in Library Settings until we get a plugin-infrastructure for custom widgets to set them |
| # | 15:22:31 | phasefx | s/flag/datatype = object/ |
| # | 15:22:58 | phasefx | or if not prevent, then warn off, hide |
| # | 15:26:34 | tsbere | Hiding them would be really easy |
| # | 15:26:42 | tsbere | One line to one javascript file, I think |
| # | 15:27:27 | phasefx | or, maybe allow them, but with a big textarea widget |
| # | 15:27:30 | tsbere tests it, finds it works |
| # | 15:27:47 | tsbere | One line = they stop showing up. Making them appear as fully editable text.....may be harder. |
| # | 15:28:19 | phasefx | we already let folks edit a/t templates |
| # | 15:28:32 | tsbere | (our test systems have a custom object org unit setting type for the moment, so I am testing with that one) |
| # | 15:28:56 | phasefx | tsbere: if we do the big textarea widget, would probably be good to do a JSON2js test for validation, as well |
| # | 15:36:06 | phasefx has to head out *waves* |
| # | 15:37:59 | csharp | bshum: re: library staff freakouts at slightest disturbance - either they'll get used to it, or you will ;-) |
| # | 15:43:22 | chirag has quit IRC |
| # | 15:47:08 | yboston | Quick question: doing a clean install of EG 2.5 for a test VM, should I go for Postgres 9.0 or stick to 8.4? |
| # | 15:47:22 | bjwebb has quit IRC |
| # | 15:50:40 | tsbere | yboston: I have no clue. What time machine did you use to get 2.5? ;) |
| # | 15:50:53 | tsbere | (I assume you mean 2.0.5, in which case I think either works) |
| # | 15:50:55 | yboston | oops, 2.05 |
| # | 15:52:15 | yboston | tsbere: thanks for your help |
| # | 15:55:08 | rsinger has joined #evergreen |
| # | 16:01:01 | bshum | csharp: That sounds like my future. |
| # | 16:02:27 | bshum | yboston: imo, doesn't hurt to take PG 9.0 for a walk, but it's not absolutely necessary with a 2.0.x release to use that version. |
| # | 16:03:17 | yboston | bshum: thank you for your tip |
| # | 16:03:22 | bshum | yboston: If you do go down the route with PG 9.0, I think a few of us would be most interested to hear how you fare. That's one of my next projects is to start tackling 9.0 |
| # | 16:03:35 | yboston | bshum++ |
| # | 16:04:58 | bshum | But most of my exploration would be intended with 2.1 testing in mind, rather than 2.0. I think moodaepo is doing some stuff with testing 2.0 stable with PG 9.0 though, so maybe he might know more about that. |
| # | 16:05:03 | bshum | yboston: Good luck! :) |
| # | 16:06:08 | yboston | bshum: thanks |
| # | 16:06:28 | moodaepo_ | yboston: I have found no issues (yet) with using 9.0 with 2.0.5 |
| # | 16:07:14 | yboston | moodeapo: good to know, thanks. |
| # | 16:10:19 | moodaepo_ | I can't seem to figure out what the hex code is for the green used on the blog > http://evergreen-ils.org/blog/ (help) |
| # | 16:11:05 | bshum | Hmm |
| # | 16:12:23 | bshum | upper=58C699&lower=379C70 |
| # | 16:12:55 | bshum | Guess it's a gradient of some kind |
| # | 16:13:04 | bshum | http://evergreen-ils.org/blog/wp-content/themes/default/images/header-img.php?upper=58C699&lower=379C70 |
| # | 16:18:08 | moodaepo_ | bshum: Nope that didn't seem to do the trick (I'd tried it earlier but gave it another go) > http://lupin.georgialibraries.org/blog/ |
| # | 16:23:17 | penni has joined #evergreen |
| # | 16:23:41 | penni | i have a troubleshooting issue. i am hoping someone might be able to help me. |
| # | 16:25:21 | moodaepo_ | penni: Ask away |
| # | 16:25:54 | bshum | moodaepo_: So wait, http://www.color-hex.com/color/58c699 and http://www.color-hex.com/color/379C70 don't show up as green to you? |
| # | 16:26:18 | bshum | moodaepo_: (asking cause that link to lupin is... blue?) |
| # | 16:26:44 | penni | since the recent upgrade/update to Evergreen/Pines I have not been able to login via Google Chrome, as I was able to do so before. I can only use Firefox which I have to reload everypage |
| # | 16:27:07 | moodaepo_ | bshum: Interesting I cleared cache after i tried those...will try again. |
| # | 16:27:35 | moodaepo_ | penni: That can be annoying, could you provide a link? |
| # | 16:27:47 | penni | to what |
| # | 16:27:53 | moodaepo_ | csharp: ^^ |
| # | 16:28:29 | moodaepo_ | penni: To the site you are trying to use. |
| # | 16:28:53 | moodaepo_ | I'm guessing this is to your account information, right? |
| # | 16:29:02 | penni | http://gapines.org/opac/en-US/skin/default/xml/index.xml |
| # | 16:29:34 | bshum | It's possible that it's a cache issue. I know we had that for awhile after going from 1.6 to 2.0 where all our pages came up... broken. |
| # | 16:29:42 | bshum | Till clearing cache or hitting refresh on each page type |
| # | 16:30:14 | moodaepo_ | penni: ^^ |
| # | 16:31:14 | penni | the page works but I can't log into my account so that I can check the status of my book reserves, and due dates. it gives me a weird message. Firefox does not but I have to refresh constantly which is annoying |
| # | 16:32:44 | moodaepo_ | Well try clearing your cache as bshum suggested (or have you tried it already?) |
| # | 16:35:19 | moodaepo_ | penni: What weird message do you get? |
| # | 16:37:06 | penni | It is working now. What happened? LOL |
| # | 16:38:26 | penni | Well now that apparently that problem is fixed, I do have another one. It is a library account and you can have your reserves/holds request sent to your email or via phone or both when they arrive. I have just email and I havent' gotten email since the update. |
| # | 16:39:39 | bshum | It's possible that PINES is still getting their upgrade worked out. |
| # | 16:40:04 | moodaepo_ | penni: Also it's possible the items you placed holds on have not been returned yet? |
| # | 16:40:06 | tsbere | penni: I have seen that happen (as a complaint) before. The person in question had yet to have anything attempt to contact them, and thus had no emails to receive. Are you sure you should have gotten one? |
| # | 16:42:37 | yboston has quit IRC |
| # | 16:42:58 | penni has quit IRC |
| # | 16:44:36 | penni has joined #evergreen |
| # | 16:44:43 | penni | i have to reload. |
| # | 16:45:06 | penni | to reiterate, I do have books available for pickup b/.c my HOLDS SHELF says "READY FOR PICKUP" on two |
| # | 16:45:38 | penni | Plus the day of the upgrade, I had a few, but I didn't let it bother or worry me that I didn't get the email b/c it the system was being upgraded |
| # | 16:48:09 | moodaepo_ | penni: Yea they may still be under the upgrade cloud check back tomorrow(?) |
| # | 16:48:53 | penni | OK. Thank you for your help! :-) |
| # | 16:49:04 | moodaepo_ | penni: I'd mention it to your local library it might not be just you. |
| # | 16:49:31 | penni | I did, but I will do so again. |
| # | 16:50:20 | moodaepo_ | penni: Feel free to drop by maybe one of us might hear something. |
| # | 16:50:43 | penni | OK. Will do. Thanks again. |
| # | 16:52:31 | penni has quit IRC |
| # | 16:53:00 | tsbere has decided to be lazy on a graphical front and only make 32x32 and 16x16 toolbar button icon variants, if only because one of the current toolbar buttons was already made up custom and thus it will be easier to shrink it than to grow it |
| # | 16:56:28 | bshum whistles in the corner |
| # | 16:59:24 | tsbere | bshum: If you want bigger icons, provide me with a 40x40 pixel version of the search items icon that looks good. ;) |
| # | 16:59:37 | tsbere | (or if you want REALLY big, I suppose you could provide me with larger) |
| # | 16:59:53 | bjwebb has joined #evergreen |
| # | 17:01:37 | bshum | tsbere: I was whistling because I knew our icon wasn't very nice. I could ask Meliss (who made the icon) if we can make one that's 40x40 |
| # | 17:01:54 | bshum | tsbere: Probably won't get done till after the conference though. |
| # | 17:02:01 | tsbere | bshum: It is nice enough. But I don't feel like re-making it at higher res right now ;) |
| # | 17:02:45 | tsbere has access to the higher-res source images and all |
| # | 17:03:18 | tsbere | But 32x32->16x16 is easy when you have the 32x32 |
| # | 17:03:29 | bshum | No doubt. |
| # | 17:15:01 | bshum | jamesrf++ sitka++ #consider me +1 to getting a cool frog image someday :) |
| # | 17:44:13 | StephenGWills has quit IRC |
| # | 17:47:55 | moodaepo_ | WordPress and DokuWiki migration/data refresh information updated > http://evergreen-ils.org/dokuwiki/doku.php?id=website_migration |
| # | 17:49:10 | tsbere | moodaepo_: Should we link to https://github.com/zoranzaric/dokuwiki-git-plugin after the "tsbere thinks" part? Tis for dokuwiki and git, but would be easily adapted (I think) to svn if needed. |
| # | 17:49:39 | moodaepo_ | tsbere++ # Do it! |
| # | 17:50:22 | moodaepo_ | csharp: Need to make sure pinesol_new is set to run on boot, if you could take care of it I think we just need to set the date of transfer. Well we could test things out more but I feel the transition is coming close. |
| # | 17:51:18 | moodaepo_ | There is also the todo - checking for bad links and such but I don't see that happening soon and can always be tackled after moving over. |
| # | 17:52:33 | tsbere | moodaepo_: Added a line. |
| # | 18:24:47 | moodaepo_ has quit IRC |
| # | 18:33:46 | bjwebb has quit IRC |
| # | 18:57:16 | bjwebb has joined #evergreen |
| # | 19:14:20 | moodaepo_ has joined #evergreen |
| # | 19:24:10 | moodaepo_ wonders if we have a client for prealpha2 out? |
| # | 19:30:21 | tsbere hates making icons |
| # | 19:30:50 | tsbere | Found some suitable ones for a toolbar button I wanted to make in the open icon library, but I need to do some modifications. >_> |
| # | 19:32:00 | tsbere | Photoshop stinks for this. And no svg source. >_> |
| # | 19:38:36 | bshum | moodaepo_ : making a 2.1 client is different, not sure if one has been made for prealpha2 yet, but I doubt it. |
| # | 19:46:29 | tsbere offers to help anyone trying, though. Or, potentially, to just make them. |
| # | 19:58:05 | moodaepo_ | bshum: Just checking thanks..and tsbere++ If you could write up a set of steps I can take over after the first one (can't promise yours or bshum's lightening fast turn around though : ) |
| # | 20:06:36 | phasefx | we could try to get some svg icons, scalable |
| # | 20:07:42 | phasefx is not saying anything new, he realizes |
| # | 20:09:44 | tsbere | phasefx: I am creating a new toolbar button, previously unmentioned. Requires 8 potential states (4 states, 2 icon sizes). PITA. |
| # | 20:10:57 | tsbere | moodaepo_: Make branding folder, copy appropriate icon into it as evergreen.ico, copy appropriate stub exe to xulrunner_stub.exe in staff_client folder, make STAFF_CLIENT_STAMP_ID=whatever build, make win-client. I think. |
| # | 20:11:16 | tsbere | Oh, after having nsis and zip around ;) |
| # | 20:12:33 | moodaepo_ | tsbere: I might try my hand at it tomorrow plan on installing 2.1-prealpha this week. Will probably bug bshum. |
| # | 20:13:05 | tsbere | moodaepo_: I am the one who rigged up this entire new method. If I am around I may be the better person to ask questions ;) |
| # | 20:13:29 | moodaepo_ | tsbere: Will do. |
| # | 20:19:27 | bshum | AHA |
| # | 20:19:34 | bshum | Oops, wrong place :) |
| # | 20:20:49 | tsbere | Yay! I have (for the original toolbar plus one button) icons that can be two sizes and "grey out" when disabled! |
| # | 20:21:14 | tsbere | (not that I expect much greying out, but I prefer that things work properly if someone does disable commands) |
| # | 20:23:03 | moodaepo_ | tsbere++ |
| # | 20:23:52 | tsbere | My new button is a toggle hotkeys button. When you click on it the icon swaps to having a red x and the button stays in. Click it again and the button pops out and loses the x. When the button is in hotkeys don't work. |
| # | 20:37:12 | eeevil | tsbere: you'd mentioned another file I should be adjusting with version numbers for releases ... I didn't for PA2 ... remind me tomorrow for my notes? |
| # | 20:37:57 | tsbere | Open-ILS/xul/staff_client/windowssetup.nsi |
| # | 20:38:18 | tsbere | eeevil: I believe I made it easier recently, there is a product tag that is "Trunk" in trunk. |
| # | 20:38:56 | tsbere needs to figure out how to make different tagged versions not try and use the same install dir, though |
| # | 20:39:19 | tsbere | Works fine until you have one installed. Then the others try and use the same folder. |
| # | 20:40:00 | tsbere probably needs to pick a better PRODUCT_DIR_REGKEY |
| # | 20:44:46 | phasefx | do we think it should be branch specific, not tag specific, the folder the installer tries to use? i.e. all 2.1.x releases would go into an EG 2.1 folder by default, 2.2.x releases into an EG 2.2 folder? |
| # | 20:45:15 | tsbere | With the current way the installer builds itself it will use the same folder as the previous NSIS installer attempt every time. |
| # | 20:45:39 | tsbere | Unless you uninstall manually, then start the installer. Then it will re-pick folders. |
| # | 20:45:52 | phasefx | hrmm, I didn't think that was true |
| # | 20:46:22 | phasefx | but I've been doing updates for the most part |
| # | 20:46:26 | tsbere points at the PRODUCT_DIR_REGKEY thing, which it reads to see if it is already installed and thus should re-use the folder |
| # | 20:46:51 | tsbere | Since that is a constant (not dependant on tag) it doesn't take into account the product tag right now. |
| # | 20:47:23 | phasefx may be thinking of innosetup behavior, also |
| # | 20:48:47 | bshum | I've always been curious about that with innosetup too actually. The path we have assigned to each subsequent 2.0 leaves whichever you installed first as the path. So like, some of our work laptops still use 2.0-alpha pathing, unless we uninstall/reinstall. |
| # | 20:49:55 | tsbere | Would be somewhat trivial to pick a new reg key for the nsis setup so you can more easily install two very different sets. Like 2.1 compares to 2.2 at the same time (though autoupdate won't update folder names for obvious reasons) |
| # | 20:51:05 | phasefx | bshum: I bet the AppId for innosetup is the determinant, like the reg keys for NSIS tsbere metnions |
| # | 20:51:09 | bshum | At some point in the 2.0 development, the default path with innosetup started including the full version name as part of it. |
| # | 20:51:54 | phasefx | probably my doing |
| # | 20:52:20 | tsbere | bshum: I take back the search items being a good icon comment, if only because I can't tell the difference with patron search at a glance when I make them both 16x16 ;) |
| # | 20:52:29 | phasefx | yeah, I even have a different AppId across 1.6 and 2.0 |
| # | 20:53:11 | bshum | tsbere: Aha... funny! |
| # | 20:54:19 | tsbere | Making the new toolbars, on its own, is a PITA. And I don't have good icons for everything. >_> |
| # | 20:55:08 | tsbere mainly has no good icons for cataloging things |
| # | 20:55:24 | phasefx | just make one of those generic binary-looking placeholder icons like unicode glyphs without the proper font :) |
| # | 20:55:49 | pmplett has joined #evergreen |
| # | 20:58:15 | tsbere was thinking about using hillblue_indicti as it was already there |
| # | 21:01:06 | phasefx | http://openiconlibrary.sourceforge.net/ |
| # | 21:02:23 | phasefx | tsbere: the double-dagger unicode glyph might be good for cataloging |
| # | 21:02:48 | tsbere | phasefx: I already dug through that to find my hotkey toggle icon |
| # | 21:03:09 | tsbere | (which I then had to modify slightly) |
| # | 21:03:30 | phasefx | http://en.wikipedia.org/wiki/Dagger_(typography) |
| # | 21:03:32 | tsbere | But at this point the icons are specified with CSS, so changing them is easy. |
| # | 21:11:47 | tsbere | phasefx: Any objections to removing the accesskeys from the toolbar buttons (that aren't defined in the lang.dtd file anyway)? Toolbars aren't keyboard-nav enabled by default..... |
| # | 21:13:18 | phasefx | tsbere: not sure; I don't think of any stock accesskeys being associated with toolbar buttons per se. As long as say, F3, still brings up the catalog, button or no button, I'm happy |
| # | 21:13:55 | tsbere | all of the lang.dtd entries were "", aka nada. |
| # | 21:14:59 | phasefx | ah, I see |
| # | 21:15:06 | phasefx | no objections from me |
| # | 21:16:53 | phasefx | though if we're still using the .labels, we should probably rename them |
| # | 21:17:59 | tsbere | ? |
| # | 21:18:18 | tsbere | (we are, but not sure why we want to rename them) |
| # | 21:18:41 | phasefx_ | the POTS stuff for I18N expect a corresponding .accesskey if it sees an entity ending in .label |
| # | 21:18:41 | phasefx | sorry, packet loss making it difficult to type here :) |
| # | 21:19:05 | phasefx | so just trim off the .label |
| # | 21:19:09 | tsbere | ok |
| # | 21:19:14 | phasefx | tsbere++ |
| # | 21:19:14 | tsbere | good to know |
| # | 21:19:26 | tsbere | especially as I still have the affected files open for editing |
| # | 21:27:21 | tsbere is giving himself a headache trying to remember all the places he has to touch when rigging up some of this stuff |
| # | 21:29:36 | tsbere | phasefx: There are already entries with .label variants but without .accesskey variants. Like replace barcode? |
| # | 21:29:48 | tsbere | (both in the xul and the lang.dtd) |
| # | 21:32:10 | tsbere also isn't sure he should be changing the ids of already translated strings, but isn't sure how the translations work in that regard |
| # | 21:32:22 | phasefx | yeah, I've been too lazy to go fix em all up, but have tried to be nice going forward. I think it's just a warning in the I18N build process, but I don't know how annoying it is |
| # | 21:32:43 | phasefx | as far as I'm concerned, there isn't a string freeze for 2.1 yet |
| # | 21:33:47 | phasefx | I think the POTS tools have fuzzy tracking for entity changes |
| # | 21:33:57 | phasefx | not sure about launchpad |
| # | 21:34:22 | phasefx | we should ask dbs which is better |
| # | 21:34:57 | tsbere | We can always define .accesskey variants and never use them! |
| # | 21:35:00 | tsbere | (for now) |
| # | 21:35:21 | phasefx | :-/ |
| # | 21:36:02 | tsbere | AKA, I don't remove the "" defs in lang.dtd |
| # | 21:36:06 | tsbere | But don't add any more |
| # | 21:36:07 | phasefx | there's probably lots of love we could give to this entities.. redundancies where we don't need them, sharing where we need more context |
| # | 21:38:25 | phasefx | tsbere: yeah, I say do the easy thing for now (leave the identifiers alone, keep the accesskey definitions), and dbs can set us straight later |
| # | 21:38:54 | phasefx | he's current the I18N champion, though I'm sure he's ready to hand that torch to someone else, if we can find such a person |
| # | 21:39:03 | tsbere will need to use this new knowledge for the rest of the menus he is adding, though |
| # | 21:43:16 | tsbere | Any thoughts on my new button? http://www.bstcon.com/hotkeys_disable_toolbar.png |
| # | 21:46:01 | phasefx | grey means no perm to toggle? looks good to me. Maybe an underline on the N would identify it more with hotkeys |
| # | 21:47:28 | tsbere | I am not assigning a perm to toggle. I am just a completionist. |
| # | 21:47:30 | tsbere | >_> |
| # | 21:48:02 | phasefx_ | :) |
| # | 21:48:12 | tsbere | And if people want to find/make better icons, all the power to them. |
| # | 21:48:50 | tsbere | In fact, it will be "make one image, maybe update the global css file" |
| # | 21:48:51 | phasefx | the power of open-criticism-software |
| # | 22:23:38 | moodaepo_ | Objections to updating the EG blog theme? > http://lupin.georgialibraries.org/blog/ |
| # | 22:26:33 | bjwebb has quit IRC |
| # | 22:31:12 | tsbere | moodaepo_: Only if that header image stays without transparency of some kind. Or pseudo-transparency. Or something? |
| # | 22:31:21 | bshum | Weird blue. |
| # | 22:32:00 | bshum | Is it just me or is the top/sides of that page light blue? |
| # | 22:32:28 | bshum | Actually bottom area too. |
| # | 22:55:35 | moodaepo_ | tsbere: the header is the default eg logo we use. |
| # | 22:56:43 | moodaepo_ | bshum: I messed with one of the default options in that theme it's grey/light blu originally 9we do have blue-green-orange combo on the site) |
| # | 22:58:44 | moodaepo_ | To compare this is our official blog using the default WordPress theme > http://evergreen-ils.org/blog/ |
| # | 23:23:56 | dbs has joined #evergreen |
| # | 23:33:44 | moodaepo_ | Removed logo and cleaned up a bit > http://lupin.georgialibraries.org/blog/ |
| # | 23:37:00 | moodaepo_ | Interesting and somewhat recent write-up on Evergreen > http://bgjackofalltrades.wordpress.com/2010/12/05/evergreen-an-open-source-integrated-library-system/ |
| # | 23:37:11 | dbs | moodaepo: wow, looking nice! any chance of getting the standard nav menu in there to tie the blog into the rest of the site? |
| # | 23:37:14 | moodaepo_ | Well interesting because it's somewhat recent. |
| # | 23:38:29 | moodaepo_ | dbs: Yes that's possible, might have to spend a little time and move it out to a theme/sub-theme so it doesn't get over written in another 6-7 years : ) |
| # | 23:40:50 | moodaepo_ | dbs: Any other suggestions re website/blog/dokuwiki there have been quite some changes. I'm not sure I like the lupin/dokuwiki wysiwig (or I just need to get used to it, I set it up hoping to lower the bar) |
| # | 23:41:28 | dbs | moodaepo: sorry, just say your blog link, haven't been paying attention this weekend |
| # | 23:43:27 | moodaepo_ | dbs: No worries. We can always update the menu once we go live (I plan on other updates anyway) |
| # | 23:43:42 | dbs | cool; it's lived this long without a menu :0 |
| # | 23:45:32 | moodaepo_ | Hey you did awesome getting one up! So a 3 month turn around ain't too bad for a semi-redesign. |
| # | 23:46:18 | dbs | oh... yeah, that wysiwyg editor doesn't give you an option of just using the regular dokuwiki syntax, eh? |
| # | 23:46:47 | dbs | oh wait - "DW edit" button at the bottom |
| # | 23:46:52 | moodaepo_ | Right |
| # | 23:47:11 | moodaepo_ | I was just typing that but it's a bloody hassel |
| # | 23:47:16 | dbs | ("Source" button on the top right was worrying me)I can live with that |
| # | 23:49:18 | dbs | The "Delete" button between "Save" and "DW Edit" scares me a bit, but I bet there's an "Are you sure?" prompt at least |
| # | 23:50:04 | moodaepo_ | I don't know...trying it |
| # | 23:52:21 | moodaepo_ | Yup it has a "Are you sure" prompt |
| # | 23:52:22 | phasefx | apparently the wysiwyg thing is a plugin, that we could remove. I don't like it, but it might make things friendlier for the average new user |
| # | 23:52:48 | moodaepo_ | phasefx: yes I installed it (it's in the migration/upgrade notes) |
| # | 23:52:56 | phasefx | cool deal |
| # | 23:53:33 | moodaepo_ | And the reason I installed was...average webteam folk commenting (yadda yadda yadda) |
| # | 23:54:14 | phasefx | well, friendly is good. Power users can deal :) |
| # | 23:55:35 | moodaepo_ | I think I have it planned out for a transfer (dokuwiki/wordpress) in at the most half an hour, I was aiming for a pre-conf move (DNS change Friday-ish not sure if it's possible). |
| # | 23:55:43 | dbs | huh. Just tried adding a bullet to a section; "Save" wouldn't do anything, so I clicked "DW Edit" and the entire section was wiped out |
| # | 23:55:51 | dbs | First section in http://lupin.georgialibraries.org/dokuwiki/doku.php?id=authorities:2.0 |
| # | 23:56:02 | moodaepo_ | Oh-Oh |
| # | 23:56:03 | dbs | Just replaced with "__false__" |
| # | 23:56:26 | dbs | Friendly is good, destructive not so good :) |
| # | 23:56:56 | dbs | Try adding a bullet onto the end of a bulleted list and see if you can reproduce? |
| # | 23:59:52 | moodaepo_ | dbs: Trying (btw the "Index" button at the bottom got replaced by "Sitemap" is that important? |
April 10-13