I've had similar thoughts before. I think you've correctly identified the downsides...<div><br></div><div>Some debate would be required, I guess. Personally I'm a bit hesitant, but don't have a strong opinion. It would certainly be cool to see someone prototype it...</div>
<div><br></div><div>Julian<br><br><div class="gmail_quote">On Mon, May 7, 2012 at 11:49 AM, Philippe Marschall <span dir="ltr"><<a href="mailto:philippe.marschall@gmail.com" target="_blank">philippe.marschall@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi<br>
<br>
I had this totally ridiculous idea. The Seaside configuration<br>
"framework" basically rebuilds Magritte-Core and Magritte-Seaside.<br>
What about if we replace these parts with Magritte? We'll have to pay<br>
attention to dependency loops like Magritte-Seaside depending on<br>
Seaside and Seaside depending on Magritte-Seaside especially for<br>
things like #componentClass:.<br>
<br>
I'm well aware of the down-sides:<br>
- More dependencies<br>
- Harder to port, you'll need to port Magritte first which requires pragmas<br>
- Magritte version of Seaside shared with applications using Magritte<br>
<br>
I'm not seriously proposing or pushing this, I just wanted to provide<br>
some food for thought. I was probably under too much Eclipse 4 / EMF<br>
influence lately.<br>
<br>
Cheers<br>
Philippe<br>
_______________________________________________<br>
seaside-dev mailing list<br>
<a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
</blockquote></div><br></div>