The main point of this tool is to make managing projects and working on them easier and faster. The goal is to create an entire suite that works as one and can be used by an entire development team, the point isn't to eliminate the IDE or graphics development tools that exist but rather to open communication between collegues using this kind of software.
The first part of the project is building a WYSIWYG editor, although I've found a few, flairbuilder in particular looks like a pretty good project I'd like to build it from scratch to be sure I have a full understanding of all the components and remain free to change anything about the behavior of the program as it evolves. It seems some things in that project are pretty buggy and I think it could be more robust by using introspection to determine what values exist on the built in objects, they allow you to use, rather than depending entirely on programmer made controls. I would like to have a mix so I will make controls for common attributes and then give the full property list on a seperate tab or within a different pane of a view stack (one in the same really).
Another section will allow users to enter requirements this would be the entry point for most projects, since requirements gathering generally happens at the beginning of a project.
Another section will allow wireframe creation and tying of wireframes to all other components of the program, for example wireframes can be tied to requirements, designs, or even deployed sections of/entire programs. This is the main reason for the WYSIWYG editor, so wireframes can be created shared, modified all online without the need to open another program.
Another section will allow bug entry, tracking, and ties to all the other sections, so bugs can apply to a certain deployment or bugs can be tied to wireframes or bugs can be tied to requirements.
Another section will allow for design submission and linking to tie it to the other sections.
Also want dependencies as well as a comments table that can tie to everything so people can comment on anything and can tie "dependencies" to anything which is just a generic thing that a requirement, wireframe, or design or bug depends on.
As an overall visual goal the plan is to make each section as modular as possible so users can customize their workspace with the tools they use the most and save different views.
I guess if you're still with me you probably get the idea, I want everything to be able to link to everything else but in a concise way. As is my current employer uses many disparete systems for inter office communication, some of our documentation gets passed through our internal wiki system and much of it gets passed through e-mails and this just seems like a crazy way to go, but I would guess a lot of business do it this way, so I'd like to build a tool that makes life easier on everyone... self included.