1 2012-03-31T00:28:05 <RogerHaase> ThomasWaldmann: fix for HTML5 errors caused by meta tags with unregistered names: http://codereview.appspot.com/5967050/
2 2012-03-31T00:45:01 <RogerHaase> ThomasWaldmann: example of error (you must be at tip, logged in, and have show comments selected in options): http://test.moinmo.in/MetaNameError
3 2012-03-31T01:15:24 *** brunomartin
4 2012-03-31T01:17:26 <ThomasWaldmann> RogerHaase: aren't all those <br> creating empty lines?
5 2012-03-31T01:26:49 <ThomasWaldmann> ah, display none, ok
6 2012-03-31T01:47:54 <ThomasWaldmann> (sorry, was rather sleepy some hours ago)
7 2012-03-31T01:48:30 <RogerHaase> ThomasWaldmann: must be very late there
8 2012-03-31T01:51:02 <ThomasWaldmann> NOW it's rather late and I am wake again :D
9 2012-03-31T01:57:24 <RogerHaase> gtg
10 2012-03-31T01:57:28 *** RogerHaase
11 2012-03-31T02:58:21 *** ayrus12
12 2012-03-31T04:33:26 *** MattMaker
13 2012-03-31T04:51:50 *** sudo_dirk
14 2012-03-31T05:06:13 *** sudo_dirk
15 2012-03-31T06:13:56 *** _mayank
16 2012-03-31T09:24:26 *** _mayank
17 2012-03-31T10:13:43 *** jaiditya
18 2012-03-31T10:31:47 *** ayrus12
19 2012-03-31T11:16:54 *** _mayank
20 2012-03-31T11:44:30 *** _mayank
21 2012-03-31T11:55:00 *** greg_f
22 2012-03-31T12:14:20 *** jaiditya
23 2012-03-31T12:31:23 *** _mayank
24 2012-03-31T13:13:18 *** kanha
25 2012-03-31T13:17:29 <kanha> eSyr:waldi:moin
26 2012-03-31T14:20:29 *** kanha__
27 2012-03-31T14:21:00 *** kanha_
28 2012-03-31T14:32:18 *** sudo_dirk
29 2012-03-31T14:32:41 *** sudo_dirk
30 2012-03-31T14:35:02 *** kanha
31 2012-03-31T14:36:34 *** kanha
32 2012-03-31T15:37:04 *** RogerHaase
33 2012-03-31T16:13:49 <xiaq> Moin
34 2012-03-31T16:13:57 <xiaq> On the issue tracker proposal:
35 2012-03-31T16:14:14 <xiaq> I guess it could be done like this
36 2012-03-31T16:15:18 <xiaq> * Invent a new mimetype for issues, say text/x.moin.issue
37 2012-03-31T16:15:55 <xiaq> That shows a nice form to change the issue properties, add new comments on rendering
38 2012-03-31T16:15:58 *** DasIch_
39 2012-03-31T16:16:45 <xiaq> * Comments can be plain wiki pages...
40 2012-03-31T16:17:30 <xiaq> * The issue page needs to do a fancy <<Include()>> to aggregate the comments plus some metadata of each comment (creator, creation date)
41 2012-03-31T16:18:22 *** DasIch
42 2012-03-31T16:18:22 *** DasIch_
43 2012-03-31T16:35:42 <ThomasWaldmann> moin
44 2012-03-31T16:36:05 <xiaq> moin :)
45 2012-03-31T16:36:16 <ThomasWaldmann> kanha__: do not personally address (highlight) people if you are not going to ask/tell them something
46 2012-03-31T16:37:12 <kanha__> ok
47 2012-03-31T16:37:55 <xiaq> ThomasWaldmann: How do you find my thoughts about the issue tracker?
48 2012-03-31T16:38:08 <ThomasWaldmann> xiaq: i think i already mentioned that i would prefer to first have a simple implementation that does not involved "threaded" or otherwise separate discussions. Maybe keep that in a separate step.
49 2012-03-31T16:40:44 <xiaq> ThomasWaldmann: Okay. What about the idea of using a separate mimetype for issues? It doesn't feel optimal even to me, as other mimetypes (crelo, moin, ...) are for data formats instead of semantics
50 2012-03-31T16:42:15 <ThomasWaldmann> well, we could think if we want to control rendering in some slightly different way than just by mimetype
51 2012-03-31T16:42:46 <xiaq> ThomasWaldmann: Metadata property?
52 2012-03-31T16:43:05 <ThomasWaldmann> there are other places where this is visible also, e.g. if you have a text/x-python mimetype you could render it in a highlighted way or just as plain text
53 2012-03-31T16:43:50 <ThomasWaldmann> also for wiki markup: plain text, highlighted text or rendered?
54 2012-03-31T16:44:20 <xiaq> ThomasWaldmann: ? I didn't quite get your last comment
55 2012-03-31T16:44:43 <ThomasWaldmann> that's the ways you could present wiki markup data
56 2012-03-31T16:51:41 <ThomasWaldmann> xiaq: btw, i don't think you primarily want to influence how DATA is rendered / dealt with
57 2012-03-31T16:53:06 *** kanha
58 2012-03-31T16:58:58 <RogerHaase> ThomasWaldmann: any comments on http://codereview.appspot.com/5967050/? I am wondering if I should have left theme_supp.meta_items as it was. With my change it is poorly named.
59 2012-03-31T17:05:21 <xiaq> ThomasWaldmann: Hm... What should be worked on then? To me the storage layer is already flexible enough...
60 2012-03-31T17:09:58 <ThomasWaldmann> xiaq: well, it sounds like you want to show and edit metadata differently
61 2012-03-31T17:11:12 <xiaq> ThomasWaldmann: Yes, that seems the primary issue to me
62 2012-03-31T17:11:55 <ThomasWaldmann> RogerHaase: well, the meta elements looked a bit more elegant, but if it is invalid to use them like that, we don't have a big choice
63 2012-03-31T17:12:41 <ThomasWaldmann> btw, we do not have "system pages" currently, they are just views now
64 2012-03-31T17:12:41 <xiaq> ThomasWaldmann: I remember the time I asked why moin1 was not great for issue tracking
65 2012-03-31T17:13:13 <xiaq> One of the problems you mentioned was editing the issue properties by hand is cumbersome
66 2012-03-31T17:13:28 <xiaq> Another is due to limited searching capability of moin1
67 2012-03-31T17:13:36 <ThomasWaldmann> xiaq: yeah, sure
68 2012-03-31T17:14:12 <xiaq> So I suppose these are the two primary issues to be tackled
69 2012-03-31T17:15:18 <ThomasWaldmann> RogerHaase: i guess the edit-on-doubleclick stuff should not be in base.html, but maybe rather in show.html or so
70 2012-03-31T17:15:56 <ThomasWaldmann> xiaq: yes, that is solved by showing and modifying metadata in a nice way
71 2012-03-31T17:18:57 <xiaq> ThomasWaldmann: So... I wonder what are the important stuff besides 1) rendering and modifying metadata 2) a nice index ? I haven't thought of much
72 2012-03-31T17:19:20 <ThomasWaldmann> thinking about the right metadata keys and values
73 2012-03-31T17:20:21 <ThomasWaldmann> (and showing and modifying metadata values in a good, pretty, generic way is already a bigger task IMHO)
74 2012-03-31T17:20:57 <xiaq> Oh yes the schema stuff
75 2012-03-31T17:21:52 <xiaq> Roundup gets around this by placing virtually all templates in the site configuration directory
76 2012-03-31T17:22:31 <xiaq> So the tracker administrator would also have to modify the template when changing the schema
77 2012-03-31T17:22:49 <RogerHaase> ThomasWaldmann: I was thinking that a custom theme may want to add meta tags for author, description, application-name, or keywords. So I will put that back as was for next try.
78 2012-03-31T17:22:58 <ThomasWaldmann> (just look at Bitbucket's "priority" key and its values to see how NOT to do it)
79 2012-03-31T17:28:36 <xiaq> What is terribly wrong with bb's the priority key?
80 2012-03-31T17:28:54 <xiaq> Is it that the values are predefined?
81 2012-03-31T17:30:06 <xiaq> And... cannot be changed?
82 2012-03-31T17:30:22 <ThomasWaldmann> key and values are mostly wrong
83 2012-03-31T17:31:32 <ThomasWaldmann> you'll have to do better ;)
84 2012-03-31T17:32:19 <xiaq> ThomasWaldmann: Is the value set fixed? If not that would not be a problem
85 2012-03-31T17:32:31 <xiaq> A customization schema is what I had in mind from the beginning
86 2012-03-31T17:33:36 <xiaq> Predefined schema is absurd
87 2012-03-31T17:33:51 <ThomasWaldmann> we can keep customization in mind, but doing a simple and versatile thing at the beginning sounds reasonable for me
88 2012-03-31T17:34:44 <ThomasWaldmann> you can have a look at githubs and bitbuckets issues trackers. they are rather simple, nevertheless they can be (and get) used
89 2012-03-31T17:35:41 <xiaq> oh... s/customization/customizable/ for my last but one comment
90 2012-03-31T17:35:56 <xiaq> (although doens't make much difference :) )
91 2012-03-31T17:36:25 <ThomasWaldmann> otoh, there are very big and customizable issue trackers and the sheer volume of features, attributes, etc. sometimes seems rather repelling than encouraging
92 2012-03-31T17:38:04 <xiaq> No I'll do it very small and customizable :)
93 2012-03-31T17:38:55 <xiaq> And if I set the schema customization stuff aside for the moment, "showing and modifying metadata values in a good, pretty, generic way" doesn't seem big to me at all
94 2012-03-31T17:39:09 <ThomasWaldmann> it is :)
95 2012-03-31T17:39:21 <xiaq> Only when the schema is fully customizable will it be tricky to do it right...
96 2012-03-31T17:39:37 <xiaq> Hm?
97 2012-03-31T17:40:07 <xiaq> There is already Flatland and Jinja2 isn't there :)
98 2012-03-31T17:40:37 <xiaq> I think the task would be just to plug them in...?
99 2012-03-31T17:40:41 <ThomasWaldmann> what I would like to see is that when new code is written (like when triggered by some issuetracker requirement), that we'll have a look then whether this is a special requirement or whether we need that thing at a lot of other places also
100 2012-03-31T17:41:16 <ThomasWaldmann> if the latter is the case, it should not get hardcoded just in the issuetracker, but done in a reusable way
101 2012-03-31T17:41:38 <ThomasWaldmann> or even done in a generic way, so other places immediately take advantage from it
102 2012-03-31T17:41:39 <xiaq> Totally agreed
103 2012-03-31T17:41:59 <xiaq> That is one of the issues that keeps troubling me
104 2012-03-31T17:43:43 <xiaq> So when you said the metadata rendering and modifying stuff is big you meant it would be big to do it in a reusable way, instead of just for issue tracker. Am I right?
105 2012-03-31T17:44:20 <ThomasWaldmann> yes. and also doing it in a way that makes sure stuff is valid.
106 2012-03-31T17:44:46 <ThomasWaldmann> so basically we need some flatland stuff for that and widgets...
107 2012-03-31T17:44:52 <xiaq> Yes
108 2012-03-31T17:46:13 <xiaq> Instead of implementing an issue editor
109 2012-03-31T17:46:23 <xiaq> I got to implement a generic metadata editor
110 2012-03-31T17:46:28 <xiaq> And it should looks nice :)
111 2012-03-31T17:46:33 <xiaq> s/looks/look/
112 2012-03-31T17:53:05 <ThomasWaldmann> first application on melange!
113 2012-03-31T17:53:33 <ThomasWaldmann> (but it can be safely ignored as it didn't have much interesting content)
114 2012-03-31T17:54:30 <ThomasWaldmann> xiaq: yeah, sounds a bit like that :)
115 2012-03-31T17:58:19 <RogerHaase> ThomasWaldmann: try 2 for meta tags fix: http://codereview.appspot.com/5967050/
116 2012-03-31T18:04:04 *** sudo_dirk
117 2012-03-31T18:05:32 * ThomasWaldmann fixed the application template on melange (now as that field is editable, it wasn't at the time when I filled it out)
118 2012-03-31T18:12:15 <ThomasWaldmann> RogerHaase: done
119 2012-03-31T18:14:03 *** dwcramer
120 2012-03-31T18:18:35 *** yufra_
121 2012-03-31T18:18:53 *** sudo_dirk
122 2012-03-31T18:47:00 <ThomasWaldmann> dwcramer: thanks for updating the ideas page (sorry, was rather busy yesterday, so couldn't answer your mails)
123 2012-03-31T18:47:39 <ThomasWaldmann> btw, it is sometimes a bit unclear whether you are referring to moin 1.9 or 2.0
124 2012-03-31T18:51:22 <dwcramer> No problem. I'll take a look at what I added and clarify that I mean 2.0 (though I haven't played with 2.0 yet, so I may not know what I'm talking about).
125 2012-03-31T18:51:31 <dwcramer> s/may not know/do not know/
126 2012-03-31T18:53:10 <ThomasWaldmann> dwcramer: hehe, maybe you should have a look at moin2 first
127 2012-03-31T18:53:36 <ThomasWaldmann> we have good docs now, so getting and installing it is no big issue
128 2012-03-31T18:54:20 <ThomasWaldmann> the point is that moin 2.0 is not just 1.9 + 0.1, it is radically different
129 2012-03-31T18:56:48 <ThomasWaldmann> (so, stuff that is in 1.9 is not necessarily also present in 2.0, and vice versa)
130 2012-03-31T18:57:22 *** dwcramer
131 2012-03-31T19:07:02 <RogerHaase> ThomasWaldmann: added id to div and moved it to end of body: http://codereview.appspot.com/5967050/
132 2012-03-31T19:22:26 *** yufra_
133 2012-03-31T19:35:40 *** greg_f
134 2012-03-31T19:41:21 <ThomasWaldmann> RogerHaase: done
135 2012-03-31T19:56:55 <dreimark> jo, hast recht, nur irgendwie hab ich in erinnerung das saetze in english auch nicht so lang sind
136 2012-03-31T20:10:05 <dreimark> sorry wrong channel
137 2012-03-31T20:36:03 <RogerHaase> ThomasWaldmann: not sure if this is what you meant: http://codereview.appspot.com/5967050/
138 2012-03-31T20:37:04 <ThomasWaldmann> RogerHaase: yeah, think that is right. did you look at other places that use super?
139 2012-03-31T20:41:06 <RogerHaase> yes, as I understand it, templates that extend show.html, can call super() and then define additional items. Templates that extend layout can define their own entries, but not call super().
140 2012-03-31T20:49:56 <RogerHaase> ThomasWaldmann: was that an OK to push?
141 2012-03-31T20:55:58 <ThomasWaldmann> well, super() is a jinja2 mechanism, it is not related to our templates
142 2012-03-31T20:56:21 <ThomasWaldmann> and it just puts whatever it finds one layer higher in the same block
143 2012-03-31T20:56:40 <ThomasWaldmann> so if the div is in the block, it would nest badly
144 2012-03-31T21:04:44 <RogerHaase> the jinja docs say super calls parent, but show.html calls super() within head_links which is defined in base, a grandparent. Head_links is not used in layout, the parent.
145 2012-03-31T21:14:41 <ThomasWaldmann> hmm, looking...
146 2012-03-31T21:15:42 <ThomasWaldmann> RogerHaase: it is in base.html
147 2012-03-31T21:19:51 <ThomasWaldmann> RogerHaase: hmm, if we need to put such javascript options into other templates also, it might make sense to have an empty one in base.html (or at least in some rather fundamental template) and just fill it from whereever we need it
148 2012-03-31T21:34:09 *** _mayank
149 2012-03-31T21:40:43 <RogerHaase> ThomasWaldmann: like this? http://codereview.appspot.com/5967050/
150 2012-03-31T21:42:35 <RogerHaase> layout is now unchanged, end result is to move stuff around in base. seems better to me.
151 2012-03-31T21:44:29 <RogerHaase> As of now, the only other thing that extends base is content.html
152 2012-03-31T21:45:51 <ThomasWaldmann> RogerHaase: ok
153 2012-03-31T21:50:52 <RogerHaase> ThomasWaldmann: pushed to https://bitbucket.org/RogerHaase/moin-2.0
154 2012-03-31T21:53:20 <CIA-41> Roger Haase <crosseyedpenguin@yahoo.com> default * 1317:ce5454f5edaa 2.0/MoinMoin/ (5 files in 3 dirs): CSS cleanup, remove unused selectors, fixes #172 align columns of integers to right, partial fix for #165 html errors on +modify
155 2012-03-31T21:53:22 <CIA-41> Roger Haase <crosseyedpenguin@yahoo.com> default * 1318:013de4f3dc4b 2.0/MoinMoin/converter/ (_tests/test_include.py include.py link.py): transclusion cleanup - change html.div > moin_page.div; remove unused import html; delete unwanted comment
156 2012-03-31T21:53:23 <CIA-41> Roger Haase <crosseyedpenguin@yahoo.com> default * 1320:8fa27ecd73f8 2.0/MoinMoin/ (static/js/common.js templates/base.html templates/show.html): eliminate HTML5 validation errors caused by meta tags with unregistered names
157 2012-03-31T21:53:24 <CIA-41> Roger Haase <crosseyedpenguin@yahoo.com> default * 1319:97398f9a6324 2.0/MoinMoin/ (5 files in 3 dirs): merge
158 2012-03-31T22:17:01 <ThomasWaldmann> DasIch: playing with your twitter macro
159 2012-03-31T22:17:26 <DasIch> ThomasWaldmann: ok
160 2012-03-31T22:17:38 <ThomasWaldmann> shouldn't <<Twitter("#galaxy #note")>> give the same stuff as entering #galaxy #note on twitter search?
161 2012-03-31T22:18:10 <DasIch> ThomasWaldmann: I suppose it should
162 2012-03-31T22:18:50 <ThomasWaldmann> try :)
163 2012-03-31T22:22:00 <DasIch> ThomasWaldmann: I have no idea why there might be differences
164 2012-03-31T22:22:36 <DasIch> ThomasWaldmann: than again twitter search is weird
165 2012-03-31T22:26:41 <ThomasWaldmann> DasIch: urllib.? is happy with unicode urls?
166 2012-03-31T22:27:13 <DasIch> ThomasWaldmann: I suppose twitter search might take location into account or uses a different source
167 2012-03-31T22:28:26 <ThomasWaldmann> yeah, might be
168 2012-03-31T22:28:43 <ronny> shouldnt a twitter macro try to use js instead of servere side call out to twitter?
169 2012-03-31T22:29:54 <ThomasWaldmann> good question. they have a comparable api for js?
170 2012-03-31T22:31:23 <DasIch> ThomasWaldmann: they have a streaming api
171 2012-03-31T22:32:16 <DasIch> this appears to be what search.twitter.com uses
172 2012-03-31T22:38:33 <ThomasWaldmann> https://dev.twitter.com/docs/api
173 2012-03-31T22:40:08 <ThomasWaldmann> btw, one other issue of that macro code is that it only works as a macro. we can't easily embed it into theme sidebar.
174 2012-03-31T22:41:11 <ThomasWaldmann> (maybe this is due to it was being written just for being a macro)
175 2012-03-31T23:58:58 *** RogerHaase
176
