Hi all, I don't know if anyone except Brian O'Reilly has looked at my Weblocks fork (https://github.com/slburson/weblocks). Just to remind you, it has some incompatible changes, most notably that it uses Bootstrap and jQuery rather than the original Weblocks CSS and JavaScript libraries.
Although it still needs more work, I'm thinking it should become the recommended version of Weblocks for new projects. How do people feel about that? Of course there are existing Web apps that use the current version, and we probably don't want to force everyone to convert their apps. So I'm thinking we should call the new version Weblocks 2, and ask Zach to set up a separate Quicklisp package for it. That will allow it to continue to diverge from the existing version, without inconveniencing anyone who still wants to use the latter. Does that seem reasonable? An alternative would be to rename the current one to something like "weblocks-stable" and let "weblocks" refer to the new one. That might be appropriate if we were fairly sure that most users would eventually want to use the new one. I don't think we're at that point yet. I'm thinking we'd maintain the two as two branches in a single repo, to make it easy to copy bug fixes between them, though I'm not sure Quicklisp can deal with that situation easily -- I'll ask Zach. What do you think? -- Scott -- You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/weblocks?hl=en.
