Lg Code Converter

2. Python → Dart (Data Processing Scripts)

Convert Python data pipelines (API fetch → transform → KML) to Dart:

3. Kotlin/Swift → Dart (Native Mobile to Flutter)

Convert existing native LG controller apps to cross-platform Flutter:

Conversion Process

Step 1: Analyze Source Code

1. Identify the code's purpose in the LG context (SSH command? KML generation? API fetch?).
2. Map source patterns to Dart equivalents.
3. Identify LG-specific logic (coordinate handling, KML XML, SSH commands).

Step 2: Convert with Architecture Alignment

1. Place converted code in the correct Flutter file:
   • Network/SSH logic → services/
   • KML generation → services/kml_service.dart or a converter in utils/
   • Data models → models/
   • UI logic → screens/ or widgets/
2. Apply Dart conventions: /// doc comments, final fields, typed collections.
3. Use Provider for state instead of global variables.

Step 3: Verify

1. flutter analyze — zero errors.
2. flutter test — write a test for the converted logic.
3. Compare output of original and converted code with identical inputs.

Example: Convert JS KML Generator to Dart

JavaScript (original):

function generateFlyTo(lat, lon, alt, heading, tilt, range) {
  return `<gx:FlyTo>
    <gx:duration>3</gx:duration>
    <LookAt>
      <longitude>${lon}</longitude>
      <latitude>${lat}</latitude>
      <altitude>${alt}</altitude>
      <heading>${heading}</heading>
      <tilt>${tilt}</tilt>
      <range>${range}</range>
    </LookAt>
  </gx:FlyTo>`;
}

Dart (converted):

/// Generates a KML FlyTo element for Google Earth camera navigation.
///
/// Note: KML uses longitude,latitude order internally, but this
/// method accepts latitude,longitude (the intuitive order).
String generateFlyTo({
  required double latitude,
  required double longitude,
  double altitude = 0,
  double heading = 0,
  double tilt = 60,
  double range = 15000,
  double duration = 3.0,
}) {
  return '''<gx:FlyTo>
  <gx:duration>$duration</gx:duration>
  <LookAt>
    <longitude>$longitude</longitude>
    <latitude>$latitude</latitude>
    <altitude>$altitude</altitude>
    <heading>$heading</heading>
    <tilt>$tilt</tilt>
    <range>$range</range>
  </LookAt>
</gx:FlyTo>''';
}

⛔ Student Interaction Checkpoints

After Conversion — Understanding Check

Before applying any converted code, STOP and engage the student:

⛔ STOP and WAIT — Ask:

"Before I apply this conversion, can you explain what the original code does? What will change in the Dart version?"

Wait for the student's answer. Evaluate:

• ✅ Correct: Acknowledge, then proceed with the conversion.
• ⚠️ Partially correct: Guide them — highlight the key pattern change (e.g., Promise → Future, EventEmitter → ChangeNotifier).
• ❌ Wrong or "I don't know": Walk through the original code line by line. Link to lg-learning-resources (.agent/skills/lg-learning-resources/SKILL.md).

After Applying — Trace Exercise

⛔ STOP and WAIT — Ask:

"Trace the data flow in this converted Dart code. Where does the input come in, how is it transformed, and where does the output go?"

Do NOT proceed to verification until the student can trace the flow.

Pattern Comparison

Present the original and converted code side-by-side, then ask:

"What are the 2-3 biggest differences between the original and the Dart version? Which Dart feature improves on the original?"

⛔ STOP and WAIT for the student's answer before moving on.

Handoff

After conversion → lg-code-reviewer for quality review.

🔗 Skill Chain

After the conversion is applied and the student can explain the Dart version, automatically offer the next stage:

"Conversion complete! You clearly understand the Dart patterns now. Let's run a code review to make sure the converted code meets LG quality standards. Ready for the Code Review? 🔍"

If student says "ready" → activate .agent/skills/lg-code-reviewer/SKILL.md.