| 00:35:37 | CIA-70: | pcav * r10609 /trunk/qgis/src/plugins/grass/config/default.qgc: Typo in GRASS default.qgc |
| 00:36:08 | sigq: | tracfeed: Changeset [10609]: Typo in GRASS default.qgc <https://trac.osgeo.org/qgis/changeset/10609> |
| 06:25:38 | CIA-70: | cfarmer * r10610 /trunk/qgis/python/plugins/fTools/ ( 6 files in 2 dirs ): |
| 06:25:38 | CIA-70: | adds ability to copy unique values to clipboard to pasting into other |
| 06:25:38 | CIA-70: | software ( i.e. excel ); updates version number as well |
| 06:29:30 | cfarmer: | I hope that commit is allowed, as it is really a bug fix, not a new feature per se? |
| 06:34:11 | : | * jef won't shoot our manual team lead |
| 06:35:19 | cfarmer: | hehe good! |
| 06:35:26 | aghisla: | hi cfarmer! |
| 06:35:35 | cfarmer: | howdy aghisla! |
| 06:35:52 | aghisla: | how are you? |
| 06:39:07 | cfarmer: | i'm good thanks... busy as always, but good... you? |
| 06:40:02 | aghisla: | good : ) accepted to SoC for the second time |
| 06:40:12 | aghisla: | and part of manual team too! |
| 06:43:11 | cfarmer: | yes I see that, excellent! congrats on the SoC project, and welcome to the team... i'm a new member myself, and i'm not quite sure yet what i've gotten myself into ;- ) |
| 06:45:54 | aghisla: | we'll see! |
| 06:46:46 | cfarmer: | yeh I'm looking forward to it... I guess we'll see what's up at the meeting... anyway, I'm going to go grab something to eat... so i'll catch you later... |
| 06:46:58 | aghisla: | ok! |
| 06:47:08 | aghisla: | I'll leave too in a while |
| 06:57:10 | dassouki: | cfarmer: there was mention once about a line of site r script, are u aware of it ? and do u know if it works on linear tables? i'm looking at finding out the line of sights on road intersections. is there a pseudo code that someone can follow ? |
| 06:57:52 | dassouki: | linear tables ( line layers such as roads ) |
| 07:33:13 | cfarmer: | dassouki: i'm not familiar with this, but that doesn't mean one doesn't exist... but if you're wokring simply with road intersections, doesn't this then become a simple point based line of sight question? |
| 07:34:37 | cfarmer: | dassouki: sorry i can't be of more help... i have to head out... but i'll be back on #qgis later... |
| 07:45:26 | dassouki: | from a design point, would it be better to ask the user to add data to a table/shapefile such as number of households, income and so on, or would it be better if i provide the code for that ? |
| 09:49:24 | sigq: | tracfeed: Ticket #1641 ( bug reopened ): trunk r10595 fails to build at parsing SIP files for 'gui' <https://trac.osgeo.org/qgis/ticket/1641#comment:8> |
| 09:50:30 | j03lar50n: | I thought I saw a blurb for a QGIS standalone installer, looking for one for coworkers..does one exist? |
| 09:50:57 | j03lar50n: | I use the OSGeo4W myself...and yes this would be for windows machines |
| 09:52:04 | dassouki: | download.qgis.org perhaps ? |
| 09:52:56 | j03lar50n: | nice, there's a 1.0.0preview2 .exe there |
| 09:53:13 | j03lar50n: | thx dassouki |
| 10:00:12 | sigq: | tracfeed: Ticket #1641 ( bug closed ): trunk r10595 fails to build at parsing SIP files for 'gui' <https://trac.osgeo.org/qgis/ticket/1641#comment:9> |
| 10:32:58 | CIA-70: | jrm * r10611 /docs/branches/1.0.0/french/user_guide/getting_started.tex: remplacement du fichier incomplet |
| 10:32:59 | sigq: | tracfeed: Changeset [10611]: remplacement du fichier incomplet <https://trac.osgeo.org/qgis/changeset/10611> |
| 11:44:01 | sigq: | tracfeed: Ticket #1645 ( enhancement created ): Add align option to Edit Current Grass Region in Toolbar <https://trac.osgeo.org/qgis/ticket/1645> |
| 12:06:35 | wildintellect: | j03lar50n, there was one built recently but it doesn't have Grass or Python |
| 12:07:16 | wildintellect: | jef, how hard would it be to add an express option to OSGeo4w - QGIS Full Install( Includes GRASS and Python ) |
| 12:07:42 | jef: | dunno. probably easy. FrankW should know |
| 12:08:09 | FrankW: | That would be pretty easy. |
| 12:08:44 | FrankW: | But I'd prefer not to have too many options in the express install. |
| 12:09:17 | FrankW: | So possibly the express QGIS option should include python and grass plugin support. |
| 12:09:39 | FrankW: | BTW, I'd suggest doing this by defining a meta-package. |
| 12:14:42 | CIA-70: | jef * r10612 /trunk/qgis/ ( CMakeLists.txt qgis.1 qgis.man qgis_help.1 qgis_help.man ): rename manual page files ( fixes #1517 ) |
| 12:14:43 | sigq: | tracfeed: Changeset [10612]: rename manual page files ( fixes #1517 ) <https://trac.osgeo.org/qgis/changeset/10612> |
| 12:15:46 | CIA-70: | jef * r10613 /trunk/qgis/debian/ ( changelog rules ): adapt debian package to r10612 |
| 12:15:47 | sigq: | tracfeed: Changeset [10613]: adapt debian package to r10612 <https://trac.osgeo.org/qgis/changeset/10613> || Ticket #1517 ( patch closed ): Wrong man page ext for qgis 1.0.0 <https://trac.osgeo.org/qgis/ticket/1517#comment:4> |
| 12:22:19 | wildintellect: | FrankW, it seems like we should probably proceed with that, we get a couple of people a week asking about where the python and grass support are in OSGeo4w |
| 12:25:49 | sigq: | tracfeed: Ticket #1646 ( patch created ): multiple statements in python console <https://trac.osgeo.org/qgis/ticket/1646> |
| 12:38:24 | wildintellect: | FrankW, jef, where would I look for how to make a meta-package |
| 13:08:26 | austin_: | I'm part of a team at UT, Austin, developing a c++ plugin of graph theory tools. A question on handling wait-time: When a command is executed from our gui plugin window, our sql/c++ grath theory routines start running. This may take minutes or hours on large vertex layers. Right now, after about 10 seconds with the Qt::WaitCursor spinning, the qgis main window fades to dark grey, giving the appearance of a crash. Eventually, when our backg |
| 13:08:27 | austin_: | round routine completes, the main window is restored and the results display successfully. Any suggestions on best-practices for dealing with the problem? Is there a user-friendly progress bar available? |
| 13:10:53 | wildintellect: | austin_, what OS was that test on |
| 13:11:59 | wildintellect: | cause I know on ubuntu/gnome any application that takes a long time fades on me - but is almost never a crash |
| 13:12:14 | wildintellect: | but yes you should be able to implement a progress bar with qt |
| 13:12:35 | wildintellect: | you will of course need to figure out how to update it appropriately based on your application |
| 13:13:07 | jef: | wildintellect: I think I now have one. qgis-full. just an empty tar.bz2 and a setup.hint that creates the dependency to the real packages. try osgeo4w-setup -t |
| 13:13:14 | cfarmer: | qt also has a handy little progress dialog... |
| 13:13:15 | austin_: | OK, I'll try that. Using Ubuntu. |
| 13:13:58 | wildintellect: | austin_, QProgressBar |
| 13:14:09 | cfarmer: | or QProgressDialog... |
| 13:14:41 | wildintellect: | the problem here is that if it's 1 sql statement then there are not updates on which to trigger a change in the Progress |
| 13:17:00 | cfarmer: | wildintellect: in this case, if you set the min and max both to -1, the progress bar will simply bounce back and forth, indicating work is being done, but the percent complete is unknown |
| 13:17:12 | wildintellect: | ah that's cool |
| 13:20:54 | cfarmer: | wait sorry I was wrong, min and max both have to be set to 0 for the busy indication... |
| 13:22:56 | timlinux1: | hi all |
| 13:23:49 | cfarmer: | howdy timlinux1 |
| 13:23:49 | jef: | cfarmer: that would still need a thread or regular calls of processEvents( ), wouldn't it? |
| 13:24:02 | timlinux1: | oh why are there two of me? |
| 13:24:11 | : | * timlinux1 must have left his computer on at work |
| 13:24:38 | jef: | timlinux1: or you have too much bandwidth ; ) |
| 13:24:54 | cfarmer: | yeh you might... I think the progressdialog can be both modal and non-modal, so depends what you need I guess? |
| 13:25:04 | timlinux1: | jef: no chance of that :- ) |
| 13:25:43 | timlinux1: | cfarmer: or they could run their stuff in its own thread if the vector was not being concurrently accessed by QGIS |
| 13:26:19 | jef: | cfarmer, wildintellect: do you actually use the python console? |
| 13:26:32 | cfarmer: | jef: constantly... |
| 13:26:32 | timlinux1: | in my experience using processEvents( ) gives mixed results in terms of making the ui feel responsive during long running processes |
| 13:26:50 | wildintellect: | jef, occasionally to test ideas |
| 13:27:13 | wildintellect: | but I haven't done much UI plugins yet |
| 13:27:19 | cfarmer: | jef: i'm actually working on a replacement one for fun that mimics a real python console almost exactly... |
| 13:27:36 | wildintellect: | any chance autocomplete is part of that? |
| 13:27:45 | cfarmer: | based on the python console in gedit ( gnome text editor ) |
| 13:27:55 | cfarmer: | wildintellect: yes |
| 13:28:09 | wildintellect: | that would be a great way for teaching new people |
| 13:28:18 | : | * jef just added a patch to allow multiple statements at once |
| 13:28:23 | jef: | did you ever miss that? |
| 13:28:31 | wildintellect: | I imagine syntax highlight is in that too |
| 13:28:35 | cfarmer: | nice one jef! |
| 13:28:37 | wildintellect: | jef, all the time |
| 13:28:45 | wildintellect: | that's why I go to scripts quickly |
| 13:29:04 | cfarmer: | maybe I don't need to implement my new version afterall?! |
| 13:30:11 | jef: | cfarmer: well, that's just a simple qtextedit without any bells and whistles. |
| 13:30:21 | jef: | instead of the lineedit |
| 13:30:43 | wildintellect: | did you turn on undo/redo? |
| 13:30:51 | cfarmer: | yeh pretty much... |
| 13:31:19 | cfarmer: | wildintellect: no, that's not quite good enough for history... so I implemented a history |
| 13:31:34 | cfarmer: | just appends commands to a history list |
| 13:32:01 | wildintellect: | ah I'd be interested in that code for my metadata editor |
| 13:33:01 | cfarmer: | jef: maybe I'll just create a new gui for the python console, and use the existing code as is...? what I have so far is similar to my manageR terminal... but I'm not married to it... |
| 13:34:53 | cfarmer: | wildintellect: it's nothing special... i have done it two ways, one: I just append commands to a QStringList, and two I created a History class with some helper functions like addCommand etc. |
| 13:35:56 | jef: | cfarmer: the current python console couldn't be any simpler than it is. I'm surprised that no one who's actually using python did a better one already. |
| 13:36:36 | cfarmer: | jef: yeh, I guess I didn't really think of it until recently... it does the job I guess...? |
| 13:37:24 | : | * cfarmer is going to go over some reviewer comments... hopefully he can handle the criticism.... |
| 13:37:53 | jef: | cfarmer: well, I was annoyed enough by having to copy the code snipped from #1644 line by line. |
| 13:38:29 | jef: | wildintellect: did you see my message about qgis-full? |
| 13:38:39 | wildintellect: | yes |
| 13:38:50 | jef: | ok |
| 13:38:54 | cfarmer: | @track |
| 13:39:00 | cfarmer: | oops |
| 13:39:30 | wildintellect: | jef, course I don't have a win box to toy with it, just friends I help |
| 13:39:39 | cfarmer: | jef: what's the command to find out about that bug? |
| 13:39:48 | jef: | @ticket 1644 |
| 13:39:48 | sigq: | jef: http://trac.osgeo.org/qgis/ticket/1644 |
| 13:39:59 | cfarmer: | jef: thanks :- ) |
| 13:40:02 | jef: | np |
| 13:41:29 | timlinux1: | cfarmer: btw I meant to mention |
| 13:41:59 | timlinux1: | that your ftools has the propensity to crash my computer when trying to clip large datasets :-( |
| 13:42:43 | cfarmer: | timlinux1: oh oh... it's probably throwing a python error in the worker thread, which is obviously not good... |
| 13:43:20 | cfarmer: | I was hoping to avoid having to reroute python errors completely, but I'll probably have to I guess... |
| 13:43:31 | cfarmer: | racicot: ping |
| 13:43:35 | timlinux1: | cfarmer: no I think its doing everything in mem and eventually it consumes so much mem the computer locks up |
| 13:44:28 | cfarmer: | hmmm, shouldn't be... unless you have one huge feature that's being clipped by a bunch of smaller ones ( or vice versa )? |
| 13:44:28 | timlinux1: | cfarmer: it would be nice if it could do : get next feature, clip feature, write to output, flush output, get next feature etc... |
| 13:44:41 | timlinux1: | or does it do that already? |
| 13:44:58 | cfarmer: | timlinux1: that *is* what it does... I think... let me check now ;- ) |
| 13:45:08 | timlinux1: | well it's a largish pg table that Im trying to clip out |
| 13:46:10 | cfarmer: | timlinux1: yup, reads in a feature, and for all features that it intersects, clip it, and write the output ( basically ) |
| 13:46:13 | jef: | hehe. borys also always wanted to improve the python console. |
| 13:46:14 | timlinux1: | cdsm50k=# select count ( * ) from reliefline; |
| 13:46:15 | timlinux1: | count |
| 13:46:15 | timlinux1: | -------- |
| 13:46:15 | timlinux1: | 903866 |
| 13:47:00 | timlinux1: | I thought I recalled Qt already having a good widget for code editing |
| 13:47:08 | timlinux1: | scintilla? |
| 13:47:20 | timlinux1: | the one that Eric uses |
| 13:47:34 | timlinux1: | granted its not part of Qt core |
| 13:48:10 | cfarmer: | btw: happy earth day all! |
| 13:50:30 | timlinux1: | cfarmer: yup celebrate while we still have one :-P |
| 13:50:52 | jef: | timlinux1: while it still has us. |
| 13:51:15 | timlinux1: | gsherman: can you see me? |
| 13:51:48 | cfarmer: | There is also this: http://code.google.com/p/pyqtshell/ which is a nice QtIDE sorta thingy... |
| 13:51:49 | sigq: | Title: pyqtshell - Google Code ( at code.google.com ) |
| 13:53:48 | timlinux1: | cfarmer: find something with no deps and we can plugin it into qgis |
| 13:54:50 | cfarmer: | timlinux1: that's why I started to make my own... everything has deps ;-p |
| 13:56:17 | timlinux1: | cfarmer: ya - pity mapnik has deps - would be nice to incorporate it into QGIS for print rendering |
| 13:56:34 | timlinux1: | or as an alternate rendering backend |
| 13:56:54 | cfarmer: | timlinux1: I saw the awesome maps it was rendering... very nice.... |
| 13:57:13 | timlinux1: | cfarmer: I guess for writing out stuff in ftools you are using qgsvectorfilewriter always? |
| 13:57:24 | cfarmer: | timlinux1: yes |
| 13:57:45 | timlinux1: | I bet the features sit in mem there until you flush it |
| 13:58:07 | timlinux1: | When I have 5 spare secs I will poke around |
| 13:59:37 | cfarmer: | coolio... you might be right on that bet though... |
| 14:09:19 | wildintellect: | that, just brings up the idea of python eggs for easier python dep handling |
| 14:09:43 | wildintellect: | although I obviously prefer not adding deps it's not always the way to go |
| 14:25:32 | macho: | evng |
| 14:28:08 | : | * racicot pokes his head in for a minute... |
| 14:28:15 | racicot: | cfarmer: did you ping me? |
| 14:30:58 | macho: | argl - i like that - inserting a DVD to watch - and the first thing i see is a anti piracy spot ( which can't be cancelled ) |
| 14:31:34 | cfarmer: | racicot: I did... do you use QThreads at all in your python applications? |
| 14:32:07 | racicot: | yes... I have used them a few times |
| 14:32:16 | cfarmer: | macho: did you pay for the DVD ;-p |
| 14:33:07 | cfarmer: | racicot: ok, what do you do to catch python errors that might occur within the thread? just try/except? |
| 14:33:44 | racicot: | cfarmer: hold on and let me find you an example... |
| 14:33:48 | cfarmer: | I'm trying to avoid the python error dialog poping up and crashing QGIS... |
| 14:33:57 | cfarmer: | racicot: thanks! |
| 14:37:11 | racicot: | cfarmer: here is an example of an object that is run in a thread ( see above it ) and in the run method you can see we just use an try/except to catch the error and format it and pump it back out to the main thread as a message... |
| 14:37:13 | racicot: | http://trondheim.cs.washington.edu/cgi-bin/trac.cgi/browser/trunk/opus_gui/scenarios_manager/run/run_simulation.py#L111 |
| 14:37:15 | sigq: | Title: /trunk/opus_gui/scenarios_manager/run/run_simulation.py – UrbanSim Trac – Trac ( at trondheim.cs.washington.edu ) |
| 14:37:39 | racicot: | This is not with QGIS specifically... but in just a PyQt based app... but should be the same thing |
| 14:38:24 | racicot: | basically just catches the error and sends it off as a signal from the worker thread back to the main thread |
| 14:38:32 | : | * racicot is not sure that helps |
| 14:40:31 | cfarmer: | racicot: no that's good thanks... it just confirms what I've been doing, which is nice ;- ) |
| 14:41:12 | racicot: | very good. |
| 14:41:50 | : | * racicot is about to start writing up a workshop on QGIS featuring ftools as the "cool new thing" ;- ) |
| 14:41:54 | gsherman: | Got 4:48 seconds to waste? http://www.youtube.com/watch?v=f1iPe0LtCew&feature=player_embedded |
| 14:41:56 | sigq: | Title: YouTube - Map Of The World As We Know It ( at www.youtube.com ) |
| 14:42:55 | cfarmer: | racicot: excellent! I should probably put together a workshop myself for the foss4g in sydney... but deadlines are killing me at the moment... |
| 14:43:03 | : | * cfarmer goes to check the deadline... |
| 14:44:03 | racicot: | I will send you what I come up with... basically going to package a dataset and walk through 1 ) general qgis on it 2 ) using grass and ftools plugins on it 3 ) loading results into a custom app based on qgis |
| 14:44:11 | racicot: | in 45 minutes of course... |
| 14:44:31 | racicot: | gsherman: that video gives me a headache... |
| 14:44:46 | gsherman: | blame paul ramsey... |
| 14:44:55 | jctull: | timlinux1: ping |
| 14:45:59 | timlinux1: | jctull: hi |
| 14:46:04 | jctull: | timlinux1: hi |
| 14:46:13 | jctull: | Was there anything you needed this weekend? |
| 14:46:23 | jctull: | I saw the ping in the logs |
| 14:46:26 | cfarmer: | gsherman: wow.... |
| 14:46:27 | timlinux1: | jctull: I was actually looking for you in the week |
| 14:46:30 | timlinux1: | yeah |
| 14:46:38 | timlinux1: | I was trying to build the xcode project |
| 14:46:44 | timlinux1: | but it fails to find some libs |
| 14:46:54 | timlinux1: | I need to fire up the macbook to give specifics |
| 14:47:00 | jctull: | hmm, I returned to it this Sunday and yesterday with success |
| 14:47:07 | cfarmer: | cool that'd great racicot, thanks! |
| 14:47:24 | jctull: | the one issue was python where you need to set it to system if using stock python frameworks ( as I am ) |
| 14:48:52 | timlinux1: | jctull: will you be around for a few mins? I just need to finish this email I am working on |
| 14:48:52 | jctull: | I should be online tomorrow. After that, I'm pretty much in communicado until the 1st. |
| 14:48:57 | timlinux1: | then I will bug you :- ) |
| 14:49:02 | jctull: | yeah, I can hang for 10-15 minutes |
| 14:49:14 | : | * timlinux1 will be offline from fri - may 4 |
| 14:49:36 | jctull: | perfect. we are almost in synchronized escape |
| 14:49:54 | jctull: | finish your email... : ) |
| 14:51:42 | macho: | cfarmer: of course .. i bought the DVD today .. |
| 14:52:14 | jctull: | but what a deal it was! ; ) |
| 14:52:15 | macho: | cfarmer: and i'm definitely the wrong guy to make anti piracy ads .. i hate this things .. they should annoy the real pirates with it |
| 14:52:40 | cfarmer: | ... funny that they tell you not to steal...after you obviously just paid for it |
| 14:52:57 | jctull: | makes you want to steal ; ) |
| 14:53:05 | cfarmer: | hehe |
| 14:53:26 | macho: | thats what i find annoying in most cinemas too - i payed to watch the film - and what do i see before - ... anti piracy ads |
| 14:54:15 | macho: | at least stolen films have no such ads .. hmm - probably i should become unhonest .. and steal too |
| 14:55:35 | : | * gsherman suspects that macho has stolen a copy of qgis as well |
| 15:01:51 | macho: | gsherman: i did not! before april, 1st it was legal to download it.. ; ) |
| 15:04:41 | jctull: | timlinux1: I have to run for a bit and will be mostly tied up til past your bedtime. Send me an email if you can. Otherwise tomorrow. |
| 15:05:26 | timlinux1: | jctull: ok tomorrow |
| 15:06:12 | timlinux1: | macho: well don't worry all piracy has been cancelled now that the pirate bay has been found guilty of piracy |
| 15:06:37 | austin_: | I was here earlier asking about a Qt Progress bar. Someone recommended that QProgressBar will simply oscillate back and forth if min and max are set to -1. I haven't been successful in making this work so far. Here is the code snippet: QProgressBar *progressBar = new QProgressBar( mQGisIface->mainWindow( ) ); progressBar->setMaximum( -1 ); progressBar->setMinimum( -1 ); progressBar->show( ); |
| 15:06:45 | timlinux1: | who would have thought that people running a site called 'Pirate Bay' would have anything to do with piracy? |
| 15:07:09 | timlinux1: | austin_: try use 0 for min and mac |
| 15:07:12 | timlinux1: | max |
| 15:07:24 | austin_: | OK |
| 15:07:51 | cfarmer: | austin_: yes that was my bad, I said -1, but in fact I realised later it was 0... sorry for the confusion |
| 15:08:38 | cfarmer: | I posted the correction, but I must have missed you... |
| 15:10:57 | austin_: | Sorry. I had logged off. The 0 is an improvement. In my current test the progress bar moved about 30% instead of none before freezing as the main window went grey. Again, I'm using Ubuntu. Is there a good way to prevent the grey-out? |
| 15:14:10 | cfarmer: | not that I know of... I often get this behavior when running long scripts and tools as well... I guess I just ignored it in the past ;-p |
| 15:14:11 | sigq: | tracfeed: Ticket #515 ( enhancement closed ): Thoroughly use OGR <https://trac.osgeo.org/qgis/ticket/515#comment:8> |
| 15:15:15 | cfarmer: | austin_: you may have to processEvents( ) at regular intervals to avoid the freeze... |
| 15:15:32 | cfarmer: | you could do this wihtin a |
| 15:16:05 | timlinux1: | austin_: try putting you code into its own thread if poss |
| 15:16:11 | cfarmer: | you could do this within a timerEvent( ) |
| 15:16:32 | cfarmer: | or that...! |
| 15:16:45 | cfarmer: | what timlinux1 said ;- ) |
| 15:18:01 | jef: | *g* |
| 15:19:17 | austin_: | Great. Thanks for the advice. I'll try those things. |
| 15:20:01 | jef: | good to see everone is on the same page : ) |
| 15:20:31 | racicot: | austin_: I had a simple threading demo in my plugins repo that might get you kick started... http://qgisplugins.z-pulley.com/ |
| 15:21:29 | timlinux1: | austin_: main gotcha is if your thread tries to access data via a provider at the same time that main qgis thread does |
| 15:21:41 | timlinux1: | since providers aren't thread safe |
| 15:21:59 | timlinux1: | unless jef fixed that when I wasn't looking :- ) |
| 15:24:39 | austin_: | racicot: Thanks for the link. Does this work for a c++ plugin too? |
| 15:25:12 | racicot: | oh, I thought you were in python... c++ would be the same idea, just harder ;- ) |
| 15:27:08 | austin_: | I'll look into it, but this may all be beyond my pay-grade. Thanks again for the advice. |
| 15:29:05 | : | * racicot has to head out for a bit... |
| 15:29:08 | racicot: | later folks |
| 15:29:21 | cfarmer: | later racicot... |
| 15:29:37 | : | * cfarmer has to head out as well... cheers all! |
| 15:45:32 | austin_: | Bye and thanks! |
| 16:11:08 | jctull: | timlinux1: I have a few minutes if you are ready. |
| 16:11:46 | jctull: | no pressure of course |
| 16:15:36 | timlinux1: | jctull: hi |
| 16:15:40 | jctull: | hey |
| 16:15:43 | timlinux1: | ok let me start the macbook again |
| 16:16:12 | jctull: | ok, I'll be back and forth from the kitchen, so bear with me |
| 16:23:34 | : | * timlinux1 should really be heading to bed so he can go and vote in the elections tomorrow |
| 16:25:15 | jctull: | do that, be civic, we'll find each other online tomorrow! seriously |
| 16:25:30 | timlinux1: | ok |
| 16:25:35 | jctull: | later |
| 16:25:37 | timlinux1: | well I have it open now |
| 16:25:52 | jctull: | you glutton |
| 16:25:52 | timlinux1: | so let me quickly see what the error was |
| 16:26:00 | jctull: | np |
| 16:26:27 | timlinux1: | ah it was looking for spatialite.sqlite.h but not finding it |
| 16:26:42 | jctull: | did you install the spatialite source? |
| 16:26:51 | timlinux1: | and then also errors relating to Python.h |
| 16:27:04 | jctull: | his sqlite framework has spatialite support, but not spatialite binary, etc. |
| 16:27:07 | timlinux1: | jctull: no - I'd like to use the QGIS internal sources |
| 16:27:23 | jctull: | the python.h is the change to system in the user_config.xcconfig |
| 16:27:32 | timlinux1: | the 'sqlite amalgamation' |
| 16:27:54 | jctull: | might be a way to point to that, a good idea, but something I have not tried. |
| 16:28:04 | jctull: | Let me try that tonight and email you if I find success |
| 16:28:24 | jctull: | note the python error problem. I think that is the same I ran into last week |
| 16:28:28 | timlinux1: | ok thanks |
| 16:28:49 | jctull: | no worries |
| 16:28:55 | timlinux1: | which python options must I change? |
| 16:29:07 | timlinux1: | PYTHON_HAVE_system_? |
| 16:29:12 | timlinux1: | or PYTHON_FORM |
| 16:29:18 | jctull: | don't expect much in terms of achieving the spatialite stuff |
| 16:29:22 | jctull: | let me look |
| 16:30:38 | jctull: | form in qgis_user.xcconfig |
| 16:30:45 | jctull: | PYTHON_FORM = system |
| 16:30:45 | timlinux1: | ok |
| 16:31:00 | timlinux1: | so trying to build again |
| 16:31:11 | jctull: | that is the only change I currently have in the config file |
| 16:31:40 | timlinux1: | still getting lots of python errors |
| 16:31:48 | timlinux1: | do you make clean each time? |
| 16:31:53 | jctull: | are you on leopard or tiger? |
| 16:31:54 | timlinux1: | or close xcode? |
| 16:32:02 | jctull: | oh yeah, delete that build directory |
| 16:32:03 | timlinux1: | ( to make it register changes ) |
| 16:32:06 | timlinux1: | leopard |
| 16:32:14 | jctull: | I just nuke the build dir every time, that's all |
| 16:32:42 | timlinux1: | mac/xcode/build? |
| 16:33:47 | jctull: | yes |
| 16:33:51 | timlinux1: | jctull: did you successfully create a standalone bundle that is independent of williams frameworks? |
| 16:34:10 | jctull: | hmmm, I don't have the wife's computer handy to test. |
| 16:34:22 | jctull: | I did set everything to bundle |
| 16:34:28 | jctull: | but untested |
| 16:34:42 | jctull: | ( she's at a conference for a few days ) |
| 16:35:15 | jctull: | I did not build universal, I know that |
| 16:37:11 | timlinux1: | ok |
| 16:37:27 | timlinux1: | what is the procedure to build spatial lite stuff that you have been using? |
| 16:37:58 | jctull: | procedure? like I document anything ; ) |
| 16:38:04 | timlinux1: | install williams sqlite framework and download spatiallite from the website? |
| 16:38:24 | jctull: | pretty much |
| 16:38:30 | timlinux1: | I do have sqlite3.framework here |
| 16:38:49 | timlinux1: | which I guess I must have grabbed from the chaos site |
| 16:39:20 | jctull: | yes, but it was updated recently I believe |
| 16:40:49 | jctull: | I think I downloaded the libspatialite and spatialite-tools binaries, then copied the libs, headers, and binaries to appropriate /usr/local/* locations |
| 16:40:58 | jctull: | I had problems with the source |
| 16:41:45 | timlinux1: | ok |
| 16:41:48 | timlinux1: | thanks |
| 16:41:53 | timlinux1: | Ill try that tomorrow |
| 16:41:59 | timlinux1: | cheers all |
| 16:42:03 | jctull: | ok, that should work |
| 16:42:04 | jctull: | bye |
| 22:40:39 | sigq: | tracfeed: Ticket #1552 ( bug closed ): plug-in installer does not work behind proxy <https://trac.osgeo.org/qgis/ticket/1552#comment:5> |
| 23:33:21 | CIA-70: | jef * r10614 /trunk/qgis/src/app/qgsserversourceselect.cpp: translation string update |
| 23:33:22 | sigq: | tracfeed: Changeset [10614]: translation string update <https://trac.osgeo.org/qgis/changeset/10614> |
| 23:33:36 | CIA-70: | jef * r10615 /trunk/qgis/i18n/qgis_de.ts: german translation update |
| 23:36:09 | sigq: | tracfeed: Changeset [10615]: german translation update <https://trac.osgeo.org/qgis/changeset/10615> |