Menu

#4 support more file formats

open
5
2003-10-24
2003-10-05
No

Would you like to support the VHSIC hardware description
language?
http://tutorgig.com/encyclopedia/getdefn.jsp?query=VHDL

Discussion

  • Markus Elfring

    Markus Elfring - 2003-10-06
    • summary: support VHDL --> support more file formats
     
  • Markus Elfring

    Markus Elfring - 2003-10-06

    Logged In: YES
    user_id=572001

    How do you think to cooperate with the file formats that are
    listed on the
    page "http://dgc.sourceforge.net/dgcprogs_1.html#SEC1"?

     
  • Pavel Bekkerman

    Pavel Bekkerman - 2003-10-17

    Logged In: YES
    user_id=595910

    UFF ! Your features acually surprised me, because I was sure
    I already enlisted most of them. But it took me some time to
    realize it's all in the TODO file!

    ---------TODO---------
    This file contains the list of major features we're working on.
    They will be introduced to the
    FSMGenerator in the near future. Anyone, wishing to
    contribute to development of the enlisted items
    or suggest new ones is warmly invited to contact the project
    team.

    - Generators for additional languages.
    PHP, C#, VB are our next majors. The rest are according to
    the demand.

    - API static and dynamic libraries.
    We currently provide API for supported languages - C, C++,
    Java.
    We wish to distribute, along with the code of the API, the
    static/dynamic libraries.
    For all platforms, for all languages.

    - Run-Time generated FSM.
    We currently generate FSM source code, which should be
    compiled with the user's software (together
    with the API) in order that FSM would be accessible and
    executable from the user's software.
    We wish to generate also a "FSM database", a snapshot of
    the internal DB. User's software, now,
    souldn't have to compile with the generated FSM code, but
    with API only (or linked with API libraries)
    and the FSM definitions are taken from the generated "FSM
    DB" in the run-time.
    Here also there're 2 possibilities: either to recreate
    (deserialize) internal DB from file OR to open the
    file and look-up in it every time needed.

    - Alternative FSM configuration format.
    We currently have our own .fsm format.
    We wish to support other formats - existing or developed by
    us. XML is the right direction.

    - GUI for FSMGenerator.
    Right now fsmgenerator is the command-line software tool.
    Someday we'll provide some neat GUI for the FSMGenerator.

    - Graphical FSM manipulation.
    Someday we'll either provide ours OR inteface vendor's
    software for FSM graphical manipulation.
    This should have the ability to add and manipulate states,
    events, transitions. At the same time it
    should support our CALLBACKS and HOOKS! It should alos be
    able to store and retrieve FSM definition in
    onei or all of the FSMGenerator supported formats.

    - Formal FSM manipulation.
    Someday we'll introduce tools for formally manipulating FSMs
    defined in our formats.
    The examples for that are: merging machines, chaining
    machines, parallelizing machines, etc...

     
  • Markus Elfring

    Markus Elfring - 2003-10-24
    • assigned_to: nobody --> where_
     
  • Markus Elfring

    Markus Elfring - 2003-10-24

    Logged In: YES
    user_id=572001

    Are you going to publish this file?
    Will a link to it be added on the
    page "http://fsmgenerator.sourceforge.net/"?

     

Log in to post a comment.

MongoDB Logo MongoDB