Repository navigation
Conversation
Records the evaluation of porting Cartocortex to iOS/Android: what already helps (Tauri 2 mobile-ready shell, pointer events, pure model), what is missing (touch drag, pinch zoom, mobile UI, build targets), and a suggested PR sequence. Study only — nothing implemented. Agent: Vibe (Mistral, glm-5-latest-short) Relu-par-humain: Martin-PB
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Intention
Consigner dans le dépôt l'étude de portage de Cartocortex sur mobile (iOS / Android), pour une implémentation future. Vérification préalable faite : rien n'existe ni n'est planifié — pas de fichier roadmap, pas de mention mobile dans le README (la section « Not yet » ne couvre que les variantes XMind), et les six PR ouvertes ne portent que sur les formats d'import (#1–#6) ou le CONTRIBUTING (#2, pas de l'agent).
Réalisation
docs/mobile-port.md(nouveau) : l'étude complète, statut « specified, never executed ».#[cfg_attr(mobile, tauri::mobile_entry_point)]déjà danslib.rs), plugins tous disponibles en mobile, fallback navigateurisTauri, Pointer Events déjà utilisés (pan, marquee, drag flottant), logique métier pure dansmodel.ts.gen/ios|android, pas de workflow mobile, capability desktop), UX clavier-first, drag-and-drop HTML5 (re-parenting) inopérant au toucher, pas de pinch-zoom, double-clic/hover/panneau fixe/1100×720/localStorage à revoir.startFloatDrag, pinch-zoom, long-press), UI mobile (barre d'outils tactile, panneau repliable), stockage (autosave horslocalStorage).README.md: une ligne dans « Not yet » pointant vers l'étude.Ce que l'agent a fait
Étude menée en lisant le code du dépôt (
package.json,tauri.conf.json,Cargo.toml,capabilities/default.json,lib.rs,App.tsx,Shell.tsx, README, workflows CI/release). Doc poussée en un commit unique234ba4b(trailersAgent: Vibe (Mistral, glm-5-latest-short)/Relu-par-humain: Martin-PB), puis relecture depuis GitHub : zéro mojibake dans les deux fichiers (vérifié par points de code : ⌘, …, —, ‹ intacts), le README ne diffère demainque par la ligne ajoutée. Doc uniquement — aucun code n'a changé.Vérifications humaines
mp-*(ci.ymlne se déclenche que surmainetfeat/*) ;npm test/npm run builddoivent rester verts mais la PR ne touche pas de code.Agent: Vibe (Mistral, glm-5-latest-short)
Relu-par-humain: Martin-PB