<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Milan.<div><br></div><div>Thanks for letting us know. This defect was indeed related to our <a href="http://github.com/rksm/LivelyKernel">refactoring efforts on github</a> and the recent sync with Webwerkstatt. The Markdown morph should work again and some new tests should prevent further regression of this jQuery interface.</div><div><br></div><div>Also, we should are done with the sync. So, please continue informing us about defects, since Webwerkstatt shouldn't be in flux any longer. </div><div><br></div><div>Please use <a href="http://lively-kernel.org/trac">webwerkstatt's trac</a> if you think that a bug is only related to our Webwerkstatt deployment (examples: parts, version support, worlds in Webwerkstatt, user or project modules, ...) and create a <a href="http://github.com/rksm/LivelyKernel/issues">github issue</a> if you think it's an issue in a module in <i>/core/</i>. </div><div>If you're not sure, it's probably good to prefer Webwerkstatt for now, but we'll follow both tracking systems closely – so either way is really fine.</div><div><br></div><div>Best,</div><div>Lauriz</div><div><br><div><div>On Feb 23, 2012, at 6:02 PM, Milan Zimmermann wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Just a note - Markdown text morph from Parts Bin stopped working a<br>few days ago - perhaps something to do with the<br>refactoring(speculating) - is it better to report on trac rather than<br>here ... or should Webwerkstatt be considered to be in flux for a<br>while?<br><br>thanks,<br>milan<br><br>MarkdownText>>>onDoubleClick: TypeError: Object<br><lively.morphic.Text#79F21... - MarkdownText> has no method 'jQuery'<br>TypeError: Object <lively.morphic.Text#79F21<br><br>On Thu, Feb 23, 2012 at 4:07 AM, Fabian Bornhofen<br><<a href="mailto:fbornhofen@googlemail.com">fbornhofen@googlemail.com</a>> wrote:<br><blockquote type="cite">Hi -<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">two weeks ago, Robert, Lauritz and I started to refactor parts of the<br></blockquote><blockquote type="cite">Lively Kernel. The idea is to modularize the code base and to answer<br></blockquote><blockquote type="cite">the question "What is the kernel in 'Lively Kernel'?". Moving the core<br></blockquote><blockquote type="cite">components of LK to a GitHub repository will allow for easier<br></blockquote><blockquote type="cite">synchronization of core code in different LK installations. We hope<br></blockquote><blockquote type="cite">that encouraging people to experiment with the most basic things in<br></blockquote><blockquote type="cite">Lively will speed up development and help us gain some momentum.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Some changes have already gone live in Webwerkstatt.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">What did we do?<br></blockquote><blockquote type="cite">We ...<br></blockquote><blockquote type="cite">- put the core/ folder on github: <a href="https://github.com/rksm/LivelyKernel">https://github.com/rksm/LivelyKernel</a><br></blockquote><blockquote type="cite">- removed PartsBin from core/<br></blockquote><blockquote type="cite">- removed a bunch of things that did not appear to be 'core' either<br></blockquote><blockquote type="cite">(there might be more)<br></blockquote><blockquote type="cite">- moved tests for each submodule into the respective module's test/ folder<br></blockquote><blockquote type="cite">- made naming more consistent ('AST' -> 'ast')<br></blockquote><blockquote type="cite">- introduced lively.lang and lively.morphic.Graphics<br></blockquote><blockquote type="cite">- added an simple test environment<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">If you encounter any problems with your existing parts or modules that<br></blockquote><blockquote type="cite">could have to do with these refactorings, please let us know.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">We have yet to introduce a more formalized process of how to port<br></blockquote><blockquote type="cite">changes from Webwerkstatt into the GitHub repository. We will probably<br></blockquote><blockquote type="cite">make an announcement about that soon. Meanwhile, we invite you to<br></blockquote><blockquote type="cite">follow or fork us on GitHub, let us know what you think and, of<br></blockquote><blockquote type="cite">course, report any issues you find.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Best,<br></blockquote><blockquote type="cite">Fabian<br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">lively-kernel mailing list<br></blockquote><blockquote type="cite"><a href="mailto:lively-kernel@hpi.uni-potsdam.de">lively-kernel@hpi.uni-potsdam.de</a><br></blockquote><blockquote type="cite"><a href="http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel">http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel</a><br></blockquote>_______________________________________________<br>lively-kernel mailing list<br><a href="mailto:lively-kernel@hpi.uni-potsdam.de">lively-kernel@hpi.uni-potsdam.de</a><br>http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel<br></div></blockquote></div><br></div></body></html>