| 00:04:11 | * | darkf joined #nimrod |
| 00:58:00 | * | jpoirier joined #nimrod |
| 01:12:11 | * | jpoirier quit (Quit: Leaving) |
| 01:12:58 | * | q66 quit (Quit: Leaving) |
| 01:57:45 | onionhammer | dom96 some way of accessing globals in the new jester would be nice |
| 01:58:02 | onionhammer | dom96 of course i know this stems back to that same gc not safe thing we talked about the other day |
| 02:42:21 | * | darkf_ joined #nimrod |
| 02:45:01 | * | darkf quit (Ping timeout: 272 seconds) |
| 02:51:32 | * | flaviu joined #nimrod |
| 03:20:44 | * | kshlm joined #nimrod |
| 03:26:56 | * | shiv joined #nimrod |
| 03:29:45 | shiv | I am unable to install 0.9.4 on Linux from github sources. Can someone help? Thanks. |
| 03:33:44 | * | flaviu quit (Ping timeout: 255 seconds) |
| 03:34:49 | * | shiv quit (Quit: Page closed) |
| 03:36:40 | * | darkf joined #nimrod |
| 03:38:44 | * | darkf_ quit (Ping timeout: 260 seconds) |
| 03:46:53 | * | skrylar joined #nimrod |
| 03:48:59 | * | Demos quit (Read error: Connection reset by peer) |
| 04:04:40 | * | xenagi quit (Quit: Leaving) |
| 04:13:56 | * | darkf_ joined #nimrod |
| 04:14:40 | * | darkf quit (Ping timeout: 260 seconds) |
| 04:19:36 | * | darkf_ is now known as darkf |
| 04:22:46 | * | darkf_ joined #nimrod |
| 04:24:27 | * | darkf quit (Ping timeout: 272 seconds) |
| 04:25:30 | * | darkf joined #nimrod |
| 04:27:16 | * | darkf_ quit (Ping timeout: 260 seconds) |
| 04:31:16 | * | ARCADIVS joined #nimrod |
| 04:36:23 | skrylar | ugh |
| 04:36:41 | skrylar | i didn't know getting a simple footpedal to work would require writing C code |
| 04:54:26 | Araq | skrylar: no, it doesn't. I'm sure you can write Nim code instead |
| 05:15:58 | * | fowl quit (Read error: No route to host) |
| 05:20:20 | * | BlaXpirit joined #nimrod |
| 05:27:38 | * | fowl joined #nimrod |
| 05:27:38 | * | fowl quit (Changing host) |
| 05:27:38 | * | fowl joined #nimrod |
| 05:27:55 | skrylar | Araq: probably. |
| 05:28:24 | skrylar | Araq: i think i ended up adding an extra ~40 minutes because i decided inspecting USB dumps woudl be a good way to practice data analytics |
| 05:29:05 | skrylar | on an up note, i ended up with a tidy little script that groups the packets in to keypress, then culls bytes that never changed, and makes this succint little "this is how you read an IN-USB-2" table </monologue> |
| 05:42:47 | skrylar | now to deal with shoving data out to uinput |
| 05:55:14 | * | kunev joined #nimrod |
| 06:09:51 | skrylar | uinput did bad bad things o.o |
| 06:22:06 | * | vendethiel quit (Quit: q+) |
| 06:27:21 | * | skrylar quit (Quit: leaving) |
| 06:53:01 | * | darkf_ joined #nimrod |
| 06:54:44 | * | darkf quit (Ping timeout: 260 seconds) |
| 06:56:42 | * | darkf__ joined #nimrod |
| 06:57:43 | * | darkf_ quit (Ping timeout: 272 seconds) |
| 06:58:30 | * | darkf__ is now known as darkf |
| 07:04:03 | * | darkf quit (Ping timeout: 272 seconds) |
| 07:04:40 | * | darkf joined #nimrod |
| 07:39:35 | * | bjz joined #nimrod |
| 08:09:41 | Araq | bogen: as a workaround, don't += global variables |
| 08:21:04 | * | Araq_ joined #nimrod |
| 08:46:47 | * | Trustable joined #nimrod |
| 08:57:00 | * | kunev quit (Ping timeout: 260 seconds) |
| 09:06:32 | * | BlaXpirit quit (Quit: Quit Konversation) |
| 09:08:02 | * | BlaXpirit joined #nimrod |
| 09:09:23 | * | Araq_ quit (Read error: Connection reset by peer) |
| 09:11:18 | * | Araq_ joined #nimrod |
| 09:16:58 | dom96 | good morning |
| 09:25:34 | * | kunev joined #nimrod |
| 09:55:53 | * | BlaXpirit quit (Quit: Quit Konversation) |
| 09:56:31 | * | BlaXpirit joined #nimrod |
| 10:10:26 | * | zahary quit (Ping timeout: 250 seconds) |
| 10:14:06 | * | Araq_ quit (Quit: ChatZilla 0.9.90.1 [Firefox 31.0/20140716183446]) |
| 10:37:59 | * | ARCADIVS quit (Quit: WeeChat 0.4.3) |
| 11:06:54 | * | kshlm quit (Ping timeout: 255 seconds) |
| 12:03:56 | bogen | Araq: ok. Well, I tried doing it all without globals. Then I ran into the lambda lifting issue, which is I why I made some local functions and variables global. I guess I could use an object and associated member functions rather than the approach I'd been using (local funcations all sharing parent functions data). |
| 12:11:07 | bogen | The reason I filed the lamda related issue is because it was only after I started making those procedures and associated data global that I started seeing the variable corruption. |
| 12:19:04 | * | jasondotstar quit (Quit: Leaving) |
| 13:32:37 | * | UNIcodeX quit (Read error: Connection reset by peer) |
| 13:47:02 | * | Araq_ joined #nimrod |
| 13:47:51 | Araq_ | bogen: well yeah. using locals and then storing it back into the global should work much better though |
| 13:55:47 | onionhammer | mornin |
| 13:56:22 | * | saml joined #nimrod |
| 14:01:46 | * | darkf quit (Quit: Leaving) |
| 14:24:19 | dom96 | hey onionhammer |
| 14:26:14 | onionhammer | hows it going dom |
| 14:30:02 | * | saml quit (Quit: Leaving) |
| 14:30:23 | * | saml joined #nimrod |
| 14:50:21 | dom96 | onionhammer: good, you liking async? |
| 14:56:21 | onionhammer | dom96 with the exception of not being able to access globals |
| 14:56:45 | onionhammer | dom96 it's looking pretty good though, i'm impressed. |
| 14:57:17 | onionhammer | dom96 There are probably still a couple of API things you're going to need to add once you get more real world programs using it |
| 15:00:21 | * | mko quit (Ping timeout: 240 seconds) |
| 15:03:01 | Araq_ | onionhammer: --threadAnalysis:off and then you can use globals |
| 15:03:09 | Araq_ | or mark them as .threadvar |
| 15:03:57 | * | Sht0 quit (Ping timeout: 245 seconds) |
| 15:05:14 | onionhammer | Araq_ okay. whats the plan for this going forward? |
| 15:05:25 | onionhammer | Araq_ seems like something a lot of people are potentially going to run into |
| 15:06:03 | onionhammer | dom96 also what's the 'match' paramter in jester.serve? |
| 15:06:14 | Araq_ | the quick fix is to tie threadAnalysis to --threads:on |
| 15:06:20 | onionhammer | dom96 presumably it's declared in some macro, but it seems messy |
| 15:06:42 | EXetoC | how would one dereference a distinct type refering to a type with a qualifier such as ptr? casting can be performed of course, and I suppose you can just make a pointer of the distinct type |
| 15:06:43 | onionhammer | Araq_ that seems like a good interim solution anyway |
| 15:06:56 | EXetoC | without any kind of alias that is, which we will get rid off |
| 15:12:47 | * | def- quit (Ping timeout: 245 seconds) |
| 15:13:59 | * | bogen quit (Quit: Leaving.) |
| 15:14:11 | * | kunev quit (Quit: leaving) |
| 15:14:20 | Araq_ | EXetoC: not sure what you mean |
| 15:17:17 | NimBot | Araq/Nimrod devel 10f6a11 fuzzthink [+0 ±1 -0]: Pointer -> pointer to fix compile error using --cs:partial |
| 15:17:17 | NimBot | Araq/Nimrod devel 967b507 Simon Hafner [+0 ±1 -0]: Merge pull request #1514 from fuzzthink/devel... 2 more lines |
| 15:19:35 | Araq_ | hmm maybe we should really merge bigbreak into devel ... |
| 15:19:56 | dom96 | yes |
| 15:22:59 | * | Demos joined #nimrod |
| 15:23:35 | Demos | what does bigbreak do? is it just the rename? |
| 15:23:54 | Araq_ | rename, T/P prefixes are deprecated, cs:partial is the default |
| 15:24:20 | Demos | wait how are T/P prefixes depricated, were there features that depended on em? |
| 15:24:30 | Demos | or were they just removed from the compiler and libraries |
| 15:24:38 | Demos | also awww I like the prefixes, oh well |
| 15:25:27 | Araq_ | {.deprecated: [TFile: File, TSocket: Socket].} has been added |
| 15:25:33 | Araq_ | so code continues to work |
| 15:25:56 | Araq_ | it's the --cs:partial which breaks everything |
| 15:26:22 | EXetoC | Araq_: distinctType.(ptr targetType) |
| 15:26:54 | Araq_ | bbs |
| 15:27:33 | * | BlaXpirit quit (Quit: Quit Konversation) |
| 15:28:18 | dom96 | onionhammer: Yes, my plan is to get the 'route' macro to generate the jester.serve. |
| 15:28:55 | dom96 | Settings then will also be a macro and they will generate a 'settings' var |
| 15:29:04 | * | BlaXpirit joined #nimrod |
| 15:29:32 | dom96 | It's a bit messy I guess, but if you have a better idea of how to implement this then tell me. |
| 15:35:24 | * | Demos quit (Ping timeout: 268 seconds) |
| 15:54:39 | * | brson joined #nimrod |
| 16:07:04 | * | noam_ quit (Ping timeout: 250 seconds) |
| 16:07:28 | * | def- joined #nimrod |
| 16:24:37 | Trustable | Hi all |
| 16:24:41 | reactormonk | o/ |
| 16:24:54 | Araq_ | hi Trustable |
| 16:30:42 | * | kunev joined #nimrod |
| 16:31:58 | Trustable | Is this the right place to discuss about Aporia or better use #Aporia? |
| 16:32:33 | EXetoC | this channel is fine |
| 16:33:42 | Trustable | dom96, I will answer your questions about my PR here, ok? |
| 16:34:05 | dom96 | Trustable: I would prefer if you answered it on github for future reference. |
| 16:34:29 | Trustable | dom96: ok |
| 16:35:46 | dom96 | Trustable: One question i'll ask here though: how do you show the key shortcuts? Is it just a number representing the key? If so it would be nice to have something more user friendly, is that easy to do? |
| 16:36:36 | Trustable | My current implementation is just the very first step to make the shortcuts configurable. |
| 16:36:50 | dom96 | Trustable: That's fine, it's better than nothing :) |
| 16:37:10 | Trustable | Only the key code is configurable, not the modifier mask. |
| 16:37:18 | dom96 | Trustable: Apart from the little issues I commented about I really like your PR. Good job! |
| 16:37:44 | Trustable | The key code is stored as integer in the config file and the main memory. |
| 16:38:46 | Trustable | In the settings window, the key is shown as character resp. "f1", f2", ... |
| 16:39:23 | dom96 | oh, that's better than I thought then. |
| 16:39:32 | dom96 | Thoguht the settings window also shows the integer. |
| 16:39:33 | Trustable | At the moment it's a simple text box. |
| 16:39:37 | dom96 | *Thought |
| 16:39:57 | Trustable | In the future it should be replaced by key capture. |
| 16:40:02 | dom96 | indeed |
| 16:40:16 | Trustable | including the modifiers |
| 16:40:42 | dom96 | Can we encode a key code + modifier in a single value? |
| 16:40:49 | dom96 | or will we need to add more setting paramters? |
| 16:41:31 | Trustable | I don't know yet. |
| 16:41:36 | onionhammer | dom96 i'll go over it tonight - im converting my blog over |
| 16:41:41 | onionhammer | dom96 once it's done i'll give you some feedback |
| 16:41:59 | dom96 | onionhammer: great |
| 16:42:09 | Araq_ | you guys should implement the biggest missing feature |
| 16:42:33 | Araq_ | I call it the "verbose view" |
| 16:42:42 | Trustable | btw. Is the Nimrod compiler ready for productive development in your opinion? |
| 16:42:52 | onionhammer | Trustable no, not yet IMO |
| 16:43:28 | Araq_ | it asks the compiler for a verbose view of a module |
| 16:43:28 | Trustable | I made some simple programs, had no problems no far. |
| 16:43:44 | Trustable | *so far |
| 16:44:13 | dom96 | Trustable: problem with adding more parameters later is that we will break people's config |
| 16:44:34 | * | q66 joined #nimrod |
| 16:44:45 | Trustable | yes, this is an important topic |
| 16:44:48 | dom96 | Trustable: But it should be ok, we can deprecate the old parameters. |
| 16:45:11 | dom96 | Trustable: And introduce new ones, perhaps under a new ini [section] |
| 16:46:13 | Trustable | first of all, are there enough Aporia users, so say, that we have to think their configs? |
| 16:46:21 | Trustable | *to say |
| 16:47:07 | dom96 | I only know of two people that use it. |
| 16:47:11 | dom96 | ok, maybe 3 |
| 16:47:16 | dom96 | me, Araq_ and fowl |
| 16:47:35 | dom96 | unfortunately we may never know how many people really use it |
| 16:47:44 | Trustable | I also use it |
| 16:47:56 | Araq_ | I will complain when you break my config :P |
| 16:48:18 | Trustable | :) |
| 16:49:33 | * | milosn quit (Ping timeout: 240 seconds) |
| 16:49:46 | Trustable | In my opinion should a incomplete config file accepted by the program. |
| 16:50:01 | Trustable | For example when some recently added options are missiong. |
| 16:50:04 | Trustable | *missing |
| 16:50:24 | * | milosn joined #nimrod |
| 16:50:46 | Trustable | ah, this is not a problem |
| 16:51:09 | Trustable | The problem might be, when the config file contains an option, which is not longer valid. |
| 16:51:55 | dom96 | Yes, we can accept it and then print a deprecation warning. |
| 16:52:02 | dom96 | Anyway, I think i'm done my review of your code. |
| 16:52:11 | dom96 | Fix those comments and it should be ready to be merged. |
| 16:52:36 | Trustable | Where do we show warning about the config? As new dialog window or in the Output window? |
| 16:53:31 | dom96 | Trustable: Here: https://github.com/nimrod-code/Aporia/pull/54/files#diff-1fe37933ce0a98156a0ef998b9996bc4L2336 |
| 16:55:11 | * | wan joined #nimrod |
| 16:55:42 | * | Matthias247 joined #nimrod |
| 16:56:01 | Trustable | dom96, I think your code review is better than that from the Heartbleed bug :) |
| 16:56:45 | dom96 | Trustable: haha, thanks. Hope you don't mind that I am so picky. |
| 16:57:19 | Trustable | dom96: absolutely not |
| 16:58:22 | * | gkoller joined #nimrod |
| 16:59:22 | * | vegai quit (Ping timeout: 240 seconds) |
| 17:00:06 | Araq_ | IMHO it should simply fix the deprecated options |
| 17:00:20 | Araq_ | instead of complaining |
| 17:00:39 | * | EXetoC quit (Read error: No route to host) |
| 17:00:54 | * | kunev quit (Ping timeout: 252 seconds) |
| 17:01:02 | * | vegai joined #nimrod |
| 17:02:00 | Trustable | But how to fix? |
| 17:02:53 | Trustable | The whole file will be overwritten on save, so unrecognized entries will be removed, right? |
| 17:03:38 | * | EXetoC joined #nimrod |
| 17:06:43 | Trustable | Another question: Why does "gtk2.delete(textBuffer, ...)" compile, but not "textBuffer.delete(...)"? |
| 17:07:17 | * | Araq_ quit (Quit: ChatZilla 0.9.90.1 [Firefox 31.0/20140716183446]) |
| 17:09:26 | dom96 | ambiguity? |
| 17:09:49 | Trustable | yes |
| 17:16:04 | Trustable | Addition: "textBuffer" is an expression which results to an instance of TSourceBuffer, which is derived from TTextBuffer. |
| 17:20:02 | * | comex quit (Quit: WeeChat 0.4.0) |
| 17:21:42 | * | Jehan_ joined #nimrod |
| 17:23:34 | * | comex joined #nimrod |
| 17:33:10 | Trustable | Why is the "delete" identifier ambiguous? And why only under Windows? |
| 17:34:00 | Araq | dunno, do you import windows.nim? |
| 17:40:06 | Araq | there is likely some windows.DELETE constant that confuses the compiler |
| 17:40:56 | Trustable | I don't see "windows" in the import section |
| 17:44:53 | Araq | try: |
| 17:45:02 | Araq | import gdk2 except DELETE |
| 17:45:42 | * | kunev joined #nimrod |
| 17:46:56 | Jehan_ | Araq: Submit new pull requests for devel or for bigbreak? |
| 17:47:38 | Araq | if only I knew, Jehan_ |
| 17:47:52 | Jehan_ | Araq: Just asking what your preference is. |
| 17:48:28 | Araq | we need to merge bigbreak into devel, but thanks to --cs:partial this breaks every babel package out there |
| 17:48:53 | * | Ven joined #nimrod |
| 17:48:59 | Trustable | Araq, it works when I change the order of the imports |
| 17:49:02 | * | wan quit (Ping timeout: 245 seconds) |
| 17:49:31 | Araq | Trustable: yeah, it's a known compiler bug |
| 17:50:05 | Araq | my workaround should work too |
| 17:50:06 | Jehan_ | Every babel package? Ouchies. |
| 17:50:39 | Araq | it's not a big deal, somebody will run "nim pretty" over every package and make PRs |
| 17:50:55 | Araq | but until we did that, I don't want to merge |
| 17:51:59 | Araq | hmm I just got an idea ... |
| 17:53:29 | Araq | Jehan_: what do you have in the pipeline? |
| 17:53:52 | Jehan_ | Araq: Nothing major right now. |
| 17:54:13 | Jehan_ | These are really minor things, such as fixing createDir permissions on POSIX. |
| 17:54:32 | Jehan_ | I have some things that I _want_ to do, but for which I don't have the time at the moment. |
| 17:54:40 | Araq | just make them against devel for now |
| 17:54:46 | Jehan_ | Alrighty. |
| 17:57:01 | Jehan_ | Ugh, they create conflicts when backporting. |
| 17:57:06 | Jehan_ | I think I'll postpone. |
| 17:57:17 | Araq | sure no worries |
| 17:57:51 | Araq | hmm finding a bug in thousands of lines of generated bytecode is not that much fun |
| 17:57:54 | Jehan_ | Yeah, they don't bother me, since I don't need the Windows version, so I can just use posix.mkdir. |
| 17:58:24 | Trustable | dom96: I have to correct myself: I store the key not as integer but as string in the config file. |
| 18:05:06 | * | wan joined #nimrod |
| 18:17:29 | dom96 | Trustable: can you give me an example of such a string? |
| 18:17:55 | Trustable | dom96: "a", "/", "F1", ... |
| 18:18:06 | dom96 | Trustable: ahh, that's good. |
| 18:18:14 | Trustable | I will extend this string with the modifier mask |
| 18:18:23 | dom96 | Yeah, that will work. |
| 18:18:44 | Trustable | The good thing of this: the config file is human readable (numbers would be not) |
| 18:19:05 | Trustable | The bad thing: more work |
| 18:19:34 | dom96 | heh yes |
| 18:19:39 | Trustable | But I think we need to have a string representation of every possible shortcut, to show it in the settings window |
| 18:20:04 | dom96 | Araq: Do we have a issue on github for that compiler bug? |
| 18:20:16 | Trustable | There are many key which are not yet included in my implementation. |
| 18:20:34 | Araq | dom96: I don't think so and it's not easy to fix either |
| 18:20:42 | Araq | otherwise I'd already have done it |
| 18:21:04 | Araq | well actually |
| 18:21:09 | Araq | it IS easy enough to fix |
| 18:21:14 | Araq | but will break your code :P |
| 18:21:37 | dom96 | is that the correct way to fix it? |
| 18:22:06 | Araq | yes |
| 18:23:42 | dom96 | well as long as it's easy to fix for me |
| 18:23:43 | dom96 | then do it |
| 18:25:36 | Araq | ok |
| 18:27:52 | Araq | I take it back, debugging this thing IS fun :-) |
| 18:34:04 | * | Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…) |
| 18:52:55 | * | gsingh93 joined #nimrod |
| 19:10:00 | * | kunev quit (Ping timeout: 268 seconds) |
| 19:12:08 | * | nande joined #nimrod |
| 19:14:03 | * | Jesin joined #nimrod |
| 19:15:20 | * | Jesin quit (Max SendQ exceeded) |
| 19:16:33 | * | Jesin joined #nimrod |
| 19:17:00 | * | Ven joined #nimrod |
| 19:17:21 | * | vendethiel joined #nimrod |
| 19:18:40 | * | Ven quit (Client Quit) |
| 19:21:52 | * | Jesin quit (Ping timeout: 240 seconds) |
| 19:33:35 | * | Jesin joined #nimrod |
| 19:42:34 | * | flaviu joined #nimrod |
| 19:54:39 | wan | What are you supposed to do when you get an "Error: 'stuff' is not GC-safe" on a previously-working program ? |
| 19:57:48 | wan | Should I mark every potentially-accessed variable either {.global.} or {.threadvar.} ? |
| 20:00:36 | dom96 | only global vars should be marked {.threadvar.} if you really need them |
| 20:00:56 | dom96 | and you need to mark your closures/proc types gcsafe I think |
| 20:01:16 | wan | Ah, I'll try marking closures gcsafe |
| 20:02:22 | wan | Hm, doesn't seem to be that |
| 20:04:16 | Araq | wan: use warning[GcUnsafe]:on to see why the compiler thinks your code is GC unsafe |
| 20:04:35 | Araq | usually it's also caused by a forward declaration |
| 20:09:15 | wan | Ha, very useful. These warning should probably be on by default (especially if the compilation fails) |
| 20:11:24 | dom96 | Bah. Looks like we really need to fix unittest. |
| 20:11:29 | dom96 | A lot of people are using it. |
| 20:12:01 | Trustable | Newbie question: How can I iterate over the elements of a TTable? |
| 20:12:12 | Araq | for key, val in tab |
| 20:12:36 | Trustable | thx :) |
| 20:12:41 | Araq | dom96: well it's easy to fix according to flaviu since it's only caused by compiler passes interacting in strange ways |
| 20:13:05 | dom96 | we also need to document it |
| 20:13:26 | Araq | well as long as it's not documented, it's not offically supported |
| 20:13:32 | dom96 | lol |
| 20:13:38 | dom96 | Yeah, people don't care. |
| 20:14:10 | Araq | I don't get why unittest buys us |
| 20:14:20 | Araq | I consider it a stress test for template expansions |
| 20:14:27 | wan | Hum, can't fix my problem yet. I have a globally-accessed seq of closures that is filled by main thread on startup, but read-only for worker threads afterwards, but I can't seem to compile on the latest bigbreak |
| 20:14:47 | dom96 | The exercism guys made a Nimrod exercise, and they make use of it. |
| 20:15:07 | dom96 | I'm of course not complaining, it's great that they are writing Nimrod :P |
| 20:15:28 | Araq | wan: interesting. well --threadAnalysis:off should make it compile for you |
| 20:15:48 | dom96 | Araq: it buys us sexy unit tests. |
| 20:16:08 | Araq | ah yeah. sex. I keep forgetting about this reason. |
| 20:16:24 | dom96 | I'll just have to spend some time understanding the code. |
| 20:16:48 | dom96 | Since zahary decided to escape into the land of narnia. |
| 20:17:25 | wan | Araq: well, not even that. I've hit a compiler bug (Error: internal error: expr: var not init) |
| 20:18:34 | Araq | wan: well report it, but fix your horrible closures |
| 20:18:49 | wan | I have to reduce it to a short failing test first, my stuff is a mess for now |
| 20:19:06 | * | zahary joined #nimrod |
| 20:19:15 | Araq | ha zahary is back |
| 20:19:26 | * | filwit joined #nimrod |
| 20:19:30 | dom96 | is he though? |
| 20:19:35 | Araq | and filwit |
| 20:19:40 | dom96 | that could just be his zombie irc client |
| 20:19:43 | dom96 | yay filwit |
| 20:19:44 | filwit | hey Araq |
| 20:19:49 | filwit | & dom96 |
| 20:19:53 | wan | Hi |
| 20:19:56 | dom96 | how's things filwit? |
| 20:19:58 | filwit | hi wan |
| 20:19:59 | Araq | well at least he can now highlight him |
| 20:20:33 | filwit | dom96: good, just stopping by for a bit (trying to finish up the forums now), but it's my grandma's b-day so I don't have much time |
| 20:20:48 | * | Jesin quit (Quit: Leaving) |
| 20:21:15 | dom96 | filwit: ahh cool. I would tell you to wish her a happy birthday from me but you may have a hard time explaining who I am hah. |
| 20:21:32 | filwit | wan: ps, new docs design (so far) are here: http://reign-studios.net/philipwitte/nim/docs.htm feedback is welcome |
| 20:21:45 | filwit | dom96: lol |
| 20:22:30 | wan | Yay! Design bashing! |
| 20:22:40 | filwit | actually i was just telling my mother today that if I learned a new language it would probably be German, so that i could talk to Araq and get tips. |
| 20:22:53 | filwit | she was like "talk to Iraq? wut?" |
| 20:23:29 | filwit | wan: bash away :) |
| 20:23:42 | wan | That's actually a lot better than I expected |
| 20:24:00 | dom96 | filwit: hrm, did you make the background color of each type/proc/iter box darker? |
| 20:24:02 | wan | I like the use of colors |
| 20:24:06 | filwit | wan: thanks, but it's not entirely done yet either (their's no isolate feature or sorting JS yet) |
| 20:24:14 | flaviu | Araq: I can't make any claims when it comes to unittest, I've never looked at the code |
| 20:24:29 | filwit | dom96: possibly, but I don't think so |
| 20:24:31 | dom96 | filwit: because I feel as if it looks better than it did previously. |
| 20:25:25 | filwit | dom96: well that's good :) but i don't think I changed anything there. Probably just the light in your room. I did fix all the issue with small-sceens though (mostly) |
| 20:26:06 | filwit | i still need to make the side-bar thing collapsible for really small devices |
| 20:26:18 | dom96 | filwit: heh, did you play around with different hyperlink colors yet? |
| 20:26:44 | dom96 | also what is that in the background? |
| 20:26:46 | filwit | dom96: no, but honestly I kinda like them as-is (i played around with those when i first made the home design) |
| 20:26:52 | dom96 | the nim logo |
| 20:27:03 | filwit | yeah, blurred version of it |
| 20:27:09 | dom96 | but what's beside it? |
| 20:27:20 | dom96 | it looks like a dragon lol |
| 20:27:30 | filwit | there's no dragon... |
| 20:27:36 | dom96 | i'll play around with the colors a bit later |
| 20:28:03 | dom96 | if I make the window smaller then there is something beside the nim logo in the backgroun |
| 20:28:04 | dom96 | d |
| 20:28:44 | filwit | i'm not sure what you're talking about. perhaps take a screenshot |
| 20:28:50 | wan | There might be a need for a max-width on the main content |
| 20:29:06 | filwit | wan: there is already |
| 20:29:12 | * | gkoller quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…) |
| 20:29:22 | dom96 | filwit: well I just looked at this: http://reign-studios.net/philipwitte/nim/images/bg.jpg |
| 20:29:27 | dom96 | looks nothing like a dragon lol |
| 20:29:27 | Jehan_ | Hmm, my mouse cursor doesn't change to a vertical bar when over text there? |
| 20:29:32 | dom96 | just my imagination. |
| 20:29:55 | dom96 | oh yeah, same here. |
| 20:30:03 | filwit | dom96: you can see that better on the homepage. It's just a faded nim logo |
| 20:30:09 | wan | Doesn't seem so, I like to ctrl- pages because most pages have too big fonts for my eyes (I like small fonts), but the parameters get away too much from the procs and all |
| 20:30:30 | filwit | Jehan_ yes, that's by design, but I can change specific elements (like the code) to vertical bars |
| 20:30:43 | Jehan_ | filwit: Why by design? |
| 20:31:38 | filwit | Jehan_ i've gotten very positive feedback from doing that in the past (it gives a clear "clicking this will take you away" message when the cursor changes, or "you can edit this", etc)... |
| 20:32:08 | Jehan_ | filwit: Hmm. I personally hate it when webpages break standard behavior. |
| 20:32:26 | dom96 | I would prefer to see a vertical bar too. |
| 20:32:36 | dom96 | Most developers will be used to the standard behaviour. |
| 20:33:18 | filwit | lol, alright guys. Will do whatever you want, but in my experience you are in the minority here. |
| 20:33:21 | EXetoC | and don't forget 3d-transforms using CSS |
| 20:33:22 | Jehan_ | The gray used to highlight text that you select probably needs to be changed to a different color. |
| 20:33:32 | wan | filwit: I would go without the text-align:justify |
| 20:33:58 | Jehan_ | There's no contrast when selecting normal text and it's the same color as parts of the code. |
| 20:34:13 | filwit | wan: on everything? I disagree (try changing that in your browser's inspector to see how it looks) |
| 20:34:24 | dom96 | Jehan_: gray? I don't see that. What browser are you using? |
| 20:34:32 | filwit | Jehan_ what browser? |
| 20:34:32 | wan | That's what I'm doing, and the paragraphs look better for me |
| 20:34:35 | Jehan_ | dom96: Chrome on Mac. |
| 20:34:55 | dom96 | is that the default on Mac&Chrome? |
| 20:35:13 | filwit | Jehan_: ahh... Mac... I will explicitly set the highlight color then. |
| 20:35:25 | Jehan_ | dom96: Possible. |
| 20:35:50 | filwit | wan: okay, i'll try it (btw it was Araq's suggestion on the original design to make things justified, so we'll have to see what he says) |
| 20:36:00 | flaviu | filwit: main thing I can say is contrast. The w3c has recommendations, and the page doesn't really do well on them. |
| 20:36:01 | Jehan_ | Actually, it looks like Chrome pulls it from System Preferences. |
| 20:36:21 | Jehan_ | wan: I also agree on the justified vs. ragged-right part. |
| 20:36:32 | filwit | flaviu: can you not read it well? Sometime I think people have their monitors brightness too low or something. |
| 20:36:55 | Jehan_ | flaviu: Yeah, there are probably accessibility issues. |
| 20:37:03 | filwit | Jehan_, wan: you want Justified in the docs, or homepage as well? |
| 20:37:14 | flaviu | filwit: I believe my brightness is fine, I have no issues even with playing minecraft without torches |
| 20:37:23 | Araq | filwit: looks the same as last time to me. it's nice, I like it |
| 20:37:47 | filwit | flaviu: okay, noted. |
| 20:37:54 | Jehan_ | filwit: I haven't seen justified text ever work well without manual typesetting/hyphenation. |
| 20:38:02 | wan | filwit: at least in the docs, everywhere if possible |
| 20:38:12 | flaviu | Jehan_: Tex does a great job... |
| 20:38:22 | wan | I have the same opinion as Jehan |
| 20:38:25 | Jehan_ | flaviu: Yes. But web browsers aren't TeX. |
| 20:38:36 | flaviu | quite a sad fact |
| 20:38:39 | filwit | btw, the sidebar has custom scrollbars, but those don't work on Firefox or IE |
| 20:38:53 | Araq | I always wonder how anybody can be serious about TeX |
| 20:38:59 | Jehan_ | flaviu: Most importantly, TeX hyphenates. |
| 20:39:08 | Jehan_ | Araq: For anyone for whom the result matters. |
| 20:39:12 | Araq | TeX -- incomprehensible error messages |
| 20:39:18 | filwit | Jehan_, wan: i'll play around with the text-alignment. |
| 20:39:19 | Jehan_ | Plus, anyone who has to typeset mathematical formulas. |
| 20:39:20 | Trustable | Newbie question: How to do bitwise AND? |
| 20:39:20 | Araq | overfull hbox issues |
| 20:39:28 | flaviu | Trustable: `and` |
| 20:39:28 | dom96 | I vote for getting rid of justified text also. |
| 20:39:49 | flaviu | Araq: You should fix those hboxes. Your text will look bad if you don't |
| 20:40:08 | Araq | flaviu: no, the fucking tool should know the limits of the sheet |
| 20:40:17 | Jehan_ | Araq: I'm not fond of TeX from a usability perspective; I use it because little else comes close when you have to typeset scientific papers. |
| 20:40:49 | Araq | I don't even want to know how many scientific bugs have been caused by TeX |
| 20:40:51 | Jehan_ | Trustable: Watch out for operator precedence, however. |
| 20:41:09 | Araq | because people never ever can see the actual formula before it's way too late in the process |
| 20:41:10 | flaviu | Araq: There are sometimes good reasons for overfull hboxes. Main one is urls. Another is big words, an overfull hbox is better than 2 half-full lines |
| 20:41:47 | Araq | TeX is like painting a picture with putPixel commands |
| 20:42:04 | Araq | it doesn't work and the whole approach is stupid as fuck |
| 20:42:10 | * | jpoirier joined #nimrod |
| 20:42:29 | flaviu | Araq: I very, very highly disagree with that, it's worked excellent for me, but I'm not going to bother argue. |
| 20:42:39 | filwit | Araq, dom96, wan, Jehan_, flaviu: btw, do you like the procs being yellow and iterators orange, or do you think they should be flipped (since orange almost stands out more).. my original plan is to make methods red as well (vars green, const blue, converters white). Opinions? |
| 20:43:21 | flaviu | Sounds good, as long as the colors are fairly muted. This is the one place where you don't want too much contrast |
| 20:43:33 | flaviu | Current colors are great |
| 20:43:47 | Jehan_ | filwit: I don't really have an opinion there. |
| 20:44:01 | filwit | k, k |
| 20:44:09 | wan | Iterators in orange look okay, there is always less iterators so it seems good not to push for too many bright orange stuff |
| 20:44:23 | EXetoC | do you do WYSIWYG-editing of css colors? that's pretty useful |
| 20:45:00 | Araq | flaviu: when I used it, I spent more time fighting with the tool than creating the content in the first place |
| 20:45:04 | filwit | EXetoC: I will use the broswer's inspector to play with colors, yes. But most of the design is done in Inkscape :) |
| 20:45:05 | dom96 | filwit: I think what you have now is fine. |
| 20:45:10 | filwit | k |
| 20:45:25 | flaviu | Araq: Not going to argue there, the learning curve is worse than vim. |
| 20:45:42 | Araq | and a lack of alternatives doesn't make it good |
| 20:46:12 | filwit | dom96: speaking of Inkscape, i'll email you all the source art for these, so you can Araq can maintain backups in case i die |
| 20:46:14 | Araq | flaviu: it's not the learning curve either, I read 2 books about it |
| 20:46:15 | dom96 | filwit: It would be nice to have the colors be a bit more vibrant but I guess you can't do that because you want the headings to be vibrant. |
| 20:46:38 | dom96 | filwit: That's a very dramatic way to put it lol |
| 20:46:52 | EXetoC | filwit: with a color map rather than manually editing hex values I hope |
| 20:46:54 | Araq | speaking of which ... how can I describe page width and height in cm in latex? |
| 20:46:56 | EXetoC | the latter sure is fiddly |
| 20:47:17 | EXetoC | there's firepicker for example |
| 20:47:27 | dom96 | I wrote a CV in latex once. It went ok. |
| 20:48:00 | flaviu | Araq: I dunno. Why do you need that? Latex has packages for all the page sizes there are. |
| 20:48:01 | dom96 | And it looked sexy in the end. Rule #1: sexiness always wins. |
| 20:48:10 | flaviu | ^ |
| 20:49:01 | filwit | EXetoC: Firefox, Chrome, and even IE now all have built-in inspectors which you can adjust things. In the case of colors, yes there is a color picker... which is very nice, i used to have to do manual hex by hand or make a mockup to play with colors in an art program. |
| 20:49:47 | Araq | flaviu: when you're typesetting a book, you can pick page sizes |
| 20:49:51 | dom96 | filwit: when I make the window width smaller and the scroll to the right, the content moves left but the index stays put. That could prove problematic. |
| 20:50:08 | dom96 | *then |
| 20:50:20 | filwit | dom96: yes, last remaining issue for rendering :| |
| 20:50:22 | Araq | flaviu: and sometimes the size should be "ok, like this book over there" |
| 20:50:34 | Jehan_ | Araq: If you're typesetting a book in TeX, your publisher will worry about that. |
| 20:50:58 | Araq | Jehan_: the publisher doesn't accept TeX anyway |
| 20:51:07 | filwit | dom96: I'm going to make the sidebar collapsible, which will auto-trigger when the screen is too small (less than the min-width) |
| 20:51:08 | flaviu | Araq: Google says \pdfpaperheight=xcm \n \pdfpaperwidth=ycm |
| 20:51:34 | Araq | flaviu: now that's helpful. thanks |
| 20:51:36 | EXetoC | filwit: what do you think about css? the difficulty involved in actually adding a footer for example makes it seem as though there's something fundamentally broken about it, but I'm still inexperienced |
| 20:51:40 | Jehan_ | Araq: Then it's really not a problem, is it? :) |
| 20:51:49 | Araq | when I looked for it, google didn't turn up anything |
| 20:51:53 | dom96 | filwit: Just tested on my iPad |
| 20:51:54 | Araq | it's been a while |
| 20:51:56 | flaviu | Now, tikz really is a rabbit hole |
| 20:52:07 | dom96 | filwit: As I predicted it causes big issues on it. |
| 20:52:10 | Jehan_ | For what it's worth, I prefer to use ConTeXt over LaTeX these days. |
| 20:52:15 | EXetoC | I'll find a nice guide next time and test things with jsfiddle a little more |
| 20:52:17 | Araq | Jehan_: well you've got to create the PDF somehow |
| 20:52:28 | Araq | and the book already is in LaTeX |
| 20:52:31 | filwit | dom96: i've tested on iPad, Android (which browser kinda sux), and Windows 8.1/Phone-8.1 |
| 20:52:32 | Jehan_ | Oh, I see. |
| 20:53:33 | dom96 | filwit: the custom scrollbar is really nice |
| 20:53:38 | filwit | EXetoC: it works, and it's better than some UI design's I've used.. but it's also not the best either. I can be confusing at times (because sometimes order is dependent, but only if the top element isn't "more descriptive" in it's selector) |
| 20:53:48 | flaviu | The number of hours I sunk into http://i.imgur.com/cu6iErV.png is really ridiculous |
| 20:54:00 | EXetoC | right |
| 20:54:06 | EXetoC | and there's the whole 'clear' business |
| 20:54:48 | filwit | EXetoC: you mean float & clear? That's all pretty straight forward... just make sure your container has "overflow:auto" on it (so it properly scales) |
| 20:55:05 | filwit | dom96: glad you like them :) |
| 20:55:26 | filwit | dom96: it's too bad FF and IE don't have them |
| 20:56:56 | dom96 | indeed |
| 20:57:10 | dom96 | flaviu: what is that? And why are you sinking time into it? |
| 20:57:29 | flaviu | dom96: A while ago. A graph rendered purely with latex |
| 20:57:39 | dom96 | flaviu: oh |
| 20:58:25 | filwit | where is BitPuffin and fowl? |
| 20:58:36 | filwit | !seen BitPuffin |
| 20:58:36 | NimBot | BitPuffin was last seen on Fri Jul 25 19:46:29 2014 quitting with message: Client Quit |
| 20:58:38 | dom96 | fowl is here |
| 20:58:39 | filwit | !seen fowl |
| 20:58:39 | NimBot | fowl was last seen on Tue Sep 2 06:27:38 2014 joining #nimrod |
| 20:58:56 | filwit | oh cool |
| 20:59:00 | dom96 | BitPuffin only hangs around in #nimrod-offtopic now |
| 20:59:13 | filwit | he doesn't use Nim anymore? |
| 20:59:14 | flaviu | He's writing his own language now or something |
| 20:59:21 | filwit | ahh, i see |
| 21:00:57 | flaviu | filwit: https://bitbucket.org/BitPuffin/yig/src/3d30b6b0f4fbc0007a775fd6b868679cc5137fea/spec/spec.rst?at=default |
| 21:00:57 | flaviu | I think his language is going to be a bit weird |
| 21:01:25 | filwit | one sec |
| 21:03:31 | filwit | yeah it doesn't appeal to me, syntactically anyways |
| 21:17:36 | * | Jehan_ quit (Quit: Leaving) |
| 21:19:46 | * | gsingh93 quit (Quit: Connection closed for inactivity) |
| 21:39:32 | * | untitaker quit (Ping timeout: 260 seconds) |
| 21:44:45 | * | untitaker joined #nimrod |
| 21:57:29 | onionhammer | no happy birthday for me huh |
| 21:57:59 | dom96 | onionhammer: happy birthday! |
| 21:58:56 | * | BlaXpirit quit (Ping timeout: 255 seconds) |
| 22:00:02 | Araq | onionhammer: happy birthday! you're a hammer |
| 22:01:25 | * | noam joined #nimrod |
| 22:07:40 | Trustable | oh, I have found a mean thing: "entry1.getText() == entry2.getText()" != "$entry1.getText() == $entry2.getText()" |
| 22:08:14 | Varriount | Trustable: O_o |
| 22:08:42 | EXetoC | I might have reported this |
| 22:08:48 | dom96 | cstring vs. string? |
| 22:08:52 | EXetoC | no, that was something else |
| 22:09:10 | EXetoC | maybe |
| 22:10:22 | onionhammer | woo |
| 22:10:24 | onionhammer | thanks :) |
| 22:10:42 | onionhammer | actually my birthday was saturday |
| 22:11:42 | dom96 | Should've told us ahead of time. I would have gotten NimBot to give you a little IRC happy birthday song :P |
| 22:13:06 | Varriount | dom96: I have all the failing tests from BigBreak open in my text editor |
| 22:13:28 | dom96 | Varriount: Nice. Is that how you keep motivated? lol |
| 22:13:43 | filwit | my birthday's next Wednesday... i want a nimbot message... |
| 22:14:00 | dom96 | filwit: the 10th? |
| 22:14:04 | filwit | yeah |
| 22:14:07 | dom96 | sure. |
| 22:14:12 | dom96 | Mine's the 12th :D |
| 22:14:13 | filwit | :D |
| 22:14:14 | EXetoC | Trustable: https://github.com/Araq/Nimrod/issues/883 |
| 22:14:18 | filwit | on, cool |
| 22:14:25 | filwit | Virgos! |
| 22:14:45 | dom96 | filwit: :D |
| 22:14:51 | EXetoC | now I want to control the memory layout of variants |
| 22:15:01 | EXetoC | cus, stupid struct definition :< |
| 22:15:04 | Trustable | nice to see the issue |
| 22:15:13 | EXetoC | value_type, padding, value |
| 22:21:36 | * | shodan45 joined #nimrod |
| 22:22:23 | * | nande quit (Read error: Connection reset by peer) |
| 22:28:36 | Varriount | dom96: You need to fix the await macro |
| 22:28:38 | * | io2 joined #nimrod |
| 22:28:47 | * | io2 quit (Changing host) |
| 22:28:47 | * | io2 joined #nimrod |
| 22:29:23 | * | nande joined #nimrod |
| 22:29:47 | dom96 | Varriount: what's wrong with it? |
| 22:30:07 | Varriount | I'm getting macro errors in many of the async tests |
| 22:30:30 | Araq | good night |
| 22:32:44 | dom96 | just let me fix them |
| 22:33:51 | * | bjz quit (Read error: Connection reset by peer) |
| 22:33:57 | * | bjz_ joined #nimrod |
| 22:34:27 | * | flaviu quit (Quit: Leaving.) |
| 22:34:53 | EXetoC | Trustable: yeah, I'll re-open it after this release. it has been a while |
| 22:43:40 | * | Matthias247 quit (Read error: Connection reset by peer) |
| 22:54:56 | * | filwit quit (Quit: Leaving) |
| 23:03:54 | * | Demos joined #nimrod |
| 23:22:37 | * | darkf joined #nimrod |
| 23:23:16 | * | brson quit (Quit: leaving) |
| 23:23:56 | * | brson joined #nimrod |
| 23:29:22 | * | io2 quit (Quit: ...take irc away, what are you? genius, billionaire, playboy, philanthropist) |
| 23:36:59 | * | Boscop__ quit (Read error: Connection reset by peer) |
| 23:37:19 | * | Boscop joined #nimrod |
| 23:41:43 | * | Boscop quit (Read error: Connection reset by peer) |
| 23:42:37 | * | Boscop joined #nimrod |
