Be the first to post a text review of XML-based Variant Configuration Language. Rate and review a project by clicking thumbs up or thumbs down in the right column.

• XVCL Processor Version 3.2.3 file released: edu.xvcl.core_3.2.3_src.zip

  - Extensions in code from v 3.2.1 to support additional tools like XVCL Eclipse Workbench, Profiler, Frame Analyzer, Debugger - For more info on these tools please visit - http://xvcl.comp.nus.edu.sg/ and http://xvcl.comp.nus.edu.sg/forum - No change in stand-alone processor functionality

  posted 433 days ago

• XVCL Processor Version 3.2.3 file released: edu.xvcl.core_3.2.3_bin.zip

  - Extensions in code from v 3.2.1 to support additional tools like XVCL Eclipse Workbench, Profiler, Frame Analyzer, Debugger - For more info on these tools please visit - http://xvcl.comp.nus.edu.sg/ and http://xvcl.comp.nus.edu.sg/forum - No change in stand-alone processor functionality

  posted 433 days ago

• File released: /XVCL Processor/Version 3.2.3/edu.xvcl.core_3.2.3_src.zip

  posted 433 days ago

• File released: /XVCL Processor/Version 3.2.3/edu.xvcl.core_3.2.3_bin.zip

  posted 433 days ago

• XVCL Specification Version 2.10 file released: XVCL_spec_2_10.pdf

  Recorded 1 September 2008, by Stan Changes in Processor specs 2.10 as compared to 2.07 and 2.08. 1.Adapting non XCL files Source files that are adapted as is (i.e., do not contain any XVCL commands) can be adapted without converting them into x-frames. New attribute src is introduced for <adapt> for that purpose: src=yes-no This attribute tells whether the file to be adapted is a proper x-frame (no) or just any source file (yes). For yes, the processor outputs files contents without processing it. The default value is "no", meaning a proper x-frame. For example, to adapt source-file as is: <adapt x-frame="source-file" src=yes> 2.Processor option A has been removed In 2.07: A processor option A allows the user to avoid deleting an existing file when the processor attempts to emit output to this file for the first time. When the processor is invoked with option A, for example: java -jar xvcl.jar A SPC the processor will append emitted output to file file-name even if the file file-name already existed before the processor was invoked. 3.Textual context Textual contents need not be written in CDATA sections. The whole paragraph about CDATA has been removed from Section 20 of specs as irrelevant. Textual Content can be any text that is intended to be customized by XVCL commands. This text may include anything including symbols that XML reserves for its own use, namely .<., .>. ,.&., double quote () and single quote (). These symbols are not interpreted as XVCL commands by the processor 2.10 or later. For compatibility with earlier versions, you can still keep those symbols in CDATA sections. The processor ignores XVCL commands if they are written inside CDATA section. Sections 3 and 4 (and no more relevant comments throughout the specs) in XVCL specs 2.10 have been updated accordingly 4.References to non-existing variables A reference to a non-existing variable in Symbol Table is considered an error in all situations. (Specs, Section 9.2) 5.X-frame file extensions An extension (if any), is treated as an integral part of the file name.

  posted 434 days ago

• File released: /XVCL Specification/Version 2.10/XVCL_spec_2_10.pdf

  posted 434 days ago

• Forum thread added

  manasgupta created the We have moved! forum thread

  posted by manasgupta 434 days ago

• Forum thread added

  manasgupta created the We have moved forum thread

  posted by manasgupta 434 days ago

• Forum thread added

  manasgupta created the We have moved! forum thread

  posted by manasgupta 434 days ago

• XVCL Processor Version 3.5.0 beta file released: edu.xvcl.core_3.5.0.v20071024_src.zip

  posted 745 days ago