Reply
Thread Tools
hhedberg's Avatar
Posts: 84 | Thanked: 212 times | Joined on Nov 2007 @ Oulu, Finland
#31
Originally Posted by nwerneck View Post
Mauku is a great application, but i have to win the lottery before buying a N900/RX-51/Rover. If Mauku is being developed only for Fremantle now, what should us, the Diablo orphans do? Start a fork project? Wait to port it to mer?... Or perhaps compile curl to use ttytter?
Use the old Mauku version 0.6.2?

Mauku 2.0 is based on GTK+ and Hildon. There are only few widgets that are not available in Diablo (kinetic scrolling, for example, and I have implemented that already earlier). At least in theory it would be easy to port version 2.0 into Diablo also. However, I cannot promise that yet.

Another option would be to enhance the old Mauku to use the new Microfeed backend. Actually, version number 1.0 is reserved for that. Unfortunately I do not have enough time to make it happen (at least without help), but we are speaking open source software here.
 

The Following 3 Users Say Thank You to hhedberg For This Useful Post:
nwerneck's Avatar
Posts: 304 | Thanked: 233 times | Joined on Jul 2009 @ São Paulo, SP, Brasil
#32
Originally Posted by hhedberg View Post
Use the old Mauku version 0.6.2?

Mauku 2.0 is based on GTK+ and Hildon. There are only few widgets that are not available in Diablo (kinetic scrolling, for example, and I have implemented that already earlier). At least in theory it would be easy to port version 2.0 into Diablo also. However, I cannot promise that yet.

Another option would be to enhance the old Mauku to use the new Microfeed backend. Actually, version number 1.0 is reserved for that. Unfortunately I do not have enough time to make it happen (at least without help), but we are speaking open source software here.
I might help... But I'm just starting to learn how to program with Maemo.

What is the best way to make the development in parallel, so that features can be easily included both in the Fremantle and Diablo versions?...

Last edited by nwerneck; 2009-08-10 at 14:36.
 
Posts: 19 | Thanked: 5 times | Joined on Mar 2009 @ Monterrey, Mexico
#33
Where's this development happening?
I took a look at https://garage.maemo.org/plugins/scm...hp/?root=mauku and there's no Mauku 2.0 to be seen.
 
hhedberg's Avatar
Posts: 84 | Thanked: 212 times | Joined on Nov 2007 @ Oulu, Finland
#34
Originally Posted by nwerneck View Post
What is the best way to make the development in parallel, so that features can be easily included both in the Fremantle and Diablo versions?...
In that case it would be easiest to either port the Fremantle version into Diablo or switch the backend code of the Diablo version to utilize the new Microfeed library. In both cases at least the same providers for network services can be used without any further efforts.
 
hhedberg's Avatar
Posts: 84 | Thanked: 212 times | Joined on Nov 2007 @ Oulu, Finland
#35
Originally Posted by alex_mayorga View Post
Where's this development happening?
I took a look at https://garage.maemo.org/plugins/scm...hp/?root=mauku and there's no Mauku 2.0 to be seen.
In my laptop. It is the fastest and most flexible way to do development when there is only one developer.

The backend code can be found from www.microfeed.org.
 
Jaffa's Avatar
Posts: 2,535 | Thanked: 6,681 times | Joined on Mar 2008 @ UK
#36
Originally Posted by hhedberg View Post
In my laptop. It is the fastest and most flexible way to do development when there is only one developer.
I assume you're being facetious (because of the smiley) but:
  1. With the current code sitting on your laptop you'll only ever have one developer (this is the same as Nokia doing lots of stuff internally and throwing it over the wall when "finished". Other developers could follow your commits and learn, or provide useful comment if development was done in the open).
  2. "This is the fastest and most flexible way to do development" until you're hit by a bus. And then Mauku dies too.
  3. "This is the fastest and most flexible way to do development" until you accidentally rm -rf the wrong folder.
  4. "This is the fastest and most flexible way to do development" as long as you're sure you never want to refactor or experiment and know exactly what code is going to be written. Once committed you've got a safe place to go back to if your refactors/experiments don't work out.

In short (and with respect), you're wrong - you just might not know it yet ;-)
__________________
Andrew Flegg -- mailto:andrew@bleb.org | http://www.bleb.org
 

The Following 8 Users Say Thank You to Jaffa For This Useful Post:
hhedberg's Avatar
Posts: 84 | Thanked: 212 times | Joined on Nov 2007 @ Oulu, Finland
#37
Originally Posted by Jaffa View Post
I assume you're being facetious (because of the smiley) but:
  1. With the current code sitting on your laptop you'll only ever have one developer (this is the same as Nokia doing lots of stuff internally and throwing it over the wall when "finished". Other developers could follow your commits and learn, or provide useful comment if development was done in the open).

In short (and with respect), you're wrong - you just might not know it yet ;-)
I know a lot. Mauku has been open for two years. Either it has not been interesting project to contribute or I have been too active myself, since no single piece of code expect mine went to production releases. I received one patch of which I included into unstable codebase. Unfortunately, the developer of that functionality never provider update of his code to fix remaining bugs.

However, I have received nice icons for Mauku (kudos to Thomas Perl of gPodder). That is the only external contribution.

Of course, the situation may be different now. If someone is really interested contributing, there should be no problem to put code into public repository.

And one important thing: Mauku (the application) is only a small part of the whole. All other parts are totally open. The most important thing is the Microfeed backend (see the relevant thread). Also, the Mauku Widget is released under GPL, and you can see the code here: http://repository.maemo.org/extras-d.../mauku-widget/ . The application is not that different.

So, there are many spots to start helping me with Mauku.
 

The Following 3 Users Say Thank You to hhedberg For This Useful Post:
hhedberg's Avatar
Posts: 84 | Thanked: 212 times | Joined on Nov 2007 @ Oulu, Finland
#38
Mauku 2.0 beta 2 is out now.

The development of this version has focused on stability. The application should be end-user quality now.

The next version may be the final (but not the last ) The focus will be on optimisations (speed and memory consumption).

Most of the work has happened in the Microfeed backend.
 

The Following 3 Users Say Thank You to hhedberg For This Useful Post:
timsamoff's Avatar
Posts: 1,605 | Thanked: 1,601 times | Joined on Mar 2007 @ Southern California
#39
Originally Posted by hhedberg View Post
...Either it has not been interesting project to contribute or I have been too active myself...
No, I think it's because Mauku has always "just worked" -- an it looks good too.

Tim
__________________
http://samoff.com
 
yerga's Avatar
Posts: 696 | Thanked: 1,012 times | Joined on Mar 2006 @ Asturies, Spain
#40
I have been testing a bit Mauku in Fremantle and it looks good except one thing I can't found: Twitter replies.

Is this feature removed in this version? Or should I go to sleep and try again tomorrow? ;-)
__________________
Daniel Martín Yerga
maemo.org profile
Twitter
 
Reply

Tags
fremantle, jaiku, mauku, micro-blogging, qaiku, tweet, twitter


 
Forum Jump


All times are GMT. The time now is 14:25.