#MAPBENDER IRC Log - 2008-06-10

For logs after Feb 3, 2007, all times are GMT-8. Prior logs are GMT-9.
Back to Logs
03:11:14 mandsch: Testbaudson: allright?
03:12:53 Testbaudson: hi mandsch
03:13:02 mandsch: hi
03:13:02 Testbaudson: sorry I left early yesterday
03:13:09 mandsch: no prob
03:13:23 mandsch: thought you were a little upset ...?
03:13:55 Testbaudson: just a little :-P
03:14:02 mandsch: ;- ) did you get the splash files?
03:14:08 Testbaudson: yes.
03:14:16 Testbaudson: I will take a look at them later today
03:14:35 Testbaudson: I already merged the old version into the trunk
03:14:41 mandsch: ok, i've tested them here on a rc3, worked ok
03:14:46 Testbaudson: nice
03:15:09 mandsch: i have talked to seven yesterday
03:15:26 mandsch: and we try to meet here later on to discuss treeconfgde
03:15:38 mandsch: not sure when
03:15:44 mandsch: i'll just hang around
03:16:35 mandsch: is this meld tool also available for windoof?
03:17:32 Testbaudson: I guess meld is not available for windows
03:17:41 Testbaudson: but I'm sure there are similar tools
03:17:54 mandsch: hmm, ok, sounded good. I'll look around...
03:18:20 mandsch: do you have any information of nimix? is here around?
03:18:32 mandsch: is he around ... ?
03:18:33 Testbaudson: I guess he is busy studying
03:18:38 mandsch: ok.
03:18:42 Testbaudson: he has not been in since...April?
03:19:04 mandsch: ok, because of this ugly bug in treegde concernign fetaureinfo
03:19:06 Testbaudson: I guess he'll be back during the summer break
03:19:36 Testbaudson: is there a ticket?
03:19:40 mandsch: yep
03:19:52 mandsch: i've cc'ed him
03:20:56 mandsch: http://trac.osgeo.org/mapbender/ticket/219
03:20:57 sigq: Title: #219 ( enabling FI from TreeGDE does not work ) - Mapbender - Trac ( at trac.osgeo.org )
03:21:59 Testbaudson: uh, this sounds tricky...
03:22:12 Testbaudson: the code of treegde2 is somehow cryptic
03:23:15 mandsch: true :- )
03:25:06 Testbaudson: I will take a look at it later today...
03:25:11 Testbaudson: I'll let you knwo
03:33:30 mandsch: ok,
06:21:12 mandsch: Testbaudson: hi, i've just tried the core.js you sent me and it works fine.
06:33:57 Testbaudson: mandsch: ok
06:35:08 mandsch: Testbaudson: I#ll try an d test it on an rc2, later today, ok?
06:35:25 mandsch: the first test was on rc3
06:35:38 Testbaudson: ok
06:35:47 Testbaudson: I will commit it to 2.5 and to trunk later on
06:38:50 mandsch: ok, great, thx
07:47:39 LenKne: Testbaudson: Any decision on user/group/service/application model?
07:52:36 Testbaudson: Hi LenKne
07:52:50 Testbaudson: we had a long discussion today
07:53:28 Testbaudson: I'm not sure if all are willing to support the motion
07:53:39 Testbaudson: maybe we will have to think it over
07:54:23 Testbaudson: I guess maybe we start with something else...
07:54:34 Testbaudson: and come back to the use model next month ( ? )
07:54:41 Testbaudson: and come back to the user model next month ( ? )
07:54:47 LenKne: Sure
07:55:16 Testbaudson: did Lars contact you?
07:55:36 LenKne: I am still inclined to start with the user/group management portion of the admin modules
07:55:44 LenKne: No, have not heard from Lars
07:56:01 Testbaudson: what do you suggest as a starting point?
07:57:13 LenKne: Keeping the same model, but looking at a cleaner interface, similar to the new WFS edit module...
07:57:22 Testbaudson: ok
07:57:51 Testbaudson: Lars told me he was preparing something...
07:57:51 LenKne: something to give people a feel for what the admin modules could look like, and get feedback on the direction
07:58:02 Testbaudson: he is our CSS guru...
07:58:51 Testbaudson: so I'm fine with it. Let's start with the interfaces.
07:59:00 LenKne: Ok...
07:59:29 LenKne: any sense on when votes will come in on the element/application split?
07:59:39 spsneo: Testbaudson: will my project be affected due to Len's?
08:00:11 Testbaudson: LenKne: I don't think it will happen...
08:00:20 Testbaudson: at least not now.
08:00:24 Testbaudson: I'm not sure
08:00:34 LenKne: Too bad :(
08:00:40 Testbaudson: Yes.
08:00:45 LenKne: It seems like a great idea
08:00:59 Testbaudson: It seems like we are not ready for it
08:01:30 Testbaudson: maybe it would also be a too big burden for us to carry
08:01:39 Testbaudson: so let's start with the current environment
08:01:49 Testbaudson: spsneo: No, you are not affected
08:01:55 LenKne: I can see that side of it too
08:02:00 spsneo: ok
08:02:59 Testbaudson: LenKne: Next week we are going to a development sprint...
08:03:10 Testbaudson: maybe I have some other results at the end of next week...
08:03:21 Testbaudson: but I think we will stick to the old model for now
08:04:01 spsneo: Testbaudson: Do we change conf file?
08:04:14 LenKne: Code sprint sounds like fun, wish I could be there
08:04:16 spsneo: I mean do we generally make changes to mapbender.conf file?
08:05:28 Testbaudson: spsneo: only mapbender.conf-dist is delivered with Mapbender
08:05:28 Testbaudson: and yes, it changes from time to time
08:06:06 Testbaudson: LenKne: I'll keep you updated
08:06:18 Testbaudson: I'll have Lars contact you tomorrow
08:06:20 spsneo: actually i wanted to .. have a file where users save their database config and that file does not changes with time
08:07:05 spsneo: so that we dont have to ask users for those information while updating
08:07:43 Testbaudson: spsneo: can you be more specific?
08:07:53 Testbaudson: database config?
08:08:37 spsneo: currently users are storing database username, host, password information in mapbender.conf file
08:09:15 spsneo: I am talking about database host, username, port, password
08:09:31 Testbaudson: ok
08:09:39 Testbaudson: why move it?
08:10:46 spsneo: because if we change the mapbender.conf file and when we release the new version, we will be asking users to replace old files with new ones..
08:11:09 spsneo: so they would replace the old conf file with the new one
08:11:24 spsneo: and hence they will have to enter those information again
08:11:44 spsneo: anyways this isnt a big issue..
08:11:52 spsneo: it can be discussed later also
08:12:16 Testbaudson: spsneo: what is your status concerning the db structure update?
08:12:39 spsneo: ya i am working on it..
08:13:07 spsneo: currently i have made classes for checking php version,
08:13:13 spsneo: and post gre sql version
08:13:17 spsneo: and mytsql version.
08:13:39 spsneo: ya and i have also started to code the build script
08:13:57 spsneo: as ,, with every release this update script may change ...
08:14:07 spsneo: beacuse the php and othe rrequirements may change
08:14:19 spsneo: so... the build script will be a kind of template..
08:14:38 : * LenKne is thinking as a Mapbender user, will the update automatically replace the existing version?
08:14:42 spsneo: Testbaudson: getting me?
08:15:09 spsneo: LenKne: no the user will have to replace the files manually
08:15:39 LenKne: Ok
08:16:22 Testbaudson: spsneo: what does the build script do exactly?
08:16:43 spsneo: hmm..I wil explain u..
08:17:06 spsneo: suppose.. we are going to release mb 2.6
08:17:21 spsneo: and.. the min requirement for mb 2.6 is say php x
08:17:27 spsneo: php x.0 say
08:17:46 spsneo: so the update script for mb 2.6 will check for php version x.0
08:17:57 spsneo: now say sometime later we are releasing mb 2.7
08:18:08 spsneo: and the min requirement is php x.1
08:18:26 spsneo: so now the update script will check for php x.1 or greater
08:18:37 spsneo: so u see.. update script varies with the release
08:18:56 spsneo: so we need to create the update script.. at the time of release..
08:19:03 spsneo: Testbaudson: did u get me?
08:19:12 : * Testbaudson is still reading
08:19:59 Testbaudson: ok, got it
08:20:36 Testbaudson: where do we put the information...
08:20:41 Testbaudson: which php version is required?
08:20:48 Testbaudson: system.php?
08:20:53 spsneo: that can be done in 2 ways..
08:21:07 spsneo: may be we can fill those information in some file..
08:21:20 spsneo: and the build script will build the update script
08:21:38 spsneo: or we may have a web based form..for building the update script
08:21:55 spsneo: which one do u prefer?
08:22:20 spsneo: Testbaudson: one more querry.. normally all our mb users use linux ?
08:22:30 Testbaudson: why a form? what data would a user enter?
08:22:34 spsneo: i mean they install mb on linux machine?
08:22:41 Testbaudson: most use linux
08:22:51 Testbaudson: some use windows
08:22:54 spsneo: user wont fill the form..
08:23:21 spsneo: while building process mb administrator will fill the form to generate the update script
08:23:42 Testbaudson: ok, got it
08:23:51 Testbaudson: but a file is preferable
08:24:01 Testbaudson: administrators know how to edit files ;- )
08:24:08 spsneo: yup, thats more geeky : )
08:24:10 Testbaudson: users don't
08:24:20 Testbaudson: and it's less error prone
08:24:23 spsneo: but web based interface is more user friendly
08:24:35 spsneo: ok..
08:24:36 Testbaudson: you named it...
08:24:40 Testbaudson: "user" friendly
08:24:43 Testbaudson: not admin friendly
08:24:46 spsneo: hehe
08:24:49 spsneo: :O
08:24:55 spsneo: :D
08:24:56 spsneo: ok..
08:25:03 spsneo: anyways it would be easy for me also..
08:25:07 spsneo: if implemented with file..
08:25:59 spsneo: Testbaudson: thats all for today.
08:26:10 spsneo: how will i commit te code
08:26:22 spsneo: i guess i will need the svn or trac acount
08:26:33 Testbaudson: Did you create an account?
08:26:39 spsneo: no not yet
08:26:50 Testbaudson: Will you be available tomorrow?
08:26:57 spsneo: yes
08:27:04 Testbaudson: we can create your account then...and LenKne's as well
08:27:11 spsneo: ok thanks
08:27:19 spsneo: ok may I leave now for 15 mins
08:27:23 spsneo: as i have to take dinner
08:27:33 spsneo: I will be back in 15 mins.
08:28:25 : * Testbaudson will be back tomorrow
08:28:27 Testbaudson: bye
08:28:31 LenKne: Testbaudson: Thanks for the updates
08:28:32 spsneo: Testbaudson: bye
08:28:36 spsneo: LenKne: bye
08:28:38 Testbaudson: thanks to both of you
08:28:41 Testbaudson: bye
08:28:42 LenKne: bye all