Am Samstag, den 05.11.2011, 21:06 +0800 schrieb PCMan:
> As I got some little free time this week, I started to implement
> "custom actions" for pcmanfm/libfm.
> I'm now trying to implement this spec proposed by the author of
> nautilus actions.
> http://www.nautilus-actions.org/?q=node/377
Why not finish 1.0 before adding new features?
> Now, I've made the decision. Let's use C/Vala and not introduce C++
> now.
Thanks!
> For the upcoming PCManFM 1.0, here is the current TODO list in my
> brain.
> 1. Finish basic custom actions (DES-EMA spec) support (required)
> 2. Try to support ~/Template folder, if possible (lower priority, may
> postponed)
> 3. Refactor job system and make it less buggy. Use UI delegate and
> reduce unnecessary signal emission. (required, may be done in vala +
> C)
> 4. Code cleanup. (required, may be done in vala + C)
> 5. Fix bugs (doing 3 and 4 might fix some existing bugs as well)
I thought the only thing that was missing for 1.0 was the tree view on
the side pane?
> For the future:
> 1. Support different filename encoding for different directories, so
> gvfs-mounted remote filesystems can have non-UTF-8 encoding.
> 2. Add "Send To" to popup menu. (no xdg spec for this, may see how
> thunar do it)
> 3. Per-folder settings (using tdb to store) (low priority, need to
> deterimine what to store for each folder)
> 4. Integrate other thumbnailers
> 5. Profiling and optimization, decrease unnecessary export symbols
> 6. Port to gtk 3
> 7. Use GtkApplication to handle IPC.
Please make a proper roadmap with versions and milestones to handle all
these new features. If you don't set yourself clearly defined goals for
each version, you will not reach your goals but slow down the overall
development. If you had focused on the tree view you could have released
1.0 months ago. Release early, release often!
The reason to tag and release a version is not only to make users and
packagers happy but to also build a common platform for further
development, so you will benefit from it, too.
Please ask yourself: How do you want to fix bugs for 1.0, when people
have to compile snapshots on their own in order to test and find bugs?
You can continue with your code from git or from your harddrive, but you
will never reach a wider audience and thus never have enough testers.
Not to mention other developers to help you.
I have to admit that I am becoming more and more disappointed by the
lack of direction and release engineering in LXDE development and I am
considering to orphan all my LXDE packages and the LXDE Spin in Fedora.
Please take a moment and ask yourself two questions:
1. When did LXDE make the most progress? Was it recently or when we
had constant releases?
2. Where do you want to see your project in 1, 2 or three years
from now?
I would like to see LXDE as a vital and developing project with a big
community. I am willing to do my part to make this happen, but IHMO this
requires that we all agree on a common roadmap and have a proper release
management.
Regards,
Christoph
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Lxde-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lxde-list
