| 00:07:31 | verena: | so, I'm back. |
| 00:09:27 | mandsch: | hey |
| 00:11:32 | mandsch: | ok, like you said, the way to go seems to provide a conf file, that describes the use of a certain template with certain placement definitions of the variuos elements... |
| 00:12:31 | mandsch: | so we would need to idetnify these elements... map, overviewmap, scalebar, |
| 00:12:40 | mandsch: | legend |
| 00:13:10 | mandsch: | kartenspiegel... what's that in english ... mapmirror? |
| 00:13:22 | verena: | don' know :- ) |
| 00:13:40 | mandsch: | sth. else? |
| 00:13:48 | verena: | hmmm.. |
| 00:14:00 | verena: | I think that would be one of the first steps... |
| 00:14:32 | verena: | to identify all necessary elements. |
| 00:14:42 | mandsch: | map coordinates .. |
| 00:15:10 | mandsch: | of the corners. |
| 00:15:18 | verena: | yes. |
| 00:15:44 | verena: | everything we want to have in the PDF. |
| 00:16:30 | verena: | it should be possible to define which elements the user wants to have in the PDF... |
| 00:16:45 | mandsch: | yep. |
| 00:17:02 | verena: | and it should be possible that these elements can be easy positioned in the PDF. |
| 00:18:22 | mandsch: | exactly, so we need a configuration file, that has defintions for each element we want to place in the pdf, |
| 00:18:40 | mandsch: | position, size, |
| 00:18:55 | mandsch: | via the request we could determine if it should be included or not |
| 00:19:52 | mandsch: | do you think it is too complicated for mapbender admins to create ( copy and modify ) such a conf file, e.g. to be suitable for their own template? |
| 00:21:58 | verena: | hmm, concerning the work we have at the moment configuring the print I can't imagine that it could be not that difficult. |
| 00:23:07 | verena: | I can't imagine that it could be that difficult. |
| 00:25:21 | mandsch: | sorry, just on the phone |
| 00:26:21 | mandsch: | yeah, i think so too, at the moment it is quite hard |
| 00:26:38 | verena: | but I think we have to spend some time with this solution to evaluate all possibilities FPDF/FPDI offers to us. |
| 00:27:10 | mandsch: | one main drawback |
| 00:27:51 | mandsch: | is that it is harder |
| 00:28:07 | mandsch: | to switch between different paper sizes and formats |
| 00:28:29 | mandsch: | or at least you'd have to provide a template and a configuration for each |
| 00:29:03 | mandsch: | otoh, it is easier for the user, e.g. to have one list to choose from, which template he wants to use |
| 00:30:42 | verena: | I think there could be many possibilities to have a better way of configuration than we have it now ( to be honest: it is really horrible at the moment to configure all formats in the scripts ) |
| 00:31:02 | verena: | It can only get better :- ) |
| 00:31:35 | mandsch: | ok, how should we proceed? |
| 00:32:03 | mandsch: | I will be on holidays for two weeks from friday on |
| 00:32:58 | mandsch: | but maybe we can use your or my dev branch or should we have a new print branch? |
| 00:34:08 | verena: | I can ask Testbaudson about that. But it could make sense to have a new print branch. |
| 00:34:49 | verena: | We can discuss about more details when you are back. |
| 00:35:13 | mandsch: | ok, |
| 00:35:20 | verena: | I don't know if I can spend time with the print in the next 2 weeks. |
| 00:35:36 | verena: | I can try, but I can't promise anything. |
| 00:36:29 | mandsch: | well. maybe we can refine what we need |
| 00:37:01 | mandsch: | also check which funtionality can be used from the current pdf ( drawing of measurements from mapframe ) |
| 00:37:22 | verena: | yes, exactly. |
| 00:38:58 | mandsch: | maybe check our both project code and look what we can use therefrom, eventually to have prototype |
| 00:40:01 | verena: | Yes, it would be really nice to have a first simple prototype. |
| 00:42:06 | verena: | we could use the discussion page of the Print module in the wiki to fix all ideas we have about restructuring the print ( http://www.mapbender.org/index.php?title=Talk:Print ) |
| 00:42:07 | sigq: | Title: Talk:Print - MapbenderWiki ( at www.mapbender.org ) |
| 00:42:35 | mandsch: | yeah, that is a good idea |
| 00:43:10 | mandsch: | I will start working on that when i'm back, maybe i can write sth. down in the coming days ... |
| 00:43:23 | verena: | yes, I will try the same. |
| 00:43:37 | mandsch: | ok sounds good. |
| 00:43:42 | verena: | :- ) |
| 00:46:01 | verena: | getting an overview about all ideas we have and all steps which have to be done sounds good. |
| 00:48:14 | mandsch: | if the project I did with fpdf is online i'll let you know |
| 00:48:42 | verena: | ok, thanks. |
| 03:26:44 | spsneo: | Testbaudson: Hello |
| 03:27:01 | spsneo: | I wanted to discuss regarding your mail on improved build script |
| 03:28:38 | spsneo: | Testbaudson: are you there? |
| 03:47:24 | Testbaudson: | hi spsneo |
| 03:47:35 | spsneo: | Testbaudson: i mailed one message |
| 03:47:38 | spsneo: | did u see that? |
| 03:48:55 | spsneo: | ? |
| 03:58:34 | spsneo: | Testbaudson: sorry I got disconnected |
| 04:05:27 | : | * Testbaudson is on the phone...sorry |
| 04:08:26 | : | * spsneo is off for swimming ! will be back after an hour |
| 05:00:34 | : | * spsneo is back |
| 05:02:36 | spsneo: | Testbaudson: are u free now? |
| 05:05:15 | Testbaudson: | hi spsneo |
| 05:05:17 | Testbaudson: | yes |
| 05:05:27 | spsneo: | Testbaudson: hello |
| 05:05:31 | spsneo: | did u go through the mail |
| 05:05:35 | spsneo: | ? |
| 05:05:37 | Testbaudson: | yes |
| 05:05:47 | spsneo: | any comments on tht |
| 05:05:53 | spsneo: | I want to add one more thing |
| 05:06:16 | spsneo: | I havent yet added the feature of selecting files according to different version. |
| 05:06:27 | spsneo: | as there is no standard nomenclature. |
| 05:06:51 | spsneo: | As soon as we decide on a standard string denoting a particular version. |
| 05:06:55 | spsneo: | I will add tht code. |
| 05:07:04 | spsneo: | That wont be any difficult job anyways |
| 05:07:21 | Testbaudson: | ok |
| 05:07:39 | Testbaudson: | I think naming the folder according to the mapbender.conf setting is goog |
| 05:07:45 | Testbaudson: | UTF-8 instead of utf8 |
| 05:07:51 | Testbaudson: | I'm fine with this |
| 05:07:52 | spsneo: | yup |
| 05:08:01 | spsneo: | because it will make the code more flexible |
| 05:08:04 | Testbaudson: | however I disagree on a separate update folder |
| 05:08:09 | spsneo: | we can later on add more charset |
| 05:08:13 | spsneo: | why? |
| 05:08:59 | Testbaudson: | resources already contains a db folder |
| 05:09:07 | spsneo: | ok |
| 05:09:20 | spsneo: | so should I make the changes accordingly in the script? |
| 05:09:27 | Testbaudson: | do you see an advantage of having it somewhere else? |
| 05:10:06 | spsneo: | it will make the update entirely separate from the whle thing |
| 05:10:23 | spsneo: | I mean it will be like an entire separate update module |
| 05:10:36 | Testbaudson: | ok, I see your point... |
| 05:10:44 | spsneo: | but ya may be placing the sql files in resources folder wont affect |
| 05:10:46 | spsneo: | much |
| 05:10:51 | Testbaudson: | however I see more advantages in keeping data and code separate |
| 05:10:53 | spsneo: | so in a way u r true also |
| 05:11:00 | spsneo: | ya u r true |
| 05:11:12 | spsneo: | Ok I wil make the changes accordingly |
| 05:11:31 | Testbaudson: | what do you think about the folder naming convention for the update sqls? |
| 05:11:47 | Testbaudson: | I proposed <timestamp>_<from>_to_<to> |
| 05:11:53 | spsneo: | folder naming convention will be like this: |
| 05:12:01 | spsneo: | in fact should be like this imho |
| 05:13:12 | Testbaudson: | what is your suggestion for the naming convention? |
| 05:14:28 | Testbaudson: | ( an other thing: we should rename the folder 'postgresql' to 'pgsql'...these are also the names in the conf file ) |
| 05:55:15 | spsneo: | Testbaudson: I am sorry again |
| 05:55:20 | spsneo: | I got disconnected |
| 05:56:53 | Testbaudson: | hi spsneo |
| 05:57:11 | spsneo: | ya I have alreayd named the fodler pgsql only |
| 05:57:22 | spsneo: | in update folder. |
| 05:57:48 | : | * spsneo will change the code tonight to update the db from sql files in resources folder |
| 05:57:59 | Testbaudson: | nice |
| 05:58:03 | spsneo: | finally I propose the folder naming convention to be like this |
| 05:58:04 | spsneo: | : |
| 05:58:42 | spsneo: | resources/db/update/DATABASENAME/CHARSET/VERSION_STRING/ |
| 05:59:14 | Testbaudson: | hmm |
| 05:59:32 | Testbaudson: | what I wanted to achieve was this: |
| 05:59:54 | Testbaudson: | a ) avoid the confusion: is this for upgrading TO the version, or FROM the version... |
| 06:00:02 | Testbaudson: | so I explicitly wanted to have both in the name |
| 06:00:13 | Testbaudson: | b ) I wanted to have them sorted by version |
| 06:00:27 | Testbaudson: | as the sort order by version is not intuitive... |
| 06:00:38 | Testbaudson: | as 2.4.2 will be listed below say 2.4.11 |
| 06:00:45 | Testbaudson: | I wanted a timestamp |
| 06:00:57 | Testbaudson: | so my suggestion would probably be this |
| 06:01:22 | Testbaudson: | resources/db/DATABASENAME/CHARSET/update/TIMESTAMP_FROM_TO |
| 06:12:42 | Testbaudson: | spsneo? |
| 06:15:49 | spsneo: | Testbaudson: I am extremely sorry |
| 06:16:04 | spsneo: | There was a power failure |
| 06:16:10 | spsneo: | I went through the logs |
| 06:16:14 | Testbaudson: | no sweat |
| 06:17:36 | spsneo: | is from_to necessary |
| 06:17:54 | Testbaudson: | I think it is better to avoid confusion |
| 06:18:06 | spsneo: | well what I wanted to say is that: |
| 06:18:29 | spsneo: | update script automatically defines the to version |
| 06:18:31 | spsneo: | isnt it? |
| 06:18:54 | Testbaudson: | yes, but we want to build an update history... |
| 06:18:54 | spsneo: | I mean we are updating using a script, that automatically defines the version to which I am updating |
| 06:19:03 | spsneo: | ok.. ya.. |
| 06:19:18 | spsneo: | so finally what should be the string for version? |
| 06:19:37 | Testbaudson: | do you agree on the necessity of a timestamp? |
| 06:19:48 | Testbaudson: | as explained above |
| 06:23:19 | spsneo: | Testbaudson: I didnt really got ur point behind timestamp |
| 06:23:25 | spsneo: | can u explain me once again |
| 06:23:47 | Testbaudson: | I would like to have the folder sorted chronologically |
| 06:24:05 | Testbaudson: | if you only have the version, the sort order can easily get mixed up... |
| 06:24:32 | Testbaudson: | so 2.5_rc1 might be listed after 2.5.1 |
| 06:24:43 | Testbaudson: | or 2.4.2 below 2.4.11 |
| 06:24:55 | spsneo: | then whats ur suggestion? |
| 06:25:03 | Testbaudson: | name the folder like this |
| 06:25:12 | Testbaudson: | TIMESTAMP_FROM_TO |
| 06:25:15 | Testbaudson: | like |
| 06:25:35 | Testbaudson: | 20080708_2.5rc1_to_2.5rc2 |
| 06:25:38 | Testbaudson: | for example |
| 06:26:07 | Testbaudson: | or even 20080708_update_from_2.5rc1_to_2.5rc2 |
| 06:26:32 | Testbaudson: | do you get what I mean? |
| 06:26:57 | spsneo: | but say the user is updating from 2.4.2 to 2.5.rc1 |
| 06:27:11 | Testbaudson: | then he has to execute all updates in between |
| 06:27:14 | Testbaudson: | sequentially |
| 06:27:15 | spsneo: | then how can the script now.. which folder to search in |
| 06:27:17 | spsneo: | ? |
| 06:27:29 | spsneo: | ok.. |
| 06:27:51 | spsneo: | but so.. do u mean .. the script will automatically..identify the current timestamp |
| 06:28:10 | Testbaudson: | no |
| 06:28:12 | spsneo: | and it will execute all the sql files chronologically |
| 06:28:14 | spsneo: | right? |
| 06:28:17 | Testbaudson: | the timestamp is just for the sort order |
| 06:28:48 | : | * spsneo is confused |
| 06:28:57 | : | * spsneo is thinking |
| 06:28:59 | Testbaudson: | the script will look for a folder that contains MB_VERSION in a folder name |
| 06:29:14 | Testbaudson: | like in "from_<MB_VERSION>" |
| 06:29:37 | Testbaudson: | then it sequentially executes all SQLs below |
| 06:29:41 | Testbaudson: | to get to the latest version |
| 06:29:51 | Testbaudson: | example |
| 06:30:00 | Testbaudson: | your update folder contains these folders |
| 06:30:10 | Testbaudson: | 20080708_update_from_2.5rc1_to_2.5rc2 |
| 06:30:16 | Testbaudson: | 20080709_update_from_2.5rc2_to_2.5rc3 |
| 06:30:23 | Testbaudson: | 20080710_update_from_2.5rc3_to_2.5rc4 |
| 06:30:36 | Testbaudson: | 20080711_update_from_2.5rc3_to_2.5 |
| 06:30:50 | Testbaudson: | the user has version 2.5rc2 in MB_VERSION |
| 06:30:56 | spsneo: | ok |
| 06:31:11 | Testbaudson: | the update script locates the folder with the "from" version matching the current version |
| 06:31:25 | Testbaudson: | and executes the SQLs in this folder... |
| 06:31:28 | Testbaudson: | and in all folders below |
| 06:32:03 | spsneo: | ok I got you |
| 06:32:08 | Testbaudson: | ok, good |
| 06:32:17 | Testbaudson: | do you think it makes sense? |
| 06:32:22 | spsneo: | so should I modify the script now? |
| 06:32:30 | spsneo: | or should we wait for other devs |
| 06:32:31 | spsneo: | ? |
| 06:32:33 | Testbaudson: | if you have the time... |
| 06:32:37 | Testbaudson: | it would be nice |
| 06:32:40 | spsneo: | to confirm on this structure |
| 06:32:41 | spsneo: | ? |
| 06:32:58 | Testbaudson: | I don't think anyone will disagree |
| 06:33:09 | Testbaudson: | but if you want to wait, it's fine |
| 06:33:14 | Testbaudson: | no problem |
| 06:33:26 | spsneo: | okk.. |
| 06:33:38 | spsneo: | well I will do this now only. |
| 06:33:44 | spsneo: | may be this weekend |
| 06:33:55 | spsneo: | and regarding the filesystem update script |
| 06:34:00 | spsneo: | is evverything ok? |
| 06:34:06 | spsneo: | or do I need to add anything else? |
| 06:34:16 | Testbaudson: | I didn't find time to test it yet... |
| 06:34:31 | Testbaudson: | I just took a short glance |
| 06:34:38 | spsneo: | ok, anyways, I am always here to maintain the update script. |
| 06:34:56 | Testbaudson: | I think we will start testing it when we really try to get it working when 2.6rc1 is released |
| 06:35:01 | Testbaudson: | I trust you it works |
| 06:35:07 | spsneo: | so even after the gsoc program is over I will voluntarily maintaining this script |
| 06:35:18 | Testbaudson: | THIS WOULD BE GREAT :- ) |
| 06:35:41 | spsneo: | so, during the release of next version, I will be there while experimenting. |
| 06:35:50 | Testbaudson: | cool |
| 06:35:53 | spsneo: | mean while I will start working on install script |
| 06:36:09 | Testbaudson: | wow, your enthusiasm is brilliant |
| 06:36:13 | Testbaudson: | I like that |
| 06:36:19 | spsneo: | thanks |
| 06:36:20 | Testbaudson: | if you need help, let me know |
| 06:36:26 | seven: | spsneo: You could consider to making this part of a for-money job. |
| 06:36:40 | spsneo: | seven: how can I/ |
| 06:36:42 | spsneo: | ? |
| 06:37:24 | spsneo: | Testbaudson, as u said version 2.6 will be released by the end of this year, so I will target to finish the install script by novemebr end.. |
| 06:37:39 | spsneo: | so that install script is included in the next version. |
| 06:37:47 | Testbaudson: | this would be nice... |
| 06:37:58 | Testbaudson: | installation and update make a good pair |
| 06:38:05 | Testbaudson: | and the users will be happy |
| 06:38:16 | Testbaudson: | to have everything in one go |
| 06:38:43 | spsneo: | I will be very happy if both the script are included in the next version |
| 06:39:01 | Testbaudson: | yes, I think we can make it |
| 06:39:09 | spsneo: | ok |
| 06:39:14 | Testbaudson: | it's about time we have this function, we waitd long enough |
| 06:39:16 | seven: | spsneo: Have to leave now, we can further discuss via email if you are interested. |
| 06:39:40 | spsneo: | seven : for sure |
| 06:40:53 | spsneo: | Testbaudson: anyways I will try to add the modification by the end of this week. |
| 06:41:05 | spsneo: | although preparing documentation , and adding a wiki page is more important |
| 06:41:14 | spsneo: | so I will do that first |
| 06:41:19 | Testbaudson: | ok, thanks. Yes documentation is important |
| 06:41:58 | Testbaudson: | Did I tell you about how I will generate the SQL files from a entity-relationship-diagram? |
| 06:42:07 | Testbaudson: | This will make the build process much easier |
| 06:43:23 | Testbaudson: | if you are interested, take a look at this |
| 06:43:23 | Testbaudson: | http://www.mapbender.org/Talk:Deployment |
| 06:43:24 | sigq: | Title: Talk:Deployment - MapbenderWiki ( at www.mapbender.org ) |
| 06:43:30 | Testbaudson: | talk to you soon |
| 06:43:31 | Testbaudson: | bye |