Re:Mail.app implemented on the web using ukijs
by rrhyne on Thursday April 08, 2010 @02:28PM
(#1250455)
They have some good videos available.
The biggest concern for me, a user considering frameworks is always: 'how long are these guys going to be around'
Re:Mail.app implemented on the web using ukijs
by tolmasky on Thursday April 08, 2010 @02:37PM
(#1250479)
The only videos I found were the screencasts on the bottom. While fine, these only demonstrate basic features, features that again are available pretty much across the board. What I want to see is them putting together this Mail app from scratch, lets have a real start and a real goal. Now, I know many frameworks don't do this, but thats precisely why it would be a huge win to have. Even we don't do this as well as we should.
Now, if the reply to this is "but the video would take 10 hours!", then unless your counting time to make the art in photoshop, there's a serious problem. If I were to do a screencast of making that Mail.app interface in Cocoa, it would literally be 10-20 minutes max. Its honestly just drag and dropping the components in in Interface Builder, then setting up the bindings and data sources.
Re:Mail.app implemented on the web using ukijs
by sant0sk1 on Thursday April 08, 2010 @05:32PM
(#1251050)
Actually, that'd be a nice screencast to put on cappuccino.org. Perhaps worth the time/effort..
Re:Mail.app implemented on the web using ukijs
by boucher on Thursday April 08, 2010 @03:52PM
(#1250698)
For the most part, open source makes the irrelevant. Not that we are going anywhere, but if we dropped off the face of the planet tomorrow, Cappuccino would go on. We already have a thriving community of contributors and users who rely on Cappuccino for their own businesses, many of whom are more than capable of continuing the frameworks development.
Re:Mail.app implemented on the web using ukijs
by papertiger on Thursday April 08, 2010 @09:59PM
(#1251627)
I don't think open source makes that consideration irrelevant. It is an important factor when choosing a framework. I would bet that most of the users and probably a good portion of the contributors are using a framework precisely because it saves them from spending the time to develop/maintain those features on their own.
Cappuccino would go on, but one must acknowledge that it could certainly flounder without the solid direction, organization, and vision that brought it into the world in the first place.
The unfortunate thing is that the "small demo" strategy really does a disservice to the framework itself: usually what happens is that competing frameworks shrug it off because they already have a demo that does the same thing (and thus don't learn from the new innovations being demonstrated), and oftentimes the "general audience" devolves into meaningless discussions about exactly how many lines of code or hours of time more or less it would have taken in some other technology.
I offer this as launch advice to anyone (as I did to the other guys here on HN):
1. Make something truly unique
2. The more "real" the better
3. Most importantly show us how you did it: I would love it if new frameworks coming out had little tutorials of these apps or better yet a video showing how the app was made as opposed to saying "it took us X hours and heres the code". You wrote this framework, for all I know you designed this framework specifically for this demo. Show me how you made this and why it was so much easier for you. For example, what we do with Cappuccino is show that you can make a similar interface with Interface Builder and nib2cib in 10 minutes, not 10 hours. If you believe that your selling point is your meta programming or whatever, then show me how it made things better in the process.
Again, I honestly haven't looked deeply enough into this to make a reasoned opinion on whether this framework is good or bad, but I see these responses a lot and I think doing the above helps avoid them and to better demonstrate what makes you "special".