Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Search results

Page title matches

  • ...ions for each Buckminster extension, examples and guidelines for extending Buckminster. ==Extending the Buckminster framework==
    402 bytes (45 words) - 09:50, 18 January 2008
  • {{Backlink|Buckminster Project}} ...tensions. It is really beyond the scope of the documentation provided with Buckminster to cover the general plug-in mechanism of Eclipse. Please see the Eclipse d
    2 KB (343 words) - 10:24, 19 July 2007
  • #redirect [[Extension Point (Buckminster)]]
    43 bytes (4 words) - 03:05, 13 November 2006
  • {{Backlink|Buckminster Project}} ...pecification Extension allows you to decorate a [[Component Specification (Buckminster)|Component Specification]] in a powerful way. It is possible to add, overri
    470 bytes (63 words) - 10:02, 18 January 2008

Page text matches

  • ...ki. This is the Wiki home page for the [http://www.eclipse.org/buckminster Buckminster Component Assembly project], an [http://www.eclipse.org/tools/eclipsetools- Buckminster is a component resolution & materialization framework. Its purpose is to ge
    3 KB (489 words) - 08:53, 2 August 2010
  • ==Buckminster Dependency Specification== <p>Buckminster creates component dependency graphs using a Dependency Specification,
    3 KB (426 words) - 06:06, 12 December 2005
  • ==Buckminster Resource Map== <p>Each Buckminster installation will utilize one or more <i>resource maps</i> (an XML
    7 KB (1,122 words) - 06:27, 12 December 2005
  • {{Backlink|Buckminster Project}} ...erializing and publishing component specifications. It provides samples of Buckminster code as XML fragments, and illustrates common usage scenarios.
    67 KB (9,899 words) - 20:05, 14 February 2009
  • ...r Architecture]]''' - provides an overview of the architectural details of Buckminster. ...know more about "How Buckminster does things" rather than "what it does". Extension point implementers should find this useful.
    823 bytes (122 words) - 07:27, 31 August 2007
  • ...ions for each Buckminster extension, examples and guidelines for extending Buckminster. ==Extending the Buckminster framework==
    402 bytes (45 words) - 09:50, 18 January 2008
  • ** Martin -- Added Mutex; I-builds fixed; Discussions with Buckminster; Simple renamings **** 248 matches for "SystemFactory" (case insensitive, not whole word) - extension points, docs, local variables
    9 KB (1,295 words) - 11:09, 16 August 2006
  • {{Backlink|Buckminster Project}} Through 2007, the Project will aim for a significant elaboration or extension of functionality at roughly three-month intervals. Our roadmap for the ne
    2 KB (233 words) - 23:45, 14 February 2009
  • {{Backlink|Buckminster Project}} ...tensions. It is really beyond the scope of the documentation provided with Buckminster to cover the general plug-in mechanism of Eclipse. Please see the Eclipse d
    2 KB (343 words) - 10:24, 19 July 2007
  • {{Backlink|Buckminster Project}} This page has been archived. Go to [[Buckminster UI Guide]] instead.
    9 KB (1,494 words) - 10:01, 24 January 2008
  • <noinclude>{{Backlink|Buckminster Project}} ...d it can read individual files, and materialize component contents for a [[Buckminster Version Selector|Version Selector]].
    4 KB (541 words) - 03:08, 26 June 2008
  • <noinclude>{{Backlink|Buckminster Project}} ...erence appoints a public attribute in a CSPEC of another component via a [[Buckminster CSPEC Dependency|dependency]]. The execution of an ''action'' will often pr
    4 KB (595 words) - 15:02, 17 July 2007
  • {{Backlink|Buckminster Project}} ...nderstands the content of a component and is responsible for producing a [[Buckminster Component Specification]] (CSPEC) containing dependency information for the
    8 KB (1,159 words) - 11:43, 31 May 2012
  • <noinclude>{{Backlink|Buckminster Project}} A [[Buckminster Version Converter|Version Converter]] is responsible for (bidirectional) tr
    2 KB (368 words) - 10:37, 19 July 2007
  • <noinclude>{{Backlink|Buckminster Project}} ...will be asked to parse and compare the text between the delimiters in a [[Buckminster Version Designator|Version Designator]].
    3 KB (399 words) - 10:38, 19 July 2007
  • Buckminster XML Schemas can be found at _www.eclipse.org/buckminster/schemas/_, but you are not allowed to browse the catalog. ====[[Component Specification (Buckminster)|CSPEC]] and its extension====
    920 bytes (109 words) - 10:23, 19 July 2007
  • ...ituations where it's not possible to use a graphical user interface. Thus, Buckminster recognizes the need to provide a way to do these things from the command li ...any other aspects of Buckminster (and Eclipse in general, of course) it is extension based, thus making it easy to plug in new commands to work seamlessly toget
    2 KB (229 words) - 19:12, 23 March 2009
  • To allow a user to do anything useful with a 'raw' [[Buckminster Headless]]. Buckminster has a minimum, core command set. ...fast way to get a reminder on what command to use. Or, to verify that the extension command just written was actually linked in properly.
    2 KB (250 words) - 15:00, 17 July 2007
  • buckminster helloworld ...which is always prefixed to the name) and 0-M aliases are declared in the extension point along with an implementation class. The implementation class must der
    3 KB (411 words) - 10:17, 18 January 2008
  • ==Declare the command using the command extension point== ...on the <tt>org.eclipse.buckminster.cmdline</tt> plugin in order to see the extension point. Use the plugin manifest editor to add this dependency.
    6 KB (937 words) - 11:32, 28 August 2009

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)

Back to the top