design

[polinekes]

No description provided.

[polinekes]

[polinekes]

טוב ח׳ברה חושבת על כיוון לטיים ליין
קווים מאונכים זה פעולות שמופיעות בעצמן באת ההקלטה - שבהם נתפס הסקריטשוט
קווים אופקיים - זה פעולות חיצוניות- שאפשר לערוך ולהוסיף גם בדיעבד

בעקרון אני שהאידיטור יהיה כמה שיותר נקי מהסחות ויהיה פשוט לתפעול

מחכה לתגובות?
כן הכיוון /לא הכיוון
אפשרי / לא אפשרי וכו׳
...

לילה טוב

[mushon]

If I understand it correctly we're looking at the bar graph at the bottom of the page and the text boxes on the top left are just an index for us, right?
I think this is a good start for addressing the depth of information and the relevant data but I must say I am missing something more simple and direct that does not have to rely so heavily on abstract visualization. I think you guys should look into video editor timelines, even simple ones and try to think what are the key "events". How are they represented through the recording? visually? (like scroll and new page) through interaction? (like a click or typing) What would be the best way to represent this timeline. I kinda think that thumbnails are essential. I would recommend creating hierarchy between the different events and data points and to design them accordingly.
Here are a few relevant references for you:
iMovie is Apple's video editor for the end user. It is very simple and straight forward.
Popcorn Maker - is Mozilla's editor for layering prerecorded video with web content
ScreenFlow - a great screencasting application. Consider their solutions for post production (after recording) tools and interfaces too.

There are many more which I'm sure you're familiar with some other examples, but try to consider using existing design patterns and extending them to meet your unique needs rather that completely reinventing the wheel.

@polinekes @eranaltay @goldido87 @yelmam Let me know if this is helpful and where you're at on other aspects of the development.

@yuvadm feel free to add if you see more pointers at this point.

[polinekes]

אוקי הבנתי את הכיוון

אתה חושב שעדיף יצור אייקונים/סמלים מזוהיים לכל event ולהשתמש בשכבות יותר מוכרות למשתמש
אני אחקור עוד את הנוסע ואעדכן

[polinekes]

VERSION 2 OF THE EXTENSION IS

• the timing, play/stop and status bar is uncompleted for now

[mushon]

@goldido87 @yelmam @eranaltay what do you guys think of this design?
We want to see you more active in the development and the discussion of the extension.

[goldido87]

This is a sample of how commands are stacked on the extension's popup window.
This is a temporary design, we need to think of a design that suits this kind of window.
The reason is because the extension won't let us put the window at the bottom.

• In terms of functionality, currently when you stop the recording, a new tab will open with the url worked on and will start to execute the commands made by the user.

[yuvadm]

@goldido87 you can use the devtools.panels API to integrate with the devtools window and add your extension there. It might not be the best place for it, but it will give you a better experience than the current location.

https://developer.chrome.com/extensions/devtools_panels

Alternatively, just build an HTML element with everything your extension needs to display on the screen, inject it to each page, and position it with something like:

div.easyguide {
    position: fixed;
    bottom: 0;
    width: 100%;
}

See a working example at http://jsfiddle.net/44Q3U/

@mushon do you know of a better way of splitting the screen like they need?

[mushon]

A sidebar panel is apparently not something supported in Chrome's extension API (it is supported in Firefox). There's some discussion about it here: https://code.google.com/p/chromium/issues/detail?id=319130

Dev tools might be the way to go, as there is a certain deviness to this extension. It would however direct you at a more techi audience and a more techi use of the tool. You could however still stick with the popup window or some other more elegant solution for the whole thing.

[polinekes]

[goldido87]

I think i'll go with the approach of the sidebar panel.
Thanks.

[goldido87]

Current design for now.

[yuvadm]

@goldido87 as a rough prototype, it's perfect! does it still have all the functionality? i.e. record starts a new recording, stop ends it and places it in the list for replay?

[goldido87]

Yes, recording is currently done by pressing the ALT + R keys and stopping by ALT + S. Stopping adds the recording in the list.
The actions made aren't currently displayed. We need to think about how to display them

[yuvadm]

@goldido87 fair enough, that should be the next main effort.