-
Notifications
You must be signed in to change notification settings - Fork 0
Possible ways to help and candidate tasks
This wiki page lists ways that contributors who are not yet committers can help the open source project.
A good way to contribute is to test the application and file good bugs.
Even better than filing bugs is fixing bugs and submitting patches for those fixes.
One possible area for contribution is to develop metadata so that particular widgets can appear in Maqetta's UI. For widgets to appear in the Maqetta widget palette, the widget needs to have widget metadata [1] to describe supportive files (e.g., JS and CSS) that the widget needs to operate. For widgets to appear in the Maqetta theme editor, the widget needs theme metadata.
Maqetta already incorporates the source editor module from the Eclipse Orion project. There are many other interesting technologies that are either in Orion today or will be coming out soon that could help Maqetta, and there are potentially strong synergies if the two projects collaborate on core technology development.
- Orion is exploring a general mechanism for integrating with source control systems and task management systems. Maqetta might be able to hook into those developments.
- Orion is exploring code comparison utilities which might be useful for Maqetta users to compare files or different versions of the same file
There are multiple scenarios where Maqetta could benefit from drawing tools. (1) For wireframing and other UI mockups, sometimes the UI designer who is sketching a proposed UI in Maqetta needs a custom UI component that hasn't been created yet (and therefore unavailable in the Maqetta widget palette), and needs basic drawing tools to sketch out how that component would look. (2) Increasing, webapps will use vector graphics to illustrate information, and therefore a Maqetta user will sometimes want to mock up the page content using simple drawing tools.
- Application Flow Diagram: Some UX designers have requested that Maqetta provide a flow diagram view that shows the different applications states for the user interface (as defined on the states palette) and possible flows among the states. For example, the application can go from A->B->C but you can't go directly from A to C. There is not yet a detailed definition of how this feature should work. For example, should the flow view be editable or view-only?
- Publish as a Document for Team Review: Maqetta generates a report of some form (a web page? a PDF?) which provides pictures of the UI and includes the application flow diagram which can be sent around for review.