First of all, thank you sculpture team of the impressive effort you did so far.
Last summer, I was thinking to start develop something very similar to sculpture then I started to investigate and learn similar ideas. Recently I found a contribution post in http://www.lhotka.net
about sculpture so you may guess the rest of the story; download, install, learn, saw the introduction video (excellent idea for attraction and demonstrating the features of sculpture), and finally rather than reinvent the wheel I decided to contribute with
Create a common repository (other than the sculpture module designer) to become the centralize location for all objects (Entities, Data Contracts, Services, etc.) and its specifications so later from this centralized
location you can add them to multiple designer.
Create an interface for that repository and I suggest calling it “Objects Manager”. Very similar to sculpture explorer (sculpture explorer should remain to increase, enhance, and speedup to locate the objects
in the model viewer).
Objects Manager can filter, search, group, create, rename and delete. (From the user perspective: Association requires the model viewer).
Store each object separately using XML format (in separate files, or common Database).
I suggest , not to store the objects as part of the project , because in our development environment we are working on a project that have 50,000+ entities, and of course not all of them related to each other
directly but all working under the same umbrella.
so if these objects are loaded in Visual studio this will raise a performance issue.
Common repository existence will make it possible and easier to have an impact analysis report, or viewer.
Consider the source control for objects.
“Code generation and refactoring”
Select single, multiple or all objects to be generated
Select what to generate, business objects, Data access object or User Interface objects.
With delete an object give the option to delete all related generated objects.
Rename entity members should be reflected on all generated code without regenerate them in order not lose custom changes.
Generated DB script should be moved automatic to the Database project.
Reserve the changes by the user and this include and limited to ( custom code regions on existing code , user interface changes, etc)
Combine the User interface template generators to project module so user define his templates for this particular project also can store them in the source control.
Group Entity member with a logical grouping mechanism and this later can be reflected as Tabs, frames or tables, etc.
“Sculpture Model viewer enhancements”
Adding Entities, services, data contracts, etc using the context menu ( I mean right click the mouse
à add entity)
Drag-drop the members from the entity to data contract to define contract members.
Do something very similar to PowerToys for the Class Designer and Distributed System Designer http://www.codeplex.com/modeling
Add Zoom in/out feature for the sculpture model viewer.
Add a toolbar with the same functions available in the details window.
Show all sculpture properties in the original property window (why to have another window for the properties).
-Why the source code is not source control under code plex ttps://Sculpture.svn.codeplex.com/svn ?
-What will be relased in Version 1.0 and what is planed so far for version 1.1 or version 2?
-How can I contribute with this effort and be part of the team?