-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rearrange pages manually #32
Comments
This is a missing feature, at the moment you can only drag pages to another sub-section of the notebook, but they remain sorted alphabetically per section. |
Hi Jaap, I can see the utility of a random reordering of the pages in the tree view. But would it please be possible to keep the default automatic alphabetical ordering? I think it makes sense for the default tree view to have everything sorted alphabetical. Maybe have a different tree view then which allows for reordering or make it a selectable option. Remember please: The beauty of Zim is that it is simple. Don't overload it with functions. |
please let me know, when it will be deployed? |
Yes. Please let us know. I am currently seeking for another solution, only because missing this feature. But other solutions are not so cool as zim. I see only tomboy (ugly), basket (buggy), wikidpad (for win), etc. Don't know what to do. Please implement this feature, on a 100+ pages notebook it is required... |
I'm in the same boat as @UralZima here. I really appreciate Zim but I need to be able to sort manually the different pages! |
same here, would be great to see this implemented. |
+1 - I just installed tonight and like it so far, but would love it (and prefer it) if an "order by" (Alphabetical or Manual) option existed. |
Funny, I have been very happily using zim for quite a few years now. Until today I did not notice that re-ordering of pages is not possible. But today I decided that zim provided the simplest, quickest way to build a genealogy website. Now I need page re-ordering - because children should be listed in order of their age, not their names! So this new functionality will be very useful in this case. In the meantime I have found a workaround (which may prove to be tedious) - the list items which form the index can be manually rearranged inside the html file after building the site with zim. |
+1 on this. I just installed Zim 0.69.1 on Mac OS (after using it for years on Linux and Windows) and just noticed that in MacOS the alphabetical order is no longer maintained for some reason, it actually seems random: Trying to workaround this problem I tried manual re-ordering only to find it's not supported |
Been using Zim for many many years. I don't need this often, but when I do I just start the name with a fixed-length number. I've found that it's always best to have 1 leading zero more than you think you'll ever need in order to both insure correct sorting, as well as avoiding lots renumbering and re-linking in the future. |
Thanks @DocSalvager |
Any progress on this feature? |
Still waiting for this feature a lot. I tried CherryTree, which allows that, but it is working ugly, not so cool as Zim. Please implement this feature, much people need it! it is so easy to implement. Even if code will be dirty, let it work. |
+1 +1 :) |
ps - cherrytree is pretty cool! - long time user |
+1 for this feature request. I really miss this feature because I have pages with many sub-pages, of which not all are equally frequently used. I would like the more frequently used ones at the top of the list. I imagine this as:
|
Is there any update on this? :) |
Are we still not able to rearrange pages manually? |
+1 |
Just wanted to add to this request. The usefulness of this very much depends on how you organise your content I guess. I use a fairly detailed tree structure to break down my notes, and have relatively few files in each folder. I use Zim a lot for outlining and researching writing projects, and ideas for novels. I have written my own application for the actual writing, where you definitely need to be able to sort scene files manually, but Zim is still my main research and note tool. It would still be useful to be able to sort my notes following the structure of my projects without having to prefix each folder with numbers. In any case, in terms of functionality, I proposal something similar to how Firefox and Chrome handles bookmarks. I.e. you can have them unordered as (an optional) default, and right click a folder to have Zim order them alphabetically. Edit: Basically the same proposal as @aNDy-Squirrel |
I am numbering pages to sort it manually for now and maybe a workaround you can use too |
+1 from me too! I think this is a basic requirement for many work-flows, and adding numbers to page titles is as inelegant as it gets. I have a lot of pages and sub-page and sub-sub-pages. Adding numbers would make things very messy. Could something not be injected into the metadata/frontmatter of the files? Cheers |
Another +1 for this feature. Like others, I use numeric prefixes to force my desired order but I'd prefer not to have to. The ability to drag'n'drop in the tree to change order or parent of a node would be great. CherryTree seems to get this right (though I'm sticking with Zim!) |
May be use hidden sort-number in Zim-notes file-name for this? Note: "My Note" |
It seems like you're suggesting that I can rename the file on disk using the numeric prefix and get the desired order without the prefixes displaying in the tree, please let me know if I have misunderstood?
Whilst it's not a show-stopping issue I think my Zim experience would be improved by the addition of this feature. |
You are confusing capability and interface, it seems to me. |
Ah, thanks for the clarification. Your suggestion was for the developer, not the end-user? |
+1 for this. I get why this is not so easy to implement: trees are folders, and file managers usually do folders that can sort files in some order (alphabetical, edit date) NOT manual. I have yet to find a file manager that allows manual ordering. For a beautiful implementation of this infinite tree, see quire.io. I agree this is a fantastic feature to have |
Whilst, in principle, I like the idea of tree nodes mapping directly to folders on disk, the reality is I've never accessed my Zim notes from outside of Zim in > 10 years usage so I would happily forego that mapping in favour of a manually sortable tree.
see also checkvist.com |
Reordering ++ |
The filesystem mapping is fantastic to have version controlled notes. This
trumps everything else for me
…On Fri, Feb 19, 2021 at 12:09 PM martinkirk ***@***.***> wrote:
+1 for this. I get why this is not so easy to implement: trees are
folders, and file managers usually do folders that can sort files in some
order (alphabetical, edit date) NOT manual. I have yet to find a file
manager that allows manual ordering.
Whilst, in principle, I like the idea of tree nodes mapping directly to
folders on disk, the reality is I've never accessed my Zim notes from
outside of Zim in > 10 years usage so I would happily forego that mapping
in favour of a manually sortable tree.
For a beautiful implementation of this infinite tree, see quire.io.
see also checkvist.com
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABMPP2ID6SW3RDI4NA7BRLS7ZBGLANCNFSM4DLAIJCQ>
.
|
Proposed Fixes would have to be Related to #1442 |
+1. I have just started using this for taking notes, and 7 pages in, and i am already feeling the lack of manual reordering bite me in the back. |
+1 |
I just registered to say that I would Love if it was possible to just drag and drop rearrange the order of pages. Love! |
I don't understand; Is it such a difficult task to add such a simple functionality to Zim?! |
I'd love to have this feature as well. |
Another +1 for this. Seems like a basic feature what would be very helpful for organization. |
As an external person very very interested in Zim having this feature, I was hoping there was a central place where this might be hacked in. I was thinking as a data structure just a simple file on disk page_index_order.txt with a list of file names in the order that they were dragged into. This file would only appear in folders once pages had been dragged out of filesystem order. Obviously, this file would have to be kept in sync / rewritten when renames, page creation, deletion, dragging occured. I was looking at the code to see if I could identify if there are points this idea could be wedged in, and it looks quite daunting -- primarily because the page index code: Edit: looks like the file https://github.com/zim-desktop-wiki/zim-desktop-wiki/blob/develop/zim/notebook/index/files.py has most of the filesystem logic that would need a proxy version of if we wanted to allow reordering. |
Actually you don't have to look into the GTK and UI code. The ordering is
taken from the SQLite table in the index. If the table changes, and the
proper signals are emitted, the TreeView follows.
Key design question is how to store the index. The SQLite table is
considered a cache, so there needs to be a file in the notebook folder that
keeps the index. There needs to be API calls on the Notebook object to
manage this storage and update the index.
Then you have the UI actions for actually reorganizing the index which need
to connect to the Notebook API.
Regards,
Jaap
Op di 30 jan. 2024 21:48 schreef yareckon ***@***.***>:
… As an external person very very interested in Zim having this feature, I
was hoping there was a central place where this might be hacked in. I was
thinking as a data structure just a simple file on disk
page_index_order.txt with a list of file names in the order that they were
dragged into. This file would only appear in folders once pages had been
dragged out of filesystem order. Obviously, this file would have to be kept
in sync / rewritten when renames, page creation, deletion, dragging occured.
I was looking at the code to see if I could identify if there are points
this idea could be wedged in, and it looks quite daunting -- primarily
because the page index code:
https://github.com/zim-desktop-wiki/zim-desktop-wiki/blob/develop/zim/plugins/pageindex/__init__.py
is wrapped around a gtk structure
https://docs.gtk.org/gtk3/struct.TreePath.html, and one would have to
understand both to see where to wedge in the ordering code. One related
point is that TreePath is deprecated in GTK 4.10+ so in 10 years if zim
gets ported to that, there will have to be a new solution anyway. I will
take a look at trying to understand the zim side of the code in case there
is a way to hack page ordering in with my limited knowledge. If this is
something the main developers have an opinion on, could give guidance on,
that would be awesome.
—
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJQYHRIQHEQGT5XUVFKL3TYRFMDVAVCNFSM4DLAIJC2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJRG44DMOBRGE4Q>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
To keep with our theme of pages being files, we could store their order in the file names and strip the edit: see also #2015 re: moving and reorganizing |
I prefer some kind of plain text index file. If you use the file names,
each change would modify all files in the folder - which easily leads to
trouble in folders that are mirrored by cloud storage etc.
…--- Jaap
On Sat, Feb 3, 2024 at 8:38 PM introt ***@***.***> wrote:
To keep with our theme of pages being files, we could store their order in
the file names and strip the ^\d+_ in the UI. This'd be similar in spirit
to how we handle spaces & the file extension.
—
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJQYHV4SCM4YYKBNTQDUCDYR2GZVAVCNFSM4DLAIJC2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJSGU2DGNZYGE2A>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
Linking #2604, the index file could list the preferred order of UUIDs (which should be added while indexing if missing) |
Hello Jaap, everyone, I'm just starting to use the tool, and I would also very, very much need this functionality. With the aim to store in Zim all the structure of a website or a long document for export in Latex, I'd say it's essential if one doesn't want to forever keep updating numbers. One train of ideas:
Could that work? thanks in advance to consider it! best regards, Géraud |
Instead of a raw sequence number (which could require editing every sibling), we could do what TiddlyWiki does: list-before and list-after; see https://tiddlywiki.com/static/Order%2520of%2520Tagged%2520Tiddlers.html - this could use page UUIDs to be robust against filename changes and solve conflicts by some simple prioritization. |
Yes, I agree using an unique identifier per page would be a robust way to
handle it
This combined with an index file per folder in plain text, which gets
cached in the index tables.
…-- Jaap
Op zo 19 mei 2024 14:49 schreef introt ***@***.***>:
Instead of a raw sequence number (which could require editing every
sibling), we could do what TiddlyWiki does: list-before and list-after; see
https://tiddlywiki.com/static/Order%2520of%2520Tagged%2520Tiddlers.html -
this could use page UUIDs to be robust against filename changes and solve
conflicts by some simple prioritization.
—
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJQYHVGXKLDS3OTMZT32XDZDCNWRAVCNFSM4DLAIJC2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMJRHEZDENRXHE4A>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
Hello. I am using zim about 2 years, all is great, but I can't understand, it is missing feature or a bug.
When I try to move a page, holding mouse button it shows a line like it is going to move, but it is not moving/rearranging in right order.
I already adding numbers to order somehow, but I have 30 pages with max 70 subpages each, and I can't rearrange them in needed order with numbers only.
Please help me with this issue
The text was updated successfully, but these errors were encountered: