spazproject / spaz-enyo Goto Github PK

^^^

This changes the state of the posting panel a bit, because the message doesn't need to be prefixed with a username, but we must store whom it's directed at. See the current Mojo version of Spaz for reference.

Note that which account we are sending from may be limited based on the service. A user we are messaging may not be from the service we last posted from! Options for which account to post from need to be limited by service.

Custom bit.ly, etc.

Do that.

Needs to do the following:

• create, edit, delete accounts

Accounts have the following data associated with them:

• Service (Twitter, Identi.ca, StatusNet/Custom)
• username
• password

That's it for now.

I'm wondering if a global refresh button might be a good idea. Probably in the left sidebar. Thoughts?

We should differentiate mentions and dms somehow; perhaps with a colored gradient in the bg. Open to suggestions.

We need an approach that allows paging back through older messages.

Emulating Twitterrific seems like a good idea,

• only the DMs and replies between the newest and oldest currently shown items from the Home timeline are shown
• If more are loaded, they can appear in other columns, and will appear in unified timeline as the user pages back
• users interested in much older @mentions or DMs can use the specific columns for those respective types

I'd go initially for a button at the bottom of the entries. Not sure how gestures will work out.

We need a simple model to handle adding, deleting, loading and saving the column data.

Properly they should be in a background service, ala mojo. That will suck.

as a hack, we skip a bg service and just use a setTimeout(). This could suck though.

Maybe just ignore it for now. Get other stuff in place first.

what it says up there

This is super annoying and makes it fairly difficult to get out of the popup.

We may or may not want to have the popup re-open when clicking on a different tweet.

For now, just pull the Twitter public timeline data into a timeline, so we have something there

Twitter API RTs are funky in that they have a whole separate status object just for the full retweeted message. If you don't use that, you can lose some chars due to the 140char limit imposed. So, we need to do a little work to display them correctly.

We need a new preferences icon. The current one looks crappy. A gear would probably be best.

This should fire something, probably just a "refresh" method on the column object

^^^

If you open up the entry view with 4 columns, scroll all the way to the right, and then remove the entry view, you won't be able to scroll back to get all 4 columns in view. It'll be stuck.

Note that which account we are replying from may be limited based on the service. A message we are replying to may not be from the service we last posted from! Options for which account to post from need to be limited by service.

It would be pretty awesome if we could get the mouse scroll events to scroll columns.

We need to not render anything until the preferences load. How to we delay this?

We need to wire this up. We also should prompt the user before deleting.

This may require some mock data stuff within chrome, as direct file uploads are not normally available in the browser environment

We need this to distinguish mentions from regular tweets in the Entry.js tweet. It would be easiest to have this a part of the Entry conversion process.

How do we handle loading older data into the timeline? Need to handle different types of columns differently. Logic for handling this needs to be written.

When we send, we need to:

• Disable compose/post controls
• show some sort of spinner
• be able to display an error and de-enable controls

Not sure exactly how to accomplish this, but I think it's important to be able to do.

"Enter Posts": true
"Default Column Width": "322px"

Add any preferences here that should be incorporated.

Do it.

We need to be able to delete accounts from the account manager.

Tibfib should make a UI, I can wire up.

I think we should support the subset of column types shared by our initial services. I'd think these are:

• Home timeline
• Replies/Mentions
• DMs
• Searches

If time allows, I would also include

• Unified (Home + Mentions + DMs)

We need to show what account a column is associated with somehow. Pehaps a subtitle-type thing in the header with the account label?

Should be part of each column.

Since it uses "flex" there is no set width making our "truncating-text" class not work.

We could probably do something by getting the width of the account label and subtracting that from a width and then hard-coding it in on create.

Popup.openAroundControl is smart enough to position your popup so it is completely onscreen, but Popup.openAtEvent is not. So if you tap on the right-most column, the items in the popup can be truncated or even completely obscured.

API RT

Waits on mockup of UI.

Needs to do the following:

• create, edit, delete accounts

Accounts have the following data associated with them:

• Service (Twitter, Identi.ca, StatusNet/Custom)
• username
• password

That's it for now.

My thinking is that we shoot for what we do now:

• Twitter
• Identi.ca
• StatusNet/Custom Twitter-compatible API

When viewing a message and expanding a long conversation, selecting a new tweet will update the message detail but not reset.

DB8?

Also, if we go DB8, we could get Just Type searching going too.

Possible something with Synergy.

Possibly Activity Stream format, but this may be overly complex for our purposes. Also, should still have access to original data structure.

Advantage here would be not having to juggle different formats when displaying in columns and detail views.