https://ioke.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=BragiIokeWiki - User contributions [en]2026-05-20T00:34:29ZUser contributionsMediaWiki 1.30.0https://ioke.org/wiki/index.php?title=User:Bragi&diff=213User:Bragi2009-03-18T11:12:39Z<p>Bragi: New page: Łukasz Piestrzeniewicz a.k.a. Bragi Ragnarson * jabber/email: bragi@ragnarson.com * blog: http://blog.rangarson.com/</p>
<hr />
<div>Łukasz Piestrzeniewicz a.k.a. Bragi Ragnarson<br />
<br />
* jabber/email: bragi@ragnarson.com<br />
* blog: http://blog.rangarson.com/</div>Bragihttps://ioke.org/wiki/index.php?title=Cane&diff=212Cane2009-03-18T11:11:32Z<p>Bragi: /* Implementation Ideas */</p>
<hr />
<div>= Cane =<br />
<br />
Cane is a library/application packaging and sharing system.<br />
<br />
== Implementation Ideas ==<br />
<br />
First iteration - for sharing libraries between early adopters only. <br />
<br />
Let's start assume that Ioke and Ioke-related libraries live in the same directory on developer's desktop, be it ~/projects or ~/Projects/IokeRelated.<br />
<br />
Implementation:<br />
* Ioke should provide method to add load paths (addLoadPath) to current runtime (absolute or relative to file from which was called)<br />
* Ioke should provide method called cane that accepts name of library<br />
* when cane() is invoked it tries to find directory with name of library in starting with parent directory and going up<br />
* when directory is found cane adds it to load path and explicitly use()s library init.ik file<br />
* init.ik file may add directories from library to load path<br />
<br />
From library developer's perspective this means that creating new library is as simple as:<br />
* creating new directory parallel to Ioke checkout<br />
* adding library files in structure they like<br />
* adding init.ik to specify which directories make the library<br />
<br />
From library user's perspective using library means:<br />
* checking out source code in parallel to Ioke directory (and project's directory as well)<br />
* adding cane('library_name') to main file<br />
* use()ing any needed files from library</div>Bragihttps://ioke.org/wiki/index.php?title=Cane&diff=211Cane2009-03-18T11:10:35Z<p>Bragi: New page: = Cane = Cane is a library/application packaging and sharing system. == Implementation Ideas == First iteration - for sharing libraries between early adopters only. Let's start assume...</p>
<hr />
<div>= Cane =<br />
<br />
Cane is a library/application packaging and sharing system.<br />
<br />
== Implementation Ideas ==<br />
<br />
First iteration - for sharing libraries between early adopters only. <br />
<br />
Let's start assume that Ioke and Ioke-related libraries live in the same directory on developer's desktop, be it ~/projects or ~/Projects/IokeRelated.<br />
<br />
Implementation:<br />
* Ioke should provide method to add load paths (addLoadPath) to current runtime (absolute or relative to file from which was called)<br />
* Ioke should provide method called cane that accepts name of library<br />
* when cane() is invoked it tries to find directory with name of library in starting with parent directory and going up<br />
* when directory is found cane adds it to load path and explicitly use()s library init.ik file<br />
* init.ik file may add directories from library to load path<br />
* both <br />
<br />
From library developer's perspective this means that creating new library is as simple as:<br />
* creating new directory parallel to Ioke checkout<br />
* adding library files in structure they like<br />
* adding init.ik to specify which directories make the library<br />
<br />
From library user's perspective using library means:<br />
* checking out source code in parallel to Ioke directory (and project's directory as well)<br />
* adding cane('library_name') to main file<br />
* use()ing any needed files from library</div>Bragi