1 2013-06-16T01:11:48 <ThomasWaldmann> http://jquerymobile.com/themeroller/ nice
2 2013-06-16T03:23:30 *** Guest31970
3 2013-06-16T03:58:01 <xiaq> ThomasWaldmann: for 5" 1920x1080 devices... css px is not a physical px: https://developer.mozilla.org/en-US/docs/Web/CSS/length#Absolute_length_units
4 2013-06-16T03:58:54 * xiaq didn't read the whole chat log, so that may be already addressed :)
5 2013-06-16T04:04:02 <xiaq> anyway, the takeaway is that a css pixel is roughly 1/96 inch (most of the time exactly 1/96, but that doesn't seem guaranteered) regardless of the display density
6 2013-06-16T04:41:52 *** ashutosh1461
7 2013-06-16T04:45:43 <ashutosh1461> moin ThomasWaldmann
8 2013-06-16T05:29:50 <ashutosh1461> ThomasWaldmann, also one cr was pending https://codereview.appspot.com/8709049/ please read description.
9 2013-06-16T05:59:11 <sharky93> moin
10 2013-06-16T06:42:24 <sharky93> ThomasWaldmann, TheSheep are we looking and keeping in mind a prospective move to bootstrap in the future?
11 2013-06-16T08:28:54 *** ashutosh1461
12 2013-06-16T08:28:59 *** ashutosh_singla1
13 2013-06-16T09:10:07 *** ana_ananasova
14 2013-06-16T09:15:42 *** ashutosh_singla1
15 2013-06-16T12:10:14 <ThomasWaldmann> moin
16 2013-06-16T12:12:49 <ThomasWaldmann> xiaq: oh, how great! so a cm is not a cm, and a px is not a px. :|
17 2013-06-16T12:18:30 <ThomasWaldmann> asingla: ah, right, i need to patch that into the src and look at more context...
18 2013-06-16T12:19:11 <ThomasWaldmann> sharky93: not sure how that should make a difference
19 2013-06-16T12:20:47 <sharky93> ThomasWaldmann, i guess still bootstrap is the best and the most popular one
20 2013-06-16T12:21:51 <ThomasWaldmann> https://github.com/twitter/bootstrap/issues/2054 working on it since a year, still no timeframe and rather quiet recently
21 2013-06-16T13:13:33 <sharky93> ThomasWaldmann, herein they say that v3 is almost ready to be released
22 2013-06-16T13:13:41 <sharky93> this is a statement on 17th May.
23 2013-06-16T13:13:50 <sharky93> http://blog.getbootstrap.com/2013/05/17/bootstrap-2-3-2-released/
24 2013-06-16T13:28:01 <xiaq> ThomasWaldmann: no, a cm is still a cm
25 2013-06-16T13:31:50 <xiaq> also, i was mistaken - a css pixel is quite likely not 1/96in except on 96dpi displays, since a css pixel maps to an integer number of device pixels most of the time
26 2013-06-16T13:32:25 <xiaq> so for a 108dpi display a css pixel *is* one device pixel, but for 192dpi devices it's 2
27 2013-06-16T13:32:51 <sharky93> TheSheep, ping
28 2013-06-16T13:37:18 <waldi> xiaq: "Alternatively if the anchor unit is a physical unit, the pixel unit might not map to a whole number of device pixels."
29 2013-06-16T13:37:32 <waldi> css pixels are not always whole numbers
30 2013-06-16T14:02:58 <TheSheep> sharky93: yes?
31 2013-06-16T14:03:53 <sharky93> TheSheep, do we need to evaluate any more frameworks? and how do we plan to handle bootstrap ( if at all )?
32 2013-06-16T14:17:30 *** ana_ananasova
33 2013-06-16T14:18:24 <TheSheep> ThomasWaldmann: looks like there are two "no" https://docs.google.com/spreadsheet/ccc?key=0Aq4ThyUfrogvdDZRZUxtUFIzT1VFeFRQTlkzZE1RcUE#gid=0
34 2013-06-16T14:22:04 <TheSheep> "All this GPLv2 project should just upgrade to GPLv3 and everytihg would be fine!"
35 2013-06-16T14:23:30 <TheSheep> right...
36 2013-06-16T14:24:24 <sharky93> TheSheep, ThomasWaldmann http://blog.getbootstrap.com/ in the plans for v3 they've mentioned about the shift to MIT
37 2013-06-16T14:25:25 <TheSheep> sharky93: can't see any mention
38 2013-06-16T14:26:02 <sharky93> TheSheep, find "MIT" it'll take you straight to it.
39 2013-06-16T14:26:06 <TheSheep> ah http://blog.getbootstrap.com/2012/12/10/bootstrap-3-plans/
40 2013-06-16T14:29:40 <sharky93> TheSheep, it is getting rather confusing now with the framework shift plans ?
41 2013-06-16T14:35:31 <TheSheep> it is
42 2013-06-16T14:36:04 <TheSheep> we should concentrate on what we have already planned that doesn't require a framework, and revisit this after it clears a little
43 2013-06-16T14:36:20 <TheSheep> I would really love to use bootstrap, it's the most mature one and I'm familiar with it
44 2013-06-16T14:41:22 <sharky93> TheSheep, hmm, the most popular one for a reason! :)
45 2013-06-16T14:42:41 <TheSheep> that reason being marketing
46 2013-06-16T14:43:00 <TheSheep> but then once it is popular, it also attracts contributors and gets better
47 2013-06-16T14:49:35 <sharky93> hmm
48 2013-06-16T15:10:09 <sharky93> TheSheep, coding starts from tomorrow.. we start with i18n ?
49 2013-06-16T15:10:57 <TheSheep> sharky93: yes, i18n and then lint
50 2013-06-16T15:11:38 <TheSheep> ThomasWaldmann: can we try using the review that is now built into bitbucket?
51 2013-06-16T15:12:24 <TheSheep> ThomasWaldmann: it seems to be much easier to use, at least for me
52 2013-06-16T15:24:49 <sharky93> TheSheep, do you have an approximate in mind for the completion of this task?
53 2013-06-16T15:36:24 <TheSheep> sharky93: 4 days for the i18n stuff, at the outside, I think, but we will see (and programmer estimates are always optimistic)
54 2013-06-16T15:37:44 <TheSheep> sharky93: assuming 8h/day of work
55 2013-06-16T15:40:36 <sharky93> TheSheep, no issues with time here :) im jobless ;)
56 2013-06-16T15:41:07 <TheSheep> motivation is still a tricky thing
57 2013-06-16T15:42:14 <ThomasWaldmann> TheSheep: i don't thing gplv3 is a solution, it just gets us from the apache license v2 issue into some other licensing issues (like gpl v2 incompatibility)
58 2013-06-16T15:42:22 <ThomasWaldmann> think*
59 2013-06-16T15:43:12 <sharky93> i think i'm motivated enough :) has got me this far
60 2013-06-16T15:44:23 <waldi> we can relicense the css stuff to gpl3+ and let the code stay at gpl2+. so people can replace the theme to get a full gpl2 compliant version
61 2013-06-16T15:44:54 <sharky93> we can do that? :O
62 2013-06-16T15:46:54 <TheSheep> ThomasWaldmann: yes, I know
63 2013-06-16T15:47:19 <ThomasWaldmann> waldi: we don't need to relicense the css stuff for that. but it also doesn't really solve anything.
64 2013-06-16T15:49:24 <ThomasWaldmann> somehow the jquery-mobile is tempting...
65 2013-06-16T15:51:30 * sharky93 feels they'll release bootstrap v3 right in the middle of our plans with the licenses fixed :P
66 2013-06-16T15:52:40 <TheSheep> ThomasWaldmann: but that requires js :(
67 2013-06-16T15:53:01 * ThomasWaldmann feels like that will fall into sleep mode again and never be changed.
68 2013-06-16T15:54:02 <ThomasWaldmann> TheSheep: requirements aren't engraved in stone. the overall goodness is somehow the key.
69 2013-06-16T15:55:08 <ThomasWaldmann> if we would go j-m and get a great and easy UI for mobile and desktop, that is even great and easy for devs, we can maybe live with that users without js get a very simple UI.
70 2013-06-16T15:55:28 <TheSheep> if we require js, then we could do all the wiki markup parsing on the browser side too! ;)
71 2013-06-16T15:55:57 <ThomasWaldmann> no, i don't want that, i don't want to code in js
72 2013-06-16T15:56:41 <TheSheep> just kidding
73 2013-06-16T15:56:47 <waldi> you can use rpython to js
74 2013-06-16T15:57:00 <TheSheep> you still have to debug js
75 2013-06-16T15:57:25 <ThomasWaldmann> but above is preferable to going with a not-so-popular framework that will be stopped to be maintained in 2y, that looks worse (like smarties and win8).
76 2013-06-16T15:58:57 <TheSheep> ThomasWaldmann: about that support, this summarises it: https://en.wikipedia.org/wiki/JQuery_Mobile#Mobile_browser_support
77 2013-06-16T16:00:13 <TheSheep> ThomasWaldmann: (note that with bootstrap we get an A everywhere)
78 2013-06-16T16:01:16 <ThomasWaldmann> that table seems outdated
79 2013-06-16T16:01:33 <ThomasWaldmann> v2.2 is the latest android ther
80 2013-06-16T16:01:34 <ThomasWaldmann> e
81 2013-06-16T16:03:28 <ThomasWaldmann> (and some stuff there I've never heard from before)
82 2013-06-16T16:03:41 <TheSheep> I doubt they added support for any of the ones marked as not supported there
83 2013-06-16T16:04:22 <TheSheep> sharky93: do you think you could try jquery-mobile mockup too?
84 2013-06-16T16:04:48 <ThomasWaldmann> isn't the leftmost column there the most important one? + chrome/ff/opera on mobile?
85 2013-06-16T16:06:17 <TheSheep> yes
86 2013-06-16T16:06:35 <ThomasWaldmann> (and isn't fennec called firefox since 2009?)
87 2013-06-16T16:08:08 <TheSheep> http://jquerymobile.com/gbs/
88 2013-06-16T16:08:13 <TheSheep> here's the updated version
89 2013-06-16T16:08:52 <ThomasWaldmann> right, just wanted to point to that, looks quite better (of course ;)
90 2013-06-16T16:09:29 <TheSheep> I'm also a little concerned about ajax page loading
91 2013-06-16T16:09:43 <TheSheep> this is a can of worms that I don't want to open
92 2013-06-16T16:10:44 <TheSheep> I have only used it with small apps, and that was fine there
93 2013-06-16T16:10:58 *** ashutosh1461
94 2013-06-16T16:11:19 <ThomasWaldmann> well, if one does not have to implement it all oneself piece-per-piece, it's maybe not that bad
95 2013-06-16T16:11:32 <TheSheep> but I have a vision of some user with a broken web server setup coming complaining that his pages don't load and then us tryiung to debug that
96 2013-06-16T16:11:38 <ThomasWaldmann> iirc we have ajax for the settings stuff right now?
97 2013-06-16T16:12:19 <TheSheep> what jquery mobile does is replacing whole pages using ajax, instead of just going to a new page with a browser
98 2013-06-16T16:12:38 <ThomasWaldmann> you mean that normal requests work and ajax don't?
99 2013-06-16T16:13:24 * ThomasWaldmann is not aware that this is a usual web server configuration issue, is it?
100 2013-06-16T16:14:03 <TheSheep> no idea what may be wrong, but imagining myself in a situation where I have to explain to an user how to use the network tab in an inspector to see what is going on doesn't make me optimistic
101 2013-06-16T16:14:13 <ashutosh1461> ThomasWaldmann, i need help in finalizing the ideas to start coding asap.
102 2013-06-16T16:14:23 <TheSheep> it's just my cynical side, I guess
103 2013-06-16T16:15:09 <ThomasWaldmann> TheSheep: guess there would be 2 ways: one to say to try against our server and if it doesn't work, it is not a moin problem. :D other to debug it ourselves against their servers.
104 2013-06-16T16:15:25 <ThomasWaldmann> ehrm "if it does work"*
105 2013-06-16T16:15:48 <TheSheep> I'm a big fan of "the simplest that could possibly work" :)
106 2013-06-16T16:16:22 <TheSheep> but sure, let's try it
107 2013-06-16T16:16:54 <ThomasWaldmann> yeah, me too. but otoh people are complaining about moin ui since a decade (rightfully, at least to some part).
108 2013-06-16T16:17:58 <TheSheep> by the way, even if we make the UI using jquery mobile, that will not magically make the wiki content accessible on mobile
109 2013-06-16T16:18:30 <ThomasWaldmann> accessible like for blind, or at all?
110 2013-06-16T16:18:35 <TheSheep> at all
111 2013-06-16T16:18:51 <ThomasWaldmann> example?
112 2013-06-16T16:19:07 <TheSheep> try resizing this: http://jquerymobile.com/demos/1.3.0/docs/examples/tables/movie-list.html
113 2013-06-16T16:19:45 <TheSheep> this is some very smart solution to the problem of small screens
114 2013-06-16T16:19:45 <ThomasWaldmann> yeah, i've seen this, pretty nice.
115 2013-06-16T16:20:00 <TheSheep> but to actually use that, the content has to be prepared for that with additional markup
116 2013-06-16T16:20:37 <ThomasWaldmann> but at least jm has something for this and we don't need to reinvent it, just use it.
117 2013-06-16T16:20:56 <TheSheep> I still think that most of moin's ui problems are not due to bad looks or using wrong technical solutions, but due to the fact that they come directly from the implementation instead of being designed from the user's point of view
118 2013-06-16T16:21:24 <TheSheep> sure, it makes it very flexible and easy to extend and hack
119 2013-06-16T16:22:27 <TheSheep> nore that it's not something wrong
120 2013-06-16T16:22:44 <TheSheep> it's just the result of how moin was created and who is using it
121 2013-06-16T16:23:50 <TheSheep> I'm not even sure if it's worth "fixing"
122 2013-06-16T16:25:08 <ThomasWaldmann> the problem (for me) is that if UI development is a pain for me, I don't like doing it. If it would be less pain, I maybe would enjoy it.
123 2013-06-16T16:25:53 <TheSheep> fair enough
124 2013-06-16T16:28:11 <ThomasWaldmann> (and there is also stuff, I simply can't do yet, like creating great colour palettes or generally visually impressive output)
125 2013-06-16T16:28:39 <ThomasWaldmann> if that we given by default somehow, it would be already a big step forwards.
126 2013-06-16T16:28:44 <ThomasWaldmann> was*
127 2013-06-16T16:28:50 <TheSheep> I think that's less important than intuitive organisation
128 2013-06-16T16:29:08 <TheSheep> yeah, remove the design from the default theme
129 2013-06-16T16:29:22 <TheSheep> make it as plain as possible while still looking good
130 2013-06-16T16:30:50 <ThomasWaldmann> sharky93: can you update EP with ALL stuff we know meanwhile for the different frameworks. and also do detailled planning for the stuff next week?
131 2013-06-16T16:32:19 <ThomasWaldmann> I'll play a bit with gumby on my tablet later, but currently I am somehow more impressed by j-m / feeling more save concerning future support/maintenance with it.
132 2013-06-16T16:33:00 <ThomasWaldmann> (just have a look at flatland what few users of something can mean)
133 2013-06-16T16:33:34 <TheSheep> ThomasWaldmann: how about that bootstrap, if they finally get the license cleared?
134 2013-06-16T16:33:55 <ThomasWaldmann> i don't think that will happen in a week or so.
135 2013-06-16T16:34:42 <ThomasWaldmann> if it happens later, we can use it later (some guy even started working with it for moin, ignoring the license issues)
136 2013-06-16T16:35:53 <ThomasWaldmann> i just fear that if we don't use any reasonable framework rather soon, we'll continue reinventing the wheel.
137 2013-06-16T16:36:49 <ThomasWaldmann> s/any/some/
138 2013-06-16T16:38:41 <ThomasWaldmann> like the stuff sharky93 sugggested - it is readily available in such framework. just use it, instead of rewriting it.
139 2013-06-16T16:40:12 * ThomasWaldmann brb
140 2013-06-16T17:38:05 *** ana_ananasova
141 2013-06-16T17:46:20 <sharky93> TheSheep, ThomasWaldmann sure i can try a mockup using j-m
142 2013-06-16T17:48:11 <sharky93> TheSheep, do we drop the plans for improving the current ui?
143 2013-06-16T17:55:20 <sharky93> I mean, the plans which do not involve the use of a framework
144 2013-06-16T18:05:31 *** ana_ananasova
145 2013-06-16T18:06:59 <sharky93> TheSheep, how about working on a different theme, rather than trying to imitate FooBar or Modernized ..
146 2013-06-16T18:07:17 <sharky93> i mean the basic layout which could be more user-friendly
147 2013-06-16T18:07:41 <sharky93> TheSheep, this is a very good blend of FooBar and Modernized layouts @ http://api.jquerymobile.com/
148 2013-06-16T18:08:10 <sharky93> TheSheep, ThomasWaldmann notice the cool way in which they collapse it with a reduced width.
149 2013-06-16T18:09:03 <sharky93> we could maybe use the horizontal bar as what FooBar does with the left navigation bar ..
150 2013-06-16T18:09:17 <sharky93> and they vertical nav for page specific views ?
151 2013-06-16T18:09:18 <sharky93> *the
152 2013-06-16T18:10:48 *** ana_ananasova
153 2013-06-16T18:22:17 * ThomasWaldmann does a j-m tutorial
154 2013-06-16T18:27:34 <ThomasWaldmann> sharky93: yeah, it's nice how it adapts
155 2013-06-16T18:29:45 <TheSheep> sharky93: it's all fine and dandy, but I think there are some more fundamental problems to be solved first, like organizing that views menu
156 2013-06-16T18:31:00 <ashutosh1461> ThomasWaldmann, went through the storage layers, seems like the code the code is already written to support revid/item id support, its just we use name meta for referring.
157 2013-06-16T18:31:16 <ashutosh1461> what am i missing ?
158 2013-06-16T18:33:48 <sharky93> TheSheep, yes you are correct, how do we proceed then? try to develop by fixing the fundamental things with the framework or improving with what we have already?
159 2013-06-16T18:34:25 <TheSheep> sharky93: the organizational stuff doesn't need a framework, so lets start with that
160 2013-06-16T18:34:43 <TheSheep> sharky93: once we have some structure we are happy about, we can revisit the frameworks
161 2013-06-16T18:35:35 <sharky93> and that includes fixing the inconsistent (distances, fonts etc.) ?
162 2013-06-16T18:36:40 <TheSheep> that can wait, I think
163 2013-06-16T18:36:58 <TheSheep> because it's all going away if we use a framework anyways
164 2013-06-16T18:37:09 <sharky93> yeah precisely.
165 2013-06-16T18:38:08 <ThomasWaldmann> ashutosh1461: the usage of name-only in parts of the api is an issue if you don't have the name, but the itemid
166 2013-06-16T18:39:37 <TheSheep> sharky93: but things like making the right-side bar consistent in all the views (both in size and content) still count
167 2013-06-16T18:39:55 <TheSheep> sharky93: and I think we should improve some of those views too
168 2013-06-16T18:40:00 <ashutosh1461> ThomasWaldmann, but what i have seen that the code is written so as too support itemid as well
169 2013-06-16T18:40:22 <ashutosh1461> i mean if we use itemid as the main identifier we can do well there also
170 2013-06-16T18:42:49 <ThomasWaldmann> storage/indexing __getitem__ works by name
171 2013-06-16T18:44:28 <ashutosh1461> but we have also a function get_item defined
172 2013-06-16T18:44:44 <ashutosh1461> that returns item as per the query provided.
173 2013-06-16T18:44:48 <ThomasWaldmann> yup.
174 2013-06-16T18:45:04 <ana_ananasova> but can we use itemid to refer to the user profiles in the subscribers list?
175 2013-06-16T18:45:36 <ThomasWaldmann> also, the highlevel picture for namespaces and names is still missing. like e.g. where the split happens.
176 2013-06-16T18:45:58 <sharky93> TheSheep, yes i guess no point in hiding Metadata in the Highlight view .. ?
177 2013-06-16T18:46:41 <sharky93> TheSheep, but there may not be too many things we can improve upon if we are concentrating on the structure..
178 2013-06-16T18:46:51 <sharky93> *just on the
179 2013-06-16T18:47:01 <ashutosh1461> so, where exactly do we need that itemid/revid support besides the url part ?
180 2013-06-16T18:47:03 <ThomasWaldmann> ana_ananasova: you can only use a "subscribers list" for precise subscriptions of one specific item
181 2013-06-16T18:47:19 <ThomasWaldmann> no foo* subscriptions with that
182 2013-06-16T18:50:10 <ana_ananasova> does that mean that we can't store references to all subscribed users to the item's metadata?
183 2013-06-16T18:51:48 <ThomasWaldmann> i am just saying this doesn't solve the whole problem
184 2013-06-16T18:52:01 <ThomasWaldmann> ana_ananasova: i put a comment on your ep
185 2013-06-16T18:52:34 <ana_ananasova> perfect
186 2013-06-16T19:10:19 <TheSheep> sharky93: I think we can do a lot of very good work, it just requires more thought
187 2013-06-16T19:17:23 <sharky93> TheSheep, how can we discuss more effectively? chat may not be a very good way.
188 2013-06-16T19:43:55 <TheSheep> sharky93: google hangouts?
189 2013-06-16T19:45:07 <sharky93> TheSheep, somewhere where we could collab on an image might be better
190 2013-06-16T19:45:20 <sharky93> like working on a screenshot, it might be faster too
191 2013-06-16T19:52:50 <TheSheep> hangouts lets you share a window
192 2013-06-16T19:53:00 <TheSheep> and there is a whiteboard plugin
193 2013-06-16T19:55:44 <sharky93> oh nice, never tried the plugin
194 2013-06-16T19:57:00 <TheSheep> we can try it tomorrow evening if like
195 2013-06-16T19:57:11 <TheSheep> (can't do it at work)
196 2013-06-16T19:58:58 <sharky93> sure
197 2013-06-16T20:03:36 * ThomasWaldmann created the diary pages and updated the main page on the wiki
198 2013-06-16T20:06:30 <ana_ananasova> the diary is accessed via the calendar?
199 2013-06-16T20:08:25 <ThomasWaldmann> just click on some day
200 2013-06-16T20:09:51 <ana_ananasova> very handy
201 2013-06-16T20:10:00 <sharky93> TheSheep, how easy / difficult would be a shift from say j-m to bootstrap?
202 2013-06-16T20:11:50 <TheSheep> sharky93: with j-m it would be tricky, I think, because it's more than just css framework, with gumby or foundation should be much easier
203 2013-06-16T20:17:27 <ThomasWaldmann> ana_ananasova: are you editing the main page?
204 2013-06-16T20:17:52 <ana_ananasova> no
205 2013-06-16T20:17:58 <ThomasWaldmann> http://www.doodle.com/xpwgqh74mrm7p2p9 < for our weekly meeting
206 2013-06-16T20:18:13 <ThomasWaldmann> ana_ananasova: moin says so
207 2013-06-16T20:18:40 <ThomasWaldmann> (GoogleSoc2013 page I meant)
208 2013-06-16T20:19:10 <ana_ananasova> hm.. i am truly not. the problem still persists?
209 2013-06-16T20:20:00 <sharky93> i can visualize the weekly meet being flooded with framework issues :P
210 2013-06-16T20:20:58 <ThomasWaldmann> ana_ananasova: moin warns you have the page open for editing. if you open a page for editing, make sure to either save or cancel at the end.
211 2013-06-16T20:22:20 <ThomasWaldmann> sharky93: it's not like the weekly meeting is the only time when communication has to happen, it is just the time where everybody has to be there.
212 2013-06-16T20:22:41 <ana_ananasova> ThomasWaldmann, i double checked every tab and I don't even have the page GoogleSoc2013 opened.
213 2013-06-16T20:24:16 <ThomasWaldmann> ok, maybe the lock was somehow not removed. it happens if one just closes a tab.
214 2013-06-16T20:28:37 <ana_ananasova> ThomasWaldmann, you were right. the edit page was opened 15 minutes ago. i see it in history.
215 2013-06-16T20:29:04 <ana_ananasova> probably double clicked accidently.
216 2013-06-16T20:29:07 <ana_ananasova> i am sorry
217 2013-06-16T20:29:58 <ThomasWaldmann> no problem, just wanted to avoid an edit conflict
218 2013-06-16T20:37:55 <sharky93> TheSheep, so this week is almost i18n, lint .. we continue discussing over the framework issue, next would be fixing the fundamental issues, once done with them, do we then shift to developing actually for a framework .. in say week 3/4 ?
219 2013-06-16T20:39:06 <ThomasWaldmann> sharky93: try to do sane multitasking. like a OS, if you wait for I/O, do something else. :)
220 2013-06-16T20:40:17 <ThomasWaldmann> (e.g. if you wait for feedback from mentors, on codereview results, work on planning, on refining, research, other topic)
221 2013-06-16T20:42:32 <sharky93> ThomasWaldmann, hmm true, i was actually interested more in will we be working with a framework this SoC after all, since completing a full UI within this period might be too much work :) .. we may have to continue later
222 2013-06-16T20:47:44 <ThomasWaldmann> there is lots of time, you just don't have to waste it
223 2013-06-16T20:48:38 <ThomasWaldmann> like e.g. if that discussion had begun 4w ago, we would be 4w more advanced by now.
224 2013-06-16T20:51:54 <sharky93> but we didn't if it was going to "this SoC" 4w ago :P
225 2013-06-16T20:55:28 <ThomasWaldmann> using a good toolkit/framework is often preferable to building your own stuff. you can save years of work, have ease of use and get maintenance of that part of the code in future for free.
226 2013-06-16T20:57:20 * ThomasWaldmann looks at jquery-i18n
227 2013-06-16T21:01:58 *** ana_ananasova
228 2013-06-16T21:04:03 *** ashutosh1461
229 2013-06-16T21:25:53 *** birkenfeld
230 2013-06-16T21:28:19 *** xorAxAx
231 2013-06-16T21:39:22 <ThomasWaldmann> TheSheep: jquery-i18n is completely separate from the gettext system?
232 2013-06-16T21:56:13 *** xorAxAx
233 2013-06-16T21:56:19 *** birkenfeld
234 2013-06-16T22:15:20 <sharky93> gn
235 2013-06-16T22:17:32 *** sharky93
236 2013-06-16T23:49:42 * ThomasWaldmann succeeded in creating some UI from scratch that doesn't look like shit. \o/ (using jquery-mobile)
237
