How important design mode support in Coolite for you
*NEW - Coolite Toolkit Version 0.7 now available for DOWNLOAD. See also Examples Explorer.
 

Coolite Forums

Welcome Guest ( Login | Register )
 
««123»»
How important design mode support in Coolite...
Subscribe
Last Login: 12/18/2008 8:53:41 AM
Posts: 1,
Posted 5/6/2008 5:00:23 PM

Group: Coolite Early Adopter
mthakershi (4/2/2008)
Design mode is extremely important. With all respect, no matter what these 'notepad' experts say, this product without full design-time support is worthless for 99% of programming community.

Just my opinion based on around 100 ASP.NET programmers I know. Thank you.


Hmm.. The current ExtJS framework has no design-time support... and it is one of the top frameworks out there.

Design-time support, in my opinion, is a luxury; it's nice to have, but in no way is absolutely needed for programmers. The current Coolite controls already have FULL intellisense support in Visual Studio's Source view, and that for me is more than I could ever ask for, and we thank you for that ^_^

I think it is more important to get the bulk of ExtJS to work in ASP.NET first, and then work on the design-time support where needed.
Last Login: 10/3/2008 1:07:41 AM
Posts: 11,
Posted 5/7/2008 1:56:00 AM

Group: Coolite Early Adopter
 Design Time support would contribute to give a more complited product, but not important to me! Then about the code, I do agree with what Chelonian said.
Last Login: 10/14/2008 3:32:03 AM
Posts: 15,
Posted 5/7/2008 2:28:48 AM

Group: Coolite Early Adopter
 I totally agree with what lohail said.  If design time support will not make available on time then it can become a future feature. You cant fly with the eagles if you swim with the ducks!
Last Login: 5/7/2008 12:31:19 PM
Posts: 1,
Posted 5/7/2008 11:25:06 AM

Group: Coolite Early Adopter
 Personally, I'm quite comfortable working in source view -- I've created & coded very complex Ext-based front-ends with Aptana (no design help).

However, I think design-time support can be helpful when it comes to dealing with Properties -- it is a frequent occurence in VS2008 that I have to click over to design view when interacting with some objects (say, objectdatasource and others) to view ALL Properties for the object (like Events associated with that object/component).

Keep up the good work. Can't wait to see the whole Ext toolkit available in VS.
Last Login: 11/18/2008 5:55:23 AM
Posts: 72,
Posted 6/4/2008 9:36:19 AM

Group: Coolite Premium Member & Early Adopter
I think Design mode support is important for Coolite as it was well said here in this site home page: 

"The suite of web controls were built with a focus on bringing full Visual Studio Design-Time support to the Ext JavaScript Framework".

That means, this is the focus, and it will be very important to the company in the market as a product for ASP.NET developers.

On the other hand, I can see that the team is endeavour to finish this design mode support to release in the 0.5 version. But I don't think it is so important that justify such delay in the version release in order to have it done. It just my personal opinion.

There are many other important resources to be explored.
Another important thing to mention is that Design Mode reduce the learning curve of a framework, as it makes easy to test properties and combine options on the solution.
However, that learning curve can also be reduced by a good documentation and good examples.

The SandBox in this site is the best idea to show how to accomplish it.

I hope that helps or make you gyus think about this release we are all anxious waiting.

Best regards,

Leonardo.
Last Login: Today @ 3:28:10 PM
Posts: 1,652,
Posted 6/5/2008 8:55:29 AM

Group: Core Development Team
http://www.coolite.com/download/
--
Geoffrey McGill
Coolite Inc.
Development Team
Coolite Examples | Coolite API Docs | ExtJS API Docs
twitter [coolite | personal]
Last Login: 12/31/2008 4:57:30 PM
Posts: 17,
Posted 7/7/2008 4:23:11 AM

Group: Coolite Premium Member & Early Adopter
 
I think from a product perspective, design time support is defintely needed. Mostly to engage the core of .NET developers who would be interacting with Coolite.

However, design time support development is complex (unless thats your thing) thus increasing time for the controls release. Personally, I hardly ever use design time features (for reasons already stated by others) and would like to see individual controls released before they are fully supported in design time. Even if its a seperate installation which we need to keep updated ourselves as each development revision has been released would work for me.

This would make both sides happy (design time developers vs non-design time developers) as the official realesed version toolkit would fully support design time capabilities; while allowing us to interact with controls that work but not fully supported.
Last Login: 12/28/2008 6:09:17 AM
Posts: 79,
Posted 9/24/2008 7:15:13 AM

Group: Coolite Premium Member & Early Adopter
 I agree with the opinion that design time support should be last.  Having everything functionally working well first is much more important.  That being said, if you want this product to be adopted by asp.net programmers (not ExtJS programmers), you will need significant design time support, and for myself, I would use it.

For example, when I create an <ext:store> It feels silly to be typing all the datafield names which are all available from reflector from any of the data source controls.  Same thing with Grid.  I wonder if there is stuff in MONO you can use?

At anyrate, I feel a little bad complaining because of the wealth of stuff that's in the package already.  This is more, "it would be nice" kind of comment.
Peter Kellner

http://peterkellner.net

Microsoft MVP, ASP.NET
Last Login: 11/27/2008 4:54:07 AM
Posts: 1,
Posted 10/9/2008 2:37:02 PM

Group: Coolite Early Adopter
Design mode is important, but is not a priority.

Last Login: 12/9/2008 8:09:08 PM
Posts: 3,
Posted 10/9/2008 4:35:36 PM

Group: Coolite Early Adopter
Given the richness of whats exposed in the objects, without solid documentation, and fuller examples, id say that design mode is an absolute priority!

Trying to work out whats possible in objects (or to guess your way into getting a control to work being new to coolite and extjs) is much easier to do in the properties window than paging though an autocomplete list.

2 cents.
« Prev Topic | Next Topic »
««123»»
Reading This Topic
Active Users: 0 ( 0 guests, 0 members, 0 anonymous members )
No members currently viewing this topic.
All times are GMT -8:00, Time now is 7:38pm