The left side panel is dedicated to all data used by your project.
By now, Enlide manages four types of element :
- templates : a template assembles components and can be easily re-used within your source code,
- snippets : a snippet is a reusable part of code. It includes all non-graphical elements,
- libraries : a library is an external template or snippet,
- components : a component is a UI element available from the Enlide and Community components library.
Thoses elements are dispatched in two tabs: the Explorer tab and the Components tab.
The Explorer tab allows you to navigate and perform all tasks on your workspace elements.
The Components tab displays icons for components that you can add to Enlide projects. Each component can be dragged and dropped onto a design view that we will see later on. Components are grouped by category and each one can be expanded or collapsed. Last but not least, the exclusive Community item gives you a direct access to a growing shared components database.
This feature, among others available, reminds you that Enlide is a Social IDE. And by social we means always connected to unlimited resources.
By now, Enlide manages four types of element :
- templates : a template assembles components and can be easily re-used within your source code,
- snippets : a snippet is a reusable part of code. It includes all non-graphical elements,
- libraries : a library is an external template or snippet,
- components : a component is a UI element available from the Enlide and Community components library.
Thoses elements are dispatched in two tabs: the Explorer tab and the Components tab.
The Explorer tab allows you to navigate and perform all tasks on your workspace elements.
The Components tab displays icons for components that you can add to Enlide projects. Each component can be dragged and dropped onto a design view that we will see later on. Components are grouped by category and each one can be expanded or collapsed. Last but not least, the exclusive Community item gives you a direct access to a growing shared components database.
This feature, among others available, reminds you that Enlide is a Social IDE. And by social we means always connected to unlimited resources.
0 comments
In next posts, we will introduce parts of Enlide Interface and here are our thought about user interface design.
The end of GUI
Early user interfaces, or Graphical User Interface (GUI), were based on operating systems multitasking ability without any Human-Computer Interaction model.
But studies have shown that users usually keep a single window up at a time on their desktop, and the internet user experience is multipages based : users go from page to page. That's the reason why so many UI are not user friendly.
The multipage navigation is visually close to the GUI way of displaying windows : each action could trigger a pop up which in turn could trigger.... But the perceived complexity of application is tightly coupled with the number of modal pop-up.
Then should we re-implement multi-window UI paradigm when designing web applications ?
The Rise of AISP
At Enlide, we believe in AISP UI : All In a Single Page User Interface. Ajax has bring a lot of features to html pages : drag and drop, auto-completion ... But one of its interesting aspect, it's the ability to group all ui element in a single page. It allows to drasticly reduce the number of modal windows and to improve the interactivity.
Most developers have faced the problem of grouping controls within forms, pages, or windows and set-up an efficient user workflow. AISP is the answer : dispatch your UI element on a single page and display them when needed. Modal pop-up are reduced to minimum and usability can be extended with each Ajax features.
A simple paradigm applied to application UI design.
The end of GUI
Early user interfaces, or Graphical User Interface (GUI), were based on operating systems multitasking ability without any Human-Computer Interaction model. But studies have shown that users usually keep a single window up at a time on their desktop, and the internet user experience is multipages based : users go from page to page. That's the reason why so many UI are not user friendly.
The multipage navigation is visually close to the GUI way of displaying windows : each action could trigger a pop up which in turn could trigger.... But the perceived complexity of application is tightly coupled with the number of modal pop-up.
Then should we re-implement multi-window UI paradigm when designing web applications ?
The Rise of AISP
At Enlide, we believe in AISP UI : All In a Single Page User Interface. Ajax has bring a lot of features to html pages : drag and drop, auto-completion ... But one of its interesting aspect, it's the ability to group all ui element in a single page. It allows to drasticly reduce the number of modal windows and to improve the interactivity.Most developers have faced the problem of grouping controls within forms, pages, or windows and set-up an efficient user workflow. AISP is the answer : dispatch your UI element on a single page and display them when needed. Modal pop-up are reduced to minimum and usability can be extended with each Ajax features.
A simple paradigm applied to application UI design.