These are chat archives for directus/directus

24th
Nov 2016
doughnet
@doughnet
Nov 24 2016 00:53
any update yet on the new version?
was hoping to try it out this weekend.
Ben Haynes
@benhaynes
Nov 24 2016 03:07
@doughnet – The new API/SDK version, or the new visual direction?
The API/SDK is still in development (close to be completed) but available on the one of the development branches (we can chat about setup over Slack if you'd like). The new visual direction is still just front-end templates – but I can provide a link if you'd like to see/comment on them. The goal is to publish those next week so we can get feedback from the community before integrating.
doughnet
@doughnet
Nov 24 2016 04:08
hmmm ... Xmas came early? ... interested in the API actually but I can wait for stable release though.
sorry; first time using gitter ... forgot to @benhaynes
but also excited to see the front end too ... ugh so many options!
Ben Haynes
@benhaynes
Nov 24 2016 05:30
@doughnet – here's your sneak peek!
Again, anything here can change still, it's just a static mockup of the templates... but we're going to use it to get community feedback in about a week
We're super excited about the new API and PHP/Node SDKs... as with anything, it's a balance of releasing sooner with more potential for issues, or extending the dev time to get something perfect. But, soon! We're working as efficiently as we can! :fire:
doughnet
@doughnet
Nov 24 2016 17:31
@benhaynes thank you for the link. it looks real awesome!
I forgot to ask as well ... in some screenshots of the existing Directus UI there is an "Activity" link on the left side (on the admin page) ... the installations I did don't have that. Is that a setting/configuration to enable that?
also, happy thanksgiving to all!
doughnet
@doughnet
Nov 24 2016 18:04
a couple suggestions: have a way to add specific data to a field based upon the user (for example if using it as a CMS backend, have a hidden field that will fill in the clientID or similar based on the person adding a new field).
also; have a way for tables to list only entries/rows that are for that user ... same scenario as above for a CMS backend, have a blog table which maybe 100 clients would use, have that client only view/add/edit/delete their own entries/rows
this may be very specific to my needs ... but would help maybe in general for someone wanting to have multiple users/purposes with few tables (instead of a blog table for every 100x clients ... all 100x clients share the same table but only view theirs)