There currently is not mechanism for that as code sharing is automatically provided by all the users using the same LK installation (e.g. WebWerkstatt or Lively Web). At least that is the idea. For sharing kernel code, we use git commits either from local installations or the Lively Web.
One way you could backup and share code (a backup is automatically done through the wiki feature btw.), you can - depending on the way you are developing - place all the code in a module that resembles a JS file (say http://lively-web.org/users/CarlosCrosetti/project.js - which makes it the users.CarlosCrosetti.project module). If you are developing with Parts, I currently cannot think of a way of achieving the same (the PartsBin is the place for sharing and reuse and it can be referenced from different LK installations, versioning is provided automatically). Though Parts are also just a combination of HTML, JSON and MetaInfo files (see http://lively-web.org/PartsBin/Fun - Elephant for example). I hope this provides you with some solution for what you are thinking about. - Marko On 06 May 2014, at 01:25, Carlos Crosetti <[email protected]> wrote: > Thanks Marko. > > The idea is to keep the source code I might write as a backup and to > eventuallu share with others. > > On 05/05/2014 05:04 AM, Marko Röder wrote: >> Hi Carlos - >> >> There currently is no equivalent to file in-out. But maybe there are other >> mechanisms to achieve what you are looking for. >> What exactly do you want to do? >> >> Best, >> >> - Marko >> >> >> >> On 05 May 2014, at 01:00, Carlos Crosetti <[email protected]> >> wrote: >> >>> Hi, what is the Smalltalk-equivalent class file in-out in the LK? >>> >>> Regards, Carlos >>> _______________________________________________ >>> lively-kernel mailing list >>> [email protected] >>> http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel >> >
_______________________________________________ lively-kernel mailing list [email protected] http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
