Do you happen to know whether a simple table cell can contain an object (mention of a page) or is it just plain text?
I believe it is just plain text for now! (so, like, really simple tables )
Math calculations and formulas arent even confirmed requests? why so? this is such an important feature, only reason i still use notion is becoz of the databases and i really wanna shift entirely to anytype, but mention of database even for consideration is nowhere to be seen
Features are coming step by step and if enough users would like to see them.
weird how many people dont find the need of math calculations in sets, coz it acts like a database but really aint getting a lot outa it coz of absence of calculations
Thanks for the input. We do understand that databases are a much desired feature, and that they are also something unique from both sets and tables. First our team needs to complete a bit of validation on which database functions are the most desired and why - is it just formulas? Or pivots and charts and…? How in general do people wish to manage multiple Objects in one view? And when considering database functionalities, at what point do we draw the line between productivity/knowledge management tool versus data management tool? (I’m not questioning the eventual necessity of formulas as I want to use them as well - just wanted to share what some of the internal discourse looks like when we consider various features. This kind of deliberation does come at a time cost, but we do so to try to maintain a level of product coherence.)
Second stage will be a bit of decision-making on where to contain these functions. Sets would seem like the more natural choice here (compared with Tables), however this would likely only come in the next iteration of Sets when we would add more flexibility.
TLDR: Rest assured that formulas are taken into account - once we have a better idea of where and how to fit them into the roadmap, we will confirm on dates
Thanks for the response! Glad its atleast considered, i know that anytypes take on databse is gonna be different as from what i have heard, but wasnt included in the confirmed feature requests, thus i was skeptical, confirmed feature requests i guess probably takes into account the features that are gonna be more or less features that would be released in aplha releases and would be in the public release of which the ETA has been given as 6 months, so according to yalls take on databases, i see it would be difficult for yall to include just temporary simple sum and average of values like formulas to sets as of now as yall are gonna change a bit of stuffs in sets as wel… Best wishes to yall, hope for a quality product
@Charlotte Will it be possible to copy and paste tables from anytype into Word? Afaik this works with Notion.
they can contain markup with mentions and links
it is possible already
Cool, even while retaining the table structure? That‘s awesome .
The sprint notes should be posted today, if I’m reading this right?
That’s the plan. We are waiting for some last info from the team before the notes go public.
But when I read the sprint review 37 it says that the features in these sprint reviews have NO specific time of release. Meaning kanban view is not promised for the release aimed a august 1.
This this comment makes me believe that everything in the sprint review IS coming in the release of august 1 (incl. kanban view, simple tables, underline text and multiple windows).
Hi @Jeroen thanks for mentioning this! In sprint review 37 a lot of cool stuff was shared and demoed without a target release date, but in sprint review 38 just the stuff that is about to be released with the 1-Aug release was presented. This might have had the unwanted effect that it is no longer clear for the reader what information is relevant for which moment/release.
I will need to reread the sprint review notes to make sure it is clear what is and what is not to be expected based on the sprint review meeting notes.
Thanks for the reply!
It can also have an unwanted effect that people see these sprint reviews as promises for next release and be disappointed that the stuff from a sprint review isn’t in the next release.
I really like the more open appraoch when it comes to these sprint reviews and other topics in the last few days/weeks but it can be a bit unclear what is going to be in the next release.
But I don’t really have a solution how to fix that hehe.
It’s also part of human nature to wish for the most (see game development of alpha games that face the same challenges as Anytype when it comes to releases and communication).
@Jeroen I appreciate the feedback and I indeed, a sudden move towards much more transparency could be mistaken for lots of promises instead of just sharing the current state of affairs. It should help to explicitly mention how people should take the information shared in these topics or any topic for that matter.
Again, I’m happy you took the time to share your thoughts on this, as I wouldn’t have known this was a side effect of sharing these meeting notes!
Edit: @Jeroen does the text added in the “Note” paragraph cover your concern(s)? For subsequent sprint review meeting notes I’m planning on a shortened version of that paragraph
I think it does yes.
A short version could be:
Please take note, these are not the release notes for next update. For the next release notes check [link to topic’]
In the next release notes topic there could be a disclaimer saying these notes are subject to change or something simular.