Eric M.

My feedback

  1. 5 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
    Eric M. supported this idea  · 
    Eric M. commented  · 

    agree

    Actually, table is not a part of standard markdown syntax. It's a part of Github-Flavored Markdown syntax.
    Please support GitHub Flavored Markdown (GFM) ignores underscores in words, and adds syntax highlighting, task lists, and tables.

  2. 1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
    Eric M. commented  · 

    agree, copy paste inside Flowchart Diagrams does not work

  3. 7 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
    Eric M. supported this idea  · 
    Eric M. commented  · 

    fully agree about the need ofr generation of C code from UML.
    Especially from the Flow Charts because it allows to generate function body as C-like pseudo code.
    In a first step it already is very useful if you only provide partial support with only

    - Flow Chart -> Pseudo code for one C-function:
    - decision points (FCDecision) -> if then else...
    - process (FCProcess) -> sub function calls
    - linked notes (grab from views) -> comments

    For me Pseudo code (C-like) generation from flowchart is higher priority than reverse engineering.

Feedback and Knowledge Base