Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 3 days, 9 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 4 days, 4 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 6 days, 13 hrs ago - more...
 |
|
2011-08-19
, 11:26
|
|
Posts: 1,918 |
Thanked: 3,118 times |
Joined on Oct 2010
@ My pants
|
#2
|
Broken by ENVY 
Good job.
Good job.
__________________
[NITDroid] [My Qtlockscreen Skins] [QBW HTC Sense on Your N900!] [CPU Power Control] [Debian Packaging] [Build Me!]
Youtube Channel - Subscribe!
Retired Dev - Thanks for all the fish!
[NITDroid] [My Qtlockscreen Skins] [QBW HTC Sense on Your N900!] [CPU Power Control] [Debian Packaging] [Build Me!]
Youtube Channel - Subscribe!
Retired Dev - Thanks for all the fish!
| The Following User Says Thank You to ammyt For This Useful Post: | ||
|
|
2011-08-19
, 11:45
|
|
Posts: 1,100 |
Thanked: 2,797 times |
Joined on Apr 2011
@ Netherlands
|
#3
|
You've got yourself a N9 or N950? Lucky you 
Did it cost a lot of modifications to make the Maemo version work on Meego, of was it mainly a recompile? Or even a total redesign?
Well, I am still happy with the Maemo version...
Did it cost a lot of modifications to make the Maemo version work on Meego, of was it mainly a recompile? Or even a total redesign?
Well, I am still happy with the Maemo version...
| The Following User Says Thank You to ade For This Useful Post: | ||
|
|
2011-08-19
, 12:44
|
|
Posts: 239 |
Thanked: 194 times |
Joined on Jul 2010
@ Amsterdam
|
#4
|
Originally Posted by ade
You should be happy with the Maemo version
You've got yourself a N9 or N950? Lucky you
Did it cost a lot of modifications to make the Maemo version work on Meego, of was it mainly a recompile? Or even a total redesign?
Well, I am still happy with the Maemo version...
It's got more functions still .EasyList-Harmattan was a total rewrite, because the EasyList-Maemo was written with QWidgets and MeeGo doesn't support the skinning of QWidgets.
I could compile EasyList-Maemo and run it on MeeGo-Harmattan, but the app would look like a desktop app. Very ugly indeed.
EasyList-Harmattan is QML only. It runs quite fast to my suprise, but I still hate the fact that Meego-Harmattan doesn't support QWidgets.
But even if it did support QWidgets I would have to do some redesigning, because I wanted the app to look native. As you can see from the screenshots the app uses native icons to create that feel.
|
|
2011-08-19
, 12:54
|
|
Posts: 1,313 |
Thanked: 2,977 times |
Joined on Jun 2011
@ Finland
|
#5
|
Thank you! Exactly what I've been missing!
| The Following User Says Thank You to ajalkane For This Useful Post: | ||
|
|
2011-08-19
, 21:03
|
|
Posts: 239 |
Thanked: 194 times |
Joined on Jul 2010
@ Amsterdam
|
#6
|
EasyList 0.0.6 brings you a Paste option in the menu of the Edit page. This allows you to copy text from any other app and paste that into EasyList. The main benefit is when someone sends you a text message with for instance a shopping list. Then you can copy that message and directly paste it into EasyList. That way you can type less and do more!
But that's not all! This version now also has a Settings page. It allows you to set your preferred sorting method. It also allows you to set orientation locks to suit your own preference.
You can get it from the project page. Enjoy!
But that's not all! This version now also has a Settings page. It allows you to set your preferred sorting method. It also allows you to set orientation locks to suit your own preference.
You can get it from the project page. Enjoy!
|
|
2011-08-22
, 08:26
|
|
Posts: 341 |
Thanked: 607 times |
Joined on Dec 2008
|
#7
|
Very nice, I was hoping there would be a simple checklist like this soon (certainly beats using Notes for shopping).
I have a few suggestions though:
1) The arrows in the viewheader indicate a filter, viewheaders should not be used for menus (as in Fremantle), since there is a menu button in the lower right. Instead, I suggest that tapping the view header opens the list selection. Also, please show the name of the list in the viewheader, as I would find this far more useful than the application name.
2) This is minor, but I find the use of the term "selected" somewhat confusing. It made me wonder at first if there was a different way of selecting items, rather than checking/completing them. I would suggest "checked" instead.
3) The way you handle multiple lists is somewhat clever, but I find it terribly confusing. The only use case that is straight forward with it is the one of cloning lists, which I never need. On the other hand, the common tasks of creating a new blank list or renaming an existing list require multiple steps and are really not very intuitive.
I would suggest to just use the standard method used by other applications in Harmattan: A "+" button in the toolbar to add a new list, and rename (or delete) items via the context menu (long press on item). The input field can then be removed, and instead appear in a sheet when a list is added or renamed. It may seem crude, but I really think it's good enough and nothing fancy is needed.
Another advantage of doing it like this would be that you could switch immediately back to the list view when a list is selected. To delete multiple items, you can still keep the delete button in the task bar and make it work like the delete function in Contacts for example (it opens a sheet with a multiple selection list and Cancel/Delete buttons at the top).
I also do not like that lists just disappear, when they become empty.
I have a few suggestions though:
1) The arrows in the viewheader indicate a filter, viewheaders should not be used for menus (as in Fremantle), since there is a menu button in the lower right. Instead, I suggest that tapping the view header opens the list selection. Also, please show the name of the list in the viewheader, as I would find this far more useful than the application name.
2) This is minor, but I find the use of the term "selected" somewhat confusing. It made me wonder at first if there was a different way of selecting items, rather than checking/completing them. I would suggest "checked" instead.
3) The way you handle multiple lists is somewhat clever, but I find it terribly confusing. The only use case that is straight forward with it is the one of cloning lists, which I never need. On the other hand, the common tasks of creating a new blank list or renaming an existing list require multiple steps and are really not very intuitive.
I would suggest to just use the standard method used by other applications in Harmattan: A "+" button in the toolbar to add a new list, and rename (or delete) items via the context menu (long press on item). The input field can then be removed, and instead appear in a sheet when a list is added or renamed. It may seem crude, but I really think it's good enough and nothing fancy is needed.
Another advantage of doing it like this would be that you could switch immediately back to the list view when a list is selected. To delete multiple items, you can still keep the delete button in the task bar and make it work like the delete function in Contacts for example (it opens a sheet with a multiple selection list and Cancel/Delete buttons at the top).
I also do not like that lists just disappear, when they become empty.
| The Following User Says Thank You to kanishou For This Useful Post: | ||
|
|
2011-08-22
, 09:53
|
|
Posts: 239 |
Thanked: 194 times |
Joined on Jul 2010
@ Amsterdam
|
#8
|
First of all I'd like to thank you for your valid remarks.
Originally Posted by kanishou
De view header has been added because it has a functional aspect to it.
1) The arrows in the viewheader indicate a filter, viewheaders should not be used for menus (as in Fremantle), since there is a menu button in the lower right. Instead, I suggest that tapping the view header opens the list selection. Also, please show the name of the list in the viewheader, as I would find this far more useful than the application name.
- The most important one is to have a place where the user can click on when the Virtual Keyboard is opened in the Edit page.
- Second I find it very hard to recognize a minimized application in the open apps overview. Especially when it's zoomed out and there are 3 icons per line. There are some apps (E-mail, Contacts, Recent Calls and Facebook) which utilize a view header. And I must say that I prefer that. Just so I know which icon to click on when I want to re-open the app.
- Some of the mentioned apps use the same arrow icons to open a menu. So I think it's ok to use it as it is.
Originally Posted by kanishou
I agree with you on this point and I shall fix this in the next version.
2) This is minor, but I find the use of the term "selected" somewhat confusing. It made me wonder at first if there was a different way of selecting items, rather than checking/completing them. I would suggest "checked" instead.
Originally Posted by kanishou
I agree with you on this point as well and I will try to make improvements here.
3) The way you handle multiple lists is somewhat clever, but I find it terribly confusing. The only use case that is straight forward with it is the one of cloning lists, which I never need. On the other hand, the common tasks of creating a new blank list or renaming an existing list require multiple steps and are really not very intuitive.
I would suggest to just use the standard method used by other applications in Harmattan: A "+" button in the toolbar to add a new list, and rename (or delete) items via the context menu (long press on item). The input field can then be removed, and instead appear in a sheet when a list is added or renamed. It may seem crude, but I really think it's good enough and nothing fancy is needed.
Another advantage of doing it like this would be that you could switch immediately back to the list view when a list is selected. To delete multiple items, you can still keep the delete button in the task bar and make it work like the delete function in Contacts for example (it opens a sheet with a multiple selection list and Cancel/Delete buttons at the top).
I also do not like that lists just disappear, when they become empty.
|
|
2011-08-22
, 10:47
|
|
Posts: 341 |
Thanked: 607 times |
Joined on Dec 2008
|
#9
|
Cool, thanks. Regarding the view headers:
First, I am not suggesting that you remove it completely. Having it there for recognizability of the app in the overview is okay (that's what it's meant for). But if you make it a popup, it should not open the normal menu. View headers with arrows are supposed to be "filters", I will explain soon what that means exactly.
This is not necessary. Instead the edit view should be a sheet, because then the "Done" and "Cancel" buttons are available at the top where they are not hidden (that's a main reason why the sheet widget was made). Copy and paste don't require the menu, as those functions can be accessed from the popups in the text edit.
Those apps use the view header as a "filter", as mentioned above. What this means is that you can switch between a set of modes (or filters), and the active filter is displayed in the view header.
So in case of Recent calls for example, clicking it opens a popup with different filters, and if you select "Missed calls", this will now be displayed in the title.
The Facebook app is a bit unusual, but it's a similar concept. If you click it you get a list of "modes", and if you e.g. select the "Photos" mode, the viewheader will now read "Photos".
This is why I suggested that you make the viewheader's function to switch between the different lists, and show the active list in the viewheader. The easiest way to do this would be to just show the lists edit view when you click the header, and then you can also remove the respective button from the toolbar.
A few more little things: There is no need for a disabled back button in the first view, you can just remove it and only display it when it's needed. And I would suggest to disable the delete button when no item is checked. Finally, the delete query text is a bit redundant, so I suggest to remove the detail text and just leave the title (so instead of "Remove selected items? Do you really want to remove all selected items?" it will just read "Remove selected items?"). That's acceptable, no need to have a body text just because we can.
First, I am not suggesting that you remove it completely. Having it there for recognizability of the app in the overview is okay (that's what it's meant for). But if you make it a popup, it should not open the normal menu. View headers with arrows are supposed to be "filters", I will explain soon what that means exactly.
The most important one is to have a place where the user can click on when the Virtual Keyboard is opened in the Edit page.
Some of the mentioned apps use the same arrow icons to open a menu. So I think it's ok to use it as it is.
So in case of Recent calls for example, clicking it opens a popup with different filters, and if you select "Missed calls", this will now be displayed in the title.
The Facebook app is a bit unusual, but it's a similar concept. If you click it you get a list of "modes", and if you e.g. select the "Photos" mode, the viewheader will now read "Photos".
This is why I suggested that you make the viewheader's function to switch between the different lists, and show the active list in the viewheader. The easiest way to do this would be to just show the lists edit view when you click the header, and then you can also remove the respective button from the toolbar.
A few more little things: There is no need for a disabled back button in the first view, you can just remove it and only display it when it's needed. And I would suggest to disable the delete button when no item is checked. Finally, the delete query text is a bit redundant, so I suggest to remove the detail text and just leave the title (so instead of "Remove selected items? Do you really want to remove all selected items?" it will just read "Remove selected items?"). That's acceptable, no need to have a body text just because we can.
| The Following User Says Thank You to kanishou For This Useful Post: | ||
|
|
2011-08-22
, 11:31
|
|
Posts: 239 |
Thanked: 194 times |
Joined on Jul 2010
@ Amsterdam
|
#10
|
Originally Posted by kanishou
Ah cool, I didn't know about that. I will try to implement it in the next version.
This is not necessary. Instead the edit view should be a sheet, because then the "Done" and "Cancel" buttons are available at the top where they are not hidden (that's a main reason why the sheet widget was made). Copy and paste don't require the menu, as those functions can be accessed from the popups in the text edit.
However I've found the Paste popup button to not work when I've copied something from another application. Hence the Paste button in the Menu.
Originally Posted by kanishou
Thanks for the explanation. I now know what you mean.
Those apps use the view header as a "filter", as mentioned above. What this means is that you can switch between a set of modes (or filters), and the active filter is displayed in the view header.
So in case of Recent calls for example, clicking it opens a popup with different filters, and if you select "Missed calls", this will now be displayed in the title.
The Facebook app is a bit unusual, but it's a similar concept. If you click it you get a list of "modes", and if you e.g. select the "Photos" mode, the viewheader will now read "Photos".
This is why I suggested that you make the viewheader's function to switch between the different lists, and show the active list in the viewheader. The easiest way to do this would be to just show the lists edit view when you click the header, and then you can also remove the respective button from the toolbar.
Originally Posted by kanishou
About the disabled back button. It's there for uniformity. I put the back button on the same spot on every page so the user always knows that that's the location for the back button and nothing else. But the disabled delete button is a good idea.
A few more little things: There is no need for a disabled back button in the first view, you can just remove it and only display it when it's needed. And I would suggest to disable the delete button when no item is checked.
Originally Posted by kanishou
I thought that I've read somewhere in Harmattan-MeeGo guidelines that a message box must have a title. That's why I've put it there.
Finally, the delete query text is a bit redundant, so I suggest to remove the detail text and just leave the title (so instead of "Remove selected items? Do you really want to remove all selected items?" it will just read "Remove selected items?"). That's acceptable, no need to have a body text just because we can.
Thanks for the comments. You've given me a lot to work with. I hope I'll find some time soon to improve the EasyList.
Here are some screenshots:
Video by MeegoExperts:
- version 0.0.5 - Video review
EasyList PHP website:
The PHP code is now attached in the zip file. The ZIP file includes all the PHP files and a SQL file which creates two empty tables: lists and users.
Please give or donate your 2 cents to help me keep on going.
Last edited by Willem Liu; 2013-10-07 at 12:53.