Lauritz: Thanks for the detail info, Webwerkstatt and Core status, and the fix - Markdown now works indeed,
later, Milan On Thu, Feb 23, 2012 at 9:54 PM, Lauritz Thamsen <[email protected]> wrote: > Hi Milan. > > Thanks for letting us know. This defect was indeed related to > our refactoring efforts on github and the recent sync with Webwerkstatt. The > Markdown morph should work again and some new tests should prevent further > regression of this jQuery interface. > > Also, we should are done with the sync. So, please continue informing us > about defects, since Webwerkstatt shouldn't be in flux any longer. > > Please use webwerkstatt's trac 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 github issue if you > think it's an issue in a module in /core/. > 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. > > Best, > Lauriz > > On Feb 23, 2012, at 6:02 PM, Milan Zimmermann wrote: > > Just a note - Markdown text morph from Parts Bin stopped working a > few days ago - perhaps something to do with the > refactoring(speculating) - is it better to report on trac rather than > here ... or should Webwerkstatt be considered to be in flux for a > while? > > thanks, > milan > > MarkdownText>>>onDoubleClick: TypeError: Object > <lively.morphic.Text#79F21... - MarkdownText> has no method 'jQuery' > TypeError: Object <lively.morphic.Text#79F21 > > On Thu, Feb 23, 2012 at 4:07 AM, Fabian Bornhofen > <[email protected]> wrote: > > Hi - > > > two weeks ago, Robert, Lauritz and I started to refactor parts of the > > Lively Kernel. The idea is to modularize the code base and to answer > > the question "What is the kernel in 'Lively Kernel'?". Moving the core > > components of LK to a GitHub repository will allow for easier > > synchronization of core code in different LK installations. We hope > > that encouraging people to experiment with the most basic things in > > Lively will speed up development and help us gain some momentum. > > > Some changes have already gone live in Webwerkstatt. > > > What did we do? > > We ... > > - put the core/ folder on github: https://github.com/rksm/LivelyKernel > > - removed PartsBin from core/ > > - removed a bunch of things that did not appear to be 'core' either > > (there might be more) > > - moved tests for each submodule into the respective module's test/ folder > > - made naming more consistent ('AST' -> 'ast') > > - introduced lively.lang and lively.morphic.Graphics > > - added an simple test environment > > > If you encounter any problems with your existing parts or modules that > > could have to do with these refactorings, please let us know. > > > We have yet to introduce a more formalized process of how to port > > changes from Webwerkstatt into the GitHub repository. We will probably > > make an announcement about that soon. Meanwhile, we invite you to > > follow or fork us on GitHub, let us know what you think and, of > > course, report any issues you find. > > > Best, > > Fabian > > _______________________________________________ > > 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 > > _______________________________________________ lively-kernel mailing list [email protected] http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
