|
|
Patch Set 1 #
Total comments: 5
Patch Set 2 : updated python code #
Total comments: 23
Patch Set 3 : fixed a bug on removing mid stops #Patch Set 4 : added comments #Patch Set 5 : updated #Patch Set 6 : renamed functions #Patch Set 7 : updated #
MessagesTotal messages: 19
enabled deleting stops from patterns server url: http://211.100.227.25:8765/
Sign in to reply to this message.
http://codereview.appspot.com/627041/diff/1/3 File transitfeed_editor.py (right): http://codereview.appspot.com/627041/diff/1/3#newcode116 transitfeed_editor.py:116: """Delete stoptime from certain pattern""" Given the stop_id, stop_sequence and trip_id, delete stoptime from certain pattern. Besides, seems "deleteStop" is not used in this function. http://codereview.appspot.com/627041/diff/1/3#newcode130 transitfeed_editor.py:130: tripId)) I don't think we need to update the stop_sequence for the stops after the deleted one, because according to GTFS format, the stop_sequence must increase along the trip, but they are not promised to be consecutive, it means that stop sequences like 0, 3, 10 ... are also fine. http://codereview.appspot.com/627041/diff/1/3#newcode530 transitfeed_editor.py:530: def DeletePattern(self, patternId, sequence, stopId, schedule): Please change to a better function name, because "DeletePattern" means deleting the whole pattern.
Sign in to reply to this message.
Your demo seems to be down. On Thu, Mar 18, 2010 at 6:06 PM, <calidion@gmail.com> wrote: > Reviewers: lychen, xan_google.com, weiliu, leio.chen, baiming, qiaojian, > > Message: > enabled deleting stops from patterns > > server url: > http://211.100.227.25:8765/ > > > > Please review this at http://codereview.appspot.com/627041/show > > Affected files: > M gtfsscheduleviewer/files/transit_editor.js > M schedule_editor.py > M transitfeed_editor.py > > > -- Ming Bai 白明 Software Engineer Google Inc. Tel(Office): 86 (10) 6250-3361 Tel(Cell): +86-159-0153-4908 Email: baiming@google.com
Sign in to reply to this message.
it is ok now. 2010/3/19 Ming Bai 白明 <baiming@google.com> > Your demo seems to be down. > > On Thu, Mar 18, 2010 at 6:06 PM, <calidion@gmail.com> wrote: > > Reviewers: lychen, xan_google.com, weiliu, leio.chen, baiming, qiaojian, > > > > Message: > > enabled deleting stops from patterns > > > > server url: > > http://211.100.227.25:8765/ > > > > > > > > Please review this at http://codereview.appspot.com/627041/show > > > > Affected files: > > M gtfsscheduleviewer/files/transit_editor.js > > M schedule_editor.py > > M transitfeed_editor.py > > > > > > > > > > -- > Ming Bai 白明 > Software Engineer > Google Inc. > Tel(Office): 86 (10) 6250-3361 > Tel(Cell): +86-159-0153-4908 > Email: baiming@google.com >
Sign in to reply to this message.
updated python code http://codereview.appspot.com/627041/diff/1/3 File transitfeed_editor.py (right): http://codereview.appspot.com/627041/diff/1/3#newcode116 transitfeed_editor.py:116: """Delete stoptime from certain pattern""" On 2010/03/18 14:18:50, weiliu wrote: > Given the stop_id, stop_sequence and trip_id, delete stoptime from certain > pattern. > > Besides, seems "deleteStop" is not used in this function. Done. http://codereview.appspot.com/627041/diff/1/3#newcode130 transitfeed_editor.py:130: tripId)) On 2010/03/18 14:18:50, weiliu wrote: > I don't think we need to update the stop_sequence for the stops after the > deleted one, because according to GTFS format, the stop_sequence must increase > along the trip, but they are not promised to be consecutive, it means that stop > sequences like 0, 3, 10 ... are also fine. Done.
Sign in to reply to this message.
http://codereview.appspot.com/627041/diff/6001/7002 File transitfeed_editor.py (right): http://codereview.appspot.com/627041/diff/6001/7002#newcode528 transitfeed_editor.py:528: def DeletePattern(self, patternId, sequence, stopId, schedule): Rename it to "DeleteStopTimeFromPattern" http://codereview.appspot.com/627041/diff/6001/7002#newcode535 transitfeed_editor.py:535: db.DeleteTripStoptime(sequence, stopId, tripIds) Rename it to "DeleteStopTimeFromTrip"
Sign in to reply to this message.
Wenxin, As we are supporting the stop deletion, did you carefully consider the garbage collection problem? Will the memory of deleted objects be properly collected? http://codereview.appspot.com/627041/diff/6001/7001 File gtfsscheduleviewer/files/transit_editor.js (right): http://codereview.appspot.com/627041/diff/6001/7001#newcode1673 gtfsscheduleviewer/files/transit_editor.js:1673: * @param {Stop} instop Stop to be determined instop is not a good parameter name. It is a little misleading. I think "stop" is enough. http://codereview.appspot.com/627041/diff/6001/7001#newcode2083 gtfsscheduleviewer/files/transit_editor.js:2083: * @param {Boolean} isSet Set stoptime tag or not isSet doesn't tell what is to set. And what does stoptime tag mean? Please rephrase the description to make it clearer. http://codereview.appspot.com/627041/diff/6001/7001#newcode2085 gtfsscheduleviewer/files/transit_editor.js:2085: Trip.prototype.onDeleteStop = function(stop, isSet) { It isn't a handler, is it? Use verbal function name, such as "deleteStop". http://codereview.appspot.com/627041/diff/6001/7001#newcode2101 gtfsscheduleviewer/files/transit_editor.js:2101: fromLeg.getGDirections(); You also need to set this.stops[i + 1].fromLeg[shape.id] = null. http://codereview.appspot.com/627041/diff/6001/7001#newcode2117 gtfsscheduleviewer/files/transit_editor.js:2117: Trip.prototype.deleteStoptime = function(stoptime) { Add comments. http://codereview.appspot.com/627041/diff/6001/7001#newcode2120 gtfsscheduleviewer/files/transit_editor.js:2120: for (var j = 0; j < patternDeleteList.length; j++) { Can you write a helper function, like deleteFromArray, for deleting an element from an array? http://codereview.appspot.com/627041/diff/6001/7001#newcode2492 gtfsscheduleviewer/files/transit_editor.js:2492: Shape.prototype.DeleteStop = function(stop) { Member function should start with an lower-case letter. s/DeleteStop/deleteStop http://codereview.appspot.com/627041/diff/6001/7001#newcode3328 gtfsscheduleviewer/files/transit_editor.js:3328: if(confirm('Sure to Delete stop? It is not revertable.')) { Space between if and ( http://codereview.appspot.com/627041/diff/6001/7001#newcode3801 gtfsscheduleviewer/files/transit_editor.js:3801: Delete the blank line.
Sign in to reply to this message.
On Fri, Mar 19, 2010 at 12:00 PM, <baiming@google.com> wrote: > Wenxin, > > As we are supporting the stop deletion, did you carefully consider the > garbage collection problem? Will the memory of deleted objects be > properly collected? Sorry, s/collected/released > > > http://codereview.appspot.com/627041/diff/6001/7001 > File gtfsscheduleviewer/files/transit_editor.js (right): > > http://codereview.appspot.com/627041/diff/6001/7001#newcode1673 > gtfsscheduleviewer/files/transit_editor.js:1673: * @param {Stop} instop > Stop to be determined > instop is not a good parameter name. It is a little misleading. > I think "stop" is enough. > > http://codereview.appspot.com/627041/diff/6001/7001#newcode2083 > gtfsscheduleviewer/files/transit_editor.js:2083: * @param {Boolean} > isSet Set stoptime tag or not > isSet doesn't tell what is to set. > And what does stoptime tag mean? > > Please rephrase the description to make it clearer. > > http://codereview.appspot.com/627041/diff/6001/7001#newcode2085 > gtfsscheduleviewer/files/transit_editor.js:2085: > Trip.prototype.onDeleteStop = function(stop, isSet) { > It isn't a handler, is it? > Use verbal function name, such as "deleteStop". > > http://codereview.appspot.com/627041/diff/6001/7001#newcode2101 > gtfsscheduleviewer/files/transit_editor.js:2101: > fromLeg.getGDirections(); > You also need to set this.stops[i + 1].fromLeg[shape.id] = null. > > http://codereview.appspot.com/627041/diff/6001/7001#newcode2117 > gtfsscheduleviewer/files/transit_editor.js:2117: > Trip.prototype.deleteStoptime = function(stoptime) { > Add comments. > > http://codereview.appspot.com/627041/diff/6001/7001#newcode2120 > gtfsscheduleviewer/files/transit_editor.js:2120: for (var j = 0; j < > patternDeleteList.length; j++) { > Can you write a helper function, like deleteFromArray, for deleting an > element from an array? > > http://codereview.appspot.com/627041/diff/6001/7001#newcode2492 > gtfsscheduleviewer/files/transit_editor.js:2492: > Shape.prototype.DeleteStop = function(stop) { > Member function should start with an lower-case letter. > s/DeleteStop/deleteStop > > http://codereview.appspot.com/627041/diff/6001/7001#newcode3328 > gtfsscheduleviewer/files/transit_editor.js:3328: if(confirm('Sure to > Delete stop? It is not revertable.')) { > Space between if and ( > > http://codereview.appspot.com/627041/diff/6001/7001#newcode3801 > gtfsscheduleviewer/files/transit_editor.js:3801: > Delete the blank line. > > http://codereview.appspot.com/627041/show > -- Ming Bai 白明 Software Engineer Google Inc. Tel(Office): 86 (10) 6250-3361 Tel(Cell): +86-159-0153-4908 Email: baiming@google.com
Sign in to reply to this message.
fixed a bug on remove mid stops. http://codereview.appspot.com/627041/diff/6001/7001 File gtfsscheduleviewer/files/transit_editor.js (right): http://codereview.appspot.com/627041/diff/6001/7001#newcode1673 gtfsscheduleviewer/files/transit_editor.js:1673: * @param {Stop} instop Stop to be determined On 2010/03/19 04:00:23, baiming wrote: > instop is not a good parameter name. It is a little misleading. > I think "stop" is enough. Done. http://codereview.appspot.com/627041/diff/6001/7001#newcode2083 gtfsscheduleviewer/files/transit_editor.js:2083: * @param {Boolean} isSet Set stoptime tag or not On 2010/03/19 04:00:23, baiming wrote: > isSet doesn't tell what is to set. > And what does stoptime tag mean? > > Please rephrase the description to make it clearer. Done. http://codereview.appspot.com/627041/diff/6001/7001#newcode2085 gtfsscheduleviewer/files/transit_editor.js:2085: Trip.prototype.onDeleteStop = function(stop, isSet) { On 2010/03/19 04:00:23, baiming wrote: > It isn't a handler, is it? > Use verbal function name, such as "deleteStop". Yes, it is. http://codereview.appspot.com/627041/diff/6001/7001#newcode2101 gtfsscheduleviewer/files/transit_editor.js:2101: fromLeg.getGDirections(); On 2010/03/19 04:00:23, baiming wrote: > You also need to set this.stops[i + 1].fromLeg[shape.id] = null. Done. http://codereview.appspot.com/627041/diff/6001/7001#newcode2117 gtfsscheduleviewer/files/transit_editor.js:2117: Trip.prototype.deleteStoptime = function(stoptime) { On 2010/03/19 04:00:23, baiming wrote: > Add comments. Done. http://codereview.appspot.com/627041/diff/6001/7001#newcode2120 gtfsscheduleviewer/files/transit_editor.js:2120: for (var j = 0; j < patternDeleteList.length; j++) { On 2010/03/19 04:00:23, baiming wrote: > Can you write a helper function, like deleteFromArray, for deleting an element > from an array? Done. http://codereview.appspot.com/627041/diff/6001/7001#newcode2492 gtfsscheduleviewer/files/transit_editor.js:2492: Shape.prototype.DeleteStop = function(stop) { On 2010/03/19 04:00:23, baiming wrote: > Member function should start with an lower-case letter. > s/DeleteStop/deleteStop seems of no use right now. removed. http://codereview.appspot.com/627041/diff/6001/7001#newcode3328 gtfsscheduleviewer/files/transit_editor.js:3328: if(confirm('Sure to Delete stop? It is not revertable.')) { On 2010/03/19 04:00:23, baiming wrote: > Space between if and ( Done. http://codereview.appspot.com/627041/diff/6001/7001#newcode3801 gtfsscheduleviewer/files/transit_editor.js:3801: On 2010/03/19 04:00:23, baiming wrote: > Delete the blank line. Done.
Sign in to reply to this message.
http://codereview.appspot.com/627041/diff/6001/7001 File gtfsscheduleviewer/files/transit_editor.js (right): http://codereview.appspot.com/627041/diff/6001/7001#newcode2085 gtfsscheduleviewer/files/transit_editor.js:2085: Trip.prototype.onDeleteStop = function(stop, isSet) { On 2010/03/19 07:39:40, calidion wrote: > On 2010/03/19 04:00:23, baiming wrote: > > It isn't a handler, is it? > > Use verbal function name, such as "deleteStop". > > Yes, it is. > > I don't think so. Is "deleteStop" an event and "onDeleteStop" the handler of that event? Actually, the real event is "click on the delete node", and handler is "onDeleteNodeClick". And in the handler, the trip does the deletion by calling this function.
Sign in to reply to this message.
Function onDeleteNodeClick is a dom event handler, while onDeleteStop is a real gtfs stop deleting handler. they are handlers of different types. though onDeleteStop is not a direct handler, it is the handler for deleting stop when the deleteNode is clicked and permission is confirmed by the user. 2010/3/19 <baiming@google.com> > > http://codereview.appspot.com/627041/diff/6001/7001 > File gtfsscheduleviewer/files/transit_editor.js (right): > > http://codereview.appspot.com/627041/diff/6001/7001#newcode2085 > gtfsscheduleviewer/files/transit_editor.js:2085: > Trip.prototype.onDeleteStop = function(stop, isSet) { > On 2010/03/19 07:39:40, calidion wrote: > >> On 2010/03/19 04:00:23, baiming wrote: >> > It isn't a handler, is it? >> > Use verbal function name, such as "deleteStop". >> > > Yes, it is. >> > > > > I don't think so. Is "deleteStop" an event and "onDeleteStop" the > handler of that event? > > Actually, the real event is "click on the delete node", and handler is > "onDeleteNodeClick". And in the handler, the trip does the deletion by > calling this function. > > > http://codereview.appspot.com/627041/show >
Sign in to reply to this message.
2010/3/19 李白,字一日 <calidion@gmail.com> > Function onDeleteNodeClick is a dom event handler, > while onDeleteStop is a real gtfs stop deleting handler. > they are handlers of different types. > Please think about: Who fires the GTFS stop deleting event? Who listens that event? In onDeleteNodeClick, the stop directly calls Trip.current to do deletion. No event here, right? If you really want to make it pure event-driven, trigger a "delete" event in onDeleteNodeClick and let Trip.current listen to stop's "delete" event. > though onDeleteStop is not a direct handler, it is the handler for deleting > stop when the deleteNode is clicked and permission is confirmed by the user. > > > 2010/3/19 <baiming@google.com> > > >> http://codereview.appspot.com/627041/diff/6001/7001 >> File gtfsscheduleviewer/files/transit_editor.js (right): >> >> http://codereview.appspot.com/627041/diff/6001/7001#newcode2085 >> gtfsscheduleviewer/files/transit_editor.js:2085: >> Trip.prototype.onDeleteStop = function(stop, isSet) { >> On 2010/03/19 07:39:40, calidion wrote: >> >>> On 2010/03/19 04:00:23, baiming wrote: >>> > It isn't a handler, is it? >>> > Use verbal function name, such as "deleteStop". >>> >> >> Yes, it is. >>> >> >> >> >> I don't think so. Is "deleteStop" an event and "onDeleteStop" the >> handler of that event? >> >> Actually, the real event is "click on the delete node", and handler is >> "onDeleteNodeClick". And in the handler, the trip does the deletion by >> calling this function. >> >> >> http://codereview.appspot.com/627041/show >> > > -- Ming Bai 白明 Software Engineer Google Inc. Tel(Office): 86 (10) 6250-3361 Tel(Cell): +86-159-0153-4908 Email: baiming@google.com
Sign in to reply to this message.
Firstly, before deleting the stop, we need a confirm from the user. Secondly, we can not bind the trip to stop previously to handle the click event of the deleting node. for the stop is shared with all the trips, and that is why the Trip.current is stand here for handling the action. so onDeleteStop is the real event handler of trip. while the onDeleteNodeClick is a bridge to bind the stop event to current trip, and give a confirmation to the end user to make sure he/she really wants to do it. 在 2010年3月19日 下午6:10,Ming Bai 白明 <baiming@google.com>写道: > > > 2010/3/19 李白,字一日 <calidion@gmail.com> > > Function onDeleteNodeClick is a dom event handler, >> while onDeleteStop is a real gtfs stop deleting handler. >> they are handlers of different types. >> > > Please think about: > Who fires the GTFS stop deleting event? > Who listens that event? > > In onDeleteNodeClick, the stop directly calls Trip.current to do deletion. > No event here, right? > > If you really want to make it pure event-driven, trigger a "delete" event > in onDeleteNodeClick and let Trip.current listen to stop's "delete" event. > > >> though onDeleteStop is not a direct handler, it is the handler for >> deleting stop when the deleteNode is clicked and permission is confirmed by >> the user. >> >> >> 2010/3/19 <baiming@google.com> >> >> >>> http://codereview.appspot.com/627041/diff/6001/7001 >>> File gtfsscheduleviewer/files/transit_editor.js (right): >>> >>> http://codereview.appspot.com/627041/diff/6001/7001#newcode2085 >>> gtfsscheduleviewer/files/transit_editor.js:2085: >>> Trip.prototype.onDeleteStop = function(stop, isSet) { >>> On 2010/03/19 07:39:40, calidion wrote: >>> >>>> On 2010/03/19 04:00:23, baiming wrote: >>>> > It isn't a handler, is it? >>>> > Use verbal function name, such as "deleteStop". >>>> >>> >>> Yes, it is. >>>> >>> >>> >>> >>> I don't think so. Is "deleteStop" an event and "onDeleteStop" the >>> handler of that event? >>> >>> Actually, the real event is "click on the delete node", and handler is >>> "onDeleteNodeClick". And in the handler, the trip does the deletion by >>> calling this function. >>> >>> >>> http://codereview.appspot.com/627041/show >>> >> >> > > > -- > Ming Bai 白明 > Software Engineer > Google Inc. > Tel(Office): 86 (10) 6250-3361 > Tel(Cell): +86-159-0153-4908 > Email: baiming@google.com >
Sign in to reply to this message.
well, check it in if you insist on the point. 2010/3/19 李白,字一日 <calidion@gmail.com> > Firstly, before deleting the stop, we need a confirm from the user. > Secondly, we can not bind the trip to stop previously to handle the click > event of the deleting node. > for the stop is shared with all the trips, and that is why the Trip.current > is stand here for handling the action. > so onDeleteStop is the real event handler of trip. while the > onDeleteNodeClick is a bridge to bind the stop event to current trip, and > give a confirmation to the end user to make sure he/she really wants to do > it. > > > 在 2010年3月19日 下午6:10,Ming Bai 白明 <baiming@google.com>写道: > > >> >> 2010/3/19 李白,字一日 <calidion@gmail.com> >> >> Function onDeleteNodeClick is a dom event handler, >>> while onDeleteStop is a real gtfs stop deleting handler. >>> they are handlers of different types. >>> >> >> Please think about: >> Who fires the GTFS stop deleting event? >> Who listens that event? >> >> In onDeleteNodeClick, the stop directly calls Trip.current to do deletion. >> No event here, right? >> >> If you really want to make it pure event-driven, trigger a "delete" event >> in onDeleteNodeClick and let Trip.current listen to stop's "delete" event. >> >> >>> though onDeleteStop is not a direct handler, it is the handler for >>> deleting stop when the deleteNode is clicked and permission is confirmed by >>> the user. >>> >>> >>> 2010/3/19 <baiming@google.com> >>> >>> >>>> http://codereview.appspot.com/627041/diff/6001/7001 >>>> File gtfsscheduleviewer/files/transit_editor.js (right): >>>> >>>> http://codereview.appspot.com/627041/diff/6001/7001#newcode2085 >>>> gtfsscheduleviewer/files/transit_editor.js:2085: >>>> Trip.prototype.onDeleteStop = function(stop, isSet) { >>>> On 2010/03/19 07:39:40, calidion wrote: >>>> >>>>> On 2010/03/19 04:00:23, baiming wrote: >>>>> > It isn't a handler, is it? >>>>> > Use verbal function name, such as "deleteStop". >>>>> >>>> >>>> Yes, it is. >>>>> >>>> >>>> >>>> >>>> I don't think so. Is "deleteStop" an event and "onDeleteStop" the >>>> handler of that event? >>>> >>>> Actually, the real event is "click on the delete node", and handler is >>>> "onDeleteNodeClick". And in the handler, the trip does the deletion by >>>> calling this function. >>>> >>>> >>>> http://codereview.appspot.com/627041/show >>>> >>> >>> >> >> >> -- >> Ming Bai 白明 >> Software Engineer >> Google Inc. >> Tel(Office): 86 (10) 6250-3361 >> Tel(Cell): +86-159-0153-4908 >> Email: baiming@google.com >> > > -- Ming Bai 白明 Software Engineer Google Inc. Tel(Office): 86 (10) 6250-3361 Tel(Cell): +86-159-0153-4908 Email: baiming@google.com
Sign in to reply to this message.
LGTM 2010/3/21 Ming Bai 白明 <baiming@google.com>: > well, check it in if you insist on the point. > 2010/3/19 李白,字一日 <calidion@gmail.com> >> >> Firstly, before deleting the stop, we need a confirm from the user. >> Secondly, we can not bind the trip to stop previously to handle the click >> event of the deleting node. >> for the stop is shared with all the trips, and that is why the >> Trip.current is stand here for handling the action. >> so onDeleteStop is the real event handler of trip. while the >> onDeleteNodeClick is a bridge to bind the stop event to current trip, and >> give a confirmation to the end user to make sure he/she really wants to do >> it. >> >> 在 2010年3月19日 下午6:10,Ming Bai 白明 <baiming@google.com>写道: >>> >>> >>> 2010/3/19 李白,字一日 <calidion@gmail.com> >>>> >>>> Function onDeleteNodeClick is a dom event handler, >>>> while onDeleteStop is a real gtfs stop deleting handler. >>>> they are handlers of different types. >>> >>> Please think about: >>> Who fires the GTFS stop deleting event? >>> Who listens that event? >>> In onDeleteNodeClick, the stop directly calls Trip.current to do >>> deletion. No event here, right? >>> If you really want to make it pure event-driven, trigger a "delete" >>> event in onDeleteNodeClick and let Trip.current listen to stop's "delete" >>> event. >>> >>>> >>>> though onDeleteStop is not a direct handler, it is the handler for >>>> deleting stop when the deleteNode is clicked and permission is confirmed by >>>> the user. >>>> >>>> 2010/3/19 <baiming@google.com> >>>>> >>>>> http://codereview.appspot.com/627041/diff/6001/7001 >>>>> File gtfsscheduleviewer/files/transit_editor.js (right): >>>>> >>>>> http://codereview.appspot.com/627041/diff/6001/7001#newcode2085 >>>>> gtfsscheduleviewer/files/transit_editor.js:2085: >>>>> Trip.prototype.onDeleteStop = function(stop, isSet) { >>>>> On 2010/03/19 07:39:40, calidion wrote: >>>>>> >>>>>> On 2010/03/19 04:00:23, baiming wrote: >>>>>> > It isn't a handler, is it? >>>>>> > Use verbal function name, such as "deleteStop". >>>>> >>>>>> Yes, it is. >>>>> >>>>> >>>>> >>>>> I don't think so. Is "deleteStop" an event and "onDeleteStop" the >>>>> handler of that event? >>>>> >>>>> Actually, the real event is "click on the delete node", and handler is >>>>> "onDeleteNodeClick". And in the handler, the trip does the deletion by >>>>> calling this function. >>>>> >>>>> http://codereview.appspot.com/627041/show >>>> >>> >>> >>> >>> -- >>> Ming Bai 白明 >>> Software Engineer >>> Google Inc. >>> Tel(Office): 86 (10) 6250-3361 >>> Tel(Cell): +86-159-0153-4908 >>> Email: baiming@google.com >> > > > > -- > Ming Bai 白明 > Software Engineer > Google Inc. > Tel(Office): 86 (10) 6250-3361 > Tel(Cell): +86-159-0153-4908 > Email: baiming@google.com > -- Ming Bai 白明 Software Engineer Google Inc. Tel(Office): 86 (10) 6250-3361 Tel(Cell): +86-159-0153-4908 Email: baiming@google.com
Sign in to reply to this message.
Ping? Seems you forgot updating the following... Please submit after you fix them. On Fri, Mar 19, 2010 at 10:28 AM, <weiliu@google.com> wrote: > > http://codereview.appspot.com/627041/diff/6001/7002 > > File transitfeed_editor.py (right): > > http://codereview.appspot.com/627041/diff/6001/7002#newcode528 > transitfeed_editor.py:528: def DeletePattern(self, patternId, sequence, > stopId, schedule): > Rename it to "DeleteStopTimeFromPattern" > > http://codereview.appspot.com/627041/diff/6001/7002#newcode535 > transitfeed_editor.py:535: db.DeleteTripStoptime(sequence, stopId, > tripIds) > Rename it to "DeleteStopTimeFromTrip" > > > http://codereview.appspot.com/627041/show > -- Best Regards, Wei Liu 86-10-62503256(o)
Sign in to reply to this message.
updated. http://codereview.appspot.com/627041/diff/6001/7002 File transitfeed_editor.py (right): http://codereview.appspot.com/627041/diff/6001/7002#newcode528 transitfeed_editor.py:528: def DeletePattern(self, patternId, sequence, stopId, schedule): On 2010/03/19 02:28:11, weiliu wrote: > Rename it to "DeleteStopTimeFromPattern" Done. http://codereview.appspot.com/627041/diff/6001/7002#newcode535 transitfeed_editor.py:535: db.DeleteTripStoptime(sequence, stopId, tripIds) On 2010/03/19 02:28:11, weiliu wrote: > Rename it to "DeleteStopTimeFromTrip" Done.
Sign in to reply to this message.
LGTM On Mon, Mar 22, 2010 at 10:45 AM, <calidion@gmail.com> wrote: > updated. > > > > http://codereview.appspot.com/627041/diff/6001/7002 > File transitfeed_editor.py (right): > > http://codereview.appspot.com/627041/diff/6001/7002#newcode528 > transitfeed_editor.py:528: def DeletePattern(self, patternId, sequence, > stopId, schedule): > On 2010/03/19 02:28:11, weiliu wrote: > >> Rename it to "DeleteStopTimeFromPattern" >> > > Done. > > > http://codereview.appspot.com/627041/diff/6001/7002#newcode535 > transitfeed_editor.py:535: db.DeleteTripStoptime(sequence, stopId, > tripIds) > On 2010/03/19 02:28:11, weiliu wrote: > >> Rename it to "DeleteStopTimeFromTrip" >> > > Done. > > > http://codereview.appspot.com/627041/show > -- Best Regards, Wei Liu 86-10-62503256(o)
Sign in to reply to this message.
update to rev 59 2010/3/22 Wei Liu <weiliu@google.com> > LGTM > > > On Mon, Mar 22, 2010 at 10:45 AM, <calidion@gmail.com> wrote: > >> updated. >> >> >> >> http://codereview.appspot.com/627041/diff/6001/7002 >> File transitfeed_editor.py (right): >> >> http://codereview.appspot.com/627041/diff/6001/7002#newcode528 >> transitfeed_editor.py:528: def DeletePattern(self, patternId, sequence, >> stopId, schedule): >> On 2010/03/19 02:28:11, weiliu wrote: >> >>> Rename it to "DeleteStopTimeFromPattern" >>> >> >> Done. >> >> >> http://codereview.appspot.com/627041/diff/6001/7002#newcode535 >> transitfeed_editor.py:535: db.DeleteTripStoptime(sequence, stopId, >> tripIds) >> On 2010/03/19 02:28:11, weiliu wrote: >> >>> Rename it to "DeleteStopTimeFromTrip" >>> >> >> Done. >> >> >> http://codereview.appspot.com/627041/show >> > > > > -- > Best Regards, > Wei Liu > 86-10-62503256(o) >
Sign in to reply to this message.
|