ShirazD joined the chat room. ShirazD ShirazD left the chat room. ShirazD "Leaving." ShirazD joined the chat room. ShirazD Souvent22 joined the chat room. Souvent22 jeffh joined the chat room. jeffh Souvent22 left the chat room. Souvent22 YesCT left the chat room. YesCT andrewl joined the chat room. andrewl ShirazD left the chat room. ShirazD "Leaving." ShirazD joined the chat room. ShirazD jim0203 joined the chat room. jim0203 ShirazD1 joined the chat room. ShirazD1 jim0203 left the chat room. jim0203 jim0203 joined the chat room. jim0203 ShirazD left the chat room. ShirazD Read error: 110 (Connection timed out) ShirazD1 left the chat room. ShirazD1 "Leaving." christefano left the chat room. christefano Read error: 104 (Connection reset by peer) christefano joined the chat room. christefano christefano left the chat room. christefano Read error: 104 (Connection reset by peer) christefano1 joined the chat room. christefano1 christefano1 left the chat room. christefano1 Read error: 104 (Connection reset by peer) christefano joined the chat room. christefano christefano left the chat room. christefano Read error: 104 (Connection reset by peer) christefano joined the chat room. christefano brianpuccio left the chat room. brianpuccio "Leaving." brianpuccio joined the chat room. brianpuccio brianpuccio left the chat room. brianpuccio Remote closed the connection YesCT joined the chat room. YesCT YesCT left the chat room. YesCT YesCT joined the chat room. YesCT Souvent22 joined the chat room. Souvent22 Souvent22 left the chat room. Souvent22 greggles joined the chat room. greggles brianpuccio joined the chat room. brianpuccio brianpuccio left the chat room. brianpuccio "Leaving." tom_o_t joined the chat room. tom_o_t Souvent22 joined the chat room. Souvent22 christefano left the chat room. christefano Read error: 104 (Connection reset by peer) bmadore joined the chat room. bmadore YesCT left the chat room. YesCT cds-mewald joined the chat room. cds-mewald YesCT joined the chat room. YesCT YesCT left the chat room. YesCT Client Quit cds-mewald left the chat room. cds-mewald jerdavis left the chat room. jerdavis Read error: 104 (Connection reset by peer) jerdavis joined the chat room. jerdavis christefano joined the chat room. christefano andrewl left the chat room. andrewl cds-mewald joined the chat room. cds-mewald ShirazD joined the chat room. ShirazD jerdavis left the chat room. jerdavis Read error: 104 (Connection reset by peer) jerdavis joined the chat room. jerdavis YesCT joined the chat room. YesCT cds-mewald left the chat room. cds-mewald tom_o_t is now known as tom_o_t-meeting. tom_o_t-meeting tom_o_t YesCT left the chat room. YesCT YesCT joined the chat room. YesCT YesCT left the chat room. YesCT tom_o_t-meeting is now known as tom_o_t. tom_o_t tom_o_t-meeting You left the chat by being disconnected from the server. You rejoined the room. christefano joined the chat room. christefano christefano left the chat room. christefano Remote closed the connection samtresler joined the chat room. samtresler samtresler s there currently any way to do proximity searches that exists? I know location module has a function I can call, but I don't see anything else built out. My current plan is to get a lattitude and longitude range and craft a db query that firsts pulls everythign in the longitude, then uses php to filter that on the latitude, and run the location module proximity function on the results that are left. realjimshady Bdragon28: ping, can you answer this question for samtresler if you're around? Bdragon28 Geo.module is built for that sort of thing, but isn't quite finished yet If you're writing your own code it's very useful though. Otherwise, you can use the functions from earth.inc from location, like you said samtresler hrm, Are Geo and location mutually exclusive, or can they exist side-by-side Bdragon28 They can exist side by side Actually, geo will be taking over the coordinate storage of location.module in the future (in my copious free time(tm)) samtresler Yeah, this latest project I really could have used that, but hopefully will turn around and submit some patches for you once I clean this mess up. Bdragon28 Geo is the "right" way to solve the problem -- location was around before spatial support was in mysql and the proximity stuff is a horrible, horrible hack. zzolo ive seen geo do the proximity stuff on a site just an fyi, that its in there. though, it still is in heavy devleopment samtresler Good to know. This is basically for a custom block that doesn't need to be alive much past Oct. 2 so heavy development is OK if the current instantiation works. Bdragon28 Or you could just do it manually zzolo well, i cant guarantee that that is the case Bdragon28 (spatially enable a table and write a simple spatial query) zzolo if you have location going, i think you will find it easier to put together a solution with its api or what bdragon is saying Bdragon28 Refrences: http://dev.mysql.com/doc/refman/5.1/en/spatial-extensions.html (explains what pieces are in mysql), http://postgis.refractions.net/documentation/manual-1.4/ (PostGIS for PostgreSQL is a superior implementation. Some of the documentation from it is useful still when working in mysql.) oh, and http://en.wikipedia.org/wiki/Simple_Features for an explanation of the syntax for representing data YesCT joined the chat room. YesCT tom_o_t left the chat room. tom_o_t You left the chat by being disconnected from the server. You rejoined the room. You are now known as zzolo. zzolo bmadore left the chat room. bmadore YesCT left the chat room. YesCT arianek left the chat room. arianek jeffh left the chat room. jeffh ShirazD left the chat room. ShirazD "Leaving." You left the chat by being disconnected from the server. You rejoined the room. samtresler left the chat room. samtresler Souvent22 left the chat room. Souvent22 jeffh joined the chat room. jeffh You left the chat by being disconnected from the server. You rejoined the room. Souvent22 joined the chat room. Souvent22 jerdavis left the chat room. jerdavis holmes.freenode.net irc.freenode.net arianek left the chat room. arianek holmes.freenode.net irc.freenode.net jim0203 left the chat room. jim0203 holmes.freenode.net irc.freenode.net Bdragon28 left the chat room. Bdragon28 holmes.freenode.net irc.freenode.net Souvent22 left the chat room. Souvent22 holmes.freenode.net irc.freenode.net jeffh left the chat room. jeffh holmes.freenode.net irc.freenode.net brianpuccio left the chat room. brianpuccio holmes.freenode.net irc.freenode.net realjimshady left the chat room. realjimshady holmes.freenode.net irc.freenode.net Druplicon left the chat room. Druplicon holmes.freenode.net irc.freenode.net ekes left the chat room. ekes holmes.freenode.net irc.freenode.net Souvent22 joined the chat room. Souvent22 arianek joined the chat room. arianek jeffh joined the chat room. jeffh jerdavis joined the chat room. jerdavis jim0203 joined the chat room. jim0203 realjimshady joined the chat room. realjimshady Bdragon28 joined the chat room. Bdragon28 ekes joined the chat room. ekes Druplicon joined the chat room. Druplicon arianek left the chat room. arianek christefano joined the chat room. christefano ShirazD joined the chat room. ShirazD christefano1 joined the chat room. christefano1 christefano left the chat room. christefano Success Souvent22_ joined the chat room. Souvent22_ Souvent22 left the chat room. Souvent22 Read error: 104 (Connection reset by peer) jeffh left the chat room. jeffh christefano1 left the chat room. christefano1 Read error: 110 (Connection timed out) brianpuccio joined the chat room. brianpuccio jeffh joined the chat room. jeffh Souvent22_ left the chat room. Souvent22_ andrewl joined the chat room. andrewl ShirazD1 joined the chat room. ShirazD1 ShirazD left the chat room. ShirazD Read error: 110 (Connection timed out) andrewl left the chat room. andrewl ShirazD1 left the chat room. ShirazD1 "Leaving." brianpuccio left the chat room. brianpuccio "Leaving." brianpuccio joined the chat room. brianpuccio brianpuccio left the chat room. brianpuccio Read error: 104 (Connection reset by peer) Souvent22 joined the chat room. Souvent22 brianpuccio joined the chat room. brianpuccio brianpuccio left the chat room. brianpuccio Read error: 54 (Connection reset by peer) greggles joined the chat room. greggles Souvent22 left the chat room. Souvent22 tom_o_t joined the chat room. tom_o_t Souvent22 joined the chat room. Souvent22 jim0203_ joined the chat room. jim0203_ jim0203 left the chat room. jim0203 Success jim0203_ is now known as jim0203. jim0203 jim0203_ tmcw joined the chat room. tmcw tmcw left the chat room. tmcw mikehostetler joined the chat room. mikehostetler bmadore joined the chat room. bmadore bmadore left the chat room. bmadore ShirazD joined the chat room. ShirazD cds-mewald joined the chat room. cds-mewald YesCT joined the chat room. YesCT cds-mewald left the chat room. cds-mewald tmcw joined the chat room. tmcw bryn-echoditto joined the chat room. bryn-echoditto arianek joined the chat room. arianek ShirazD left the chat room. ShirazD "Leaving." Souvent22 left the chat room. Souvent22 Souvent22 joined the chat room. Souvent22 ShirazD joined the chat room. ShirazD YesCT left the chat room. YesCT Souvent22_ joined the chat room. Souvent22_ Souvent22 left the chat room. Souvent22 Connection reset by peer spydmobile joined the chat room. spydmobile Souvent22_ left the chat room. Souvent22_ You left the chat by being disconnected from the server. You rejoined the room. brianpuccio joined the chat room. brianpuccio mikehostetler left the chat room. mikehostetler "Leaving." s4j4n left the chat room. s4j4n Read error: 131 (Connection reset by peer) bryn-echoditto left the chat room. bryn-echoditto jeffh left the chat room. jeffh ShirazD left the chat room. ShirazD "Leaving." You left the chat by being disconnected from the server. You rejoined the room. jeffh joined the chat room. jeffh arianek left the chat room. arianek greggles left the chat room. greggles verne.freenode.net irc.freenode.net spydmobile left the chat room. spydmobile verne.freenode.net irc.freenode.net jerdavis left the chat room. jerdavis verne.freenode.net irc.freenode.net jeffh left the chat room. jeffh verne.freenode.net irc.freenode.net cds-mewald left the chat room. cds-mewald verne.freenode.net irc.freenode.net jeffh joined the chat room. jeffh cds-mewald joined the chat room. cds-mewald spydmobile joined the chat room. spydmobile jerdavis joined the chat room. jerdavis Druplicon left the chat room. Druplicon Excess Flood Druplicon joined the chat room. Druplicon Druplicon left the chat room. Druplicon Excess Flood Druplicon joined the chat room. Druplicon You left the chat by being disconnected from the server. You rejoined the room. YesCT joined the chat room. YesCT ShirazD left the chat room. ShirazD "Leaving." ShirazD joined the chat room. ShirazD Souvent22_ joined the chat room. Souvent22_ Souvent22 left the chat room. Souvent22 Read error: 104 (Connection reset by peer) Souvent22_ left the chat room. Souvent22_ Read error: 104 (Connection reset by peer) Souvent22 joined the chat room. Souvent22 brianpuccio left the chat room. brianpuccio "Leaving." Souvent22 left the chat room. Souvent22 greggles joined the chat room. greggles greggles left the chat room. greggles Remote closed the connection Souvent22 joined the chat room. Souvent22 Souvent22 left the chat room. Souvent22 Read error: 104 (Connection reset by peer) Souvent22 joined the chat room. Souvent22 Souvent22_ joined the chat room. Souvent22_ Souvent22 left the chat room. Souvent22 Read error: 104 (Connection reset by peer) cds-mewald left the chat room. cds-mewald brianpuccio joined the chat room. brianpuccio brianpuccio left the chat room. brianpuccio Remote closed the connection YesCT left the chat room. YesCT Souvent22_ left the chat room. Souvent22_ jeffh left the chat room. jeffh Souvent22 joined the chat room. Souvent22 Souvent22 left the chat room. Souvent22 Client Quit jeffh joined the chat room. jeffh ShirazD left the chat room. ShirazD Read error: 110 (Connection timed out) jeffh left the chat room. jeffh gagarine joined the chat room. gagarine gagarine hello :) brianpuccio joined the chat room. brianpuccio brianpuccio left the chat room. brianpuccio "Leaving." YesCT joined the chat room. YesCT YesCT left the chat room. YesCT Client Quit jim0203 joined the chat room. jim0203 jim0203 left the chat room. jim0203 Client Quit jim0203 joined the chat room. jim0203 Souvent22 joined the chat room. Souvent22 tmcw joined the chat room. tmcw greggles joined the chat room. greggles gagarine left the chat room. gagarine Read error: 110 (Connection timed out) Souvent22 left the chat room. Souvent22 tom_o_t joined the chat room. tom_o_t mikehostetler joined the chat room. mikehostetler mikehostetler left the chat room. mikehostetler Remote closed the connection Souvent22 joined the chat room. Souvent22 tobiassjosten joined the chat room. tobiassjosten kbell joined the chat room. kbell kbell left the chat room. kbell Remote closed the connection kbell joined the chat room. kbell tmcw left the chat room. tmcw tmcw joined the chat room. tmcw gnat_x joined the chat room. gnat_x gnat_x hey folks. a while back i was in here a bunch asking about GMap module macro stuff in views. in the crush of deadline time, and the business of summer, i never came back to talk about a real solution to the hacks that i made to gmap to do dynamic macro handling. anyway, the main thing i'm looking for right now is the best place to start the discussion, it it g.d.o? err is it greggles gnat_x: I'd say so, yes gnat_x: or the issue queue, if it's down to one module zzolo yeah, i second greggles maybe both, actually, start and issue and then maybe try to get some discussion around it on g.d.o gnat_x okay. it is definitely down to one module. i made a patch file so i could find my changes. tmcw zzolo: hey, how's it going? zzolo hey tmcw. not too bad. busy, busy as usual. how about you? tmcw yep, always pretty packed with work over here but cool stuff, so I can't complain zzolo yeah, i dont alwyas have the cool stuff to work on. :( but so it goes hence why i spend too much time outside of drupal job, doing drupal :) tmcw Ha, yeah.. to be honest, when I spend time outside of this job I use django :) Which gets me lots of flak with the coworkers zzolo i dont knwo too much about it, but form what i understand its a good system Drupal is not always the answer ducks gnat_x i have a buddy that swears by django. tmcw Haha, that should be on the homepage. Using other stuff is good for perspective if nothing else gnat_x indeed. tmcw Too much religiousness in frameworks/cms'es, too little science gnat_x i'm tempted to learn it django for the opportunity to get away from php for a bit. tmcw zzolo: anyway, I'm interested in your thoughts on the 2.x branch zzolo i figured as much. :) tmcw Hah, yep, predictable zzolo well, most of my thoughts are in that issue the big thing for me is to actually create it together in a nice open fashion with incremental changes and history. my thoguht was alwyas to help speed this a long so that you guys can get back to what you were doing but, today i came up with the thought of jsut doing it all this weekend tmcw Well, so, yeah zzolo of making the ports of your version into the 2.x version and just being done with it tmcw We can pretty easily make our entire version history public With diffs, etc., and possibly even get all of those things ported to CVS with some svn/git magic The main concern at this point is really time, and we're under a serious time crunch The principle is that openlayers is going to be an external for a bigger project which we've built around the 2.x branch zzolo well, thats the thing for me, i dont really have the incentive to sacrifice the right way for your time to be blunt (also, not just my decision) tmcw Yeah, I understand that Like, for instnace If we could get it tagged as alpha or tagged as 3 and move between the two, then that would be great zzolo does the drupal cvs do a 0.x version. i think so how about a 0.x version? i dont want to take up the 2.x branch i mean 3 tmcw understandable I mean, a 0.x branch is fine by me I think that there are a few problems here The changes in 2.x aren't going to be a weekend to dissolve into patches zzolo yeah, i am definitely interested in hearing about that in more detail bryn-echoditto joined the chat room. bryn-echoditto zzolo from the code i ahve seen, it doesnt seem all the caomplicated bryn-echoditto harro zzolo hey (also, its alreayd been written) either way, a 0.x version woudl solves everyones problem (though it would be a little messy in the repo, but i can get past that) and i wouldnt have to rush to make large changes over the weekend though, i might make some large changes over the weekend :) tmcw I'm fine with that, and then 2.x could be the place where those changes are ported from 1.x? bryn-echoditto can you guys catch me up real quick? zzolo well, coming from that issue tmcw basically, we (me, rsoden) are interested in getting the 2.x codebase up on d.o soon because there is a time crunch in which it will be an external zzolo and, i personally dont have the incentive to sacrifice the right way for their time tmcw and we really don't want to branch or take another namespace or anything like that because it would be crappy for the project & everyone zzolo so, a 0.x version where we dump their code could solve both problems and then we can start to flesh out the 2.x branch the right way bryn-echoditto that makes some sense to me but like if this whole thing has just been wrangling over verbiage well i think that's kind of stupid i agree that we need both codebases online and preferably under one project and preferably arranged in a way that we can be sort of splicing them together bit by bit in the public repo tmcw zzolo: I understand your problems with the fact that this dev wasn't on drupal.org and, I guess you've never gotten the full answer as to why basically, we were running with openlayers in a big project and needed the changes in the codebase and it sucks that we weren't able to discuss all of the changes with you, phayes, and bryn zzolo i talked with eric. i understand wehre you are coming from and it makes sense. thats how most things get done but. that doesnt mean we can jsut blindly take your code. not blindly in that we cant see, but blindly in that we are not discusssing its parts in an open fashion in a meaningful way i shoudl nto use we dont get me wrong, i like the changes you have made, and dont really want to re-code a lot of it but, i think its important to put them in as parts and discuss them i know you guys have put a lot of work into it, and my goal is to avoid work for everyone but, i dont think we can do this without having to do some extra work on everyone's part tmcw I mean, we're totally 100% up for discussing every big change made to the codebase And also up for porting all of the changes which happened after we branched If there's something that's seriously distasteful to everyone in the project, then of course it will be nuked spydmobile left the chat room. spydmobile "Page closed" tmcw I'm already trying to create issues for all of the serious changes in the version, trying to explain stuff like the behaviors unification zzolo thats awesome as far as logistics, does a 0.x version solve your time needs? tmcw That's great, solves my problem We should talk about how to eventually merge this into 2.x, but as soon as this gets on 0.x, at least my/rsoden/yhahn/etc's work will move entirely there zzolo ok, so heres my proposal. lets do the 0.x version and put your current version of it in there. then, if we want to discuss how to do the 2.x branch some more, then we have time to do that. otherwise, i will volunteer my sunday to porting as much as your changes over as i can (it also gives me a chance to understand it all better) tmcw That sounds great. zzolo hey, si robert there? he jsut sent me an email. he shoudl proabbyl know about this tmcw yeah - let me see if I can get him in zzolo ping Bdragon28 robertsoden joined the chat room. robertsoden tmcw hey robertsoden robertsoden so what'd i miss? (hey everybody) zzolo ha hey robertsoden robertsoden :) zzolo maybe its just best if i paste the log somewhere robertsoden haha ok zzolo http://drupalbin.com/11511 thats not that readable, sorry well, the gist of what we arecoming to is this you guys have this version that has some good work. but you also have a client need to have that version in the openlayers drupal repo i think making incremnetal changes to our version is more of the right way, then just putting in your version we shoudl be able to do a 0.x version of your code in the drupal cvs tmcw ( http://dpaste.com/97265/ ) zzolo this will address your client need and allow you to have your code ina more public place tom_o_t is now known as tom_o_t-lunch. tom_o_t-lunch tom_o_t zzolo this will also allow us to have a reall discussion about how to do the 2.x branch that is not affected by your clients' needs robertsoden hey reading this now zzolo and to address teh difference on the 2.x branch, i have volunteered by sunday to making some of the larger archectural changes, porting them form yours to the current 2.x branch ok, ill wait robertsoden ok this all sounds god im much less concerned about the 0.x stuff but thanks, that helps us in our immediate bind zzolo ok, well heres my question to you guys. if we disregard time needed to port things, do you really think that putting your code into the 2.x branch and porting pur changes over, is really a good, fair, open process to take for the openlayers module on d.o? robertsoden to be honest, i dont think its as not-open and unfair as its being portrayed it sounded to me like you guys were all on board with the general direction we wanted to take and we've tried to be open about what got changed and why so yeah, we could get really into the weeds about the exact implentation but i dont know how that helps us zzolo well, lets compare it to the drupal core development. if someone branched ot on 6.1 and made some awesome changes, do you think the community would ust be like: "sure, lets just start with your version." when we are at 6.15 the value is in the issue threads and the cvs changes robertsoden sure, agreed zzolo and having incremental changes and parts robertsoden but the kind of architecture changes we are all shooting for zzolo i want to put (most of) your changes into the module cause they are awesome! that is what we are on board with. but how to do that is where we differ robertsoden at least i think we are all on the same page about gagarine joined the chat room. gagarine robertsoden arent really comparable to a 6.1 => 6.15 update at any rate zzolo sure, its just an anolgy of process, not of code robertsoden but i think youve made it pretty clear that the 2.x branch will start with 1.x and i think we're basically resigned to that bryn-echoditto fwiw i'm happy to do some heavy lifting trying to merge the branches actually robert on that point let me hear your reaction to what i was saying to zzolo yesterday which is that zzolo robertsoden: i havent made any decisions, i just havent heard anything to change my mind i like discussion bryn-echoditto in my opinion it's much easier to graft our 1.x interfaces and features (to the extent that they differ) onto the ctoolsish codebase you guys have put together pattyhayes joined the chat room. pattyhayes zzolo and i want everyones input bryn-echoditto than to try to slip ctools underneath our functionality robertsoden i mean i totally agree with that bryn bryn-echoditto so before we make any pronouncements on 2.x zzolo well, i woudl love to hear more details on that, because its easy to see the details of what we have done, but i have to go through the whole code base to see all the chagnes you have made bryn-echoditto well what i was gonna say is before we get cracking on 2.x doing any merging, etc. i think it's only fair to ask zzolo and phayes to get familiar with ctools and also with the devseed OL codebase robertsoden totally bryn-echoditto i'd be a lot more comfortable lending a hand pulling 1.x stuff on top of the "0.x" codebase than the reverse i know you said you're pretty consumed this next little while, zzolo especially with the move and all but it seems like this is the only fair and intelligent way to move forward so maybe once you feel that 1.x is stable enough for now which, imho, is pretty soon robertsoden zzolo is there stuff we can to facilitate you getting familiar with the 0.x? bryn-echoditto it'd be a good idea to shift this to the top of the list zzolo this is not about being familar witht he code 1) i think i understand it jsut fine 2) this module is large enough where i dont expect to know every line robertsoden ok good zzolo as far as time and effort, if youa re going to compare what is easier, we need some sort of quantification of it. i attempted that in the issue but, for me its nto about time and effort, its about process and that is why i am offering a day of my time to attempt to make these ports int eh right way, imo bryn-echoditto sry i probably missed some stuff while i was grabbing lunch -- which way are you referring to when you say the right way? zzolo well, the "right" way is the way i have been describing all along. taking the 1.x branch and porting devseed's version on top if in incremental, rational, and discussed aprts tmcw That sounds like a week or two minimum, not a sunday? bryn-echoditto err zzolo my question for you bryn-echoditto, is if it was nto a matter of time or effort, which way do you see as being the better for the project? tmcw: well, then enlighten me. cause honeslty lookign at your code, its a long day, but it diesnt seem like two weeks worth. at least given that the code is there bryn-echoditto zzolo: i mean i think if you consider general coding principles, you always wanna put leaves onto branches onto tree trunks and i think what 0.x is, is a new tree trunk not to be confused with scm terminology zzolo like, i have estimated that i put in a weeks worth of time since fork, and it would be a day to wort that over in my opinion since the worsk mostly been done tmcw the dependencies of the code are not easily to dissolve. Like, parting out openlayers_ui, changing openlayers_views to just provide an page/block hook... bryn-echoditto it totally redoes the underlying code flow of the module, so far as i understand tmcw Rewriting all behaviors and starting from scratch, basically, in openlayers.js bryn-echoditto i don't think doing it this way is going to screw up the upgrade path any more than doing it the other way zzolo at the moent, there is no upgrade path tmcw I don't think there can or should be one zzolo why do you say that? robertsoden zzolo can you describe what an upgrade path would look like? zzolo what about the peopel using 1.x now, that will eventually want to go to 2.x? yeah, an update function to change map preset in the database to map presets in the new structure. and documentation on api changes tmcw Trust me, there will be loads of documentation on the api changes I want to document the *($ out of this bryn-echoditto i think we can keep an upgrade path open without THAT much extra work, to be honest robertsoden tmcw - whats the issue with upgrading the presets? (also layers, behaviors, styles, no?) tmcw layer presets will be simple to update, but automatically updating views into two views? moving the information that used to be in views into presets? bryn-echoditto yeah, the views portion is gonna be a little wonky, admittedly i don't believe it's impossible i believe everything else will be trivial tmcw I don't think it's impossible either bryn-echoditto but look robertsoden views is always wonky :P bryn-echoditto that would happen no matter which way we do this zzolo fair enough, that does seem a little difficult. but an upgrade path does nto mean everything has to change at button, but it has to be well documented bryn-echoditto with 0.x on bottom or 1.x on bottom it's an issue both ways tmcw I just think that the manual upgrade path isn't that crazy, and there are 100 max people who will have to do it +1 documentation zzolo +5 documentation robertsoden agreed zzolo :) robertsoden lol ok but still in terms of fairness and openness - it seems like all the contributors have read the 0.x branch are familiar with it and like the general direction if not exact implementation tmcw And we're very willing to document the changes in issues robertsoden im not getting why this is being painted as such a closed process? i get why its not ideal, but we're hardly being shady zzolo i dont think youre being shady. :) at all robertsoden so seriously then, why is this such a bad approach? i should also point out that i thought that this is what we were doing the whole time, so i completely misread the conversation and that's my bad, so apologies zzolo i was not that clear about my intentions. though i had never assumed your path persontally, i think there is a lot of value in doing things in an incremental fashion. by making specific changes that get discussed (not necessaryily challenged). a lot like how drupal core is developed. if we jsut start with your version, i dont see that process able to happen. and i see it as having to go through and take out things that we might not agree with, and add the stuff that we have already worked on. it seems like a pretty big loss for this project so far, except that we get some cool code bryn-echoditto usually i'd agree wholeheartedly, but i think the issue is incrementality robertsoden do you have a list of things you dont agree with in mind? could we make individual issues for these things? bryn-echoditto these changes are sweeping enough that it would make more sense to discuss them in a broad architectural sense all together and then begin with what we decide after that conversation robertsoden and i think everyone is willing to sprint together on the merge, regardless of which direction it goes in zzolo well, its not that i disgree with taking out the presets and replacing them with ctools plugins its just that that shoudl happen in a single issue and in single or set of commits, and so if someone comes along, they dont have to go throgh every line of code to see what has happened, and they will know why thigs were decided robertsoden: well, from your intial reaction, i did not get that idea but, that was my thoght from the beginning, do a sprint where we put this all together tmcw This is what we're offering to do, by documenting the changes? Giving people descriptions and justifications of the changes The only difference is the missing cvs history and prior discussion of the changes robertsoden i mean there's already issues open for a lot of the changes made in the 0.x branch would be pretty straightforward to add descriptive comments in there that describe how things are done or have conversations about the specific implementations zzolo "he only difference is the missing cvs history and prior discussion of the changes" i feel those thigns are pretty important robertsoden yes, ideally they would be in there but there are some things we can do to get us pretty close, no? zzolo so, you guys are willing to port over all the things that have been done in the 1.x branch. all the documentation, bug fixes, etc, instead of pulling in your already-done, exciting, architectural changes inot the 1.x branch? samtresler joined the chat room. samtresler tmcw I mean, the level of work and the reasons why we'd do each are wildly different samtresler Hey all, we are still smashing bugs but it finally launched. Just wanted to say a big thank you to everyone who helped me by writing the modules that made possible. http://www.livestrongaction.org/map zzolo samtresler: congrats! you have a link? tmcw samtresler: congrats robertsoden ha, sweet samtresler needs to catch up on sleep this week. tmcw samtresler: also, you might want to make sure that it has openstreetmap attribution or you might get a nastygram from them samtresler Ah, interesting will look into that. happy to give them a link somewhere, just need to clear it through 40 layers of campaign strategists :( tmcw Ha, yeah. We're currently figuring out how to make the link to osm pretty and all. but like lots of other open-source stuff, the license is indeed a serious legal doc samtresler yes, totally robertsoden zzolo - that has been basically my understanding of what the plan has been all along samtresler SHould be able to get something up there soon. zzolo well, robertsoden and tmcw, i gotta focus more on work. ill think about this some more tonight. honestly im not that convinced. maybe phayes will have some more opinions. either way, we'll get it worked out. my thought right now is me attempting to make the changes over the weekend and see how that works. but, no decisions for me yet. but, lets talk 0.x tmcw: are you comfortale enough with d.o cvs to make that happen? otherwise, i can do it at some point this evening. its basically doing what i did for the 2.x branch checking out head, removing everything, putting in your code, then branching it tom_o_t-lunch is now known as tom_o_t. tom_o_t tom_o_t-lunch tmcw_ joined the chat room. tmcw_ robertsoden_ joined the chat room. robertsoden_ zzolo tmcw_: robertsoden_ you guys have some internet things going on robertsoden_ whoops internet over here blipped so where are we? zzolo what was the last ting you hear? robertsoden_ samtresler: SHould be able to get something up there soon. zzolo zzolo : well, robertsoden and tmcw, i gotta focus more on work. ill think about this some more tonight. honestly im not that convinced. maybe phayes will have some more opinions. either way, we'll get it worked out. my thought right now is me attempting to make the changes over the weekend and see how that works. but, no decisions for me yet. but, lets talk 0.x [12:31p] zzolo: tmcw: are you comfortale enough with d.o cvs to make that happen? otherwise, i can do it at some point this evening. [12:32p] zzolo: its basically doing what i did for the 2.x branch [12:32p] zzolo: checking out head, removing everything, putting in your code, then branching it robertsoden_ ok zzolo robertsoden_: im all about geting you cvs access, but Bdragon28 is hard to get a hold of robertsoden_ tmcw's eating but yeah, we can make a 0.x branch Bdragon28 notices the popup robertsoden_ that helps our immediate problem zzolo :) Bdragon28 Who needs acceess to what now? zzolo hey Bdragon28 it would be seet to get robertsoden_ (drupal name rsoden) access to openlayers *sweet Bdragon28 30 seconds please zzolo 1 2 3 ... :) Bdragon28 CVS access has been granted to rsoden. tmcw left the chat room. tmcw Read error: 113 (No route to host) tmcw_ is now known as tmcw. tmcw tmcw_ zzolo Bdragon28: much obliged, good buddy robertsoden_ w00t Bdragon28 Welcome aboard gagarine left the chat room. gagarine robertsoden_ so yeah zzolo i really think trying to make these changes all in one day will be rough robertsoden left the chat room. robertsoden Read error: 110 (Connection timed out) zzolo somehwere in the distnant laugh i hear roberts maniacal alughter robertsoden_ heh zzolo god, i cant type today robertsoden_ but i wont stop you from trying :P zzolo it might be best for me to try, since i seem to be pretty stubborn about it but, ill let you know tonight or tomorrow, and it will happen this weekned if it does robertsoden_: good talking. thanks for the discussion. let me know if you need any assistance with the 0.x branch. feel free to put up a note on teh project page and on that issues. im gonna go get some food robertsoden_ ciao gagarine joined the chat room. gagarine robertsoden_ left the chat room. robertsoden_ ShirazD joined the chat room. ShirazD gagarine hello, I have a problem with geocode wiget... If i use node_save (in rules for exemple) geo value is reset to 0 see http://drupal.org/node/585526 Druplicon http://drupal.org/node/585526 => geocode_widget_form_validate is not run on node_save and geo field are set to 0 => Geocode, Code, critical, active, 0 comments, 1 IRC mention gagarine Any body have an idea to workaround or the good way to change geocode or geo? bryn-echoditto sql hacks! bryn-echoditto left the chat room. bryn-echoditto tmcw Is the other module one that you're developing? Your problem is generally the problem with node_save etc., since the API sucks, it's not symmetrical - you can get and then save something and lose information Probably the solution to your problem is to save the value of the field that the geocode widget is determining and then reset it back when you call node save ( http://drupal.org/node/218862 ) Druplicon http://drupal.org/node/218862 => node_save() with CCK fields => Content Construction Kit (CCK), General, normal, active, 6 comments, 1 IRC mention tmcw thank you, Druplicon. tmcw left the chat room. tmcw ShirazD left the chat room. ShirazD Read error: 54 (Connection reset by peer)