-
Notifications
You must be signed in to change notification settings - Fork 19
Conversation
…uery library that nicely resize form. I Also created a basic template for listing posts - html content is only temporary and it will be replaced with javascript generated content
Please merge with main repository. |
border: none; | ||
outline: none; | ||
resize: none; | ||
font-family: Verdana, Arial, Helvetica, sans-serif; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No spaces between commas?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed that line, we don't need different font for the textarea...
OK, I don't know how to comment on this. Yes, it looks good. But it is a bit messy. Maybe first let us get all features in and then clean the code, no? So we need post updates to all clients connected to the page. This is still missing. Otherwise it looks nice. |
But you really have to update to latest version. It also uses newer version of our tastypie library with many bugfixes. |
function generate_post_html(data) { | ||
var li = $('<li/>').prop(); | ||
|
||
return '<li class="post"><span class="author">'+ data.author['username'] + '</span><p class="content">' + data.message + '</p><span class="date">'+ format_post_date(data.created_time) +'</span></li>' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Create HTML elements through jQuery.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, done.
Just to make sure, I am waiting for you here, no? |
So the dates work for you now? Do you know what was wrong? Why you had problems with them? |
The translations for dates and time diff calculations are now working fine. Translations started working after merging with upstream so I'm not sure what exactly was the problem. |
In which way translations didn't work for you? So the only problem I noticed (after you did translations right) was that because of timezones, calculated delta was always negative between current time and post time, so "right now" was always displayed. (Probably you had some other time-span displayed, so some other time offset, because you are in the other timezone.) So when you write "does not work", you should explain how it does not work for you. |
Yes I also noticed the problem with timezones and I fixed it. The other problem was that I wasn't getting Slovenian translations for "days, hours, minutes". Maybe it was cache. I don't know anymore. |
It looks good now. I am still missing that you open tickets and pull requests. :-) |
delete_link | ||
); | ||
|
||
var post = $('<li/>') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Better, but a bit too much now. :-0
var post = $('<li/>').addClass('post').data('post', self).append(
post_options
).append(
$('<span/>').addClass('author').text(self.author.username)
).append(
$('<p/>').addClass('content').text(self.message)
).append(
$('<span/>').addClass('date').text(formatPostDate(self.created_time))
);
So, do you remember which tickets we talked to open? Because I don't. :-) |
Let me check. |
You can open tickets for important TODOs so that your colleagues can easier find it. Maybe just the one for dates. |
Hmm I made a pull request for tastypie and now also all your and my comments appeared there? Didn't think of that. Should I delete them or is it okay to leave them? |
I don't see them. |
OK. I see them. He he. Leave. :-) |
Where are other pull requests? |
Please link them all here. |
Ticket: Pull requests: |
Good job! |
See changes I did after merge. |
Oh. Was this pull request a hidden mine. It is not good to just so upgrade dependencies to newest versions (and even unreleased ones). Things completely broke. Which would be quite obvious if would run the tests. Or, if you would run the tests. Even if we do not have many of them, they fail loudly. |
Hmmm where exactly is the problem? Forgot about tests... :/ |
I fixed the problem by reverting to older versions. But simply, mongoengine in newer versions works a bit differently, so things fail. And tastypie changed API, so things fail fast and REST protocol do not work for subresources (like comments, attachments). So the problem is when you change requirements, then you have to test if everything still works. This is why we have concrete versions hard-coded. For all modules. |
Uhh that's not good. I'm sorry about that, I completely forgot about the tests, will know better next time. But this will have to be fixed once or we'll just stick to this versions forever? |
I have also forgot about tests. This is why I have now integrated the repository with Travis CI. It will check automatically every time. Yes, we will have to fix it. But this can be a ticket or another branch/pull request, not that we have broken code and everything does not work anymore in master, where others are working on it. |
The most basic wall with input box and post listing. Not finished yet but so that you can see we are moving forward. Ideas welcome. :)