Where is the entry point?

[Pokerface]

I try to run this project, but where is the entry point? (main)

[Ian Clarke]

We're working on that and we're still a few weeks away from the point where Tahrir is useable.  Ravi is our full-time Google Summer of Code student and his goal is to get an alpha out ASAP.

For now tahrir.ui.GUITest will launch the GUI.

Ravi's initial focus is a Desktop GUI but the next highest priority will be to get Tahrir working on Android.  If you're interested in helping let us know!

Ian.

On Sun, Jun 16, 2013 at 6:44 AM, Pokerface <kev...@gmail.com> wrote:

I try to run this project, but where is the entry point? (main)

--
You received this message because you are subscribed to the Google Groups "Tahrir Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tahrir-developm...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Ian Clarke

Blog: http://blog.locut.us/

[Kevin Wang]

I am a student as well and I will help.  I have some experience on Java.  I have read the Wiki.  Please let me know where to start.

----------------------------------

Yours sincerely,

Kevin Wang

[Ian Clarke]

Take a look at the open issue list: https://github.com/sanity/tahrir/issues?sort=updated&state=open

Some of these are quite complicated, but others should be simple enough.

Do you have any experience writing Android apps - or would you like some?

Ian.

[Kevin Wang]

Not much.  I can do that.

----------------------------------

Yours sincerely,

Kevin Wang

[Ian Clarke]

Ok.  Note that we've more-or-less standardized on IntelliJ IDEA as an IDE, and I believe it is the basis for Google's Android IDE also.  You might find it most convenient to use this IDE also if you can.

Our philosophy with UIs is to stick as closely as possible to what people are likely to expect, which means looking closely at how Twitter, Path, Google Plus, and other microblogging UIs work and emulating that whenever possible.

Ian.

[Kevin Wang]

I will use Google's Android IDE maybe

​, as I already have on installed on my PC​

.

I believe using Web View technology

​could be​

 the best way to keep correspondence to Twitter or other We

​b page ​based service on Android.  Have you already started working on any Android version?  Or I need to create a new Android project myself?

[Ian Clarke]

Kevin,

We have not yet done any work on an Android version.

I think there are (at least) two options:

1. We create an Android entry point in the existing codebase, which would co-exist with the Swing GUI and the command line interface.

2. We create a separate project for the Android app, and include the first project as a Maven dependency.

The second option would probably be easier to get started immediately, but it would mean that we'd need to deploy Tahrir to a public Maven repository, and ensure that it stays in sync.

Thoughts?

Ian.

[Kevin Wang]

I prefer the second one.  Android package have different Android dependencies, merging with desktop version will be quite confusion.  Plus, some resources such as Android Manifest file, Android layout xml files will make the main code base a mess, considering the desktop version and mobile version don't have much in common despite of the majoy library.

Some codes, in my view, may be translated to native code (C / C++) regarding the performance of Android at a later time.  We want our app staying at the background, while does not exhaust the battery too soon.  That may need us do some modification with JNI (or maybe we can do this to the desktop version as well?).

So if we want our mobile version be more flexible, I suggest we create a separate project for Android.  With git we may create a new branch as shared library, then one branch for desktop and one branch for Android, then merge them locally.  I don't think we necessarily need Maven

----------------------------------

Yours sincerely,

Kevin Wang

[Ian Clarke]

On Sun, Jun 16, 2013 at 1:06 PM, Kevin Wang <kev...@gmail.com> wrote:

I prefer the second one.  Android package have different Android dependencies, merging with desktop version will be quite confusion.  Plus, some resources such as Android Manifest file, Android layout xml files will make the main code base a mess, considering the desktop version and mobile version don't have much in common despite of the majoy library.

Yes, I think the second one probably makes more sense.

 

Some codes, in my view, may be translated to native code (C / C++) regarding the performance of Android at a later time.  We want our app staying at the background, while does not exhaust the battery too soon.  That may need us do some modification with JNI (or maybe we can do this to the desktop version as well?).

Perhaps, although nothing Tahrir does should be particularly CPU intensive, so hopefully it won't be necessary - since native code will significantly complicate things.

 

So if we want our mobile version be more flexible, I suggest we create a separate project for Android.  With git we may create a new branch as shared library, then one branch for desktop and one branch for Android, then merge them locally

I don't think we should use different Git branches, these are intended for different versions of the same codebase, not totally separate codebases.

I have created a new repository here: https://github.com/sanity/tahrir-android - what is your github username?  I can add you as a collaborator.

I don't think we necessarily need Maven

I think we should use Maven since we are using it for the main Tahrir codebase, and since most modern Java projects use it for dependency management, and since there is an Android plugin for it.

Ian.

[Kevin Wang]

My github is kevinxw

I will create an Android project then. Please tell me after the Maven
repo is ready.

> --
> You received this message because you are subscribed to the Google Groups
> "Tahrir Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tahrir-developm...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>


--

[Ian Clarke]

Sorry about the delay, you're added to the project now: https://github.com/sanity/tahrir-android/settings/collaboration

You should take a look at this: https://code.google.com/p/maven-android-archetype/

Ian.

[Kevin Wang]

The maven android archetype seems like somehow obsolete.  Can I use another Maven plugin?

I find this after a little research:

https://code.google.com/p/maven-android-plugin/

----------------------------------

Yours sincerely,

Kevin Wang

[Ian Clarke]

Of course, whatever is best.