Paste number 54932: CDAN proposals

Index of paste annotations: 1 | 2 | 3 | 4

Paste number 54932: CDAN proposals
Pasted by: pet-ro
5 months, 3 weeks ago
#dylan | Context in IRC logs
Paste contents:
Raw Source | XML | Display As
This paste  is titled CDAN proposals:
                  CDAN proposals
This new paste is published to the #dylan channel only
and is listed on
    http://paste.lisp.org/list/dylan
via the title
    CDAN proposals  
This paste will be the information board for discussinng CDAN proposals.

Please add your proposal and comment as an annotation to this paste.
The web frontend paste.lisp.org allows you to choose a new title for
any annotation. To annotate select the paste number which related to
this paste or annotate to a paste on the #dylan channel directly.

Sending only annotations to this paste and by not creating new pastes
related to topic "CDAN proposals" avoids that related information is
spread around.
Try to feel comfortable with this information board, even if
you do not feel during your first tries. I believe you will
feel comfortable as soon as you are interested to find what is
already published related to the topic "CDAN proposals".
Then you either can go to
              http://paste.lisp.org/list/dylan
and find the related entry via title or paste number
Or you can use a paste to the #dylan channel to see what is
already published.

A specific CDAN related proposal will come as soon as annotation.

Annotations for this paste:

Annotation number 1: proposing CDAN node: w3-related
Pasted by: pet-ro
5 months, 3 weeks ago
Context in IRC logs
Paste contents:
Raw Source | Display As
w3-related   -- node
w3-related/readme
             The "w3-related" node will be part of the CDAN
             (Comprehensive Dylan Archive Network)
             
             While it is a node of CDAN this does not require
             that the node is a repository. So we discuss here
             currently only the structure of the CDAN, not how
             the structure is mapped to repositories
w3-related/xml   -- node
w3-related/xml/readme
             xml is a subnode of the "w3-related" node.
             Here we list all the activities of the Open Dylan
             Community which are related to the xml-activities
             of the w3 organisation (www.w3.org)
w3-related/xml/native-parser -- node
w3-related/xml/native-parser/readme
             native-parser is a subnode of the "w3-related/xml"
             node.
             Here we list all native dylan implementation of
             xml parsers.
             Currently all implementations are listed in the
             "w3-related/xml/native-parser" node are in the
             subnode "based-on-parser"                    
w3-related/xml/native-parser/base-on-parser
w3-related/xml/native-parser/base-on-parser/readme
             Each subnode of
                "w3-related/xml/native-parser/base-on-parser"
             entitles the parser library which is used by the
             xml-parser.
w3-related/xml/native-parser/base-on-parser/meta -- node
w3-related/xml/native-parser/base-on-parser/meta/readme
             This node is the source location for the xml-parser
             which is based on the Meta parser
             
w3-related/xml/no-native-parser -- node
w3-related/xml/no-native-parser/readme
              A no-native parser is based on a not natively in Dylan
              written parser. This could be a C-parser (e.g expat,
              or a COM-component (e.g. Microsoft Core XML Services
              (MSXML) ). How interfacing with foreign format (C, COM)
              is currently depends on the Dylan implementation.
              A general solution related to C is via a project by
              Peter Housel.
w3-related/xml/no-native-parser/any -- node
w3-related/xml/no-native-parser/any/readme
              No-native xml parser implementations which can be used
              with ANY dylan implemenation are listed here
w3-related/xml/no-native-parser/gd-only
w3-related/xml/no-native-parser/gd-only/readme
              No-native xml parser implementations which can be used
              onyl with the Gwydion Dylan (GD) implemenation are listed
              here.
w3-related/xml/no-native-parser/od-only
w3-related/xml/no-native-parser/od-only/readme
              No-native xml parser implementations which can be used
              onyl with the Open Dylan (OD) implemenation are listed
              here



Annotation number 2: Andreas Bogk's CDAN vision
Pasted by: pet-rp
5 months, 3 weeks ago
Context in IRC logs
Paste contents:
Raw Source | Display As
see http://www.opendylan.org/pipermail/gd-hackers/2004-November/005107.html
its titled "Open Dylan migration plan" and contains some statements about CDAN.

Annotation number 3: Peter Housel note about library unifiaction back in 2004 relates to CDAN
Pasted by: pet-ro
5 months, 3 weeks ago
Context in IRC logs
Paste contents:
Raw Source | Display As
Back in Nov 2004 Peter Housel wrote:

"...I'm not interested in doing any library unification until we have a unified Foreign Function Interface on both systems, namely Collage.  Work on part of this, namely the C Program Representation (cpr) library, is in progress in the Monday project repository.  (It will be back-ported as an "illiterate" program for Open Dylan and Gwydion when it's done.)"

Q: What's the last status about the C Program Representation (cpr) library?

Annotation number 4: CDAN proposals: First drafts
Pasted by: pet-ro
3 months, 4 weeks ago
Context in IRC logs
Paste contents:
Raw Source | Display As
First (unstable) ideas about CDAN (Comprehensive Dylan Archive Network)
are now in the the Open Dylan Wiki:

* http://wiki.opendylan.org/wiki/view.dsp?title=CDAN:%20Structure%20Proposal
* http://wiki.opendylan.org/wiki/view.dsp?title=CDAN%20Prerequests

Colorize as:
Show Line Numbers
Index of paste annotations: 1 | 2 | 3 | 4

Ads absolutely not by Google

Lisppaste pastes can be made by anyone at any time. Imagine a fearsomely comprehensive disclaimer of liability. Now fear, comprehensively.