Note: the orirginal database for this project corrupted, and I've tried to piece together
as much as I can for portfolio and informational purposes. We are currently working
on creating new tutorials and examples, which we hope to have available soon.
Thanks, and enjoy poking around the site.
The Emerge Toolkit Has Arrived.
- Instaneous, two way communication between server and browser.
- 100% C# 2.0. Write your entire application in your favorite CLR-supported language.
- Build application logic with existing widgets, or roll your own.
- Construct your interfaces in C# or XML. Control your design with CSS.
- Model your application domain with the integrated O/R mapper. Write your models in C# or XML. Store them in an embedded SQLite database, or soon MySQL or SQL Server!
- Prototype applications rapidly with our Scaffold and other data bound widgets
- Present data visually with rich, interactive SVG widgets.
- Tie everything togther with our live data binding services -- makes simultaneous event updates a snap, perfect for the Living Web.
- GPL and commercial licenses available.
News
emergetk documentation
06/26/2007 -- I finally got this up! Wow - that feels good Believe it or not, I'm still rocking with the emerge toolkit. Despite it's serious under-development, and the looming state persistence architectural quandary, I'm still loving using it. Getting Monodoc to work was a bit of a challenge, certainly still have a [...]A thousand boroughs: the future of digital communit(y|ies)
06/07/2007 -- I have been thinking a lot lately about what comes next after distributed identities take off. For the last 7 months or so, my friends and I have been researching, exploring and creating software and protocols to facilitate distributed social networks. As incredibly popular social networking has become, I'm surprised at how little open source [...]Another day, another project
10/18/2006 -- Well, it's been a while since the last post. A lot has happened, as is typical in one's life. While building the emerge toolkit was enjoyable, engaging, challenging and educational, financial profitable it was not. Which I basically understood would be the case when I decided to open source the project. So, as [...]