Platform Team/Glossary: Difference between revisions

Line 36:

=====local sweet=====

:It is an important high-level concept in ''Sweets'', which is intended to make the development process of ''sweet'' projects more comfortable. Technically, it is the source software of the ''sweet'' project (i.e., with a ''recipe'' file) placed somewhere in the file system and registered in the local ''Sweets'' instance as a single ''implementation'' for ''interfaces'' it ''implements''. It is always possible to run this ''local sweet'' directly by using the full filesystem path as an ''interface'', but its most useful feature is reuse of the ''local implementation'' in routine ''Sweets'' workflows. For example, if sugar-toolkit sources were cloned to the {{Code|~/src/sugar-toolkit}} directory, then while running a {{Code|sugar}} ''sweet'', it would become possible to reuse local sugar-toolkit sources as a regular ''implementation''.

:It is an important high-level concept in ''Sweets'', which is intended to make the development process of ''sweet'' projects more comfortable. Technically, it is the source software of the ''sweet'' project (i.e., with a ''recipe'' file) placed somewhere in the file system and registered in the local ''Sweets'' instance as a single ''implementation'' for ''interfaces'' it ''implements''. It is always possible to run this ''local sweet'' directly by using the full filesystem path as an ''interface'', but its most useful feature is reuse of the ''local implementation'' in routine ''Sweets'' workflows. For example, if sugar-toolkit sources, that implements {{Code|sdk/sugar-toolkit}} ''interface'', were cloned to the {{Code|~/src/sugar-toolkit}} directory, then while running a {{Code|sdl/sugar}} ''sweet'', it would become possible to reuse local sugar-toolkit sources as a regular ''implementation'' of {{Code|sdk/sugar-toolkit}} dependency of {{Code|sdk/sugar}}.

=====sweet package=====

@@ Line 36: / Line 36: @@
 =====local sweet=====
-:It is an important high-level concept in ''Sweets'', which is intended to make the development process of ''sweet'' projects more comfortable. Technically, it is the source software of the ''sweet'' project (i.e., with a ''recipe'' file) placed somewhere in the file system and registered in the local ''Sweets'' instance as a single ''implementation'' for ''interfaces'' it ''implements''. It is always possible to run this ''local sweet'' directly by using the full filesystem path as an ''interface'', but its most useful feature is reuse of the ''local implementation'' in routine ''Sweets'' workflows. For example, if sugar-toolkit sources were cloned to the {{Code|~/src/sugar-toolkit}} directory, then while running a {{Code|sugar}} ''sweet'', it would become possible to reuse local sugar-toolkit sources as a regular ''implementation''.
+:It is an important high-level concept in ''Sweets'', which is intended to make the development process of ''sweet'' projects more comfortable. Technically, it is the source software of the ''sweet'' project (i.e., with a ''recipe'' file) placed somewhere in the file system and registered in the local ''Sweets'' instance as a single ''implementation'' for ''interfaces'' it ''implements''. It is always possible to run this ''local sweet'' directly by using the full filesystem path as an ''interface'', but its most useful feature is reuse of the ''local implementation'' in routine ''Sweets'' workflows. For example, if sugar-toolkit sources, that implements {{Code|sdk/sugar-toolkit}} ''interface'', were cloned to the {{Code|~/src/sugar-toolkit}} directory, then while running a {{Code|sdl/sugar}} ''sweet'', it would become possible to reuse local sugar-toolkit sources as a regular ''implementation'' of {{Code|sdk/sugar-toolkit}} dependency of {{Code|sdk/sugar}}.
 =====sweet package=====