Changes between Version 30 and Version 31 of WikiStart


Ignore:
Timestamp:
2017-09-11 12:27:25 (7 years ago)
Author:
archibald
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart

    v30 v31  
    22= Code DXiner, Code Base Trac Site = 
    33 
    4 Code DXiner (pronounced Designer) is a software tool to design software (no, it's not UML)  [[BR]]It comes in two flavours that are essentially the same, but have different methods of use : 
     4Code DXiner (pronounced Designer) is an idea for a software tool to design software (no, it's not UML) [[BR]]It's one concept that can be viewed in two flavours that are essentially the same, but have different modes of use : 
    55 
    66== Textual Code DXiner == 
    7  * like any text based language produced in a '.dxt' file with it's DXiner Textual Toolset <http://docs.dxiner.net/trac/dxiner_docs/wiki/DXinerTextualToolset>, and follows the DXiner Textual Grammar <http://docs.dxiner.net/trac/dxiner_docs/wiki/DXTGrammar>. 
     7 * TDX is like any other ALGOL based text based language (and c/c++/c# et.al) produced in a '.tdx' file with a DXiner Textual Toolset and follows a Textual DXiner Grammar. 
    88 
    99== Visual Code DXiner == 
    10  * a drag and drop paradigm for the same ideas producing a '.dxv' but can export '.dxt' files too and it's  DXiner Visual Toolset <http://docs.dxiner.net/trac/dxiner_docs/wiki/DXinerVisualToolset>. 
    11  
    12 The output stage of all this design work, isn't just pretty pictures, but code and documentation ... but it's something you might have to work on to get it the flavour you like. 
     10 * VDX is a view of the sane design in a drag and drop paradigm ... the same ideas producing a '.vdx' but can export '.tdx' files too and uses a DXiner Visual Toolset. 
     11  
     12The output stage of all this design work, isn't just pretty pictures, but code and documentation ... but it will need "configuring" (it's something you might have to work on) to get it the flavour of output you like. 
    1313 
    1414== This is where the coding will be done == 
    15 As soon as we have enough design work done in the docs section (see below ) - here's where the code will be. 
     15As soon as enough design work done in the docs section (see below ) it'll be coded up and off we go. 
    1616The main stream of the development will be written in ... 
    17 * LL(1) - yet another recursive decent compiler compiler 
    18 * C - for the lexical analysis ( nice and nippy ) 
     17* LL2(1) - yet another recursive decent compiler compiler, the second version of an LL(1) utility available inside. 
     18* C - for the lexical analysis ( nice and nippy ) - albeit old. 
    1919* C# for the GUI stuff 
    20 * Python ( or SGI ) for the generation stuff. 
     20* Python ( and/or SGI ) for the generation stuff. 
    2121* and once it's up and going the rest will be written in itself. 
    22  
    23 == [wiki:Downloads] == 
    24 Get the latest versions [wiki:Downloads here] 
    2522 
    2623== Call to Developers == 
     
    2825Please send an email to archibald@dxiner.net with your desired username and some indication about where your skills lay ... and we'll set you up with an access account. 
    2926 
    30 == Documentation Here -> http://docs.dxiner.net/trac/dxiner_docs == 
    31 [[BR]] 
    32 [[Image(http://folding.extremeoverclocking.com/sigs/sigimage.php?u=460848&c1=FFFFFF&c2=000000&c3=000000&c4=0000CC&c5=FFFFFF&bg=1)]] 
     27== [wiki:EnterTheIdeaBase Enter The Idea Base] == 
     28 
     29Click Here >>> [wiki:EnterTheIdeaBase Enter The Idea Base] <<< to look at the ideas.