Re: andTweet infos

[Yuri Volkov]

Hi Paolo,

AndTweet may be extended for any needs, of course :-)

I see several areas of development here:

 

1. Creating another type of connection for this Diasaster mode. AndTweet already has two connection types, so addition of the third is no problem.

BTW, the Disaster connection Type may use any other network library... if it's necessary.

 

2. Creation of connectionType-independent message's (update's) queueing component, so Twitter updates | other commands (e.g. "Create favorite"...) may wait for delivery to the server for any amount of time.

 

3. Improving support of several User accounts: AndTweet already has different stores (different preferences files) for different User accounts but tweet's database is common yet. It should be extended so each user has his own subset of messages/tweets in the database.

 

...

 

--

Yuri Volkov

On Tue, Mar 22, 2011 at 13:57, Carta Paolo <pca...@student.ethz.ch> wrote:

Hello Guys,

My name Is Paolo and I am Master student at the ETH Zurich ( Switzerland) and I have just started with my thesis. The idea would be extending an existing open source twitter application with a disaster mode.

brief explanation of the work ( If you want you can skip it):
-----------------------------------------
When the user turns on the disaster mode, the application switches the WLAN interface to Ad-hoc mode and/or uses Bluetooth and starts advertising it’s presence by sending out beacon messages to the ad-hoc network.

Once a peer is discovered by its beacon messages, relevant updates are exchanged. Tweets are no longer sent to the Twitter server but stored locally, carried around as people move, and forwarded as they are in proximity. Until connection to Twitter is re-established, then all the updates are posted to the server.
--------------------------------------------

I have been surveying some apps and yours seems pretty handy. I had a look at the source code and it seems you just use the signpost library for OAuth and not some others like JTwitter or Twitter4J ( I might be wrong since I'm still a beginner with this topic).

Would you mind giving some hints to me? Do you think this kind of work might be feasible on your app?

I thank you in advance

Paolo Carta

PS: sorry if there are some english mistakes but it is not my native language !

[PaoloCarta]

Fair enough. I have seen the code has some comments as well, do you
think I can use some kind of documentation generator like javadoc or
Doxygen in order to get started ?
You know, in my thesis I need to start with a graphic scheme of the
application logic and perhaps I will have to use UML to do that. It
would be handy if you already had something like this.

PS: I have been thinking of joining the developers group as well since
likely I will work on this app for the thesis.

Cheers

Paolo Carta

[yvolk]

What's about documentation, existence of comments/explanations IMHO is
more
important than tools usage :-)
So my advice is to write comments/document the code as much as you
think is necessary. Personally I don't use any special tools yet e.g.
to automate "documentation generation" :-), but if these "reports" are
important for your format work procedures - go try them, of course,
from very start.

I didn't see any diagrams about AndTweet yet :-), but you may try to
draw some. Personally I think your work will benefit from BPMN
diagram(s) of application logic: starting from depicting people/
servers interactions and then (other diagram(s)) - deeper down to
AndTweet app objects interactions (maybe Activity (UI), User (user
account object), Queue, Service, Connection, Database, Tweet (as
data) ...).

This conceptual level diagrams/artefacts may be posted to this, wider
group. I think...

> > > language !- Hide quoted text -
>
> - Show quoted text -

[PaoloCarta]

Ok, so you did not use any documentation tool syntax for your
comments.

By the way why did you not use any standard libraries such as Jtwitter
or twitter4j ? I think it might simplify a bit the program .

[yvolk]

OAuth was implemented in Summer 2010.
As I remember I had no other
working options that time.

[Torgny Bjers]

The idea is also to rely on our own code instead of having a conglomeration of other code/libraries. What makes our code a bit more complicated is the support for multiple user accounts.

--
You received this message because you are subscribed to the Google Groups "AndTweet" group.
To post to this group, send email to andt...@googlegroups.com.
To unsubscribe from this group, send email to andtweet+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/andtweet?hl=en.